My Oracle Support Banner

ORA-600 [kdourp_inorder] and ORA-600 [kcbzpbuf_1] and Instance Failure. (Doc ID 1066772.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 30-Aug-2013***

Symptoms


This problem was observed on Oracle 10.2.0.4 64-bit on a HP-UX PA-Risc 64bit server, using ASM


Problem description
Internal errors showing in the alert log, followed by instance termination.

The alert log shows these types of errors:
Errors in file /oracle/admin/epprd/udump/epprd_ora_17239.trc:
ORA-00600: internal error code, arguments: [kdourp_inorder1], [4], [211], [233], [44], [35], [0], []
Doing block recovery for file 206 block 1122542
. . . .
Hex dump of (file 2, block 46006) in trace file /oracle/admin/epprd/bdump/epprd_dbw2_7755.trc
Corrupt block relative dba: 0x0080b3b6 (file 2, block 46006)
Bad header found during preparing block for write
Data in bad block:
type: 167 format: 3 rdba: 0x0003ffbf
last change scn: 0x0003.a77d9080 seq: 0xff flg: 0xbf
spare1: 0x38 spare2: 0x80 spare3: 0xb800
consistency value in tail: 0x92d302dc
check value in block header: 0xa77d
computed block checksum: 0xa922
. . . . . .  .
Errors in file /oracle/admin/epprd/bdump/epprd_dbw2_7755.trc:
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], []
. . . . . .  . . . .
DBW2: terminating instance due to error 471
Instance terminated by DBW2, pid = 7755


Dbverify on the datafile will show to be clean, so this is an in-memory corruption.

The trace file will show a failing DML statement, for example, an update statement.
UPDATE <Table_name> SET ............

The function stack shows the problem occurring on an update, and writing a log entry.
   ksedst <- ksedmp <- ksfdmp <- kgerinv <- kgeasnmierr
   kdourp2 kdoura kco_issue_callback kcoapl kcbchg1_main
   kcbchg1 <- ktuchg <- ktbchg2 <- kdu_array_flush <- 424
   kdusru <- kauupd <- updrow




In the trace file, undo records will be dumped and you may see messages similar to the following

Block after image is corrupt:
buffer tsn: 3 rdba: 0x019120ee (6/1122542)
scn: 0x00b3.cf5f2e22 seq: 0x00 flg: 0x08 tail: 0x0003ffbf
frmt: 0x02 chkval: 0x0000 type: 0x06=trans data
Hex dump of corrupt header 2 = BROKEN




Other symptoms or conditions
   The Compatibility parameter in the database is set to 10.2....
   The database is using AUM (undo_management=auto)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.