RMAN-06492: controlfile autobackup format string must specify a string format specifier

RMAN-06492: controlfile autobackup format string must specify a string format specifier

Cause: A reserved format specifier was not specified for the CONTROLFILE AUTOBACKUP FORMAT

Action: Add a specifier to the CONTROLFILE AUTOBACKUP FORMAT

RMAN-06491: controlfile autobackup format string contains more than one string format specifier

RMAN-06491: controlfile autobackup format string contains more than one string format specifier

Cause: A CONTROLFILE AUTOBACKUP FORMAT cannot have more than one reserved format specifier.

Action: Specify only one reserved format specifier or use an alternative format.

RMAN-06490: WARNING: limit of autobackups for the day has been reached

RMAN-06490: WARNING: limit of autobackups for the day has been reached

Cause: No more control file autobackups are possible in this day.

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

RMAN-06489: no configuration found to allocate clone channel number for device type string

RMAN-06489: no configuration found to allocate clone channel number for device type string

Cause: Target channel configuration could not be used for clone channel as it contains CONNECT option.

Action: Setup clone channel configuration using CONFIGURE CLONE command for required channel number and device type

RMAN-06488: restore from autobackup does not allow any other modifiers

RMAN-06488: restore from autobackup does not allow any other modifiers

Cause: A control file or SPFILE restore from autobackup was attempted and other restore options were used.

Action: Do not specify any other options for the control file autobackup restore.

RMAN-06487: changed proxy copy expired

RMAN-06487: changed proxy copy expired

Cause: This is an informational message only.

Action: No action is required.

RMAN-06486: changed backup piece expired

RMAN-06486: changed backup piece expired

Cause: This is an informational message only.

Action: No action is required.

RMAN-06485: changed archivelog expired

RMAN-06485: changed archivelog expired

Cause: This is an informational message only.

Action: No action is required.

RMAN-06484: changed control file copy expired

RMAN-06484: changed control file copy expired

Cause: This is an informational message only.

Action: No action is required.

RMAN-06483: changed datafile copy expired

RMAN-06483: changed datafile copy expired

Cause: This is an informational message only.

Action: No action is required.

RMAN-06482: WARNING: proxy copy string cannot be found on the storage medium

RMAN-06482: WARNING: proxy copy string cannot be found on the storage medium

Cause: The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk.

Action: If the storage containing the proxy copy has been removed from the host, restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy.

RMAN-06481: WARNING: backup piece string cannot be found on the storage medium

RMAN-06481: WARNING: backup piece string cannot be found on the storage medium

Cause: The CHANGE BACUKPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium.

Action: If the storage containing the backup piece has been removed from the host, restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece.

RMAN-06480: WARNING: archivelog string cannot be found on disk

RMAN-06480: WARNING: archivelog string cannot be found on disk

Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archivelog cannot be found on disk.

Action: If the storage containing the archivelog has been removed from the host, restore it and retry the command. If the archivelog is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archivelog.

RMAN-06479: WARNING: control file copy string cannot be found on disk

RMAN-06479: WARNING: control file copy string cannot be found on disk

Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk.

Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this control file.

RMAN-06478: WARNING: datafile copy string cannot be found on disk

RMAN-06478: WARNING: datafile copy string cannot be found on disk

Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafile copy cannot be found on disk.

Action: If the storage containing the datafile copy has been removed from the host, restore it and retry the command. If the datafile copy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.

RMAN-06477: configuration value length exceeds 1024

RMAN-06477: configuration value length exceeds 1024

Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes.

Action: Reduce the length of CONFIGURE CHANNEL command options

RMAN-06476: channel number out of range (1-254): number

RMAN-06476: channel number out of range (1-254): number

Cause: Channel number entered in CONFIGURE CHANNEL command is out of range.

Action: Enter channel number within allowed range and retry the command. for this device and retry the command

RMAN-06475: parallelism setting out of range (1-254): number

RMAN-06475: parallelism setting out of range (1-254): number

Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range

Action: Enter value of parallelism that are within the allowed range.

RMAN-06474: maintenance channels are not allocated

RMAN-06474: maintenance channels are not allocated

Cause: RELEASE CHANNEL was used without allocating any maintenance channels.

