Handling of ORA-39700 with UPGRADE option errors

Handling of ORA-39700 with UPGRADE option errors

Scenario: Use rman to recover a database from a different machine, and perform the most critical step. An error is reported when the database is opened. The details are as follows:

SQL> startup mount;

The Oracle routine has been started.

Total System Global Area 6797832192 bytes

Fixed Size 2241264 bytes

Variable Size 3523218704 bytes

Database Buffers 3254779904 bytes

Redo Buffers 17592320 bytes

The database has been loaded.

SQL> alter database open resetlogs;

Alter database open resetlogs

*

Row 3 has an error:

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure.

ORA-39700: database must be opened with UPGRADE option

Process ID 3650

Session ID: 292 serial number: 5
 

Cause: When a database error is reported, the original database version is 11.2.0.1, but the target database version is 11.2.0.3. Therefore, the 0RA-39700 is prompted when the database is opened.

Solution: Open the database through upgrade, as shown below:

[Oracle @ ekptest001 ~] $ Sqlplus/as sysdba

SQL * Plus: Release 11.2.0.3.0 Production on Wednesday December 24 15:31:16 2014

Copyright (c) 1982,201 1, Oracle. All rights reserved.

Already connected to the idle routine.

SQL> startup mount;

The ORACLE routine has been started.

Total System Global Area 6797832192 bytes

Fixed Size 2241264 bytes

Variable Size 3523218704 bytes

Database Buffers 3254779904 bytes

Redo Buffers 17592320 bytes

The database has been loaded.

SQL> alter database open upgrade;

The database has been changed.

SQL> select status from v $ Instance;

STATUS

------------------------------------

OPEN MIGRATE

SQL> @ $ ORACLE_HOME/rdbms/admin/catupgrd. SQL;
 

It takes 30 minutes to run the catupgrd. SQL script. After the script is completed, the database is automatically shut down to enable it normally.

Principle: When the database is upgraded, the base table in the database is changed, and the data dictionary needs to be updated accordingly. When you run catupgrd. SQL, the corresponding objects are updated;

[Oracle @ ekptest001 admin] $ cat catupgrd. SQL

Rem

Rem $ Header: rdbms/admin/catupgrd. SQL/st_rdbms_11.2.0/3 2011/05/18 15:07:25 cmlim Exp $

Rem

Rem catupgrd. SQL

Rem

Rem Copyright (c) 1999,201 1, Oracle and/or its affiliates.

Rem All rights reserved.

Rem

Rem NAME

Rem catupgrd. SQL-CATalog UPGraDe to the new release

Rem

Rem DESCRIPTION

Rem This script is to be used for upgrading a 9.2, 10.1 or 10.2

Rem database to the new release. This script provides a direct

Rem upgrade path from these releases to the new Oracle release.

Rem

Rem The upgrade is partitioned into the following 5 stages:

Rem STAGE 1: call the "I" script for the oldest supported release:

Rem This loads all tables that are necessary

Rem to perform basic DDL commands for the new release

Rem STAGE 2: call utlip. SQL to invalidate PL/SQL objects

Rem STAGE 3: Determine the original release and call

Rem c0x0x0x0. SQL for the release. This performs all

Rem necessary dictionary upgrade actions to bring

Rem database from the original release to new release.

Rem

Rem NOTES

Rem

Rem * This script needs to be run in the new release environment

Rem (after installing the release to which you want to upgrade ).

Rem * You must be connected as sysdba to run this script.

Rem

Rem MODIFIED (MM/DD/YY)

Rem skabraha 05/16/11-Backport skabraha_bug-11823179 from main

Rem cmlim 05/12/11-Backport cmlim_bug-12337546 from main

Rem skabraha 07/29/10-Backport skabraha_bug-9928461 from main

Rem cdilling 03/29/07-set error logging off-bug 5959958

Rem rburns 12/11/06-eliminate first phase

Rem rburns 07/19/06-fix log miner location

Rem rburns 05/22/06-restructure for parallel upgrade

Rem rburns 02/15/06-re-run message with expected errors

Rem gviswana 03/09/06-Add utlrdt

Rem rburns 02/10/06-fix re-run logic for 11.1

Rem rburns 01/10/06-release 11.1.0

Rem rburns 11/09/05-version fixes

Rem rburns 10/21/05-remove 817 and 901 upgrades

Rem cdilling 09/28/05-temporary version until db version updated

Rem ssubrama 08/17/05-bug 4523571 add note before utlip

Rem sagrawal 06/28/05-invalidate PL/SQL objects for upgrade to 11

Rem rburns 03/14/05-dbms_registry_sys timestamp

Rem rburns 02/27/05-record action for history

Rem rburns 10/18/04-remove catpatch. SQL

Rem rburns 09/02/04-remove dbms_output compile

Rem rburns 06/17/04-use registry log and utlusts

Rem mvemulap 05/26/04-grid mcode compatibility

Rem jstamos 05/20/04-utlip workaround

Rem rburns 05/17/04-rburns_single_updown_scripts

Rem rburns 01/27/04-Created

Rem

DOC

######################################## ###############################

######################################## ###############################

The first time this script is run, there shoshould be no error messages

Generated; all normal upgrade error messages are suppressed.

If this script is being re-run after correcting some problem, then

Failed CT the following error which is not automatically suppressed:

ORA-00001: unique constraint (<constraint_name>) violated

Possibly in conjunction

ORA-06512: at "<procedure/function name>", line NN

These errors will automatically be suppressed by the Database Upgrade

Assistant (DBUA) when it re-runs an upgrade.

######################################## ###############################

######################################## ###############################

#

Rem Initial checks and RDBMS upgrade scripts

@ Catupstr. SQL

Rem catalog and catproc run with some multiprocess phases

@ Catalog. SQL -- CATFILE-X

@ Catproc. SQL -- CATFILE-X

-- CATCTL-S

Rem Final RDBMS upgrade scripts

@ Catupprc. SQL

Rem Upgrade components with some multiprocess phases

@ Cmpupgrd. SQL -- CATFILE-X

-- CATCTL-S

Rem Final upgrade scripts

@ Catupend. SQL

Rem Set errorlogging off

Set errorlogging off;

Rem end of catupgrd. SQL

REM bug 12337546-Exit current sqlplus session at end of catupgrd. SQL.

REM This forces user to start a new sqlplus session in order

REM to connect to the upgraded db.

Exit

Rem *************************************** ******************************

Rem END catupgrd. SQL

Rem *************************************** ******************************

Conclusion: After the above operations, you can open the database. Some may have discovered that this process also applies to Database Upgrade operations.