DB Listener does not start

Hello,

My db listener doesn't restart when my server boots up or is rebooted? Does anyone know what the problem could be?

I had a batch file set up as a scheduled task to do it for a while, but has mysteriously stopped working. Would really like to get the core problem sorted.

At the moment my db is off line. Not good!!
When I try to connect to the DB I get the error -

Quote:

---

ORA-01034: Oracle Not available
ORA-27101: Shared memory realm does not exist

---

I also get an error when the server starts saying that a service failed to start and to check the event log. On inspection there are two -
[list=1][*]The OracleOraHome81HTTPServer service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.[*]The OracleOraHome81HTTPServer service hung on starting[/list=1]

Don't know whether this info is relevant?

Any help will be greatly appreciated.

Regards Al

Quote:

---

Originally posted by Running Bear
I had a batch file set up as a scheduled task to do it for a while, but has mysteriously stopped working.

---

What happens if you execute these individual commands at the command prompt? Diagnostics? ORACLE_SID set correctly?

Are all the required Win Services there? Can you start them manually?

Sure it's the listener? (The ORA- msgs look like the instance isn't running - I could be wrong.) Have you tried lsnrctl?

say
net stop oracleservice then start the oracle service

net start oracleservice and then

start the listener

lsnrctl start

also make sure u have set the ORACLE_SID at the command prompt

regards
anandkl

Dapi, Crickey! Your're a busy bee. Thanks for all the pointers will give them a go on Tue

Anandkl, Thanks for the suggestion will also try that out.

I managed to get the db back up recreating the service using oraDim and took a back up of the data. I then rebooted the server so see whether the problem was sorted sinc then I've been unable to get the db up again and the oraDim option doesn't work any more.

So will try your suggestions in earnest on Tue. No that I've got the data off as a last resort I'll blow the whole thing away and start again.

Cheers Al

Quote:

---

Originally posted by Running Bear
Crickey! Your're a busy bee.

---

I see it as a learning experience and a chance to experiment without putting my db's at risk ;)

Now this IS a coincidence.

I've been creating a 9.2 db at home and had a brain fart while creating the startup job:

sqlplus /

gives the error you have seen. (DON'T ask why!)

It works better as:
sqlplus "/ as sysdba"
OR
sqlplus /nolog @startup.sql (with a connect command in the .sql)

FURTHERMORE

That error is given if you CAN connect (services started) and then try to execute a command, other than a startup command, against an instance that is not started.

Dapi & Anandkl,

Hello, thanks for your help with this, one of my colleagues managed to get the DB working again over the weekend unfortunately he's out until Friday so I don't know what he did to get it sorted.

Many thanks again

Regards Al