RMAN Error Codes 6000-6999

General compilation

6000-6999

RMAN-06000

could not open recovery manager library file: string
Cause:The "recover.bsq" file could not be opened.
Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file.

RMAN-06001

error parsing job step library
Cause:A syntax error was encountered while parsing "recover.bsq".
Action: Ensure that the correct version of the file is installed and that it has not been modified in any way.

RMAN-06002

command not allowed when not connected to a recovery catalog
Cause:A command that is allowed only when a recovery catalog connect string was supplied was attempted.
Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the CATALOG parameter.

RMAN-06003

ORACLE error from target database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06004

ORACLE error from recovery catalog database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06005

connected to target database: string (DBID=string)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06006

connected to target database: string (not mounted)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06007

target database not mounted and db_name not set in init.ora
Cause:The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter.
Action: MOUNT the target database, or add the DB_NAME parameter to its "init.ora" and restart the instance.

RMAN-06008

connected to recovery catalog database
Cause:This is an informational message only.
Action: No action is required.

RMAN-06009

using target database control file instead of recovery catalog
Cause:This is an informational message only.
Action: No action is required.

RMAN-06010

error while looking up datafile: string
Cause:An error occurred while looking up the specified datafile in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06011

invalid level specified: number
Cause:An invalid incremental backup level was specified.
Action: Incremental backup level must be between 0 and 4.

RMAN-06012

channel: string not allocated
Cause:A RELEASE or SETLIMIT command was found for a channel identifier that was not yet allocated.
Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command.

RMAN-06013

duplicate channel identifier found: string
Cause:A channel identifier was reused without first releasing the channel.
Action: Add a RELEASE CHANNEL command.

RMAN-06014

command not implemented yet: string
Cause:Not all commands are implemented for the beta release.
Action: Avoid using the command.

RMAN-06015

error while looking up datafile copy name: string
Cause:An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafilevopy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06016

duplicate backup operand specified: string
Cause:The specified operand appears more than once in the same backup specifier or backup command.
Action: Delete the duplicated operand.

RMAN-06017

initialization of parser failed
Cause:The parser package initialization routine returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06018

duplicate operand specified in backup specification: string
Cause:A backup specification operand appears more than once in a backup specification.
Action: Delete the duplicate operand.

RMAN-06019

could not translate tablespace name "string"
Cause:An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06020

connected to auxiliary database (not started)
Cause:This is an informational message only.
Action: No action is required.

RMAN-06021

FROM DATAFILECCOPY/BACKUPSET may not be specified with archive logs
Cause:The FROM DATAFILECCOPY/BACKUPSET option applies only to datafile and control file restores.
Action: Use this option only for datafile and control file restores.

RMAN-06022

invalid level specified for image copy: number
Cause:An invalid incremental backup level was specified for an image copy.
Action: Incremental backup level must be 0 for image copies.

RMAN-06023

no backup or copy of datafile number found to restore
Cause:A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06024

no backup or copy of the control file found to restore
Cause:A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06025

no backup of log thread number seq number lowscn string found to restore
Cause:An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06026

some targets not found - aborting restore
Cause:Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.

RMAN-06027

no archive logs found that match specification
Cause:An archive log record specifier did not match any archive logs in the recovery catalog.
Action: Resubmit the command with a different archive log record specifier. The rman LIST command can be used to display all archive logs that Recovery Manager knows about.

RMAN-06028

duplicate operand specified in restore specification: string
Cause:The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE, CHECK READONLY or DB_UNIQUE_NAME option was specified more than once in the restore command or in one of the restore specifications.
Action: Correct and resubmit the comand.

RMAN-06029

the control file may be included only in a datafile backup set
Cause:The "include current/standby control file" option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06030

the DELETE [ALL] INPUT option may not be used with a datafile backup set
Cause:The DELETE [ALL] INPUT option was specified for a backup that contains the current control file or datafiles.
Action: Remove the option and resubmit the command.

RMAN-06031

could not translate database keyword
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-06032

at least 1 channel of TYPE DISK must be allocated to execute a COPY command
Cause:No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command.

RMAN-06033

channel string not allocated
Cause:An rman command requests a specific channel, but the requested channel has not been allocated.
Action: ALLOCATE the channel, or correct the channel identifier.

