Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

RMAN-03002: failure of restore command at 04/05/2016 17:14:40 RMAN-06026: some targets not found - a

Noname123Apr 5 2016 — edited Apr 7 2016

I am cloning the database in another server using rman backup (to test the backup)

so far I have restored the controlfile successfully. When I attempted to restore

the datafiles and archivelogs it is giving error:

RMAN-03002: failure of restore command at 04/05/2016 17:14:40

RMAN-06026: some targets not found - aborting restore

RMAN-06023: no backup or copy of datafile 407 found to restore

RMAN-06023: no backup or copy of datafile 406 found to restore

RMAN-06023: no backup or copy of datafile 405 found to restore

RMAN-06023: no backup or copy of datafile 404 found to restore

Does that mean that my backup wasn't taken properly (invalid) ? Or the problem is something else?

Know that I have copied the backup directory to the target server and I have cataloged the backuppieces

in rman

The following is what I did:

[oratest5@erpappstest 11.2.0.3]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Tue Apr 5 17:14:30 2016

connected to target database: PROD (DBID=250231014, not open)

RMAN>

run {

set newname for datafile 1 to '/Stage/prod/db/apps_st/data/system01.dbf';

set newname for datafile 2 to '/Stage/prod/db/apps_st/data/system02.dbf';

set newname for datafile 3 to '/Stage/prod/db/apps_st/data/system03.dbf';

set newname for datafile 4 to '/Stage/prod/db/apps_st/data/system04.dbf';

set newname for datafile 5 to '/Stage/prod/db/apps_st/data/system05.dbf';

set newname for datafile 6 to '/Stage/prod/db/apps_st/data/ctxd01.dbf';

set newname for datafile 7 to '/Stage/prod/db/apps_st/data/owad01.dbf';

set newname for datafile 8 to '/Stage/prod/db/apps_st/data/a_queue02.dbf';

set newname for datafile 9 to '/Stage/prod/db/apps_st/data/odm.dbf';

set newname for datafile 10 to '/Stage/prod/db/apps_st/data/olap.dbf';

set newname for datafile 11 to '/Stage/prod/db/apps_st/data/sysaux01.dbf';

set newname for datafile 12 to '/Stage/prod/db/apps_st/data/apps_ts_tools01.dbf'

;

set newname for datafile 13 to '/Stage/prod/db/apps_st/data/system12.dbf';

set newname for datafile 14 to '/Stage/prod/db/apps_st/data/a_txn_data04.dbf';

set newname for datafile 15 to '/Stage/prod/db/apps_st/data/a_txn_ind06.dbf';

set newname for datafile 16 to '/Stage/prod/db/apps_st/data/a_ref03.dbf';

set newname for datafile 17 to '/Stage/prod/db/apps_st/data/a_int02.dbf';

set newname for datafile 18 to '/Stage/prod/db/apps_st/data/sysaux02.dbf';

set newname for datafile 19 to '/Stage/prod/db/apps_st/data/sysaux002.dbf';

set newname for datafile 20 to '/Stage/prod/db/apps_st/data/a_media02.dbf';

set newname for datafile 21 to '/Stage/prod/db/apps_st/data/a_txn_data05.dbf';

set newname for datafile 22 to '/Stage/prod/db/apps_st/data/TAS.DBF';

set newname for datafile 288 to '/Stage/prod/db/apps_st/data/system10.dbf';

set newname for datafile 295 to '/Stage/prod/db/apps_st/data/system06.dbf';

set newname for datafile 314 to '/Stage/prod/db/apps_st/data/portal01.dbf';

set newname for datafile 351 to '/Stage/prod/db/apps_st/data/system07.dbf';

set newname for datafile 352 to '/Stage/prod/db/apps_st/data/system09.dbf';

set newname for datafile 353 to '/Stage/prod/db/apps_st/data/system08.dbf';

set newname for datafile 354 to '/Stage/prod/db/apps_st/data/system11.dbf';

set newname for datafile 379 to '/Stage/prod/db/apps_st/data/undo01.dbf';

set newname for datafile 392 to '/Stage/prod/db/apps_st/data/a_txn_data01.dbf';

set newname for datafile 393 to '/Stage/prod/db/apps_st/data/a_txn_ind01.dbf';

set newname for datafile 394 to '/Stage/prod/db/apps_st/data/a_ref01.dbf';

set newname for datafile 395 to '/Stage/prod/db/apps_st/data/a_int01.dbf';

set newname for datafile 396 to '/Stage/prod/db/apps_st/data/a_summ01.dbf';

set newname for datafile 397 to '/Stage/prod/db/apps_st/data/a_nolog01.dbf';

set newname for datafile 398 to '/Stage/prod/db/apps_st/data/a_archive01.dbf';

set newname for datafile 399 to '/Stage/prod/db/apps_st/data/a_queue01.dbf';

set newname for datafile 400 to '/Stage/prod/db/apps_st/data/a_media01.dbf';

set newname for datafile 401 to '/Stage/prod/db/apps_st/data/a_txn_data02.dbf';

set newname for datafile 402 to '/Stage/prod/db/apps_st/data/a_txn_data03.dbf';

set newname for datafile 403 to '/Stage/prod/db/apps_st/data/a_txn_ind02.dbf';

set newname for datafile 404 to '/Stage/prod/db/apps_st/data/a_txn_ind03.dbf';

set newname for datafile 405 to '/Stage/prod/db/apps_st/data/a_txn_ind04.dbf';

set newname for datafile 406 to '/Stage/prod/db/apps_st/data/a_txn_ind05.dbf';

set newname for datafile 407 to '/Stage/prod/db/apps_st/data/a_ref02.dbf';

restore database;

switch datafile all;

}

