Rman recover noredo vs. until cancel

Hi,
Oracle 11g 11.2.0.1
What is the difference please between rman +recover noredo+ and +recover until cancel+ ?
According to Oracle documentation, noredo can be used if the database is in noarchvielog mode and the online redo logs are lost. Does this mean it actually does not apply the archvielogs, even if available? Is this the difference from recover until cancel ?
Also, why do I need to run recvover until cancel using backup controlfile from SQL, and cannot use RMAN, which does not understand this command?
Thanks.

According to Oracle documentation, noredo can be used if the database is in noarchvielog mode and the online redo logs are lost. Does this mean it >actually does not apply the archvielogs, even if available? Is this the difference from recover until cancel ?If database is in NOARCHIVE mode, there are NO archivelogs to apply!

Similar Messages

RMAN - Incremental backup / NOARCHIVELOG / Restore & Recover Until Cancel

I'm testing out a weekly plan as follows:
Sun : Shutdown db, RMAN level 0 Incremental Backup
Mon-Sat: Shutdown db, RMAN level 1 Incremental Backup.
The database is NOARCHIVELOG mode and is 10.2 XE.
I then run a restore (which I understand to be to move the datafiles from the backup set to their online location). My next aim is to do a recover.
I'm really confused at this point. Say I take the backup the night before (either a level 0 or 1, I'm assuming that this makes no difference) then in the morning I drop a table accidentally. Okay - I want to go back to the position after the backup. When I do recover, I understand that Oracle applies redo logs written since the backup.
So I don't want a recover, I want a recover until cancel. When I issue this command it is suggesting that I use an archive log file. Well obviously I don't have any of those so I press cancel thinking that this will bring me back to the point EXACTLY AFTER THE NIGHTLY BACKUP and with my table back. But it doesn't!
I would be really grateful if anyone has a definitive answer to this - what are the steps to recover a database to the point after the backup was taken ignoring any changes since the backup.
Thanks all.
Tom.

Hi Werner
Do you mean if the online logs are available with the changes after the last backup until the database restore then there is a possibility to apply changes? Ie at this point I could put in the redo log names instead of the archive log names.
If they have been overwritten since the backup (ie cycled round completely) then is the behaviour to restore the database and then not apply any logs?
Do you know if this is documented anywhere? There seems to be an emphasis on ARCHIVELOG mode only, especially in the books I have seen.
Thanks,
Tom

Recover database until cancel using backup controlfile Fails with ORA-01547

Hi
First of all, I'm sorry for posting in this community as my issue doesn't have any thing to do with Rman, but I couldn't find any more relative Community to post in
our System is Oracle EBS 11i and the OS on the production is AIX 5.2 / and the DR is 5.3 / DB version is 9i
we have our Oracle ERP scheduled using crontab to take a database COLD backup daily using gtar -cvzf .
yesterday I needed to clone the database only, so I used my usual method witch is
1) on the source SQL> alter database backup controlfile to trace as '<dest>/makecntrlfil.sql'
then you can delete the Commented header and change the first command from
"CREATE CONTROLFILE REUSE DATABASE <SOURCE> NORESETLOGS ..."
TO
CREATE CONTROLFILE SET DATABASE <TARGET> RESETLOGS <NO>ARCHIVELOG
2) de-compress the tgz files
3) on the target edit the $ORACLE_HOME/dbs/init<source>.ora, $ORACLE_HOME/environment file
4)run /ORACLE_HOME/appsutils/clone/bin/adcfgclone.prl
5) delete old controlfiles
6) on the database run the script you created on firs t step to create a new control fole
7)recover database until cancel using backup controlfile
8) alter database open resetlogs
add new temp file system
this way I used to do it
but yesterday when trying to execute recover database it didn't work, and gave this error
ORA-00279: change 6450277404 generated at 02/28/2013 02:47:56 needed for thread
1
ORA-00289: suggestion : /ERPDEV/DBASE/devdb/9.2.0/dbs/arch1_188462.dbf
ORA-00280: change 6450277404 for thread 1 is in sequence #188462
Specify log: {<RET>=suggested | filename | AUTO | CANCEL} >> I gave cancel >> so >>
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: '/ERPDEV/DBASE/SYS/devdata/system01.dbf'
nothing strange in the original alert log file in the time of taking the backup
So can You please tell me what maybe wrong and why it used to work before and now it's not
take in consideration that we are on archive log mode, but not using Rman or the archived Logs for backup and the sequence it needed ( 188462 ) is too old and already deleted on Production.

