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-14193: invalid ALTER INDEX MODIFY SUBPARTITION option

1 Answers  

---

ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it

1 Answers  

---

ORA-02790: File name is too long

1 Answers  

---

ORA-07842: sllfcl: SYS$CLOSE failure

1 Answers  

---

NZE-28805: Cannot retrieve information from the data source.

1 Answers  

---

SQL*Loader-00947: subpartition load requested and string has enabled triggers or constraints

1 Answers  

---

NNO-00705: warning: cannot open checkpoint file "string", checkpointing disabled

1 Answers  

---

NID-00135: There are number active threads

1 Answers  

---

SQL-02152: Invalid numeric variable for use in an array GET/SET statement

1 Answers  

---

DRG-11732: phrase does not have any translations

1 Answers  

---

ORA-07613: $GETJPIW failed in retrieving the user's process label

1 Answers  

---

ORA-13702: Snapshot IDs specified by the range [string, string] are equal.

1 Answers  

---