RMAN-06034

at least 1 channel must be allocated to execute this command
Cause:No channels were allocated.
Action: ALLOCATE a channel.

RMAN-06035

wrong version of recover.bsq, expecting string, found string
Cause:The "recover.bsq" file is incompatible with the RMAN executable.
Action: Install the correct version of recover.bsq.

RMAN-06036

datafile number is already restored to file string
Cause:A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.
Action: None - this is an informational message.

RMAN-06038

recovery catalog package detected an error
Cause:A call to dbms_rcvman returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06039

no set newname command has been issued for datafile number
Cause:A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued.
Action: Correct and resubmit the SWITCH command.

RMAN-06040

control file is already restored to file string
Cause:The best candidate control file for restoration is the one that is named in the RESTORE CONTROLFILE command, hence no action need be taken.
Action: None - this is an informational message.

RMAN-06041

cannot switch file number to copy of file number
Cause:An attempt was made to switch a datafile to a copy of a different datafile.
Action: Correct and resubmit the SWITCH command.

RMAN-06042

PLUS ARCHIVELOG option is not supported with non-datafile backups
Cause:The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup.
Action: Remove the PLUS ARCHIVELOG operand and re-enter the command.

RMAN-06043

TAG option not supported for archive log copies
Cause:The tag option was supplied but does not apply to this type of copy.
Action: Remove the TAG operand and re-enter the command

RMAN-06045

LEVEL option not supported for archive log or current/standby control file copies
Cause:The LEVEL option was supplied but does not apply to this type of copy.
Action: Remove the LEVEL operand and re-enter the command.

RMAN-06046

archive log name: string
Cause:An error occurred while translating an archive log name to its recovery catalog recid/timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06047

duplicate datafile number specified for restoration from copy
Cause:The indicated datafile was specified more than once in the same restore command.
Action: Correct and resubmit the RESTORE command.

RMAN-06048

duplicate control file specified for restoration from copy
Cause:The control file was specified more than once in the same RESTORE command.
Action: Correct and resubmit the RESTORE command.

RMAN-06049

CHECK LOGICAL option not supported for archive log or current/standby control file copies
Cause:The check logical option was supplied but does not apply to this type of copy.
Action: Remove the CHECK LOGICAL operand and re-enter the command

RMAN-06050

archive log thread number sequence number is already on disk as file string
Cause:An archive log which was requested to be restored (either explicitely or via a range specification) does not need to be restored because it already exists on disk.
Action: None - this is an informational message

RMAN-06051

DELETE INPUT option not implemented yet
Cause:This option was specified in a backup specification.
Action: Remove the DELETE INPUT option.

RMAN-06052

no parent backup or copy of datafile number found
Cause:An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.
Action: This is an informational message only.

RMAN-06053

unable to perform media recovery because of missing log
Cause:This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.
Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.

RMAN-06054

media recovery requesting unknown log: thread string seq string lowscn string
Cause:Media recovery is requesting a log whose existance is not recorded in the recovery catalog or control file.
Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command.

RMAN-06055

could not find log sequence string thread string
Cause:A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.
Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support.

RMAN-06056

could not access datafile number
Cause:A backup or copy could not proceed because the datafile header could not be read or the header was not valid.
Action: Make the datafile accessible or skip it.

RMAN-06057

a standby control file cannot be included along with a current control file
Cause:"current controlfile" was specified along with "standby controlfile".
Action: Remove "current controlfile" or "standby controlfile" from backup specification.

RMAN-06058

a current control file cannot be included along with a standby control file
Cause:"standby controlfile" was specified along with "current controlfile".
Action: Remove "standby controlfile" or "current controlfile" from backup specification.

RMAN-06059

expected archived log not found, lost of archived log compromises recoverability
Cause:The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06060

WARNING: skipping datafile compromises tablespace string recoverability
Cause:SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafiles during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archive logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE [DROP].
Action: If there is no backup of skipped datafiles and the tablespace has to be recoverable without ALL archive logs since datafile creation, then you should make these datafiles available for backup.

RMAN-06061

WARNING: skipping archivelog compromises recoverability
Cause:SKIP INACCESSIBLE option resulted in skipping archivelogs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the repository.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06062

can not backup SPFILE because the instance was not started with SPFILE
Cause:A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE or modify the command.

