Errors in file c:\hvisa\udump\prod_ora_5372.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Tue Mar 25 11:47:12 2008
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Tue Mar 25 11:47:12 2008
Errors in file c:\hvisa\bdump\prod_pmon_5380.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:12 2008
Errors in file c:\hvisa\bdump\prod_reco_5084.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:12 2008
Errors in file c:\hvisa\bdump\prod_smon_4212.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:12 2008
Errors in file c:\hvisa\bdump\prod_ckpt_5464.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:13 2008
Errors in file c:\hvisa\bdump\prod_lgwr_5968.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:13 2008
Errors in file c:\hvisa\bdump\prod_dbw0_5696.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:13 2008
Errors in file c:\hvisa\bdump\prod_mman_4696.trc:
ORA-00704: bootstrap process failure
Tue Mar 25 11:47:13 2008
Errors in file c:\hvisa\bdump\prod_psp0_1708.trc:
ORA-00704: bootstrap process failure
Instance terminated by USER, pid = 5372
ORA-1092 signalled during: alter database open...
al the BD process were corrupted...
So how do i overcome this problem... Anyone can help me..
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
If you are upgrading your database, do it properly.
If you are not upgrading your database and you have multiple ORACLE_HOME on the box you are probably trying to start a database using the wrong Oracle version.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Look for trace files in the background_dump_dest and check the alert.log.
You might find some trace files for the smon or pmon process indicating the real problem.
Mostly this error can be caused by the following:
1. A shutdown abort
2. Incorrect permissions of BDUMP, CDUMP or UDUMP directories
3. Missing datafiles
4. Renaming files when Oracle is down
and some times due to OS issues as well.
If you are trying to do any DB upgrade then follow the supporting documents.
Reply With Quote
Originally Posted by basmgokul
Bookmarks