ORA-00600 [kdifind:kcbget_24],[25542720],[1],[0] 一例

Maclean Liu(刘相兵

ORA-00600 [kdifind:kcbget_24],[25542720],[1],[0] 一例


stack call 看是匹配 Bug:13464002的。

APPLIES TO:

Oracle Server - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
SYMPTOMS

The following errors are reported in the alert file:
ORA-00600: internal error code, arguments: [kdifind:kcbget_24], [10180101], [1], [0], [1], [], [], [], [], [], [], []


There may or may not be a current SQL reported in the incident trace file:
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)

----- Current SQL Statement for this session (sql_id=ghk07c6394jhz) -----
UPDATE CA_PMD_LOAD_GT GT SET GT.MKT_DATA_TYPE_CD = :B5 , GT.MKT_DATA_UOM = :B4 WHERE GT.INP_PMD_DATA_ITEM = :B3 AND GT.INP_PMD_MKT_TYPE = :B2 AND GT.INP_PMD_REPORT = :B1
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object      line  object
handle    number  name
42f7a9eb0      1124  package body NMARKET.CA_IM_LOAD_PUBLIC_DATA
42f7a9eb0      1728  package body NMARKET.CA_IM_LOAD_PUBLIC_DATA
4787780e8         1  anonymous block


Review of the generated tracefiles reveals a call stack similar to:
dbgeEndDDEInvocationImpl <- kcbget <- ktbxchg <- kdifind <- kdimod0 <- kauXuFinish <- kxibFinish <- qerupFetch <- updaul <- updThreePhaseExe <- 352 <- updexe <- opiexe <- opipls
CAUSE

The cause of this problem has been identified in:
Bug:12410357 - ORA-600 [KDIFIND:KCBGET_24]
closed as duplicate of:
Bug:13464002 - PREFETCH INVOLVING TEMP OBJECTS MAY RAISE ORA-600[KCBCHG1_12]/[KDIFIND:KCBGET_24

Bug:13464002 is fixed in RDBMS 12.1.

SOLUTION

To implement a solution for Bug:13464002, please execute any of the below alternative solutions:

Upgrade to 12.1 when it will become available.

OR
Apply patchset release 11.2.0.4 when it becomes available (not available as of time of publishing this article: JUL-2012) in which Bug:13464002 is fixed.

OR
Download and apply interim Patch:13464002, if available for your platform and RDBMS release. To check for conflicting patches, please use the MOS Patch Planner Tool. If no patch is available, file a Service Request through My Oracle Support for your specific Oracle version and platform.

OR
Use the workaround of setting "_db_file_noncontig_mblock_read_count"=0:

This parameter can be set only in the SPFILE and this requires a database restart:

SQL> ALTER SYSTEM SET "_db_file_noncontig_mblock_read_count"=0 SCOPE=SPFILE;

Restart the instance.

Explanation:

Setting "_db_file_noncontig_mblock_read_count"=0 will disable prefetching of non-contiguous blocks.

To reset "_db_file_noncontig_mblock_read_count"=0 to its default value use:

SQL> ALTER SYSTEM RESET "_db_file_noncontig_mblock_read_count";