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

DRG-13000: error while adding or removing a sub lexer

1 Answers  

---

ORA-31433: subscriber view does not exist

1 Answers  

---

DRG-11121: failed to read from file string

1 Answers  

---

DRG-11825: Not Acceptable

1 Answers  

---

DRG-13001: sub lexer and multi lexer must have the same owner

1 Answers  

---

ORA-22826: cannot construct an instance of a non instantiable type

1 Answers  

---

ORA-28577: argument string of external procedure string has unsupported datatype string

1 Answers  

---

ORA-32507: expecting string but found string

1 Answers  

---

ORA-38450: error computing a stored attribute for the expression set.

1 Answers  

---

TNS-00013: INTCTL: error while performing NS disconnect command

1 Answers  

---

ORA-28603: statement not permitted on empty tables

1 Answers  

---

ORA-01900: LOGFILE keyword expected

1 Answers  

---