Oracle Data Guard Failover(activate)

最新推荐文章于 2019-07-26 15:59:01 发布

cqhiabc50405

最新推荐文章于 2019-07-26 15:59:01 发布

阅读量145

点赞数

物理备库的强制激活的步骤如下：

SQL> alter database activate standby database;

Database altered.

SQL> shutdown immediate;
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
SQL> startup
SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ WRITE

以下是failover的日志：

Mon Jun 25 11:06:36 2012
alter database activate standby database
ALTER DATABASE ACTIVATE [PHYSICAL] STANDBY DATABASE (testdb)
Begin: Standby Redo Logfile archival
End: Standby Redo Logfile archival
RESETLOGS after incomplete recovery UNTIL CHANGE 42529492545
Archived Log entry 1764 added for thread 1 sequence 1780 ID 0x4176f7fd dest 1:
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/data/oracle/oradata/testdb/redo1.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /data/oracle/oradata/testdb/redo1.log
Clearing online log 1 of thread 1 sequence number 1779
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/data/oracle/oradata/testdb/redo1.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/data/oracle/oradata/testdb/redo1.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Mon Jun 25 11:06:51 2012
Clearing online redo logfile 1 complete
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/data/oracle/oradata/testdb/redo2.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 2 /data/oracle/oradata/testdb/redo2.log
Clearing online log 2 of thread 1 sequence number 1780
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/data/oracle/oradata/testdb/redo2.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/data/oracle/oradata/testdb/redo2.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 2 complete
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/data/oracle/oradata/testdb/redo3.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 3 /data/oracle/oradata/testdb/redo3.log
Clearing online log 3 of thread 1 sequence number 1778
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/data/oracle/oradata/testdb/redo3.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/data/oracle/oradata/testdb/redo3.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Mon Jun 25 11:07:09 2012
Clearing online redo logfile 3 complete
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/data/oracle/oradata/testdb/redo4.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 4 /data/oracle/oradata/testdb/redo4.log
Clearing online log 4 of thread 1 sequence number 20
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/data/oracle/oradata/testdb/redo4.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /data/oracle/diag/rdbms/std01/testdb/trace/testdb_ora_22538.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/data/oracle/oradata/testdb/redo4.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 4 complete
Resetting resetlogs activation ID 1098315773 (0x4176f7fd)
Online log /data/oracle/oradata/testdb/redo1.log: Thread 1 Group 1 was previously cleared
Online log /data/oracle/oradata/testdb/redo2.log: Thread 1 Group 2 was previously cleared
Online log /data/oracle/oradata/testdb/redo3.log: Thread 1 Group 3 was previously cleared
Online log /data/oracle/oradata/testdb/redo4.log: Thread 1 Group 4 was previously cleared
Standby became primary SCN: 42529492543
Mon Jun 25 11:07:16 2012
Setting recovery target incarnation to 2
ACTIVATE STANDBY: Complete - Database mounted as primary
Completed: alter database activate standby database