Error in Database backup using RMAN.

Hi
While taking full online backup using RMAN i got the following error.
ORA-19566: exceeded limit of 0 corrupt blocks for file /oracle/DEV/sapdata2/dev640_6/dev640.data6
Please help me how to resolve this issue.

Hi,
Please perform DBverify Job and Also analyze the alert<SID>.log file for your Database to get more information about such logical or physical corruption.  You may require Block level recovery for the complained DB Files. Please refer this useful document " [Early Detection and Correction of Data Block Corruptions Using RMAN |http://www.ioug.org/client_files/members/select_pdf/04q4/RMAN.pdf]" and share the same with your Oracle DBA.
You can execute the following commands to get information about corrupted block(s), if its there.
select * from v$backup_corruption;
select * from v$database_block_corruption;
Regads,
Bhavik G. Shroff

Similar Messages

  • Database backup using RMAN

    Hello All,
    I am new to RMAN.
    I am trying to make some backups of my database using enterprise manager, so i choose to backup my database based on the Oracle-Suggested Backup schedule.
    I got the below command from EM:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA_OEM_LEVEL_0';
    backup incremental level 1 cumulative  copies=1 for recover of copy with tag 'ORA_OEM_LEVEL_0' database;
    }i have the below question:
    what does the above script do ? EM will create a job that will run it daily ? how can i check this job ? where is it logged?
    where and how can i check the already configured channels ? for ex: channel oem_disk_backup
    what does this script do ? recover copy of database with tag 'ORA_OEM_LEVEL_0' does it recover the database?
    What are the RMAN scripts (run block), to backup my database once per week (for ex on Sunday)as level 0 backup and every day as incremental level 1 cumulative backup ? Since I think that the above script will run a level 0 backup once on the first execution and then the remaining backups are level 1 Incremental backups
    Thanks and regards,

    NB wrote:
    Hello All,
    I am new to RMAN.
    I am trying to make some backups of my database using enterprise manager, so i choose to backup my database based on the Oracle-Suggested Backup schedule.
    I got the below command from EM:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA_OEM_LEVEL_0';
    backup incremental level 1 cumulative  copies=1 for recover of copy with tag 'ORA_OEM_LEVEL_0' database;
    }i have the below question:
    what does the above script do ? EM will create a job that will run it daily ? how can i check this job ? where is it logged?You can check the the view V$RMAN_BACKUP_JOB_DETAILS.
    where and how can i check the already configured channels ? for ex: channel oem_disk_backupConnect to RMAN and execute the command show all;
    what does this script do ? recover copy of database with tag 'ORA_OEM_LEVEL_0' does it recover the database?
    What are the RMAN scripts (run block), to backup my database once per week (for ex on Sunday)as level 0 backup and every day as incremental level 1 cumulative backup ? Since I think that the above script will run a level 0 backup once on the first execution and then the remaining backups are level 1 Incremental backupsYour script is doing a daily incremental updated backup. Every day, You are asking Oracle to update your image copy with latest changes of all redo as of yesterday. You are recovering your backup copies; see the following link;
    See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref408

  • Backup using RMAN

    Hi,
    I want to perform the first backup with RMAN and I used this command and I got error:
    RMAN> BACKUP AS COPY DATABASE;
    can not backup or copy active file in noarchivelog mode.
    But in order to turn on the log_mode to ARCHIVELOG, first I need to do shutdown the db and perform the backup. Right?
    So how can I get my first backup using RMAN if the log mode is in NOARCHIVELOG mode?
    I also performed controlfile autobackup on but I'm not sure the controlfiles are being backed up. How can I verify this and where I can find the controlfile backup file?
    Thanks,

    Hi
    Yes, you must shutdown the database and set it to start in ARCHIVELOG mode.
    After that you can connect to the rman catalog and the target database and execute a backup.
    eg. RMAN> backup database;
    You can search other example posted by me:
    eg.
    - Re: Backup with RMAN
    - Re: How do i set up this backup strategy?
    To be sure that you backed up your control file you can issue the rman-command:
    RMAN> list backup of controlfile summary;
    Bye, Aron

  • PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN

    제품 : RMAN
    작성날짜 : 2002-05-30
    PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN
    =====================================================
    PURPOSE
    RMAN을 이용하여 Test Backup을 수행하기 위한 정보를 제공한다.
    EXPLANATION
    8.1.7 부터 RMAN에서 BACKUP command에 VALIDATE keyword를 사용할 수 있게 되었다
    이 명령의 수행은 다음과 같은 작업을 수행한다.
    - Datafile의 physical and logical corruption을 check한다.
    - 모든 database file들이 존재하는지, 그리고 올바른 위치에 있는지를 검증한다.
    RMAN은 실제적으로 backupset을 생성하지 않는다 그러나 그것들이 backup될 수
    있는지 없는지를 결정하기 위해서 기술된 file들을 scan한다.
    BACKUP VALIDATE 는 backup job을 수행시 수행되는 것을 제외하고는
    RESTORE VALIDATE와 거의 비슷하다.
    EXAMPLE
    아래와 같은 command들을 수행하여 backup하고자 하는 database file과 archived redo
    log들이 실제로 backup될 수 있는지를 검증할 수 있다.
    RUN {
    ALLOCATE CHANNEL ch1 TYPE 'sbt_tape';
    BACKUP VALIDATE
    DATABASE
    ARCHIVELOG ALL;
    Note: MAXCORRUPT or PROXY parameter는 VALIDATE option과 함께 사용할 수 없다.
    REFERENCE DOCUMENTS
    NOTE:121109.1

    Clint,
    I ran the command lines you wrote me after i placed the database in Startup MOUNT state, RMAN gave error messages that the database needs to be open:
    RMAN> SQL 'ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE';
    sql statement: ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 11/04/2005 15:31:33
    RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
    ERTB2 OFFLINE IMMEDIATE
    ORA-01109: database not open
    Then I ran the same command lines after I opened the database, RMAN gave error messages that "offline immediate disallowed unless media recovery enabled":
    RMAN> SQL 'ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE';
    sql statement: ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 11/04/2005 15:48:17
    RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
    ERTBS2 OFFLINE IMMEDIATE
    ORA-01145: offline immediate disallowed unless media recovery enabled
    I am stuck again and need your help!
    Thank you,
    Mitra

  • Differences between using Data Pump to back up database and using RMAN ?

    what are differences between using Data Pump to back up database and using RMAN ? what is CONS and PROS ?
    Thanks

    Search for Database backup in
    http://docs.oracle.com/cd/B28359_01/server.111/b28318/backrec.htm#i1007289
    In short
    RMAN -> Physical backup.(copies of physical database files)
    Datapump -> Logical backup.(logical data such as tables,procedures)
    Docs for RMAN--
    http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmcncpt.htm#
    Docs for Datapump
    http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_overview.htm
    Edited by: Sunny kichloo on Jul 5, 2012 6:55 AM

  • Cold backup using RMAN

    Dear All,
    db_version :10.2.0.4
    os_version:Window 2003 server
    Environment:Test
    I wish to perform cold backup using RMAN for the same i want to know following :
    1. What is the script / command ?
    2. How to restore cold backup completely ( ex:- if i lost all my data,redo and archives )
    3. Is it mandatory to open the database in RESETLOG mode after recovery ( since i have a cold backup ) ?
    Thanks in advance

    A "Cold" Backup is called a "Consistent" Backup.
    See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref297
    Backup :
    From the RMAN command line :
    SHUTDOWN IMMEDIATE
    STARTUP MOUNT
    BACKUP DATABASE
    BACKUP CURRENT CONTROLFILE  -- to get the controlfile in a separate backupsetRestore :
    STARTUP MOUNT
    RESTORE DATABASE
    ALTER DATABASE OPENIf you use an SPFILE, you can have an SPFILE backup included automatically with the controlfile backupset with CONFIGURE CONTROLFILE AUTOBACKUP ON and CONFIGURE CONTROLFILE AUTOBACKUP FORMAT ...
    Read the documentation.
    Hemant K Chitale

  • Can u we take online redo log backups using RMAN......can any one guide me

    can u we take online redo log backups using RMAN.....in 1og

    'Backup' solution for online redo logs is multiplexing (members of a group on different independent drives).
    Werner

  • Can I Scheduled Backups Using RMAN ?

    Hi,
    Can I schedule Backups using RMAN without depending on Any O/S utilities....
    If ,Yes......Let Me Know How it sis possible.....
    Thanks In Advance.....
    Prasannakumar.

    Yes, easiest way is Enterprise Manager. Otherwise you have to define your own DBMS_SCHEDULER tasks.
    Werner

  • Performing database backup using SAPDBA

    Guys could u please let me know how to take whole database backup using SAPDBA to another hard disk attached to the system (i.e rather than taking the backupto /oracle/<SID>/sapbackup on the same system i want to take the backup to another harddisk attached to the same system?)
    should i change any parameter in init<SID>.DBA?

    You dont need to change the init<SID>.dba.
    Rather you need to change init<SID>.sap.
    make a copy of init<SID>.sap and save it as for e.g. init<SID>1.sap change the value of the following entries as follows.
    backup_root_dir=your desired directory
    stage_root_dir=your desired directory
    Now use this init<SID>1.sap as the profile parameter file in sapdba and your backup will be stored in the"your desired directory".

  • Implementing RAC database backup through RMAN and grid control.

    Hi...
    plz... can any one give me good document (metalink documents id or else) to implement RAC database backup through RMAN. and also grid document...

    user8943492 wrote:
    Hi...
    plz... can any one give me good document (metalink documents id or else) to implement RAC database backup through RMAN. and also grid document...Read below links
    http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/backup.htm#i443637
    http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/rmanops.htm#i474611
    http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/toc.htm

  • Error while taking backup  through RMAN in 10g XE

    While taking backup through RMAN in XE instance , an error comes out.
    The contents of oxe_backup_current file is as below :
    XE Backup Log
    Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 6 15:49:51 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: XE (DBID=2635631092)
    RMAN>
    echo set on
    RMAN> shutdown immediate;
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    RMAN> startup mount;
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area     805306368 bytes
    Fixed Size                     1261444 bytes
    Variable Size                209715324 bytes
    Database Buffers             591396864 bytes
    Redo Buffers                   2932736 bytes
    RMAN> configure retention policy to redundancy 2;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    new RMAN configuration parameters are successfully stored
    RMAN> configure controlfile autobackup format for device type disk clear;
    RMAN configuration parameters are successfully reset to default value
    RMAN> configure controlfile autobackup on;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    RMAN> sql "create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile";
    *sql statement: create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile*
    *RMAN-00571: ===========================================================*
    *RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
    *RMAN-00571: ===========================================================*
    *RMAN-03009: failure of sql command on default channel at 07/06/2011 15:50:57*
    *RMAN-11003: failure during parse/execution of SQL statement: create pfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora' from spfile*
    *ORA-27086: unable to lock file - already in use*
    *Linux Error: 11: Resource temporarily unavailable*
    Additional information: 8
    Additional information: 16476
    RMAN> backup as backupset device type disk database;
    Starting backup at 06-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=102 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00003 name=/usr/lib/oracle/xe/oradata/XE/sysaux.dbf
    input datafile fno=00005 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_log01.dbf
    input datafile fno=00006 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_lrg01.dbf
    input datafile fno=00001 name=/usr/lib/oracle/xe/oradata/XE/system.dbf
    input datafile fno=00009 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_log01.dbf
    input datafile fno=00010 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_lrg01.dbf
    input datafile fno=00002 name=/usr/lib/oracle/xe/oradata/XE/undo.dbf
    input datafile fno=00004 name=/usr/lib/oracle/xe/oradata/XE/users.dbf
    input datafile fno=00008 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_sml01.dbf
    input datafile fno=00012 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_sml01.dbf
    input datafile fno=00011 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_mdm01.dbf
    input datafile fno=00007 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_mdm01.dbf
    channel ORA_DISK_1: starting piece 1 at 06-JUL-11
    channel ORA_DISK_1: finished piece 1 at 06-JUL-11
    piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T155057_718dw649_.bkp tag=TAG20110706T155057 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
    Finished backup at 06-JUL-11
    Starting Control File and SPFILE Autobackup at 06-JUL-11
    piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755797849_718dwofy_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 06-JUL-11
    RMAN> configure controlfile autobackup off;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    new RMAN configuration parameters are successfully stored
    RMAN> alter database open;
    database opened
    RMAN> delete noprompt obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           3      06-JUL-11        
      Backup Piece       3      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp
    Backup Set           4      06-JUL-11        
      Backup Piece       4      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp
    deleted backup piece
    backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp recid=3 stamp=755789684
    deleted backup piece
    backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp recid=4 stamp=755789699
    Deleted 2 objects
    RMAN>
    Recovery Manager complete.
    RMAN error: See log for details.

    I think it is trying to overwrite exiting file. Either give a different name or cleanup the files in preferred location.

  • Error when I backup with rman plus archive log

    Hi All,
    I tried below command
    run {
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    BACKUP DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG DELETE ALL INPUT;
    and that show below error
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=259 instance=pimdb1 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=153 RECID=113 STAMP=705896703
    input archived log thread=1 sequence=154 RECID=116 STAMP=705983105
    input archived log thread=1 sequence=155 RECID=119 STAMP=706069504
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03002: failure of backup plus archivelog command at 12/21/2009 11:00:18
    ORA-03114: not connected to ORACLE
    There are RAC 11.1.0.6.0 on AIX 5.3 with ASM.
    Please advise,
    Thank you,
    Hiko

    ็Hi All,
    I tried backup archivelog again and show same error,
    Line: -----
    rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Mon Dec 21 14:48:29 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: PIMDB (DBID=3834713912)
    RMAN> run
    2> {
    3> backup archivelog all;
    4> }
    Starting backup at 21-DEC-09
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=275 instance=pimdb1 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=161 RECID=131 STAMP=706190624
    input archived log thread=1 sequence=162 RECID=133 STAMP=706200525
    input archived log thread=2 sequence=97 RECID=132 STAMP=706190625
    input archived log thread=2 sequence=98 RECID=134 STAMP=706200526
    channel ORA_DISK_1: starting piece 1 at 21-DEC-09
    channel ORA_DISK_1: finished piece 1 at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Fulldata_20091221_97_1.bck tag=TAG20091221T144854 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 21-DEC-09
    Starting Control File and SPFILE Autobackup at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Controlfile_c-3834713912-20091221-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03009: failure of REFAF command on default channel at 12/21/2009 14:59:33
    ORA-03114: not connected to ORACLE
    RMAN> exit
    Recovery Manager complete.
    Line: -----
    And I check in alert log file that show below error
    Line: -----
    Mon Dec 21 14:48:44 2009
    Thread 1 advanced to log sequence 163
    Current log# 1 seq# 163 mem# 0: +DATA/pimdb/onlinelog/group_1.282.698703549
    Mon Dec 21 14:49:17 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_ora_5095646.trc (incident=64044):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64044/pimdb1_ora_5095646_i64044.trc
    Mon Dec 21 14:49:31 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_m000_1831050.trc (incident=64163):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64163/pimdb1_m000_1831050_i64163.trc
    Mon Dec 21 14:49:33 2009
    Trace dumping is performing id=[cdmp_20091221144933]
    Mon Dec 21 14:49:34 2009
    Sweep Incident[64163]: completed
    Mon Dec 21 14:59:33 2009
    Process 0x70000020477df88 appears to be hung while dumping
    Current time = 1584185732, process death time = 1584124482 interval = 60000
    Attempting to kill process 0x70000020477df88 with OS pid = 5095646
    OSD kill succeeded for process 70000020477df88
    Line: -----
    Please advice,
    Thank you
    Hiko

  • Problem in performing multiple Point-In-Time Database Recovery using RMAN

    Hello Experts,
    I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
    Environment:
    Oracle 11g, ASM,
    Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
    Snapshot DiskGroups :
    Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
    Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
    Steps performed for point in time recovery:
    1. Restore control file from snapshot 2.
         RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
    2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
    3. Catalog data files from snapshot 1.
    4. Catalog archive logs from snapshot 2.
    5. Perform point in time recovery till given time.
         STARTUP MOUNT;
         RUN {
              SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
              SET UNTIL TIME "06-mar-2013 09:30:00";
              RESTORE DATABASE;
              RECOVER DATABASE;
              ALTER DATABASE OPEN RESETLOGS;
    Results:
    Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
    Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
    Starting recover at 28-FEB-13
    using channel ORA_DISK_1
    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/06/2013 11:10:57
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
    start until time 'MAR 06 2013 09:45:00'
    ORA-00283: recovery session canceled due to errors
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
    ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
    ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
    Doubts:
    1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
    3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
    However for this to work, I always need to keep the AutoBackup feature enabled.
    How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
    4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
    Please help me out in this issue.
    Thanks.

    992748 wrote:
    Hello experts,
    I'm little newbie to RMAN recovery. Please help me in these doubts:
    1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
    2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
    3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
    Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
    Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
    But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.

  • Validate backup using RMAN

    Hi,
    This is a 9i RAC environment. RMAN is used to take the backup. The database is running fine and backup is taken using cron 3 times a week. There is no error messages generated when the backup is taken.
    However, in the alert log file I noticed that there are corrupted blocks in the backup files. I tried to validate the backup using (restore database validate) but I ended up with erros. Then, I tried (validate backupset) to check the corruption and I am getting different errors. 2 of the backupsets says that the data file can not be verfied. 1 of the backupset throws ORA-06510: PL/SQL: unhandled user-defined exception
    Can anyone guide me with this problem?
    Thank you in advance

    Sorry,
    but there is one big problem: you don't backup your archivelogs!
    Apart from a series of redundant commands (about the only required command is 'backup database', the rest needs to be relegated to house keeping scripts), this script doesn't result in a valid backup at all!
    What I do is
    ORAENV_ASK="NO"
    export ORACLE_SID=${DB}
    . $ORAENV
    case ${TRACE:-""} in
    T) set -x ;;
    esac
    dg="`date +%a`"
    case "$dg" in
    Mon) LVL=0
    Tue|Wed|Thu|Sat|Sun) LVL=2
    Fri) LVL=1
    *) LVL=2
    esac
    echo $LVL
    exec 1>>$LOGFILE 2>&1 # redirect alle output naar de logfile
    # fase 1, maak een backup van de database. Bail out als dit fout gaat
    rman <<EOD
    connect target ${UID}
    set echo on;
    run
    backup incremental level ${LVL}
    tag="db${TIMESTAMP}" database filesperset=1
    format '${BACKUP_DIR}/${ORACLE_SID}/backup_%d_db_%T_%s_%p.bck'
    plus archivelog tag="arch${TIMESTAMP}"
    skip inaccessible
    format '${BACKUP_DIR}/${ORACLE_SID}/backup_%d_arch_%T_%s_%p.bck'
    restore database validate;
    And in my case I ran
    configure controlfile autobackup on, and I set the format appropiately.
    The main advantage ot this code is you can always use
    list backupset tag="db<yyyymmdd>"
    and you don't need to think about the tag.
    resync catalog is implicit with autobackup on;
    Autobackup is required anyway, as the autobackup saves you from loosing the catalog.
    backup database validate only ensures the database can be backed up (ie the corruption is not in the datafiles). It looks like in your case the corruption is in the backup.
    Obviously, due to legal regulations, I can not post the complete script.
    It is also a bit smarter than I have shown here. When this phase fails, it automatically deletes the backup, using the tag mechanism.
    Sybrand Bakker
    Senior Oracle DBA

  • Script for cold backup using RMAN

    Dear all,
    db_version:-10.2.0.4
    os_version:- Windows 2003 server
    I wish to schedule a script that will take cold backup of my database using RMAN.
    Any help is appreciated ..
    Edited by: user12000301 on May 18, 2011 5:02 AM

    Dear All,
    Thanks a lot for your valuable time :
    However i have managed to do it as follows :
    1. First i have configure the parameter of RMAN ( Since it is my UAT in Noarchive log mode), I have never tried RMAN cold backup on the same.
    Following is the out put of SHOW ALL;
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DB\RMAN_BKP\BACKUPS%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\DB\RMAN_BKP\BACKUPS\DB_%U.%r';
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\DB\RMAN_BKP\BACKUPS\SNCFDB.ORA';
    2. I have created a rman_cold_bkp.bat file which has following entry :
    cd c:\oracle10g\bin
    set oracle_sid=DB
    rman target system/*** @D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.rcv log=D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.log
    exit
    3. Whereas rman_cold_bkp.rcv file contains following contents:
    run
    allocate channel C1 device type disk;
    shutdown immediate;
    startup mount;
    backup database;
    alter database open;
    release channel C1;
    exit
    I did checked it and it;s working fine for me :-)
    Regards,
    Girish

Maybe you are looking for


HashFlare