Oracle Error Messages: 10/12/11

RMAN-20241: ambiguous archived log name

RMAN-20241: ambiguous archived log name

Cause: more than one archived log in the recovery catalog match the specified name

Action: use the archived log key to uniquely specify the archived log

RMAN-20240: archived log not found in the recovery catalog

RMAN-20240: archived log not found in the recovery catalog

Cause: the specified archived log was not found in the recovery catalog or it has been marked deleted

Action: check the archived log name or key

RMAN-20231: ambiguous datafile copy name

RMAN-20231: ambiguous datafile copy name

Cause: more than one control file copy in the recovery catalog match the specified name.

Action: use the datafile copy key to uniquely specify the datafile copy

RMAN-20230: datafile copy not found in the recovery catalog

RMAN-20230: datafile copy not found in the recovery catalog

Cause: the specified datafile is not in the recovery catalog or it has been marked deleted

Action: check the datafile copy name or key

RMAN-20222: datafilename not found in recovery catalog or is ambiguous

RMAN-20222: datafilename not found in recovery catalog or is ambiguous

Cause: The specified datafilename is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the filename was for a different datafile at the time specified by the UNTIL clause than it is now.

Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER.

RMAN-20221: ambiguous control file copy name

RMAN-20221: ambiguous control file copy name

Cause: more than one control file copy in the recovery catalog match the specified name.

Action: none

RMAN-20220: control file copy not found in the recovery catalog

RMAN-20220: control file copy not found in the recovery catalog

Cause: the specified control file is not in the recovery catalog or it has been marked deleted

Action: check the filename

RMAN-20218: datafile not found in recovery catalog

RMAN-20218: datafile not found in recovery catalog

Cause: This is an internal error

Action: Contact Oracle Customer Support.

RMAN-20217: datafile not part of the database

RMAN-20217: datafile not part of the database

Cause: the datafile does not exists or did not exist at until time or scn

Action: check the datafile name or number. This is an internal error for restore database or tablespace.

RMAN-20215: backup set not found

RMAN-20215: backup set not found

Cause: The specified backup set key was not found in the recovery catalog

Action: Specify a different backup set key.

RMAN-20212: UNTIL CHANGE is an orphan incarnation

RMAN-20212: UNTIL CHANGE is an orphan incarnation

Cause: Specified UNTIL CHANGE was an orphan incarnation.

Action: Check the UNTIL CHANGE or UNTIL RESTORE POINT. If the database needs to be restored or flashed back to an orphan incarnation, use the RESET DATABASE TO INCARNATION command.

RMAN-06929: Cannot specify TRANSPORT SCRIPT clause more than once

RMAN-06929: Cannot specify TRANSPORT SCRIPT clause more than once

Cause: TRANSPORT SCRIPT clause specified more than once

Action: Remove redundant ON TARGET PLATFORM clause and retry the operation.

RMAN-06928: Cannot specify ON TARGET PLATFORM clause more than once

RMAN-06928: Cannot specify ON TARGET PLATFORM clause more than once

Cause: ON TARGET PLATFORM clause specified more than once

Action: Remove redundant ON TARGET PLATFORM clause and retry the operation.

RMAN-06927: Cannot specify NEW DATABASE clause more than once

RMAN-06927: Cannot specify NEW DATABASE clause more than once

Cause: NEW DATABASE clause specified more than once

Action: Remove redundant NEW DATABASE clause and retry the operation.

RMAN-06926: User string with string privilege found in password file

RMAN-06926: User string with string privilege found in password file

Cause: Password file was used.

Action: Re-create the password file on the target platform using ORAPWD for the transported database.

RMAN-06925: BFILEs are used in the system, please redefine them in the transported database

RMAN-06925: BFILEs are used in the system, please redefine them in the transported database

Cause: BFILEs may or may not exist in the database. Automatically performed BFILE check failed because database was open read-only and could not allocate temporary space. This does not affect CONVERT DATABASE operation.

Action: Use dbms_tdb.check_external to perform BFILE check when the database is open in read or write mode.

RMAN-06924: BFILE string.string found in the database

RMAN-06924: BFILE string.string found in the database

Cause: A BFILE was found in the database.

Action: Redefine the BFILE in the transported database.

RMAN-06923: Directory string.string found in the database

RMAN-06923: Directory string.string found in the database

Cause: A directory object was found in the database.

Action: Redefine the directory in the transported database.

RMAN-06922: External table string.string found in the database

RMAN-06922: External table string.string found in the database

Cause: An external table was found in the database.

Action: Redefine the table in the transported database.

RMAN-06921: Convert database check failed

RMAN-06921: Convert database check failed

Cause: This database could not be transported because dbms_tdb.check_db returned FALSE.

Action: None

