Problems after a live reboot of the machine

Today our server was having problems letting people on, so in his infinite wisdom the sysadmin had the server rebooted, of course Oracle, Applications, and the rest of the bunch were all up and running at the time.

After I found out and the machine was up, I tried to start the demo database that was just installed (8.1.6). Svrmgrl, connect internal, startup. I figured if anything happened in the reboot it would let me know after trying to start it up. I get a "not connected to oracle" error. I try to log in, it says a startup/shutdown is in progress. I try to shut it down, and it gives me a "not connected to oracle" no matter what I do.

I start checking the Alert logs, there are a bunch of these:


Errors in file /app/oralmc/demodb/8.1.6/admin/udump/demo_ora_8359.trc:
ORA-07445: exception encountered: core dump [lxdgetobj()+60] [SIGSEGV] [Address
not mapped to object] [1886351316] [] []


I'm assuming there isn't much I can do other than Open a TAR and hope I can get it open, or re-install (it's the vision demo database installed with applications). I don't have a backup yet because I just installed it yesterday, and didn't have the disk space to temporarily store the files I needed, or have the sysadmin available to dump it to tape.

It's not a huge loss, it's just the canned demo database anyway, just a pain how things tend to work out.

Before you open the server manager check your environment variables whether they had been set correctly.

ORACLE_HOME
LD_LIBRARY_PATH
PATH
CLASSPATH
ORACLE_SID=sid

To me it looks like that you have not set your demo_db's sid on the ORACLE_SID env variable. as a result, when you get to open the server manager and ask it to connect internal, it does not know of where to connect.

Also make sure that the database name is set on the tnsnames.ora and the listeners are there to listen.

Good luck
Sam

hi pat,

I am also in the process of installing vision database on sun sparc solaris 2.6

can u tell me what exactly are the initial requirements,since u have done, its easy to talk to u now .

I will be starting it tomorrow.

thanks

It sounds like Oracle still thinks he's up. As Sam said, make sure your environment variables are setup correctly. You can set them by sourcing the DEMO.env file probably in /app/oralmc/demodb/816.

If that doesn't work, start svrmgrl, connect internal, and shutdown abort. Then look for $ORACLE_HOME/dbs/lkDEMO. You can then remove this file (or move it to another file) and try to start your db.

Also, make sure your concurrent managers are down while your are doing all this...

Env's were set the whole time, but following the shutdown abort/lkDEMO, I was able to get it open. Thanks for the help.

Jeff: What was the significance of removing lkDEMO?

Yenni, here are the space requirements for my the different homes.


oralmc@irad-rms:/app/oralmc> cd /app/oralmc/demodb (this is the oracle home)
oralmc@irad-rms:/app/oralmc/demodb> du -sk
680727 .
oralmc@irad-rms:/app/oralmc/demodb> cd /app/applsand (this is appl top)
oralmc@irad-rms:/app/applsand> du -sk
7869452 .
oralmc@irad-rms:/app/applsand> cd /u12/oradata/demodata (this is the data home for data/index)
oralmc@irad-rms:/u12/oradata/demodata> du -sk
7275073 .
oralmc@irad-rms:/u12/oradata/demodata> cd /u10/oradata/demodata (this is data home for sys/log)
oralmc@irad-rms:/u10/oradata/demodata> du -sk
3853929 .
oralmc@irad-rms:/u10/oradata/demodata>

Pat,
AFAIK, If you want, you can play with sql.bsq little bit but, definitely not with lkXXXX file. You can't bring your database up without that file. I do not have some insight information on it. I appreciate, if someone could throw light on it.

Quote:

---

Originally posted by pwoneill
Jeff: What was the significance of removing lkDEMO?

---

I'm not exactly sure what it does, but it has something to do with saving the state your last startup/shutdown. If your database is down and you remove the file it will be re-created upon startup. I had a problem similar to yours and when I called Oracle Support, they told me to delete this file.

Actually, if you take a look at the file it contains "DO NOT DELETE THIS FILE!". Just when you think you have a firm grasp on Oracle...