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-20272: no parent backup found for the incremental backup

1 Answers  

---

PCB-00233: Table size mismatch in INTO/USING. Minimum is: number

1 Answers  

---

CLSR-06507: Cannot add to SERVICE_NAMES, SERVICE_NAMES will be too long

1 Answers  

---

ORA-32136: Cannot perform operation on an invalid stream

1 Answers  

---

ORA-08263: ora_addr: cannot free listener address

1 Answers  

---

ORA-38480: creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.

1 Answers  

---

CLSR-06504: Service name not in SERVICE_NAMES

1 Answers  

---

ORA-02441: Cannot drop nonexistent primary key

1 Answers  

---

NNL-01006: META VIOLATION responses received: number

1 Answers  

---

ORA-13610: The directive string does not exist for task string.

1 Answers  

---

TNS-12232: TNS:No path available to destination

1 Answers  

---

ORA-15072: command requires at least string failure groups, specified only string

1 Answers  

---