RMAN-06063

DBID is not found in the recovery catalog
Cause:DBID is not found in the recovery catalog.
Action: Verify that the DBID is correct and restart the command.

RMAN-06064

creating datafile fno=string name=string
Cause:RESTORE/RECOVER command was issued and there were no backup available for the datafile.
Action: This is an informational message only.

RMAN-06065

The backup operand [string] conflicts with another specified operand.
Cause:The user attempted to use two (or more) conflicting operands within the same statement.
Action: Remove one or both of the conflicting operands.

RMAN-06066

the target database must be mounted when issuing a RECOVER command
Cause:A RECOVER command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06067

RECOVER DATABASE required with a backup or created control file
Cause:The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.
Action: Use the RECOVER DATABASE command to perform the recovery.

RMAN-06068

recovery aborted because of missing datafiles
Cause:This error should be accompanied by one or more instances of message ORA-06094.
Action: Refer to message ORA-06094.

RMAN-06069

the filename for datafile string is missing in the control file
Cause:Media recovery of a backup control file added this datafile to the control file, but it does not set the filename because that is unsafe.
Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.

RMAN-06070

DBWR could not identify datafile string
Cause:DBWR could not find the specified datafile.
Action: Ensure that the datafile exists and is accessible.

RMAN-06071

could not open datafile string
Cause:An error was encountered when trying to open the specified datafile.
Action: Ensure that the datafile exists and is accessible.

RMAN-06073

file header is corrupt for datafile string
Cause:ORACLE detected a corruption in the file header. A media failure has probably occurred.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06074

file string is not an ORACLE datafile
Cause:The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06075

datafile string does not belong to this database
Cause:The file header indicates that this file belongs to some other ORACLE database.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06076

datafile string contains wrong datafile
Cause:The datafile header indicates the file contains a different datafile number.
Action: RESTORE the datafile, and then retry the RECOVER command.

RMAN-06077

datafile string is a different version than contained in the control file
Cause:The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.
Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.

RMAN-06078

the control file is older than datafile string
Cause:The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup controlfile which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such controlfiles are marked as backups.
Action: RESTORE a control file and perform RECOVER DATABASE.

RMAN-06079

database must be mounted to perform recovery
Cause:A RECOVER command was issued, but the target database is not mounted.
Action: Issue ALTER DATABASE MOUNT.

RMAN-06080

SWITCH required for datafile string
Cause:The control file record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to updated the control file before doing RECOVER.
Action: Issue SWITCH command then retry RECOVER.

RMAN-06081

error reading datafile header for datafile string, code string
Cause:X$KCVFH returned the specified code in the hxerr column when it was queried for the specified datafile.
Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support.

RMAN-06082

datafile copy tag string is ambiguous
Cause:The specified tag refers to multiple datafile copies belonging to different datafiles.
Action: Specify the datafile copy by filename rather than by tag.

RMAN-06083

error when loading stored script string
Cause:The recovery catalog database returned an error. This error explains the cause of the problem.
Action: Correct the problem and retry.

RMAN-06084

the target database may not be mounted when issuing REPLICATE
Cause:A REPLICATE command was issued, but the target database is already mounted.
Action: dismount the target database control file by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager.

RMAN-06085

must use SET NEWNAME command to restore datafile string
Cause:A RESTORE command for the specified datafile could not find a destination name for the specified datafile.
Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file.

RMAN-06086

offline files may only be skipped in a datafile backup set
Cause:The SKIP OFFLINE option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06087

read-only files may only be skipped in a datafile backup set
Cause:The SKIP READONLY option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.

RMAN-06088

datafile copy string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06089

archived log string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06090

error while looking up control file copy: string
Cause:An error occurred while looking up the specified control file copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the control file copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06091

no channel allocated for maintenance (of an appropriate type)
Cause:A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type.
Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands. Proxy copies require a non-DISK channel.

RMAN-06092

error while looking up backup piece
Cause:An error occurred while looking up the specified backup piece in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06093

recovery catalog contains obsolete version of datafile string
Cause:The specified datafile number was dropped and then reused. The control file mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version.
Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Customer Support.

RMAN-06094

datafile string must be restored
Cause:A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the control file, and cannot be found on disk.
Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER.

