Incomplete recovery 10g

hi all,
i am confise when i read the document 10g about incompltete recovery
hte document said when you take incomplete recovery take full cold backup and after not take backup
can you tell me why i yake backup before ??? what advantage when not take full backup after complete incomplete recovery???
pleasee advice MANY THANKS

861100 wrote:
hi all,
i am confise when i read the document 10g about incompltete recovery
hte document said when you take incomplete recovery take full cold backup and after not take backup>
can you tell me why i yake backup before ??? what advantage when not take full backup after complete incomplete recovery???
pleasee advice MANY THANKSpost URL to this document so we can read what you read

Similar Messages

  • Incomplete recovery in Oracle 10g

    hello,
    I have been trying Incomplete recovery in oracle 10g. The steps i did were.
    1. Set the database in archivelog mode.
    2. shutdown immediate
    3. Take physical copies of control files, datafiles and redo files
    4. open the database.
    5. Insert three rows in test table and commit. (and note the time )
    6. shutdown abort
    7. copy the restored datafiles to the desired location
    8. startup mount
    9 recover database until time (the time noted in step 5)
    10. alter database open resetlogs
    After doing this, i still do not get the three records inserted in step 5.
    Can anyone suggest why this is so ? am i missing something. ?
    Thanx.
    Trupti

    Hello,
    Thank you for the prompt reply.
    I did what you suggested. Here are the output.
    16:17:52 SQL> select * from testing.test;
    NO
    1
    2
    3
    4
    17:09:26 SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    *** Here i took a backup of all files.
    17:10:16 SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 788224 bytes
    Variable Size 66058496 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 262144 bytes
    Database mounted.
    17:13:45 SQL> alter database open;
    Database altered.
    17:14:07 SQL> alter system switch logfile;
    System altered.
    17:14:17 SQL> select * from testing.test;
    NO
    1
    2
    3
    4
    17:14:25 SQL> insert into testing.test values(5);
    1 row created.
    17:14:40 SQL> insert into testing.test values(6);
    1 row created.
    17:14:43 SQL> insert into testing.test values(7);
    1 row created.
    17:14:45 SQL> commit;
    Commit complete.
    17:14:47 SQL> alter system switch logfile;
    System altered.
    17:14:50 SQL> insert into testing.test values(8);
    1 row created.
    17:14:55 SQL> insert into testing.test values(9);
    1 row created.
    17:14:57 SQL> insert into testing.test values(10);
    1 row created.
    17:15:00 SQL> commit;
    Commit complete.
    17:15:02 SQL> alter system switch logfile;
    System altered.
    17:15:04 SQL> shutdown abort;
    ORACLE instance shut down.
    *** Here i restored the datafiles
    17:15:15 SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 788224 bytes
    Variable Size 66058496 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 262144 bytes
    Database mounted.
    17:18:09 SQL> recover database until time '2004-12-05:17:14:45';
    ORA-00279: change 402561 generated at 12/05/2004 17:10:03 needed for thread 1
    ORA-00289: suggestion :
    G:\ORACLE10G\ORADATA\NEWTEST\ARCHIVE\ARC00002_0544119450.001
    ORA-00280: change 402561 for thread 1 is in sequence #2
    17:18:43 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    Media recovery complete.
    17:19:20 SQL>
    17:19:51 SQL> alter database open resetlogs;
    Database altered.
    17:20:33 SQL> select * from testing.test;
    NO
    1
    2
    3
    4

  • Datafile Incomplete recovery

    Hi,
    I am using oracle database 10g(10.2.0.10) in RHEL5. I want to perform a point in time recovery a datafile from backup. Through RMAN i issued the following command
    RMAN> run{           
    2> sql "alter session set nls_date_format=''dd-mon-yyyy hh24:mi:ss''";
    3> set until time '21-aug-2011 13:04:00';
    4> restore datafile 4;
    5> recover datafile 4;
    6> alter database open resetlogs;}
    But RMAN performed complete recovery. Again i deleted the datafile and restore the datafile from backup. Now i issued the following command in SQL prompt
    SQL> alter session set nls_date_format='dd-mon-yyyy hh24:mi:ss';
    Session altered.
    SQL>recover datafile '/u01/app/oracle/oradata/ORATESTDB/datafile/o1_mf_users_751h7fmh_.dbf' UNTIL TIME '21-aug-2011 13:04:00';
    ORA-00274: illegal recovery option UNTIL
    It shows the above error. But i am able to perform Incomplete recovery of whole database using the same RMAN command as shown above.
    Does datafile point-in-time recovery is not possible?????? or Is there anything wrong in my approach?????
    Regards,
    007

    A Datafile cannot be recovered to a point in time that is incosistent with the rest of the database.
    (why ? Data Integrity !!!! A table with multiple extents may span multiple datafiles. You cannot have some extents with data as of 12:05 and other extents in another datafile recovered with data as of 10:05 !! Even if it is a single datafile tablespace, you will be violating referential integrity (whether enforced or not) if, say, the SALES table has entries upto 12:05 but the SALES_LINES table has entries upto 10:05 !!)
    You can do a Tablespace Point In Time Recovery using an Auxiliary Instance and then copy the whole tablespace back. You have to ensure that Integrity is maintained.
    Hemant K Chitale

  • Incomplete recovery after open resetlogs

    hi gurus
    Every sunday,consistent backups are performed on your database.Because of a user error,you performed an incomplete recovery on Tuesday and opened the database with RESETLOGS option.
    A user error occurs again on Thursday,whick necessitates an incomplete recovery.Sunday's bakcup is the most recent backup avaliable.
    what would you do in this scenario?
    A. recovery cannot be performed because backup was not performed after the last incomplete recovery.
    B. restore all backups from Sunday's backup,and then perform an incomplete recovery up to the point in time when the user error occured Thursday.
    C. restore all the files from Sunday's backup,and then recover up to the point in time when the RESETLOGS operation was performed on Tuesday.
    D. restore all the file from Sunday's backup, and open the database to reset the database to the point in time when the backup was performed on Sunday.
    I choose C but answer gives B. what do u think?
    thank u in advance.

    As of oracle 10g, it is possible to restore and recover across RESETLOGS operations: see http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr006.htm#sthref667. So B is correct for 10g or 11g.

  • Incomplete recovery

    You are using Oracle Database 10g. Which statement regarding an incomplete recovery is true?
    A.You do not need to restore all the data files.
    B.You do not need to open the database with theRESETLOGSoperation
    C.You do not need to perform a full backup after theRESETLOGSoperation.
    D.You do not need to recover all the data files to the same system change number (SCN).

    if you just remove one datafile ,will oracle allows you to start?
    Therotically option "C" is ok. but oracle will work without backup.
    Message was edited by:
    Ora-Lad
    Message was edited by:
    Ora-Lad

  • Can you help me? I meet  errors when I do incomplete recovery with RMAN

    In recover step, There are following errors:
    RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
    question:
    1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
    2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
    The following is the detail information:
    The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
    The following is the backup script:
    run {
    allocate channel 'dev_0' type 'sbt_tape'
    parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
    backup incremental level 0 filesperset 1
    format 'ora8i_online<db01_%s:%t:%p>.dbf'
    database
    include current controlfile
    archivelog all delete input;
    I use it to do a full backup on July 16th,17th successfully.
    And I use the following scripts to do incomplete recovery:
    run {
    allocate channel 'dev_0' type 'sbt_tape'
    parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
    sql "alter database mount";
    set until time ='17.07.2004';
    restore database;
    recover database;
    sql "alter database open resetlogs";
    sql "alter database open";
    There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: dev_0
    RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
    RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
    RMAN-03022: compiling command: sql
    RMAN-06162: sql statement: alter database mount
    RMAN-03023: executing command: sql
    RMAN-03022: compiling command: set
    RMAN-03022: compiling command: restore
    RMAN-03022: compiling command: IRESTORE
    RMAN-03023: executing command: IRESTORE
    RMAN-08016: channel dev_0: starting datafile backupset restore
    RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
    RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
    RMAN-08016: channel dev_0: starting datafile backupset restore
    RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
    RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
    RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
    RMAN-08023: channel dev_0: restored backup piece 1
    RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
    RMAN-08024: channel dev_0: restore complete
    RMAN-08023: channel dev_0: restored backup piece 1
    RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
    RMAN-08024: channel dev_0: restore complete
    RMAN-03022: compiling command: recover
    RMAN-03022: compiling command: recover(1)
    RMAN-03022: compiling command: recover(2)
    RMAN-03022: compiling command: recover(3)
    RMAN-03023: executing command: recover(3)
    RMAN-08054: starting media recovery
    RMAN-03022: compiling command: recover(4)
    RMAN-03026: error recovery releasing channel resources
    RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
    RMAN-08031: released channel: dev_1
    RMAN-08031: released channel: dev_2
    RMAN-08031: released channel: dev_0
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover(4)
    RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
    ORA-06512: at line 1
    I repeat my questions:
    1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
    2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
    Can you help me ? Thank you.

    which o.s u are using i can't help you as i never worked on ver 8i,i can tell you incomplete recovery on oracle 9i on win 2000 server.
    thanks : alok kumar

  • Can you help me? I meet some errors when I do incomplete recovery with RMAN

    In recover step, There are following errors:
    RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
    question:
    1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
    2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
    The following is the detail information:
    The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
    The following is the backup script:
    run {
    allocate channel 'dev_0' type 'sbt_tape'
    parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
    backup incremental level 0 filesperset 1
    format 'ora8i_online&lt;db01_%s:%t:%p&gt;.dbf'
    database
    include current controlfile
    archivelog all delete input;
    I use it to do a full backup on July 16th,17th successfully.
    And I use the following scripts to do incomplete recovery:
    run {
    allocate channel 'dev_0' type 'sbt_tape'
    parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
    sql "alter database mount";
    set until time ='17.07.2004';
    restore database;
    recover database;
    sql "alter database open resetlogs";
    sql "alter database open";
    There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: dev_0
    RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
    RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
    RMAN-03022: compiling command: sql
    RMAN-06162: sql statement: alter database mount
    RMAN-03023: executing command: sql
    RMAN-03022: compiling command: set
    RMAN-03022: compiling command: restore
    RMAN-03022: compiling command: IRESTORE
    RMAN-03023: executing command: IRESTORE
    RMAN-08016: channel dev_0: starting datafile backupset restore
    RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
    RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
    RMAN-08016: channel dev_0: starting datafile backupset restore
    RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
    RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
    RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
    RMAN-08023: channel dev_0: restored backup piece 1
    RMAN-08511: piece handle=netace_ora8i_online&lt;db01_2180:531623409:1&gt;.dbf tag=null params=NULL
    RMAN-08024: channel dev_0: restore complete
    RMAN-08023: channel dev_0: restored backup piece 1
    RMAN-08511: piece handle=netace_ora8i_online&lt;db01_2212:531623994:1&gt;.dbf tag=null params=NULL
    RMAN-08024: channel dev_0: restore complete
    RMAN-03022: compiling command: recover
    RMAN-03022: compiling command: recover(1)
    RMAN-03022: compiling command: recover(2)
    RMAN-03022: compiling command: recover(3)
    RMAN-03023: executing command: recover(3)
    RMAN-08054: starting media recovery
    RMAN-03022: compiling command: recover(4)
    RMAN-03026: error recovery releasing channel resources
    RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
    RMAN-08031: released channel: dev_1
    RMAN-08031: released channel: dev_2
    RMAN-08031: released channel: dev_0
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover(4)
    RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
    ORA-06512: at line 1
    I repeat my questions:
    1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
    2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
    Can you help me ? Thank you.

    You are correct. In RMAN8i, you should add the "alter system archive log current; command before you backup the archive logs.
    You are running into the case where Oracle needs additional redo to make the database consistent that was located in the current online log at the time of the backup.
    If you set UNTIL TIME to an earlier time does the recover work?
    In Oracle9i, if you issue the command, "backup database plus archive logs", RMAN will automatically archive the current online log before performing the archive log backups.
    Thanks, Tammy

  • An error occurred during the process of recovery(incomplete recovery)

    Hi,
    I have a HP envy m6 1154ez. When I tried to restore to factory default I have an error incomplete recovery
    Can someone tell me how to fix this or what needs to be done to get my Windows working again, any help would be greatly appreciated.
    Report an error,
    Component: Windows 8 Preinstall Diagnostic Tools - TDC
    Timing: FactoryUpdate
    Regional SKU: No
    RCTO Image: No
    Error: Mismatched option code (LOC#ACB) for dash code (-BGx)
    Error: Option code LOC#ACB should use dash code -25x
    Next Step: Please dash image SKU number with xxxxxx-25x
    Next Step: Or change LOC# in SKU Number or CTO Localization Code via EEPROM
    [ 0:17:59.87] ------------------------------------------------------------------------------------------
    ***CTO Error condition has been dtected in [Factory Update] phase !! ***
    [ 0:17:59.87] Suggest to create PIN-log and send to TWN PDC NB-PreinPM for further analysis ...
    [ 0:17:59.87] ------------------------------------------------------------------------------------------
    [ 0:16:27.91] Start BBOffline.cmd...
    UPDrv=[C:]
    [ 0:16:27.92] Set UIA Error Code to 951
    [ 0:16:28.12] Delete [FBI] folder.
    [ 0:16:28.14] WinPE is 64bit.
    [ 0:16:37.29] Starts [FixUps].
    [ 0:16:37.34] ---------------------------------------------------------------------
    [ 0:16:37.34] FixUps.cmd...
    [ 0:16:40.59] FixUps.cmd completed...
    [ 0:16:40.59] ---------------------------------------------------------------------
    [ 0:16:40.59] Starts [Tweaks for SSRD].
    [ 0:16:40.63] ---------------------------------------------------------------------
    [ 0:16:40.63] SSRD Tweaks to change user default locale...
    [ 0:16:40.63] Copy C:\System.sav\Util\TDC\MCPP\FBIRES\FBIGRRES.DLL.
    [ 0:16:40.84] Run "Dism.exe /image:C:\ /Set-SKUIntlDefaults:de-DE ".
    [ 0:16:52.90] ---------------------------------------------------------------------
    [ 0:16:52.92] Launch PININST.exe for Offline ...
    [ 0:16:56.54] Starts [Sleep 10 sec].
    [ 0:17:06.58] Starts [Create RStoneFUpdate.INI].
    [ 0:17:07.18] Starts [create 1GB Pagefile for offline].
    Volume in drive C has no label.
    Volume Serial Number is 8025-9CBE
    Directory of C:\System.sav\bbv
    04/04/2015 12:17 AM 1,073,741,824 pagefile.sys
    1 File(s) 1,073,741,824 bytes
    0 Dir(s) 90,616,721,408 bytes free
    [ 0:17:07.28] Brand detection.
    [ 0:17:07.33] Customize error handling for Specialize ~ BBV1.
    0 file(s) copied.
    [ 0:17:07.34] ---------------------------------------------------------------------
    [ 0:17:17.11] Check Win 8 configuration...
    [ 0:17:18.11] Check system ID...
    [ 0:17:19.12] Check OS SKU...
    [ 0:17:20.12] Check option code...
    [ 0:17:21.12] Check brand name...
    SKU_DEF_COUNTRY=[203]
    SKU_DEF_SYS_LOC=[ru-RU]
    Reset country in administrator...
    Reset country in Default user...
    Reset System locale
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    Image Version: 6.2.9200.16384
    Reporting offline international settings.
    Default system UI language : de-DE
    System locale : ru-RU
    Default time zone : W. Europe Standard Time
    User locale for default user : de-DE
    Location : Russia (GEOID = 203)
    Active keyboard(s) : 0407:00000407
    Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)
    Installed language(s): de-DE
    Type : Fully localized language.
    Installed language(s): en-GB
    Type : Partially localized language, MUI type.
    Fallback Languages en-US
    Installed language(s): fr-FR
    Type : Fully localized language.
    Installed language(s): it-IT
    Type : Fully localized language.
    The operation completed successfully.
    Updated System Locale info...
    [ 0:17:34.16] Start PIN Tweaks...
    [ 0:17:35.20] ---------------------------------------------------------------------
    [ 0:17:35.20] PIN Tweaks to hide All for BurnBoot BBV and BBV2 on restored image...
    [ 0:17:35.20] ----------------------------------------
    [ 0:17:35.20] Tweaks for OOBE's Unattend.xml
    [ 0:17:35.20] to pick up the proper file...
    [ 0:17:35.20] ----------------------------------------
    [ 0:17:35.20] rename unattend.org to unattend.or_
    [ 0:17:35.24] ----------------------------------------
    [ 0:17:35.24] without Light Sensor..
    [ 0:17:35.24] ----------------------------------------
    [ 0:17:35.24] update unattend.reg for Minimized Image Recovery...
    [ 0:17:35.27] This is Restored image [RImage.flg]...
    [ 0:17:35.27] ---------------------------------------------------------------------
    [ 0:17:36.15] Start MIR Tweaks...
    [ 0:17:37.22] ---------------------------------------------------------------------
    [ 0:17:37.22] [MIR Tweaks] ...
    [ 0:17:37.22] ----------------------------------------
    [ 0:17:37.22] apply Device Path registry for MIR image
    [ 0:17:37.22] ----------------------------------------
    [ 0:17:38.21] ---------------------------------------------------------------------
    [ 0:17:43.18] Start Factory Update(s)...
    [ 0:17:55.19] Start QFE Offline installation...
    [ 0:17:59.78] PININST_OFF: PASSED...
    [ 0:17:59.80] Type C:\System.sav\Logs\BBFindEr.log...
    [ 0:17:59.80] Type C:\System.sav\Logs\BBFindE0.log...
    ---------- C:\SYSTEM.SAV\LOGS\PININST_OFF.LOG
    Result=PASSED
    [ 0:17:59.81] There was no QFE installation...
    [ 0:17:59.81] Check FUList.log if there is duplicate Desc...
    No duplication.
    [ 0:17:59.86] No Duplicated Desc is found... PASSED.
    [ 0:17:59.86] There was no Factory Update...

    Hi @artem98765,
    Welcome to the HP Forums!
    It is a terrific place to find answers and suggestions.
    For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
    I grasp that when you tried to do a recovery back to factory you received the error incomplete recovery.
    As you did not state if how you were doing the recovery I will include documentation for the process along with a troubleshooting document.
    HP PCs - Performing an HP system recovery (Windows 8)
    HP PCs - Troubleshooting HP System Recovery Problems (Windows 8)
    If you are still unable to complete the recovery please contact HP support for further assistance.
    Please call our technical support at 800 474 6836. If you live outside the US/Canada Region, please click the link below to get a support number for your region.
    World Wide Phone Support
    Good Luck!
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • A problem about incomplete recovery

    All,
    I'm a freshman for oracle knowledge and skill. I'm simulating the incomplete recovery for database. Here are my scenarios and steps:
    1. In database "db1", there is a table named "tb1" has 2 records, the whole database running on archive log mode and has 3 redo log groups(each group contains one member) ---- status "A"
    2. Make a cold backup for all datafiles, controlfiles and redo logs;
    3. startup database again, and insert 3 records into "tb1", then switch log file at least 3 times. Get the frist change number form latest archived log. ---- status "B"
    4. after the 3rd step over, drop a tablespace named "indx" and do a switching log file operation again.
    5. shutdow database immediate and restore all the backuped datafile and controlfiles, not including the redo logs and startup database with mount option.
    6. run recover command to execute the incomplete recovery to database.
    whatever using "recover until time '<almost close the drop operating time>" or "recover until change number", I only got the status "A" after open the database, not status "B". But as my understanding and some reference from books, it should return to status "B" which includes the newer 3 records.
    Now, I adhere some alert logs at below (the number 54878 is the latest change number in archived log files before dropping that tablespace)
    alter database recover until change 54878
    Tue Jul 03 17:30:34 2007
    Media Recovery Start
    Media Recovery Not Required
    Completed: alter database recover until change 54878
    Tue Jul 03 17:31:35 2007
    alter database open resetlogs
    Tue Jul 03 17:31:35 2007
    RESETLOGS after complete recovery through change 54742
    why the recovery use change number 54742 but not 54878 I expected. Did I go the correct steps for this incomplete recovery. Does anyone can give me some piece of advice to resolve this problem

    Are you using 'recover using backup controlfile'...???????????
    If not, it will take the restored controlfiles as the latest copy and will only recover up to the SCN in there.
    Using the above, Oracle will simply ignore the SCN in the controlfile, since it knows its an old controlfile and should recover beyond the restored controfile..

  • Incomplete Recovery After Drop Tablespace.

    Hi...some technical help required.
    I was trying a hands-on for incomplete recovery. That is drop a tablespace and then retrieve back until 1 second before drop statement.
    The Steps were like this...
    1) Shutdown Immediate;
    2) Copy all *.ctl, *.dbf, logfiles into a different folder <nis_back>
    3) Startup;
    4) Enter 3-4 Records and Commit. Table is in <USER> Tablespace.
    5) 3 times "alter system switch logfile;"
    5) drop tablespace users;
    6) shutdown;
    7) Check the Alter Log and find the time when tablespace dropped.
    Suppose time when dropped is -> 21-Aug 10:30:45 AM. (HH:MM:SS)
    7) copy back only *.dbf, *.ctl files from backup folder <nis_back>
    8) startup mount;
    9) alter database recover automatic until time '2002-08-21:10:30:40';
    10) <<Statement Process>> Message Comes.
    11) alter database open resetlogs;
    When I open the table into which I inserted records just before dropping the tablespace I dont see the records (Inseretd in Step - 4) but the tablespace is back.
    Now My Concern -> Why did the 3-4 record which I inserted in step 4 did not get restored from the archieve log ?
    Hope to hear from you all soon.
    Thanks in advance.
    Regards
    Nishit

    After step 5, try ALTER SYSTEM ARCHIVELOG ALL
    Naveen
    Hi...some technical help required.
    I was trying a hands-on for incomplete recovery. That is drop a tablespace and then retrieve back until 1 second before drop statement.
    The Steps were like this...
    1) Shutdown Immediate;
    2) Copy all *.ctl, *.dbf, logfiles into a different folder <nis_back>
    3) Startup;
    4) Enter 3-4 Records and Commit. Table is in <USER> Tablespace.
    5) 3 times "alter system switch logfile;"
    5) drop tablespace users;
    6) shutdown;
    7) Check the Alter Log and find the time when tablespace dropped.
    Suppose time when dropped is -> 21-Aug 10:30:45 AM. (HH:MM:SS)
    7) copy back only *.dbf, *.ctl files from backup folder <nis_back>
    8) startup mount;
    9) alter database recover automatic until time '2002-08-21:10:30:40';
    10) <<Statement Process>> Message Comes.
    11) alter database open resetlogs;
    When I open the table into which I inserted records just before dropping the tablespace I dont see the records (Inseretd in Step - 4) but the tablespace is back.
    Now My Concern -> Why did the 3-4 record which I inserted in step 4 did not get restored from the archieve log ?
    Hope to hear from you all soon.
    Thanks in advance.
    Regards
    Nishit

  • Clarification on Incomplete recovery

    Hi Friends,
    Just clarification on 2 Things on incomplete recovery.
    Undo tablespace (datafiles):
    I lost current undo tablespace datafile but i have datafiles from backup,archived logs,current control file,online redo log and still can i perform complete recovery ?
    because complete recovery means= restore datafiles from backup +roll forward (online redo logs which is available) and roll back (current undo datafile , the current file is not available but only the backup undo datafiles is available)
    so in this case how will the roll forward happen? so is this in complete recovery?
    Control Files:
    My control files got lost but i have control trace file , dbf files(inclusing undo),archived logs,online redo logs. in this case i won't lose any data but since i am recreating control file i will perform open reset logs (new incarnation) so is this considered as in complete recovery (though my data is intact - all committed but the DB is incarnated)
    so what is complete recovery?
    DB should not be incarnated? (or) DB should have only commited data (or) both
    Regards,
    DB

    839396 wrote:
    Hi Friends,
    Just clarification on 2 Things on incomplete recovery.
    Undo tablespace (datafiles):
    I lost current undo tablespace datafile but i have datafiles from backup,archived logs,current control file,online redo log and still can i perform complete recovery ?
    because complete recovery means= restore datafiles from backup +roll forward (online redo logs which is available) and roll back (current undo datafile , the current file is not available but only the backup undo datafiles is available)
    so in this case how will the roll forward happen? so is this in complete recovery? If you have all the back up filles, archive logs and you have lost the undo tablespace data file, you would be still doing the complete recovery only. What makes you think that it would be an incomplete recovery?
    >
    Control Files:
    My control files got lost but i have control trace file , dbf files(inclusing undo),archived logs,online redo logs. in this case i won't lose any data but since i am recreating control file i will perform open reset logs (new incarnation) so is this considered as in complete recovery (though my data is intact - all committed but the DB is incarnated)
    so what is complete recovery?
    DB should not be incarnated? (or) DB should have only commited data (or) bothRead the reply of Rp!
    Aman....

  • Incomplete Recovery and Read Only

    Ok, I seem to be missing something. I've performed an incoplete recovery to a specified SCN. Everything is great if I open the database with resetlogs. But, the documentation (see quote below) says I can open the database as read only to check the recovery before I do the "resetlogs". However, I get the error (RMAN-01009) when I try to open the database read only. Can anyone explain?
    Oracle Database Concepts (B14220-02) - 15 Backup and Recovery:
    Before using the OPEN RESETLOGS command to open the database in read/write mode after an incomplete recovery, it is a good idea to first open the database in read-only mode, and inspect the data to make sure that the database was recovered to the correct point. If the recovery was done to the wrong point, then it is easier to re-run the recovery if no OPEN RESETLOGS has been done. If you open the database read-only and discover that not enough recovery was done, then just run the recovery again to the desired time. If you discover that too much recovery was done, then you must restore the database again and re-run the recovery.
    The script I ran:
    run
    set until restore point r1;
    restore database;
    recover database;
    }

    To generate the exception RMAN-01009 it appears you are trying to open the database using RMAN ... try it with SQL*Plus ... and if you have a problem post the full error message not just your impression of it along with the corresponding section of the alert log and full version number.

  • Problem with RMAN incomplete recovery

    Oracle Version: 9i
    Operating System: Windows 2000
    I have a problem with RMAN incomplete recovery until sequence.
    According to my database structure ............
    SQL> SELECT GROUP#,SEQUENCE#,THREAD# FROM V$LOG;
    GROUP# SEQUENCE# THREAD#
    1 14 1
    2 13 1
    3 12 1
    I took the backup of backup of full database using RMAN and i am trying to recover like this:
    RUN
    ALLOCATE CHANNEL C1 TYPE DISK;
    SET UNTIL SEQUENCE 7 THREAD 1;
    RESTORE DATABASE;
    RECOVER DATABASE;
    ALTER DATABASE OPEN RESETLOGS;
    BUT i am getting a message saying there is no backup of DATAFILE 1,2,......10 to restore although my database is in archivelog mode and i took a backup.
    Yachendra

    Please consult v$backup_datafile.
    It will tell you when the file was backed up.
    RMAN will always search for a datafile backup prior to the logsequence or whatever is limiting the incomplete recovery.
    Likely when you made your backup Oracle was already past sequence 7.
    Sybrand Bakker
    Senior Oracle DBA

  • Incomplete Recovery Fails using Full hot backup & Archive logs !!

    Hello DBA's !!
    I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
    1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
    2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
    3) Restored all Hot backup files from Tape to Test Server.
    4) Restored all archive logs from tape to Test server.
    5) Restored Latest Binary Control file from Tape to Test Server.
    6) Now, Started recovery using following command from SQL prompt.
    SQL> recover database until cancel using backup controlfile;
    7) Open database after Recovery Completion using RESETLOGS option.
    Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
    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'
    Let me know What should be the reason behind recovery failure !
    Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
    Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
    Atul Patil.

    oh you made up a new thread so here again:
    there is nothing wrong.
    You restored your backup, archives etc.
    you started your recovery and oracle applyed all archives but the archive
    '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    does not exist because it represents your current online redo log file and that is not present.
    the recovery process cancels by itself.
    the solution is:
    restart your recovery process with:
    recover database until cancel using backup controlfile
    and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    type cancel!
    now you should be able to open your database with open resetlogs.

  • Incomplete recovery question

    Hi guys
    As a DBA, we must to know about all backup and recover strategies. Today i was trying to simulate a recover from a lost of current relog group.
    In order to deal with this situation, we need to perform an incomplete recovery.
    The following steps were used to simulate a lost of current redo log and recover from it
    1) Shutdown abort
    2) delete all redo log files
    3) open database to show there was an error in relog file
    4) replace the existng datafiles with backup datafiles
    5) recover database using backup control file until cancel
    6) alter database open resetlogs
    After the above steps, the database was able to operate as normal.
    After that, i tried to perform incremental level 0 (backup incremental level 0 database plus archivelog delete input) to backup the database and archive and i got an error message :
    "error identifying file c:\ARC00002.001"
    "unable to open file"
    "<OS 2 > The system cannot find the file specified"
    I am sure that the archived file does not exist at the first place_
    Can anyone tell me why this kind of error occur even you have successful performed incomplete recovery and how to solve this kind of situation.

    Unless you were sloppy enough to put all of your log groups into a single directory on a single disk and lucky enough to have something bad happen while the database was down what you did doesn't truly simulate reality.
    Here's reality.
    Scenario 1:
    1. Database is open and transactions are taking place ... code a simple PL/SQL loop
    2. Query the database and look at your log files status values in v$log
    3. Drop an inactive log
    4. Issue an ALTER SYSTEM SWITCH LOGFILE until something breaks.
    Scenario 2:
    1. Database is open and transactions are taking place ... code a simple PL/SQL loop
    2. Query the database and look at your log files status values in v$log
    3. Drop an active log
    4. Issue an ALTER SYSTEM SWITCH LOGFILE until something breaks.
    Scenario 1:
    1. Database is open and transactions are taking place ... code a simple PL/SQL loop
    2. Query the database and look at your log files status values in v$log
    3. Drop the current log
    4. Issue an ALTER SYSTEM SWITCH LOGFILE until something breaks.
    Be prepared to deal with all three scenarios.

Maybe you are looking for