Corrupt block senerio how to ??

Hello all,
This might be a stupid question...but i want to do a block recovery thru rman and want to corrupt some of my datafile blocks...so here is the question...how do i go about corrupting just couple of blocks ??? as i said i dont want to restore the datafile, TSPITR or anything like that...just want to recover the single block...but to do that...i need to corrupt my block...how can i do this ?? This will be 10g on AIX....on dev box ofcourse..LOL

Niall Litchfield wrote:
yingkuan wrote:
dd command in each OS is slightly different. Make sure double check with especially windows where it doesn't exist :( You could probably use a hex editor while the db was down on that platform.
Niall Litchfield
http://www.orawin.info/
That's not a concern here, OP using AIX :)

Similar Messages

  • Corrupt Block Found

    Hi,
    on 10g R2, Win server 2003, I have this error :
    Corrupt Block Found
             TSN = 2, TSNAME = SYSAUX
             RFN = 3, BLK = 36473, RDBA = 12619385
             OBJN = 150506, OBJD = 150506, OBJECT = MGMT_METRICS_RAW_PK, SUBOBJECT =
             SEGMENT OWNER = SYSMAN, SEGMENT TYPE = Index SegmentHow to identify this corrupted block ?
    How to remedy ?
    Thank you.

    There're many solutions to resolve block corruption. One of them is by using DBMS_REPAIR
    Look at this link http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/repair.htm#i1006090
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com

  • 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

  • How to identify corrupted block in Particular tablespace?

    Hi,
    i am getting lot of block corruption error from particular tablesapce datafile. i couldn't able to use DBVerify utility .bcz datafiles not created using .dbf format.
    how to idetify corrupted blocks?

    Detecting and Repairing Data Block Corruption
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96521/repair.htm(9i)
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/repair.htm(10g)
    Find more information “Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g” Metalink Note: 28814.1.
    http://dbataj.blogspot.com/2008/04/oracle-database-block-corruption.html
    http://sysdba.wordpress.com/2006/04/05/how-to-check-for-and-repair-block-corruption-with-rman-in-oracle-9i-and-oracle-10g/

  • How to make a corrupted block?

    Hi all,
    Is there any method to make a block corrupted in Oracle (for Windows)?
    My target is to test detecting and repairing corrupted blocks tools in Oracle.
    Thanks in advance,
    Ahmed B.

    Its not a great practice to do and oracle doesn't recommend such act. However, Oracle Support they have some internal utility for such, I dont know whether it is available to public or not. Search at metalink.
    Jaffar
    I just reaclled, there is a utility called 'bbed' which comes with oracle.
    However in UNIX you can use the dd command to corrupt a few blocks.Something like
    dd ibs=db_block_Size skip=n count=n if=/dev/null of=full_path_name_of_file_to_corrupt
    You can use the freeware hexedit to simulate block corruption in Windows.
    My sincere request is that dont do this with your production db. Use it very caciously.
    Message was edited by:
    The Human Fly

  • Recovery is repairing media corrupt block x of file x in standby alert log

    Hi,
    oracle version:8.1.7.0.0
    os version :solaris  5.9
    we have oracle 8i primary and standby database. i am getting erorr in alert log file:
    Thu Aug 28 22:48:12 2008
    Media Recovery Log /oratranslog/arch_1_1827391.arc
    Thu Aug 28 22:50:42 2008
    Media Recovery Log /oratranslog/arch_1_1827392.arc
    bash-2.05$ tail -f alert_pindb.log
    Recovery is repairing media corrupt block 991886 of file 179
    Recovery is repairing media corrupt block 70257 of file 184
    Recovery is repairing media corrupt block 70258 of file 184
    Recovery is repairing media corrupt block 70259 of file 184
    Recovery is repairing media corrupt block 70260 of file 184
    Recovery is repairing media corrupt block 70261 of file 184
    Thu Aug 28 22:48:12 2008
    Media Recovery Log /oratranslog/arch_1_1827391.arc
    Thu Aug 28 22:50:42 2008
    Media Recovery Log /oratranslog/arch_1_1827392.arc
    Recovery is repairing media corrupt block 500027 of file 181
    Recovery is repairing media corrupt block 500028 of file 181
    Recovery is repairing media corrupt block 500029 of file 181
    Recovery is repairing media corrupt block 500030 of file 181
    Recovery is repairing media corrupt block 500031 of file 181
    Recovery is repairing media corrupt block 991837 of file 179
    Recovery is repairing media corrupt block 991838 of file 179
    how i can resolve this.
    [pre]
    Thanks
    Prakash
    Edited by: user612485 on Aug 28, 2008 10:53 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Dear satish kandi,
    recently we have created index for one table with nologgign option, i think for that reason i am getting that error.
    if i run dbv utility on the files which are shown in alert log file i am getting the following results.
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx055.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:18:27 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx053.dbf
    Block Checking: DBA = 751593895, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 751593896, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 1036952
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 7342
    Total Pages Empty : 4282
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx053.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:23:12 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx054.dbf
    Block Checking: DBA = 759492966, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 759492967, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 759492968, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 585068
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 8709
    Total Pages Empty : 454799
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx054.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:32:28 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx055.dbf
    Block Checking: DBA = 771822208, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 771822209, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 771822210, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 157125
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 4203
    Total Pages Empty : 887248
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    My doubts are :
    1.if i drop the index and recreate the index with logging option will this error won't repeat in alert log file
    2.in future if i activate the standby database will database is going to open without any error.
    Thanks
    Prakash
    .

  • ORA-19566: exceeded limit of 999 corrupt blocks for file

    Hi All,
    I am new to Oracle RMAN & RAC Administration. Looking for your support to solve the below issue.
    We have 2 disk groups - +ETDATA & +ETFLASH in our 3 node RAC environments in which RMAN is configured in node-2 to take backup. We do not have RMAN catalog and the RMAN is fetching information from control file.
    Recently, the backup failed with the error ORA-19566: exceeded limit of 999 corrupt blocks for file +ETFLASH/datafile/users.6187.802328091.
    We found that the datafiles are present in both disk groups and from the control file info, we got to know that the datafiles in +ETDATA are currently in use and +ETFLASH is having old datafiles.
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name LABWRKT are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ETFLASH/CONTROLFILE/snapcf_LABWRKT.f';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ETFLASH/controlfile/snapcf_labwrkt.f';
    Above configuration shows that SNAPSHOT CONTROLFILE is pointing to +ETFLASH. So I changed the configuration with the SNAPSHOT CONTROLFILE points to '+ETDATA/controlfile/snapcf_labwrkt.f'. At the end of backup, SNAPSHOT file was created in +ETDATA and I was expecting it to be the copy of control file being used which has dbf located in +ETDATA. But still the backup was pointing to old datafiles in +ETFLASH. Since we dont have RMAN catalog, resync also is not possible.
    When I ran it manually, it was successfull without any error and was pointing to the exisiting datafiles.
    RMAN> backup database plus archivelog all;
    I hope the issue will get resolved if the RMAN points only to the datafiles present in +ETDATA. If I am correct, please let me know how can i make it possible? Also please explain me why the newly created snapshot file does not reflect the existing control file info?

    Hi,
    I am getting an error from the DBA Planning Calendar every time the job ...
    So when was your last successfull backup of this datafile. Check if still available.
    If this is some time ago, and may be you are currently without any backup, try to backup without rman at once,
    to have at least something to work with in case you get additional errors right now.
    Then you need to find out what object is affected. You are on the right way already. You need the statement,
    that goes to dba_extents to check what object the block belongs to.
    Has the DB been recovered recently, so the block might possibly belong to an index created with nologging ?
    (this could be the case on BW systems).
    If the last good backup of that file is still available and the redologs belonging to this backup up to current time are as well, you could try to recover that file. But I'd do this only after a good backup without rman and by not destroying the original file.
    If the last good backup was an rman backup, you can do a verify restore of that datafile in advance, to check if the corruption is really not inside the file to be restored.
    Check out the -w (verify) option of brrestore first, to understand how it works.
    (I am not sure it this is already available in version 7.00, may be you need to switch to 7.10 or 7.20)
    brrestore -c -m /oracle/SHD/sapdata4/sr3_16/sr3.data16  -b xxxxxxxx.ffr -w only_rmv
    You should do a dbv check of that file as well, to check if it gets more information. I.E if more blocks are
    affected. rman stops right after the first corruption, but usually you have a couple of those in line, esp. if these are
    zeroed ones. (This one would also work with version 7.00 brtools)
    brbackup -c -u / -t online -m /oracle/SHD/sapdata4/sr3_16/sr3.data16 -w only_dbv
    Good luck.
    Volker

  • Does a truncate table solve corrupt blocks in a table

    Hi Guys,
    Got a question:
    Does a truncate table solve corrupt blocks in a table?
    I have found corrupt blocks in rman, located them, they are in 1 table.
    And contacted the business, and have permission to drop and recreate the table,
    but my question is does truncate table drop storage also solves my problem?
    And will it let me to do a full backup without set max corrupt blocks?
    To my knowledge does a truncate table moves the high watermark to 0 + 1 extend, but I am unsure how this will effect the corrupt blocks.
    Thanks in advance for your advice

    Hi,
    Yes truncate/drop table fixes the corruption at the database level. You may like to take the backup(if you have index on it) of that table so that you may restore it later if anything goes wrong.
    Note: This would not fix any corruption at the disk level (like bad sectors).
    Regards
    Anurag

  • Strange Corrupt Block Error in Control File not in CONTROL_FILES

    When in RMAN connected to the TARGET and CATALOG I issue a RESYNC CATALOG I get this error:
    RMAN> RESYNC CATALOG;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of resync command on default channel at 08/17/2009 10:36:59
    ORA-00227: corrupt block detected in control file: (block 15, # blocks 1)
    ORA-00202: control file: 'E:\ORACLE\PRODUCT\10.2.0\DATABASE\SNCFEBIZ01PD.ORA'
    RMAN>
    This control file is in the Oracle Windows default dir but I am not using it and did not create it.
    My control files listed in the init.ora are:
    SQL> show parameter control
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    control_files string E:\ORACLE\ORADATA\EBIZ01PD\CNT
    RL01.DBF, D:\ORACLE\ORADATA\EB
    IZ01PD\CNTRL02.DBF, E:\ORACLE\
    ORADATA\EBIZ01PD\CNTRL03.DBF
    Any idea why this is happening?

    That is a SNAPSHOT CONTROLFILE, created by RMAN as a copy of the current controlfile.
    Wonder how and why the copy is corrupted ? Check the timestamp of the file to see when it was created. A RESYNC will always create a fresh Snapshot Controlfile.
    See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmarchi.htm#sthref65

  • Help Fix 26473 Corrupt blocks in system09.dbf

    How to Format Corrupted Block Not Part of Any Segment [ID 336133.1]
    I'm following the above doc to fix 26K corrupt blocks in system09.dbf
    in Step 7 of the Doc it says:
    +" First find the *extent size* by querying dba_free_space "+
    +65536 = If its 64 K+
    +1048576 = 1M+
    I'm getting 891559936 with the following query:
    SQL> Select bytes from dba_free_space where file_id= 352 and 192128 between block_id and block_id + blocks -1;
    BYTES
    891559936
    What will be my extent size?
    I'm lost on how to proceed with the following steps:
    BEGIN
    for i in 1..1000000 loop
    EXECUTE IMMEDIATE 'alter table apps.s allocate extent (DATAFILE '||'''/oracle/KPSO/db/apps_st/data/system09.dbf''' ||'SIZE 64K) ';
    end loop;
    end ;
    +/+
    Note you need to change accordingly the size (1M ,64K or 128k) and the value of for loop
    can be changed as per requirement.
    Thanks.
    -Joey-

    >
    currently doing another round of steps 5-9 to see if it will wipe out all the corrupt blocks.Just want to give an update:
    Datafile was completely free of corruption after 2 more passes ..
    $ dbv file=/oracle/KPSO/db/apps_st/data/system09.dbf blocksize=8192
    DBVERIFY: Release 11.1.0.7.0 - Production on Thu Mar 22 05:08:56 2012
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle/KPSO/db/apps_st/data/system09.dbf
    DBVERIFY - Verification complete
    Total Pages Examined : 192128
    Total Pages Processed (Data) : 160979
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 26455
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 2124
    Total Pages Processed (Seg) : 0
    Total Pages Failing (Seg) : 0
    Total Pages Empty : 2570
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    Total Pages Encrypted : 0
    Highest block SCN : 3757005752 (1388.3757005752)

  • Corrupt block relative dba: in alert log

    hi,
    In our recovery database,I've found following error in alert log.
    Thu Mar 27 07:05:57 2008
    Hex dump of (file 3, block 30826) in trace file /u01/app/oracle/admin/catdb/bdump/catdb_m000_21795.trc
    Corrupt block relative dba: 0x00c0786a (file 3, block 30826)
    Bad check value found during buffer read
    Data in bad block:
    type: 6 format: 2 rdba: 0x00c0786a
    last change scn: 0x0000.0013ed4d seq: 0x1 flg: 0x06
    spare1: 0x0 spare2: 0x0 spare3: 0x0
    consistency value in tail: 0xed4d0601
    check value in block header: 0x937c
    computed block checksum: 0x8000
    Reread of rdba: 0x00c0786a (file 3, block 30826) found same corrupted data
    Thu Mar 27 07:05:59 2008
    Corrupt Block Found
    TSN = 2, TSNAME = SYSAUX
    RFN = 3, BLK = 30826, RDBA = 12613738
    OBJN = 8964, OBJD = 8964, OBJECT = WRH$_ENQUEUE_STAT, SUBOBJECT =
    SEGMENT OWNER = SYS, SEGMENT TYPE = Table Segment
    Now, how solve this error?
    Thanks in advance.
    Leo

    Refer to metalink Note:77587.1. You may need to do further sanity block checking by placing the following parameters in the database instance init.ora parameter file:
    db_block_checking=true
    db_block_checksum=true
    dbblock_cache_protect= true
    Consult Oracle support before changing hidden parameters.

  • Finding Total Number Of Corrupted Blocks

    Hello,
    I just browsed several websites including RMAN documentation and information on how to identifiy corrupted blocks.
    I´m in the middle of reorganizing production backups and their restore tests by duplication, which should (in my opinion) be followed by an analysis for corrupted blocks.
    I found RMAN command  BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL; to fit my needs. Recently I read the validate command only writes NEWLY found corrupted blocks to View V$DATABASE_BLOCK_CORRUPTION.
    1. How do I check the WHOLE database for its TOTAL physical and logical corrupted blocks?
    2.Under which circumstances is it NOT necesssary to check the database after the restore? In other words is there a way to ensure the backup cancels immediately when finding a corrupted block?
    3. Is it necessary to set maxcorrupt to "0" during the Backup to get it cancelled for every corrupted block found?
    4. What does dbv in contrast to backup validation?
    Please be so kind to post me some short hints.
    Regards
    Dominik

    Hi,
    thanks for your feedback again.
    Yesterday I "accidently" faced the situation to work with a block corrupted database during a restore test.
    So I had the chance to run both backup validate and dbv against its corrupted files.
    dbv worked fine, recognized all corrupted blocks and reported them in its output.
    Disappointingly backup validate neither reportted any corrupt withtin the whole database (there are several datafiles with corrupted blocks), nor posted them to V$DATABASE_BLOCK_CORRUPTION. There I could only find a hand full, but not all of them.
    I´m very consufed now, what would I need backup validate for anymore??? :-/
    I built myself a script to check the whole database with dbverify. Regarding production databases we cannot live with uncertainties like that
    Regards
    Dominik

  • Corrupt Block and Standby Database

    Guys,
    I created a standby database recently. I then discovered a corrupt block on my primary, I assume the corruption is also on the standby since the files were coppied. If I repair the corrupt block on the primary how do I move the correction to the standby, do I have to recreate it?
    DB version is 9iR2
    Delton

    Hi Delton,
    How do you plan to repair the corrupt block ?
    * Drop and re-create the object
    * Restore from backup
    In both cases, changes are replicated to the standby database, so nothing to worry about. As Sybrand has mentioned, make sure the changes are done with LOGGING option.
    Regards
    Asif Momen
    http://momendba.blogspot.com

  • Old corrupted blocks in nologging mode.

    Dear All,
    I m facing issue of block corruption, when I check through select from v$database_block_corruption it shows total 511 blocks corrupted and below is one result. This are old one and not having backup for the same.
    But when I validate the backup it shows no error. How to resolve this.....
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    11 3638851 6 5.4254E+12 NOLOGGING

    the RMAN backup validate to check block corruption will return if any ACTIVE DB blocks are corrupted or not. So to my knowledge the corrupted blocks u have are not being used by the DB for any read/write hence RMAN backup is not returning an information about the block corruption. The DBverify is an old version if RMAN did not find the corruption then DBVerify will also not return anything. So if RMAN des nt return any block corruption then you will not have any DB outage.

  • BR0398E DBVERIFY detected corrupted blocks in TS SAPSR3

    Hi!
    After DBVerify I get the following error:
    BR0398E DBVERIFY detected corrupted blocks in /oracle/<sid>/sapdata4/sr3_8/sr3.data8
    Furthermore I get the following warning/information:
    Completely zero block found during dbv:
    Page 286685 is marked corrupt
    Question:
    1) Does it mean that my database is corrupt and should be recovered from a valid backup?
    2) What is the approach to handle here and to solve the error?
    Enclosed the output of the following SQL commandos:
    > select dbms_utility.data_block_address_block(1522735858) from dual;
    DBMS_UTILITY.DATA_BLOCK_ADDRESS_BLOCK(1522735858)
                                               203506
    > select dbms_utility.data_block_address_file(1522735858) from dual;
    DBMS_UTILITY.DATA_BLOCK_ADDRESS_FILE(1522735858)
                                                 363
    > select file#, rfile# from v$datafile where name = '/oracle/<sid>/sapdata4/sr3_8/sr3.data8';
         FILE#     RFILE#
            11         11
    > select segment_name, partition_name, segment_type, block_id, blocks   from dba_extents   where (203506 between block_id and (block_id + blocks - 1))   and file_id = 363 and rownum<2;
    no rows selected
    Thank you very much!

    Hi!
    Some additional information
    SQL> SELECT dbms_utility.data_block_address_block(1522735858) "BLOCK", dbms_utility.data_block_address_file(1522735858) "FILE" FROM dual;
         BLOCK       FILE
        203506        363
    After this I executed alter system dump commando:
    > alter system dump datafile 363 block 203506;
    When I open the generated dump file I can see:
    Error: alter system dump datafile/tempfile: invalid input file # 363
    SQL>  select owner, segment_name, partition_name, segment_type, block_id, blocks
      2  from dba_extents  
      3 where (525 between
      +4  block_id and (block_id + blocks - 1))+
      5  and file_id = 4
      6  and rownum < 2;
    OWNER SEGMENT_NAME PARTITION_NAME   SEGMENT_TYPE         BLOCK_ID     BLOCKS
    SAPSR3                    DD08T~0                   INDEX                           521        128
    Question
    Should I run the following SQL commando or how can I solve my problem?
    ALTER INDEX DD08T~0 REBUILD ONLINE;

Maybe you are looking for

  • Job work in SAP SD

    Dear All My client have a requirement.... they have got empty bottles and their logo we have to just paste them and send it back, so its a matter of JOB WORK in SAP SD, here the customer and Vendor is same, so how can I map this in sap. Matter is mos

  • Clone system, will it work for both 17" & 20" rev a's

    If I clone my 20" iMac G5 rev A to my external fire wire HD, in a total disaster can I use this system clone in my 17" iMac G5 rev A? can't remember is they came with different system disk, or if they need different system disks. Hoping one backup of

  • Quicktime 7.0.3 and FCP 4.5

    Are there major issues with these two? I am on 10.3.9 OS FCP has been acting a little weird since installing QT 7.0.3. It's harder to make exact cuts in the timeline among other issues.

  • Get service ticket details

    Dear All, I have a requirement wherein, Pass the Status of the Ticket and Get the details of all the Service Tickets whose status is mentioned So please let me know of the FM/BAPI to achieve this task. Thanks Shweta

  • Line Item discount

    Hi, I am writing a query when line item discount is greaterthan 33%, it should go for approval. Here I am facing a problem: 1. If line 1 discount is greaterthan 33%, document is going for approval 2. If line 1 discount is lessthan 33% and line 2 disc