Action: Allocate maintenance channel before executing this command.

RMAN-06472: channel id string is automatically allocated

RMAN-06472: channel id string is automatically allocated

Cause: Channel id was used on ALLOCATE or RELEASE command.

Action: Use other channel id that does not belong to reserved channel id s namespace

RMAN-06471: no configuration found to allocate channels for string

RMAN-06471: no configuration found to allocate channels for string

Cause: Device type configuration was not found in recovery catalog

Action: Setup device type configuration using configure command for required device type

RMAN-06470: DEVICE TYPE is supported only when automatic channels are used

RMAN-06470: DEVICE TYPE is supported only when automatic channels are used

Cause: The DEVICE TYPE option was specified with a BACKUP, RESTORE, RECOVER, DUPLICATE, CHANGE, VALIDATE, CROSSCHECK, or DELETE EXPIRED command. This option is allowed only when automatically allocated channels are used.

Action: Remove the DEVICE TYPE option and re-run the command. Or Remove all ALLOCATE commands and re-run the script so that channels are automatically allocated.

RMAN-06469: could not translate corruption list

RMAN-06469: could not translate corruption list

Cause: An error was received when calling dbms_rcvman

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06468: Invalid Data Block Address: number

RMAN-06468: Invalid Data Block Address: number

Cause: The DBA specified doesn t belong to the mentioned tablespace

Action: Check the DBA

RMAN-06467: could not translate DBA: number

RMAN-06467: could not translate DBA: number

Cause: An error was received when calling dbms_rcvman

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06466: error parsing configuration string (string)

RMAN-06466: error parsing configuration string (string)

Cause: Unsupported configuration string is stored in recovery catalog or target database control file.

Action: Check compatibility matrix rman executable and target database and recover catalog. Use dbsm_backup_restore.deleteConfig to remove problematic configuration.

RMAN-06465: configuration not implemented: string

RMAN-06465: configuration not implemented: string

Cause: The configuration is not implemented in the current release.

Action: Avoid using the command.

RMAN-06464: BACKUP BACKUPSET is not supported with VALIDATE option

RMAN-06464: BACKUP BACKUPSET is not supported with VALIDATE option

Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command.

Action: To VALIDATE BACKUPSET use validate or restore validate command.

RMAN-06463: Backup set key string cannot be backed up by proxy.

RMAN-06463: Backup set key string cannot be backed up by proxy.

Cause: The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set.

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

RMAN-06462: no backupsets found on device DISK that match specification

RMAN-06462: no backupsets found on device DISK that match specification

Cause: A backupset record specifier did not match an backupset on device DISK in the recovery catalog.

Action: Resubmit the command with a different backupset record specifier. The rman LIST command can be used to display all backupsets that Recovery Manager knows about.

RMAN-06461: current control file cannot be backed up by proxy.

RMAN-06461: current control file cannot be backed up by proxy.

Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.

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

RMAN-06460: control cile copy string cannot be backed up by proxy.

RMAN-06460: control cile copy string cannot be backed up by proxy.

Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.

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

RMAN-06459: BACKUP lamp;lt;lamp;nbsp;VALIDATE|DURATIONlamp;gt; is not supported with PROXY

RMAN-06459: BACKUP lamp;lt;lamp;nbsp;VALIDATE|DURATIONlamp;gt; is not supported with PROXY

Cause: BACKUP lamp;lt;lamp;nbsp;VALIDATE|DURATIONlamp;gt; and PROXY were specified in the same backup command.

Action: Remove the incompatible option.

RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST

RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST

Cause: The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_ DEST was specified with AS COPY.

Action: Remove the AS COPY option and resubmit the command.

RMAN-06457: UNTIL scn (string) is ahead of last scn in archived logs (string)

RMAN-06457: UNTIL scn (string) is ahead of last scn in archived logs (string)

Cause: UNTIL scn cannot be more than the last scn of the last archived log

Action: Check the UNTIL scn.

RMAN-06456: command is obsolete

RMAN-06456: command is obsolete

Cause: This is an informational message only.

Action: No action is required.

RMAN-06455: point-in-time tablespace recovery requires Enterprise Edition

RMAN-06455: point-in-time tablespace recovery requires Enterprise Edition

