| RMAN Recovery failing with Incremental level 0 Backup [message #493963] |
Thu, 10 February 2011 11:39  |
Jagdeep
Messages: 15
Registered: August 2004
|
Junior Member |
|
|
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremetal level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Levle 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. I would really appreciate your quick inputs since we are in middle of recovery and trying to resolve if this is even doable. Please share with your views.
|
|
|
|
|
|
|
|
| Re: RMAN Recovery failing with Incremental level 0 Backup [message #493978 is a reply to message #493967] |
Thu, 10 February 2011 12:17  |
Jagdeep
Messages: 15
Registered: August 2004
|
Junior Member |
|
|
Michel,
Here is output of the the rman restore log:
channel c7: reading from backup piece K:\RMAN\PR1_DF_7BM282JA_1_1
ORA-19870: error reading backup piece K:\RMAN\PR1_DF_QPM1LK9R_1_1
ORA-19505: failed to identify file "K:\RMAN\PR1_DF_QPM1LK9R_1_1"ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-19870: error reading backup piece K:\RMAN\PR1_DF_R3M1M3VO_1_1
ORA-19505: failed to identify file "K:\RMAN\PR1_DF_R3M1M3VO_1_1"ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
channel c7: restored backup piece 1
piece handle=K:\RMAN\PR1_DF_7BM282JA_1_1 tag=TAG20110116T020100
channel c7: restore complete, elapsed time: 09:12:05
channel c6: restored backup piece 1
piece handle=K:\RMAN\PR1_DF_79M27VJK_1_1 tag=TAG20110116T020100
channel c6: restore complete, elapsed time: 09:30:30
channel c5: restored backup piece 1
piece handle=K:\RMAN\PR1_DF_6TM27H7B_1_1 tag=TAG20110116T020100
channel c5: restore complete, elapsed time: 09:30:55
channel c3: restored backup piece 1
piece handle=K:\RMAN\PR1_DF_70M27H7S_1_1 tag=TAG20110116T020100
channel c3: restore complete, elapsed time: 09:30:57
channel c4: restored backup piece 1
piece handle=K:\RMAN\PR1_DF_6UM27H7J_1_1 tag=TAG20110116T020100
channel c4: restore complete, elapsed time: 09:39:52
failover to previous backup
creating datafile fno=1 name=G:\ORACLE\PR1\SYSTEM.DATA1
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
released channel: c9
released channel: c10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/10/2011 03:30:03
ORA-01180: can not create datafile 1
ORA-01110: data file 1: 'G:\ORACLE\PR1\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
Recovery Manager complete.
If you see it failed to identify two backup pieces. When I inquired about those pieces, I found those to be of 1/9. I don;t know why it requires the earlier backups. Please comment.
Regards.
Jagdeep
|
|
|
|
|
|
| Re: RMAN Recovery failing with Incremental level 0 Backup [message #493982 is a reply to message #493980] |
Thu, 10 February 2011 12:41 |
Jagdeep
Messages: 15
Registered: August 2004
|
Junior Member |
|
|
Here it is:
RMAN> connect target /
connected to target database: PR1 (DBID=819047839, not open)
RMAN> report need backup database;
using target database control file instead of recovery catalog
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of files with less than 1 redundant backups
File #bkps Name
---- ----- -----------------------------------------------------
RMAN>RMAN> connect target /
connected to target database: PR1 (DBID=819047839, not open)
RMAN> report need backup database;
using target database control file instead of recovery catalog
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of files with less than 1 redundant backups
File #bkps Name
---- ----- -----------------------------------------------------
RMAN>
|
|
|
|
|
|
|
|
|
|
|
|
| Re: RMAN Recovery failing with Incremental level 0 Backup [message #493991 is a reply to message #493990] |
Thu, 10 February 2011 14:09 |
Jagdeep
Messages: 15
Registered: August 2004
|
Junior Member |
|
|
Following is list of control files on 1/16th and we did restore controlfile from PR1_DF_7JM28J4B_1_1 backupset as following and this is the one which is marked for level 0. We can restore the one which is the last one in the day and see if that works..What do you suggest..?
run{
ALLOCATE CHANNEL c1 DEVICE TYPE DISK FORMAT 'k:\rman\%F';
restore controlfile from 'k:\rman\PR1_DF_7JM28J4B_1_1';
}
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7364 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7364 Status: AVAILABLE Compressed: NO Tag: TAG20110116T000034
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_6PM27A52_1_1
Control File Included: Ckp SCN: 5339854689 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7368 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7368 Status: AVAILABLE Compressed: NO Tag: TAG20110116T020128
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_6VM27H7O_1_1
Control File Included: Ckp SCN: 5343218683 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7372 Full 34.33M DISK 00:00:03 16-JAN-11
BP Key: 7372 Status: AVAILABLE Compressed: NO Tag: TAG20110116T040041
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_74M27O79_1_1
Control File Included: Ckp SCN: 5344357515 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7376 Full 34.33M DISK 00:00:03 16-JAN-11
BP Key: 7376 Status: AVAILABLE Compressed: NO Tag: TAG20110116T060024
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_78M27V7O_1_1
Control File Included: Ckp SCN: 5344614255 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7382 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7382 Status: AVAILABLE Compressed: NO Tag: TAG20110116T080017
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_7EM2868H_1_1
Control File Included: Ckp SCN: 5344663895 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7385 Full 34.33M DISK 00:00:01 16-JAN-11
BP Key: 7385 Status: AVAILABLE Compressed: NO Tag: TAG20110116T100012
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_7HM28D9C_1_1
Control File Included: Ckp SCN: 5344695057 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7388 Incr 0 4.19M DISK 00:00:02 16-JAN-11
BP Key: 7388 Status: AVAILABLE Compressed: YES Tag: TAG20110116T020100
Piece Name: K:\RMAN\PR1_DF_7JM28J4B_1_1
Control File Included: Ckp SCN: 5344896735 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7394 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7394 Status: AVAILABLE Compressed: NO Tag: TAG20110116T120030
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_7OM28KAU_1_1
Control File Included: Ckp SCN: 5344902748 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7398 Full 34.33M DISK 00:00:01 16-JAN-11
BP Key: 7398 Status: AVAILABLE Compressed: NO Tag: TAG20110116T140015
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_7SM28RBG_1_1
Control File Included: Ckp SCN: 5345049943 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7400 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7400 Status: AVAILABLE Compressed: NO Tag: TAG20110116T154211
Piece Name: K:\RMAN\PR1_CF_7TM291AJ_1_1
Control File Included: Ckp SCN: 5345082545 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7404 Full 34.33M DISK 00:00:01 16-JAN-11
BP Key: 7404 Status: AVAILABLE Compressed: NO Tag: TAG20110116T180016
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_81M299DH_1_1
Control File Included: Ckp SCN: 5345193521 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7408 Full 34.33M DISK 00:00:01 16-JAN-11
BP Key: 7408 Status: AVAILABLE Compressed: NO Tag: TAG20110116T200020
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_85M29GEK_1_1
Control File Included: Ckp SCN: 5345403495 Ckp time: 16-JAN-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7412 Full 34.33M DISK 00:00:02 16-JAN-11
BP Key: 7412 Status: AVAILABLE Compressed: NO Tag: TAG20110116T220023
Piece Name: K:\RMAN_ARCHIVES\PR1_CF_89M29NFN_1_1
Control File Included: Ckp SCN: 5345636060 Ckp time: 16-JAN-11[Updated on: Thu, 10 February 2011 14:11] by Moderator Report message to a moderator |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
