Resolving Database Registration Issues when Using add brokerconfig in GDS Environments

If the GDS database not registering after add brokerconfig, then review common causes and their solutions.

When configuring a Global Data Services (GDS) environment, you might encounter database registration issues with the GDS listeners. The following are common causes and solutions for missing database registration.

A common sign of this issue is the absence of database registration on GSM listeners. You can detect this by running the GDSCTLstatus database command. For example:

status database
Database: "test" Registered: N State: Ok ONS: Y. Role: N/A Instances: 0 Region: region1
Service: "test_failover" Globally started: Y Started: N
Scan: Y Enabled: Y Preferred: Y

The important part of this output is Registered property. If this property is set to N, then registration has not occurred.

For a database to register with a GDS listener, you must assign a region to the database. If you used the add brokerconfig command to add databases to a GDS pool that contains two or more regions, and the status database command shows no registration, then assign the region manually using the modify database command:

modify database ... -region

If you add more than one standby database to the GDS configuration simultaneously, then you can receive the error `ORA-45539: Database *db_name* has already been added to another pool`. To resolve this issue, add and synchronize standby databases one at a time.

Parent topic: Troubleshooting Global Data Services