Prerequisites for Getting Started

One of the prerequisites for using DGMGRL is that a primary database and any standby databases must already exist.

The DG_BROKER_START initialization parameter must be set to TRUE for all databases in the configuration. Each database must also be configured to use a server parameter file (SPFILE).

Convert the initialization parameter files (PFILE) on both primary and standby databases into server parameter files (SPFILE), if necessary. Use the following SQL*Plus command:

CREATE SPFILE='spfilename' FROM PFILE='pfilename';

If an instance was not started with a server parameter file, then shut down the instance and restart it using the server parameter file.

After starting the Oracle instance, set the DG_BROKER_START=TRUE initialization parameter using the SQL ALTER SYSTEM statement. The parameter value will be saved in the server parameter file. The next time you start the Oracle instance, the broker is started automatically, and you do not need to issue the SQL ALTER SYSTEM statement again.

The following assumptions are made in these scenarios:

  • TCP/IP is used to connect to primary and standby databases.

  • The standby database has been created from backups of the primary database control files and datafiles as described in the Oracle Data Guard Concepts and Administration.

  • The scenarios assume the following broker configuration:

    • The configuration name is DRSolution.

    • The database unique name (DB_UNIQUE_NAME) of the primary database is North_Sales.

    • The database unique name (DB_UNIQUE_NAME) of the remote standby database is South_Sales.

    • The protection mode is maximum performance mode.

    • There are standby redo log files configured for both the primary and standby database. The transport mode for both databases is ASYNC.

    • The standby database is a physical standby database.