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

ORA-13405: null or invalid dimensionSize parameter

1 Answers  

---

ORA-02700: osnoraenv: error translating ORACLE_SID

1 Answers  

---

ORA-16104: invalid Logical Standby option requested

1 Answers  

---

ORA-25148: ONLINE option not permitted

1 Answers  

---

TNS-00536: Connection entered inappropriate state

1 Answers  

---

IMG-00815: merged area queue free failed

1 Answers  

---

ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE.

1 Answers  

---

ORA-09821: Numeric label is not valid

1 Answers  

---

ORA-29851: cannot build a domain index on more than one column

1 Answers  

---

ORA-15094: attempted to write to file opened in read only mode

1 Answers  

---

KUP-04009: invalid SLF handle

1 Answers  

---

TNS-12516: TNS:listener could not find available handler with matching protocol stack

1 Answers  

---