一套HP-UX Itanium上的10.2.0.3系统出现了ORA-00600: internal error code, arguments: [ksnpost:ksnigb], [], [], [], [], [],错误，相关的日志如下：
ORA-00600: internal error code, arguments: [kolaslGetLength-1], [], [], [], [], [], [], []ORA-00600: internal error code, arguments: [ksnpost:ksnigb], [], [], [], [], [], [], []ORA-00609: could not attach to incoming connectionORA-12157: TNS:internal network communication errorORA-27300: OS system dependent operation:fork failed with status: 12ORA-27301: OS failure message: Not enough spaceORA-27302: failure occurred at: skgpspawn3ORA-00600: internal error code, arguments: [kolaslGetLength-1], [], [], [], [], [], [], []Current SQL statement for this session:SELECT * FROM gv$sqlksedmp: internal or fatal errorORA-00600: internal error code, arguments: [ksnpost:ksnigb], [], [], [], [], [], [], []ORA-00609: could not attach to incoming connectionORA-12157: TNS:internal network communication errorCurrent SQL information unavailable - no session.
Mos上相关的Bug 信息： Bug # 4634662 - Ora-600 [kolaslGetLength-1] Bug # 7479468 - Ora-600 [ksnpost:ksnigb] Issue 1) This issue is described in the note 357016.1.Please apply the patch mentioned in the note 357016.1 to avoid this issue. Issue 2) This is due to OS resource limitation. You need to check with HP for this.We are running out of OS resources and hence this issue is coming. Also you can set the ulimit -a values to unlimited for oracle and root user to avoid this issue.
Bug 4634662 OERI:kolaslGetLength-1 from V$SQL in RAC ORA-600[kolaslGetLength-1] selecting from V$SQL (of GV$SQL) Range of versions believed to be affected Versions < 11 Versions confirmed as being affected 10.1.0.5 10.2.0.3 his issue is fixed in 10.2.0.3 Patch 5 on Windows Platforms 10.2.0.4 (Server Patch Set) 11.1.0.6 (Base Release) on a RAC database with a varying width character set. Applies to: Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.3 - Release: 10.1 to 10.2 Information in this document applies to any platform. Symptoms select * from gv$sql on a RAC enviornment errors with: ORA-00600: internal error code, arguments: [kolaslGetLength-1], [], [], [], [], [], [], []. with a multibye characterset (ie:al32utf8, utf8 ) Note: This error has also been reported when select from SQLT$_GV$SQL_PLAN while running Sqlt Execute diagnostic utility - SQLTXPLAIN.SQLT$* Cause This is Bug 4634662 Details: ora-600[kolaslGetLength-1] received selecting from v$sql over a RAC db which has a varying width character set Solution Bug 4634662 is fixed in 10.2.0.4 and Rel 11. To check if a patch exists for your platform, go to Metalink: a) Click on Patches & Updates Folder. b) Click on Simple Search. c) Enter patch#: Patch 4634662 d) Select your O/S e) Click Go. ORA-600 [Ksnpost:Ksnigb] ORA-12157 Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.4 and later [Release: 10.2 and later ] Information in this document applies to any platform. Symptoms In the alert log is reported the following: ORA-00600: internal error code, arguments: [ksnpost:ksnigb], [], [], [], [], [], [], [] ORA-00609: could not attach to incoming connection ORA-12157: TNS:internal network communication error Cause ORA-600 [ksnpost:ksnigb] along with ORA-600 [729] errors are creating problem while creating new sessions. All these point to insufficient memory or OS limits. Bug 7479468 was raised for similar issue that was closed as there was not enough swap swap space hence was the problem. Solution Check the swap space in the system and increase if required. References BUG:7479468 - ORA-600 [KSNPOST:KSNIGB] AND ORA-12157 分析发现在10.2.0.3等版本上存在RAC中查询gv$sql视图会引发ORA-600[kolaslGetLength-1]错误的bug，该bug 可以通过实施补丁4634662来解决。 此外当有效内存不足或OS参数上限过小时可能导致Oracle无法成功创建新的session ，引发ORA-600[ksnpost:ksnigb]错误。 建议检查ulimit -a 的输出， 在HP-UX上不妨将stack size设置为unlimited(set the stack size to unlimited.) $ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) 1048576 stack(kbytes) 131072 memory(kbytes) unlimited coredump(blocks) 4194303 nofiles(descriptors) 2048