06000-06429: SQL*Net Messages

ORA-06165: datafile name 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.

ORA-06166: datafile name 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.

ORA-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.

ORA-06168: no backup pieces with this tag found: name

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.

ORA-06169: could not read file header for datafile %s error reason %s

Cause: The specified datafile could not be accessed. The reason codes are:

1 - filename is MISSINGxx in the controlfile
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 - controlfile 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.

ORA-06170: no controlfile copy found with offline range recid num stamp name datafile name

Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current controlfile and no controlfile copy with the record could be accessed. At least 1 controlfile 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 controlfile copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.

ORA-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.

ORA-06172: not connected to recovery catalog database

Cause: A command was issued but no connection to the recovery catalog database has been established.

Action: Issue a CONNECT RCVCAT command to connect to the recovery catalog database. If you are not have a recovery catalog, then you must use the NOCATALOG option when starting RMAN.

ORA-06173: no set newname command has been issued for datafile name when restore clone

Cause: Clone type was specified for the controlfile, but no SET NEWNAME command has been previously issued for a datafile.

Issue SET NEWNAME command for every datafile in the recovery set.

---