Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on December 22, 2025. To monitor Oracle databases, we recommend that you use PATROL for Oracle Enterprise Database.

Configuring the standby instance of the dataguard setup

The following information describes the procedure to configure a standby dataguard instance for monitoring at the standby host. This standby dataguard instance ensures that the standby host is ready to take over monitoring parameters if the production Oracle database is unavailable.

 

Related topics

Monitoring-the-dataguard-environment

Configuring-a-Failover-DataGuard-monitoring

Dataguard-failover-configuration-requirements

Modifying an existing standby instance

Before you begin

  • The PATROL account must have read access to the tnsnames.ora file.
  • Confirm that ORACLE_STANDBY_DG.kml is loaded on your system.
Click here to view information for loading a knowledge module

 From the PATROL Central Console:

  1. In the Common Tasks tab of the PATROL Central Operator Taskpad, click the Load Knowledge Modules icon.
  2. To start the wizard, click Next.
  3. Select the check boxes for the managed systems that you want to load Knowledge Modules on. Click Next.
  4. Select the check box for each Knowledge Module or KML that you want to load. Click Next.

      • Individual Knowledge Modules are on the Individual Knowledge Modules tab.
      • KMLs are on the Knowledge Module Lists tab.
  5. Click Finish.

Preparing a standby dataguard instance for monitoring in the PATROL Central console

To configure the standby dataguard instance

Click to view a short video on how to configure an Oracle standby dataguard instance for monitoring in a PATROL environment.

icon-play.pnghttps://youtu.be/2FkoL3a8iHM

Note

Verify that the PATROL console user has the privilege to execute SQL*Plus commands.

  1. From theORACLE_STANDBY_DG application class, right-click and select Knowledge Module Commands>Standby Configuration>StandBy DG Instance Configure.

  2. In the DataGuard Instance Configuration dialog box, enter the standby instance details.

    Field

    Description

    Instance Name

    The name of the standby dataguard instance

    Note

    The name is case sensitive must be the same as Oracle instance name.

    Oracle Home

    The home directory of the standby dataguard  instance

    User Name and Password

    The username and password for the standby dataguard  instance

    Note

    To configure a standby dataguard instance for monitoring, you must be a user with SYSDBA system privileges.

    If the database user password contains special characters, specify the password within the double quotes. Example: “%BMC$"

  3. Click Apply to accept the information and configuration the standby instance.
  4. Click Exit to close the dialog box.

To copy the standby information to the current primary agent in case of failover

To be ready for failover, or switchover, from the primary instance, you must copy the configuration details from the standby instance to the primary instance of the agents that are part of the dataguard setup.

  1. In the standby instance ORACLE_STANDBY_DG application class, right-click and select the Knowledge Module Commands>Instance Config Copy.

  2. From the Instance Config Copy dialog box, enter the Agent and Oracle system ID (SID) details of the instance.

    Field

    Description

    Patrol Agent Host

    The target PATROL Agent host name

    Patrol Agent Port

    The target PATROL Agent port

    The default PATROL Agent port is 3181. You can change the default port number but ensure that the new port number is available.

    Local SID Name

    The local SID instance name already appears in the field. This name cannot be changed.

    Remote SID Name

    The remote SID instance name

    Save to file

    Saves this standby configuration information to a file

    Send to remote

    Sends this standby configuration information to a remote host

    File Location

    Path for the configuration file's location

  3. Click OK to save this configuration information.

Viewing the ORACLE_STANDBY_DG instance in the PATROL Central interface

After configuring the ORACLE_STANDBY_DG instance, the standby dataguard implementation hierarchy in the PATROL Central interface is as follows:

Patrol_Central_Standby_DataGuard.png

  1. ORACLE_STANDBY_DG application class represents the standby dataguard instance-monitoring feature.
  2. Oracle Standby Data Guard Instance represents the individual standby dataguard instances configured through KM commands.
  3. DGCollectors application class with parameters that collect the data for the standby instance.
    This application class parameters includes:
  4. DGPARAMS application class with data and time lag parameters for the standby dataguard instance.
    This application class parameters includes:
  5. StandbyAlertLog retrieves the data from the Standby Alert log file.
  6. StandbyStatus queries to the standby instance to get its status.
  1. StandByConfigurationStatus checks the status of the configured standby database running on a dataguard environment.

 You can also use the PCM rule sets to configure the Standby instance, by using the DGStandByConfig.cfg template.

Preparing a standby dataguard instance for monitoring in the TrueSight console

You can configure a standby dataguard instance for monitoring in the TrueSight console and then apply the instance to a PATROL Agent. 

