ORA-3113 in database startup(open) URGENT ?

Quote:

---

Originally posted by csvenkata
Shutdown the NT Server and restart and try starting the database. It believe it will work.

---

I also think that this should work. And that's what I suggested him but he say it doesn't help.

Now, do that:

1. Open the "Services" dialog box from the NT Control Panel.

2. Click on the OracleService then click the "Startup..." button.

3. Change the "Log on as:" information to "This Account: "
plus the appropriate password where = the person who created
the services.

4. Repeat steps 2 & 3 for the OracleStart service.

5. Try again to startup the DB

Tell me: have you rebooted the server during the last few days and do you find ORA-00600 in the trace files.

Dear Freinds,

Don't use SHUTDOWN IMMEDIATE on Oracle 8.1.6. If you shoutdown with IMMEDIATE option sometimes datafile will corrupt. This is a Bug in Oracle 8.1.6. We have financial running under Oracle 8.1.6. Last month what happened know our DBA shutdown our database with IMMEDIATE option. Its takes along time to shutdown. Finally one datafile was corrupted we could 't startup the Database again. some Java classes having problem. So please don't use IMMEDIATE option in Oracle 8.1.6.

Thanks

Ram

Check if all the Oracle services are running. If yes try stopping all the services and then restart all the services.

This might help

Quote:

---

Originally posted by Ram
Don't use SHUTDOWN IMMEDIATE on Oracle 8.1.6. If you shoutdown with IMMEDIATE option sometimes datafile will corrupt. This is a Bug in Oracle 8.1.6.

---

One of the many bugs in 8.1.6 :-)

Refer the metalink on the ORA-3113. This can occour on a wide range of scenarios. Oracle has a note on this error.

Sam

I had this problem before. The solution for my case was:

1. set the sid.
2. net stop oracleservicesid.
3. using oradim to drop and recreate oracleservicesid.
4.startup database.

It appears as if it is mounted but having trouble opening. Check the alert log and see if there is an error relating to the startup. Post the information on the startup from the alert so we can review.

Quote:

---

Originally posted by lgaorcl
I had this problem before. The solution for my case was:

1. set the sid.
2. net stop oracleservicesid.
3. using oradim to drop and recreate oracleservicesid.
4.startup database.

---

I have also had it and your solution is the right one. I think it even worked without 3.