f 10g data guard 如何解決archive log gap太大,已被清掉的問題 ~ 迪貝之家

Pages

10g data guard 如何解決archive log gap太大,已被清掉的問題

我的環境還蠻常發生的
好加在,要升到18c了
1. On the standby database, stop the managed recovery process (MRP):
可能得先停掉DMON -- ALTER SYSTEM SET dg_broker_start=false scope=both;-- 如果有的話
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

2. On the standby database, find the SCN which will be used for the incremental
backup at the primary database:
SQL> SELECT to_char(CURRENT_SCN) FROM V$DATABASE;

3. incremental backup
BACKUP INCREMENTAL FROM SCN 9396571788224 AS COMPRESSED BACKUPSET DATABASE FORMAT '/oradata2/syncdr/DBtandby_2019_0812%U' tag 'DBSTANDBY_2019_0812';

4.Connect to the standby database as the RMAN target, and catalog all incremental backup pieces:
CATALOG START WITH '/oradata2/syncdr/DBStandby_2019_0812'; -- 傳檔

5.
Recover the standby database with the cataloged incremental backup
RMAN> RECOVER DATABASE NOREDO;

6. In RMAN, connect to the primary database and create a standby control file backup:
BACKUP CURRENT CONTROLFILE FOR STANDBY FORMAT '/oradata2/syncdr/DBStandbyCTRL_0812.bck'; -- 傳檔

7.Shut down the standby database and startup nomount:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;

8.
In RMAN, connect to standby database and restore the standby control file:
RMAN> RESTORE STANDBY CONTROLFILE FROM '/oradata2/syncdr/DBStandbyCTRL_0812.bck';


11. Shut down the standby database and startup mount:
SQL> SHUTDOWN;
SQL>startup nomount;
SQL>alter database mount standby database;
SQL>alter database recover managed standby database disconnect from session;

I think you should still catch or register log after recovering the standby control file.