DG Databroker Configuration Problems
841531Aug 8 2012 — edited Aug 9 2012I was wondering if someone might be able to provide me some ideas on
what I could check or change to get a Dg databroker
configuration working. I’m sorry about the length of this post. I have
run out of ideas on what to check or review
to resolve this problem. I have contacted Oracle but
not gotten any response to this point.
We have setup a data guard configuration of a primary db and physical standby
database running on 11.2.0.3 which is working correctly.
The setup for the dg databroker checked and
1. Both primary and secondary databases are running using spfiles.
2. The value of the dg_broker_start init parameter in both db’s is set
to true.
3. The primary and secondary db’s have the dg_broker_config_file1 and
dg_broker_config_file2 defined.
4. In the listener.ora file on both the primary and secondary a service is setup
that has as a name the <db_unique_name>DGMGRL.world for GlobalDBNAME.
5. A check of the listener status command show that the service on both environments
is active and pointing to the correct database.
The DGMGRL command line is started
a. A create configuration <db_unique_name> is create using the connect identifier for the primary db.
b. A add database command is entered using the connect identifier for the secondary db.
At this point the first odd situation can be observed. If a show database verbose command
is run using either the primary db or the secondary db – the result shows that
property StaticConnectIdentifier has an incorrect value in the PORT definition.
The value is shown in both cases as 1521 however, the actual
listeners on both systems is set to port to 1526. I’m surprised
that the correct value shown in the port setting isn't correct. To correct that
setting a edit is done on the StaticConnectIdentifier
c. An edit database db_name set property StaticConnectIdentifier is running and
the correct value for port is set. A check of the show database verbose on both
databases reflect the correct port value.
d. An enable configuration command is issued. That returns a enabled result
and doesn’t indicate any errors.
e. However, when a show configuration command is run the result is:
DGMGRL> show configuration
Configuration - tool2_config
Protection Mode: MaxPerformance
Databases:
tool2 - Primary database
tool2c - Physical standby database
Error: ORA-16664: unable to receive the result from a database
While running the enable command and tailing out the dg broker
log file on both the primary and secondary db the following is observed.
Primary dg broker log – A “Site tool2c returned ORA-16665”. is generated from the secondary db
is created a number of times. After the enable command is
finished the following repeated:
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration tool2_config Warning ORA-16607
Primary Database tool2 Success ORA-00000
Physical Standby Database tool2c Error ORA-16664
Secondary dg broker log – A “Failed to send message to site tool2. Error code is ORA-12514” is
generated several times. After the enable command completes the following is repeated:
Warning: Property 'ArchiveLagTarget' has inconsistent values:METADATA='0', SPFILE='', DATABASE='0'
Warning: Property 'LogArchiveMaxProcesses' has inconsistent values:METADATA='4', SPFILE='', DATABASE='4'
Warning: Property 'LogArchiveMinSucceedDest' has inconsistent values:METADATA='1', SPFILE='', DATABASE='1'
SPFILE is missing value for property 'LogArchiveTrace' with sid='tool2c'
Warning: Property 'LogArchiveTrace' has inconsistent values:METADATA='0', SPFILE='(missing)', DATABASE='0'
SPFILE is missing value for property 'LogArchiveFormat' with sid='tool2c'
Warning: Property 'LogArchiveFormat' has inconsistent values:METADATA='%t_%s_%r.dbf', SPFILE='(missing)', DA
TABASE='%t_%s_%r.dbf'
I have checked and I can’t see any difference between the settings in the primary or secondary.