Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

ORACLE ORA-00600: internal error code, parameters: [kokbcvb1] and merge into

2025-04-07 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

Recently, a city's Oracle database ran a Job to report an error, and the error content is as follows:

Operating system: windows server 2008R2

Database version: oracle 11.2.0.1

Error content:

Fri Aug 11 11:08:14 2017

Errors in file d:\ app\ administrator\ diag\ rdbms\ bmi\ bmi\ trace\ bmi_ora_2376.trc (incident=64225):

ORA-00600: internal error code. Parameter: [kokbcvb1], []

Incident details in: d:\ app\ administrator\ diag\ rdbms\ bmi\ bmi\ incident\ incdir_64225\ bmi_ora_2376_i64225.trc

Check the trc file bmi_ora_2376_i64225.trc prompted by the alarm log. The core content of the error report is as follows:

Dump file d:\ app\ administrator\ diag\ rdbms\ bmi\ bmi\ incident\ incdir_64225\ bmi_ora_2376_i64225.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Windows NT Version V6.1 Service Pack 1

CPU: 32-type 8664, 16 Physical Cores

Process Affinity: 0x0x0000000000000000

Memory (Avail/Total): Ph:88095M/130883M, Ph+PgF:218580M/261764M

Instance name: bmi

Redo thread mounted by this instance: 1

Oracle process number: 78

Windows thread id: 2376, image: ORACLE.EXE (SHAD)

* 2017-08-11 11 14. 0814. 729.

* SESSION ID: (352.202) 2017-08-11 1115 0814. 729

* CLIENT ID: () 2017-08-11 1115 0814. 729

* SERVICE NAME: (bmi) 2017-08-11 1115 0815 14.729

* MODULE NAME: (PL/SQL Developer) 2017-08-11 1115 0815 14.729

* ACTION NAME: (Primary Session) 2017-08-11 1115 0815 14.729

Dump continued from file: d:\ app\ administrator\ diag\ rdbms\ bmi\ bmi\ trace\ bmi_ora_2376.trc

ORA-00600: internal error code. Parameter: [kokbcvb1], []

= Dump for incident 64225 (ORA 64225 [kokbcvb1]) =

* 2017-08-11 11 14. 0814. 729.

DbkedDefDump (): Starting incident default dumps (flags=0x2, level=3, mask=0x0)

-Current SQL Statement for this session (sql_id=14qa0m0uufbbv)-

MERGE INTO DW_BILL T1 USING (SELECT B.HIS_ID, SUM (CASE WHEN B.REJECT_MONEY > = B.CAN_REJECT_MONEY THEN B.CAN_REJECT_MONEY ELSE B.REJECT_MONEY END) REJECT_MONEY, SUM (B.RULE_TYPE) RULE_TYPE, B.TABLE_PAR FROM (SELECT T.HIS_ID, T.DETAIL_ID, T.CAN_REJECT_MONEY, SUM (T.REJECT_MONEY) REJECT_MONEY, SUM (TO_NUMBER (T.RULE_TYPE)) RULE_TYPE T.TABLE_PAR FROM TMP_DEDUCTIONPLAN_BILLDETAIL T GROUP BY T.HIS_ID, T.DETAIL_ID, T.CAN_REJECT_MONEY, T.TABLE_PAR) B GROUP BY B.HIS_ID, B.TABLE_PAR) T2 ON (T1.HISID = T2.HIS_ID AND T1.TABLE_PAR = T2.TABLE_PAR AND T1.TABLE_PAR > =: B2 AND T1.TABLE_PAR

< :B1 ) WHEN MATCHED THEN UPDATE SET T1.BMI_NOPAY = CASE WHEN T1.BMI_NOPAY + T2.REJECT_MONEY >

= T1.BMI_CONVERED_AMOUNT THEN T1.BMI_CONVERED_AMOUNT ELSE T1.BMI_NOPAY + T2.REJECT_MONEY END, T1.RULETYPE = CASE WHEN T2.RULE_TYPE > 0 THEN'1' ELSE T1.RULETYPE END, T1.AUDIT_RESULT_F = '3percent, T1.AUDIT_RESULT_S =' 3percent, T1.ANDIT_MANU_STATUS = '3percent, T1.ANDIT_MANU_DATE = SYSDATE

-PL/SQL Stack-

-PL/SQL Call Stack-

Object line object

Handle number name

