RMAN-06560: WARNING: backup set with key number will be read number times
Cause: Backup set size is bigger than MAXSIZE limit, so it will be read more than once. This can cause slower restore performance.
Action: Increase the MAXSIZE parameter and retry the command.
RMAN-06559: MAXSIZE must be larger than 1 KB
Cause: The MAXSIZE parameter is out of range.
Action: Specify a valid size and retry the command.
RMAN-06558: an archived log size of number KB is bigger than MAXSIZE limit of number KB
Cause: This is an informational message only.
Action: No action required. See message RMAN-06557 for further details.
RMAN-06557: unable to restore archived log thread number, sequence number
Cause: Restore of the specified archived log failed because the size of the archived log is larger than MAXSIZE specified in the RECOVERY command.
Action: Specify a larger MAXSIZE limit. See message RMAN-06558 for further details.
RMAN-06556: datafile string must be restored from backup older than scn string
Cause: An incomplete recovery session was started, but the file is newer than the UNTIL clause.
Action: Check the UNTIL clause or restore the file from a sufficient old backup.
RMAN-06555: datafile string must be restored from backup created before string
Cause: An incomplete recovery session was started, but the file is newer than the UNTIL TIME clause.
Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup.
RMAN-06554: WARNING: file string is in backup mode
Cause: A file which is being backed up or copied is in backup mode. RMAN will back up the file anyway, but files do not need to be put into backup mode before backing them up with RMAN.
Action: Use the ALTER TABLESPACE ... END BACKUP statement, at the target database server, to take the files out of backup mode.
RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME ... TO NEW
Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destination initialization parameter DB_CREATE_FILE_DEST is not set.
Action: Supply a full name to the SET NEWNAME command or set DB_CREATE_FILE_DEST at the target database.
RMAN-06552: newname for datafile number was set to NEW, but file was not restored
Cause: A SWITCH command was specified for a datafile, but the newname was set to NEW and the file was not restored. If newname is set to NEW, then the file must be restored before issuing a SWITCH command.
Action: Correct and resubmit the SWITCH command.
RMAN-06551: error while looking up datafilecopy for file number: string
Cause: An error occurred while looking up the specified datafilecopy in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. If the datafilecopy was created during a RESTORE with a new name, then ensure that the RESTORE completed successfully.