【翻译自mos文章】重新创建物理standby database 的 控制文件的方法

重新创建物理standby database 的 控制文件的方法

参考自：
Steps to recreate a Physical Standby Controlfile (文档 ID 459411.1)

适用于：
Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.3 [Release 8.1.7 to 11.2]
Information in this document applies to any platform.
 ***Checked for relevance on 29-Aug-2014***

解决方法：
请遵守下列方法来重新创建物理standby controlfile 

1. Stop Managed Recovery Process on the Standby Database (if still running):
   

SQL> alter database recover managed standby database cancel;


2. Shutdown the Standby Database:
   

SQL> shutdown immediate;


3. Connect to the Primary Database as SYS:
   

SQL> connect sys/<Password>@<Primary> as sysdba


4. Create a new Physical Standby Controlfile from the Primary:
   

SQL> alter database create standby controlfile as '<File-Specification>';


5. Copy the new created Standby Controlfile to the Standby Database using OS-Tools (eg. cp or ftp) and replace the current Standby Controlfile with the new created one.

6. Mount the Standby Database with the new Standby Controlfile:

    Oracle 8i and 9i (8.x - 9.x):
   

SQL> startup nomount
SQL> alter database mount standby database;


    Oracle 10g and 11g (10.x - 11.x):
 

SQL> startup mount


7. If the File-Structure is different between Primary and Standby Database,  you could either rename the File-Location(s) in the new Standby Controlfile:
   

SQL> alter database rename file '<old Filespecification or file#>' to '<new Filespecification>';

or set db_file_name_convert or/and log_file_name_convert init parameters in the standby database.

8. Starting with 9i: If you don't have Standby RedoLogs proactively on the Primary and want them on the Standby Database or you had Standby RedoLogs with this Standby Database before, now add the Standby RedoLogs (again):
   

SQL> alter database add standby logfile group <Group No.> ('Filespecification(s)') size <size> reuse;


Please see
Document 219344.1:Usage, Benefits and Limitations of Standby Redo Logs (SRL)
for further Details about Standby RedoLogs

9. Re-enable Flashback (if Flashback was enabled previously):



SQL> alter database flashback off;
SQL> alter database flashback on;


10. Start Managed Recovery again:
   

SQL> alter database recover managed standby database disconnect [using current logfile];