RMAN-06556: datafile string must be restored from backup older than scn string

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

RMAN-06555: datafile string must be restored from backup created before string

Cause: An incomplete recovery session was started, but the file is in 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

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

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 destinatation init 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

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, the file must be restored before issuing a SWITCH command.

Action: Correct and resubmit the SWITCH command.

RMAN-06551: error while looking up datafile copy for file number: string

RMAN-06551: error while looking up datafile copy for file number: string

Cause: An error occurred while looking up the specified datafile copy in the recovery catalog or target database control file.

Action: This error is accompanied by other errors describing the reason for the failure. If the datafile copy was created during a RESTORE with a new name, ensure that the RESTORE completed successfully.

RMAN-06550: clone database not mounted and db_name not set in init.ora

RMAN-06550: clone database not mounted and db_name not set in init.ora

Cause: The clone database init.ora file does not specify the DB_NAME parameter.

Action: Add the DB_NAME parameter to the clone database init.ora and restart the instance.

RMAN-06549: connected to auxiliary database: string (not mounted)

RMAN-06549: connected to auxiliary database: string (not mounted)

Cause: This is an informational message only.

Action: No action is required.

RMAN-06548: connected to auxiliary database: string (DBID=string)

RMAN-06548: connected to auxiliary database: string (DBID=string)

Cause: This is an informational message only.

Action: No action is required.

RMAN-06547: tablespace SYSTEM cannot be excluded from whole database backup

RMAN-06547: tablespace SYSTEM cannot be excluded from whole database backup

Cause: The SYSTEM tablespace must be included in whole database backup.

Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation.

RMAN-06546: Error occurred getting response - assuming NO response

RMAN-06546: Error occurred getting response - assuming NO response

Cause: An error occurred reading user response.

Action: No action is required, this is an informational message only.

RMAN-06545: string is an invalid response - please re-enter.

RMAN-06545: string is an invalid response - please re-enter.

Cause: An incorrect response was entered.

Action: Enter a correct response.

RMAN-06544: Do you really want to delete the above objects (enter YES or NO)?

RMAN-06544: Do you really want to delete the above objects (enter YES or NO)?

Cause: This is a user prompt.

Action: Answer the question to proceed.

RMAN-06543: duplicate or conflicting LIST options: string and string

RMAN-06543: duplicate or conflicting LIST options: string and string

Cause: The indicated options conflict with each other or appear more than once in a LIST command.

Action: remove the duplicate or conflicting option from the command.

RMAN-06542: file string is excluded from whole database backup

RMAN-06542: file string is excluded from whole database backup

Cause: The indicated file will not be included in the backup set because it s tablesapce is configured as excluded from backup.

Action: No action is required.

RMAN-06541: tablespace string will be included in future whole database backups

RMAN-06541: tablespace string will be included in future whole database backups

Cause: This is an informational message only.

Action: No action is required.

RMAN-06540: tablespace string will be excluded from future whole database backups

RMAN-06540: tablespace string will be excluded from future whole database backups

Cause: This is an informational message only.

Action: No action is required.

RMAN-06537: CHANGE ... KEEP not supported for BACKUP

RMAN-06537: CHANGE ... KEEP not supported for BACKUP

Cause: The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command.

Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06536: BACKED UP ... TIMES option is supported only for archived logs

RMAN-06536: BACKED UP ... TIMES option is supported only for archived logs

Cause: The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs.

Action: Remove the option and resubmit the command.

RMAN-06535: LIST COPY OF SPFILE is not supported

RMAN-06535: LIST COPY OF SPFILE is not supported

Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy.

Action: Remove SPFILE from the command.

RMAN-06534: KEEP ... CONSISTENT option is not supported

RMAN-06534: KEEP ... CONSISTENT option is not supported

Cause: The KEEP ... CONSISTENT option was specified but the option is not supported.

Action: Remove the option and resubmit the command.

RMAN-06533: KEEP ... NOLOGS option cannot be used when datafiles are fuzzy

RMAN-06533: KEEP ... NOLOGS option cannot be used when datafiles are fuzzy

Cause: The KEEP ... NOLOGS option was specified for a backup or copy of files in a fuzzy state. This kind of backup requires archive logs for recovery, so archive logs must be kept.

