Standby not in sync with primary

Question

Hi,
I am having oracle 9.2.0.7 on AIX and having physical standby database running on another server. Since the last 2 days it is not in sync and the required archivelog files are removed from production.
Could you please help me out to resolve the issue?
Thanx

Answer 1

Hi
Step 1 On the standby database, find the SCN which will be used for the incremental
backup at the primary database:
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
Step 2 In RMAN, connect to the primary database and create an incremental backup
from the SCN derived in the previous step:
Step 3 RMAN> BACKUP INCREMENTAL FROM SCN <SCN from previous step>
DATABASE FORMAT '/tmp/ForStandby_%U' tag 'FORSTANDBY';
step 4 Transfer all backup sets created on the primary system to the standby system
SCP /tmp/ForStandby_* standby:/tmp
Step 5 Connect to the standby database as the RMAN target, and catalog all incremental
backup pieces:
RMAN> CATALOG START WITH '/tmp/ForStandby';
Step 6 Recover the standby database with the cataloged incremental backup:
RMAN> RECOVER DATABASE NOREDO;
Step 7 In RMAN, connect to the primary database and create a standby control file
backup:
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY FORMAT '/tmp/ForStandbyCTRL.bck';
Step 8 Copy the standby control file backup to the standby system. For example:
SCP /tmp/ForStandbyCTRL.bck standby:/tmp
Step 9 Shut down the standby database and startup nomount:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;
Step 10 In RMAN, connect to standby database and restore the standby control file:
RMAN> RESTORE STANDBY CONTROLFILE FROM '/tmp/ForStandbyCTRL.bck';
Step 11 Shut down the standby database and startup mount:
RMAN> SHUTDOWN;
RMAN> STARTUP MOUNT;
Step 12 If the primary and standby database data file directories are identical, skip to step13. If the primary and standby database data file directories are different, then in
RMAN, connect to the standby database, catalog the standby data files, and switch
the standby database to use the just-cataloged data files. For example:
RMAN> CATALOG START WITH '+DATA_1/CHICAGO/DATAFILE/';
RMAN> SWITCH DATABASE TO COPY;
Step 13 If the primary and standby database redo log directories are identical, skip to step 14. Otherwise, on the standby database, use an OS utility or the asmcmd utility (if
it is an ASM-managed database) to remove all online and standby redo logs from
the standby directories and ensure that the LOG_FILE_NAME_CONVERT parameter
is properly defined to translate log directory paths. For example, LOG_FILE_
NAME_CONVERT=’/BOSTON/’,’/CHICAGO/’.
Step 14 On the standby database, clear all standby redo log groups (there may be more
than 3):
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
Step 15 On the standby database, restart Flashback Database:
SQL> ALTER DATABASE FLASHBACK OFF;
SQL> ALTER DATABASE FLASHBACK ON;
Step 16 On the standby database, restart MRP:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
With this you can recvoer your Standby . I wish it will works for You.
Thanks
Karan