this is not a RAC datbase. None of the background or any oracle process was killed on OS level, as this metalink note says it may happen if a process is killed on OS level. Thanks Arvind Kumar ________________________________ From: David Barbour [mailto:david.barbour1@xxxxxxxxx] Sent: Tue 1/27/2009 10:06 PM To: Arvind Kumar Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: ORA-00600: [kcbzfb_3], [0x3A3FC0B00], , [0x4FCF93668], [0x44CFD5468] From Metalink Note #3704314.8: Subject: Bug 3704314 - OERI:kcbzfb_3 / OERI:kjmsm_epc instance crash possible Doc ID: 3704314.8 Type: PATCH Modified Date: 24-SEP-2008 Status: PUBLISHED Bug 3704314 OERI:kcbzfb_3 / OERI:kjmsm_epc instance crash possible This note gives a brief overview of bug 3704314. The content was last updated on: 24-JAN-2005 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.1.0.2 Versions confirmed as being affected * 126.96.36.199 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in * 188.8.131.52 (Server Patch Set) * 10.1.0.2 (Base Release) Symptoms: Related To: * Internal Error May Occur (ORA-600) * Instance May Crash * ORA-600 [kcbzfb_3] * ORA-600 [kjmsm_epc] * RAC (Real Application Clusters) / OPS Description ORA-600 [kcbzfb_3] / ORA-600 [kjmsm_epc] instance crash possible in RAC if a process is killed at OS level (eg: using kill -9) at an particular point in the code. Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. References Bug 3704314 <https://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=3704314> (This link will only work for PUBLISHED bugs) Note 245840.1 <https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=245840.1&blackframe=1> Information on the sections in this article On Tue, Jan 27, 2009 at 2:55 PM, Arvind Kumar <Arvind.Kumar@xxxxxxxxxxxxx> wrote: Hello all, I got the following error in alert log and instance crashed, Has any experienced such ORA-00600 : [kcbzfb_3] ? Errors in file /u300/app/oracle/admin/SIYPROD/bdump/siyprod_j000_5157.trc: ORA-00600: internal error code, arguments: [kcbzfb_3], [0x3A3FC0B00], , [0x4FCF93668], [0x44CFD5468], , ,  And /u300/app/oracle/admin/SIYPROD/bdump/siyprod_j000_5157.trc Oracle9i Enterprise Edition Release 184.108.40.206.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 220.127.116.11.0 - Production ORACLE_HOME = /u300/app/oracle/product/9.2.0 System name: SunOS Node name: ora01 Release: 5.9 Version: Generic_122300-26 Machine: sun4us Instance name: SIYPROD Redo thread mounted by this instance: 1 Oracle process number: 56 Unix process pid: 5157, image: oracle@ora01 (J000) *** SESSION ID:(99.21742) 2009-01-27 00:54:04.912 *** 2009-01-27 00:54:04.912 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [kcbzfb_3], [0x3A3FC0B00], , [0x4FCF93668], [0x44CFD5468], , ,  Current SQL statement for this session: SELECT SUM( DECODE(PAYMENTSTATUSID, 3, DECODE(NVL(GROSSCREDITDAYS, 0), 0, (nvl(creditDays,0) + nvl(UnderCreditDays,0)-nvl(OverCreditDays,0)), GROSSCREDITDAYS), 0)), SUM(DECODE(PAYMENTSTATUSID, 5, NVL(GROSSCREDITDAYS, 0), 0)) FROM CLA_T_UPaySchedule WHERE claimno=12090655 AND paymentstatusid IN(3,5) ----- PL/SQL Call Stack ----- object line object handle number name 6329cba80 102 package body SIYAYAUSER.PK_CLAIMFINALIZED 65f5052f8 1 anonymous block ----- Call Stack Trace ----- Thanks & Regards, Arvind Kumar Disclaimer This e-mail and any attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. If you have received this e-mail in error please notify the sender and delete the original message. Any views or opinion expressed in this e-mail are those of the author and do not necessarily represent those of the Department of Labour. The recipient should check this e-mail and any attachments for the presence of viruses and other destructive codes. While all possible precautions have been taken, the Department accepts no liability whatsoever for loss or damage resulting from the opening of this message or attachments, or the use of the information contained in this message or attachment.