In my recent post I already mentioned it a little bit: Integrating your manual Data Guard Broker configuration in OEM Cloud Control can become a sort of climbing a Mountain. And it doesn’t have to be.
But first a short description of the situation. I have a working Data Guard broker configuration between two Cluster Databases running Oracle 220.127.116.11 on linux x86-64. Both clusters have an Cloud Control agent (18.104.22.168) deployed on all the nodes in question. De databases are monitored just fine and accessible via Cloud Control. But the Data Guard Admin page shows:
And the Data Guard Performance page shows:
Data Guard DGMGRL view of the configuration is:
When you press the link “Verify Configuration” under the Additional Administration heading in the Data Guard Admin page Cloud Control starts to verify your Data Guard configuration (and changing it, but more on that later):
And it completes with warnings:
Nothing to big to deal with so far (Just have a look at your broker log file to see what else Cloud Control has changed).
The Data Guard Admin page briefly showed the notification that the broker wasn’t configured but still shows some graphs for the Redo Generation Rate, Lag times and Apply rate.
Then I added the Standby Database again via:
But I’m more concerned with the change in database “broker” parameters. I had configured one broker config file in +DATA and one in +FRA. Both in a sub directory called BROKER, but both have been changed to the same +DATA location (different file names) but no longer in my BROKER sub directory.
So I will need to set the dg_broker_start parameter to FALSE, change the config file locations to where I want them and set the start parameter to TRUE again. It bothers me that I wasn’t asked where I wanted the broker configuration files, and that the old broker config files are still there on ASM. That leaves room for errors in the future…