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-40211: algorithm name string is invalid

1 Answers  

---

QSM-02131: agg(expr) requires correspondng SUM(expr) function

1 Answers  

---

LSX-00231: invalid unsigned integer "~S"

1 Answers  

---

TNS-00109: Message could not be printed; not enough memory

1 Answers  

---

RMAN-08010: channel string: specifying datafile(s) in backupset

1 Answers  

---

ORA-13013: the specified topology was not INTERIOR or BOUNDARY

1 Answers  

---

ORA-22976: incorrect number of arguments to MAKE_REF

1 Answers  

---

ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.

1 Answers  

---

ORA-01951: ROLE 'string' not granted to 'string'

1 Answers  

---

ORA-24408: could not generate unique server group name

1 Answers  

---

ORA-06142: NETTCP: error getting user information

1 Answers  

---

IMG-00705: unsupported or corrupted input format

1 Answers  

---