ORA-01679: database must be mounted EXCLUSIVE and not open to activate
Subject: | ORA-01679 When Activating the Standby Database | |||
Doc ID: | Note:123133.1 | Type: | PROBLEM | |
Last Revision Date: | 04-MAY-2004 | Status: | PUBLISHED |
Problem Description ------------------- You try to activate the standby database and you get the following error: SVRMGR> alter database activate standby database; alter database activate standby database * ORA-01679: database must be mounted EXCLUSIVE and not open to activate Solution Description -------------------- Solution 1: Verify the standby site init.ora file does not have the parameter parallel_server=true. This parameter should not be set on the standby site.
Solution 2: 1. Shutdown the standby database 2. Start the standby instance 3. Mount the instance as a standby database 4. Activate the standby database Explanation ----------- The standby database has been opened in READ ONLY mode. Though you recovered the standby database by applying the appropriate archive log files, the standby database has to be shut down and then restarted in mounted mode. Test ---- ========================================== Start the STANDBY database in mounted mode ========================================== SVRMGR> startup nomount ORACLE instance started. Total System Global Area 23482352 bytes Fixed Size 69616 bytes Variable Size 6455296 bytes Database Buffers 16777216 bytes Redo Buffers 180224 bytes SVRMGR> alter database mount standby database; Statement processed. SVRMGR> select instance_name,status from v$instance; INSTANCE_NAME STATUS ---------------- ------- std MOUNTED 1 row selected. SQL> select name, open_mode, controlfile_type from v$database; NAME OPEN_MODE CONTROL --------- ---------- ------- PRIM MOUNTED STANDBY =========================================== Open the STANDBY database in READ ONLY mode =========================================== SVRMGR> alter database open read only; Statement processed. SVRMGR> select instance_name,status from v$instance; INSTANCE_NAME STATUS ---------------- ------- std OPEN 1 row selected. SQL> select name, open_mode, controlfile_type from v$database; NAME OPEN_MODE CONTROL --------- ---------- ------- PRIM READ ONLY STANDBY 1 row selected. =============================================== Reset the STANDBY database back in mounted mode =============================================== SVRMGR> recover standby database; ORA-00279: change 93581 generated at 09/01/2000 17:13:52 needed for thread 1 ORA-00289: suggestion : /filer1/archivelogs/aleger/stdby/arch_1_454.arc ORA-00280: change 93581 for thread 1 is in sequence #454 Specify log: {=suggested | filename | AUTO | CANCEL} /filer1/archivelogs/aleger/primary/arch_1_454.arc Log applied. Media recovery complete. SVRMGR> select instance_name,status from v$instance; INSTANCE_NAME STATUS ---------------- ------- std MOUNTED 1 row selected. SVRMGR> select name, open_mode from v$database; NAME OPEN_MODE --------- ---------- PRIM MOUNTED 1 row selected. ============================= Activate the STANDBY database ============================= SVRMGR> alter database activate standby database; alter database activate standby database * ORA-01679: database must be mounted EXCLUSIVE and not open to activate ============================================ Restart the STANDBY database in mounted mode ============================================ SVRMGR> shutdown immediate ORA-01109: database not open Database dismounted. ORACLE instance shut down. SVRMGR> startup nomount ORACLE instance started. Total System Global Area 23482352 bytes Fixed Size 69616 bytes Variable Size 6455296 bytes Database Buffers 16777216 bytes Redo Buffers 180224 bytes SVRMGR> alter database mount standby database; Statement processed. ============================= Activate the STANDBY database ============================= SVRMGR> alter database activate standby database; Statement processed. SVRMGR> select instance_name,status from v$instance; INSTANCE_NAME STATUS ---------------- ------- std STARTED 1 row selected. SVRMGR> select name, open_mode from v$database; NAME OPEN_MODE --------- ---------- ORA-01507: database not mounted =============================================================== Follow the normal procedure to open the STANDBY database as the PRIMARY database =============================================================== SVRMGR> shutdown immediate ORA-01507: database not mounted ORACLE instance shut down. SVRMGR> exit $ ORACLE_SID=prim $ svrmgrl SVRMGR> connect / as sysdba Connected. SVRMGR> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SVRMGR> exit Server Manager complete. $ ORACLE_SID=std $ svrmgrl SVRMGR> connect / as sysdba Connected. SVRMGR> startup ORACLE instance started. Total System Global Area 23482352 bytes Fixed Size 69616 bytes Variable Size 6455296 bytes Database Buffers 16777216 bytes Redo Buffers 180224 bytes Database mounted. Database opened. SVRMGR> select instance_name,status from v$instance; INSTANCE_NAME STATUS ---------------- ------- std OPEN 1 row selected. SQL> select name, open_mode, controlfile_type from v$database; NAME OPEN_MODE CONTROL --------- ---------- ------- PRIM READ WRITE CURRENT
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/35489/viewspace-84841/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- How a Database Is Mounted (293)Database
- How a Standby Database Is Mounted (295)Database
- How a Clone Database Is Mounted (296)Database
- cannot mount database in EXCLUSIVE modeDatabase
- Exclusive access could not be obtained because the database is in useAIDatabase
- How a Database Is Mounted with Real Application Clusters (294)DatabaseAPP
- [20170302]關於activate standby databaseDatabase
- ARC1: Thread not mounted lead to database not mountingthreadDatabase
- alter database open resetlogs;Database
- Tasks of a Database Administrator : Create and Open the Database (10)Database
- ORA-39700: database must be opened with UPGRADE optionDatabase
- ORA-01102: cannot mount database in EXCLUSIVE modeDatabase
- ORA-01102 cannot mount database in EXCLUSIVE modeDatabase
- [Oracle] ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- 關於ORA-01102: cannot mount database in EXCLUSIVE modeDatabase
- Oracle ORA-01102故障: cannot mount database in EXCLUSIVE modeOracleDatabase
- What Happens When You Open a Database (297)APPDatabase
- Oracle案例04——ORA-39700: database must be opened with UPGRADE optionOracleDatabase
- RAC 11.2.0.3 ORA-01102: cannot mount database in EXCLUSIVE mode”Database
- 恢復備庫 activate standby database 報錯找不到standby redo - ORA-00313Database
- ORA-16009: remote archive log destination must be a STANDBY databaseREMHiveDatabase
- ORA-01102: cannot mount database in EXCLUSIVE mode 的解決辦法Database
- Oracle 11g RAC ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- InfluxDB 2.x Open Source Time Series DatabaseUXDatabase
- Open a Database in Read-Only Mode (301)Database
- Summary For Forcing The Database Open With `_ALLOW_RESETLOGS_CORRUPTION`Database
- ORA-16433 The database must be opened in read write mode故障解決Database
- Oracle 11g 報錯ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- 啟動資料庫時 ORA-01102: cannot mount database in EXCLUSIVE mode資料庫Database
- oracle ORA-01102: cannot mount database in EXCLUSIVE mode(無法起到獨佔模式)OracleDatabase模式
- Oracle Data Guard Failover(activate)OracleAI
- 12C-ORA-65086: cannot open/close the pluggable databaseDatabase
- 部署 11G 物理DataGuard時 ALTER DATABASE OPEN 報錯Database
- Oracle startup mount exclusive作用Oracle
- WM Activate Storage Bin Type Search(十四)
- ORA-1113 signalled during: alter database open...Database
- It's a must to ghd
- 物理備庫open報錯ORA-10458: standby database requires recoveryDatabaseUI