Printable View
Hi gurus,
I first get a too many processes message when I try to connect.
I raised the processes parameter...
Then,
SVRMGR> shutdown immediate
ORA-01034: ORACLE not available
SVRMGR> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
What do I do?
This is urgent..my db is down!
If you are running o unix. Try running
/usr/proc/bin/ptree
and it may return ALOT of processes such as the following...
26694 oracleCFA (DESCRIPTION=(LOCAL=no)(ADDRESS=(PROTOCOL=BEQ)))
In startup, init.ora, you scecifiy how many process Oracle may keep running at anyone time. In your case, when you try and log in, Oracle senses you trying to exceed this and returns the error you are seeing.
You are going to have to manually kill at least one process, before you can log in.
The big question is WHY is it occuring. I have this issue currently, we are running a Websphere front end, and webphere keeps the Oracle processes alive if somebody drops out of Websphere, which is a real pain in the butt, because it means websphere has to be manually stopped and restarted periodically in order to release the Oracle processess. You may be having a similer issue.
Hope this helps.
Cheers,
Thanks John,
You gave me exactly what I needed!
Cheers!
When you, issue the shutdown immediate and still if you see oracle not available, then it would be the time to just abort the oracle instace through shutdown abort...
SVRMGR> shutdown immediate
ORA-01034: ORACLE not available
SVRMGR> shutdown abort
SVRMGR> startup mount
SVRMGR> recover database
SVRMGR> alter database open;
This would be the way to go...
Sam
You can try one more thing.
In this situation.
STARTUP FORCE
Will start the database ignoring the earlier errors.
Kishore
This is quiet unsafe!!
Sam
It is quite a risky game to startup force :-) If you then get the 1019 error, you'll need to manually remove the old SGA.
I think it´s ok if you do
alter system checkpoint
startup force
shutdown immediate
startup
I once played the game of startup force and got into trouble... Its not worth the trouble that you have to go through to get it back if it goes wrong!!!
This is my personal opinion. I would take a long shot and save time....
Sam
Ahhh guys.... it was the number of processes running on the server. It wouldn't mater what shutdown method you used, if the number of processes have maxed out, you wouldn't be able to connect to do any on that until you kill one of the Dedicated Oracle processes in the background..
Cheers,
The error was in relation to not running out of processes, it could be a case that the shutdown operation earlier was interrupted too. So the shutdown abort will abort the database, no matter whether it runs out of the # of processes or not.
Sam
Hmmm, yes, looking back at the error, the user was connected to Oracle at the time shutdown was attempted, it may not have been a max number of processes. BUT, if if you do max out the processes, you still won't be able to connect to shutdown the database without first killing another process.
Cheers,
Same here Sam, easy to come into a situation when you have to manually remove the old SGA...Quote:
Originally posted by sambavan
I once played the game of startup force and got into trouble... Its not worth the trouble that you have to go through to get it back if it goes wrong!!!
This is my personal opinion. I would take a long shot and save time....
Sam
Using STARTUP FORCE is absolutely no more dangerous then using SHUTDOWN ABORT + STARTUP..... In fact , it is only a one-comand operation that performs SHUTDOWN ABORT and then starts up the database. Only a short cut to save some typing, nothing more dangerous than SHUTDOWN ABORT about it.
And Sam, I see no reason to perform step no.3 in the following sequence of statements - Oracle will do it for you automaticaly.
It would be exactly the same if you simply use:Quote:
Originally posted by sambavan
SVRMGR> shutdown abort
SVRMGR> startup mount
SVRMGR> recover database
SVRMGR> alter database open;
SVRMGR> shutdown abort
SVRMGR> startup
And it would be exactly the same if you simply use
SVRMGR> startup force
[Edited by jmodic on 10-31-2001 at 03:36 PM]