RMAN-06147: no obsolete backups found
Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness. This is an informational message.
Action: No action required.
Category Archives: RMAN Database Error Messages
RMAN-06146: changes found for file number beyond offline SCN
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-06145: controlfile is not current – obsolete file list may be incomplete
RMAN-06145: controlfile 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. This is an informational message.
Action: No action required. To ensure a complete report of obsolete backups, mount a current control file.
RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION
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-06143: LIKE may only be specified with COPY
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-06142: DEVICE TYPE may only be specified with LIST BACKUP
RMAN-06142: DEVICE TYPE may only be specified with LIST BACKUP
Cause: The DEVICE TYPE option was specified with a LIST COPY, LIST INCARNATION, CROSSCHECK, or DELETE EXPIRED command. This is not permitted because only backup sets may reside on different types of devices and CROSSCHECK and DELETE EXPIRED commands must use the same device type as was specified in the ALLOCATE CHANNEL FOR MAINTENANCE/DELETE command.
Action: Remove the DEVICE TYPE option and re-run the command.
RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE
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-06140: cannot specify TAG option with LIST INCARNATION
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-06139: WARNING: controlfile is not current for REPORT SCHEMA
RMAN-06139: WARNING: controlfile 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-06138: controlfile not mounted – must specify AT clause with REPORT command
RMAN-06138: controlfile 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.