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

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

  • 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!

  • 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.

  • 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 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 -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.

  • Recover database cancel using controlfile

    Hi,
    I want to know what means and what will do this command
    RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
    and what means the option
    Specify log: {=suggested | filename | AUTO | CANCEL}
    thanks for you help

    I want to know what means and what will do this command
    RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
    and what means the option
    Specify log: {=suggested | filename | AUTO | CANCEL}You can perform recovery by providing logs how you wish.
    suggested - you can give enter, so that which thread & Sequence it wants it will apply one archive.
    filename - if you want to mention filename(in case actual file name is different) ,ofcourse you can give one by one up to what archives you want to apply
    Auto - If you want to perform recovery with all the available archvies, you can prefer option too
    Cancel - if you apply any of the archives, when you want to cancel, If you perform this recovery will be cancelled.
    Also read documentation from Oracle http://docs.oracle.com/cd/B12037_01/server.101/b10734/rcmrecov.htm
    Edited by: CKPT on Jun 4, 2012 10:38 AM

  • RECOVER UNTIL SEQ= 1425

    Hi,
    my database in 9i. It is in archive log. It has crashed just now at 11 Am. I have the cold backups of last night 00 PM. I have also my today archivlogs and the last one is 1_5_636384500.DBF.
    Can I open my database with cold backup and then do
    RECOVER DATABASE UNTIL LOGSEQ=636384500 THREAD= 1;
    to have all my today transaction until 11 Am ?
    If the syntax is wrong please correct it.
    Many thanks.

    Well, as orafad says, it helps to have the right syntax.
    Also, you are doing incomplete recovery. That means you are using archivelogs which contain information which is unknown to the control file. You have to tell Oracle this, otherwise it will look in your control file and refuse to recover your database in the belief that it is already good and consistent.
    You need
    recover database using backup controlfile until <whatever>;
    alter database open resetlogs;
    As for <whatever> you can use 'cancel' or a time or a change number.
    what should also work would be:
    recover automatic database using backup controlfile;
    In this case it will generate archivelog names and continually apply them until it can't find a log.
    at that point you type in cancel and
    'alter database open resetlogs;
    (It will expect to find archivelogs in the directory it copied them to in the first place)

  • HP LaserJet 3700 - Reprints job until cancelled

    I have a HP Color LaserJet 3700n on my network and I am attempting to set it up with OS X 10.7. The driver is built in to Lion and is unavailable anywhere else.
    When I send a test page or any other print job to the printer, it repeats printing it until the paper runs out or I cancel the job. Something is wrong here but I can't see how to change any relevant settings.
    Changing the driver to "Generic PCL" works fine but then doesn't support color.
    Any ideas?

    I suggest you redownload the drivers for your system.
    LJ 3700 Win 7 32bit drivers
    LJ 3700 Win 7 64bit drivers
    See if that helps.
    What the message is teeling you is that the installed drivers don't support collation. Its possible that the Win 7 drivers are not able to do collation yet. If that is the situation I would suggest using the support area to e-mail HP to see if this is true and, if so, when they might be available.
    Hope this helps,
    Scott

  • Duplication doesnt recover until set time asks for more archives

    Hi all
    Today i refreshed Database (TST)
    Datafile backup was taken ataround 21:33 and at same time controlfile was taken backup then start Archive files backup and then again 2nd time controlfile was taken backup
    Sep 24 20:15 DF_PROD.bak
    Sep 24 20:36 DF_PROD.bak
    Sep 24 20:56 DF_PROD.bak
    Sep 24 21:11 DF_PROD.bak
    Sep 24 21:33 DF_PROD.bak
    Sep 24 21:33 CF_c-20130924-00_PROD.bak
    Sep 24 21:36 AF_13318_1_afterbu_PROD.bak
    Sep 24 21:37 AF_13319_1_afterbu_PROD.bak
    Sep 24 21:37 AF_13320_1_afterbu_PROD.bak
    Sep 24 21:40 AF_13317_1_afterbu_PROD.bak
    Sep 24 21:40 AF_13314_1_afterbu_PROD.bak
    Sep 24 21:40 AF_13315_1_afterbu_PROD.bak
    Sep 24 21:40 AF_13316_1_afterbu_PROD.bak
    Sep 24 21:40 CF_c-616662153-20130924-01_PROD.bak
    this was the backup taken with catalog also
    CF is control file
    AF is archives
    DF is datafiles
    now while doing refresh i used
    set until time "to_date(upper('24-Sep-20132133'),'DD-MON-YYYYHH24MI')+(1/24/60)";
    Since 1st control file was taken and 21:33 and 1/24/60 means recover database until 21:33 + 1minute
    After this also duplication is asking for archives which are generated latest .
    please suggest me on this why database is not able to recover and left in mounted stage as it should be able to open database without any issue
    Regards

    Hi
    I think i should go for restore control file from CF_c-616662153-20130924-01_PROD.bak
    eg
    restore controlfile from '<path>/CF_c-616662153-20130924-01_PROD.bak ';
    in target  database and then go from duplication and set until time mentioned below
    which is the last control file backup and then go for
    set until time "to_date(upper('24-Sep-20132133'),'DD-MON-YYYYHH24MI')+(1/24/60)";
    Hope this will resolve this issue and database will refresh and open automatically without asking further archive information
    please give suggestion or correct me if i am wrong ..
    Regards

  • RECOVER UNTIL TIME

    Hi all,
    I try to flashback my database and when i do the command FLASHBACK DATABASE TO SCN 122343434; i receive the message saying that i don´t have any flashback logs. I don´t know why these logs disappear. What i whant now is recover database until time because i have all my archives. How can i do this??
    RECOVER DATABASE UNTIL SCN my_scnnumber;
    ALTER DATABASE OPEN RESETLOGS;
    Is just that??
    Tks,
    Paulo.

    Do you have FLASHBACK enabled?
    sys@ORCL> select flashback_on from v$database;
    FLASHBACK_ON
    YES
    Elapsed: 00:00:00.03
    sys@ORCL>You can do incomplete recovery with user managed backups.
    http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/osrecov008.htm#sthref1743

  • 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
    Den

    You 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).

  • Lost seq of redo log due to corruption and cannot recover database.

    Hi!
    This db I am working on is a test database running 10.2.0.3 on OEL5. Unfortunately due to some human error, we lost the redo log sequence 1_28_xxxxxx.redo. As this was a non-critical db, we didn't plan any backups for the db... and now whenever I try to open the db I get the error:
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/app/oracle/oradata/tadb1/system01.dbf'
    SQL> recover until cancel
    ORA-00279: change 510956 generated at 08/31/2010 22:00:17 needed for thread 1
    ORA-00289: suggestion :
    /opt/app/oracle/oradata/tadb1/archive/1_28_728336713.dbf
    ORA-00280: change 510956 for thread 1 is in sequence #28
    SQL> recover database until time '31-AUG-2010 22:00:00';
    ORA-00283: recovery session canceled due to errors
    ORA-00314: log 1 of thread 1, expected sequence# 28 doesn't match 0
    ORA-00312: online log 1 thread 1: '/opt/app/oracle/oradata/tadb1/redo01.log'
    Is there a way to open the database!?
    Thanks,
    AB007

    Sorry for the late response guys... had called it a night earlier... well, I tried your suggestion... but still, the database can't recover -
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 510958 generated at 09/02/2010 23:56:37 needed for thread 1
    ORA-00289: suggestion : /opt/app/oracle/oradata/tadb1/archive/1_1_728697397.dbf
    ORA-00280: change 510958 for thread 1 is in sequence #1
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    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: '/opt/app/oracle/oradata/tadb1/system01.dbf'
    ORA-01112: media recovery not started
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ALERT LOG
    ALTER DATABASE RECOVER database using backup controlfile until cancel
    Fri Sep 3 10:14:22 2010
    Media Recovery Start
    WARNING! Recovering data file 1 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 2 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 3 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 4 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    parallel recovery started with 2 processes
    ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
    Fri Sep 3 10:14:25 2010
    ALTER DATABASE RECOVER CANCEL
    ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep 3 10:14:26 2010
    ALTER DATABASE RECOVER CANCEL
    ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep 3 10:14:43 2010
    alter database open resetlogs
    Fri Sep 3 10:14:43 2010
    RESETLOGS is being done without consistancy checks. This may result
    in a corrupted database. The database should be recreated.
    RESETLOGS after incomplete recovery UNTIL CHANGE 510958
    Resetting resetlogs activation ID 2129258410 (0x7ee9e7aa)
    Online log /opt/app/oracle/oradata/tadb1/redo02.log: Thread 1 Group 2 was previously cleared
    Online log /opt/app/oracle/oradata/tadb1/redo03.log: Thread 1 Group 3 was previously cleared
    Fri Sep 3 10:14:45 2010
    Setting recovery target incarnation to 3
    Fri Sep 3 10:14:45 2010
    Assigning activation ID 2129271722 (0x7eea1baa)
    Thread 1 opened at log sequence 1
    Current log# 1 seq# 1 mem# 0: /opt/app/oracle/oradata/tadb1/redo01.log
    Successful open of redo thread 1
    Fri Sep 3 10:14:45 2010
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Sep 3 10:14:45 2010
    SMON: enabling cache recovery
    Fri Sep 3 10:14:45 2010
    Errors in file /opt/app/oracle/admin/tadb1/udump/tadb1_ora_5949.trc:
    ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [], []
    Fri Sep 3 10:14:45 2010
    Errors in file /opt/app/oracle/admin/tadb1/udump/tadb1_ora_5949.trc:
    ORA-00704: bootstrap process failure
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [], []
    Fri Sep 3 10:14:45 2010
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Instance terminated by USER, pid = 5949
    ORA-1092 signalled during: alter database open resetlogs...

Maybe you are looking for