ORA-16745: unable to add DB_UNIQUE_NAME “string” into the DG_CONFIG list because it is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.
ERROR:
ORA-16745: unable to add DB_UNIQUE_NAME “string” into the DG_CONFIG list because it is full
DETAILED EXPLANATION:
This Oracle Database error message indicates that the Data Guard configuration has reached its maximum membership of 32 databases. The Broker configuration is full and Oracle Database is skilling in adding a database. The name of the database trying to join the configuration is provided in the error string.
COMMON CASE:
An administrator is trying to add another database to an Oracle Data Guard Broker configuration but is not able to.
NORMAL PROCEDURE:
In order to resolve this error, the maximum configuration membership for the Data Guard Broker would have to be increased.
STEPS:
1. Stop the Data Guard Broker as follows:
ALTER SYSTEM SET DG_BROKER_START=FALSE;
2. Use the DBMS_DG Broker package to config the maximum configuration membership using the following command:
EXECUTE DBMS_DG.SET_MAX_CONFIGURATIONS(value);
3. Start the Data Guard Broer as follows:
ALTER SYSTEM SET DG_BROKER_START=TRUE;