Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US

Index > ORACLE Server Parameters > dg_broker_start

dg_broker_start

Oracle 11.1.0:

Parameter Name:dg_broker_start
Description:start Data Guard broker framework (DMON process)
Type:BOOL Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.2.0:

Parameter Name:dg_broker_start
Description:start Data Guard broker framework (DMON process)
Type:BOOL Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.1.0:

Parameter Name:dg_broker_start
Description:start Data Guard broker framework (DMON process)
Type:BOOL Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 9.2.0:

Parameter Name:dg_broker_start
Description:start Data Guard broker framework (DMON process)
Type:BOOL Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 8.1.7:

No such parmeter in Oracle 8.1.7.

Oracle 8.0.6:

No such parmeter in Oracle 8.0.6.

Oracle 7.3.4:

No such parmeter in Oracle 7.3.4.

Related Error Messages:

ORA-16525: the Data Guard broker is not yet available
    Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start.

    Action: If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.

ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier

    Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID='*' qualifier was required in the command.

    Action: Reenter the command using the SID='*' qualifier.

ORA-16637: an instance failed to access the Data Guard broker configuration

    Cause: When an instance was started, the DMON process on the instance failed to access the Data Guard broker configuration. This can happen if the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters are not set up correctly to point to the broker configuration files shared among all instances.

    Action: Set DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the correct file specifications that point to the broker configuration files shared among all instances. Bounce the DMON process by setting DG_BROKER_START initialization parameter to FALSE and then to TRUE.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ dg_broker_start ] on the Oracle FAQ.

HOME | ASK QUESTION | ADD FAQ | SEARCH | E-MAIL US