the output of the sript
Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
172.16.10.10:1.0
access control disabled, clients can connect from any host
You are running adstpall.sh version 115.19
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh stop script returned:
adapcctl.sh version 115.54
Apache Web Server Listener :httpd ( pid 765998 ) is running.
Stopping Apache Web Server Listener (dedicated HTTP) ...
Apache Web Server Listener (PLSQL) :httpd ( pid 2830390 ) is running.
Stopping Apache Web Server Listener (dedicated PLSQL) ...
adapcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh stop script returned:
adalnctl.sh version
Shutting down listener process APPS_ABP.
adalnctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh stop script returned:
You are running adtcfctl.sh version 115.14
Shutting down TCF SocketServer for ABP on port -1.
adtcfctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh stop script returned:
You are running adcmctl.sh version 115.28
Shutting down concurrent managers for ABP ...
Submitted request 7481224 for CONCURRENT FND SHUTDOWN
adcmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh stop script returned:
You are running adfrmctl.sh version 115.37
Stopping forms server for ABP on port 9003.
adfrmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh stop script returned:
You are running adrepctl.sh version 115.32
stopping Reports Server for ABP on port 7003.
kill -9 827420
Reports Server for ABP successfully stopped.
adrepctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh stop script returned:
You are running adfmcctl.sh version 115.19
Stopping forms load balancing client for ABP.
adfmcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh stop script returned:
You are running adfmsctl.sh version 115.15
Stopping forms metrics server for ABP on port 9203.
adfmsctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh stop script returned:
You are running jtffmctl.sh version 115.16
Shutting down Fulfillment Server for ABP on port 9303 ...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
All enabled services on this node are stopped.
Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010130.log for details
Exiting with status 0
You are running addlnctl.sh version 115.7
Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
Shutting down listener process ABP ...
addlnctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Shutting down database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:36:25 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
Database closed.
Database dismounted.
ORACLE instance shut down.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Starting the database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:38:48 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 6829474752 bytes
Fixed Size          742336 bytes
Variable Size          1493172224 bytes
Database Buffers     5324800000 bytes
Redo Buffers          10760192 bytes
Database mounted.
Database opened.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Shutting down database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:39:08 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
Database closed.
Database dismounted.
ORACLE instance shut down.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
root 2883784 2097278 0 01:39:54 - 0:00 grep abpappl
root 1425530 2097278 1 01:39:54 - 0:00 grep abpora
Taring /ERPABP/DBASE/SYS/abpdata
Mon Apr 1 01:39:54 SAUST 2013
Mon Apr 1 03:00:16 SAUST 2013
Taring /ERPDEV/DBASE/SYS/abpdata
Mon Apr 1 03:00:16 SAUST 2013
Mon Apr 1 03:10:18 SAUST 2013
Taring /ERPABP/DBASE/DATA/abpdata
Mon Apr 1 03:10:18 SAUST 2013
Mon Apr 1 04:51:04 SAUST 2013
Taring /ERPDEV/APPL/DATA/abpdata
Mon Apr 1 04:51:04 SAUST 2013
Mon Apr 1 05:02:58 SAUST 2013
You are running addbctl.sh version 115.10
Starting the database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 05:04:46 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 6829474752 bytes
Fixed Size          742336 bytes
Variable Size          1493172224 bytes
Database Buffers     5324800000 bytes
Redo Buffers          10760192 bytes
Database mounted.
Database opened.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addlnctl.sh version 115.7
Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
Starting listener process ABP ...
addlnctl.sh: exiting with status 0
Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
172.16.10.10:1.0
access control disabled, clients can connect from any host
You are running adstrtal.sh version 115.16
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh start script returned:
adapcctl.sh version 115.54
Apache Web Server Listener is not running.
Starting Apache Web Server Listener (dedicated HTTP) ...
Apache Web Server Listener (PLSQL) is not running.
Starting Apache Web Server Listener (dedicated PLSQL) ...
adapcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh start script returned:
adalnctl.sh version
Checking for FNDFS executable.
Starting listener process APPS_ABP.
adalnctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh start script returned:
You are running adtcfctl.sh version 115.14
TCF SocketServer for ABP on port -1 is already started.
adtcfctl.sh: exiting with status 2
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh start script returned:
You are running adcmctl.sh version 115.28
Starting concurrent manager for ABP ...
Starting ABP_0401@ABP Internal Concurrent Manager Default printer is noprint
adcmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh start script returned:
You are running adfrmctl.sh version 115.37
Starting forms server for ABP on port 9003.
adfrmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh start script returned:
You are running adrepctl.sh version 115.32
starting Reports Server for ABP on port 7003.
adrepctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh start script returned:
You are running adfmcctl.sh version 115.19
Starting forms load balancing client for ABP.
adfmcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh start script returned:
You are running adfmsctl.sh version 115.15
starting forms metrics server for ABP.
adfmsctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh start script returned:
You are running jtffmctl.sh version 115.16
Validating Fulfillment patch level via /ERPABP/APPL/abpcomn/java Fulfillment patch level validated.
Starting Fulfillment Server for ABP on port 9303 ...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
All enabled services for this node are started.
Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010505.log for details
Exiting with status 0
MWA Telnet Server Release: 1.0.8.4 [December 12th 2002] Mon Apr 1 05:06:01 SAUST 2013
9653.50     /store/abp/data/data_abpdata_010413.tgz
1089.50     /store/abp/data/datadev_abpdata_010413.tgz
0.04     /store/abp/data/mkctrl.sql
13309.38     /store/abp/data/sys_abpdata_010413.tgz
1000.25     /store/abp/data/sysdev_abpdata_010413.tgz
Mon Apr 1 05:06:01 SAUST 2013
#######################################################################################################################

