Error: ORA-16532: Data Guard broker configuration does not exist

Question

Hi there folks. Hope everyone is having a nice weekend.
Anyways, we have a 10.2.0.4 rac primary and a 10.2.0.4 standby physical standby. We recently did a switchover and the dgbroker files automatically got created in the Oracle_home/dbs location of the primary. Now need to move these files to the common ASM DG. For this, I followd the steps from this doc:
How To Move Dataguard Broker Configuration File On ASM Filesystem (Doc ID 839794.1)
The only exception to this case is that I have to do this on a Primary and not a standby so I am disabling and enabling the Primary(and not standby as mentioned in below steps)
To rename the broker configuration files in STANDBY to FRA/MYSTD/broker1.dat and FRA/MYSTD/broker2.dat, Follow the below steps
1. Disable the standby database from within the broker configuration
DGMGRL> disable database MYSTD;
2. Stop the broker on the standby
SQL> alter system set dg_broker_start = FALSE;
3. Set the dg_broker_config_file1 & 2 parameters on the standby to the appropriate location required.
SQL> alter system set dg_broker_config_file1 = '+FRA/MYSTD/broker1.dat';
SQL> alter system set dg_broker_config_file2 = '+FRA/MYSTD/broker2.dat'
4. Restart the broker on the standby
SQL> alter system set dg_broker_start = TRUE
5. From the primary, enable the standby
DGMGRL> enable database MYSTD;
6. Broker configuration files will be created in the new ASM location.
I did so but when I try to enable the Primary back I get this:
Error: ORA-16532: Data Guard broker configuration does not exist
Configuration details cannot be determined by DGMGRL
Form this link,(Errors setting up DataGuard Broker it would seem that I would need to recreate the configuration....Is that correct ? If yes then how come Metalink is missing this info of recreating the configuration... OR is it that that scenario wouldnt be applicable in my case ?
Thanks for your help.

Answer 1

Yes I can confirm from the gv$spparameter view that the changes are effective for all 3 instances. From the alert log the alter system didnt throw u pany errros. I didnt restart the instances though since I dont have the approvals yet. But I dont think thats required.