Action: Remove the KEEP ... NOLOGS option or make sure the files are not in in a fuzzy state and resubmit the command.

RMAN-06532: redundancy count must be greater than zero

RMAN-06532: redundancy count must be greater than zero

Cause: The REDUNDANCY operand specified for the retention policy was zero.

Action: Specify a REDUNDANCY operand of 1 or greater.

RMAN-06531: CHANGE ... KEEP not supported for incremental BACKUPSET

RMAN-06531: CHANGE ... KEEP not supported for incremental BACKUPSET

Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets cannot have KEEP attributes.

Action: Do not specificy backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.

RMAN-06530: CHANGE ... KEEP not supported for backup set which contains archive logs

RMAN-06530: CHANGE ... KEEP not supported for backup set which contains archive logs

Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archive logs. Backup sets with archive logs cannot have KEEP attributes.

Action: Do not specify backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.

RMAN-06529: CHANGE ... KEEP not supported for ARCHIVELOG

RMAN-06529: CHANGE ... KEEP not supported for ARCHIVELOG

Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archive logs.

Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE

RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE

Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces.

Action: Use CHANGE BACKUPSET ... KEEP instead.

RMAN-06527: KEEP option is not supported for backup of backup sets

RMAN-06527: KEEP option is not supported for backup of backup sets

Cause: The KEEP option is not supported for backup of backup sets.

Action: Either remove KEEP option and retry the command or don t specify backup sets for this backup.

RMAN-06526: KEEP option cannot be used with incremental backup

RMAN-06526: KEEP option cannot be used with incremental backup

Cause: The KEEP option was specified for a incremental backup.

Action: Remove the option and resubmit the command.

RMAN-06525: RMAN retention policy is set to none

RMAN-06525: RMAN retention policy is set to none

Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either: * RMAN retention policy is not NONE or, * RMAN retention policy is specified with REPORT or DELETE command.

Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE or REPORT command.

RMAN-06524: RMAN retention policy will be applied to the command

RMAN-06524: RMAN retention policy will be applied to the command

Cause: This is an informational message only.

Action: No action is required.

RMAN-06522: KEEP FOREVER option is not supported without the recovery catalog