Recover until cancel

Oracle XE windows xp
hi
lets say I dont have any backup which is taken by RMAN
SQL>recover database until cancel
Media recovery complete.
SQL>recover database until cancel using backup controlfile
ORA-00280: change 2019545 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
What is the diffrence between two recover options?
In the first recover statement why ıt doesnt let me to cancel redolog.

but I dont have an old control file,even no backupswhat do you mean by dont have old controlfile even no backups??
recover database using backup controlfile will not take care of the SCN within controlfile ,normally when you issue recover database oracle aplly logs from redo till the CKPT SCN at controlfile but in case of using recover database using backup controlfile oracle neednt to know the SCN to stop applying recovery it starts aplly all archive logs as possible.You use recover database using backup controlfile when you have controlfile is older then yours datafile or you dont have valid controlfile i.e corrupted controlfile.
Khurram

"recover database until cancel" asks for archive log file that do not exist

Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.

Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1.   When you have current controlfile and need complete data (no data loss),
      then do not go for until cancel recovery.
2.   Oracle will apply all the redologs (including current redolog) while recovery
     process is    on.
3. During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you    can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar

Doubt in Recover database until cancel

Hi experts,
One query, I want to try out recover database until cancel. But my archivelog files are in tape drive. How do i do it as it ask for archiver destination directory for the archivelog file.
Or can any please explain how should i do it.
Thanks in advance
shaan

Hi Satist,
when i apply the other archivelog file, it again shows the error
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 1740044 generated at 06/18/2007 21:20:18 needed for thread 1
ORA-00289: suggestion : /oracle/NEWDB/admin/arch/1_5.dbf
ORA-00280: change 1740044 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/NEWDB/admin/arch/1_30.dbf
ORA-00310: archived log contains sequence 30; sequence 5 required
ORA-00334: archived log: '/oracle/NEWDB/admin/arch/1_30.dbf'
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: '/oracle/NEWDB/oradata/NEWDB/system.dbf'
Please tell me why this happening or any solution for this. Moreover i have archivelog file
from 1_1 to 1_14 .
Thanks in advance
shaan

DB Back to a Specific Time with Archive Logs (Until cancel or time?)

