STOP OBSERVING
The STOP OBSERVING command stops all local observers running on this host (where this DGMGRL session is running) for all broker configurations in a specific group.
Format
STOP OBSERVING [<configuration_group_name>] [TRACE_LEVEL= USER | SUPPORT];
Command Parameters
Usage Notes
-
If no
configuration_group_nameis specified, then this command stops allLOCALobservers running on this host (where this DGMGRL session is running) for all broker configurations defined in the observer configuration file. -
The
configuration_group_namecannot be the keywordALL. -
Information about the DGMGRL commands run and execution details are written to the log file,
superobserver.log. This file is located in the$DG_ADMIN/admin/directory. If theDG_ADMINenvironment variable is not defined, this file is located in the current working directory. - The optional clause
TRACE_LEVELIS lets you control the amount of tracing done and written to the observer log file. The default value isUSER, which limits the observer log contents to tracing information about fast-start failover, status changes of the primary and target standby database, and error/warning messages. SettingTRACE_LEVELtoSUPPORTincreases the amount of tracing information to include lower-level information needed by Oracle Support Services.
Command Example
DGMGRL> STOP OBSERVING;
ObserverConfigFile=/net/oracle/dataguard/observer.ora
observer configuration file parsing succeeded
Submitted command "STOP OBSERVER HOST IS OBM1" using connect identifier cfg1_cid.
Submitted command "STOP OBSERVER HOST IS OBM1" using connect identifier cfg2_cid.
Submitted command "STOP OBSERVER HOST IS OBM1" using connect identifier cfg3_cid.
Check superobserver.log and individual observer logs for execution details.
DGMGRL> STOP OBSERVING GRP_A;
ObserverConfigFile=/net/oracle/dataguard/observer.ora
observer configuration file parsing succeeded
Submitted command "STOP OBSERVER HOST IS OBM1" using connect identifier cfg1_cid.
Submitted command "STOP OBSERVER HOST IS OBM1" using connect identifier cfg2_cid.
Check superobserver.log and individual observer logs for execution details.