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

Similar Messages

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.

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

Oracle 11g - How to repair block corruption(on free space) in datafile

Hi,
I have a tablesopace with 3 datafiles, out of which one datafile has corrupted block. But no objects or data is affected as the corrupted block os in free space. This was shown in the alert logs.
Please see below the details:
Wed Apr 06 15:30:04 2011
SMON: Restarting fast_start parallel rollback
SMON: ignoring slave err,downgrading to serial rollback
ORACLE Instance geooap (pid = 12) - Error 1578 encountered while recovering transaction (10, 6) on object 149755.
Errors in file f:\oracle11g\diag\rdbms\geooap\geooap\trace\geooap_smon_5540.trc:
ORA-01578: ORACLE data block corrupted (file # 7, block # 54053)
ORA-01110: data file 7: 'F:\ORACLE11G\ORADATA\GEOOAP\ORDER_DATA_01.DBF'
GEOAP:
Fri Apr 01 14:57:48 2011
Errors in file f:\oracle11g\diag\rdbms\geop\geop\trace\geop_arc1_2156.trc:
ORA-00235: control file read without a lock inconsistent due to concurrent update
Fri Apr 01 14:57:58 2011
================================================================
The corruption is being reported in a free space block of the ORDER_DATA_01.DBF.
I’ve checked all the tables (and indexes) in this tablespace and none report corruption.
=====================================================Is there any action I need to take to remove corruption at this point?It is not affected any operation on the database yet.
What is the best way to do get rid of the corrupt block, without dropping and rebuillding the full tablespace(which is around 6 GB -total of 3 datafiles)
Thanks a lot

Can RMAN recover the datablock from this cold backup(which is a week old, the data file was not corrupted then) ?Please note that to do the recovery, you would need the backup and the archivelog files since the backup. Think about what you are asking to do. Its a single block whose recovery you are asking from a week old backup which obviously would be on an much older SCN compared to the rest of the database. How would you make that block consistent with the rest of the datafile. If you don't have archivelog in that db whose block is corrupted, you may forget that block and any data that it might ever had. Also, please read the documentation about the block recovery which explains the requirements very clearly,
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmblock.htm#BRADV89784
From the above link, 1st point,
The target database must run in ARCHIVELOG mode and be open or mounted with a current control file.HTH
Aman....

How create data block corruption for test DBMS_REPAIR

Hello to all
I wanna create data block corruption in a table for testing Dbms_repair
is it possible ? if yes please say to me how I can do it ,by example please
thanks

thank you so much that link was helpful (specially it's last respond)
I could create data block corruption and I tested DBMS_REPAIR and RMAN for data block recovery
but now I got head spin that if we have rman backup from database so using dbms_repair is what for?
while we can recover corrupted data blocks
please guide me
thanks

Block corruption in Free Space

Hi,
Environment:-
Oralce 10.2.0
Windows platform
I am facing problem of Logical block corruption.
RMAN validate block corruption (DBVerify as well) But no entry in Alert log file.
When I check Which segment has block corruption I found that block corruption are in free blocks of tablespace (DBA_FREE_SPACE).
To Fix it I create table and allocate corrupted block to that table. I confirm corrupted block allocation in table (using DBA_EXTENTS).
But when I insert rows in that table to reuse corrupted block Oracle give error of ora-1578 Block corruption, and I am not able to reuse corrupted block(as many expert suggest to overcome block corruption in free space).
I dropped table and recreate and repeat this process many times but still no success.
So. can anybody help me on this.
I appreciate your efforts and time you spend to read this
Thanks

Hello,
Please check the link i posted.
Example: Detecting Corruption
The CHECK_OBJECT procedure checks the specified object, and populates the repair table with information about corruptions and repair directives. You can optionally specify a range, partition name, or subpartition name when you want to check a portion of an object.
Validation consists of checking all blocks in the object that have not previously been marked corrupt. For each block, the transaction and data layer portions are checked for self consistency. During CHECK_OBJECT, if a block is encountered that has a corrupt buffer cache header, then that block is skipped.
The following is an example of executing the CHECK_OBJECT procedure for the scott.dept table.
SET SERVEROUTPUT ON
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'SCOTT',
OBJECT_NAME => 'DEPT',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
SQL*Plus outputs the following line, indicating one corruption:
number corrupt: 1

Block corruption error

Hi,
We are facing block corruption error file system file. I rtied to identify the corrupted object using dba_extents but that query is also giving the block corruption error for the same block. we are running the database in noarchivelog mode and we don't have backup.
please suggest the way how can i solve this corruption error?
Thanks in advance.
Regards
Chirag

you can use dbverify to check which blocks are corrputed and see below to know how to solve it http://www.google.co.in/search?hl=en&q=how+to+resolve+block+corruption%2Boracle&btnG=Search&aq=f&aqi=&aql=&oq=&gs_rfai=

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

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,

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

How to respond to physical block corruption??

Hi, all.
As far as I know, there are two types of block corruption.
1. logical block corruption
2. physical block corruption
In case of logical block corruption, there are a few method of how to take care of it.
such as BMR with rman, media recovery, and dbms package.
In case of physical block corruption, how can I respond to this type of errors?
Does physical block corruption of a disk mean disk failure??
If so, I have to replace the disk? Or, is there any other way to solve
this type of errors?
In addition, how can I know that the block corruption is caused by logical problems
or physical problems??
Thanks and Regards.

> In case of physical block corruption, how can I respond to this type of
errors?
Round around in circles, screaming at the top of your voice "we're all going to die!".
Hey, why that funny looks? It works. And it scares the stuffings out of management and colleagues... ;-)
> Does physical block corruption of a disk mean disk failure??
If by physical corruption you mean that reading a data block results in I/O errors and a corrupt/incomplete read buffer, then yes. The "disk" is failing - or more correctly, the I/O h/w is failing. It may not be the disk itself. It could be a problem with the HBA, a controller card, etc.
In exceptional cases it may not even be a h/w issue. It could be a s/w induced error. I once got physical I/O errors reported by Oracle. The problem was traced to an incompatibility between the ASMlib kernel module and EMC Powerpath. The SAN disks & h/w were fine.
> If so, I have to replace the disk? Or, is there any other way to solve
this type of errors?
There should be some kind of diagnostics you can run on the disks to determine if they are failing. Simply replacing a disk because there seems to be a physical corruption problem may not solve the problem itself.
You need to identify the actual problem. Which means looking at all Oracle traces/dumps in this regard, looking at the kernel logs, manually dumping blocks to see the results, using whatever I/O & disk diagnostic tools available, etc.
> In addition, how can I know that the block corruption is caused by logical
problems or physical problems??
That depends on what you define as logical and physical corruption. The latter means to me that I cannot get the data off the disk without some kind of I/O error. Logical means that the data can be read just fine, but is garbage. Which could simply mean GIGO without implying any kind of underlaying h/w failure.

How to practice "Archived log sequences loss- Block corruptions recovery"

Hello,
Prepare and test a recovery scenarios
- System Tablespace loss
- Online Redolog loss
- Controlfile loss
- Data Tablespace loss
- Single/multiple datafile loss
- Archived log sequences loss- Block corruptions recovery
- Total loss (database)
- Total loss (server = database/software/parameter files)
11g on windows
I am practicing my rman recovery and found this list of recovery scenarios. I have completed all scenarios
besides "Archived log sequences loss- Block corruptions recovery"
How do I break the database for the snenario "Archived log sequences loss- Block corruptions recovery"?
Do I delete the acr.001 files in directory I:\oracle\product\11.1.0\db_1\RDBMS? Then recovery as far forward as I can?
thanks for your help.

thanks for the tips
11g on windows 2003
I broke the database like this:
rman backup
shutdown immediate;
deleted datafile 5
delete most recent archivelogs seq 5 and 6;
recovered like this:
startup mount;
restore datafile 5;
recover datafile 5;
alter database open;
This does not seem correct? Did this also apply my archivelogs seq 5 and 6? Should I also do a point in time recovery?
Should I also run this?
run (set until sequence 6 thread 1; restore database; recover database;)
thanks for any help

How to detect corrupt archivelog? and continue the backup.

Hi Folks,
In RMAN, While doing backup of archivelog, I am getting some error regarding some archivelog are corrupt.I have two question here?
1) How to detect that particular archivelog is corrupt or not?
2) how to continue the backup even if we have corrupt archivelog?
Thanks
Shailesh

