GDS: Add Brokerconfig Fails with ORA-44881 ORA-45539
(Doc ID 2926518.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.16.0.0.0 and laterInformation in this document applies to any platform.
Goal
Disclaimer:
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
DB Unique Name: orcl, Net Connection Alias: orcl.db_domain.com
gdspool: orclqa,orcldev
region: west
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
DB Unique Name: orcl, Net Connection Alias: orcl.db_domain.com
gdspool: orclqa,orcldev
region: west
When trying to add a dg broker in GDS configuration, It fails with following errors:
1. While doing add broker configurations , It fails with ORA-44881: GDS pool is not empty
The above error occurs when one database has already been added to GDS as standalone and later a standby database is added.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |