DBA_LOGSTDBY_HISTORY displays the history of switchovers and failovers in a Data Guard configuration. It does this by showing the complete sequence of redo log streams processed or created on the local system, across all role transitions. (After a role transition, a new log stream is started and the log stream sequence number is incremented by the new primary database.) This view is for logical standby databases only.
Lists the sequence numbers for all log streams created or applied on the local system.
Note: A value of 0 indicates an unknown sequence order; this is reserved for future log streams.
Description of the log stream processing:
Past - The log stream has already been processed
Immediate Past - This is the most recently processed log stream; its status is transitioning from Current to Past
Current - The log stream is currently being processed
Immediate Future - This is the next log stream to be processed; its status is transitioning from Future to Current
Future - The log stream will be processed
Describes how the log stream was started:
RFS - The RFS process created the log stream
User - A user registered the initial log file for the log stream
Synch - A user issued the ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY DDL statement
Redo - The log stream information was recorded in the redo log
Database identifier of the primary database that created the log stream
Lowest system change number (SCN) in the current log file
Highest system change number (SCN) in the current log file
Time of the first SCN entry (FIRST_CHANGE#) in the current log file
Time of the last SCN entry (LAST_CHANGE#) in the current log file
Unique database name (DB_UNIQUE_NAME) of the primary database that produced the log stream. See V$DATAGUARD_CONFIG to display all database DB_UNIQUE_NAME values defined in the Data Guard configuration.
SCN that should be used to flashback a failed primary (that created the log stream) or to flashback a bystander logical standby database following a failover, in the context of the associated redo log stream. It is the SCN up to which redo for the associated log stream can be merged safely in all databases using local copies of archived logs received from the primary database. In order to apply changes beyond this following a failover, you will need to fetch and mine the redo logs from the failover target.
Strict upper bound on the SCN up to which SQL Apply has applied redo records before it switched to a new log stream (either because it was activated and became the primary database, or in the case of a bystander logical standby database where it switched to a new log stream in order to accommodate a new primary database).