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-30690: timeout occurred while registering a TCP/IP connection for data traffic detection

1 Answers  

---

ORA-38464: expression set is not empty.

1 Answers  

---

ORA-01208: data file is an old version - not accessing current version

1 Answers  

---

ORA-29863: warning in the execution of ODCIINDEXCREATE routine

1 Answers  

---

LPX-00303: attribute value "~S" not expected for ~S

1 Answers  

---

---

LPX-00018: internal error "nested open strings"

1 Answers  

---

NNL-00244: Processing of modification requests is now disabled

1 Answers  

---

ORA-13526: baseline (string) does not exist

1 Answers  

---

DRG-11531: start token not found on line string

1 Answers  

---

ORA-32772: BIGFILE is invalid option for this type of tablespace

1 Answers  

---

ORA-06601: LU6.2 Driver: Invalid database ID string

1 Answers  

---

ORA-14614: List value 'string' specified twice in subpartition 'string'

1 Answers  

---