RMAN-06912: backup of spfile was cancelled

RMAN-06912: backup of spfile was cancelled

Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.

Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06911: only one PARALLEL or NOPARALLEL clause may be specified

RMAN-06911: only one PARALLEL or NOPARALLEL clause may be specified

Cause: Recover database was called with PARALLEL and NOPARALLEL option

Action: Call recover database with either just the PARALLEL or NOPARALLEL option.

RMAN-06910: can not invoke parallel recovery for test recovery

RMAN-06910: can not invoke parallel recovery for test recovery

Cause: Recover database was called with TEST and PARALLEL option

Action: Call recover database with either just the TEST or PARALLEL option

RMAN-06909: WARNING: parallelism require Enterprise Edition

RMAN-06909: WARNING: parallelism require Enterprise Edition

Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.

Action: None

RMAN-06908: WARNING: operation will not run in parallel on the allocated channels

RMAN-06908: WARNING: operation will not run in parallel on the allocated channels

Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.

Action: None

RMAN-06907: MINIMIZE LOAD option not allowed for the specified input files

RMAN-06907: MINIMIZE LOAD option not allowed for the specified input files

Cause: This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command.

Action: Remove the MINIMIZE LOAD option and retry the command.

RMAN-06906: backup of control file was cancelled

RMAN-06906: backup of control file was cancelled

Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.

Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06905: backup of backupset key number was cancelled

RMAN-06905: backup of backupset key number was cancelled

Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.

Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06904: backup of log thread number seq number lowscn string was cancelled

RMAN-06904: backup of log thread number seq number lowscn string was cancelled

Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.

Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06903: backup of datafile string was cancelled

RMAN-06903: backup of datafile string was cancelled

Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time.

Action: Run the BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option.

RMAN-06902: AS COMPRESSED BACKUPSET option cannot be used when backing up backupsets

RMAN-06902: AS COMPRESSED BACKUPSET option cannot be used when backing up backupsets

Cause: The backupset was specified with AS COMPRESSED BACKUPSET.

Action: Remove the AS COMPRESSED BACKUPSET option.

RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows

RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows

Cause: Informational message only.

Action: No action required.

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_ OUTPUT row

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_ OUTPUT row

Cause: The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT.

Action: Check the associated error messages. If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

RMAN-06899: updating recovery catalog with new database incarnation

RMAN-06899: updating recovery catalog with new database incarnation

Cause: The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a point-in-time recovery was done. RMAN has made the necessary updates to the recovery catalog.

Action: This is an informational message only.

RMAN-08503: piece handle=string comment=string

RMAN-08503: piece handle=string comment=string

Cause: This is an informational message only.

Action: No action is required.

RMAN-08501: output filename=string recid=string stamp=string

RMAN-08501: output filename=string recid=string stamp=string

Cause: This is an informational message only.

Action: No action is required.

RMAN-08500: channel string: sid=string devtype=string

RMAN-08500: channel string: sid=string devtype=string

Cause: This is an informational message only.

Action: No action is required.

RMAN-08306: channel string: datafile checking complete, elapsed time: string

RMAN-08306: channel string: datafile checking complete, elapsed time: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-08305: channel string: starting to check datafiles

RMAN-08305: channel string: starting to check datafiles

Cause: This is an informational message only.

Action: No action is required.

RMAN-08304: To change the internal database identifier, use DBNEWID Utility

RMAN-08304: To change the internal database identifier, use DBNEWID Utility

Cause: This is an informational message only.

Action: Transport script does not invoke DBNEWID Utility automatically.

RMAN-08303: To recompile all PL or SQL modules, run utlirp.sql and utlrp.sql on the target platform

RMAN-08303: To recompile all PL or SQL modules, run utlirp.sql and utlrp.sql on the target platform

Cause: This is an informational message only.

Action: Transport script invokes utlirp.sql and utlrp.sql.

RMAN-08302: Run RMAN script string on target platform to convert datafiles

RMAN-08302: Run RMAN script string on target platform to convert datafiles

Cause: This is an informational message only.

Action: No action is required.

RMAN-08301: Edit init.ora file string. This PFILE will be used to create the database on the target platform

RMAN-08301: Edit init.ora file string. This PFILE will be used to create the database on the target platform

Cause: This is an informational message only.

Action: No action is required.

RMAN-08300: Run SQL script string on the target platform to create database

RMAN-08300: Run SQL script string on the target platform to create database

Cause: This is an informational message only.

Action: No action is required.

RMAN-08190: validate found one or more corrupt blocks, see trace file for details

RMAN-08190: validate found one or more corrupt blocks, see trace file for details

Cause: Backup validate found that one or more blocks were corrupt in the specified datafiles.

Action: See trace file for details on the corrupted blocks. Repair them at your earliest convenience.