Data Guard Create Configuration Tips Oracle Database Tips by Donald BurlesonDecember 9, 2015

Oracle Data GuardChapter 8 - Data Guard Broker

Data Guard Configuration Management

CREATE CONFIGURATION 'appsconfig' AS
PRIMARY DATABASE IS 'appsdb'
CONNECT IDENTIFIER IS 'appsprimary';

The PRIMARY DATABASE identifier should match the initialization parameter db_unique_name, exactly.

After creating a configuration, the next step is to add sites to the configuration. This is achieved by using the CREATE SITE statement for Oracle9i and ADD DATABASE for Oracle10g. Usage of the CREATE SITE statement is similar to the CREATE CONFIGURATION statement, except that the primary site name does not have to be specified. This statement does not require the name of the configuration, which implies that there can only be one configuration per primary site.

The following script shows an example of adding a site in the configuration. These statements should be executed after connecting to the primary database using DGMGRL. Here is the statement as it would appear in Oracle9i syntax.

CREATE SITE 'stdbydb' RESOURCE IS 'stdbydb' HOSTNAME IS 'jrpr02'
INSTANCE NAME IS 'stdbydb' SERVICE NAME IS 'appsstdby'
SITE IS MAINTAINED AS PHYSICAL;

Here is it as it would appear in Oracle10g Syntax:

ADD DATABASE 'stdbydb'
CONNECT IDENTIFIER IS 'appsstdbydb'
MAINTAINED AS PHYSICAL;

The keyword MAINTAINED AS identifies the present type of database and not the type it will assume after switchover. In the above example, the standby site added to the configuration is a physical standby database.

By default, a newly created configuration will be in a disabled state. The configuration will have to be enabled so that the Data Guard broker can manage it. The ENABLE CONFIGURATION statement can be used to enable a configuration and all of its dependents. The syntax is identical for Oracle9i and Oracle10g. Similarly, the DISABLE CONFIGURATION statement can be used to disable a configuration and all the sites and databases included in the configuration.

A configuration can be completely removed using the REMOVE CONFIGURATION statement.

Data Guard broker writes its log file in the location specified by the background_dump_dest initialization parameter. In addition to the DMON process log file, there will be a drc<primary site>.log file, which contains detailed messages regarding the Data Guard broker.