Recovery using backup controlfile

hai,
can any one explain me on what is the difference between recovering database as,
recover database until cancel using backup controlfile;and
recover database until cancel;regards
ashik

Hi,
>>Note that you should only use a backup controlfile that was created via 'alter database backup controlfile to /path/to/your/controlfile_backup;'
Not exactly... we can use a control file that was made by a cold backup in order to recover a database.
SQL*Plus: Release 9.2.0.4.0 - Production on Tue Nov 21 21:10:19 2006
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
Enter user-name: / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area   93394180 bytes
Fixed Size                   451844 bytes
Variable Size              67108864 bytes
Database Buffers           25165824 bytes
Redo Buffers                 667648 bytes
Database mounted.
Database opened.
SQL> create user SCOTT identified by TIGER default tablespace USERS quota unlimited on USERS;
User created.
SQL> grant connect to SCOTT;
Grant succeeded.
SQL> connect SCOTT/TIGER
Connected.
SQL> create table emp (cod number primary key);
Table created.
SQL> begin
2 for i in 1..10000 loop
3 insert into emp values (i);
4 end loop
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> select count(*) from emp;
  COUNT(*)
     10000
SQL> connect system/manager
Connected.
SQL> select name from v$archived_log;
NAME
/backup/archive/1_10.dbf
/backup/archive/1_11.dbf
/backup/archive/1_12.dbf
/backup/archive/1_13.dbf
4 rows selected.
SQL> select * from v$log;
    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
1 1 14 512000 1 NO CURRENT 51849 22-NOV-06
         2          1         12     512000          1 YES INACTIVE                 51826 22-NOV-06
         3          1         13     512000          1 YES ACTIVE                   51840 22-NOV-06
