oracle9204(9i)_dg(data guard)_重新命名主庫資料檔案_指南_轉摘官檔
When you rename one or more datafiles in the primary database, the change is not propagated to the standby database. Therefore, if you want to rename the same datafiles on the standby database, you must manually make the equivalent modifications on the standby database because the modifications are not performed automatically, even if the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
The following steps describe how to rename a datafile in the primary database and manually propagate the changes to the standby database. If you do not want the standby database to have the same physical structure as the primary database, then these steps are not required.
- To rename the datafile in the primary database, take the tablespace offline:
SQL> ALTER TABLESPACE tbs_4 OFFLINE;
- Exit from the SQL prompt and issue an operating system command, such as the following UNIX mv command, to rename the datafile on the primary system:
% mv tbs_4.dbf tbs_x.dbf
- Rename the datafile in the primary database and bring the tablespace back online:
SQL> ALTER TABLESPACE tbs_4 RENAME DATAFILE 'tbs_4.dbf'
2> TO 'tbs_x.dbf';
SQL> ALTER TABLESPACE tbs_4 ONLINE; - Connect to the standby database and make sure that all the logs are applied; then stop managed recovery operations:
SQL> SELECT NAME, SEQUENCE#, ARCHIVED, APPLIED
2> FROM V$ARCHIVED_LOG;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; - Shut down the standby database:
SQL> SHUTDOWN;
- Rename the datafile at the standby site using an operating system command, such as the UNIX mv command:
% mv tbs_4.dbf tbs_x.dbf
- Start and mount the standby database with the new control file:
SQL> STARTUP NOMOUNT;
SQL> ALTER DATABASE MOUNT STANDBY DATABASE; - Rename the datafile in the standby controlfile. Note that the STANDBY_FILE_MANAGEMENT initialization parameter must be set to MANUAL.
SQL> ALTER DATABASE RENAME FILE 'tbs_4.dbf'
2> TO 'tbs_x.dbf'; - On the standby database, restart managed recovery operations:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;
If you do not rename the corresponding datafile at the standby site, and then try to refresh the standby database control file, the standby database will attempt to use the renamed datafile, but it will not find it. Consequently, you will see error messages similar to the following in the alert log:
ORA-00283: recovery session canceled due to errors
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '/disk1/oracle/dbs/tbs_x.dbf'
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/9240380/viewspace-628161/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle10g data guard(dg)__主庫重新命名資料檔案_在備庫上同步重新命名資料檔案Oracle
- 【轉載】Oracle Data Guard 主庫 歸檔檔案 刪除策略Oracle
- DATA GUARD主庫丟失資料檔案的恢復(2)
- DATA GUARD主庫丟失資料檔案的恢復(3)
- DATA GUARD主庫丟失資料檔案的恢復(1)
- Oracle Data Guard 主庫歸檔檔案刪除策略Oracle
- Oracle Data Guard 主庫 歸檔檔案 刪除策略Oracle
- oracle9204(9i)_dg(data guard)__Tuning Logical Standby DatabasesOracleDatabase
- Oracle Data Guard 主庫 歸檔檔案 刪除策略--續Oracle
- oracle10 data guard(dg)__主庫添刪表空間及資料檔案相關測試Oracle
- oracle9204(9i)_dg(data guard)_archive gap_query_apply_transmitOracleHiveAPPMIT
- DATA GUARD手工管理資料檔案
- DG備援資料檔案重新命名
- 【DG】Data Guard主備庫Switchover切換
- 【DG】Data Guard主備庫Failove切換AI
- Data Guard 主端OFFLINE資料檔案和表空間
- oracle10g data guard(dg)_主庫控制檔案受損或loss_自動關庫測試Oracle
- 【轉載】Oracle Data Guard 備庫 歸檔檔案 刪除指令碼Oracle指令碼
- 9i 克隆+data guard 實現資料庫搬遷資料庫
- Oracle 9i Data Guard進行資料庫的災難防護(轉)Oracle資料庫
- 重新命名資料檔案
- oracle dg庫資料檔案空間不足Oracle
- DG 主庫丟失歸檔
- DG備庫手動管理 新增資料檔案
- ORACLE 重新命名資料檔案Oracle
- Oracle 9i Data Guard進行資料庫的災難防護簡介(轉)Oracle資料庫
- 邏輯Data Guard主備庫的轉換
- dg主庫建立檔案備庫未同步解決方法
- data_guard 雙standby pfile 檔案配置
- data gurad物理備份方式下重新命名資料檔案
- Oracle DG備庫手動管理新增資料檔案Oracle
- 【故障處理】DG環境主庫丟失歸檔情況下資料檔案的恢復
- Data Guard之Snapshot Standby資料庫功能[轉]資料庫
- oracle9204(physical dg)配置_指南Oracle
- Data Guard主備庫切換
- 玩轉Data Guard的switchover後切不回主庫
- 【DG】Data Guard搭建(physical standby)
- data guard中增加與刪除主備資料庫中的聯機重做日誌與備重做日誌檔案資料庫