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

RMAN-00552: syntax error in command line arguments

1 Answers  

---

ORA-13758: "SQL Tuning Set" "string" is in use.

1 Answers  

---

ORA-29292: file rename operation failed

1 Answers  

---

ORA-33010: (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.

1 Answers  

---

NNL-01061: Cache checkpoint interval: string

1 Answers  

---

---

ORA-09205: sfqio: error reading or writing to disk

1 Answers  

---

TNS-12513: TNS:service handler found but it has registered for a different protocol

1 Answers  

---

ORA-16620: one or more databases could not be contacted for a delete operation

1 Answers  

---

ORA-16760: Resource guard could not start logical apply engine

1 Answers  

---

ORA-29365: parameters string and string cannot both be set

1 Answers  

---

ORA-32805: identifier for string too long, maximum length is string characters

1 Answers  

---

ORA-13266: error inserting data into table string

1 Answers  

---