The Oracle Dataguard Environment's Standby and Primary Databases may be verified by using the following command.
On Primary Server:
alter system archive log current;
select thread#,max(sequence#)"Last Primary Seq Generated"from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;
On Physical Standby Server:
--Check received log on standby
select thread#,max(sequence#)"Last Standby Seq Received"from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;
--Check applied log on standby
select thread#,max(sequence#)"Last Standby Seq Applied"from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and val.applied in('YES','IN-MEMORY') group by thread# order by 1;
The Oracle Dataguard Environment's Standby and Primary Databases may be verified by using the following command.
On Primary Server:
alter system archive log current; select thread#, max(sequence#) "Last Primary Seq Generated" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;
On Physical Standby Server:
--Check received log on standby
select thread#, max(sequence#) "Last Standby Seq Received" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;
--Check applied log on standby
select thread#, max(sequence#) "Last Standby Seq Applied" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and val.applied in ('YES','IN-MEMORY') group by thread# order by 1;