Oracle Ora-01033 Oracle Initialization Or Shutdown In Progress
ORA-00600 is Oracle's generic message for un-handled internal exceptions i.e. Usually they require us to raise an SR with Oracle Support. This can be a problem for sites who are using Oracle without a support contract. Cs 2.0 download mega. In that situation we are thrown on the resources of the internet. The problem you are experiencing is due to a corrupted.
I had installed Oracle 11g on windows 07,everything was working fine.But today it is giving me an error saaying ORA-01033: ORACLE initialization or shutdown in progress . I followed the steps mentioned in the different communities but unable to solve the error. After connecting as sqlplus sys/sys as sysdba. and executing below statement,i got following error. How to solve this error?
Thanks in advance!!
maheshmahesh
Oracle Ora-01033 Oracle Initialization Or Shutdown In Progress Today
2 Answers
First, check your ALERT.LOG file typically located in D:apporaclediagrdbmsDBNAMESIDtrace.
The latest entries in your ALERT.LOG should give you an indication on what is going on. Is the database starting? Shutting down?
Should the database be stuck in the shutdown process, you can try to kill the oracle.exe process and then restart the database via Windows Service.
Often, when the database seems to hang on startup, it is actually applying REDO to get a consistent state, so pay close attention on what the ALERT.LOG tells you.
There's more info needed to be able to solve similar issues. Questions like these are interesting to get answered:
- To what level can you start the database ? None, nomount, mount oropen (exclude the last one in this case)
- What does the ALERT.LOG file show ? This from the moment the firstissue is suspected to be around
- An obvious question is just : what happened ? What action were youdoing when you saw the first error message ?
- Can you shutdown the database ? If yes, which methods : normal,immediate or abort only ? Know that stopping the database with ABORToption may make problems bigger as they are already.
- Did you try rebooting the server ? This is particularly an issue onWindows, which is your case.
- Depending on how you stopped the database, do you have a cold backup?
- Depending on RMAN still working : can you take a backup ? The RECOVERY you were trying is not bad, but it could be interesting to know what is happening on OS level with that file; Is it there ? If yes, is it locked or not ? Does the OS think it's a valid file ?