ORA-00600[kjpsod1]&ORA-44203错误一例

一套HPUX-Itanium平台上版本为10.2.0.2 的系统出现ORA-00600: internal error code, arguments: [kjpsod1], [], [], [], [], [], [], []，并伴随有"ORA-44203: timeout waiting for lock on cursor".错误，详细的日志如下：  

Database get error
Errors in file /s01/admin/udump/prod_ora_14084.trc:
ORA-00600: internal error code, arguments: [kjpsod1], [], [], [], [], [], [], []
ORA-44203: timeout waiting for lock on cursor
ORA-44203: timeout waiting for lock on cursor

44203, 0000, "timeout waiting for lock on cursor"
// *Document : Yes
// *Cause    : A timeout occured while waiting for a cursor to be compiled.  
//             This is usually caused by the SQL parse requiring access to
//             system resources which are locked by concurrently executing
//             sessions.
// *Action   : Investigate possible causes of resource contention. If
//             neccessary, contact support for additional information
//             on how to diagnose this problem.
/
//    Reserving 44301 - 44400 for DBMS_SERVICES errors
/

    与该Internal error相关的知识如下：   CAUSE DETERMINATION =================== A fix for “ORA-00600: internal error code, arguments: [kjpsod1],” issue is in a patch 5169475. CAUSE JUSTIFICATION =================== A fix for “ORA-00600: internal error code, arguments: [kjpsod1],” issue is in a patch 5169475. PROPOSED SOLUTION(S) ==================== Apply patch 5169475 PROPOSED SOLUTION JUSTIFICATION(S) ================================== A fix for “ORA-00600: internal error code, arguments: [kjpsod1],” issue is in a patch 5169475. SOLUTION / ACTION PLAN ====================== -- To implement the solution, please execute the following steps:: Apply patch 5169475 KNOWLEDGE CONTENT ================= Errors in file /s01/admin/udump/prod_ora_14084.trc: ORA-00600: internal error code, arguments: [kjpsod1], [], [], [], [], [], [], [] ORA-44203: timeout waiting for lock on cursor ORA-44203: timeout waiting for lock on cursor Solution: Apply patch 5169475  Bug 5169475  HPUX-Itanium: trace files may not dump all memory  This note gives a brief overview of bug 5169475.  The content was last updated on: 30-APR-2008  Click here for details of each of the sections below. Affects:     Product (Component)    Oracle Server (Rdbms)     Range of versions believed to be affected    Versions >= 10.2.0.2 but < 11     Versions confirmed as being affected             10.2.0.2     Platforms affected             HPUX Itanium 64bit      It is believed to be a regression in default behaviour thus:        Regression introduced in 10.2.0.2 Fixed:     This issue is fixed in             10.2.0.3 (Server Patch Set)         11.1.0.6 (Base Release) Symptoms: Related To:     Diagnostic Output Problem / Improvement     Miscellaneous Description     This problem is introduced in 10.2.0.2 on HPUX Itanium.     Trace files produced on HPUX Itanium may not dump all     memory , may show memory as inaccessible ("**********")     when it is accessible and may abort early due with     false errors such as       ERROR, BAD EXTENT ADDRESS IN DS(800000010021e098)     due to incorrect response from the internal slrac()     function.     This can make it hard to progress a problem as the trace     may omit essential information.     Sub-Note:       See bug 5918964 for a similar issue on HPUX PA-Risc.   解决方案是在10.2.0.2 的基础上打5169475补丁(Patch 5169475: SLRAC() IS UNRELIABLE ON HPUX - FALSE KGHU ERRORS AND KGH MESSAGES)，或者升级到Patchset 10.2.0.5+ psu 10.2.0.5.5。