ora-00600錯誤系列-kokle_lob2lob13:input mismatch

這個錯誤沒有實際遇到，先摘過來以備後用：
原文連結：
http://blog.itpub.net/193161/viewspace-50342/

版本：

SYS@ning>select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for 32-bit Windows: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production

場景：

執行set autotrace on以後，在生成執行計劃的部分報錯：ORA-00600: internal error code, arguments: [kokle_lob2lob13:input mismatch], [1], [], [], [], [], [], []

使用alter session set sql_trace=true得到的trace檔案中，導致錯誤產生的語句為：

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kokle_lob2lob13:input mismatch], [1], [], [], [], [], [], []
Current SQL statement for this session:
SELECT /*+ opt_param('parallel_execution_enabled', 'false') */
/* EXEC_FROM_DBMS_XPLAN */ id, position, depth, operation, options, object_name, cardinality, bytes, temp_space, cost, io_cost, cpu_cost , time, partition_start, partition_stop, object_node, other_tag, distribution, projection, access_predicates, filter_predicates , other, qblock_name, object_alias, nvl(other_xml, remarks), null, null, null, null, null, null, null,
null, null, null, null, null,
null, null, null, null from PLAN_TABLE where plan_id = (select max(plan_id)
from PLAN_TABLE where id=0 and statement_id = :stmt_id)
order by id

查metalink，該錯誤相關的文章有3篇，都是被報告為bug的：

• Bug No.5370758
• Bug No.5259008
• Bug No.4292049

其中5259008，5370758都提到另外一個bug（Bug No.5135557），但是5135557的文件無法開啟。不知道是我的帳號沒許可權看還是怎麼的，有能看到該文章的朋友，請share一份給我，謝謝^_^

Bug 5135557.cannot be displayed. Possible reasons are:

• The bug is not classified as publicly accessible ("non-public").
• The bug is filed under a product for which you have no license. To view your product licenses go in your User profile and select the Show Licenseoption.
• The bug was filed before June 1996. Only bugs that were opened after this date are accessible on this server.
• The bug number does not exist (it was referenced incorrectly).

If you still have questions about why you weren't able to access this bug number, please use the Feedback button at the bottom of the left-hand menu bar.

上述bug報告中都沒有給出應對策略，並且sqlplus重新登入後，該錯誤消失。Bug報告中有說該錯誤可能重複出現，記錄一下，以後再觀察。