ORA-39700 with UPGRADE option错误的处理
通过rman做一个数据库的异机恢复，进行到最关键的一步，打开数据库的时候报了错误，详细如下
场景：通过rman做一个数据库的异机恢复，进行到最关键的一步，打开数据库的时候报了错误，详细如下
SQL> startup mount;
Oracle 例程已经启动。
Total System Global Area 6797832192 bytes
Fixed Size 2241264 bytes
Variable Size 3523218704 bytes
Database Buffers 3254779904 bytes
Redo Buffers 17592320 bytes
数据库装载完毕。
SQL> alter database open resetlogs;
alter database open resetlogs
*
第 1 行出现错误:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
进程 ID: 3650
会话 ID: 292 序列号: 5
问题原因：进行数据库报错的时候才突然想起犯了一个错误原数据库的版本是11.2.0.1，但是目标数据库的版本是11.2.0.3，，所以在打开的时候就提示了0RA-39700。
解决方法：通过upgrade的方式打开数据库，如下
[oracle@ekptest001 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on 星期三 12月 24 15:31:16 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
已连接到空闲例程。
SQL> startup mount;
ORACLE 例程已经启动。
Total System Global Area 6797832192 bytes
Fixed Size 2241264 bytes
Variable Size 3523218704 bytes
Database Buffers 3254779904 bytes
Redo Buffers 17592320 bytes
数据库装载完毕。
SQL> alter database open upgrade;
数据库已更改。
SQL> select status from v$Instance;
STATUS
------------------------------------
OPEN MIGRATE
SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql;
其中运行catupgrd.sql脚本花费了30分钟，完成后会自动关闭数据库，就可以正常打开了。
原理：当数据库的升级的时候，数据库内部的基表进行了变更，数据字典也需要进行相应的更新，运行catupgrd.sql会进行相应对象更新；
[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, 2011, 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 the
Rem c0x0x0x0.sql for the release. This performs all
Rem necessary dictionary upgrade actions to bring the
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 should be no error messages
generated; all normal upgrade error messages are suppressed.
If this script is being re-run after correcting some problem, then
expect the following error which is not automatically suppressed:
ORA-00001: unique constraint (
possibly in conjunction with
ORA-06512: at "
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 *********************************************************************
总结：经过以上操作，便可以打开数据库了。可能有朋友已经发现其实这个过程也同样适用于数据库升级的操作。
本文永久更新链接地址：
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
When might a full table scan be faster than using an index in MySQL?
Apr 09, 2025 am 12:05 AM
Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.
Explain InnoDB Full-Text Search capabilities.
Apr 02, 2025 pm 06:09 PM
InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.
Can I install mysql on Windows 7
Apr 08, 2025 pm 03:21 PM
Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.
Difference between clustered index and non-clustered index (secondary index) in InnoDB.
Apr 02, 2025 pm 06:25 PM
The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.
MySQL: Simple Concepts for Easy Learning
Apr 10, 2025 am 09:29 AM
MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.
Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial).
Apr 02, 2025 pm 07:05 PM
MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
The relationship between mysql user and database
Apr 08, 2025 pm 07:15 PM
In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.
Can mysql and mariadb coexist
Apr 08, 2025 pm 02:27 PM
MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
