ORA-16745: unable to add DB_UNIQUE_NAME string into The
DG_CONFIG list because it is full
- 1 Answers
- 2600 Views
- I also Faced
- E-Mail Answers
Answer / guest
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 re-enable the database.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
SQL*Loader-00706: Bad argument to ulerr [number].
SQL*Loader-00969: Error performing file name translation on kernel side
NZE-28841: Operation is not supported.
ORA-16108: database is no longer a standby database
ORA-07650: sigunc: $GETJPIW failure
ORA-10920: Cannot offline tablespace belonging to default temporary tablespace group
PLS-00101: reserved for future use
ORA-31048: Unsaved resources cannot be updated
PLS-00390: undefined column 'string' in INSERT statement
TNS-01300: ERROR at string
SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic
NNL-00271: Default domain is now "string"
Oracle Errors 
