Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later
Problem:- (trying to upgrade a older database via patch set fail.)
today i face this problem when my junior dba trying to ready a test
database with oracle database 10.2.0.3 version .
first he install oracle 10.2.0.3 then
he trying to install patch set for 10.2.0.4 .
but somehow the installation of patch set fail...then he found this problem.
Recovery of an older database version backup results in error upon database open:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
ORA-01092: ORACLE instance terminated. Disconnection forced
Error occurs because the current database version is newer than the backup datafiles, upgrade
steps must be taken which require the database to be started with the UPGRADE option.
When a database is upgraded from one version to another, the database must be started with UPGRADE
option to execute the necessary upgrade steps. The database cannot be opened in read write under
the new version until these steps are taken. This justifies cause.
If incomplete recovery is required, the database should be opened with:
SQL> alter database open resetlogs upgrade;
If an attempt to open the database without the upgrade option, the error will occur. This can be resolved with the steps documented below.
To implement the solution, please execute the following steps:
1. Perform restore and recovery.(if necessary)
or can do
SQL> startup nomount pfile=d:/pfile/init.4646464666.ora ;
SQL> alter database mount ; --or alter database mount exclusive ;
SQL> alter database open upgrade ;
SQL> @catupgrd.sql ---and catproc.sql---(from oracle_home/rdbms/admin/)
----Perform necessary upgrade steps as documented in the readme file for the
----patch/upgrade you applied. For example, catupgrd.sql.
SQL> create spfile from pfile='d:/pfile/init.4646464666.ora' ;
SQL> shutdown immediate ;
SQL> startup ;
SQL> ---take a backup
NOTE: any attempts to recover after the upgrade steps (especially with 'using backup
controlfile') will result in error. In addition, there is no need to use the RESETLOGS option
upon open. The key here is after the upgrade, the database should be opened with STARTUP.
Instance recovery and the fact that the controlfile is now CURRENT, will allow Oracle to apply the
necessary information in the online redo log files and startup the database.