Shailesh.mishra wrote:
Hi Folks,
In RMAN, While doing backup of archivelog, I am getting some error regarding some archivelog are corrupt.I have two question here?
1) How to detect that particular archivelog is corrupt or not?DBV can be used to detect corruption or archives.
2) how to continue the backup even if we have corrupt archivelog?What kind of error you are experincing? You can use skip clause if you know which one is corrupted.
HTH
Aman....

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

Block Corruption (BR0398E DBVERIFY detected corrupted blocks in /oracle/TS2

Hello Gurus
I am facing Data Block corruption error for single datafile....
BR0278W Command output of '/oracle/TS2/102_64/bin/dbv file=/oracle/TS2/sapdata3/ts2_73/ts2.data73 blocksize=8192':
DBVERIFY: Release 10.2.0.2.0 - Production on Thu Jul 17 23:31:25 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /oracle/TS2/sapdata3/ts2_73/ts2.data73
Block Checking: DBA = 528925394, Block Type = KTB-managed data block
row 4: key out of order
     end index block validation
Page 443090 failed with check code 6401
DBVERIFY - Verification complete
Total Pages Examined         : 1280000
Total Pages Processed (Data) : 248379
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 180541
Total Pages Failing   (Index): 1
Total Pages Processed (Other): 13272
Total Pages Processed (Seg) : 0
Total Pages Failing   (Seg) : 0
Total Pages Empty            : 837808
Total Pages Marked Corrupt   : 0
Total Pages Influx           : 0
Highest block SCN            : 65006255 (0.65006255)
BR0398E DBVERIFY detected corrupted blocks in /oracle/TS2/sapdata3/ts2_73/ts2.data73
appriciated help please..
Regards
Giridhar.

Dump file /oracle/TS2/saptrace/usertrace/ts2_ora_23103.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
ORACLE_HOME = /oracle/TS2/102_64
System name:    SunOS
Node name:      sassad25
Release:        5.10
Version:        Generic_120011-14
Machine:        sun4u
Instance name: TS2
Redo thread mounted by this instance: 1
Oracle process number: 53
Unix process pid: 23103, image: oracle@sassad25 (TNS V1-V3)
2008-07-18 13:48:40.486
SERVICE NAME:(SYS$USERS) 2008-07-18 13:48:40.484
SESSION ID:(925.20292) 2008-07-18 13:48:40.484
Block Checking: DBA = 528925394, Block Type = KTB-managed data block
row 4: key out of order
end index block validation
for block 0x1f86c2d2
Block header dump: 0x1f86c2d2
Object id on Block? Y
seg/obj: 0x2c6f0 csc: 0x00.3f418d9 itc: 2 flg: E typ: 2 - INDEX
     brn: 0 bdba: 0x1f86c00b ver: 0x01 opc: 0
     inc: 0 exflg: 0
Itl           Xid                  Uba         Flag Lck        Scn/Fsc
0x01   0x0000.000.00000000 0x00000000.0000.00 -
    0 fsc 0x0000.00000000
0x02   0x0002.008.00002cb6 0x02475283.0359.19 --U-    2 fsc 0x0000.03f418ee
Leaf block dump
===============
header address 17494483044=0x412c0a064
kdxcolev 0
KDXCOLEV Flags = - - -
kdxcolok 0
kdxcoopc 0x80: opcode=0: iot flags=--- is converted=Y
kdxconco 7
kdxcosdc 0
kdxconro 174
kdxcofbo 384=0x180
kdxcofeo 967=0x3c7
kdxcoavs 583
kdxlespl 0
kdxlenxt 528925395=0x1f86c2d3
kdxleprv 528925393=0x1f86c2d1
kdxledsz 6
kdxlebksz 8032
row#0[7990] flag: -
, lock: 0, len=42, data:(6): 1b ce 75 c6 00 15
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 31 31 30 30 69
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#1[7952] flag: -
, lock: 0, len=38, data:(6): 1c 46 88 34 00 0e
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 5; (5): 48 50 4c 4a 34
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#2[7913] flag: -
, lock: 0, len=39, data:(6): 1b 8f 2b bd 00 03
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 6; (6): 48 50 4c 4a 34 30
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#3[7871] flag: -
, lock: 0, len=42, data:(6): 20 03 18 b1 00 0a
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 00
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#4[7830] flag: -
, lock: 0, len=41, data:(6): 1b 4f 19 ef 00 0b
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 8; (8): 48 50 4c 4a 34 30 30 30
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#5[7788] flag: -
, lock: 0, len=42, data:(6): 21 03 15 12 00 02
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 31
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#6[7746] flag: -
, lock: 0, len=42, data:(6): 1c 86 83 6a 00 0c
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 37
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#7[7704] flag: -
, lock: 0, len=42, data:(6): 1b 4f 19 0f 00 02
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 44
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#8[7662] flag: -
, lock: 0, len=42, data:(6): 1f 03 50 f5 00 03
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 44
col 4; len 3; (3): 37 30 30
col 5; len 1; (1): 44
col 6; len 1; (1): 80
row#9[7619] flag: -
, lock: 0, len=43, data:(6): 1f 03 50 f5 00 04
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 44
col 4; len 3; (3): 37 30 30
col 5; len 1; (1): 44
col 6; len 2; (2): c1 02
row#10[7577] flag: -
, lock: 0, len=42, data:(6): 1f 43 21 d1 00 09
col 0; len 3; (3): 30 31 35
col 1; len 2; (2): 58 58
col 2; len 8; (8): 46 4f 4e 54 52 45 50 4c
col 3; len 9; (9): 48 50 4c 4a 34 30 30 30 45
col 4; len 3; (3): 34 36 43
col 5; len 1; (1): 44

How RMAN detect block corruption

Similar Messages

Maybe you are looking for