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-01027: bind variables not allowed for data definition operations

1 Answers  

---

LRM-00106: out of memory

1 Answers  

---

DGM-16933: Unable to start instance "string".

1 Answers  

---

PCB-00402: Pseudo-text not properly terminated

1 Answers  

---

IMG-00582: output format does not support the specified interleave

1 Answers  

---

---

RMAN-06549: connected to auxiliary database: string (not mounted)

1 Answers  

---

ORA-21527: internal OMS driver error

1 Answers  

---

LPX-00202: could not open "~s" (error ~u)

1 Answers  

---

LPX-00285: invalid Unicode surrogate ~X ~X

1 Answers  

---

RMAN-20011: target database incarnation is not current in recovery catalog

1 Answers  

---

RMAN-06702: could not initialize for input file: "string"

1 Answers  

---

ORA-13641: Task cannot be interrupted yet. You may cancel it instead.

1 Answers  

---