I'll try to be as clear as possible with my intended goals and the limitations of the system I'm working with:
1. We have a test instance of our Oracle DB that I would like to be able to refresh with data from the production instance at any time, without having to shut down the production database or put tablespaces into hot backup mode.
2. Both systems are HP Itanium boxes with differing numbers of CPUs and RAM. Those differences have been taken into account in the init.ora file for the DB instances.
3. The test and production instances are using a SAN to hold the following file systems: ora_redo1, ora_redo2, ora_archlog, oradata10g. The test instance is using SAN snapshots (HP EVA series SAN) of the production file systems to pull the data over when needed. The problem is that the only window to do this is when the production system is down for nightly maintenance which is about a 20 minute period. I want to escape this limitation.
What I've been doing is using the HP SAN to take snapshots of the file systems on the production system mentioned above. I do this while the production DB is up and running. I then import those snapshots into the test system, run an fsck to ensure file system integrity, then start up the Oracle instance as follows:
startup mount
Then I run the following query I found on line to determine the current redo log:
select member from v$logfile lf , v$log l where l.status='CURRENT' and lf.group#=l.group#;
Then I attempt to run a recovery as follows:
recover database using backup controlfile until cancel;
When prompted, I enter the path to the first of the current redo logs and hit enter. After waiting, sometimes it says that the recovery completed, other times it stops saying there was an error and that more files are needed to make the DB consistent.
I took the above route because doing a recover until time (which is what I really want to do) kept prompting me for the next archive log in sequence that didn't yet exist when I took the SAN snapshot. Here was my recover until time command:
recover database until time 'yyyy-mm-dd:hh:mm:ss' using backup controlfile;
What I would like to do is take the SAN snapshot and then recover the database to about a minute before the snapshot using the archive logs. I don't want to use RMAN since that seems to be overkill for this purpose. A simple recovery to a specific point in time seems to be all that is needed and I have archive logs which, I assume, SHOULD help me get there. Even if I have to lose the last hour's worth of transactions I could live with that. But my tests setting the specific time of recovery to even 12 hours earlier still resulted in a prompt for the next, non-existent archivelog.
I will also note that I even tried copying the next archive log over once it did exist and the recovery would then prompt me for the next archive log! I will admit right now that I really don't know a whole lot about Oracle or DBs, but it's my task to try and make it possible to "refresh" the test DB with the most recent data with no impact on the production DB.
The reason I don't want to use hot backup mode is that I don't know the DB schema other than there are probably 58 or more tablespaces. The goal is to use SAN snapshots for their speed instead of having to take RMAN files and copy them to the test instance. I'm sure I'm not the only person who has ever tried this. But most of what I've found on line refers to RMAN, hot backup mode, or down time. The first two don't take advantage of SAN snapshots for a quick swap of all the Oracle file systems and I can't afford downtime other than that window at night. Is there some reason that the recover to time didn't work even though I have archive logs?
One final point. The recover until cancel actually worked a couple of times, but it seems to be sporadic. It likely has something to do with what was happening on the production DB when I created the SAN snapshots. I actually thought I had a solution with recover until cancel last week until it didn't work three times in a row.

I haven't completely discounted it but it seems like I would need to back up to files, then restore from files. I don't want to do that. I want a full file system level SAN snapshot that I can just drop into place. The does work when the production base is shut down. However, considering that I do have archive logs, shouldn't it be possible to use them to recover to a specific scene without having to do an RMAN backup at all? It seems that doing an RMAN backup/recovery would just make this whole process a lot longer since the DB is 160 gigs in size (not huge, but the dump would take more time than I would like). With a SAN snapshot, if I can get this to work, I'm looking at about a 15-20 minute period of time to move the production DB over to test.
Since you are suggesting that RMAN may be a better approach I'll provide more details about what I'm trying to do. Essentially this is like trying to recover a DB from a server that had its power plug pulled. I was hoping that Oracle's automatic recovery would do the same thing it would do in that instance. But obviously that doesn't work. What I want to do is bring over all the datafiles, redo logs, and archive logs using the SAN snapshot. Then if possible use some aspect of Oracle (RMAN if it can do it) to mount the database, then recover to a specific time or SCN if using RMAN. However, when I tried using RMAN to do it, I got an error saying that it couldn't restore the data file because it already existed. Since I don't want to start from scratch and have RMAN rebuild files that I've already taken snapshots of (needless copying of data), I gave up on the RMAN approach. But, if you know of a way to use RMAN so that it can recover to a specific incarnation without needing to runm a backup first, I am completely open to trying it.

