RMAN-6026 RMAN-6023 During RESTORE Operation

Problem Description

-------------------

You are attempting to restore a database using Oracle Recovery

Manager (RMAN) using a 'set until time' parameter to do a point-in-time

Recovery

Run {

Set until time = '09-JUN-2000:10:30:00';

Allocate channel x type disk;

Restore database;

Recover database;

}

However, this command fails with the following error stack

RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore

...

A 'list backupset of database' command shows there to be multiple backups

Of these files available.

Solution Description

--------------------

You have issued a 'resetlogs' prior to the last backup but before the 'Until

Time' clause in the RMAN script.

For instance,

- the last BACKUP taken of the database was June 8, 2000.

- you opened the database with RESETLOGS On June 9, at 9:08 AM,

- Then, do to complications, you decide to restore the database to a point in time on June 9, 10:30 AM.

Because you cannot roll forward through the resetlogs, RMAN cannot find any legitimate

Backups to restore from within this incarnation.

O The solution is to reset database incarnation to previous incarnation and

Set the 'until time' clause to a time before the resetlogs.

Explanation

-----------

You need to check the incarnation of the database

Rman>list incarnation of database;

RMAN-03022: compiling command: list

List of Database Incarnations

DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time

------- ------- ------------------------------ ---------------- --- ---------- ----------

1 2 <backup name> 4094805351 NO 159907 28-apr-2000:10:24:43

1 461 <backup name> 4094805351 NO 220532 09-jun-2000:08:22:08

1 521 <backup name> 4094805351 YES 220693 09-jun-2000:09:08:20

If the current incarnation reset time falls between the last backup and

The time specified for 'Set Time,' then the recovery catalog acknowledges

That there are no backups that match the time criteria specified, and errors

Out with RMAN-6023.

Search Words

------------

BACKUP, COPY, RECOVER, TARGETS

REFERENCES

DBRECOVER Recovery Options

For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.

When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.