Next log sequence to archive is different

Question

Hi,
I have doubt on standby (DR) concept.
I can see that in my standby database next log sequence to archive shows 0.
Is this ok or something is wrong?
PRODUCTION
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 2631
Current log sequence 2631
STANDBY
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 0
Current log sequence 2631

Answer 1

Hello;
Short answer no nothing is wrong.
Its the same on mine :
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     5069
Next log sequence to archive   0
Current log sequence           5071
SQL> I use v$archived_log to check mine standby :
SELECT  name as STANDBY, SEQUENCE#, applied, completion_time from v$archived_log WHERE  DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;Against my Primary I get the last log :
select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;Data Guard has a set of v$ views to check results, 8archive log list8 isn't so good since with Data Guard you have two copies of the same database in different roles.
Another query I like is : (Run on the standby)
select process, status, sequence#, block# from v$managed_standby;The Oracle doc E10700-02 has several example in chapter 9 "Monitoring Primary, Physical Standby, and Snapshot Standby Databases"
Also section "3.2.7 Verify the Physical Standby Database Is Performing Properly"
Best Regards
mseberg