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

TNS-04232: Trace Assistant WARNING: Not retrieving all rows

1 Answers  

---

ORA-13250: insufficient privileges to modify metadata table entries

1 Answers  

---

ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.

1 Answers  

---

ORA-25951: join index where clause cannot contain OR condition

1 Answers  

---

ORA-16547: cannot disable the primary database

1 Answers  

---

---

ORA-08466: raw buffer length string is too short for string

1 Answers  

---

ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table

1 Answers  

---

ORA-24148: cannot drop rule string.string with dependents

1 Answers  

---

ORA-39726: unsupported add/drop column operation on compressed tables

1 Answers  

---

TNS-00253: Error in reading network configuration data from file string with error string

1 Answers  

---

LSX-00246: invalid QName "~S"

1 Answers  

---

ORA-12661: Protocol authentication to be used

1 Answers  

---