Block corruption + Rman backup.

I know that when RMAN is in the process of backing up a datafile and when it encounters a corrupted block, rman updated several V$ views. My question is will the backup process run successfully even when corrupted block is found???
kumaresh

I believe the answer to your question is YES - RMAN will run and complete succesfully (and do what it is supposed to do) even when it encounters a corrupt block - each time RMAN runs, you will notice an entry in the alert_log file indicating that this block was 'passed through' during the regular back up process.
I work at a company where we have a corrupt block and where the only available solution is to re-install and restore from backups......(for the APPS portion of things)

Similar Messages

  • System datafile block corruption - no backups and database in NOARCHIVELOG mode

    Dear All,
    Database version - oracle 11.1 Enterprise
    OS - RHELinux 5.8
    What are the options of recovering from physical block corruption when there are no backup available to perform block media recovery?
    V$DATABASE_BLOCK_CORRUPTION reports two segments corrupted (please see attached image for details).
    1 table in system datafile - sys_fba_barrierscn
    1 index - (applicaiton index)
    What are my options?
    I know there is a possibility that the database will not restart after a shutdown due to corruption in system tablespace.
    Database is in noarchivelog mode. So online backups are not possible and there aren't any full backups either.
    I am thinking of below,
    1. Run dbms_repair with fix_block_corruption. - Still database startup might fail?
    2. Shutdown the database and take offline full backup with RMAN MAXCorrupt option.
    Appreciate your suggestions and advises.
    Thanks
    Stefan

    Thanks Sybrand,
    Agree with your first two suggestions .
    Also scheduled a expdp job tonight. (Only backup like thing they had was a expdp cron, but until today all the large tables were failing due to small undo_retention).
    Yes. Flashback is not used. So hopefully it will not affect the a database restart i guess?
    Related to dbms_repair, I was referring to - http://askdba.org/weblog/2010/08/physical-corruption-ora-1578-part-3/.
    Where DBMS_REPAIR.FIX_CORRUPT_BLOCKS and DBMS_REPAIR.SKIP_CORRUPT_BLOCKS used.
    Which i think will not use any redo.
    Thanks
    Stefan

  • How to check & resolve block corruption if no RMAN backup is there?

    *<<+MY Findings+>>*
    to check block corruption :
    (run command)
    select * from v$database_block_corruption;
    DB_VERIFY is useful in these situations:
    When block corruption is expected;
    Forecast any future problems w.r.t. database file/ block corruption;
    When you restore files from a tape. It will help knowing if the first file pulled from tape is corrupt, instead of spending hours to extract all of them.
    to check block corruption
    DBVerify
    C:\>dbv userid=nfadmin/nfadmin file=+DG1/nfdb/datafile/low_s_data.304.782536883 feedback=10000 blocksize=8192
    can use DBMS_REPAIR to detect and repair corrupt blocks in tables and indexes
    BEGIN
    DBMS_REPAIR.admin_tables (
    table_name => 'REPAIR_TABLE',
    table_type => DBMS_REPAIR.repair_table,
    action => DBMS_REPAIR.create_action,
    tablespace => 'USERS');
    DBMS_REPAIR.admin_tables (
    table_name => 'ORPHAN_KEY_TABLE',
    table_type => DBMS_REPAIR.orphan_table,
    action => DBMS_REPAIR.create_action,
    tablespace => 'USERS');
    END;
    Question* :::how to check & resolve block corruption if no RMAN backup is there?

    http://www.oracle.com/technetwork/database/focus-areas/availability/maa-datacorruption-bestpractices-396464.pdf
    http://www.oracle-base.com/articles/misc/detect-and-correct-corruption.php

  • Logical Block corruption - not enough RMAN backups

    I have to deal with logical block corruption but these guys do not have enough rman backups to go back enough to recover blocks.
    All bad blocks are in SYSAUX and it seems because of it EM doesn't work as it's suppose to do. I dropped and recreated EM repository hoping it will clean itself but .... no.
    Any ideas?
    Oracle Linux 4.7 i386
    Oracle 10.2.0.4

    OCCUPANT_NAME OCCUPANT_DESC SCHEMA_NAME MOVE_PROCEDURE MOVE_PROCEDURE_DESC SPACE_USAGE_KBYTES
    EM Enterprise Manager Repository SYSMAN emd_maintenance.move_em_tblspc Move Procedure for Enterprise Manager Repository 52800
    EM_MONITORING_USER Enterprise Manager Monitoring User DBSNMP *** MOVE PROCEDURE NOT APPLICABLE *** 1600

  • Rman backup with corrupted block

    Hello,
    Firstly - I have problem on non-production database 11.2.0.1.0, so I am not deeply worried about data. But I need to understand what happened with database backups and how to prevent such things in future.
    So - I have EM scheduled weekly full backup and daily incremental backups. Later there was problem with hardware and some corrupted blocks in database were found. The weekly backup ran without error and obsolete backups were deleted. Now it is not possible to "recover corruption list" because no backup without corruption exists (RMAN-06023: no backup or copy of datafile 6 found to restore). I am not worried about the lost data, but I need to find out how come the backup contains corrupted block.
    I have checked the data file using dbv utility
    DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
    DBV-00200: Block, DBA 27525766, already marked corrupt
    csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
    Page 2359942 failed with check code 6054
    DBVERIFY - Verification complete
    Total Pages Examined         : 3840000
    Total Pages Processed (Data) : 453896
    Total Pages Failing   (Data) : 1
    Total Pages Processed (Index): 2959104
    Total Pages Failing   (Index): 0
    Total Pages Processed (Other): 424025
    Total Pages Processed (Seg)  : 0
    Total Pages Failing   (Seg)  : 0
    Total Pages Empty            : 2975
    Total Pages Marked Corrupt   : 1
    Total Pages Influx           : 0
    Total Pages Encrypted        : 0
    Highest block SCN            : 2156227446 (1.2156227446)As you can see the datafile 6 - user03.dbf has errors. Also backups now contain errors.
    1) So how is it possible that the EM scheduled backup ran without problems and the backup now contains corrupted blocks. How to prevent this in future ? I know there is setting MAXCORRUPT. How can I check its current value ? How can I configure it using EM scheduled backups ?
    2) Secondly, meanwhile I studied the RMAN commands. So I have suspended EM backup jobs, and executed follwing command. And backup ran without error again. How is this possible, if data file users06.dbf has corrupted block ?
    Thanks !
    RMAN> run {
    set MAXCORRUPT for datafile 6 to 0;
    backup as compressed backupset datafile 6;
    2> 3> 4>
    executing command: SET MAX CORRUPT
    Starting backup at 07-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 07-NOV-12
    channel ORA_DISK_1: finished piece 1 at 07-NOV-12
    piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
    Finished backup at 07-NOV-12
    Starting Control File and SPFILE Autobackup at 07-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
    Finished Control File and SPFILE Autobackup at 07-NOV-12

    I have updated database to 11.2.0.3
    However, the problem still persists. rman backup went ok on broken file
    oracle@orcl-cluster:~> sqlplus
    SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 20 09:24:11 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Enter user-name: system
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
         FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
             6    2359942          1                  0 FRACTURED
            25    1855622          1                  0 FRACTURED
    oracle@orcl-cluster:~> rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue Nov 20 08:04:57 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ORCL (DBID=1253245572)
    RMAN> backup as compressed backupset datafile 6;
    Starting backup at 20-NOV-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1596 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=1568 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=2357 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=2341 device type=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: SID=86 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 20-NOV-12
    channel ORA_DISK_1: finished piece 1 at 20-NOV-12
    piece handle=/opt/oraBackup/rman/2rnqovpp_1_1 tag=TAG20121120T080513 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:10:35
    Finished backup at 20-NOV-12
    Starting Control File and SPFILE Autobackup at 20-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121120-00 comment=NONE
    Finished Control File and SPFILE Autobackup at 20-NOV-12
    RMAN> backup validate datafile 6;
    Starting backup at 20-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: backup set complete, elapsed time: 00:03:05
    List of Datafiles
    =================
    File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
    6    OK     1              2975         3840000         6489027926
      File Name: /opt/oracle/oradata/orcl/users03.dbf
      Block Type Blocks Failing Blocks Processed
      Data       0              453912
      Index      0              2959091
      Other      0              424022
    Finished backup at 20-NOV-12Edited by: kamilp on Nov 20, 2012 12:23 AM

  • Block corruption - cant restore from backup

    Hi,
    we have development database 11.2.0.1. There was problem with storage, and as a result there are two corrupted blocks in data files.
    SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    6 2359942 1 0 FRACTURED
    25 1855622 1 0 FRACTURED
    I have scheduled weekly full backup and daily incremental backup using EM so now I want to use rman to perform media recovery on corrupted blocks. However rman says there is no backup for affected data files (see below)
    RMAN> RECOVER CORRUPTION LIST;
    Starting recover at 03-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: restoring block(s)
    channel ORA_DISK_1: specifying block(s) to restore from backup set
    restoring blocks of datafile 00006
    channel ORA_DISK_1: reading from backup piece /opt/oraBackup/rman/i2npb3o9_1_1
    channel ORA_DISK_1: piece handle=/opt/oraBackup/rman/i2npb3o9_1_1 tag=BACKUP_FULL_110212103009
    channel ORA_DISK_1: restored block(s) from backup piece 1
    channel ORA_DISK_1: block restore complete, elapsed time: 00:42:35
    channel ORA_DISK_1: restoring block(s)
    channel ORA_DISK_1: specifying block(s) to restore from backup set
    restoring blocks of datafile 00025
    channel ORA_DISK_1: reading from backup piece /opt/oraBackup/rman/i9npbd5e_1_1
    channel ORA_DISK_1: piece handle=/opt/oraBackup/rman/i9npbd5e_1_1 tag=BACKUP_FULL_110212103009
    channel ORA_DISK_1: restored block(s) from backup piece 1
    channel ORA_DISK_1: block restore complete, elapsed time: 00:16:35
    failover to previous backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/03/2012 11:59:29
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 25 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    I dont understand this, because the backups are performed weekly and daily and all files are at their proper location. When I check the EM backup reports, I see COMPLETED for every weekly and daily backup.
    Anyone please could suggest how to repair the blocks from backups ?

    Hi people, I am back to this issue. I have found this in the database
    SQL> select * from v$backup_corruption;
         RECID      STAMP  SET_STAMP  SET_COUNT     PIECE#      FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# MAR CORRUPTIO
             1  796949262  796948233       9293          1          6    2359942          1                  0 NO  CORRUPT
             2  796953328  796949174       9300          1         25    1855622          1                  0 NO  CORRUPT
             3  797035604  797034635       9318          1          6    2359942          1                  0 NO  CORRUPT
             4  797039692  797035556       9325          1         25    1855622          1                  0 NO  CORRUPT
             5  797134390  797121030       9343          1          6    2359942          1                  0 NO  CORRUPT
             6  797137228  797134397       9368          1         25    1855622          1                  0 NO  CORRUPT
             7  797739951  797725854       9590          1          6    2359942          1                  0 NO  CORRUPT
             8  797744507  797739957       9597          1         25    1855622          1                  0 NO  CORRUPT
             9  798340269  798330633       9794          1          6    2359942          1                  0 NO  CORRUPT
            10  798343497  798340270       9801          1         25    1855622          1                  0 NO  CORRUPTSo the backup contains corrupted blocks. Right ? Older backups are already gone because of retention policy.
    I have set up the backup using Enterprise Manager - Schedule Backup.
    What I need to know is how to avoid taking backup with corrupted blocks in future. I need such backup to fail.
    Thank you for advices and regards.

  • Block corruption problem in alert and rman/dbv no show errors

    Hello, I'm new in Oracle's world. I have one problem with Oracle 10.2.0.4 (RHEL 5.6) x64. Archive redo-log enable
    In the alert.log, three days ago show (the server have kernel panic & rebooted):
    Mon Sep 24 18:18:17 2012
    Hex dump of (file 17, block 669888) in trace file xxxxxxxxxx.trc
    Corrupt block relative dba: 0x044a38c0 (file 17, block 669888)
    Bad check value found during buffer read
    Data in bad block:
    type: 6 format: 2 rdba: 0x044a38c0
    last change scn: 0x0000.14eb5309 seq: 0x1 flg: 0x04
    spare1: 0x0 spare2: 0x0 spare3: 0x0
    consistency value in tail: 0x53090601
    check value in block header: 0x6ea3
    computed block checksum: 0x2
    Reread of rdba: 0x044a38c0 (file 17, block 669888) found same corrupted data
    Mon Sep 24 18:18:19 2012
    Corrupt Block Found
    TSN = 23, TSNAME = TABLE_TSD1
    RFN = 17, BLK = 669888, RDBA = 71973056
    OBJN = 86908, OBJD = 86908, OBJECT = SYS_C0040110, SUBOBJECT =
    SEGMENT OWNER = SCHEMA1, SEGMENT TYPE = Index Segment
    Yesterday, we detected this error because SQL don't execute.
    The error repeat 47times and there is 6 different file-block combination (4 index of schemas, 1 of sys and ¡2 tables!)
    First, I launched expdp and exp of the one problematic schema. The export was fine, no errors while exporting, but in the alert.log show one block corruption. Should exp and expd show error and stop?
    Next, I used dbv and verify all dbfs. Only show 2 blocks error in two datafiles (indexes).
    Next, I used RMAN:
    A) check database: no error.
    B) validate database: error in two blocks (logical error) and different from the 6 in alert.log. This two blocks are indexes.
    I re-create this two indexes. When i re-create, the block error disappear (not inmediate, suppose that disappear when block was rewrite). Now dbv and rman show no error.
    I have read one note about types of error, other about procedures if db is in archivelog/noarchivelog. Also if object is index or table. But I find anything about auto-repair corrupt blocks in Oracle or why now the 6 block error are solved. I don't know if two tables with two block corrupt lost rows or not.
    Appreciate any help.
    Regards

    Hello Fran. Result of query before rebuild problematic INDEXES:
    SQL> select * from V$database_block_corruption;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    3 98857 1 390928740 LOGICAL
    9 48632 1 390325900 LOGICAL
    When I ran RMAN first time to check blocks, it filled V$database_block_corruption with two bad blocks. Different from the 6 errors from alert.:
    RMAN> backup validate check logical database;
    Error backing up file 9, block 48632: logical corruption
    Error backing up file 3, block 98857: logical corruption
    I extracted index name from each block and I re-created it. Also, I created a temporary table in tablespace's datafile to fill blocks empty. Problem solved. Rman / dbv show no error.
    I'm searching for similar experiences and found: Re: Data in bad block
    First 6 bad checksum errors in alert.log disappear with any visible problem?
    Can I sure that DB is fine if RMAN and DBV show no errors?
    Thank you very much
    Edited by: user7755509 on 27-sep-2012 5:43

  • RMAN problem with block corruption

    Hi
    I have problem with the block corruption in one of the database .
    here is the error message .
    ora-01578:oracle data block corrupted (file# 10,block # 55309) ora-01110: data file 10:
    '/db/gist1/data/gist1_gis_nologging_01.dbf' ora-26040: data block was loaded using the NOLOGGING option .
    gisq SQL> select * from v$database_block_corruption;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    10 11 126 3754364971 LOGICAL
    RMAN> blockrecover datafile 10 block 11;
    Starting blockrecover at 14/DEC/2012 16:25:48
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of blockrecover command at 12/14/2012 16:25:48
    RMAN-05009: Block Media Recovery requires Enterprise Edition
    Could some one help me in providing solution for this . we we have standard addition only .
    Thanks in advance ...

    It appears that there was a NOLOGGING operation on an object that resides in '/db/gist1/data/gist1_gis_nologging_01.dbf' .
    NOLOGGING operations, as the name suggests, do generate limited redo log, which makes the objects affected by them non-recoverable.
    RMAN Blockrecover, as far as I understand, uses full and archivelog backup to perform the block recovery. Since the archivelog backup does not store any changes related to the NOLOGGING operation, then Blockrecover would not be able to help you even if you were licensed.
    You can try to restore the object as of the most recent full backup…
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • RMAN Block Corruption

    Hi,
    i am using oracle 11g R1 database in windows 2003 server. i need to stimulate two scenario
    1 . I want to corrupt a block and identify the corrupt block using RMAN.
    2 . I need to corrupt a block and while taking backup using RMAN it should tell that the block is corrupt.
    can anyone tell me how to do the above scenario
    Regards,
    007

    007 wrote:
    Hi,
    i am using oracle 11g R1 database in windows 2003 server. i need to stimulate two scenario
    1 . I want to corrupt a block and identify the corrupt block using RMAN.
    2 . I need to corrupt a block and while taking backup using RMAN it should tell that the block is corrupt.
    can anyone tell me how to do the above scenario
    Regards,
    007Check the link I've provided:
    https://forums.oracle.com/forums/thread.jspa?messageID=9850924#9850924

  • Block corruption detection in RMAN.

    Hi,
    I'd be be grateful if anyone could confirm or clarify the behaviour of the RMAN backup command with regard to detecting corrupt blocks in the datafiles.
    The environment is as follows:
    10.2.0.5.1
    Solaris 10
    2 node RAC
    Block Change Tracking file is not used.
    DB_BLOCK_CHECKING=OFF
    DB_BLOCK_CHECKSUM=OFF
    Does the BACKUP DATABASE command check both physical and logical block corruptions when run either as a full backup or incremental?
    I'm trying to establish wether running a BACKUP _VALIDATE [CHECK LOGICAL]_* DATABASE on a nightly basis provides any value if the same checks are being performed by the standard backup commands that are already scheduled every night?
    Any input appreciated.
    Thanks

    Hi,
    By default, RMAN just check for physical corruption, either in full or incremental backups. To check logical corruption you have to use the command "backup check logical;".
    About the parameter DB_BLOCK_CHECKSUM, its default is TRUE and Oracle Corporation advises leaving this parameter on default, so that any damage caused while the block is on disk, or corruptions introduced during the write and read process, will be detected.
    Hope it help.
    Regards,

  • RMAN backup piece corruption.

    Hi,
    I m having multiple databases where RMAN backup configured and scheduled. I want to know from backup piece how I can know the block corruption?

    What is the version of your RMAN utility.
    Try this:
    Start RMAN and connect to a target database and recovery catalog (if used).
    Run the BACKUP VALIDATE command.
    For example, you can validate that all database files and archived logs can be backed up by running a command as shown in the following example. This command checks for physical corruptions only.
    BACKUP VALIDATE
    DATABASE
    ARCHIVELOG ALL;
    To check for logical corruptions in addition to physical corruptions, run the following variation of the preceding command:
    BACKUP VALIDATE
    CHECK LOGICAL
    DATABASE
    ARCHIVELOG ALL;
    In the preceding examples, the RMAN client displays the same output that it would if it were really backing up the files. If RMAN cannot back up one or more of the files, then it issues an error message. For example, RMAN may show output similar to the following:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 08/29/2007 14:33:47
    ORA-19625: error identifying file /oracle/oradata/trgt/arch/archive1_6.dbf
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Source: http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmvalid.htm (To validate files with the BACKUP VALIDATE command)

  • How RMAN detect block corruption

    Hi,
    how RMAN detect block corruption( means how RMAN work internally to find corrupted block).
    thanks.

    There are initialization parameters (like DB_BLOCK_CHECKING) which will detect block corruption on block access. Go through the following link also:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm

  • How to overcome Block corruption using RMAN

    Hi All,
    How to overcome bolck corruption using RMAN. What is the procedure to do so.
    Thanks & Regards
    J.Venugopal

    Hi all,
    I´ve performed the following command on RMAN:
    RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL;After, I query the V$DATABASE_BLOCK_CORRUPTION table, and the below records
    was returned:
         FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
            67       4670          1         1202832866 LOGICAL
            68     154131        338         1175601952 LOGICAL
            68     155329         60         1174783128 LOGICAL
            68     155409         60         1174783132 LOGICAL
            68     155471         78         1174783135 LOGICAL
            68     155551         78         1174783139 LOGICAL
            68     155631         18         1174783143 LOGICAL
            68     155651         18         1174783144 LOGICAL
            68     155671         18         1174783145 LOGICAL
            68     155691         18         1174783146 LOGICAL
            68     155711         18         1174783147 LOGICAL
            68     155731         18         1174783148 LOGICAL
            68     155751         18         1174783149 LOGICAL
            68     155771         78         1174783150 LOGICAL
            68     155851         78         1174783154 LOGICAL
            68     155931         49         1174783158 LOGICAL
            73     165758          1         1180191676 LOGICALSo, when I try to recover these blocks by using blockrecover command, I got the error:
    RMAN> blockrecover corruption list;
    Starting blockrecover at 27-SEP-07
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of blockrecover command at 09/27/2007 10:22:10
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 73 found to restore
    RMAN-06023: no backup or copy of datafile 68 found to restore
    RMAN-06023: no backup or copy of datafile 67 found to restoreWhat can I do in this case?
    Thank U very much!
    []´s

  • Rman Detect Block Corruption

    Hi
    I know rman detect block corruption but my question is block corruption having two types one is physical block corruption and other is logical block corruption
    by default rman enable physical block corruption but by default rman not able to detect logical block corruption.Plz tell how i enable logical block corruption with RMAN?
    Please make correction if i m wrong.
    Thanks a lot.

    >> Sorry i am not telling you i am using oracle 9iR2 instead of oracle 10g
    It's okay.
    That's why; it's been already told that before posting in the forums, better it's better to specify/mention the Oracle Version/OS Details, etc to get the accurate and response.
    >> Send me if you have 9i related document.
    No need to send you the related documents, when there is a bulk repository available for free of cost for everybody.
    All you need to do is, just search in http://tahiti.oracle.com/ with the required word or phrase.
    Don't take me wrong, but make a habit of searching related documents from the Oracle Documentations.
    Regards,
    Sabdar Syed.

  • Need advice on ORA-01578: ORACLE data block corrupted

    We have a development database server version- 10.2.0.3 with materialized views refresh as complete every morning. Yesterday we had a power failure and the server went down and database was shutdown unexpectedly.
    When we restarted the database after the server restarted, we found some of the datablocks got corrupted . Following were the exceptions that we saw in the alert.log.
    Errors in file /i01_01/app/oracle/product/10.2.0/db_1/admin/orcl9/bdump/orcl9_smon_7547.trc:
    ORA-01578: ORACLE data block corrupted (file # 11, block # 257712)
    ORA-01110: data file 11: '/i01_01/app/oracle/product/10.2.0/oradata/orcl9/ts_gen_data_02.dbf'
    ORACLE Instance orcl9 (pid = 8) - Error 1578 encountered while recovering transaction (9, 38) on object 54463
    I tried the following query to see the segment type.
    select owner, segment_name, segment_type from dba_extents where file_id =11 and 257712 between block_id and block_id + blocks - 1;
    OWNER
    SEGMENT_NAME
    SEGMENT_TYPE
    VISH
    INVENTORY_TXN
    TABLE
    where " INVENTORY_TXN " is a materialized view that was using the block that got corrupted. I can always recreate the MV by dropping and recreating it. Will it solve the problem???
    If not, how can I recover/repair the block.???
    Can anyone advice on this. Thanks very much in advance.

    To recover a corrupted block,the best way out is to use Blockrecover command of RMAN. So you would need RmAN backup to perform the operation.But first ypu you need to ensure that this is a persistent error or not? Is this error is coming repeatedly or just once it happened?
    About Blockrecover command,read here,
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov005.htm#BRADV157
    HTH
    Aman....

Maybe you are looking for