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

ORA-16169: LGWR network server invalid parameters

1 Answers  

---

ORA-06306: IPA: Message write length error

1 Answers  

---

NNL-00295: Controller's local trace level is currently number

1 Answers  

---

TNS-12169: TNS:Net service name given as connect identifier is too long

1 Answers  

---

NNL-00298: No cache dump currently scheduled

1 Answers  

---

---

DRG-10516: failed to perform DDL operation due to an Oracle error

1 Answers  

---

SQL*Loader-03120: Resumable parameters ignored -- current session not resumable

1 Answers  

---

ORA-14638: cannot MERGE subpartitions in different Range Composite partitions

1 Answers  

---

ORA-01267: Failure getting date/time

1 Answers  

---

KUP-04105: zoned decimal to number conversion caused overflow for string

1 Answers  

---

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

1 Answers  

---

ORA-31426: cannot modify active subscriptions

1 Answers  

---