There are a few simple steps that needs to be followed to make the data broker be able to function.
On the primary
alter system set local_listener=This will ensure that the database knows about the listener that is running on a virtual host name.
After this step is completed Follow the steps in Metalink Doc # 808783.1
I'm listing the steps below
ALTER SYSTEM SET DG_BROKER_START=FALSE; SQL> show parameter dg_broker_config_file --- remove files that are displayed on the primary and the start broker on both the primary and the standby SQL>ALTER SYSTEM SET DG_BROKER_START=TRUE;After this connect to Dataguard Manager
DGMGRL>CREATE CONFIGURATION 'DGCONF' AS PRIMARY DATABASE IS 'PROD' CONNECT IDENTIFIER IS PROD; DGMGRL> ADD DATABASE 'STDBY' AS CONNECT IDENTIFIER IS STDBY MAINTAINED AS PHYSICAL; --or LOGICAL DGMGRL> ENABLE CONFIGURATION; -- validate DGMGRL> SHOW CONFIGURATION; --Success means all is goodThe above commands are from the Metalink Doc above and work perfectly for a CFC . We are now able to failover our clusters and have Dataguard broker work for us to manage our configurations.