Oracle checks the master database, physical and snapshot slave databases through views and alarm logs

Oracle checks the master database, physical and snapshot slave databases through views and alarm logs

Oracle checks the master database, physical and snapshot slave databases through views and alarm logs

Master database action	Master database information	Slave database information
Enable redo thread	Alert log V $ thread	Alert log
Displays the database role, protection mode, protection level, switch status, quick start, and invalid conversion information.	V $ database	V $ database
Add/delete redo log file groups	Alert log V $ log V $ logfile status field	Alert log
Control File Creation	Alert log	Alert log
Changes in tablespace status	V $ recover_file Dba_tablespace Alert log	V $ recover_file Dba_tablespace
Add/delete data files or tablespaces	Dba_data_files Alert log	V $ datafile Alert log
Rename a data file	V $ datafile Alert log	V $ datafile Alert log
Unrecorded logs or unrecovered operations	V $ datafile V $ database	Alert log
Monitor redo Transmission	V $ archive_dest_status V $ archived_log V $ archived_dest Alert log	V $ archived_log Alert log
Publish open resetlogs or clear unarchived logfiles statements	Alert log	Alert log
Modify initialization parameters	Alert log	Alert log

Use the following statements to obtain the current role, protection mode, protection level, switch status, quick start, and invalid conversion information of the master database and slave database.
Select protection_mode,

Protection_level,

Database_role role,

Switchover_status

From v $ database;

Returns the Failover Status of the fast-start instance.
Select fs_failover_status "fsfo status ",

Fs_failover_current_target target,

Fs_failover_threshold threshold,

Fs_failover_observer_present "observer present"

From v $ database;

Obtain the redo application and transmission status on the physical standby database.
Select process, status, thread #, sequence #, block #, blocks

From v $ managed_standby;

Query archived Log File Information and historical archive information
Select thread #, sequence #, first_change #, next_change #

From v $ archived_log;

Select thread #, sequence #, first_change #, next_change # from v $ log_history;

View the DG event information written into the alert log
Select message from v $ dataguard_status

View the status of the redo log transmitted from the master database to the target database. SCN indicates the system change number of the last redo log applied to the standby database.
Select dest_id, applied_scn from v $ archive_dest where target = 'standby ';