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

NID-00505: REVERT Revert failed change NO

1 Answers  

---

ORA-29518: name string resolved to an object in schema string that is not a Java class

1 Answers  

---

ORA-06254: NETNTT: cannot share connection to cube

1 Answers  

---

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

1 Answers  

---

ORA-19621: archivelog range has already been specified

1 Answers  

---

TNS-12688: Login failed: the SecurID server rejected the new pincode

1 Answers  

---

ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE

1 Answers  

---

TNS-00291: Navigator: Enabled Interchange

1 Answers  

---

DRG-51313: timeout while waiting for DML or optimize lock

1 Answers  

---

ORA-30075: TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint

1 Answers  

---

ORA-31195: XML node 'string' (type=string) does not support this operation

1 Answers  

---

PCC-02104: Unable to connect to Oracle

1 Answers  

---