Pages

Thursday, March 15, 2012

Gap Resolution of Physical Standby Database to Hang

Fetching gap sequence in thread 1, gap sequence 53713-53713FAL[client]:
Error fetching gap sequenceWed May 12 15:26:44 2010FAL[client]:
Failed to request gap sequenceGAP - thread 1 sequence 53713-53713DBID 2748812654 branch 645984751

select sequence#, name, archived, applied from v$archived_log
where sequence# like '%53713%';


SEQUENCE# NAME ARC APP
---------- ------------------------------------------------------- --- ---
53713 /opt/oracle/admin/PROD/standby/arch_3_53713_645984751 YES NO


* check which sequence is not sync.

* copy them to primary to standby.

* then register the sequence.


ALTER DATABASE REGISTER OR REPLACE PHYSICAL LOGFILE '/opt/oracle/admin/BMCPD/standby/arch_1_53713_645984751';

No comments:

Post a Comment