| 10g ORA-01033 Shutdown in process [message #122076] |
Thu, 02 June 2005 14:01  |
sophietje
Messages: 8
Registered: June 2005
|
Junior Member |
|
|
I've been searching the archives for a couple hours for help with this, but to no avail....
(I'm a pl/sql programmer and out dba had to have emergency surgery this morning and isn't contactable... so be gentle, please...)
We're getting the ORA-1033 error when connecting via SQL*PLUS. Not sure what caused the issue initially, but several attempts to restart the server has not helped. Most posts have suggested waiting it out, but it's already been 2 hours and it still hasn't fixed itself.
Through reading, I've gathered that I probably need to do a "shutdown immediate", but I can't figure out where I would do that since I can't connect at all to SQL*PLUS.
Any clues? This is a 10g db running on windows.
many thanks....
|
|
|
|
| Re: 10g ORA-01033 Shutdown in process [message #122085 is a reply to message #122076] |
Thu, 02 June 2005 14:55  |
sophietje
Messages: 8
Registered: June 2005
|
Junior Member |
|
|
since last posting, I've figured out how to shutdown the db using sql*plus. I tried both shutdown immediate and shutdown abort.
Both resulted in the db shutting down saying: ORACLE instance shut down.
however, after it's shutdown, I type startup and the result is:
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
ORA-12528: Message 12528 not found; product=RDBMS; facility=ORA
I also tried startup mount, with the same result....
update:
several hours(?) later, my co-progammer and I decided to see if we could find the alert log. we found what was causing the error: the db_recovery_file_dest_size was too small. Altered that, did a shutdown normal and startup and it is running correctly now.
So anyone who finds this post looking for a solution, I suggst looking in the alert log.
[Updated on: Thu, 02 June 2005 17:03] Report message to a moderator |
|
|
|
| Re: 10g ORA-01033 Shutdown in process [message #123117 is a reply to message #122085] |
Thu, 09 June 2005 21:46 |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
hi
Just do one thing delete your archive file .. or better shift from its current loaction to another location so that there can be space where your archive was generating.... your error was b'coz arch process not able to write on the specified location as the location was totally filled... now reboot your server then try to start the database by startup mount and then alter the database so the user can connect... still if user are not able to connect then start listener.....
I hope it should work still if you get error then let me know
From:- sunilkumar
|
|
|
|
|
|
| Re: 10g ORA-01033 Shutdown in process [message #123253 is a reply to message #123217] |
Fri, 10 June 2005 16:19 |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
hi ...
Yea dont delete your archive file ..... just shift archive file form its location so that there can be free space on that location .... and once your issue is resolved ... take backup of the database (cold backup) and then you can delete the archive file from where you had shifted....
From:- sunilkumar
|
|
|
|
| Re: 10g ORA-01033 Shutdown in process [message #397094 is a reply to message #122085] |
Wed, 08 April 2009 21:41 |
antgaudi
Messages: 5
Registered: April 2009
|
Junior Member |
|
|
| Quote: | I decided to see if we could find the alert log. we found what was causing the error: the db_recovery_file_dest_size was too small. Altered that, did a shutdown normal and startup and it is running correctly now.
|
What do you mean that you altered? How is the step-by-step process to correct the issue?
Thanks.
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
