Oracle Error Messages: 10/05/11

RMAN-06597: conversion between platforms string and string is not implemented

RMAN-06597: conversion between platforms string and string is not implemented

Cause: Conversion of Oracle data files between the specified platforms was not supported.

Action: Do not do the conversion.

RMAN-06596: to use CONVERT compatibility must be set to 10.0.0 or greater, currently set to string

RMAN-06596: to use CONVERT compatibility must be set to 10.0.0 or greater, currently set to string

Cause: A command was attempted that requires a higher database compatibility.

Action: Raise the compatibility of the database before attempting the command again.

RMAN-06595: platform name string does not match database platform name string

RMAN-06595: platform name string does not match database platform name string

Cause: The platform name specified did not match the name of the database performing the conversion.

Action: Specify the correct platform name.

RMAN-06594: platform name string specified in TO PLATFORM is not valid

RMAN-06594: platform name string specified in TO PLATFORM is not valid

Cause: The platform name was not recognized.

Action: Specify a valid platform name.

RMAN-06593: platform name string specified in FROM PLATFORM is not valid

RMAN-06593: platform name string specified in FROM PLATFORM is not valid

Cause: The platform name was not recognized.

Action: Specify a valid platform name.

RMAN-06592: must specify FROM PLATFORM

RMAN-06592: must specify FROM PLATFORM

Cause: There was a missing parameter to the command.

Action: Specify the FROM PLATFORM parameter with the command.

RMAN-06591: must specify TO PLATFORM

RMAN-06591: must specify TO PLATFORM

Cause: There was a missing parameter to the command.

Action: Specify the TO PLATFORM parameter with the command.

RMAN-06590: tablespace string cannot be converted

RMAN-06590: tablespace string cannot be converted

Cause: The system tablespaces could not be transported to other platforms.

Action: Remove the specified tablespace from the CONVERT command and retry the operation.

RMAN-06589: cannot specify DB_FILE_NAME_CONVERT option without AS COPY

RMAN-06589: cannot specify DB_FILE_NAME_CONVERT option without AS COPY

Cause: The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backupset backups where multiple files are combined into a set.

Action: Remove the DB_FILE_NAME_CONVERT option and re-run the BACKUP command.

RMAN-06588: number of patterns (number) to DB_FILE_NAME_CONVERT should be even

RMAN-06588: number of patterns (number) to DB_FILE_NAME_CONVERT should be even

Cause: An uneven number of patterns was specified.

Action: Specify one more or one less pattern.

RMAN-06587: one or more datafilecopies were not found

RMAN-06587: one or more datafilecopies were not found

Cause: This error message was accompanied by an additional error message or messages indicating the cause of the error.

Action: Follow the recommended actions of the additional error message or messages.

RMAN-06586: no copy of datafile number with tag string found

RMAN-06586: no copy of datafile number with tag string found

Cause: An available datafile copy for the specified datafile could not be found.

Action: make sure that all specified datafiles have a copy available.

RMAN-06585: no copy of datafile number found

RMAN-06585: no copy of datafile number found

Cause: An available datafile copy for the specified datafile could not be found.

Action: make sure that all specified datafiles have a copy available.

RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types

RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types

Cause: DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETs will be created on DISK.

Action: Do not allocate non DISK channels to produce image copies to DISK or allocate only non DISK channels to produce BACKUPSETs only.

RMAN-06583: at least 1 channel of TYPE DISK must be allocated to use AS COPY option

RMAN-06583: at least 1 channel of TYPE DISK must be allocated to use AS COPY option

Cause: No channel of TYPE DISK was allocated.

Action: Allocate a channel of TYPE DISK and re-issue the command or remove AS COPY.

RMAN-06582: AS COPY option cannot be used when backing up backupsets

RMAN-06582: AS COPY option cannot be used when backing up backupsets

Cause: The backupset was specified with AS COPY.

Action: Remove the AS COPY option or remove the backupsets.

RMAN-06581: option string not supported

RMAN-06581: option string not supported

Cause: This option was specified and it is not supported.

Action: Remove the specified option.

RMAN-06580: the string option cannot be used with AS COPY

RMAN-06580: the string option cannot be used with AS COPY

Cause: The specified option was specified for a backup as copy command.

Action: Remove the option and resubmit the command.

RMAN-06578: INCREMENTAL LEVEL lamp;gt; 0 must be specified with FOR RECOVER OF

RMAN-06578: INCREMENTAL LEVEL lamp;gt; 0 must be specified with FOR RECOVER OF

Cause: The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL lamp;gt; 0.

Action: Specify INCREMENTAL LEVEL lamp;gt; 0 and resubmit the command.

RMAN-06577: FROM TAG option may only be used with datafilecopies

RMAN-06577: FROM TAG option may only be used with datafilecopies

Cause: The FROM TAG option was specified for datafiles.

Action: Remove the option and resubmit the command.

RMAN-06576: platform string (number) found in header of datafile string does not match specified platform name string (number)

RMAN-06576: platform string (number) found in header of datafile string does not match specified platform name string (number)

Cause: The platform specified in the command did not match the platform found in the datafile header.

Action: Specify the correct platform name and retry the command.

RMAN-06575: platform id number found in datafile string header is not a valid platform id

RMAN-06575: platform id number found in datafile string header is not a valid platform id

Cause: The platform id found in the datafile header was not recognized.

Action: Verify that this is a valid datafile.

RMAN-06572: database is open and datafile number is not offline

RMAN-06572: database is open and datafile number is not offline

Cause: The SWITCH command with the option TO COPY was specified, but datafile is not offline and database is open.

Action: Either make sure the datafile is offline or the database must be mounted but not opened.

RMAN-06571: datafile number does not have recoverable copy

