START OBSERVING

The START OBSERVING command starts a new observer for each broker configuration in the specified group.

The effect of the START OBSERVING command is equivalent to submitting a START OBSERVER command on each individual configuration.

Note:

Before using START OBSERVING, configure observer authentication as described in START OBSERVER IN BACKGROUND. The same authentication requirements apply when using Secure External Password Store (SEPS), TLS external authentication, or Kerberos external authentication.

Format

START OBSERVING [configuration_group_name];

Command Parameters

configuration_group_name: The name of a broker configuration group, in which you want to start one observer for each broker configuration.

Usage Notes

If no configuration_group_name is specified, then this command will start a new observer for each configuration defined in the observer configuration file.
The configuration_group_name cannot be the keyword ALL.
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 the DG_ADMIN environment variable is not defined, this file is located in the current working directory.

Command Example

DGMGRL> START OBSERVING;
ObserverConfigFile=/net/oracle/dataguard/observer.ora
observer configuration file parsing succeeded
Submitted command “START OBSERVER” using connect identifier "cfg1_cid".  
Submitted command “START OBSERVER”  using connect identifier "cfg2_cid".  
Submitted command “START OBSERVER” using connect identifier "cfg3_cid".  

Check superobserver.log and individual observer logs for execution details.

DGMGRL> START OBSERVING GRP_A;
ObserverConfigFile=/net/oracle/dataguard/observer.ora
observer configuration file parsing succeeded
Submitted command “START OBSERVER” using connect identifier "cfg1_cid".  
Submitted command “START OBSERVER”  using connect identifier "cfg2_cid".  

Check superobserver.log and individual observer logs for execution details.