executing command: SET NEWNAME

Starting restore at 05-APR-16

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=376 device type=DISK

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 04/05/2016 17:14:40

RMAN-06026: some targets not found - aborting restore

RMAN-06023: no backup or copy of datafile 407 found to restore

RMAN-06023: no backup or copy of datafile 406 found to restore

RMAN-06023: no backup or copy of datafile 405 found to restore

RMAN-06023: no backup or copy of datafile 404 found to restore

RMAN-06023: no backup or copy of datafile 403 found to restore

RMAN-06023: no backup or copy of datafile 402 found to restore

RMAN-06023: no backup or copy of datafile 401 found to restore

RMAN-06023: no backup or copy of datafile 400 found to restore

RMAN-06023: no backup or copy of datafile 399 found to restore

RMAN-06023: no backup or copy of datafile 398 found to restore

RMAN-06023: no backup or copy of datafile 397 found to restore

RMAN-06023: no backup or copy of datafile 396 found to restore

RMAN-06023: no backup or copy of datafile 395 found to restore

RMAN-06023: no backup or copy of datafile 394 found to restore

RMAN-06023: no backup or copy of datafile 393 found to restore

RMAN-06023: no backup or copy of datafile 392 found to restore

RMAN-06023: no backup or copy of datafile 379 found to restore

RMAN-06023: no backup or copy of datafile 354 found to restore

RMAN-06023: no backup or copy of datafile 353 found to restore

RMAN-06023: no backup or copy of datafile 352 found to restore

RMAN-06023: no backup or copy of datafile 351 found to restore

RMAN-06023: no backup or copy of datafile 314 found to restore

RMAN-06023: no backup or copy of datafile 295 found to restore

RMAN-06023: no backup or copy of datafile 288 found to restore

RMAN-06023: no backup or copy of datafile 18 found to restore

RMAN-06023: no backup or copy of datafile 17 found to restore

RMAN-06023: no backup or copy of datafile 16 found to restore

RMAN-06023: no backup or copy of datafile 15 found to restore

RMAN-06023: no backup or copy of datafile 14 found to restore

RMAN-06023: no backup or copy of datafile 13 found to restore

RMAN-06023: no backup or copy of datafile 12 found to restore

RMAN-06023: no backup or copy of datafile 11 found to restore

RMAN-06023: no backup or copy of datafile 10 found to restore

RMAN-06023: no backup or copy of datafile 9 found to restore

RMAN-06023: no backup or copy of datafile 8 found to 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

In order to investigate whether the backup was invalid, I tried to use "restore database validate" commands on the production to check if the backup was valid but it is causing some performance issue on the

system. So I had to quit validating . I can't know now whether the problem is from the backup or not...

This post has been answered by oraLaro on Apr 5 2016

Jump to Answer

Locked Post

New comments cannot be posted to this locked post.

Locked on May 5 2016

Added on Apr 5 2016

#performance-availability, #recovery-manager-rman

16 comments

12,687 views