RMAN-06095

a backup control file must be restored to recover datafile string
Cause:The controfile currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the point-in-time being recovered to.
Action: Restore the control file, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no control file can be restored, then you should issue a CREATE CONTROLFILE command.

RMAN-06096

SWITCH required for newname of datafile string to take effect
Cause:A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command.
Action: Issue a SWITCH command to make the newname take effect before doing RECOVER.

RMAN-06098

the target database must be mounted when issuing a BACKUP command
Cause:A BACKUP command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06099

error occurred in source file: string, line: number
Cause:See accompanying error
Action: See accompanying error

RMAN-06100

no channel to restore a backup or copy of datafile number
Cause:A datafile, tablespace, or database restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06101

no channel to restore a backup or copy of the control file
Cause:A control file restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06102

no channel to restore a backup or copy of log thread number seq number lowscn string
Cause:An archive log restore restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.

RMAN-06103

duplicate qualifier found in REPORT command: string
Cause:The indicated qualifier appears more than once in a REPORT qualifier list.
Action: delete the duplicate qualifier

RMAN-06105

duplicate qualifier found in LIST command: string
Cause:The indicated qualifier appears more than once in a LIST qualifier list.
Action: delete the duplicate qualifier

RMAN-06106

this command requires that target database be mounted
Cause:A command was issued that requires the target database to be mounted, but the target database is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06107

WARNING: control file is not current for REPORT NEED BACKUP DAYS
Cause:The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted.
Action: No action is required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output.

RMAN-06108

changed datafile copy unvailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06109

changed archive log unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06110

changed control file copy unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06111

changed backup piece unavailable
Cause:This is an informational message only.
Action: No action is required.

RMAN-06112

changed datafile copy available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06113

changed archive log available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06114

changed control file copy available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06115

changed backup piece available
Cause:This is an informational message only.
Action: No action is required.

RMAN-06116

cannot crosscheck unavailable object
Cause:An attempt was made to crosscheck an object which is unavailable.
Action: Make object available and try again or don't crosscheck object.

RMAN-06117

cannot do DELETE EXPIRED on an object which is not expired
Cause:An attempte was made to DELETE EXPIRED an object which is not expired.
Action: Remove EXPIRED keyword, crosscheck object, or don't delete object.

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 ;(where is the SCN displayed in the message) RESTORE CONTROLFILE;

RMAN-06119

uncataloged datafile copy
Cause:This is an informational message only.
Action: No action is required.

RMAN-06120

uncataloged archive log
Cause:This is an informational message only.
Action: No action is required.

RMAN-06121

uncataloged control file copy
Cause:This is an informational message only.
Action: No action is required.

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-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-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-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-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-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-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-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-06131

skip offline/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/readonly status.
Action: Remove the skip option or mount a current control file on the target database.

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-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-06134

host command complete
Cause:An operating system command has completed.
Action: None - this is an informational message.

RMAN-06135

error executing host command: string
Cause:A host command returned a non-zero return code.
Action: Correct the offending command.

RMAN-06136

ORACLE error from auxiliary database: string
Cause:This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.

RMAN-06137

must have recovery catalog for REPORT SCHEMA AT TIME
Cause:A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause.

RMAN-06138

control file not mounted - must specify AT clause with REPORT command
Cause:A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database.
Action: Use a recovery catalog or mount a control file at the target database.

RMAN-06139

WARNING: control file is not current for REPORT SCHEMA
Cause:A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current.
Action: Use a recovery catalog or mount a current control file.

RMAN-06140

cannot specify TAG option with LIST INCARNATION
Cause:The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.

RMAN-06141

cannot specify ARCHIVELOG LIKE option with RESTORE
Cause:The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk.
Action: Remove the ARCHIVELOG LIKE option and re-run the command.

RMAN-06142

DEVICE TYPE cannot be specified with this command
Cause:The DEVICE TYPE option was specified with a command that does not support it.
Action: Remove the DEVICE TYPE option and re-run the command.

RMAN-06143

LIKE may only be specified with COPY
Cause:The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.

RMAN-06144

FROM or UNTIL may not be specified with LIST INCARNATION
Cause:The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.

RMAN-06145

control file is not current - obsolete file list may be incomplete
Cause:A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file.

