In the trace file table being loaded by BW with Error

[Former Member]

In the trace file I could see the table being loaded by BW with the

following error

*** 2012-08-31 10:54:27.592

ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [kcfrbd_3], [4], [2097440],

[1], [1379840], [1379840], [], []

Current SQL statement for this session:

INSERT INTO "/BIC/AZWM_O0840" VALUES

( :A0 , :A1 , :A2 , :A3 , :A4 , :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A1

1 , :A12 , :A13 , :A14 , :A15 , :A16 , :A17 , :A18 , :A19 , :A20 , :A21

, :A22 , :A23 , :A24 , :A25 , :A26 , :A27 , :A28 , :A29 , :A30 , :A31 ,

:A32 , :A33 , :A34 , :A35 , :A36 , :A37 , :A38 , :A39 , :A40 )

In the Alert log, after seeing multiple occurrences of the same error,

it then issues an ORA 600 with a Block Corruption.

[former_member289242 · Accepted solution]

Hello Manoj,

Please do a full consistency check on your database to find corrupted blocks as per attached Note 23345. You need to perform a database consistency via rman validate as well.

You need to identify the object that belongs to the corrupt blocks refer note 365481.

Use the following command to determine the objects.

select segment_name, segment_type, block_id, blocks from dba_extents

sewhere (<corrupted block> between block_id and (block_id + blocks - 1))

and file_id = <DB verification report>;

For index corruption, you can drop and recreate the index. For table corruption, please perform the restore and recovery on the effected datafile if you have valid backup.

Please proceed as per note 365481 to handle the block corruption issue.

Hope the above information helps.

In case you have any doubts in understanding these or if the issue persist again then kindly get back to me.

Best Regards,

Gunjan

[Former Member · Accepted solution]

Thanks Everyone. It was helpful..

[volker_borowski2]

Hi,

This was two months ago!

Is this still a relvant problem?

May be you already patched it out with a more recent SBP?

Volker

[Former Member]

To resolve your issue please read Note 376755 - ORA-00600 - what to do?

Regards

Roman