RMAN-06571: datafile number does not have recoverable copy

Cause: The SWITCH command with the option TO COPY was specified but the datafile has no valid copy to switch to.

Action: Verify whether the datafile has a valid datafile copy.

RMAN-06570: datafile number switched to datafile copy string

RMAN-06570: datafile number switched to datafile copy string

Cause: This message was issued in response to a SWITCH command.

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

RMAN-06568: connected to target database: string (DBID=string, not open)

RMAN-06568: connected to target database: string (DBID=string, not open)

Cause: This is an informational message only.

Action: No action is required.

RMAN-06567: connected to auxiliary database: string (DBID=string, not open)

RMAN-06567: connected to auxiliary database: string (DBID=string, not open)

Cause: This is an informational message only.

Action: No action is required.

RMAN-06566: target database incarnation not found in control file

RMAN-06566: target database incarnation not found in control file

Cause: resetlogs change# and or or time of the target database doesn t match any database incarnation in the control file.

Action: One of the following actions can be taken to resolve this error 1) Restore the control file from the incarnation. 2) To populate the new incarnation, inspect or restore an archived log or datafile or datafile copy or backup set from the target incarnation

RMAN-06565: WARNING: string: sqlcode number was caught, automatic retry #number

RMAN-06565: WARNING: string: sqlcode number was caught, automatic retry #number

Cause: The RMAN client caught a transient error and will automatically retry several times.

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

RMAN-06564: must use the TO clause when the instance is started with SPFILE

RMAN-06564: must use the TO clause when the instance is started with SPFILE

Cause: A restore of the SPFILE from autobackup was attempted when the instance is started with SPFILE and no alternate destination was specified.

Action: Specify an alternate destination with the TO clause.

RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP

RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP

Cause: RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog.

Action: If the recovery catalog is available, connect to the recovery catalog and retry the restore. If the recovery catalog in not available, following is the procedure to restore control file or SPFILE: 1. Specify the DBID of the database with the SET DBID command. 2. If the autobackup was created with non-default autobackup format, then specify the autobackup format using the SET CONTROLFILE AUTOBACKUP FORMAT command. 3. If the backup was created with SBT device, then allocate an SBT channel using the ALLOCATE CHANNEL command. 4. Restore control file or SPFILE by starting the RESTORE ... FROM AUTOBACKUP command.

RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times

RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times

Cause: A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files.

Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.

RMAN-06561: available space must be larger than number kb

RMAN-06561: available space must be larger than number kb

Cause: The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files.

Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.

RMAN-06135: error executing host command: string

RMAN-06135: error executing host command: string

Cause: A host command returned a non-zero return code.

Action: Correct the offending command.

RMAN-06134: host command complete

RMAN-06134: host command complete

Cause: An operating system command has completed.

Action: None -this is an informational message.

RMAN-06133: recovery catalog may have obsolete data for datafile string

RMAN-06133: recovery catalog may have obsolete data for datafile string

Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the control file.

Action: If the recovery catalog has correct data for the datafile, then restore a backup control file using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the control file.

RMAN-06132: cannot backup datafile string because it is not in the control file

RMAN-06132: cannot backup datafile string because it is not in the control file

Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the control file. The control file is not current (it is a backup or a created control file).

Action: Recover the control file to make it current, then retry the backup command.

RMAN-06131: skip offline or readonly only allowed with current control file

RMAN-06131: skip offline or readonly only allowed with current control file

Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database control file is current. When the target control file is not current, it is not possible to obtain a datafile s offline or readonly status.

Action: Remove the skip option or mount a current control file on the target database.

RMAN-06129: invalid reserved channel ID: string

RMAN-06129: invalid reserved channel ID: string

Cause: The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users.

Action: Specify a different channel ID.

RMAN-06128: skipping inaccessible file string

RMAN-06128: skipping inaccessible file string

Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified.

Action: No action is required.

RMAN-06127: skipping read-only file string

RMAN-06127: skipping read-only file string

Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified.

Action: No action is required.

RMAN-06126: skipping offline file string

RMAN-06126: skipping offline file string

Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified.

Action: No action is required.

RMAN-06125: error while looking up archive log key: number

RMAN-06125: error while looking up archive log key: number

Cause: An error occurred while looking up the specified archive log key in the recovery catalog.

Action: This error is accompanied by other errors describing the reason for the failure.

RMAN-06124: error while looking up datafile copy key: number

RMAN-06124: error while looking up datafile copy key: number

Cause: An error occurred while looking up the specified datafile copy key in the recovery catalog.

Action: This error is accompanied by other errors describing the reason for the failure.

RMAN-06123: operation not supported without the recovery catalog or mounted control file

RMAN-06123: operation not supported without the recovery catalog or mounted control file

Cause: A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available.

Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command.

RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET

RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET

Cause: The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set.

Action: Use CHANGE BACKUPSET .. DELETE instead.

RMAN-06121: uncataloged control file copy

RMAN-06121: uncataloged control file copy

Cause: This is an informational message only.

Action: No action is required.

RMAN-06120: uncataloged archive log

RMAN-06120: uncataloged archive log

Cause: This is an informational message only.

Action: No action is required.

RMAN-06119: uncataloged datafile copy

RMAN-06119: uncataloged datafile copy

Cause: This is an informational message only.

Action: No action is required.

RMAN-06118: a backup control file older than SCN string must be used for this recovery

RMAN-06118: a backup control file older than SCN string must be used for this recovery

Cause: An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup.

Action: Restore a control file that was backed up before the specified SCN. The following RMAN commands can be used to do this: SET UNTIL SCN lamp;lt;lamp;nbsp;xlamp;gt;;(where lamp;lt;lamp;nbsp;xlamp;gt; is the SCN displayed in the message) RESTORE CONTROLFILE;