RMAN-06146

changes found for file number beyond offline SCN
Cause:A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.
Action: Mount a current control file or a backup control file.

RMAN-06147

no obsolete backups found
Cause:A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.
Action: None - this is an informational message.

RMAN-06148

redundancy count must be greater than zero
Cause:The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.

RMAN-06150

auxiliary name for datafile number set to: string
Cause:This message is issued in response to a CONFIGURE AUXNAME command.
Action: None - this is an informational message.

RMAN-06151

datafile string creation scn string
Cause:This is an informational message. It should be accompanied by other messages.
Action: none

RMAN-06153

validation failed for datafile copy
Cause:The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.

RMAN-06154

validation succeeded for datafile copy
Cause:The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.
Action: None - this is an informational message.

RMAN-06155

validation failed for control file copy
Cause:The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.

RMAN-06156

validation succeeded for control file copy
Cause:The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog.
Action: None - this is an informational message.

RMAN-06157

validation failed for archived log
Cause:The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired.
Action: None - this is an informational message.

RMAN-06158

validation succeeded for archived log
Cause:The CROSSCHECK ARCHIVELOG command determined that the archived log still matches its data.
Action: None - this is an informational message.

RMAN-06159

error while looking up backup set
Cause:An error occurred while looking up the specified backup set in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06160

no backup pieces found for backup set key: number
Cause:No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file.
Action: Specify an existing backup set.

RMAN-06161

error when inspecting auxiliary filename: string
Cause:This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary filename if it is wrong via the CONFIGURE AUXNAME command.

RMAN-06162

sql statement: string
Cause:This is the sql statement about to be executed for a SQL command.
Action: None, informational message only.

RMAN-06163

some datafiles cannot be recovered, aborting the RECOVER command
Cause:This message should be followed by one or more 6162 or 6164 messages.
Action: Check the accompanying errors.

RMAN-06164

WARNING: no channel of required type allocated to recover datafile number
Cause:A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.

RMAN-06165

datafile string is too old to recover, restore a more recent copy
Cause:The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.

RMAN-06166

datafile string cannot be recovered
Cause:Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.

RMAN-06167

already connected
Cause:a CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.

RMAN-06168

no backup pieces with this tag found: string
Cause:A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.

RMAN-06169

could not read file header for datafile string error reason string
Cause:The specified datafile could not be accessed. The reason codes are: 1 - filename is MISSINGxx in the control file 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - control file is not current
Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup.

RMAN-06170

no control file copy found with offline range recid string stamp string datafile string
Cause:This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the rc_controlfile_copy view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.

RMAN-06171

not connected to target database
Cause:A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.

RMAN-06172

no autobackup found or specified handle is not a valid copy or piece
Cause:A restore could not proceed because no autobackup was found or specified handle is not a valid copy or backup piece. In case of restore from autobackup, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or controflile copy. In may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.

RMAN-06173

no set newname command has been issued for datafile string when restore auxiliary
Cause:Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.

RMAN-06174

not connected to auxiliary database
Cause:An auxiliary command was issued but no connection to a auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.

RMAN-06175

deleted script: string
Cause:A DELETE SCRIPT command was executed.
Action: None, informational message only.

RMAN-06176

no recovery required; all files are readonly or offline
Cause:A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace.
Action: None, informational message only

RMAN-06177

restore not done; all files readonly, offline, or already restored
Cause:A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations.
Action: None, informational message only

RMAN-06178

datafile number not processed because file is offline
Cause:A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time.
Action: None, informational message only

RMAN-06179

datafile number not processed because file is read-only
Cause:A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time.
Action: None, informational message only

RMAN-06180

incremental backups require Enterprise Edition
Cause:A BACKUP command with INCREMENTAL LEVEL > 0 was specified.
Action: Use FULL, or INCREMENTAL LEVEL 0.

RMAN-06181

multiple channels require Enterprise Edition
Cause:Attempt to allocate more than 1 channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.

RMAN-06182

archive log larger than MAXSETSIZE: thread string seq string string
Cause:A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archive log is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.

RMAN-06183

datafile or datafile copy larger than MAXSETSIZE: file# string string
Cause:A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.

RMAN-06184

duplicate object in backup specifier: string string
Cause:A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.