Cause: A point-in-time tablespace recovery was attempted, but Enterprise Edition is not installed.

Action: Do not do point-in-time tablespace recovery.

RMAN-06454: duplexed backups require Enterprise Edition

RMAN-06454: duplexed backups require Enterprise Edition

Cause: The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed.

Action: Do not attempt to create more than one copy of each backup piece.

RMAN-06453: RECOVERABLE may only be used with datafile objects

RMAN-06453: RECOVERABLE may only be used with datafile objects

Cause: An attempt was made to use LIST ... RECOVERABLE .. with OF CONTROLFILE or OF ARCHIVELOG.

Action: Remove the RECOVERABLE keyword and try again.

RMAN-06452: %s package upgraded to version string

RMAN-06452: %s package upgraded to version string

Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog packages are not changed with each Oracle release.

Action: No action is required.

RMAN-06451: proxy copy handle=string recid=string stamp=string

RMAN-06451: proxy copy handle=string recid=string stamp=string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06450: crosschecked proxy copy: found to be string

RMAN-06450: crosschecked proxy copy: found to be string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06449: deleted proxy copy

RMAN-06449: deleted proxy copy

Cause: This is an informational message only.

Action: No action is required.

RMAN-06448: uncataloged proxy copy

RMAN-06448: uncataloged proxy copy

Cause: This is an informational message only.

Action: No action is required.

RMAN-06447: changed proxy copy available

RMAN-06447: changed proxy copy available

Cause: This is an informational message only.

Action: No action is required.

RMAN-06446: changed proxy copy unavailable

RMAN-06446: changed proxy copy unavailable

Cause: This is an informational message only.

Action: No action is required.

RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used

RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used

Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.

Action: Re-start rman if you wish to use a recovery catalog.

RMAN-06444: %s created with compilation errors

RMAN-06444: %s created with compilation errors

Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL or SQL package specification or body could not be created because of PL or SQL compilation errors.

Action: The PL or SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle support. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.

RMAN-06443: error upgrading recovery catalog

RMAN-06443: error upgrading recovery catalog

Cause: An error was received from the recovery catalog database while upgrading the recovery catalog.

Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as column already exists, which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.

RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade

Cause: The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN.

Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult the Migration Guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN.

RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN

RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN

Cause: The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed.

Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager.

RMAN-06439: RMAN must be upgraded to version string to work with this package

RMAN-06439: RMAN must be upgraded to version string to work with this package

Cause: This message indicates the minimum version of recovery manager required to use the package which was specified in message 6191.

Action: A newer version of RMAN must be used with this package.

RMAN-06438: error executing package DBMS_RCVMAN in string database

RMAN-06438: error executing package DBMS_RCVMAN in string database

Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb.

Action: re-create the DBMS_RCVMAN package in the SYS schema.

RMAN-06437: cannot drop catalog - catalog is newer than this RMAN

RMAN-06437: cannot drop catalog - catalog is newer than this RMAN

Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog.

Action: Use the version of RMAN which most recently created or upgraded the recovery catalog.

RMAN-06436: enter DROP CATALOG command again to confirm catalog removal

RMAN-06436: enter DROP CATALOG command again to confirm catalog removal

Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.

Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again.

RMAN-06435: recovery catalog owner is string

RMAN-06435: recovery catalog owner is string

Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands.

Action: No action is required.

RMAN-06434: some errors occurred while removing recovery catalog

RMAN-06434: some errors occurred while removing recovery catalog

Cause: Some errors were received from the recovery catalog database while removing the recovery catalog.

Action: Correct the error(s) and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as object not found , which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog.

RMAN-06433: error installing recovery catalog

RMAN-06433: error installing recovery catalog

Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server.

Action: The most common reasons for failure to install the recovery catalog are: DROP CATALOG command to remove any partially installed recovery catalog, and retry the command. the DROP CATALOG command to remove the partially installed recovery catalog and retry the command.

RMAN-06432: recovery catalog dropped

RMAN-06432: recovery catalog dropped

Cause: This is an informational message issued by the DROP CATALOG command.

Action: No action is required.

RMAN-06431: recovery catalog created

RMAN-06431: recovery catalog created

Cause: This is an informational message issued by the CREATE CATALOG command.

Action: No action is required.