Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16745: unable to add DB_UNIQUE_NAME string into The
DG_CONFIG list because it is full
- 1 Answers
- 2982 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-02805: Unable to set handler for SIGTPA
NZE-28833: inadequate information provided
ORA-16700: The standby database has diverged from the primary database.
ORA-27091: unable to queue I/O
ORA-16078: media recovery disabled
ORA-36902: (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
PCC-00071: Unable to open message file.
QSM-01053: NORELY referential integrity constraint on table, string, in TRUSTED/STALE TOLERATED integrity mode
ORA-12728: invalid range in regular expression
PCC-02354: A file included with #include may not contain SQL statements
ORA-00112: value of string is null
QSM-01039: selection present on right hand side of an outer join
Oracle Errors 