RMAN-06185

Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required
Cause:This version of recovery manager was incompatible with the indicated database or the dbms_backup_restore package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. Otherwise, use a version of RMAN within the range specified in the error message.

RMAN-06186

PL/SQL package string.string version string in string database is too old
Cause:The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.

RMAN-06187

control file copy string not found or out of sync with catalog
Cause:The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.

RMAN-06188

cannot use command when connected to a mounted target database
Cause:An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.

RMAN-06189

current DBID number does not match target mounted database (number)
Cause:SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.

RMAN-06190

PL/SQL package string.string version string in string database is not current
Cause:RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb.

RMAN-06191

PL/SQL package string.string version string in string database is too new
Cause:RMAN detected an incompatible version of the specified package.
Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager.

RMAN-06192

maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb
Cause:Input size for MAXPIECESIZE or MAXSETSIZE was out of range.
Action: Specify a valid size and retry the command.

RMAN-06193

connected to target database (not started)
Cause:This is an informational message only.
Action: The database must be started before any other RMAN commands are issued.

RMAN-06194

target database instance not started
Cause:A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.

RMAN-06195

auxiliary database not started
Cause:A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.

RMAN-06196

Oracle instance started
Cause:A STARTUP command completed successfully.
Action: None, this is an informational message.

RMAN-06197

Total System Global Area string bytes
Cause:This is an informational message only.
Action: No action is required.

RMAN-06198

%-24s string bytes
Cause:This is an informational message only.
Action: No action is required.

RMAN-06199

database mounted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06200

Changed string objects to AVAILABLE status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06201

Deleted string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06202

Deleted string EXPIRED objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06203

Changed KEEP options for string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06204

Changed string objects to UNAVAILABLE status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06205

Uncataloged string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06206

Crosschecked string objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06207

WARNING: string objects could not be deleted for string channel(s) due
Cause:This is an informational message only.
Action: No action is required.

RMAN-06208

to mismatched status. Use CROSSCHECK command to fix status
Cause:This is an informational message only.
Action: No action is required.

RMAN-06209

List of failed objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06210

List of Mismatched objects
Cause:This is an informational message only.
Action: No action is required.

RMAN-06211

==========================
Cause:This is an informational message only.
Action: No action is required.

RMAN-06212

Object Type Filename/Handle
Cause:This is an informational message only.
Action: No action is required.

RMAN-06213

--------------- ---------------------------------------------------
Cause:This is an informational message only.
Action: No action is required.

RMAN-06214

%-15s string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06220

Creating automatic instance, with SID='string'
Cause:No connection to the auxiliary instance was provided, but the command requires an auxiliary instance.
Action: No action is required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection.

RMAN-06221

Removing automatic instance
Cause:RMAN is removing the automatic auxiliary instance that was created for this command.
Action: No action is required.

RMAN-06223

starting up automatic instance string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06224

Automatic instance created
Cause:This is an informational message only.
Action: No action is required.

RMAN-06225

shutting down automatic instance string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06226

Automatic instance removed
Cause:This is an informational message only.
Action: No action is required.

RMAN-06230

List of Stored Scripts in Recovery Catalog
Cause:This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script.
Action: No action is required.

RMAN-06246

List of Database Incarnations
Cause:This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: SCN of the most recent resetlogs operation. Reset Time: Time of the most recent resetlogs operation.
Action: No action is required.

RMAN-06250

Report of files that need backup due to unrecoverable operations
Cause:An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes.
Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice.

RMAN-06263

%-4s string string
Cause:This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery.
Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now.

RMAN-06270

Report of files whose recovery needs more than number days of archived logs
Cause:This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days' archived logs for recovery.
Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now.

RMAN-06274

Report of files that must be backed up to satisfy number days recovery window
Cause:This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS command for those files that must be backed up to satisfy specified retention policy.
Action: To satisfy specified recovery window for this datafile, take a new full or incremental backup now.

RMAN-06275

invalid number of days specified for report : string days
Cause:This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS or REPORT NEED BACKUP DAYS n command when an invalid number of days was specified in input command.
Action: The number of days specified in REPORT command must be greater than zero.

RMAN-06280

Report of obsolete backups and copies
Cause:This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command.
Action: Depending on your needs, you might need to take new backups.

