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. This is an informational message.
Action: No action required.
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. This is an informational message.
Action: No action required.
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. This is an informational message.
Action: No action required.
RMAN-06175: deleted script: string
Cause: A DELETE SCRIPT command was executed.
Action: No action required.
RMAN-06174: not connected to auxiliary database
Cause: A auxiliary command was issued but no connection to an auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.
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-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 the 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 controlfile copy. It may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.
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-06170: no controlfile 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 one 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-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 - file name is missing 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.