RMAN-01009: syntax error: found "cancel"

Hi!
I am playing with rman on my test machine and I encountered error that I can't resolve.
I've tried to restore/recover datafiles executing this commands:
$ sqlplus "/as sysdba"
SQL>startup mount
RMAN> restore database
(everything went well)
RMAN> recover database until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "cancel": expecting one of: "logseq, scn, sequence, time"
RMAN-01007: at line 1 column 24 file: standard input
I've executed this command on several occasions and never had a problem, but now syntax error.
Just don't know why syntax error?!
OS: Centos 5
DB: 11.1.0.7.0
Thanks for any help,
Marko

RMAN> alter database recover database using backup controlfile until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recover": expecting one of: "mount, open"
RMAN-01007: at line 1 column 16 file: standard input
RMAN> recover database;
Starting recover at 05-FEB-09
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 02/05/2009 00:11:30
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oradata/testdb/redo/testdb/onlinelog/o1_mf_3_4qfwj5fn_.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
I am trying to execute:
RMAN> sql 'alter database open resetlogs';
sql statement: alter database open resetlogs
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 02/05/2009 00:09:18
RMAN-11003: failure during parse/execution of SQL statement: alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
This is the reason why I am trying to execute cancel-based recovery.

RMAN recover on a different server - Verify all changes are applied

Hey everyone,
I have two database servers, Oracle 10g SE on linux. One is the 'primary', and we plan to switchover to the other newer server. In order to minimize the downtime from a duplicate database, or a full backup and restore/recover, I restored the database to the newer server using RMAN, and just continuously apply the archivelogs generated from the original database through RMAN> recover database;.
My question is, at the time when we do do the switchover, how can I ensure that all changes in the database are written to the archivelogs? I understand I can do a 'alter system switch archivelog' until all groups are inactive, but will this be enough? I've noticed that when I force an archivelog switch, the previous group still has an 'ACTIVE' status, even though I thought that the ARC process had just written out all the changes from that redo log to the archivelog?
Any help would be much appreciated. Thanks

Dear oscrub,
You can compare the system change numbers on both databases and you can also use the standby redo log files for synchronized data replication with the maximum availability or maximum protection protection levels.
I you don't want to see the archivelog as ACTIVE state you need to run the following command;
SQL> ALTER SYSTEM CHECKPOINT GLOBAL;You will manually trigger the checkpoint and the data in the redolog (active one) will be written to the database thanks to the database writer processes. With that way, you won't see the online redo log as ACTIVE state. You will see online redologs as "CURRENT" and "INACTIVE".
I hope that addresses your questions.
Regards.
Ogan

DB -What action have been done by until cancel?

