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.
Category Archives: RMAN Database Error Messages
RMAN-06167: already connected
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-06166: datafile string cannot be recovered
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-06165: datafile string is too old to recover, restore a more recent copy
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-06164: no channel of required type allocated to recover datafile number
RMAN-06164: 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-06163: some datafiles cannot be recovered, aborting the RECOVER command
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: Refer to the accompanying messages.
RMAN-06162: sql statement: string
RMAN-06162: sql statement: string
Cause: This is the SQL statement about to be executed for a SQL command. This is an informational message.
Action: No action required.
RMAN-06161: error when inspecting auxiliary filename: string
RMAN-06161: error when inspecting auxiliary filename: string
Cause: This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary file name if it is wrong via the SET AUXNAME command.
RMAN-06160: no backup pieces found for backup set key: number
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-06159: error while looking up backup set
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.