RMAN-06290

Report of database schema
Cause:This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile and temporary file: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile/Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended
Action: No action is required.

RMAN-06300

Report of files with less than number redundant backups
Cause:This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery.
Action: Take another backup of the datafiles listed.

RMAN-06306

====================
Cause:This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup.
Action: No action is required.

RMAN-06378

List of Backup Sets
Cause:This message is issued in response to a LIST BACKUP command.
Action: No action is required.

RMAN-06400

database opened
Cause:This is an informational message only.
Action: No action is required.

RMAN-06401

database is already started
Cause:A STARTUP command without the FORCE option was issued, but the target database is already started.
Action: Use the FORCE option if you want to restart the database.

RMAN-06402

Oracle instance shut down
Cause:This is an informational message only.
Action: No action is required.

RMAN-06403

could not obtain a fully authorized session
Cause:The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem.
Action: Startup the database causing the problem.

RMAN-06404

database dismounted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06405

database closed
Cause:This is an informational message only.
Action: No action is required.

RMAN-06406

deleted archive log
Cause:This is an informational message only.
Action: No action is required.

RMAN-06407

auxiliary instance file string deleted
Cause:This is an informational message only.
Action: No action is required.

RMAN-06408

recovery catalog upgraded to version string
Cause:This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog 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 schema is not changed with each Oracle release.
Action: No action is required.

RMAN-06409

LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported
Cause:LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
Action: Remove LIKE clause from command.

RMAN-06410

cannot use command when channels are allocated
Cause:An attempt was made to issue a command that can be used only when there are no allocated channels.
Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.

RMAN-06411

backup copies setting out of range (1-4): number
Cause:An attempt was made to set backup copies to an invalid value.
Action: Use a value in the specified range.

RMAN-06412

no proxy copy channel found
Cause:A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores.

RMAN-06413

channel string does not support proxy copy
Cause:The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores.

RMAN-06414

target database COMPATIBLE option does not support proxy copy
Cause:PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.
Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter.

RMAN-06415

file string cannot be proxy backed up
Cause:The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file.

RMAN-06416

PROXY ONLY was specified and some files could not be proxy copied
Cause:PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files.

RMAN-06418

proxy incremental backups with level > 0 not supported
Cause:PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups.
Action: Remove one of the conflicting options.

RMAN-06419

file string cannot be proxy restored from handle string
Cause:The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle.
Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor.

RMAN-06420

some files could not be proxy restored - aborting restore
Cause:Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored.
Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from these proxy backups.

RMAN-06421

sent command to channel: string
Cause:This is an informational message only.
Action: No action is required.

RMAN-06422

no channels found for SEND command
Cause:No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated.
Action: Specify a different channel type or allocate a channel of the desired type.

RMAN-06423

requested limit of number exceeds vendor limit of number
Cause:A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.
Action: Specify a smaller backup piece limit.

RMAN-06424

error while looking up proxy copy
Cause:An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06425

Cause:This is an informational message only.
Action: No action is required.

RMAN-06426

RECOVERY_CATALOG_OWNER role must be granted to user string
Cause:The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.
Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.

RMAN-06427

recovery catalog already exists
Cause:The CREATE CATALOG command cannot be used when the recovery catalog already exists.
Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.

RMAN-06428

recovery catalog is not installed
Cause:A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.
Action: If you mis-typed the recovery catalog owner userid, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema. Alternatively, exit RMAN and connect without specifying a recovery catalog connection.

RMAN-06429

%s database is not compatible with this version of RMAN
Cause:The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.
Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.

RMAN-06430

recovery catalog userid cannot be SYS
Cause:A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.
Action: Specify a different userid in the CATALOG connect string.

RMAN-06431

recovery catalog created
Cause:This is an informational message issued by the CREATE CATALOG command.
Action: No action is required.

RMAN-06432

recovery catalog dropped
Cause:This is an informational message issued by the DROP CATALOG command.
Action: No action is required.

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:
- Lack of space in the recovery catalog database: allocate more space, use the DROP CATALOG command to remove any partially installed recovery catalog, and retry the command.
- Object already exists: This is caused by a partial recovery catalog installation. Use the DROP CATALOG command to remove the partially installed recovery catalog and retry the command.

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-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-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-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-06438