pat98's always & forever

ORA-00600:
: [kgiinb_invalid_obj], [0xC0000000C276EA28], [0xC0000000C2C61628], [], [], [], [], [], [], [], [], []
========= Dump for incident 31773 (ORA 600 [kgiinb_invalid_obj]) ========

----- Current SQL Statement for this session (sql_id=acxwkzfyc5ghs) -----

========================== 해결책==================================

Oracle Server - Enterprise Edition - Version: 11.1.0.7
This problem can occur on any platform.
Oracle Server Enterprise Edition - Version: 11.1.0.7

Symptoms

Running a PL/SQL it's possible to hit the internal error:
   ORA-00600: internal error code, arguments: [kgiinb_invalid_obj], [0x67F45C7D8], [0x68ED1C1E0],

The call stack looks like:
   dbgexProcessError dbgeExecuteForError dbgePostErrorKGE dbkePostKGE_kgsf kgeadse
   kgerinv_internal kgerinv kgeasnmierr kgiinb pfri7_inst_body_com mon pfri3_inst_body pfrrun plsql_run
   peicnt kkxexe opiexe

Cause

The cause of this problem has been identified and verified in an Unpublished Bug 7420394.

Solution

Unpublished Bug 7420394 is fixed in 11.2 release.

To avoid the issue:

1. check if it's available oneoff Patch 7420394 on your current release and for your platform.

8i ->9i 로 업그레이드 후 아래와 같은 에러 발생시 check 사항
==========================================================
8i 에서 쓰던 드라이버를 쓰다가 9i로 올리고 9i버전으로 업데이트 안해 주면 나는거 같은데.

udump 화일에 이런 에러메세지가 막 떨어질 것임.

*** SESSION ID:(119.40422) 2007-02-13 10:53:10.517
*** 2007-02-13 10:53:10.517
ksedmp: internal or fatal error
ORA-00600: 내부 오류 코드, 인수 : [ttcgcshnd-1], [0], [], [], [], [], [], []
Current SQL statement for this session:
SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER ='NLS_DATE_FORMAT'
----- Call Stack Trace -----
calling              call     entry                argument values in hex     
location             type     point                (? means dubious value)    
-------------------- -------- -------------------- ----------------------------
ksedmp()+328         CALL     ksedst()             00000000B ? 000000000 ?
                                                   000000000 ? 102FFB548 ?
                                                   00000003E ?
                                                   FFFFFFFF7FFF6658 ?

조치 방법
1. 아래와 같이 조치해 볼것
SQL> alter system set events '10841 trace name context forever';

요게 안되면 2번

2. 버전에 맞는 JDBC driver 로의 교체
ojdbc14.jar
Java classes when using the JDBC Thin and OCI client-side driver - with Java 1.4 or 5.0 VM. With Java 5.0 VM, you can use this library if the JDBC version is 10.2.

classes12.jar
Same as ojdbc14.jar except for use with with Java 1.2 or 1.3 VM.

classes12.zip
Same as classes12.jar except in zip format. This file will almost certainly not be available in future releases. You should use classes12.jar instead.

classes111.jar, classes111.zip
Classes for the Thin and OCI drivers when using a Java 1.1 VM.

- $ORACLE_HOME/jdbc/lib 밑에 최신 화일 업로드
- CLASSPATH에 추가 시켜줄것. (ex) export CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc14.jar

3. OS 에 설치된 JDK 버전의 down or upgrade 확인