0000000E1719FA18 111 package body BMI.PKG_D_REALMONEY_SUM

0000000E1719FA18 58 package body BMI.PKG_D_REALMONEY_SUM

0000000E1719FA18 8 package body BMI.PKG_D_REALMONEY_SUM

0000000E26CEDB20 15 package body BMI.PKG_DEDUCTION_REALMONEY

0000000E2F232798 156 package body BMI.PKG_DEDUCTION_COMMON

0000000E1E7739A0 1 anonymous block

0000000E1717C1A8 651 package body SYS.DBMS_IJOB

0000000E26CEF490 284 package body SYS.DBMS_JOB

0000000E0F00AEE8 1 anonymous block

According to the trc file prompt, ORA-00600 [kokbcvb1] is caused by the following SQL:

MERGE INTO DW_BILL T1

USING (SELECT B.HIS_ID

SUM (CASE

WHEN B.REJECT_MONEY > = B.CAN_REJECT_MONEY THEN

B.CAN_REJECT_MONEY

ELSE

B.REJECT_MONEY

END) REJECT_MONEY

SUM (B.RULE_TYPE) RULE_TYPE

B.TABLE_PAR

FROM (SELECT T.HIS_ID

T.DETAIL_ID

T.CAN_REJECT_MONEY

SUM (T.REJECT_MONEY) REJECT_MONEY

SUM (TO_NUMBER (T.RULE_TYPE)) RULE_TYPE

T.TABLE_PAR

FROM TMP_DEDUCTIONPLAN_BILLDETAIL T

GROUP BY T.HIS_ID

T.DETAIL_ID

T.CAN_REJECT_MONEY

T.TABLE_PAR) B

GROUP BY B.HIS_ID, B.TABLE_PAR) T2

ON (T1.HISID = T2.HIS_ID AND T1.TABLE_PAR = T2.TABLE_PAR AND T1.TABLE_PAR > = B2 AND T1.TABLE_PAR

< :B1) WHEN MATCHED THEN UPDATE SET T1.BMI_NOPAY = CASE WHEN T1.BMI_NOPAY + T2.REJECT_MONEY >

= T1.BMI_CONVERED_AMOUNT THEN

T1.BMI_CONVERED_AMOUNT

ELSE

T1.BMI_NOPAY + T2.REJECT_MONEY

END

T1.RULETYPE = CASE

WHEN T2.RULE_TYPE > 0 THEN

'1'

ELSE

T1.RULETYPE

END

T1.AUDIT_RESULT_F ='3'

T1.AUDIT_RESULT_S ='3'

T1.ANDIT_MANU_STATUS ='3'

T1.ANDIT_MANU_DATE = SYSDATE

With regard to ORA-00600 [kokbcvb1], the official oracle document (document ID 1182535.1) mentions that it was caused by Bug 9471103:

Merge Query Failed with Ora-00600: [Kokbcvb1] (document ID 1182535.1)

APPLIES TO:

Oracle Database-Enterprise Edition-Version 10.2.0.4 to 11.2.0.2.0 [Release 10.2 to 11.2]

Information in this document applies to any platform.

* Checked for relevance on 29, FebMub, 2012, February 2012

SYMPTOMS

A merge query failed with the error below:

ORA-600: internal error code, arguments: [kokbcvb1], []

For example:

Merge into X USING (select a col1,'B' col2,3 col3,...

Even with Patch 8651671 and Patch 5308497 applied, the problem still reproduces.

When "_ optimizer_push_pred_cost_based" = false; the statement fails with

ORA-2070: database does not support antijoin

With "_ subquery_pruning_enabled" = false; statement finishes with

0 rows merged.

CAUSE

This could possibly be due to Bug 9471103 MERGE QUERY FAILED WITH ORA-600 [KOKBCVB1] which was closed as duplicate of unpublished Bug 9757249 ORA-600 [KOKBCVB1]

SOLUTION1. The fix for Unpublished Bug 9757249 is included in 11.2.0.2 and above. Therefore, please upgrade to 11.2.0.2 or higher.

OR

2. Apply one off Patch 9757249 if available on My Oracle Support for your Oracle version and platform. If a patch is not available, please log a Service Request with Oracle Support to assist you.

The extracted error message is consistent with bug 9471103. The processing method is to apply the patch pack patch 9757249 or upgrade the database version to 11.2.0.2 or above.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 299

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report