Skip to Content
0
Former Member
Jan 18, 2012 at 12:36 PM

How to correct table block corruption on EDI40 table ?

491 Views

Hi,

I have discovered that there is table block corruption on the EDI40 table. Following OSS 365481 I have found the Idoc number that the corruption is specific to.

I can't see what options are available to me to correct the situation :-

WE11 short-dumps due to the corruption when attempting to delete the Idoc.

Manual 'delete from sapd1p.edi40 where docnum='idocnumber'' also fais due to the corruption.

Reorg is not possible as the EDI40 table contains a LONG field.

Trying to create a dummy table using Oracle 'create table ... as select from' doesn't work due to the LONG field.

DBMS_REPAIR package use seems to be not supported by SAP.

Oracle EXP/IMP based export will fail on impot due to the corruption.

Can anyone suggest what options could still be used to enable me to either delete the specific DOCNUM records from the EDI40 table or be able to export then re-import the EDI40 table data ?.

BR0301E SQL error -1578 at location stats_tab_validate-2, SQL statement:

'ANALYZE TABLE "SAPD1P"."EDI40" VALIDATE STRUCTURE CASCADE ONLINE'

ORA-01578: ORACLE data block corrupted (file # 62, block # 2163100)

ORA-01110: data file 62: '/oracle/D7R/sapdata6/d1p_49/d1p.data49'

BR0893E Validating structure failed for table/cluster SAPD1P.EDI40

I had hoped the corruption was index related but based on the contents of the dba_extents table for the block # and file # , the corruption is related to table data.

SQL> select segment_name, partition_name, segment_type, block_id, blocks from dba_extents where (2163100 between block_id and (block_id + blocks - 1)) and file_id = 62 and rownum < 2;

SEGMENT_NAME

-


PARTITION_NAME SEGMENT_TYPE BLOCK_ID BLOCKS

-


-


-


-


EDI40

TABLE 2162185 3072

SQL>

Regards,

Brian.