| RMAN-20243 |
database db_unique_name is not known to the recovery catalog |
| RMAN-20244 |
can not change currently connected database db_unique_name |
| RMAN-20245 |
can not specify db_unique_name option in nocatalog mode |
| RMAN-20246 |
new db_unique_name is already known to the recovery catalog |
| RMAN-20250 |
offline range not found in the recovery catalog |
| RMAN-20260 |
backup piece not found in the recovery catalog |
| RMAN-20261 |
ambiguous backup piece handle |
| RMAN-20272 |
no parent backup found for the incremental backup |
| RMAN-20280 |
too many device types |
| RMAN-20298 |
DBMS_RCVCAT package not compatible with the recovery catalog |
| RMAN-20299 |
DBMS_RCVMAN package not compatible with the recovery catalog |
| RMAN-20310 |
proxy copy not found in the recovery catalog |
| RMAN-20311 |
ambiguous proxy copy handle |
| RMAN-20401 |
script already exists |
| RMAN-20501 |
redo logs from parent database incarnation cannot be applied |
| RMAN-20502 |
DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK |
| RMAN-20503 |
DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED |
| RMAN-20504 |
corruption list not found in recovery catalog |
| RMAN-20505 |
create datafile during recovery |
| RMAN-20506 |
no backup of archived log found |