ORA-00600 [kddummy_blkchk] with argument 18083

[Former Member]

I copied a system using R3load and "-loadprocedure fast" on Oracle 9.2.0.8 (+ latest interim patches). The system was then upgraded to 10.2.0.2 plus the interim patches (40+).

During upgrade preparation (4.7 --> ERP 6.0) the database crashed with

ORA-00600: internal error code, arguments: [kddummy_blkchk], [15], [252696], [18038], [], [], [], []
Sun Apr 13 01:11:06 2008
Doing block recovery for file 15 block 252696
Block recovery from logseq 3131, block 61851 to scn 22287175
Sun Apr 13 01:11:06 2008
Recovery of Online Redo Log: Thread 1 Group 3 Seq 3131 Reading mem 0
  Mem# 0 errs 0: /oracle/T03/origlogA/log_g13m1.dbf
  Mem# 1 errs 0: /oracle/T03/mirrlogA/log_g13m2.dbf
Block recovery stopped at EOT rba 3131.68849.16
Block recovery completed at rba 3131.68849.16, scn 0.22287175

this is repeated several times until smon dies.

I used note 1136063 to find out the tables with corruptions:

% grep seg error_1828.log | grep -v dba: | cut -d " " -f 3
seg:COSL
seg:HRPY_WPBP
seg:HUMSEG
seg:JCDS
seg:K810016
seg:K810024
seg:LTBK
seg:MBEW
seg:MC04P_0ARBSETUP
seg:MC11VA0STISETUP
seg:MCVSRFP
seg:MDSM
seg:MFRES_TMP
seg:MSTA
seg:RBKP
seg:S031
seg:SOFFPHF
seg:SOFFPHIO
seg:SWP_HEADER
seg:T599U
seg:TBTCP
seg:WBCROSSGT

There were more tables listed but they have been "repaired" using exp/imp.

For table COSL this does not work because the database will still give that ORA-00600 and shuts down.

Is there any other way of working around that error without using a restore?

% $ORACLE_HOME/OPatch/opatch lsinventory | grep Patch
Invoking OPatch 10.2.0.2.0
Oracle Interim Patch-Installationsprogramm Version 10.2.0.2.0
OPatch-Version    : 10.2.0.2.0
Oracle Database 10g Release 2 Patch Set 1                            10.2.0.2.0
Interim-Patches (40) :
Patch  6819785      : applied on Fri Mar 07 02:18:27 CET 2008
Patch  6771608      : applied on Fri Mar 07 02:17:24 CET 2008
Patch  6740811      : applied on Fri Mar 07 02:16:34 CET 2008
Patch  6729801      : applied on Fri Mar 07 02:14:14 CET 2008
Patch  6663258      : applied on Fri Mar 07 02:13:21 CET 2008
Patch  6447320      : applied on Fri Mar 07 02:12:43 CET 2008
Patch  6435823      : applied on Fri Mar 07 02:12:14 CET 2008
Patch  6340979      : applied on Fri Mar 07 02:11:58 CET 2008
Patch  6153847      : applied on Fri Mar 07 02:11:18 CET 2008
Patch  6046043      : applied on Fri Mar 07 02:10:35 CET 2008
Patch  6024730      : applied on Fri Mar 07 02:10:20 CET 2008
Patch  5941030      : applied on Fri Mar 07 02:09:49 CET 2008
Patch  5636728      : applied on Fri Mar 07 02:09:19 CET 2008
Patch  5635254      : applied on Fri Mar 07 02:08:49 CET 2008
Patch  5618049      : applied on Fri Mar 07 02:07:56 CET 2008
Patch  5581518      : applied on Fri Mar 07 02:07:26 CET 2008
Patch  5530958      : applied on Fri Mar 07 02:06:54 CET 2008
Patch  5458753      : applied on Fri Mar 07 02:06:25 CET 2008
Patch  5442919      : applied on Fri Mar 07 02:05:56 CET 2008
Patch  5369855      : applied on Fri Mar 07 02:05:26 CET 2008
Patch  5363584      : applied on Fri Mar 07 02:04:57 CET 2008
Patch  5345999      : applied on Fri Mar 07 02:04:28 CET 2008
Patch  5308692      : applied on Fri Mar 07 02:03:44 CET 2008
Patch  5188321      : applied on Fri Mar 07 02:02:28 CET 2008
Patch  5103126      : applied on Fri Mar 07 01:55:05 CET 2008
Patch  5099986      : applied on Fri Mar 07 01:54:34 CET 2008
Patch  5063279      : applied on Fri Mar 07 01:53:58 CET 2008
Patch  4952782      : applied on Fri Mar 07 01:53:28 CET 2008
Patch  4899479      : applied on Fri Mar 07 01:52:57 CET 2008
Patch  4883635      : applied on Fri Mar 07 01:52:17 CET 2008
Patch  4864648      : applied on Fri Mar 07 01:51:43 CET 2008
Patch  4773931      : applied on Fri Mar 07 01:51:28 CET 2008
Patch  5102799      : applied on Fri Mar 07 01:51:10 CET 2008
Patch  4704890      : applied on Fri Mar 07 01:50:55 CET 2008
Patch  4668719      : applied on Fri Mar 07 01:50:13 CET 2008
Patch  4638550      : applied on Fri Mar 07 01:49:32 CET 2008
Patch  5090361      : applied on Fri Mar 07 01:49:17 CET 2008
Patch  4518443      : applied on Fri Mar 07 01:48:48 CET 2008
Patch  3748430      : applied on Fri Mar 07 01:48:31 CET 2008
Patch  5117016      : applied on Fri Mar 07 01:48:01 CET 2008

Markus

[Former Member · Accepted solution]

Hi Markus

Please check SAP Note 1136063 - Oracle Direct Path Load leads to block corruptions in ASSM

Regards Michael

Edited by: mho on Apr 17, 2008 9:23 AM

Sorry, you already found it, my bad

[markus_doehr2]

Restored the DB

closing thread...

[lbreddemann]

Hi Markus,

this should be checked by support. So I propose to open a support message.

Hmm... was the patch for bug 5386204 installed on the 9i DB when the R3Load was done?

regards,

Lars

[markus_doehr2]

Hi Markus,

this should be checked by support. So I propose to open a support message.

Ok. Will do that...

Hmm... was the patch for bug 5386204 installed on the 9i DB when the R3Load was done?

% ls -l P*.ZIP
-rw-r--r--   1 orat03   dba        91324 Feb  4 01:53 P3755693_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba       288231 Feb  4 01:53 P4660718_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba       197618 Feb  4 01:54 P5057695_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        88315 Feb  4 01:54 P5345999_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        16411 Feb  4 01:54 P5369855_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        38778 Feb  4 01:54 P5442919_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba       164604 Feb  4 01:54 P5508574_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        42528 Feb  4 01:54 P5530958_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        80422 Feb  4 01:54 P5660451_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba       168717 Feb  4 01:54 P5728380_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba        74607 Feb  4 01:54 P5842790_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba      1403659 Feb  4 01:55 P5977665_92080_SOLARIS64.ZIP
-rw-r--r--   1 orat03   dba       832788 Feb  4 01:55 P5985053_92080_SOLARIS64.ZIP

Those patches were installed on 9.2.0.8. So the single patch for that bug was not installed because it wasn´t availalbe...

Interestingly enough, after the import to that database (9.2.0.8), it was exported using R3load just before the upgrade to 10.2 and this export worked fine without any of those errors. That error appeared first after the upgrade to 10.2.

Markus