ORA-16745: unable to add DB_UNIQUE_NAME string into The
DG_CONFIG list because it is full
- 1 Answers
- 2442 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 |
ORA-32739: Hang analysis aborted due to failed heap re-grow
ORA-19200: Invalid column specification
NNL-00903: SERVER FAILURE responses sent: number
ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes
TNS-00501: Cannot allocate memory
ORA-24149: invalid rule name
ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You specified number.
ORA-09799: File label retrieval failed.
ORA-09765: osnmop: fork failed
ORA-08265: create_ora_addr: cannot open nameserver
DRG-12500: stoplist string already exists
RMAN-06107: WARNING: controlfile is not current for REPORT NEED BACKUP DAYS
Oracle Errors 