SQL> connect / as sysdba
Connected.
Crash Simulation
SQL> shutdown abort
ORACLE instance shut down.
Lost Data files and Control Files Simulation
SQL> host
oracle@linux:/u01> rm oradata/BDRPS/*.dbf
oracle@linux:/u01> rm oradata/BDRPS/*.ctl
oracle@linux:/u01> ls -l oradata/BDRPS/
total 1524
-rw-r-----    1 oracle   oinstall   512512 2006-11-22 08:20 redo01.log
-rw-r-----    1 oracle   oinstall   512512 2006-11-22 08:18 redo02.log
-rw-r-----    1 oracle   oinstall   512512 2006-11-22 08:19 redo03.log
Restore Data Files and Control Files from last cold backup
oracle@linux:/u01> cp -a /backup/oradata/BDRPS/*.dbf oradata/BDRPS/
oracle@linux:/u01> cp -a /backup/oradata/BDRPS/*.ctl oradata/BDRPS/
oracle@linux:/u01> exit
exit
SQL> startup
ORACLE instance started.
Total System Global Area   93394180 bytes
Fixed Size                   451844 bytes
Variable Size              67108864 bytes
Database Buffers           25165824 bytes
Redo Buffers                 667648 bytes
Database mounted.
ORA-00314: log 1 of thread 1, expected sequence# doesn't match
ORA-00312: online log 1 thread 1: '/u01/oradata/BDRPS/redo01.log'
Begin Recovery Process
SQL> recover database using backup controlfile;
ORA-00279: change 51548 generated at 11/07/2006 20:24:21 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_10.dbf
ORA-00280: change 51548 for thread 1 is in sequence #10
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52048 generated at 11/22/2006 08:18:35 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_11.dbf
ORA-00280: change 52048 for thread 1 is in sequence #11
ORA-00278: log file '/backup/archive/1_10.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52056 generated at 11/22/2006 08:18:36 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_12.dbf
ORA-00280: change 52056 for thread 1 is in sequence #12
ORA-00278: log file '/backup/archive/1_11.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52076 generated at 11/22/2006 08:18:37 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_13.dbf
ORA-00280: change 52076 for thread 1 is in sequence #13
ORA-00278: log file '/backup/archive/1_12.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52087 generated at 11/22/2006 08:18:37 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_14.dbf
ORA-00280: change 52087 for thread 1 is in sequence #14
ORA-00278: log file '/backup/archive/1_13.dbf' no longer needed for this
recovery
In this moment, I don't have a sequence log 14 archived, then I will use the Current Log File Group for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/oradata/BDRPS/redo01.log
Log applied.
Media recovery complete.
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;
Database altered.
SQL> connect SCOTT/TIGER
Connected.
SQL> select count(*) from emp;
  COUNT(*)
     10000Cheers

Similar Messages

  • Recovery using backup control file

    Hello friends,
    I have a scenario where i am unable to recover by database by using backup control file option can u pls give ur expert advice.
    1) Database is working in ARCHIVE MODE.
    2) One of my file was READ ONLY when i take my closed backup. At this time
    v$log file output is :
    group# thread# sequence# bytes member arc status first_change#
    1 1 8 8192 2 yes inactive 4697463
    2 1 9 8192 2 yes active 4717493
    3 1 10 8192 2 no current 4717738
    3) After 2-3 log switches i have made it READ WRITE.
    4) After making it READ WRITE i have taken controlfile backup by using
    ALTER SYSTEM BACKUP CONTROLFILE TO 'E:\ORACLE\CONTROL01.CTL';.
    5) Again i have make some log switches.
    6) Shutdown my database using SHUTDOWN option.
    7) Copy my SYSTEM,UNDO,USER,INDEX datafiles from my backup (taken at
    step 2) and CONTROL file (taken at step 4).
    8) I have not copied my old redo log files so those are new.
    9) I mount database & then use this command to recover database :
    RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
    10) My recovery process starts applying archived log files and applied upto
    sequence no 9. When it starts applying last one 10 which is online redo log
    and not yet archived my recovery process fails by giving this error:
    ORA-00308: cannot open archived log 'd:\oracle\oradata\practice\archive\1_10.dbf'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    11) I try to open database using :
    ALTER DATABASE OPEN RESETLOGS;
    it gives following warning:
    Error at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: datafile 1: 'D:\ORACLE\ORADATA\PRACTICE\SYSTEM01.DBF'
    Please guide me why it is so ?
    Whether in BACKUP CONTROL FILE CASES system didn't recognise ONLINE REDO LOG FILES or it is anything else.
    Regards
    Sethi

    Hi,
    >>I am not using RMAN. I am taking user managed backups. Moreover i have tried what u said that make checkpoints also but again i came to the same result when it try to apply last archived log which was current redo log when database was started to shutdown it says unable to find the specified file & then when i open database using resetlogs it says system file needs media recovery.
    it show error because you are using wrong approach of Recovery.
    Alter database open Resetlog command is used only in incomplete recovery.
    but your are giving
    Recover database command,it means ur performing full recovery (means you have apply online redo logfile.) and after applying it you should open the database with Alter database Open command.
    No need to give resetlog option.
    Again Restore all backup;
    Issue Recover database;
    and open the database with
    Alter database open;
    Thanks
    Kuljeet Pal Singh

  • ORA-01194 and ORA-00604 when using backup controlfile set #2

    Database version Oracle 11.2.0.1
    Enterprise Linux 5.4
    Database is in archivelog mode.
    I'm trying to recover a database according to set #2 of a backup controlfile to trace. Creating the controlfile works fine, but recovering the database fails.
    From what I can gather, the recovery fails because it cannot roll forward - sequence 39 is in the missing online redo logfile. However, the database is opened with the restlogs option, and I understand that it should use the archivelogs in order to roll backwards. Since this is a new controlfile it does not know about archivelogs, but it does not accept to register or use any archivelog files.
    The recovery as outlined in set #2 does not seem to work as advertised. Any ideas?
    Following errors:
    SQL>  CREATE CONTROLFILE REUSE DATABASE "RCAT" RESETLOGS  ARCHIVELOG etc.
    Control file created.
    Tyring to register on of the archivelogs does not work:
    SQL>  ALTER DATABASE REGISTER LOGFILE '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc';
    ALTER DATABASE REGISTER LOGFILE '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc'
    ERROR at line 1:
    ORA-00604: error occurred at recursive SQL level
    Applying an existing archivelog during recovery does not work:
    SQL> recover database using backup controlfile until cancel
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc
    ORA-00310: archived log contains sequence 33; sequence 39 required
    ORA-00334: archived log:
    '/u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc'
    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: '/u02/RCAT/datafile/o1_mf_system_6959kz7l_.dbf'
    ls -l /u02/fra/RCAT/archivelog/2010_09_19:
    -rw-r----- 1 oracle dba 49313280 Sep 19 00:01 o1_mf_1_33_69bfo5tx_.arc
    -rw-r----- 1 oracle dba   312320 Sep 19 00:03 o1_mf_1_34_69bft63b_.arc
    -rw-r----- 1 oracle dba 20343808 Sep 19 02:10 o1_mf_1_35_69bo6y6j_.arc
    -rw-r----- 1 oracle dba    40960 Sep 19 02:12 o1_mf_1_36_69boc9t8_.arc
    -rw-r----- 1 oracle dba    20992 Sep 19 02:13 o1_mf_1_37_69bofng4_.arc
    -rw-r----- 1 oracle dba   794624 Sep 19 02:15 o1_mf_1_38_69bokwbf_.arcThanks,
    Markus

    Specifying sequence 39 results in the same error message, which is what is what it tries to apply when using "recover until cancel" and typing cancel. But the problem is that sequence 39 was in the online redologs, which were not archived yet.
    SQL> select name, first_change#,next_change# from v$archived_log;
    NAME                                        FIRST_CHANGE# NEXT_CHANGE#
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_34_69bft63b_.arc        1259096     1259295
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_37_69bofng4_.arc        1269876     1269935
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_35_69bo6y6j_.arc        1259295     1269766
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_36_69boc9t8_.arc        1269766     1269876
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_38_69bokwbf_.arc        1269935     1270557
    /u02/fra/RCAT/archivelog/2010_09_19/o1_mf_1_33_69bfo5tx_.arc        1241003     1259096
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_21_699l4tkj_.arc        1215727     1215730
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_24_699s5pj8_.arc        1215736     1224966
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_26_699s5rp4_.arc        1224969     1224972
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_15_6987rbqp_.arc        1174393     1174511
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_23_699l4xng_.arc        1215733     1215736
    NAME                                        FIRST_CHANGE# NEXT_CHANGE#
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_28_699s5tqt_.arc        1224975     1224987
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_22_699l4w5r_.arc        1215730     1215733
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_29_699s5vw2_.arc        1224987     1224990
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_19_699l4or0_.arc        1215721     1215724
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_25_699s5qd6_.arc        1224966     1224969
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_30_699s5yvs_.arc        1224990     1224999
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_27_699s5stf_.arc        1224972     1224975
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_32_69b2hgvz_.arc        1225003     1241003
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_17_699k5oxl_.arc        1194778     1209476
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_16_699jsxol_.arc        1174511     1194778
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_20_699l4rx2_.arc        1215724     1215727
    NAME                                        FIRST_CHANGE# NEXT_CHANGE#
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_18_699l4msq_.arc        1209476     1215721
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_14_6987mljx_.arc        1162149     1174393
    /u02/fra/RCAT/archivelog/2010_09_18/o1_mf_1_31_699s61sr_.arc        1224999     1225003
    25 rows selectedHow does it actually know about all the archivelogs?
    Edited by: Markus Waldorf on Sep 20, 2010 8:37 AM

  • Why cant the controlfile be in sync, when using backup controlfile

    hi all,
    i understand a few point ...from a dba friend of mine..
    you need a resetlog to sync the datafile headers and the controlfiles
    1) you need a resetlog when doing incomplete recovery
    2) you can recovery completely using a backup controlfile provided you have all the necessary archived logs and online redo logs.
    3) but in order not to do resetlog after 2) , you must re-create the controlfile
    my questions are
    q1) are the following point above true ?
    *q2)  why cant oracle update the controlfile when recovering using the backup controlfile ? in that case, i do not need to recreate a controlfile , isnt it ?
    Rgds,
    Noob

    user12050668 wrote:
    hi hermant,
    q1) why would i need to open the database with resetlog ?
    Yes. i am using a backup controlfile, but i have all the archived and online redologs till point of failure ?
    The purpose of a resetlog is to sync the controlfile and datafile headers , isnt it ? but i do not need to sync, as i have all the latest applied
    am i right ?
    If you use RECOVER DATABASE USING BACKUP CONTROLFILE in this case control file type is *"BACKUP"* but not *"CURRENT"* due to even you have all archivelogs and online logs you have to open database RESETLOGS statement.Actually after applying all archive and online redo logs ALTER DATABASE OPEN RESETLOGS internally sync and "Say" to control files "RECOVER FINISHED".Because CF type is BACKUP.
    q2) You need to OPEN RESETLOGS. You can choose to create controlfile OR not create controlfile (i.e. open with the backup controlfile that was used for the RECOVER).
    If you do a CREATE CONTROLFILE it has to be CREATE CONTROLFILE RESETLOGS, followed by ALTER DATABASE OPEN RESETLOGS.
    in what circumstances, would i need to re-create the controlfile when i can still use the backup controlfile ? as in any case, i would still need to resetlog.
    Rgds,
    NoobIf you have backup controlfile then do not need recreate control files.And you need use backup control file.If you lost all backup of control files and copies then or you want change database name then you can use RECREATE CONTROL FILE again.

  • Recovering using backup controlfile

    Hello,
    When we do database recovery (not until some time in the past, but until "now") using binary backup of controlfile why do we need to open it with resetlogs?
    The scenario is: we have all the datafiles, archived redo and online redo logs, but all of the controlfile are lost. We have backup of controfile and we need to restore and recover it. I've read we need to open the db with resetlogs then. Why?
    I heard we don't need to do this if there was backup of the controlfile to text trace. I also don't understand why.
    Thanks in advance for help
    Aliq

    Navneet wrote:
    Hi,
    In case when controlfile i lost and restored from the bcakup, Datafiles are uptodate with the redo log files but controlfiles are behind,
    WHen we say "Recover databse using backup controlfile" this means we are applying the archives to the datafiles as well as controlfiles. But datafiles are uptodate aor they will remain untopuched and controlfile wil be updated to the recnt redo.
    Now the quetion is why we need reetlogs even when we are doing complete recovery?
    So the reasin for this is controlfile needs to be updated with some datastructure updatations and those updations are performed during resetlog option. These data structure updatation may contain some changes in the properties of datafiles,blocks, or somethng internal processes of ORacle.
    So we need to use resetlogs.
    Regards,
    NavneetNavneet,
    Control flies are going to get updated from the datafile info which are going to get update from the archived logs.We never apply archive logs to the control file , they are meant for datafiles only.
    Now the quetion is why we need reetlogs even when we are doing complete recovery?
    So the reasin for this is controlfile needs to be updated with some datastructure updatations and those updations are performed during resetlog option. These data structure updatation may contain some changes in the properties of datafiles,blocks, or somethng internal processes of ORacle.
    So we need to use resetlogs.
    Hmm well I am afraid that its plainly wrong. Resetlog is required because we are stopping the recovery in between. This means whatever we have done and is stored in the archived logs , we can't apply it all. Now we have thrown datafiles and control file back in the time but redo logs never come back. So we are starting from fresh with resetlogs which will make the seuence numbers 0,1 and lets open the db. After the db is open, the sequence numbers are matched with the stored ones in the controlfile and datafile.
    Aman....

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

  • Rman Recovery using backup created using dbconsole

    Thanks for taking my questions. First, I see there is another person asking about rman recovery but I am hoping mine is not identical.
    BACKGROUND
    Archiving and flashback is on.
    Database is 11g.
    Full on-line database backup is done using dbconsole (oem) and includes control, spfile and archive logs.
    RECOVERY
    I am testing my recovery to a new serve.
    I installed oracle
    Restored a backupset from one backup to the new servers flashbackup area.
    Recovered the spfile ok
    Recovered the control file ok
    Found last seq number ok
    Restore database ok
    RECOVER DATABASE UNTIL SEQUENCE - NOT OK
    Error=DATAFILE 1 MUST BE RESTORED FROM BACKUP OLDER THAN SCN
    QUESTIONS
    Where did I go wrong?
    Could it be my rman backup didn't backup all necessary archive logs?
    How do I fix this and can I fix it using dbconsole?
    Also, is it still possible to fix the test server without loading any new files?
    Thanks!
    Kathie

    Hello,
    To answer your questions, it looks like your backup is out of sync with SCN for datafiles with your Oracle 11g database.
    What you need to do is first check the low SCN and current SCN for your database to that in your RMAN backup files.
    You can check backups in RMAN command line with
    RMAN> list backup;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1 349.08M DISK 00:01:14 24-JAN-08
    BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20080124T180119
    Piece Name: C:\ORACLE\FLASHBACK\ORCL\BACKUPSET\2008_01_24\O1_MF_ANNNN_TA
    G20080124T180119_3SLJQOFO_.BKP
    List of Archived Logs in backup set 1
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 1 1030802 04-JAN-08 1053767 05-JAN-08
    1 2 1053767 05-JAN-08 1104812 06-JAN-08
    Then open another prompt window and SQL*PLUS session as sysdba privileged account:
    SQL> select name, current_scn from v$database;
    NAME CURRENT_SCN
    ORCL 4089528
    You need to make sure that you are trying to restore database with RMAN with a backup for the SCN numbers that are older than the current database SCN in database or Oracle will complain.
    Enterprise Manager dbconsole will work but nothing beats the power of a command line.
    Use the automated repair options for the Oracle 11g Database Repair advisors.
    1. Connect to RMAN
    rman target=/
    RMAN> list failure;
    RMAN> repair failure preview;
    RMAN> repair failure;
    For more details, Arup Nanda has a good overview of RMAN with Oracle 11g:
    http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-rman.html
    Hope this helps you out.
    -Ben
    Cheers,
    Ben Prusinski
    http://oracle-magician.blogspot.com/

  • ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

    Hello All,
    I have an instance on my LAB server. To explore more avenues in cloning a DB I did the following.
    1. On my Oracle 10g Instance I fired an large query which would take atleast an hour to execute.
    2. Opened another session and executed shu ABORT to shutdown the above instance abruptly.
    3. Took backup of datafiles, archive logs and redologs [ prior to shu abort, I had issued ALTER DATABASE BACKUP CONTROLFILE TO TRACE]
    Restoration steps:
    NOMOUNT with pfile edited to hold the name of the new DB_NAME
    Create control file script edited to reflect the new paths of datafile and redologs.
    MOunted succesfully.
    ALTER DATABASE OPEN RESETLOGS;
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1:
    'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\DATAFILE\DUPLISYSTEM_553LC8QX_.DBF'
    SQL> recover datafile 'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\DATAFILE\DUPLISYSTEM_553LC8QX_.DBF';
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 2962256 generated at 09/03/2009 12:06:49 needed for thread 1
    ORA-00289: suggestion :
    F:\ORACLE\COLD_BACKUP_TRIAL\SET2\FLASH_RECOVERY_AREA\DUPLI\ARCHIVELOG\2009_09_23
    \O1_MF_1_2_%U_.ARC
    ORA-00280: change 2962256 for thread 1 is in sequence #2
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    F:\oracle\cold_backup_trial\SET2\ONLINELOG_BK\O1_MF_3_553LGCH3_.log
    ORA-00342: archived log does not have expected resetlogs SCN 2933995
    ORA-00334: archived log:
    'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\ONLINELOG_BK\O1_MF_3_553LGCH3_.LOG'
    I didn't find the file it was suggesting so I tried many combinations of providing the right recovery file name :-- All the latest Archive logs and Redologs in my backup.
    Still the recovery is not successful. Please let me know how can I recover my DATABASE.
    Many thanks in advance.
    Regards,
    Valli

    Greetings,
    If I understood, you basically have a copy of a primary database and the redo log archives of this pretty same database, you have backed up the control file of this primary database, edited it pointing all paths of your datafiles to the new location but renaming the instance name.
    I am assuming that you have edited the first line of your control file to something like "CREATE CONTROLFILE SET DATABASE "DB02" RESETLOGS ARCHIVELOG", in this case are you sure that the redolog archives have not loose the sequence? In this case it will ask more and more archives and it will never end, take a look at the date and time of the thread that your instance is asking for recovery. Is your instance a production database? If it is NOT production and you are SURE that the database is completely recovered and is asking for redolog files that does not even exist you can try to add the ALLOWRESETLOGS_CORRUPTION=TRUE to your init.ora and open the db... This solution is not recommended and you should never use it on production instances... take this hint as a LAST effort to bring your db online.
    Regards,
    Bruno Carvalho

  • Recovery using Full BCV backup & archive logs

    Hello DBA's ,
    I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
    Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
    Kindly update me- Can I go for following recovery steps for above scenario.
    1) Install ORACLE software on new server.
    2) Restore the last Sunday's FULL BCV (Hot backup)
    3) Restore the archive log from last Sunday's Full BCV backup.
    4) Restore the latest backed up control file.
    5) Mount the database.
    6) Recover the database using backed up control file & archive logs.
    7) Open the database with RESETLOGS option.
    Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
    I want to test this scenario bcz.
    a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
    b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
    c) Currently we are not thinking for any another Backup options.
    OS platform -- SOLARIS 10
    Database version -- ORACLE 9i/10g
    Atul.

    Hello everybody ....
    Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
    ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
    1
    ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
    ORA-00280: change 7001791222 for thread 1 is in sequence #9623
    ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
    for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
    1
    ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
    ORA-00280: change 7001816252 for thread 1 is in sequence #9624
    ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
    for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    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/EPR/sapdata1/system_1/system.data1'
    SQL> SQL> SQL> SQL> SQL> SQL> SQL>
    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: '/oracle/EPR/sapdata1/system_1/system.data1'
    So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
    Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
    I want to recover my database upto Saturday then What should I do ?
    Please help me out !
    Atul.

  • Backup controlfile to trace as 'c:\prod_ctl.txt'

    Hi All,
    11.2.0.1
    I am examining the output of the trace file, because I want to simulate or test this process.
    This file has two(2) sets of command. one(1) is for the intact online logs and the other one(1) is for damage online logs.
    Questions:
    1. What do u mean by damage online logs. does this mean that i lost all these redo files:
    LOGFILE
      GROUP 1 'D:\APP\PROD\ORADATA\ORCL\REDO01.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 2 'D:\APP\PROD\ORADATA\ORCL\REDO02.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 3 'D:\APP\PROD\ORADATA\ORCL\REDO03.LOG'  SIZE 50M BLOCKSIZE 512
    2. Why is that the two(2) sets are just the same set of commands? except for backup controlfile and open resetlogs?
    3. Do I need RMAN backup to run this recovery statements?
    Thanks,
    pK
    ========
    -- The following are current System-scope REDO Log Archival related
    -- parameters and can be included in the database initialization file.
    -- LOG_ARCHIVE_DEST=''
    -- LOG_ARCHIVE_DUPLEX_DEST=''
    -- LOG_ARCHIVE_FORMAT=ARC%S_%R.%T
    -- DB_UNIQUE_NAME="orcl"
    -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
    -- LOG_ARCHIVE_MAX_PROCESSES=4
    -- STANDBY_FILE_MANAGEMENT=MANUAL
    -- STANDBY_ARCHIVE_DEST=%ORACLE_HOME%\RDBMS
    -- FAL_CLIENT=''
    -- FAL_SERVER=''
    -- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
    -- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
    -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
    -- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
    -- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
    -- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
    -- LOG_ARCHIVE_DEST_STATE_1=ENABLE
    -- Below are two sets of SQL statements, each of which creates a new
    -- control file and uses it to open the database. The first set opens
    -- the database with the NORESETLOGS option and should be used only if
    -- the current versions of all online logs are available. The second
    -- set opens the database with the RESETLOGS option and should be used
    -- if online logs are unavailable.
    -- The appropriate set of statements can be copied from the trace into
    -- a script file, edited as necessary, and executed when there is a
    -- need to re-create the control file.
    --     Set #1. NORESETLOGS case
    -- The following commands will create a new control file and use it
    -- to open the database.
    -- Data used by Recovery Manager will be lost.
    -- Additional logs may be required for media recovery of offline
    -- Use this only if the current versions of all online logs are
    -- available.
    -- After mounting the created controlfile, the following SQL
    -- statement will place the database in the appropriate
    -- protection mode:
    --  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS  NOARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 292
    LOGFILE
      GROUP 1 'D:\APP\PROD\ORADATA\ORCL\REDO01.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 2 'D:\APP\PROD\ORADATA\ORCL\REDO02.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 3 'D:\APP\PROD\ORADATA\ORCL\REDO03.LOG'  SIZE 50M BLOCKSIZE 512
    -- STANDBY LOGFILE
    DATAFILE
      'D:\APP\PROD\ORADATA\ORCL\SYSTEM01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\SYSAUX01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\UNDOTBS01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\USERS01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\EXAMPLE01.DBF'
    CHARACTER SET WE8MSWIN1252
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE 'D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_.ARC';
    -- ALTER DATABASE REGISTER LOGFILE 'D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_.ARC';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    -- Database can now be opened normally.
    ALTER DATABASE OPEN;
    -- Commands to add tempfiles to temporary tablespaces.
    -- Online tempfiles have complete space information.
    -- Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\APP\PROD\ORADATA\ORCL\TEMP01.DBF'
         SIZE 20971520  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    -- End of tempfile additions.
    --     Set #2. RESETLOGS case
    -- The following commands will create a new control file and use it
    -- to open the database.
    -- Data used by Recovery Manager will be lost.
    -- The contents of online logs will be lost and all backups will
    -- be invalidated. Use this only if online logs are damaged.
    -- After mounting the created controlfile, the following SQL
    -- statement will place the database in the appropriate
    -- protection mode:
    --  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS  NOARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 292
    LOGFILE
      GROUP 1 'D:\APP\PROD\ORADATA\ORCL\REDO01.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 2 'D:\APP\PROD\ORADATA\ORCL\REDO02.LOG'  SIZE 50M BLOCKSIZE 512,
      GROUP 3 'D:\APP\PROD\ORADATA\ORCL\REDO03.LOG'  SIZE 50M BLOCKSIZE 512
    -- STANDBY LOGFILE
    DATAFILE
      'D:\APP\PROD\ORADATA\ORCL\SYSTEM01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\SYSAUX01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\UNDOTBS01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\USERS01.DBF',
      'D:\APP\PROD\ORADATA\ORCL\EXAMPLE01.DBF'
    CHARACTER SET WE8MSWIN1252
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE 'D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_.ARC';
    -- ALTER DATABASE REGISTER LOGFILE 'D:\APP\PROD\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_12_26\O1_MF_1_1_%U_.ARC';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE USING BACKUP CONTROLFILE
    -- Database can now be opened zeroing the online logs.
    ALTER DATABASE OPEN RESETLOGS;
    -- Commands to add tempfiles to temporary tablespaces.
    -- Online tempfiles have complete space information.
    -- Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\APP\PROD\ORADATA\ORCL\TEMP01.DBF'
         SIZE 20971520  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    -- End of tempfile additions.
    ===============,

    Hi ,
    As far as i understand  , one is with :
    CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS  NOARCHIVELOG
    and the other one is with :
    CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS  NOARCHIVELOG
    The first one (resetlogs) is useful when you are trying to open a database after incomplete recovery (during cloning for example) or while changing the name of the database after restoring and recovering a database during a clone process.
    The second one ( noresetlogs )is used when we have a consistent database and we are recreating the controlfile.
    In General , you may be using resetlogs while opening a cloned database after incomplete recovery.
    Regards
    Karan

  • Database Recovery using Archive files

    Dears,
    Due to some issue our database get crashed.
    We have saturday night offline backup and archive backup till yesterday night.
    We have restored offline backup and system is Up but it is on saturday night state.
    We want to apply these archive files to make the system state to current.
    In restore our control file also get replace with our saturday night control file status.
    We have copied our archive files in oraarch directory.
    Now when using brtools I am applying archive files:
    Command executing in brtools:
    recover from '/oracle/<SID>/oraarch' database
    it shows
    unknow command beginning
    No recovery required
    On sqlplus also when I execute
    sql>recover database;
    It shows no recovery required.
    When I give command:
    sql>recover database using backup control file;
    it ask for some {file name| AUTO | CANCEL}
    I give first file name of oraarch it shows "Can not access the file".
    File permissions are ok.
    I give AUTO, It also then do not do anything.
    Please suggest the correct method to make my system in latest current date.
    Shivam

    Hi Shivam,
    This is absolutely normal that during the restore your control files will be replaced by the old one which were backed up during database backup.
    Logic is that you can not apply the redolgs which are having the timestamps older than your  restored datafile's / controlfile's timestamp.
    If your DB is not yet opened, you can check the status of your database using below command which will tell you, till what timestamp your data is restored or currently available.
    select to_char(CHECKPOINT_TIME,'yyyy-mm-dd:hh24:mi:ss') from v$datafile where file#=1;
    >
    > From command I want to know "from backup control file"....Do SAP take backup of control file as in system only old is
    >
    > available.
    > Shivam
    >
    recover database using backup controlfile.....  this command does not backup the controlfile . this will make use of old controlfile only which came along with the restore  and start the recovery using this controlfile only.
    Its just make use of available controlfile ..No backup will be triggered.
    Please make a note that after DB restore; ..recovery is possible only in case database is not yet opened in OPEN state.
    Cheers !!!
    Ashish

  • Backup Controlfile - Lost information?

    Hello guys,
    if i made a backup of my controlfile, the following way:
    ALTER DATABASE BACKUP CONTROLFILE to 'location';Which information is getting lost (SCNs,etc) , if i create a backup controlfile? As far as i know it is not possible to perform a complete recovery with a backup controlfile - am i right?
    Is there any difference between a "backup controlfile" and a creation of a new controlfile out of a "controlfile to trace"?
    Maybe you have got some oracle documents or something else which describes that.
    Thanks and Regards
    Stefan

    Using a backup controlfile in any recovery situation means you will have to open the database with a resetlogs operation -but that doesn't mean you've just performed an incomplete recovery! In other words, a complete recovery with a backup controlfile is not a problem, but it will be performed a little differently from a "normal" complete recovery.
    If, for example, you lost all your controlfiles and one of your datafiles, you would restore the datafile from backup and you'd maybe restore a binary backup of the controlfile, too. The recovery would be 'recover database until cancel using backup controlfile', and you'd type 'cancel' once the last bit of redo had been applied from the current online log. You'd then 'alter database open resetlogs'. Despite the resetlogs, however, you'd have recovered every single committed transaction and the database would have been rolled forward to the time of the datafile loss... and those things are the hallmarks of a complete recovery.
    If you 'backup controlfile to 'somewhere/filename', that's an exact binary copy of the current controlfile, so nothing whatsoever is lost. The reason for having to do the 'until cancel', however, in a recovery situation is simply that the copy of the controlfile has a bit set in it that means 'I have no idea what redo has been generated after this time, so the user will have to tell you when to stop applying it'.
    It's that bit which makes the big difference between a binary backup of the controlfile and the backup of script instructions on how to re-create the file. A recovery performed by running the 'controlfile to trace' to create a new controlfile does NOT need to say 'using backup controlfile' (because it isn't: it's a new controlfile, not a backed up copy of one from the past), and it doesn't need to use the 'until cancel' syntax because it knows what the last piece of redo to be applied is: running the script causes SMON to consult the headers of all the datafiles and the contents of each of the online redo logs: the largest SCN found will then be assumed to be the 'age' of the database and the point at which recovery has to stop.

  • Need a help: how to recover using backup control file?

    Please a help:
    First computer
    1. I create a database
    2. put it in archive mode,
    3. shutdown and made a cold backup
    4. Created backup control file (alter database backup control file to trace)
    5. I started up and created some archived log files.
    Second Computer
    1. I copied all files created in the step 3 above except the control file
    2. I create all the same map directory on the 2nd computer as in the 1st computer
    3. I recreate the control file from the script got in the step 4 above
    4. I Copy archived log files generated at the step 5 in the local directory in the second computer
    5. I set the logsource and set the autorecovery to on
    6. I recover the database: RECOVER DATABASE USING BACKUP CONTROL FILE UNTIL CANCEL
    Error got:
    the archived log file applied do not go beyond the first one?,How could I do to applied all archived log files copied from the first computer to the second computer to have the same data?
    Thank you very much

    archived log sequeces in the first computerSQL> select sequence#,first_change#,next_change# from v$log_history;
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
    1 553723 555484
    2 555484 557345
    Actions I did in the second Computer(after copied the former two archived log files from the 1st computer)
    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG
    2 MAXLOGFILES 16
    3 MAXLOGMEMBERS 3
    4 MAXDATAFILES 100
    5 MAXINSTANCES 8
    6 MAXLOGHISTORY 292
    7 LOGFILE
    8 GROUP 1 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG' SIZE 50M,
    9 GROUP 2 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG' SIZE 50M,
    10 GROUP 3 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG' SIZE 50M
    11 -- STANDBY LOGFILE
    12 DATAFILE
    13 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF',
    14 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF',
    15 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF',
    16 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF'
    17 CHARACTER SET WE8ISO8859P1
    18 ;
    Control file created.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 0
    Next log sequence to archive 0
    Current log sequence 0
    SQL> alter database archivelog;
    Database altered.
    SQL> set logsource C:\local_destination1_orcl
    SQL> set autorecovery on;
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 555611 generated at 01/18/2007 14:14:14 needed for thread 1
    ORA-00289: suggestion :
    C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC
    ORA-00280: change 555611 for thread 1 is in sequence #1
    ORA-00328: archived log ends at change 555483, need later change 555611
    ORA-00334: archived log:
    'C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC'
    Idon't know where the change 555611 is coming from?

  • Error in recovery after BACKUP DATABASE PLUS ARCHIVELOG

    Hi,
    With Oracle 9.2.0.6 on Unix Aix 5, I made:
    rman ...
    RUN
    ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
    BACKUP DATABASE PLUS ARCHIVELOG;
    Copy files from /base/tempora/% to another server in a directory with the same name.
    Recreate the pfile and directory structure, and then
    rman...
    RUN
    ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
    restore controlfile to '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
    restore controlfile from '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
    sql 'alter database mount';
    restore database;
    recover database;
    sql 'alter database open resetlogs';
    release channel disk1;
    But rman fails at -> recover database; by asking an archive log 6 months old (and not in the backupset):
    ORA-00279: change 1224563589 generated at 02/09/2006 16:29:46 needed for thread
    1
    ORA-00289: suggestion : /base/.../arch/arch0000001819.arc
    ORA-00280: change 1224563589 for thread 1 is in sequence #1819
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log '/base/.../arch/arch0000001819.arc'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    Original base seems to works fine (can be stoped and restarted).
    I thought that this BACKUP DATABASE PLUS ARCHIVELOG would contain in itself all the data needed to restart the database. Database has been stopped and restarted last week with no problem and I regularly do full backup with RMAN and TSM (we are testing now backups without TSM for a spacial case).
    Has someone an idea of what's wrong?
    Thanks

    Hi,
    Thanks for taking care of my problem.
    When I try to do a set until sequence..., the RESTORE CONTROLFILE fails, telling it has nothing to restore. I think this is the same kind of problem I encounter with the full restore.
    Aniway, the restore being good, i try to finish the recover and it fails, asking for a very old archive. Is it possible a transaction to be active after so much time?
    In fact, I just decovered a file is in RECOVER status. I did an :
    alter database datafile '...' offline drop;
    since that, the recover is ok, from oracle (not rman):
    recover database using backup controlfile until cancel;
    Thanks again to everyone.
    Regards.

  • BACKUP AND RECOVERY USING RMAN

    제품 : ORACLE SERVER
    작성날짜 : 2003-08-04
    BACKUP AND RECOVERY USING RMAN
    ==============================
    1. Backup Method
    1.1 backing up in noarchivelog mode
    SVRMGR> shutdown;
    SVRMGR> startup mount
    rman을 가동시킨 후 다음을 수행
    run {
    # backup the database to disk
    allocate channel dev1 type disk;
    backup (database format '/oracle/backups/bp_%s_%p'); }
    1.2 Backing up databases and tablespaces in archivelog mode >
    - database 단위 backup script
    run {
    allocate channel dev1 type 'sbt_tape';
    backup skip offline (database format '/oracle/backups/%d_%u');
    release channel dev1;
    - tablespace 단위 backup script
    run {
    allocate channel dev1 type disk;
    backup
    (tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
    format '/oracle/backups/bp_%s_%p');
    - datafile 단위 backup script
    run { 
    allocate channel dev1 type disk;
    backup
    (datafile '?/dbs/t_dbs1.f'
    format '/oracle/backups/%d_%u');
    - control file backup script
    control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
    같은 방법으로도 백업받을 수 있다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (tablespace tbs_5 include current controlfile
    format '%d_%u');
    - archived logs backup script
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog from time 'Nov 13 1996 20:57:13'
    until time 'Nov 13 1996 21:06:05'
    all
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog low logseq 288 high logseq 301 thread 1
    all delete input
    format '%d_%u');
    - copying datafiles
    run {
    allocate channel dev1 type disk;
    copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
    - incremental backups
    새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
    반드시 수행한다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 0
    (database
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 1
    (database
    format '&d_%u');
    2. Recovery Method
    - tablespace recovery
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    sql "alter tablespace tbs_1 offline immediate" ;
    set newname for datafile 'disk7/oracle/tbs11.f'
    to 'disk9/oracle/tbs11.f' ;
    restore (tablespace tbs_1) ;
    switch datafile all ;
    recover tablespace tbs_1 ;
    sql "alter tablespace tbs_1 online" ;
    release channel dev1;
    release channel dev2;
    - point-in-time recovery
    TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
    data는 없는 temporary segemnt만 가지고 있음.
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    SVRMGR> shutdown abort;
    SVRMGR> startup nomount;
    run { 
    # recover database until 3pm after restoring tbs_1 to a new location
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    set until time 'Nov 15 1996 15:00:00'
    set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
    to '?/dbs/temp1.f' ;
    set newname for datafile '?/dbs/tbs_12.f'
    to '?/dbs/temp2.f' ;
    restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
    replicate controlfile from '/vobs/oracle/dbs/cf1.f';
    sql "alter database mount" ;
    restore database skip tablespace temp1;
    switch datafile all;
    recover database skip tablespace temp1;
    sql "alter database open resetlogs";
    sql "drop tablespace temp1";
    sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
    release channel dev1;
    release channel dev2;
    - 전체 데이타베이스를 복구하려 할때
    current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
    수 있다.
    replace script restore_recover_db_cf {
    execute script restore_cf;
    sql 'alter database mount';
    execute script restore_db;
    execute script recover_db;
    sql 'alter database open resetlogs';
    replace script alloc_1_disk {
    allocate channel d1 type disk;
    setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
    replace script rel_1_disk {
    release channel d1;
    replace script restore_cf {
    execute script alloc_1_disk;
    restore
    controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    replicate
    controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    execute script rel_1_disk;
    replace script restore_db {
    execute script alloc_1_disk;
    restore
    (database);
    execute script rel_1_disk;
    replace script recover_db {
    execute script alloc_1_disk;
    recover
    database;
    execute script rel_1_disk;
    Reference Documents
    <Note:104796.1>

    Hi Alok,
    why there is a need for standby here? you mean to say standby db?
    what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

Maybe you are looking for

  • Converting into widescreen

    i wonder if you guys could help me out with something on imovie 6?? i want video footage from my canon ixus 65 camera to be in widescreen in a movie project. according to imovie help as long as im importing it into a movie that is set to widescreen i

  • SuPM - Data from SAP BW Query(Automatic) and Manual not displayed in KPI

    Dear Forum, I am also, currently working on a project implementing BO SuPM Version 1.0. Landscape is ECC -> BI -> SuPM dashboards. I have created a KPI in SuPM dashboard. Case 1 : Automatic data collection - This KPI is marked for Automatic data coll

  • Firefox crashes after clean install as well

    AvailablePageFile: 4165484544 AvailablePhysicalMemory: 2321932288 AvailableVirtualMemory: 2046500864 BlockedDllList: BreakpadReserveAddress: 56623104 BreakpadReserveSize: 41943040 BuildID: 20150122214805 CrashTime: 1423444970 InstallTime: 1422331294

  • PRA (Production Revenue Accounting)

    Hi Guru's, Can any body help me, what is the PRA(Production Revenue Accounting) in SAP Fi/Co? is it submodule or ? Thanks&Regards, Veera

  • Problem in running j2ee programs with SSL: SSL context init failed : cannot

    Hi, I am just trying to run some servlet program that creates some SSL socket to communicate with a server. I have configured my java.security file but when i run my rpogram i get this error SSL context init failed : cannot recover key.i am using Sun