|
Index >
ORACLE Server Parameters >
dg_broker_config_file2
dg_broker_config_file2
Oracle 11.1.0:
| Parameter Name: | dg_broker_config_file2
| | Description: | data guard broker configuration file #2
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | IMMEDIATE
|
Oracle 10.2.0:
| Parameter Name: | dg_broker_config_file2
| | Description: | data guard broker configuration file #2
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | IMMEDIATE
|
Oracle 10.1.0:
| Parameter Name: | dg_broker_config_file2
| | Description: | data guard broker configuration file #2
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | IMMEDIATE
|
Oracle 9.2.0:
| Parameter Name: | dg_broker_config_file2
| | Description: | data guard broker configuration file #2
| | Type: | CHAR
| 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-16637: an instance failed to access the Data Guard broker configurationCause: 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_config_file2 ]
on the Oracle FAQ.
| 