To configure the standby dataguard instance

  1. Define a monitoring policy in the TrueSight Console, select the following parameters, and click Add:

    • Monitoring Solution: Oracle Database
    • Version: 9.7.10
    • Monitor Profile: Oracle Standby Data Guard
    • Monitor Type: Oracle Standby Data Guard

  2. For the standby dataguard instance, enter the monitoring configuration details and click OK:

    Field

    Description

    Standby Data Guard instance name

    The standby dataguard instance name

    Note

    The name is case sensitive must be the same as Oracle instance name.

    Standby Data Guard instance home 

    The home directory of the standby dataguard instance

    User Name and Password

    The username and password for the standby dataguard instance

    Note

    To configure a standby dataguard instance for monitoring, you must be a user with SYSDBA system privileges.

    StandBy Data Guard debug

    (Optional) Enable the debugging process of the standby dataguard instance configuration

    Exclude error log strings

    (Optional) Any error log strings that will not be monitored by the KM

    Include error log strings

    (Optional) Any error log strings that will be monitored by the KM

  3. Click OK to save this configuration information.

After creating the standby dataguard instance, the implementation hierarchy for the application class is similar to the PATROL Central view.

 

Preparing standby dataguard instances for monitoring with batch configuration

You can prepare a batch configuration to set up many standby dataguard instances through the TrueSight console, or by using text configuration file outside Oracle KM.

Batch configuration can be completed through the TrueSight console, or manually with a batch configuration file that you can work with in a text editor. After the batch configuration has been saved, the KM agent discovery scans for the existence of the configuration file. After it finds the file, it automatically starts the configuration process, using the information in the configuration file.

The batch configuration file contains the settings for all the instances that you want to configure. When the discovery process runs, all the instances defined in the configuration file are simultaneously configured, which saves time versus configuring all of the instances individually.

To use the TrueSight console for standby dataguard batch configuration

You can configure a batch standby dataguard instance for monitoring in the TrueSight console and then apply the instance to a PATROL Agent.

  1. Create a monitoring policy in the TrueSight Console, select the following parameters, and click Add:

    • Monitoring Solution: Oracle Database
    • Version: 9.7.10
    • Monitor Profile: Oracle Standby Data Guard
    • Monitor Type: Oracle Standby Data Guard Global Configuration

  2. For the standby dataguard instance batch configuration, enter the monitoring details and click OK:

    Field

    Description

    Standby Data Guard config unique group name

    The unique group name for the batch standby dataguard instance.

    Standby Data Guard instance name

    The standby dataguard instance name

    Standby Data Guard instance home

    The home directory of the standby dataguard instance

    User Name and Password

    The username and password for the standby dataguard instance

    Note

    To configure a standby dataguard instance for monitoring, you must be a user with SYSDBA system privileges.

  3. For the shared batch configuration's shared properties, you can enter the following optional details:

    Field

    Description

    Exclude error log strings

    Any error log strings that will not be monitored by the KM

    Include error log strings

    Any error log strings that will be monitored by the KM

    StandBy Data Guard debug

    Enable the debugging process of the standby dataguard instances' configuration

  4. Click OK to save this configuration information.

To manually configure a batch file for the standby dataguard instances

To configure a batch configuration file, you can use the SB_batch_conf_sample.wri file as a template.From a command prompt:

  1. Open the SB_batch_conf_sample.wri file in the following location, depending on your operating system.
    • For UNIX systems, the file is located at $PATROL_HOME/../oracle/conf.
    • For Windows systems, the file is located at %PATROL_HOME%\oracle\conf.
  2. Edit the Oracle System ID (SID) and the keyword values to reflect the instances you want to configure.
  3. Save the file as SB_batch_conf<port_number>.txt, in a text only format.

When the discovery finds this file, it starts processing the file to configure the instances on that PATROL agent port.

When the discovery completes processing this file, the file name is changed to SB_batch_conf<port_number>.done .

You can check the following log files for the successful completion of the batch configuration, or any errors. These files are saved in the same directory location as the SB_batch_conf_sample.wri file.

  • SBBatchConfig<port_number>.log
  • StandByConfig<port_number>.log

Note

You can add many instances. Each instance has its own configuration data.

Preparing a standby dataguard instance for monitoring with Patrol Configuration Management

You have an option to configure a standby dataguard instance by using Patrol Configuration Management (PCM).

After you have configured the instance for monitoring, the PCM creates a DGStandByConfig.cfg file in the %PATROL_HOME%\oracle\rulesets directory.

When you apply the rule set to the configured PATROL Agent, it automatically configures all the instances for which the rule sets have been created.

For the configuration details, you can see the StandByConfig{Agentport-no}.log file in the %PATROL_HOME%\oracle\conf directory.

Note

 You can add many instances. Each instance has its own configuration data.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*