ORA-39700 with UPGRADE option錯誤的處理
場景:透過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 ********************************************************************* |
總結:經過以上操作,便可以開啟資料庫了。可能有朋友已經發現其實這個過程也同樣適用於資料庫升級的操作。
******************************************************************************************************
本文作者:JOHN QQ:1916066696 (請備註資料庫)
ORACLE技術部落格:
ORACLE 獵人筆記 http://blog.itpub.net/12679300/
********************************************************************************************************
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12679300/viewspace-1379299/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-39700 with UPGRADE option錯誤的處理(轉)
- ORA-39700: database must be opened with UPGRADE optionDatabase
- Oracle案例04——ORA-39700: database must be opened with UPGRADE optionOracleDatabase
- 錯誤處理
- go的錯誤處理Go
- PHP 錯誤處理PHP
- php錯誤處理PHP
- Go 錯誤處理Go
- Swift錯誤處理Swift
- Zabbix錯誤處理
- mysqldump錯誤處理MySql
- axios 的錯誤處理iOS
- COM的錯誤處理 (轉)
- 錯誤處理:如何通過 error、deferred、panic 等處理錯誤?Error
- PHP錯誤處理和異常處理PHP
- Python錯誤處理Python
- ORA-00704、ORA-39700處理
- 請教 Element 的錯誤處理
- Restful API 中的錯誤處理RESTAPI
- 【譯】RxJava 中的錯誤處理RxJava
- grpc中的錯誤處理RPC
- JavaScript的錯誤簡易處理JavaScript
- 【故障處理】ORA-12162 錯誤的處理
- 前端的水平線,錯誤處理和除錯前端除錯
- 異常錯誤資訊處理
- PHP 核心特性 - 錯誤處理PHP
- 常用模組 PHP 錯誤處理PHP
- laravel9 錯誤處理Laravel
- 淺談前端錯誤處理前端
- Oracle異常錯誤處理Oracle
- ORACLE 異常錯誤處理Oracle
- 15-錯誤處理(Error)Error
- 學習Rust 錯誤處理Rust
- Go語言之錯誤處理Go
- GOLANG錯誤處理最佳方案Golang
- Objective-C:錯誤處理Object
- javascript之處理Ajax錯誤JavaScript
- 搭建dataguard時,錯誤處理