Standby Not Applying After Outage

Question

We have a 11r2 primary and standby running on RHEL 5. The primary lost network connectivity for a time and VMWare locked up. The VM admin restarted the primary VM (it was a hard-boot). This all happened while I was gone and when I came into work, the primary database appeared to be working. I decided to dig deeper and check out the standby.
On the standby...
SQL> select * from v$archive_gap;
Thread#: 1
low_sequence: 123120
high_sequence: 123120
DGMGRL> show configuration
Configuration - prodDB
     Protection Mode: MaxPerformance
     Databases:
          prodDB - Primary database
          prodDB2 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
SQL> select count(*) from v$archived_log where applied='NO';
Count(*): 107
SQL> select process, client_process, thread#, sequence#, block#, status from v$managed_standby where process='MRP0' or client_process='LGWR';
Process: MRP0
Client_Process: N/A
Thread#: 1
Sequence#: 123120
Block#: 0
Status: WAIT_FOR_LOG
Process: RFS
Client_Process: LGWR
Thread#: 1
Sequence#: 128315
Block#: 4686
Status: IDLE
DGMGRL> show database prodDB2;
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 2 days 3 minutes 53 seconds
Apply Lag: 2 days 3 minutes 53 seconds
Real Time Query: OFF
Instance(s): prodDB
It appears all is well (just very far behind) but when I run the last code block (show database prodDB2;) again ...
DGMGRL> show database prodDB2;
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 2 days 1 hour(s) 42 minutes 37 seconds
Apply Lag: 2 days 1 hour(s) 42 minutes 37 seconds
Real Time Query: OFF
Instance(s): prodDB
...it looks as if the massive backlog is just increasing. How can I confirm that everything that things are going well? I am still learning Data Guard.
Thank you

Answer 1

Hello;
It shows 9851 logs behind. If you created the standby more than once then the query could be giving incorrect information. If this is the case then check from the standby. For example
PRIMARY SIDE
/home/oracle:PRIMARY >sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 5 16:14:06 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;
MAX(SEQUENCE#)
  766
SQL>
STANDBY SIDE
/home/oracle:STANDBY >sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 5 16:14:40 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;
MAX(SEQUENCE#)
  766
If you do this is the difference  really 9851?
Best Regards
mseberg