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 a new 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-02203: INITIAL storage options not allowed

1 Answers  

---

ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous memory

1 Answers  

---

ORA-12228: TNS:protocol adapter not loadable

1 Answers  

---

ORA-00972: identifier is too long

1 Answers  

---

ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)

1 Answers  

---

SQL-02130: EXEC TOOLS interface is not available.

1 Answers  

---

ORA-16808: unable to resolve the full path name

1 Answers  

---

ORA-24011: cannot drop QUEUE, string should be stopped first

1 Answers  

---

PCC-00083: Bind and define variables not allowed in CREATE statement

1 Answers  

---

KUP-04072: error writing to file string

1 Answers  

---

ORA-28137: Invalid FGA audit Handler

1 Answers  

---

TNS-00515: Connect failed because target host or object does not exist

1 Answers  

---