ORALCE 8174/Hotbackup:
SQL> SELECT TO_CHAR(CHECKPOINT_CHANGE#) DATAFILE_SCN, TO_CHAR(LAST_CHANGE#) DATAFILE_LASTSCN FROM V$DATAFILE;
2 /
DATAFILE_SCN DATAFILE_LASTSCN
9220396163609
9220396163791
9220396163711
9220396163711
9220396163764
9220396163764
9220396163789
9220396163611
9220396163624
9220396163791
9220396163655
DATAFILE_SCN DATAFILE_LASTSCN
9220396163655
12 rows selected.
SQL> SELECT TO_CHAR(CHECKPOINT_CHANGE#) DATAFILE_HSCN FROM v$datafile_header
2 /
DATAFILE_HSCN
9220396163609
9220396163667
9220396163687
9220396163711
9220396163748
9220396163764
9220396163789
9220396163611
9220396163624
9220396163791
9220396163640
DATAFILE_HSCN
9220396163655
12 rows selected.
SQL> recover database using backup controlfile;
ORA-00279: change 9220396163609 generated at 07/28/2007 00:01:07 needed for thread 1
ORA-00289: suggestion : /data1/newdb/orcl/arch/arch_1_13876.arc
ORA-00280: change 9220396163609 for thread 1 is in sequence #13876
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279: change 9220396171447 generated at 07/28/2007 01:31:22 needed for thread 1
ORA-00289: suggestion : /data1/newdb/orcl/arch/arch_1_13877.arc
ORA-00280: change 9220396171447 for thread 1 is in sequence #13877
ORA-00278: log file '/data1/newdb/orcl/arch/arch_1_13876.arc' no longer needed for this recovery
ORA-00308: cannot open archived log '/data1/newdb/orcl/arch/arch_1_13877.arc'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
SQL> SELECT TO_CHAR(CHECKPOINT_CHANGE#) DATAFILE_HSCN FROM v$datafile_header;
DATAFILE_HSCN
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
DATAFILE_HSCN
9220396171447
12 rows selected.
SQL> SELECT TO_CHAR(CHECKPOINT_CHANGE#) DATAFILE_SCN, TO_CHAR(LAST_CHANGE#) DATAFILE_LASTSCN FROM V$DATAFILE;
DATAFILE_SCN DATAFILE_LASTSCN
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
9220396171447
DATAFILE_SCN DATAFILE_LASTSCN
9220396171447
12 rows selected.
SQL> SELECT TO_CHAR(CHECKPOINT_CHANGE#) DB_SCN,TO_CHAR(CONTROLFILE_CHANGE#) CONTROL_SCN FROM v$database;
DB_SCN CONTROL_SCN
9220396163608 9220396171447
SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/data1/newdb/orcl/datafile/system01.dbf'
*********why still show above error and can't open db?
SQL>[color=Red] recover database using backup controlfile until cancel;[color]
ORA-00279: change 9220396171447 generated at 07/28/2007 01:31:22 needed for thread 1
ORA-00289: suggestion : /data1/newdb/orcl/arch/arch_1_13877.arc
ORA-00280: change 9220396171447 for thread 1 is in sequence #13877
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
[color=Red]AUTO[color]
ORA-00308: cannot open archived log '/data1/newdb/orcl/arch/arch_1_13877.arc'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
[color=Red]SQL> recover database using backup controlfile until cancel;[color]
ORA-00279: change 9220396171447 generated at 07/28/2007 01:31:22 needed for thread 1
ORA-00289: suggestion : /data1/newdb/orcl/arch/arch_1_13877.arc
ORA-00280: change 9220396171447 for thread 1 is in sequence #13877
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
[color=Red]CANCEL[color]
Media recovery cancelled.
SQL> alter database open resetlogs;[color=Red][color]
Database altered.
*********What action have been done by UNTIL CANCEL?
Message was edited by:
[email protected]

I'll say it again in case you missed it the first time: V$ views are NOT part of the data dictionary. You can't read the data dictionary until the database is opened.
If you've performed a recovery 'until cancel', your datafiles are all in synch with each other. They may even agree with checkpoint change number in the controlfile. But what about your redo logs? By definition, they will have changes in them from a time after the point in the redo stream you got to when you said 'cancel'.
Therefore, the redo logs will be ahead of where the rest of the database has now gotten to.
And that is why you HAVE to open the database with a resetlogs operation (that is, 'alter database open resetlogs;'). That causes the existing redo logs to be wiped clean and thus cleared of any redo from a time after the time the rest of your database has been recovered to.

RMAN Recover database error..

Hi All,
We were trying to restore and recover one of our databases. The restore went well but the recover is erroring out. Can someone please let us know what we should do to remedy this and carry on with the recovery.
We got an error when we were trying to restore the controlfile at the begining (details below), but as you can see, it did manage to restore a copy of the controlfile successfully..
Details below.
C:\Users\oracle>rman target system/XXXX catalog rman/XXXX@rmancat
Recovery Manager: Release 11.1.0.7.0 - Production on Thu Dec 2 08:31:03 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CODP (not mounted)
connected to recovery catalog database
RMAN> set dbid=2399577932
executing command: SET DBID
database name is CODP and DBID is 2399577932
RMAN> RESTORE CONTROLFILE;
Starting restore at 02-DEC-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=152 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00
channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
"ORA-19505: failed to identify file D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
failover to previous backup
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1
channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
"ORA-19505: failed to identify file D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
failover to previous backup
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01 tag=TAG20101130T204059
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=C:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL01.CTL
output file name=D:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL02.CTL
output file name=D:\ORACLE\ORADATA\CODP\CONTROL03.CTL
Finished restore at 02-DEC-10
RMAN> RESTORE SPFILE FROM AUTOBACKUP;
Starting restore at 02-DEC-10
using channel ORA_DISK_1
recovery area destination: D:\oracle\flash_recovery_area\
database name (or database unique name) used for search: CODP
channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101202
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101201
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101130
channel ORA_DISK_1: AUTOBACKUP found: D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
channel ORA_DISK_1: restoring spfile from AUTOBACKUP D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
Finished restore at 02-DEC-10
RMAN> restore database;
Starting restore at 02-DEC-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00020 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T1.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00002 to D:\ORACLE\ORADATA\CODP\UNDOTBS01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:03:25
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00009 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00010 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to D:\ORACLE\ORADATA\CODP\SYSTEM01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00005 to D:\ORACLE\ORADATA\CODP\PROD_T1_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00006 to D:\ORACLE\ORADATA\CODP\PROD_T2_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00007 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00025 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:36
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00024 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00026 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00027 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_04.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00011 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00030 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_07.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00028 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_05.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00029 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_06.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00003 to D:\ORACLE\ORADATA\CODP\SYSAUX01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00008 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00032 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00033 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00034 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00031 to D:\ORACLE\ORADATA\CODP\PROD_I1_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00004 to D:\ORACLE\ORADATA\CODP\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00021 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T2.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 02-DEC-10
RMAN> recover database;
Starting recover at 02-DEC-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/02/2010 09:08:05
ORA-00210: cannot open the specified control file
RMAN>Thanks

Sorry everyone.. My bad.. I forgot to MOUNT the instance before trying to use the RECOVER DATABASE command.
Thanks

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/

Recover datafile datafile_name until consistent with controlfile;

Hi.
When I tried to start a database I got message
Database mounted.
ORA-01113: file 22 needs media recovery
ORA-01110: data file 22: '/d01/ORACLE/DEV06/DEV06_sl_def_eo_01.dbf'
Can I use the above command in subject i.e.
recover datafile <datafile_name> until consistent with controlfile;
and then use alter database open to bring up the database.
It is a 10.1.0.4
Thanks
/SKH

Did you try what Eric recommended?
Restore the affected datafiles from backup and perform recovery
SQL> RECOVER DATAFILE <FILE NUMBER>
or
SQL> RECOVER DATABASE ;
V$DATAFILE
V$RECOVER_FILE
V$RECOVERY_FILE_STATUS
V$RECOVERY_PROGRESS Also check if you experience the below explained situation (Query V$BACKUP) :-
Ending a Backup After an Instance Failure or SHUTDOWN ABORT
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/osbackup004.htm
Hope it helps,
Babu Rangasamy

What order are Archive logs restored in when RMAN recover database issued

Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
Thanks

Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions.

Question:rman recover (error:Bad header found during inspecting archived )

oracle9208 aix5.2
after restore database successfully,i recover database
i receive info in alert_sid.log
Corrupt block seq: 0 blocknum=1.
Bad header found during inspecting archived log
Data in bad block - seq:184680448. bno:369098753. time:0
beg:0 cks:260
calculated check value: 2653
Reread of seq=0, blocknum=1, file=/dev/rora_redo1_21, found same corrupt data
alter database recover datafile list
161 , 162 , 163 , 164 , 165 , 166 , 167 , 168
Completed: alter database recover datafile list
161 , 162 ,
Fri Nov 6 22:37:17 2009
alter database recover if needed
start until time 'NOV 01 2009 21:07:53' using backup controlfile
Media Recovery Start
ORA-279 signalled during: alter database recover if needed
start until time...
then recover processes hang for a long time
so why and how can i solve this problem??

Dear user097815,
I think there are a couple of syntax errors and it would be better for you to first try each one one-by-one than add them into your "run" block.
RMAN> allocate channel for maintenance device type 'SBT_TAPE';
using target database control file instead of recovery catalog
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=910 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protector A.06.10/611
RMAN> allocate auxiliary channel t1 type 'sbt_tape';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
RMAN-01007: at line 1 column 10 file: standard input
RMAN> ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
RMAN-01007: at line 1 column 10 file: standard input
RMAN> run
ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
}Hope That Helps.
Ogan

Rman recover noredo vs. until cancel

Similar Messages

Maybe you are looking for