| RMAN-05048 |
specified file name string conflicts with a file used by the target database |
| RMAN-05049 |
datafile string is an Oracle Managed File, DB_CREATE_FILE_DEST not set at target |
| RMAN-05051 |
analyzing automatic repair options; this may take some time |
| RMAN-05052 |
Repair string is not compatible with this version of RMAN. |
| RMAN-05053 |
Do you really want to execute the above repair (enter YES or NO)? |
| RMAN-05054 |
recover block operand string cannot be used to recover datafile |
| RMAN-05055 |
recover datafile operand string cannot be used to recover block |
| RMAN-05057 |
Do you want to open the database (enter YES or NO)? |
| RMAN-05058 |
Do you want to open resetlogs the database (enter YES or NO)? |
| RMAN-05060 |
block specifier must be specified to recover block |
| RMAN-05061 |
analyzing automatic repair options complete |
| RMAN-05062 |
image copy needs no roll forward |
| RMAN-05500 |
the auxiliary database must be not mounted when issuing a DUPLICATE command |
| RMAN-05501 |
aborting duplication of target database |
| RMAN-05502 |
the target database must be mounted when issuing a DUPLICATE command |
| RMAN-05503 |
at least one auxiliary channel must be allocated to execute this command |
| RMAN-05504 |
at least two redo log files or groups must be specified for this command |
| RMAN-05505 |
auxiliary file name conversion of string exceeds maximum length of string |
| RMAN-05506 |
error during recursive execution |
| RMAN-05507 |
standby control file checkpoint (string) is more recent than duplication point in time (string) |