2.7 Verify the Physical Standby Database Is Performing Properly
Step 1 Identify the existing archived redo log files.
SYS@PRODSTD>SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME,applied from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME APP ---------- --------- --------- --- 11 25-MAR-14 25-MAR-14 YES 12 25-MAR-14 25-MAR-14 YES
Step 2 Force a log switch to archive the current online redo log file.
SYS@PROD>ALTER SYSTEM SWITCH LOGFILE;
tail -f alert_PROD.log Tue Mar 25 11:32:49 2014 Thread 1 advanced to log sequence 14 Current log# 1 seq# 14 mem# 0: /u01/app/oracle/oradata/PROD/Disk1/redo01.log Current log# 1 seq# 14 mem# 1: /u01/app/oracle/oradata/PROD/Disk2/redo01_1.log Tue Mar 25 11:32:50 2014 LNS: Standby redo logfile selected for thread 1 sequence 14 for destination LOG_ARCHIVE_DEST_2
tail -f alert_PRODSTD.log Tue Mar 25 11:32:50 2014 Primary database is in MAXIMUM PERFORMANCE mode RFS[3]: Successfully opened standby log 7: '/u01/app/oracle/oradata/PRODSTD/Disk1/standby07.log' Tue Mar 25 11:32:51 2014 Media Recovery Log /u01/app/oracle/oradata/PRODSTD/Disk2/arch/1_13_842523531.arc Media Recovery Waiting for thread 1 sequence 14 (in transit)
Step 3 Verify the new redo data was archived on the standby database. Step 4 Verify new archived redo log files were applied.
SYS@PRODSTD>SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME,applied from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME APP ---------- --------- --------- --- 11 25-MAR-14 25-MAR-14 YES 12 25-MAR-14 25-MAR-14 YES 13 25-MAR-14 25-MAR-14 YES