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

NNL-00852: Renames refused, name is a topology name: number

1 Answers  

---

ORA-07425: sdpri: error string in translating dump file location.

1 Answers  

---

LFI-00132: Record length string is greater than max length of string.

1 Answers  

---

ORA-33050: (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.

1 Answers  

---

ORA-01799: a column may not be outer-joined to a subquery

1 Answers  

---

---

ORA-13369: invalid value for etype in the 4-digit format

1 Answers  

---

ORA-30462: unsupported operator: string

1 Answers  

---

ORA-04027: self-deadlock during automatic validation for object string.string

1 Answers  

---

ORA-01198: must specify size for log file if RESETLOGS

1 Answers  

---

DRG-11603: URL store: payment required to access string

1 Answers  

---

PCC-00032: Invalid option "string"

1 Answers  

---

DRG-10601: failed to remove pending DML for this index

1 Answers  

---