Hi,
I'm dealing right now with database restore and I have been surprised by RMAN (not a first time).
I have limited space for archivelog so I decide to use recover database delete archive maxsize 2G
but I got a error
RMAN-06560: WARNING: backup set with key 4452 will be read 2 times
RMAN-06560: WARNING: backup set with key 4456 will be read 2 times
RMAN-06560: WARNING: backup set with key 4460 will be read 2 times
available space of 2406169 kb needed to avoid reading the backup set multiple times
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/webpr/datafile/system.273.689011611'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/09/2009 10:04:42
RMAN-06561: available space must be larger than 1489217 kb
I was really surprised why ?
And I found a root cause - backup set number are in different order then archive logs in them
ex.
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
4446 579.29M DISK 00:00:00 07-JUN-09
BP Key: 8873 Status: AVAILABLE Compressed: YES Tag: TAG20090607T230016
Piece Name: /Scratch/backup/production/bck_xxxxx_12591_1__prod_totape
List of Archived Logs in backup set 4446
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 3078 10640624851 07-JUN-09 10640624930 07-JUN-09
1 3079 10640624930 07-JUN-09 10640625010 07-JUN-09
1 3080 10640625010 07-JUN-09 10640625088 07-JUN-09
1 3081 10640625088 07-JUN-09 10640625171 07-JUN-09
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
4463 588.83M DISK 00:00:00 07-JUN-09
BP Key: 8960 Status: AVAILABLE Compressed: YES Tag: TAG20090607T230016
Piece Name: /Scratch/backup/production/bck_xxxxx_12590_1__prod_totape
List of Archived Logs in backup set 4463
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 2984 10633864777 06-JUN-09 10640579082 07-JUN-09
1 2985 10640579082 07-JUN-09 10640579298 07-JUN-09
1 2986 10640579298 07-JUN-09 10640579480 07-JUN-09
1 2987 10640579480 07-JUN-09 10640580301 07-JUN-09
1 2988 10640580301 07-JUN-09 10640580517 07-JUN-09
1 2989 10640580517 07-JUN-09 10640582425 07-JUN-09
1 2990 10640582425 07-JUN-09 10640582632 07-JUN-09
1 2991 10640582632 07-JUN-09 10640583492 07-JUN-09
1 2992 10640583492 07-JUN-09 10640584853 07-JUN-09
1 2993 10640584853 07-JUN-09 10640584987 07-JUN-09
1 2994 10640584987 07-JUN-09 10640585071 07-JUN-09
And RMAN decide to restore first a archivelog from BS with lower number - apply and delete them and then restore other archivelogs.
Hmmm I don't have a other db here but I was always thinking that RMAN is dealing with SEQ# number not a BS number.
Is any one had similar problem ?
Now I'm going to recheck a backup script.
My version is 10.2.0.4 on Linux
regards,
Marcin Przepiorowski
http://oracleprof.blogspot.com/