RMAN & UNTIL SCN
Hello,
How do i know what SEQUENCE and THREAD to put into the command, is there any query to run?
Example:
RMAN> RUN
SET UNTIL SEQUENCE 11 THREAD 1;
DUPLICATE TARGET DATABASE TO "clone" NOFILENAMECHECK;
With regards
Assuming a non-RAC database, it is always THREAD 1 (i.e. you do NOT need to specify the THREAD).
For the SEQUENCE value, query V$ARCHIVED_LOG for the max(SEQUENCE#).
Hemant K Chitale
Similar Messages
-
Hello,
my question might be a little strange, but I would just like to confirm my understanding to be sure about my testing.
Consider the following:
RMAN> list backup
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
5520 396.79M DISK 00:02:38 15-OCT-11
BP Key: 5541 Status: AVAILABLE Compressed: YES Tag: TAG20111015T190048
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T190048_79MKSH03_.BKP
List of Archived Logs in backup set 5520
Thrd Seq Low SCN Low Time Next SCN Next Time
1 37170 690296258 14-OCT-11 690301863 14-OCT-11
1 37171 690301863 14-OCT-11 690306944 14-OCT-11
1 37172 690306944 14-OCT-11 690312517 14-OCT-11
1 37173 690312517 14-OCT-11 690326343 14-OCT-11
1 37174 690326343 14-OCT-11 690328734 14-OCT-11
1 37175 690328734 14-OCT-11 690334332 14-OCT-11
1 37176 690334332 14-OCT-11 690354457 14-OCT-11
1 37177 690354457 14-OCT-11 690365309 14-OCT-11
1 37178 690365309 14-OCT-11 690383830 14-OCT-11
1 37179 690383830 14-OCT-11 690389381 14-OCT-11
1 37180 690389381 14-OCT-11 690399124 14-OCT-11
1 37181 690399124 14-OCT-11 690403117 14-OCT-11
1 37182 690403117 14-OCT-11 690408333 14-OCT-11
1 37183 690408333 14-OCT-11 690411748 14-OCT-11
1 37184 690411748 14-OCT-11 690417353 14-OCT-11
1 37185 690417353 14-OCT-11 690422345 14-OCT-11
1 37186 690422345 14-OCT-11 690428300 15-OCT-11
1 37187 690428300 15-OCT-11 690433347 15-OCT-11
1 37188 690433347 15-OCT-11 690439543 15-OCT-11
1 37189 690439543 15-OCT-11 690444502 15-OCT-11
1 37190 690444502 15-OCT-11 690450317 15-OCT-11
1 37191 690450317 15-OCT-11 690453707 15-OCT-11
1 37192 690453707 15-OCT-11 690457501 15-OCT-11
1 37193 690457501 15-OCT-11 690458775 15-OCT-11
1 37194 690458775 15-OCT-11 690464449 15-OCT-11
1 37195 690464449 15-OCT-11 690469446 15-OCT-11
1 37196 690469446 15-OCT-11 690474941 15-OCT-11
1 37197 690474941 15-OCT-11 690481459 15-OCT-11
1 37198 690481459 15-OCT-11 690484981 15-OCT-11
1 37199 690484981 15-OCT-11 690490292 15-OCT-11
1 37200 690490292 15-OCT-11 690495899 15-OCT-11
1 37201 690495899 15-OCT-11 690500991 15-OCT-11
1 37202 690500991 15-OCT-11 690508506 15-OCT-11
1 37203 690508506 15-OCT-11 690514835 15-OCT-11
1 37204 690514835 15-OCT-11 690519918 15-OCT-11
1 37205 690519918 15-OCT-11 690535732 15-OCT-11
1 37206 690535732 15-OCT-11 690626387 15-OCT-11
1 37207 690626387 15-OCT-11 690629393 15-OCT-11
1 37208 690629393 15-OCT-11 690634991 15-OCT-11
1 37209 690634991 15-OCT-11 690640154 15-OCT-11
1 37210 690640154 15-OCT-11 690646056 15-OCT-11
1 37211 690646056 15-OCT-11 690651236 15-OCT-11
1 37212 690651236 15-OCT-11 690656775 15-OCT-11
1 37213 690656775 15-OCT-11 690662593 15-OCT-11
1 37214 690662593 15-OCT-11 690668154 15-OCT-11
1 37215 690668154 15-OCT-11 690673574 15-OCT-11
1 37216 690673574 15-OCT-11 690677649 15-OCT-11
1 37217 690677649 15-OCT-11 690683129 15-OCT-11
1 37218 690683129 15-OCT-11 690688406 15-OCT-11
1 37219 690688406 15-OCT-11 690693988 15-OCT-11
1 37220 690693988 15-OCT-11 690698971 15-OCT-11
1 37221 690698971 15-OCT-11 690705146 15-OCT-11
1 37222 690705146 15-OCT-11 690710236 15-OCT-11
1 37223 690710236 15-OCT-11 690715886 15-OCT-11
1 37224 690715886 15-OCT-11 690719326 15-OCT-11
1 37225 690719326 15-OCT-11 690724866 15-OCT-11
1 37226 690724866 15-OCT-11 690729976 15-OCT-11
1 37227 690729976 15-OCT-11 690735596 15-OCT-11
1 37228 690735596 15-OCT-11 690740660 15-OCT-11
1 37229 690740660 15-OCT-11 690746167 15-OCT-11
1 37230 690746167 15-OCT-11 690751851 15-OCT-11
1 37231 690751851 15-OCT-11 690756900 15-OCT-11
1 37232 690756900 15-OCT-11 690759044 15-OCT-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
5521 Incr 0 494.68M DISK 00:03:24 15-OCT-11
BP Key: 5542 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79MKZP6W_.BKP
List of Datafiles in backup set 5521
File LV Type Ckp SCN Ckp Time Name
14 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\CCAPP.DBF
126 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\WAAPP.DBF
131 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\PSDEFAULT02.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Incr 0 193.66M DISK 00:01:38 15-OCT-11
BP Key: 5543 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML6DXJ_.BKP
List of Datafiles in backup set 5522
File LV Type Ckp SCN Ckp Time Name
3 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDOTBS01.DBF
4 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\USERS01.DBF
128 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX02.DBF
132 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDO3.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
5523 Incr 0 644.30M DISK 00:04:11 15-OCT-11
BP Key: 5544 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML9NMK_.BKP
List of Datafiles in backup set 5523
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM01.DBF
2 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX01.DBF
127 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM02.DBF
129 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX03.DBF
BS Key Size Device Type Elapsed Time Completion Time
5524 18.86M DISK 00:00:10 15-OCT-11
BP Key: 5545 Status: AVAILABLE Compressed: YES Tag: TAG20111015T200023
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T200023_79MLKTVM_.BKP
List of Archived Logs in backup set 5524
Thrd Seq Low SCN Low Time Next SCN Next Time
1 37233 690759044 15-OCT-11 690764137 15-OCT-11
1 37234 690764137 15-OCT-11 690768526 15-OCT-11
1 37235 690768526 15-OCT-11 690770962 15-OCT-11
RMAN> /** I left out some lines that seemed duplicate for my question - lines with the same SCN and some older archived logs. I can post the whole thing if it should turn out to be relevant.
What SCN would be appropriate for me to use, taking into account this is a level 0 incremental backup, to restore to the point of a full backup?
I'm fairly sure i can do the following: (and yes, this will result in a successful restore/recover)
run{
set until scn 690770341;
restore database;
switch datafile all;
recover database;
} But is that really the point that I should recover to? The other alternative would be to recover to the SCN of those archivelogs at the very bottom?
Thank you for any comments, whatever they are :-)I am copying the backups between different hosts (or external tape applications) and building the database from backups. So I create a blank instance and catalog the backup files, then specify an SCN to restore/recover.
Would the SCN part be unneeded? I guess if I want to recover to the latest possible state, I do not need to specify any SCN :-). For testing purposes I only specified the full backup SCN to save time, but in the event this would be needed in a production environment, you are right that I would need to recover to the latest possible SCN. Thanks for pointing that out. -
RMAN restore UNTIL SCN in DATA GUARD environment
Hello,
OS=RHL5
DB=11.2.0.3 Primary and 1 Physical STANDBY database.
I have a huge application changes tomorrow and its possible that I have the requirement to ROLLBACK the database 5 hours back because the application.
I am thinking to adopt following method from the official Oracle documentation (untilClause):
STARTUP FORCE MOUNT
RUN
SET UNTIL SCN 1418901; ## Any required SCN number will be used here.
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
I will of course take LEVEL0 backup tonight and LEVEL1 backup before the start of work.
My humble question to you is that: If this is the correct method I am adopting? and if yes, then what about Physical standby database? Will there something to restore/recover too? or it's not required or standby database need to create again (which I am afraid of)?
Flash back is not enabled.
Bundle of thanks for the suggestion.
Best Regardshello John-MK,
My humble question to you is that: If this is the correct method I am adopting?
the method is correct but not the BEST PRACTICE...create a RESTORE POINT instead of using SCN. for example:
SET UNTIL RESTORE POINT before_app_changes;
1. drawbacks of using flashback feature are:
a. you need more disk space
b. there is CPU overhead associated with flashback log operation
c.compulsorily need to use fast recovery area and you can not backup flashback log
d.others..
but my own opinion, i think the advantage out weight the drawbacks, since you are paying for it already
2. if the standby database did not apply redo data past the new resetlogs SCN, then you do not need to re-build. no manual intervention
HTH
Tobi -
RMAN restore using set until scn
Hi guys.
Quick question about using set until scn
when I do list backup output shows multiple scn's for one full (I allocated 4 tape channels for the backup so there are 4 scn's in the output)
Which one do I specify in the set until scn command? Below there is ..163 ...164 ...165 ...166
Here is the backup I want to use:
BS Key Type LV Size Device Type Elapsed Time Completion Time
12526 Incr 0 19G SBT_TAPE 00:27:22 Dec 31 2009 10:25:30
BP Key: 12526 Status: AVAILABLE Tag: TAG20091231T095808
Piece Name: rcworaprd-vprd2-full<12920:707047088:1>.dbf
List of Datafiles in backup set 12526
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/system01.dbf
11 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/ppa_data01.dbf
12 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/ppa_index01.dbf
13 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/itd_index01.dbf
16 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/rcl_data01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
12527 Incr 0 21G SBT_TAPE 00:29:19 Dec 31 2009 10:27:27
BP Key: 12527 Status: AVAILABLE Tag: TAG20091231T095808
Piece Name: rcworaprd-vprd2-full<12921:707047088:1>.dbf
List of Datafiles in backup set 12527
File LV Type Ckp SCN Ckp Time Name
4 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/tools01.dbf
7 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/xdb01.dbf
8 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/user_index02.dbf
9 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/una_data01.dbf
14 0 Incr 1697159164 Dec 31 2009 09:58:08
BS Key Type LV Size Device Type Elapsed Time Completion Time
12528 Incr 0 29G SBT_TAPE 00:33:48 Dec 31 2009 10:31:57
BP Key: 12528 Status: AVAILABLE Tag: TAG20091231T095808
Piece Name: rcworaprd-vprd2-full<12923:707047089:1>.dbf
List of Datafiles in backup set 12528
File LV Type Ckp SCN Ckp Time Name
6 0 Incr 1697159166 Dec 31 2009 09:58:09 /u02/oradata/vprd2/user_index01.dbf
17 0 Incr 1697159166 Dec 31 2009 09:58:09 /u02/oradata/vprd2/rcl_index01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
12529 Incr 0 23G SBT_TAPE 00:38:09 Dec 31 2009 10:36:17
BP Key: 12529 Status: AVAILABLE Tag: TAG20091231T095808
Piece Name: rcworaprd-vprd2-full<12922:707047088:1>.dbf
List of Datafiles in backup set 12529
File LV Type Ckp SCN Ckp Time Name
2 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/drsys01.dbf
3 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/eng_data01.dbf
5 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/user_data01.dbf
10 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/una_index01.dbf
15 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/eng_index01.dbf
Or would it be better to use the set until time... using the oldest time from the backupset 12529 (Dec 31 2009 10:36:17)
All input is appreciated.
Thanks
JamieNote that an online backup is an inconsistent backup:
>
Any backup taken when the database has not been shut down normally is an inconsistent backup. When a database is restored from an inconsistent backup, Oracle must perform media recovery before the database can be opened, applying any pending changes from the redo logs.
As long as your database is running in ARCHIVELOG mode, and you back up your archived redo log files as well as your datafiles, inconsistent backups can be the foundation for a sound backup and recovery strategy. Inconsistent backups are an important part of the backup strategy for most databases, because they offer superior availability. For example, backups taken while the database is still open are inconsistent backups
>
If you need to restore your database using the listed backups, you need to apply the archived redo logs until a SCN which is greater than any SCN in the datafile backup sets: otherwise Oracle won't open the database because some datafiles may have different SCN. -
Incremental backup and recover with UNTIL SCN options.
Hi there
My question is just about internal RMAN mecanisms.
Suppose i've cumulative method for backup with RMAN.
Reference backup provided by Level 0 (by night)
after that i've file001.arc, file002.arc during day
Baclup cumulative Level 1 (by night)
after that i've file003.arc, file004.arc, file005.arc during day
Baclup cumulative Level 1 (by night)
after that i've file006.arc, file007.arc, file008.arc, file009.arc, file010.arc, file011.arc during day
Baclup cumulative Level 1 (by night)
after that i've file012.arc, file013.arc during day
Baclup cumulative Level 1 (by night)
Suppose we need to recover with UNTIL SCN ... (incident can be identied by SCN #nnnnn, suppose SCN near of file008.arc).
Is Rman use benefits of incremental, or in this case (need to recover before particular SCN) systematically start with Reference backup (Created by Incremental Level 0) and then file001.arc, file002.arc ....
Platform:Oracle 10g
Regards
DenYou recover using backup controlfile when you have lost the controlfile - should be obvious.
You recover until cancel when, for example, you want to manually see the archive logs being applied and decide when to stop recovering (maybe you have lost the archive log backups and want it to stop when you don't have any more left to apply). -
RECOVER DATABASE AUTOMATIC UNTIL SCN
Hi,
in 10gR2 on Win 2003, I receive the following error :
RECOVER DATABASE AUTOMATIC UNTIL SCN 584413;
ORA-00905Unfortunately documentation site is not available :
Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.24e70cc3.1270721326.3a6c8f5 Do you know the correct syntaxe ?
Thank you.Hi,
The below link can help you.
http://ss64.com/ora/recover.html
Best regards,
Rafi.
http://rafioracledba.blogspot.com/ -
RMAN duplicate target using set until telling me it can not find data files
I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
However, whenever I try to execute the rman clone, it tells me for each datafile:
RMAN-06023: no backup or copy of datafile 1 found to restore
Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
Here is the RMAN script:
spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
#connect to catalog <catalog info>
# target is the source and auxiliary is destination
#connect target <put in source info here>
#connect auxiliary /
run {
allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
##Archivelog number get from sql archive log list command
#set until sequence 831;
set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
duplicate target database to CSPRSUM1 nofilenamecheck
logfile
group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
Exit
Here is the output:
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog <redacted info>>
2> # target is the source and auxiliary is destination
3> #connect target <redacted info>
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> #set until sequence 831;
14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
starting full resync of recovery catalog
full resync complete
allocated channel: d1
channel d1: SID=534 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=532 device type=DISK
allocated channel: d4
channel d4: SID=531 device type=DISK
allocated channel: a1
channel a1: SID=530 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 15-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 260398799;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
"+data";
set newname for datafile 3 to
"+data";
set newname for datafile 4 to
"+data";
set newname for datafile 5 to
"+data";
set newname for datafile 6 to
"+data";
set newname for datafile 7 to
"+data";
set newname for datafile 8 to
"+data";
set newname for datafile 9 to
"+data";
set newname for datafile 10 to
"+data";
set newname for datafile 11 to
"+data";
set newname for datafile 12 to
"+data";
set newname for datafile 13 to
"+data";
set newname for datafile 14 to
"+data";
set newname for datafile 15 to
"+data";
set newname for datafile 16 to
"+data";
set newname for datafile 17 to
"+data";
set newname for datafile 18 to
"+data";
set newname for datafile 19 to
"+data";
set newname for datafile 20 to
"+data";
set newname for datafile 21 to
"+data";
set newname for datafile 22 to
"+data";
set newname for datafile 23 to
"+data";
set newname for datafile 24 to
"+data";
set newname for datafile 25 to
"+data";
set newname for datafile 26 to
"+data";
set newname for datafile 27 to
"+data";
set newname for datafile 28 to
"+data";
set newname for datafile 29 to
"+data";
set newname for datafile 30 to
"+data";
set newname for datafile 31 to
"+data";
set newname for datafile 32 to
"+data";
set newname for datafile 33 to
"+data";
set newname for datafile 34 to
"+data";
set newname for datafile 35 to
"+data";
set newname for datafile 36 to
"+data";
set newname for datafile 37 to
"+data";
set newname for datafile 38 to
"+data";
set newname for datafile 39 to
"+data";
set newname for datafile 40 to
"+data";
set newname for datafile 41 to
"+data";
set newname for datafile 42 to
"+data";
set newname for datafile 43 to
"+data";
set newname for datafile 44 to
"+data";
set newname for datafile 45 to
"+data";
set newname for datafile 46 to
"+data";
set newname for datafile 47 to
"+data";
set newname for datafile 48 to
"+data";
set newname for datafile 49 to
"+data";
set newname for datafile 50 to
"+data";
set newname for datafile 51 to
"+data";
set newname for datafile 52 to
"+data";
set newname for datafile 53 to
"+data";
set newname for datafile 54 to
"+data";
set newname for datafile 55 to
"+data";
set newname for datafile 56 to
"+data";
set newname for datafile 57 to
"+data";
set newname for datafile 58 to
"+data";
set newname for datafile 59 to
"+data";
set newname for datafile 60 to
"+data";
set newname for datafile 61 to
"+data";
set newname for datafile 62 to
"+data";
set newname for datafile 63 to
"+data";
set newname for datafile 64 to
"+data";
set newname for datafile 65 to
"+data";
set newname for datafile 66 to
"+data";
set newname for datafile 67 to
"+data";
set newname for datafile 68 to
"+data";
set newname for datafile 69 to
"+data";
set newname for datafile 70 to
"+data";
set newname for datafile 71 to
"+data";
set newname for datafile 72 to
"+data";
set newname for datafile 73 to
"+data";
set newname for datafile 74 to
"+data";
set newname for datafile 75 to
"+data";
set newname for datafile 76 to
"+data";
set newname for datafile 77 to
"+data";
set newname for datafile 78 to
"+data";
set newname for datafile 79 to
"+data";
set newname for datafile 80 to
"+data";
set newname for datafile 81 to
"+data";
set newname for datafile 82 to
"+data";
set newname for datafile 83 to
"+data";
set newname for datafile 84 to
"+data";
set newname for datafile 85 to
"+data";
set newname for datafile 86 to
"+data";
set newname for datafile 87 to
"+data";
set newname for datafile 88 to
"+data";
set newname for datafile 89 to
"+data";
set newname for datafile 90 to
"+data";
set newname for datafile 91 to
"+data";
set newname for datafile 92 to
"+data";
set newname for datafile 93 to
"+data";
set newname for datafile 94 to
"+data";
set newname for datafile 95 to
"+data";
set newname for datafile 96 to
"+data";
set newname for datafile 97 to
"+data";
set newname for datafile 98 to
"+data";
set newname for datafile 99 to
"+data";
set newname for datafile 100 to
"+data";
set newname for datafile 101 to
"+data";
set newname for datafile 102 to
"+data";
set newname for datafile 103 to
"+data";
set newname for datafile 104 to
"+data";
set newname for datafile 105 to
"+data";
set newname for datafile 106 to
"+data";
set newname for datafile 107 to
"+data";
set newname for datafile 108 to
"+data";
set newname for datafile 109 to
"+data";
set newname for datafile 110 to
"+data";
set newname for datafile 111 to
"+data";
set newname for datafile 112 to
"+data";
set newname for datafile 113 to
"+data";
set newname for datafile 114 to
"+data";
set newname for datafile 115 to
"+data";
set newname for datafile 116 to
"+data";
set newname for datafile 117 to
"+data";
set newname for datafile 118 to
"+data";
set newname for datafile 119 to
"+data";
set newname for datafile 120 to
"+data";
set newname for datafile 121 to
"+data";
set newname for datafile 122 to
"+data";
restore
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 15-JUN-11
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 122 found to restore
RMAN-06023: no backup or copy of datafile 121 found to restore
RMAN-06023: no backup or copy of datafile 120 found to restore
RMAN-06023: no backup or copy of datafile 119 found to restore
RMAN-06023: no backup or copy of datafile 118 found to restore
RMAN-06023: no backup or copy of datafile 117 found to restore
RMAN-06023: no backup or copy of datafile 116 found to restore
RMAN-06023: no backup or copy of datafile 115 found to restore
RMAN-06023: no backup or copy of datafile 114 found to restore
RMAN-06023: no backup or copy of datafile 113 found to restore
RMAN-06023: no backup or copy of datafile 112 found to restore
RMAN-06023: no backup or copy of datafile 111 found to restore
RMAN-06023: no backup or copy of datafile 110 found to restore
RMAN-06023: no backup or copy of datafile 109 found to restore
RMAN-06023: no backup or copy of datafile 108 found to restore
RMAN-06023: no backup or copy of datafile 107 found to restore
RMAN-06023: no backup or copy of datafile 106 found to restore
RMAN-06023: no backup or copy of datafile 105 found to restore
RMAN-06023: no backup or copy of datafile 104 found to restore
RMAN-06023: no backup or copy of datafile 103 found to restore
RMAN-06023: no backup or copy of datafile 102 found to restore
RMAN-06023: no backup or copy of datafile 101 found to restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
RMAN-06023: no backup or copy of datafile 98 found to restore
RMAN-06023: no backup or copy of datafile 97 found to restore
RMAN-06023: no backup or copy of datafile 96 found to restore
RMAN-06023: no backup or copy of datafile 95 found to restore
RMAN-06023: no backup or copy of datafile 94 found to restore
RMAN-06023: no backup or copy of datafile 93 found to restore
RMAN-06023: no backup or copy of datafile 92 found to restore
RMAN-06023: no backup or copy of datafile 91 found to restore
RMAN-06023: no backup or copy of datafile 90 found to restore
RMAN-06023: no backup or copy of datafile 89 found to restore
RMAN-06023: no backup or copy of datafile 88 found to restore
RMAN-06023: no backup or copy of datafile 87 found to restore
RMAN-06023: no backup or copy of datafile 86 found to restore
RMAN-06023: no backup or copy of datafile 85 found to restore
RMAN-06023: no backup or copy of datafile 84 found to restore
RMAN-06023: no backup or copy of datafile 83 found to restore
RMAN-06023: no backup or copy of datafile 82 found to restore
RMAN-06023: no backup or copy of datafile 81 found to restore
RMAN-06023: no backup or copy of datafile 80 found to restore
RMAN-06023: no backup or copy of datafile 79 found to restore
RMAN-06023: no backup or copy of datafile 78 found to restore
RMAN-06023: no backup or copy of datafile 77 found to restore
RMAN-06023: no backup or copy of datafile 76 found to restore
RMAN-06023: no backup or copy of datafile 75 found to restore
RMAN-06023: no backup or copy of datafile 74 found to restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 72 found to restore
RMAN-06023: no backup or copy of datafile 71 found to restore
RMAN-06023: no backup or copy of datafile 70 found to restore
RMAN-06023: no backup or copy of datafile 69 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restore
RMAN-06023: no backup or copy of datafile 66 found to restore
RMAN-06023: no backup or copy of datafile 65 found to restore
RMAN-06023: no backup or copy of datafile 64 found to restore
RMAN-06023: no backup or copy of datafile 63 found to restore
RMAN-06023: no backup or copy of datafile 62 found to restore
RMAN-06023: no backup or copy of datafile 61 found to restore
RMAN-06023: no backup or copy of datafile 60 found to restore
RMAN-06023: no backup or copy of datafile 59 found to restore
RMAN-06023: no backup or copy of datafile 58 found to restore
RMAN-06023: no backup or copy of datafile 57 found to restore
RMAN-06023: no backup or copy of datafile 56 found to restore
RMAN-06023: no backup or copy of datafile 55 found to restore
RMAN-06023: no backup or copy of datafile 54 found to restore
RMAN-06023: no backup or copy of datafile 53 found to restore
RMAN-06023: no backup or copy of datafile 52 found to restore
RMAN-06023: no backup or copy of datafile 51 found to restore
RMAN-06023: no backup or copy of datafile 50 found to restore
RMAN-06023: no backup or copy of datafile 49 found to restore
RMAN-06023: no backup or copy of datafile 48 found to restore
RMAN-06023: no backup or copy of datafile 47 found to restore
RMAN-06023: no backup or copy of datafile 46 found to restore
RMAN-06023: no backup or copy of datafile 45 found to restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 41 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 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
RMAN> Exit
Recovery Manager complete.
Edited by: kerrygm on Jun 15, 2011 11:36 AMMaybe making progress.
I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
BS Key Type LV Size Device Type Elapsed Time Completion Time
965689 Full 19.86M DISK 00:00:01 16-JUN-11
BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
SPFILE Included: Modification time: 16-JUN-11
SPFILE db_unique_name: CSPROD
Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
BS Key Size Device Type Elapsed Time Completion Time
966218 403.84M DISK 00:00:00 20-MAY-11
BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
List of Archived Logs in backup set 966218
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2112 237027300 20-MAY-11 237046947 20-MAY-11
1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
1 2114 237059284 20-MAY-11 237216514 20-MAY-11
1 2115 237216514 20-MAY-11 237709545 20-MAY-11
1 2116 237709545 20-MAY-11 237722825 20-MAY-11
1 2117 237722825 20-MAY-11 237730431 20-MAY-11
1 2118 237730431 20-MAY-11 237860199 20-MAY-11
I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog 'rmancat/rmancat@rmancat';
2> # target is the source and auxiliary is destination
3> #connect target sys/<pwd>@csprod
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> set until sequence 237046947;
14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
allocated channel: d1
channel d1: SID=532 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=531 device type=DISK
allocated channel: d4
channel d4: SID=555 device type=DISK
allocated channel: a1
channel a1: SID=534 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 17-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 373021170;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
Starting restore at 17-JUN-11
channel d1: starting datafile backup set restore
channel d1: specifying datafile(s) to restore from backup set
channel d1: restoring datafile 00003 to +DATA
channel d2: restoring datafile 00122 to +DATA
channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
channel d3: starting datafile backup set restore
channel d3: specifying datafile(s) to restore from backup set
channel d3: restoring datafile 00002 to +DATA
channel d3: restoring datafile 00020 to +DATA
channel d4: restoring datafile 00120 to +DATA
channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
channel d1: restored backup piece 1
channel d1: restore complete, elapsed time: 00:01:15
channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
channel d4: restored backup piece 1
channel d4: restore complete, elapsed time: 00:03:15
channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
channel d2: restored backup piece 1
channel d2: restore complete, elapsed time: 00:03:35
channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
channel d3: restored backup piece 1
channel d3: restore complete, elapsed time: 00:04:55
Finished restore at 17-JUN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
MAXLOGFILES 23
MAXLOGMEMBERS 3
MAXDATAFILES 1021
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
DATAFILE
'+DATA/csprsum1/datafile/system.1535.754067379'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
datafile 121 switched to datafile copy
input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
datafile 122 switched to datafile copy
input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
contents of Memory Script:
set until scn 373021170;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-JUN-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/csprsum1/datafile/system.1535.754067379'
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
RMAN> Exit
Recovery Manager complete.
What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
(e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
Also, as you can see it was not able to do a media recovery.
Thanks in advance for your help. -
RMAN-05556: not all datafiles have backups that can be recovered to SCN
Oracle 11.2.0.2 SE-One
Oracle Linux 5.6 x86-64
Weekly refresh of a test db from prod, using rman DUPLICATE DATABASE, failed with “RMAN-05556: not all datafiles have backups that can be recovered to SCN”
Background Summary:
Weekly inc 0 backup of production starts on Sunday at 0100, normally completes around 1050. Includes backups of archivelogs
Another backup of just archivelogs runs on Sunday at 1200, normally completes NLT 1201.
On the test server, the refresh job starts on Sunday at 1325. In the past this script used a set until time \"to_date('`date +%Y-%m-%d` 11:55:00','YYYY-MM-DD hh24:mi:ss')\"; -- hard-coded for ‘today at 11:55’.
For a variety of reasons I decided to replace this semi-hard coding of the UNTIL with a value determined by querying the rman catalog, getting the completion time of the inc 0 backup. This tested out just fine in my vbox lab, even when I deliberately drove some updates and log switches during the period the backup was running. But the first time to go live I got the above reported error.
Details:
The key part of the inc 0 backup is this (run from a shell script)
export BACKUP_LOC=/u01/backup/dbprod
$ORACLE_HOME/bin/rman target=/ catalog rman/***@rmcat<<EOF
configure backup optimization on;
configure default device type to disk;
configure retention policy to recovery window of 2 days;
crosscheck backup;
crosscheck archivelog all;
delete noprompt force obsolete;
delete noprompt force expired backup;
delete noprompt force expired archivelog all;
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '$BACKUP_LOC/%d_%F_ctl.backup';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '$BACKUP_LOC/%U.rman' MAXPIECESIZE 4096 M;
sql "alter system archive log current";
show all;
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
backup as compressed backupset incremental level 0 database tag tag_dbprod;
sql "alter system archive log current";
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
list recoverable backup;
EOF
The archivelog-only backup (runs at noon) looks like this:
export BACKUP_LOC=/u01/backup/dbprod
$ORACLE_HOME/bin/rman target=/ catalog rman/***@rmcat<<EOF
configure backup optimization on;
configure default device type to disk;
configure retention policy to recovery window of 2 days;
crosscheck backup;
crosscheck archivelog all;
delete noprompt force obsolete;
delete noprompt force expired backup;
delete noprompt force expired archivelog all;
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '$BACKUP_LOC/%d_%F_ctl.backup';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '$BACKUP_LOC/%U.rman' MAXPIECESIZE 4096 M;
sql "alter system archive log current";
show all;
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
list recoverable backup;
EOF
And the original refresh looked like this:
>> a step to ftp the backups from the prod server to the test server, and some other housekeeping <<, then
cd /backup/dbtest
echo "connect catalog rman/***@rmcat" > /backup/dbtest/dbtest_refresh.rman
echo "connect target sys/*******@dbprod" >> /backup/dbtest/dbtest_refresh.rman
echo "connect auxiliary /" >> /backup/dbtest/dbtest_refresh.rman
echo "run {" >> /backup/dbtest/dbtest_refresh.rman
echo "set until time \"to_date('`date +%Y-%m-%d` 11:55:00','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbtest/dbtest_refresh.rman
echo "duplicate target database to DBTEST;" >> /backup/dbtest/dbtest_refresh.rman
echo "}" >> /backup/dbtest/dbtest_refresh.rman
So, my mod to the refresh was
bkup_point=`sqlplus -s rman/***@rmcat <<EOF1
set echo off verify off feedback off head off pages 0 trimsp on
select to_char(max(completion_time),'yyyy-mm-dd hh24:mi:ss')
from rc_backup_set_details
where db_name='DBPROD'
and backup_type='D'
and incremental_level=0
exit
EOF1`
cd /backup/dbtest
echo "connect catalog rman/***@rmcat" > /backup/dbtest/dbtest_refresh.rman
echo "connect target sys/*******@dbprod" >> /backup/dbtest/dbtest_refresh.rman
echo "connect auxiliary /" >> /backup/dbtest/dbtest_refresh.rman
echo "run {" >> /backup/dbtest/dbtest_refresh.rman
echo "set until time \"to_date('${bkup_point}','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbtest/dbtest_refresh.rman
echo "duplicate target database to DBTEST;" >> /backup/dbtest/dbtest_refresh.rman
echo "}" >> /backup/dbtest/dbtest_refresh.rman
Now the fun begins.
First, an echo in the refresh script confirmed the ‘bkup_point’:
=======================================================
We will restore to 2013-08-25 10:41:38
=======================================================
Internally, rman reset the ‘until’ as follows:
executing command: SET until clause
Starting Duplicate Db at 25-Aug-2013 15:35:44
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=162 device type=DISK
contents of Memory Script:
set until scn 45633141350;
Examining the result of LIST BACKUP (the last step of all of my rman scripts) the full backup shows this:
BS Key Type LV Size Device Type Elapsed Time Completion Time
5506664 Full 61.89M DISK 00:00:03 25-Aug-2013 02:11:32
BP Key: 5506678 Status: AVAILABLE Compressed: NO Tag: TAG20130825T021129
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-00_ctl.backup
SPFILE Included: Modification time: 24-Aug-2013 22:33:08
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45628880455 Ckp time: 25-Aug-2013 02:11:29
BS Key Type LV Size Device Type Elapsed Time Completion Time
5507388 Incr 0 206.03G DISK 08:30:00 25-Aug-2013 10:41:30
List of Datafiles in backup set 5507388
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/datafile/system.258.713574775
>>>>>>>>> snip lengthy list <<<<<<<<<
74 0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/event_i2.dbf
Backup Set Copy #1 of backup set 5507388
Device Type Elapsed Time Completion Time Compressed Tag
DISK 08:30:00 25-Aug-2013 10:41:36 YES TAG_DBPROD
List of Backup Pieces for backup set 5507388 Copy #1
BP Key Pc# Status Piece Name
5507391 1 AVAILABLE /u01/backup/dbprod/eeoi55iq_1_1.rman
>>>>>>>>>>>>> snip lengthy list <<<<<<<<<<<
5507442 52 AVAILABLE /u01/backup/dbprod/eeoi55iq_52_1.rman
Notice the slight difference in time between what is reported in the LIST BACKUP and what was reported by my query to the catalog.
Continuing with the backup list, the second archivelog backup in the script generated six backupsets. The fifth set showed:
BS Key Size Device Type Elapsed Time Completion Time
5507687 650.19M DISK 00:02:18 25-Aug-2013 10:54:53
BP Key: 5507694 Status: AVAILABLE Compressed: YES Tag: TAG20130825T104156
Piece Name: /u01/backup/dbprod/ekoi643j_1_1.alog
List of Archived Logs in backup set 5507687
Thrd Seq Low SCN Low Time Next SCN Next Time
1 1338518 45632944587 25-Aug-2013 05:58:18 45632947563 25-Aug-2013 05:58:20
>>>>>>>>>>>>> snip lengthy list <<<<<<<<<<<
1 1338572 45633135750 25-Aug-2013 10:08:21 45633140240 25-Aug-2013 10:08:24
1 1338573 45633140240 25-Aug-2013 10:08:24 45633141350 25-Aug-2013 10:30:06
1 1338574 45633141350 25-Aug-2013 10:30:06 45633141705 25-Aug-2013 10:41:51
1 1338575 45633141705 25-Aug-2013 10:41:51 45633141725 25-Aug-2013 10:41:55
Notice the availability of the archivelogs including the referenced scn.
Investigation of the ftp portion of the refresh script confirmed that all backup pieces were copied from the prod server.
So what am I overlooking? Having reverted back to the original script to get the refresh completed,HemantKChitale wrote:
So, technically, you only need the database and archivelogs backed up by the database script and not the noon run of the archivelog backup.
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
backup as compressed backupset incremental level 0 database tag tag_dbprod;
sql "alter system archive log current";
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
Yet, why does backupset 5 of the noon archivelog backup show archivelogs from 10:30 to 10:40 if they had been deleted by the database backup script which has a delete input ? It is as if the database backup script did NOT delete the archivelogs and the noon run was the one to backup the archivelogs (again ?)
No, that is from the morning full backup. Note the 'Completion Time" of 25-Aug-2013 10:54:53
However, the error message seems to point to a datafile. Why would reverting the recovery point to 11:55 make a difference, I wonder.
As do I.
Also puzzling to me are the times associated with the completion of the backups. I don't recall ever having to scrutinize a backup listing this closely so I'm sure it's just a matter of filling in some gaps in my understanding, but I noticed this. The backup report (list backup;) shows this for the inc 0 backup:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507388 Incr 0 206.03G
DISK
08:30:00
25-Aug-2013 10:41:30 ------- NOTE THE COMPLETION TIME ----
List of Datafiles in backup set 5507388
File LV Type Ckp SCN
Ckp Time
Name
1
0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/datafile/system.258.713574775
------ SNIP ------
74 0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/event_i2.dbf
Backup Set Copy #1 of backup set 5507388
Device Type Elapsed Time Completion Time
Compressed Tag
DISK
08:30:00
25-Aug-2013 10:41:36 YES
TAG_DBPROD ------- NOTE THE COMPLETION TIME ----
List of Backup Pieces for backup set 5507388 Copy #1
BP Key Pc# Status
Piece Name
5507391 1 AVAILABLE /u01/backup/dbprod/eeoi55iq_1_1.rman
------ SNIP ------
5507442 52 AVAILABLE /u01/backup/dbprod/eeoi55iq_52_1.rman
Then the autobackup of the control file immediatly following:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507523 Full
61.89M
DISK
00:00:03
25-Aug-2013 10:41:47 ------- NOTE THE COMPLETION TIME ----
BP Key: 5507587 Status: AVAILABLE Compressed: NO Tag: TAG20130825T104144
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-01_ctl.backup
SPFILE Included: Modification time: 25-Aug-2013 05:57:15
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45633141671 Ckp time: 25-Aug-2013 10:41:44
Then the archivelog backup immediately following (remember, this created a total of 5 backupset, I'm showing number 4)
BS Key Size
Device Type Elapsed Time Completion Time
5507687 650.19M
DISK
00:02:18
25-Aug-2013 10:54:53 ------- NOTE THE COMPLETION TIME ----
BP Key: 5507694 Status: AVAILABLE Compressed: YES Tag: TAG20130825T104156
Piece Name: /u01/backup/dbprod/ekoi643j_1_1.alog
List of Archived Logs in backup set 5507687
Thrd Seq
Low SCN
Low Time
Next SCN Next Time
1
1338518 45632944587 25-Aug-2013 05:58:18 45632947563 25-Aug-2013 05:58:20
------ SNIP ------
1
1338572 45633135750 25-Aug-2013 10:08:21 45633140240 25-Aug-2013 10:08:24
1
1338573 45633140240 25-Aug-2013 10:08:24 45633141350 25-Aug-2013 10:30:06
1
1338574 45633141350 25-Aug-2013 10:30:06 45633141705 25-Aug-2013 10:41:51
1
1338575 45633141705 25-Aug-2013 10:41:51 45633141725 25-Aug-2013 10:41:55
and the controlfile autobackup immediately following:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507984 Full
61.89M
DISK
00:00:03
25-Aug-2013 10:55:07 ------- NOTE THE COMPLETION TIME ----
BP Key: 5508043 Status: AVAILABLE Compressed: NO Tag: TAG20130825T105504
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-02_ctl.backup
SPFILE Included: Modification time: 25-Aug-2013 05:57:15
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45633142131 Ckp time: 25-Aug-2013 10:55:04
and yet, querying the rman catalog
SQL> select to_char(max(completion_time),'yyyy-mm-dd hh24:mi:ss')
2 from rc_backup_set_details
3 where db_name='DBPROD'
4 and backup_type='D'
5 and incremental_level=0
6 ;
TO_CHAR(MAX(COMPLET
2013-08-25 10:41:38
SQL>
which doesn't match (to the second) the completion time of either the full backup or the associated controlfile autobackp.
Hemant K Chitale
I hope this posts in a readable, understandable manner. I really struggeled with the 'enhanced editor', which I normally use. When I pasted in blocks from the rman report, it kept trying to make some sort of table structure out of it .... guess I'll have to follow that up with a question in the Community forum .... -
How to get the last SCN number from catalog database
Hi All,
I have a catalog database where my PROD database is registered. Evereyday at 12AM rman takes the hot backup of PROD.
Now I want to create a auxillary database using the last RMAN backup, for this I want to restore using the SCN from the catalog views.
Please help me to get the SCN number from the RC_ views.
Regards,
Bikramasifkabirdba wrote:
Current SCN:
Use the dbms_flashback package to get the current SCN. This value will be used during instantiation at the destination site, as well as by RMAN when duplicating the database.
SET SERVEROUTPUT ON
DECLARE
until_scn NUMBER;
BEGIN
until_scn:=
DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER;
DBMS_OUTPUT.PUT_LINE('Until SCN: ' || until_scn);
END;
Regards
Asif KabirHello,
i am a bit confused,
SELECT CURRENT_SCN FROM V$DATABASE;
6272671324
and from your package
SET SERVEROUTPUT ON
DECLARE
until_scn NUMBER;
BEGIN
until_scn:=
DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER;
DBMS_OUTPUT.PUT_LINE('Until SCN: ' || until_scn);
END;Until SCN: 6272671267
why are they different, and why first result is lower than yours? can you explain please, thank you
Ugur MIHCI -
Got error while recover controlfile with rman
Dear all,
My controlfile and some datafiles were crash and i tried to recover their with rman as the following step:
1. startup nomount;
2. restore controlfile from autobackup;
3. alter database mount;
4. restore database;
5.SELECT archivelog_change#-1 FROM v$database;
ARCHIVELOG_CHANGE#-1
1301671
6.run {
set until scn 1301671;
recover database;
executing command: SET until clause
Starting recover at 01 พ.ย. 2006
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/01/2006 15:38:01
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start until change 1301671 using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\DB01\SYSTEM01.DBF'
What happend? Please give me some advise.
Thaks for advance !
CharaAfter every resetlogs you have to take fresh backup.
It seems you have opened your database in resetlogs and your backup is prior to this resetlogs.So the controlfile is showing inconsistance with the other datafiles. -
Unable to recover database after rman recovery and database open resetlogs
I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM -
How can I determine what is the minimum SCN number I need to restore up to.
Say if I have a full database backup, I know I have file inconsistency, but I want to know what is the minimum time or SCN number a need to roll forward to in order to be able to open the database?
For example: I do a database restore.
restore database ;
RMAN> sql 'alter database open read only';
sql statement: alter database open read only
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 03/16/2009 15:00:04
RMAN-11003: failure during parse/execution of SQL statement: alter database open read only
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oradata/p1/system01.dbf'
I need need to apply archive log files. All references I find for ORA-00194 state the solution is to "apply more logs until the file is consistent " But "HOW MANY LOGS", or more apporaite up to what time or SCN? How does one determine what TIME or SCN is required to get all file consistent?
I thought this query might provide the answer, but it doesn't
select max(checkpoint_change#)
from v$datafile_header
MAX(CHECKPOINT_CHANGE#)
7985876903
--It applies a bit more redo, but not enough to make my datafiles consistent.
recover database until SCN=7985876903 ;
Starting recover at 03/16/09 15:04:54
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
using channel ORA_DISK_6
using channel ORA_DISK_7
using channel ORA_DISK_8
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=18436
channel ORA_DISK_1: reading from backup piece /temp-oracle/backup/hot/p1/20090315/hourly.arch_P1_47353_681538638_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/temp-oracle/backup/hot/p1/20090315/hourly.arch_P1_47353_681538638_1 tag=TAG20090315T041716
channel ORA_DISK_1: restore complete, elapsed time: 00:02:26
archive log filename=/u01/app/oracle/flash_recovery_area/P1/archivelog/2009_03_16/o1_mf_1_18436_4vxd81yc_.arc thread=1 se quence=18436
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oradata/p1/system01.dbf'
I've discover I need to apply archive logs until this query reports all datafiles as FUZZY=NO , but this only works by guessing at some time periord to roll forward to, then checking the FUZZY column, and try again. Is there a way to know, I have to roll forward to a specific SNC in order for all my datafiles to be consistent?
select file#
, status
, checkpoint_change#
, checkpoint_time
, FUZZY
, RECOVER
,LAST_DEALLOC_SCN
from v$datafile_header
order by checkpoint_time
Thanks,
JasonThe minimum point in time is the time when the last backup piece for datafiles in that backup was completed.
Your alert.log should show the redo log sequence number at that time.
You can query V$ARCHIVED_LOG and get the FIRST_CHANGE# of the first archivedlog generated after that backup piece completed.
A
LIST BACKUP;in RMAN should also show you the SCNs at the time of the backups.
You can also query SCN_TO_TIMESTAMP -- eg
select timestamp_to_scn(to_timestamp('15-MAR-09 09:24:01','DD-MON-RR HH24:MI:SS')) from dual;will return an approximation of the SCN.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on Mar 17, 2009 9:41 AM
added the LIST BACKUP command from RMAN. -
Control file failed error while duplicating database using RMAN
I am using oracle database 10g R2 and trying to make a clone of the source database orcl on the same machine but with different directory structure with the name of test.
When i run the duplicate command to create test database, then following error is generted:
D:\>rman target sys@orcl nocatalog auxiliary /
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Nov 11 12:13:26 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: ORCL (DBID=1264668332)
using target database control file instead of recovery catalog
connected to auxiliary database: TEST (not mounted)
RMAN> @script.txt
RMAN> Run {
2> Allocate channel C1 type disk;
3> allocate auxiliary channel 'adisk_0' type DISK;
4> duplicate target database to "test";
5> #BACKUP INCREMENTAL LEVEL 1 DATABASE;
6> #BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;
7> #BACKUP INCREMENTAL LEVEL 0 DATABASE;
8> #delete obsolete;
9> }
allocated channel: C1
channel C1: sid=140 devtype=DISK
allocated channel: adisk_0
channel adisk_0: sid=157 devtype=DISK
Starting Duplicate Db at 11-NOV-11
contents of Memory Script:
set until scn 12926250;
set newname for datafile 1 to
"D:\TEST\ORADATA\SYSTEM01.DBF";
set newname for datafile 2 to
"D:\TEST\ORADATA\UNDOTBS01.DBF";
set newname for datafile 3 to
"D:\TEST\ORADATA\SYSAUX01.DBF";
set newname for datafile 4 to
"D:\TEST\ORADATA\USERS01.DBF";
set newname for datafile 5 to
"D:\TEST\ORADATA\EXAMPLE01.DBF";
set newname for datafile 6 to
"D:\TEST\ORADATA\GL.DBF";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 11-NOV-11
channel adisk_0: starting datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\TEST\ORADATA\SYSTEM01.DBF
restoring datafile 00002 to D:\TEST\ORADATA\UNDOTBS01.DBF
restoring datafile 00003 to D:\TEST\ORADATA\SYSAUX01.DBF
restoring datafile 00004 to D:\TEST\ORADATA\USERS01.DBF
restoring datafile 00005 to D:\TEST\ORADATA\EXAMPLE01.DBF
restoring datafile 00006 to D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ44MH4_.BKP tag=TAG20111107T220
channel adisk_0: restore complete, elapsed time: 00:01:46
Finished restore at 11-NOV-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M REUSE,
GROUP 2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M REUSE,
GROUP 3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M REUSE
DATAFILE
'D:\TEST\ORADATA\SYSTEM01.DBF'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=766930525 filename=D:\TEST\ORADATA\UNDOTBS01.DBF
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=766930525 filename=D:\TEST\ORADATA\SYSAUX01.DBF
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=766930526 filename=D:\TEST\ORADATA\USERS01.DBF
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=766930526 filename=D:\TEST\ORADATA\EXAMPLE01.DBF
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=766930526 filename=D:\TEST\ORADATA\GL.DBF
contents of Memory Script:
set until scn 12926250;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 11-NOV-11
channel adisk_0: starting incremental datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7CO
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7COGJZVT_.BKP tag=TAG20111109T223
channel adisk_0: restore complete, elapsed time: 00:00:07
channel adisk_0: starting incremental datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR1MQFO_.BKP tag=TAG20111110T221
channel adisk_0: restore complete, elapsed time: 00:00:16
starting media recovery
archive log thread 1 sequence 524 is already on disk as file D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CS
C
archive log filename=D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CSG2HVT_.ARC thread=1 sequence=524
media recovery complete, elapsed time: 00:00:14
Finished recover at 11-NOV-11
contents of Memory Script:
shutdown clone;
startup clone nomount ;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 230686720 bytes
Fixed Size 1248236 bytes
Variable Size 67109908 bytes
Database Buffers 155189248 bytes
Redo Buffers 7139328 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M REUSE,
GROUP 2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M REUSE,
GROUP 3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M REUSE
DATAFILE
'D:\TEST\ORADATA\SYSTEM01.DBF'
CHARACTER SET WE8MSWIN1252
released channel: C1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/11/2011 12:16:21
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
RMAN> **end-of-file**
Script.txt
Run {
Allocate channel C1 type disk;
allocate auxiliary channel 'adisk_0' type DISK;
duplicate target database to "test";
}Kindly help?Moazzam wrote:
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
Kindly help?>Please check what is the value of parameter db_name in the standby database? It should be match with TEST name
Cheers -
Control File error while duplicating Database through Rman
Hi,
Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
Os:Win Xp
I am trying to create a Standby through Rman....
I am using this Run Block to take backup of Primary Database.......
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
setlimit channel d1 kbytes 2097150;
setlimit channel d2 kbytes 2097150;
backup incremental level 0 format 'e:\Oracle\standby\rman\df_%U' database
include current controlfile for standby;
sql "alter system archive log current";
backup
archivelog all format 'e:\Oracle\standby\rman\al_%U' delete input;
}After taking the Backup when I am trying to create the standby with Duplicate command it s giving me Error...
The Run Block I am using is ......
RMAN> run {
2> allocate auxiliary channel dup1 type disk;
3> allocate auxiliary channel dup2 type disk;
4> set newname for datafile 1 to 'E:\Oracle\standby\system01.dbf';
5> set newname for datafile 2 to 'E:\Oracle\standby\UNDOTBS01.DBF';
6> set newname for datafile 3 to 'E:\Oracle\standby\SYSAUX01.DBF';
7> set newname for datafile 4 to 'E:\Oracle\standby\USERS01.DBF';
8> duplicate target database for standby
9> dorecover;
10> }
allocated channel: dup1
channel dup1: sid=37 devtype=DISK
allocated channel: dup2
channel dup2: sid=36 devtype=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 02-OCT-08
contents of Memory Script:
set until scn 1105194;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 02-OCT-08
channel dup1: starting datafile backupset restore
channel dup1: restoring control file
channel dup1: reading from backup piece E:\ORACLE\STANDBY\RMAN\DF_0VJS4RS7_1_1
channel dup1: restored backup piece 1
piece handle=E:\ORACLE\STANDBY\RMAN\DF_0VJS4RS7_1_1 tag=TAG20081002T124502
channel dup1: restore complete, elapsed time: 00:00:01
output filename=D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CTL1STANDBY.ORA
Finished restore at 02-OCT-08
sql statement: alter database mount standby database
released channel: dup1
released channel: dup2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/02/2008 13:01:43
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/02/2008 13:01:43
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
*ORA-00201: control file version 10.2.0.1.0 incompatible with ORACLE version 10.2.0.0.0*
ORA-00202: control file: 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CTL1STANDBY.ORA'Why i am getting this Incomaptable Control File error inspite of Backing up the control File.....
Regards,
Prosenjit MukherjeeCheck the value for the parameter "COMPATIBLE" in the source and standby database instance parameter files.
"COMPATIBLE" should be the same.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i70517
"... ensure the COMPATIBLE initialization parameter is set to the same value on both the primary and standby databases"
Edited by: Hemant K Chitale on Oct 2, 2008 4:09 PM
Added link and quote from 10g doc -
Problem in recover physical standby database(Data Guard) by rman
Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle 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: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PMhi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks
Maybe you are looking for
-
After upgrade to CS5 Audio does not import / load with video in avi
I updated from Ppro CS3 to CS5 purchased from the Adobe store. I opened a project created in CS3 in CS5 and followed the prompt to save it as a new project. All tracks, edits, etc were intact and any given sequence played re-rendered etc., as expecte
-
CRM 5.0 outbound queues to Mobile sales
Hi all, We have upgraded from CRM 3.0 to CRM 5.0. I am looking at the outbound queues in SMQ1 that are bound to Mobile sales Sites and am not finding any data bundles other than the name of the Replication Object name in the LUW's of these queues. Bu
-
HI,I have a officejet 6700 printer I'v been trying since I got it to have it print in black ink only .I click on preferences and advanced then choose black ink only it prints then in black but then reverts back to color !!!! how do I make it (BLACK)
-
Using the Clip function of an AP-Element
This is a follow up question to my previous post asking about opening external links within my site. After taking some good advice on embedding the image in an HTML doc on my site and then calling this page from the navigation bar.......I'm now on th
-
I am a photographer who likes to arrange what I have shot after I have put the images into Lightroom. I often want to drag one shot before another to make the presentation more powerful. With even most of the cheapest programs I can drag and drop ima