ADG 容灾切换--- 2013.10.16 22:30 -- 2013.10.17 06:30

ADG 容灾切换--- 2013.10.16 22:30 -- 2013.10.17 06:30

留个脚印

primary 站点执行了切换命令后，standby 站点切换 primary 不成功的恢复步骤。

[@more@]Roll Back After Unsuccessful Switchover and Start Over
For physical standby databases in situations where an error occurred and it is not
possible to continue with the switchover, it might still be possible to revert the new
physical standby database back to the primary role by using the following steps:
1. Connect to the new standby database (old primary), and issue the following
statement to convert it back to the primary role:
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
If this statement is successful, then shut down (if necessary) and restart the
database. Once restarted, the database will be running in the primary database
role, and you do not need to perform any more steps.
If this statement is unsuccessful, then continue with Step 3.
2. When the switchover to change the role from primary to physical standby was
initiated, a trace file was written in the log directory. This trace file contains the
SQL statements required to re-create the original primary control file. Locate the
trace file and extract the SQL statements into a temporary file. Execute the
temporary file from SQL*Plus. This will revert the new standby database back to
the primary role.
3. Shut down the original physical standby database.
4. Create a new standby control file. This is necessary to resynchronize the primary
database and physical standby database. Copy the physical standby control file to
the original physical standby system. Section 3.2.2 describes how to create a
physical standby control file.
5. Restart the original physical standby instance.
If this procedure is successful and archive gap management is enabled, the FAL
processes will start and re-archive any missing archived redo log files to the
physical standby database. Force a log switch on the primary database and
examine the alert logs on both the primary database and physical standby
database to ensure the archived redo log file sequence numbers are correct.
See Section 6.3.3.1 for information about archive gap management and
Appendix G for information about locating the trace files.
6. Try the switchover again.
At this point, the Data Guard configuration has been rolled back to its initial state,
and you can try the switchover operation again (after correcting any problems that might have led to the initial unsuccessful switchover).

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/66634/viewspace-1060960/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/66634/viewspace-1060960/