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-24023: Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]

1 Answers  

---

ORA-01615: instance string (thread string) is mounted - cannot disable

1 Answers  

---

ORA-39043: Object type string is not supported for string jobs.

1 Answers  

---

ORA-29381: plan/consumer_group string referred to by another plan and cannot be deleted

1 Answers  

---

ORA-31515: CDC change source string already exists

1 Answers  

---

ORA-06420: NETCMN: SID lookup failure

1 Answers  

---

SQL*Loader-00423: element count is greater than maximum allowed for the column

1 Answers  

---

NCR-00001: NCR: Could not allocate memory

1 Answers  

---

ORA-01922: CASCADE must be specified to drop 'string'

1 Answers  

---

ORA-19604: conversation file naming phase is over

1 Answers  

---

ORA-12539: TNS:buffer over- or under-flow

1 Answers  

---

ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes

1 Answers  

---