Answer / guest

Cause: The KEEP FOREVER option was used, but it requires a
connection to a recovery catalog database. The KEEP FOREVER
option cannot be used when the backup repository is the
target database controlfile. This is because information
about this backup cannot be permanently stored. (If
information is stored just in the controlfile it will be
aged out depending on CONTROL_FILE_RECORD_KEEP_TIME
initialization parameter.)

Action: If a recovery catalog database is available, then
connect to the recovery catalog and retry the command,
otherwise use a different KEEP option. 6523, 1, "unused"

Please add more information about this Error

PLS-00206: %%TYPE must be applied to a variable, column, field or attribute, not to "string"

1 Answers  

---

ORA-06747: TLI Driver: error in listen

1 Answers  

---

ORA-32057: invalid lock mode

1 Answers  

---

NID-00410: Reversion of database changes failed during validation - database is intact.

1 Answers  

---

RMAN-06515: archived logs required to recover from this copy will expire when this copy expires

1 Answers  

---

---

ORA-24203: operation failed, queue table string.string has errors

1 Answers  

---

ORA-28509: unable to establish a connection to non-Oracle system

1 Answers  

---

CLSR-00519: No instance found

1 Answers  

---

ORA-12235: TNS:Failure to redirect to destination

1 Answers  

---

ORA-06000: NETASY: port open failure

1 Answers  

---

DRG-51023: stemmer file cannot be opened

1 Answers  

---

ORA-12728: invalid range in regular expression

1 Answers  

---