How to resolved gap on standby

How to resolved gap on standby

Simple Step--

Firstly in primary db we check archive status -

1.select max(SEQUENCE#) from V$ARCHIVED_LOG;

MAX(SEQUENCE#)

--------------

         30849                

2. Now we check in standby archive detail           

SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied",

(ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN

(SELECT THREAD#,MAX(FIRST_TIME) FROM v$ARCHIVED_LOG GROUP BY THREAD#)) ARCH, (SELECT THREAD# ,SEQUENCE# FROM v$LOG_HISTORY WHERE (THREAD#,FIRST_TIME )

IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;

           

    Thread Last Sequence Received Last Sequence Applied Difference

---------- ---------------------- --------------------- ----------

         1                  30850                 30766         84

(As per above we can see gap on standby database )

                         

3. we will immediately check alert log file on standby database. Here we will get some clue.

FAL[client]: Failed to request gap sequence

 GAP - thread 1 sequence 31301-31301

 DBID 2359012130 branch 846904520

FAL[client]: All defined FAL servers have been attempted.

In above noticeable point is that we can see gap in archive file. so we will go to the next step.

4. we will copy missing archive file from primary to standby database

scp * (ip):loction on standby where we want to keep this file

enter

password.xyz

5. Now we register this file in db level.

ALTER DATABASE REGISTER LOGFILE '/archive/MARIGOLD/MARIGOLD_1_29726_846904520.arch';

6.Then we start mrp process

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

7. Now automatically archive apply on standby database .We can verify in alert log file.

RFS[10]: Archived Log: '/archive/MARIGOLD/MARIGOLD_1_32222_846904520.arch'

Primary database is in MAXIMUM PERFORMANCE mode

Fri Feb 13 03:19:13 2015

Media Recovery Log /archive/MARIGOLD/MARIGOLD_1_32222_846904520.arch

Fri Feb 13 03:19:39 2015

Media Recovery Waiting for thread 1 sequence 32223 (in transit)