RMAN-06522: KEEP FOREVER option is not supported without the recovery catalog

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 control file. This is because information about this backup cannot be permanently stored. (If information is stored just in the control file 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

RMAN-06521: archived logs required to recover from this backup will expire when this backup expires

RMAN-06521: archived logs required to recover from this backup will expire when this backup expires

Cause: This is an informational message only.

Action: No action is required.

RMAN-06520: archived logs required to recover from this backup will not be kept

RMAN-06520: archived logs required to recover from this backup will not be kept

Cause: This is an informational message only.

Action: No action is required.

RMAN-06519: backup will never be obsolete

RMAN-06519: backup will never be obsolete

Cause: This is an informational message only.

Action: No action is required.

RMAN-06518: backup will be obsolete on date string

RMAN-06518: backup will be obsolete on date string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06517: KEEP option is not supported for archive log backups

RMAN-06517: KEEP option is not supported for archive log backups

Cause: The KEEP option is not supported for archive logs.

Action: Either remove KEEP option and retry the command or don t specify archive logs for this backup.

RMAN-06516: time specified in KEEP UNTIL clause must be be after today

RMAN-06516: time specified in KEEP UNTIL clause must be be after today

Cause: KEEP UNTIL support only a future time.

Action: Correct the time and retry the command.

RMAN-06515: archived logs required to recover from this copy will expire when this copy expires

RMAN-06515: archived logs required to recover from this copy will expire when this copy expires

Cause: This is an informational message only.

Action: No action is required.

RMAN-06514: archived logs required to recover from this copy will not be kept

RMAN-06514: archived logs required to recover from this copy will not be kept

Cause: This is an informational message only.

Action: No action is required.

RMAN-06513: copy will never be obsolete

RMAN-06513: copy will never be obsolete

Cause: This is an informational message only.

Action: No action is required.

RMAN-06512: copy will be obsolete on date string

RMAN-06512: copy will be obsolete on date string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06511: RMAN retention policy is set to redundancy number

RMAN-06511: RMAN retention policy is set to redundancy number

Cause: This is an informational message only.

Action: No action is required.

RMAN-06510: RMAN retention policy is set to recovery window of number days

RMAN-06510: RMAN retention policy is set to recovery window of number days

Cause: This is an informational message only.

Action: No action is required.

RMAN-06509: only SPFILE or control file can be restored from autobackup

RMAN-06509: only SPFILE or control file can be restored from autobackup

Cause: A datafile or archived log restore from autobackup was attempted.

Action: Do not specify DATAFILE or ARCHIVELOG for restore from autobackup.

RMAN-06508: MAXSETSIZE string kbytes should be greater than blocksize string bytes

RMAN-06508: MAXSETSIZE string kbytes should be greater than blocksize string bytes

Cause: MAXSETSIZE configured or specified in backup command should be greater than database blocksize.

Action: Specify a larger MAXSETSIZE limit.

RMAN-06507: trying alternate file for archivelog thread number, sequence number

RMAN-06507: trying alternate file for archivelog thread number, sequence number

Cause: This is an informational message, appearing when an archivelog was found out of sync with catalog database.

Action: No action is required.

RMAN-06506: the MAXSETSIZE option cannot be used with a backup backupset

RMAN-06506: the MAXSETSIZE option cannot be used with a backup backupset

Cause: The MAXSETSIZE option was specified for a backup backupset command.

Action: Remove the option and resubmit the command.

RMAN-06504: PROXY option with multiple backup copies is not supported

RMAN-06504: PROXY option with multiple backup copies is not supported

Cause: Multiple backup copies and PROXY option were specified in BACKUP command.

Action: Resolve the conflict.

RMAN-06503: skipping backupset key string; already backed up on string

RMAN-06503: skipping backupset key string; already backed up on string

Cause: The indicated backupset will not be backed up. It has already been backed up on the device once, or before the since time specified.

Action: No action is required.

RMAN-06502: skipping archive log file string; already backed on string

RMAN-06502: skipping archive log file string; already backed on string

Cause: The indicated log file will not be included in the backup set. It is already been backed up once, or before the since time specified.

Action: No action is required.

RMAN-06501: skipping datafile string; already backed up on string

RMAN-06501: skipping datafile string; already backed up on string

Cause: The indicated datafile will not be included in the backup set. It is already been backed up once, or before the since time specified.

Action: No action is required.

RMAN-06500: skipping backupset key string; already backed up string time(s)

RMAN-06500: skipping backupset key string; already backed up string time(s)

Cause: The indicated backupset will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization.

Action: No action is required.

RMAN-06499: skipping archive log file string; already backed up string time(s)

RMAN-06499: skipping archive log file string; already backed up string time(s)

Cause: The indicated log file will not be included in the backup set because it is already backed up on the device requested. Use FORCE option to override backup optimization.

Action: No action is required.

RMAN-06498: skipping datafile string; already backed up string time(s)

RMAN-06498: skipping datafile string; already backed up string time(s)

Cause: The indicated datafile will not be included in the backup set. It is already backed up on the device requested and file is offline or read-only datafile. Use the FORCE option to override backup optimization.

Action: No action is required.

RMAN-06497: WARNING: control file is not current, control file autobackup skipped

RMAN-06497: WARNING: control file is not current, control file autobackup skipped

Cause: Control file autobackup is not possible without a current control file.

Action: This is a warning message, no action is required.

RMAN-06496: must use the TO clause when the database is mounted or open

RMAN-06496: must use the TO clause when the database is mounted or open

Cause: A control file restore was attempted when the database is mounted or open and no alternate destination was specified.

Action: Specify an alternate destination with the TO clause or dismount the database.

RMAN-06495: must explicitly specify DBID with SET DBID command

RMAN-06495: must explicitly specify DBID with SET DBID command

Cause: Restore of a control file autobackup was attempted when the database is not mounted.

Action: Specify the DBID of the database using SET DBID or mount the database.

RMAN-06494: %s = string is out of range (string-string)

RMAN-06494: %s = string is out of range (string-string)

Cause: The specified parameter for restoring a control file autobackup is out of the valid range.

Action: Change the parameter value to a valid number or do not specify it.

RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string

RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string

Cause: For restoring a control file autobackup only SET UNTIL TIME can be used. It is not possible to translate the others to a precise day.

Action: Specify SET UNTIL TIME to indicate the day to start the restore of a control file autobackup.