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-22345: recompile type string.string before attempting this operation

1 Answers  

---

ORA-29557: Java system class string cannot be modified

1 Answers  

---

PLS-00580: supertype must be an object type

1 Answers  

---

IMG-00540: contentFormat and interleave conflict

1 Answers  

---

RMAN-06183: datafile or datafilecopy larger than MAXSETSIZE: file# string string

1 Answers  

---

ORA-30487: ORDER BY not allowed here

1 Answers  

---

ORA-30937: No schema definition for 'string' (namespace 'string') in parent 'string'

1 Answers  

---

CLSR-01003: Error number encountered during mounting database

1 Answers  

---

RMAN-05002: aborting point-in-time tablespace recovery

1 Answers  

---

ORA-16742: The standby "string" has used up its quota.

1 Answers  

---

NNO-00330: server saved the config file "string".

1 Answers  

---

PCB-00217: OCCURS INDEXED clause not allowed for host variable "string"

1 Answers  

---