ORA-00600: internal error code, arguments... Problem

ORA-00600: internal error code, arguments .. problem: When querying the wwl005 table, an internal error is reported. For this table, we just restored the inconsistency, and then the following error is reported during the query, this is generally caused by bugs or bad blocks. 15:43:53 SQL> select * from wwl005; select * from wwl005 * ERROR at line 1: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], [], [] troubleshooting: First, check the alert Log and find an error, but it is not clear: errors in file/DBSoft/admin/WWL/udump/wwl_ora_4724.trc: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], [] www.2cto.com
Check the corresponding trace file to see: [root @ wwldb ~] # Cat/DBSoft/admin/WWL/udump/wwl_ora_4724.trc | moreDump file/DBSoft/admin/WWL/udump/login Database 10g Enterprise Edition Release 10.2.0.1.0-ProductionWith the Partitioning, OLAP and Data Mining optionsORACLE_HOME =/DBSoft/product/10.2.0/db_1System name: LinuxNode name: wwldb. localdomainRelease: 2.6.18-164. el5Version: #1 SMP Thu Sep 3 02:16:47 EDT 2009 Machine: i686Instance name: WWLRedo thread mounted by this instance: 1 Oracle process number: 12 Unix process pid: 4724, image: oracle@wwldb.localdomain (TNS V1-V3) *** action name :() 15:44:04. 239 *** module name :( SQL * Plus) 15:44:04. 239 *** service name :( SYS $ USERS) 15:44:04. 239 *** session id: (50.5) 15:44:04. 239 *** session id: (50.5) 15:44:04. 239 objd mismatch typ = 35, seg. obj = 0, diskobj = 51698, dsflg = 0, dsobj = 51697, tid = 51697, cls = 4 Formatted dump of block: www.2cto.com buffer tsn: 6 rdba: 0x0140002b (5/43) scn: 0x0000. 0014adb8 seq: 0x01 flg: 0x04 tail: 0xadb82301frmt: 0x02 chkval: 0x6296 type: 0x23 = pagetable segment HEADERHex dump of block: st = 0, typ_found = 1 Dump of memory from 0x25DB2000 to 0x25DB400025DB2000 running a223 0140002B 0014ADB8 04010000 [#... +. @ ......] 25DB2010 00006296 00000000 00000000 00000000 [. B ......] 25DB2020 00000000 00000001 00000008 00000A9C [......] 25DB2030 00000000 00000003 00000008 0140002C [............,. @.] 25DB2040 00000000 00000000 00000000 [......] 25DB2050 000E0004 000000F4 00000001 00000000 [......] 25DB2060 00000003 00000008 0140002C 00000000 [........,. @ ......] 25DB2070 00000000 00000000 00000000 01400029 [............). @.] 25DB2080 01400029 00000000 00000000 00000000 [). @ ......] 25DB2090 00000000 00000000 00000000 00000000 [......] repeat 3 times25DB20D0 00000001 00002000 00000000 [........... 4...] 25DB20E0 00000000 0140002A 00000001 01400029 [.... *. @.....). @.] 25DB20F0 0140002A 00000000 00000000 00000000 [*. @ ......] 25DB2100 00000000 00000000 00000001 [...] 25DB2110 c9f2 10000000 01400029 00000008 [........). @ ......] 25DB2120 00000000 00000000 00000000 00000000 [......] repeat 152 times25DB2AB0 01400029 0140002C 00000000 00000000 [). @.,. @ ......] 25DB2AC0 00000000 00000000 00000000 [......] repeat 151 times25DB3440 00000000 00000000 0140002A 00000000 [........ *. @ ......] 25DB3450 00000000 00000000 00000000 00000000 [......] repeat 185 times25DB3FF0 00000000 00000000 00000000 ADB82301 [............. #...] extent Control Header www.2cto.com extends Extent Header: spare1: 0 spare2: 0 # extents: 1 # blocks: 8 last map 0x00000000 # maps: 0 offset: 2716 Highwater :: 0x0140002c ext #: 0 blk #: 3 ext size: 8 # blocks in seg. hdr's freelists: 0 # blocks below: 0 mapblk 0x00000000 offset: 0 Disk Lock: Locked by xid: 0x0004. 00e. 1000000f4 ------------------------------------------------------ Low HighWater Mark: Highwater: 0x0140002c ext #: 0 blk #: 3 ext size: 8 # blocks in seg. hdr's freelists: 0 # blocks below: 0 mapblk 0x00000000 offset: 0 Level 1 BMB for High HWM block: 0x01400029 Level 1 BMB for Low HWM block: 0x01400029 ---------------------------------------------------------- More -- from the above information, we can see the SQL error at the beginning. Which object is the corresponding? Check: 16: 03: 17 SQL> select object_id, data_object_id, owner, object_name, object_type from dba_objects where data_object_id in (51698,516 97) or object_id in (51698,516 97 ); OBJECT_ID DATA_OBJECT_ID OWNER OBJECT_NAME OBJECT_TYPE ---------- ---------------- ------------------------- 51697 51697 WWL WWL005 TABLE Metalink provides the following explanations: summary of Bugs Containing ORA-00600 [databases] [ID 466049.1] Using Modified 20-DEC-2009 Type REFERENCE Status PUBLISHED www.2cto.com In this Document Purpose Scope Summary of Bugs Containing ORA-00600 [databases] Using Applies: oracle Server-Enterprise Edition-Version: 9.2.0.8 to 10.2.0.4 Information in this document applies to any platform. purpose This article is intended to1. Help the reader to understand the ORA-600 [kcbz_check_objd_typ_3] error and how is this caused.2. List the most common bugs of the aforesaid error and thefixir es. scope This is a temporary lidated article based upon various bugs logged for the error ORA-600 [kcbz_check_objd_typ_3] and gives the reader an overview about the most frequent bugs which the MERs are affected. the error ORA-600 [kcbz_check_objd_typ_3] is raised because we see different object id in bufffer cache (BH) and on disk. summary of Bugs Containing ORA-00600 [published] Bug 5466416 --- Closed as Duplicate of Unpublished Bug 4430244 Abstract: ORA-600 [published] on insert via DBMS_STATS OR DBMS_SPACE www.2cto.com Versions affected: 10.2 ed fixreleases: 10.2.0.4, 11.0.0.0Details: Segment advisor code (eg: blocks) can load blocks into the cache for Dropped objects as CURRENT leadingto subsequent operations seeing an incorrect (old) version of a block. this can lead to varous internal buffer cache related errors such asORA-600 [kcbnew_3]/ORA-600 [kcbz_check_objd_typ_3]. the exact error depends on which code sees the block. backportable: yes to 10.2
Symptoms: 1. ORA-600 [kcbnew_3] internal error reported in the alert. log2. May occur if segment advisor and DROP operation are being run concurrently on the same object. workaround: SQL> alter system flush buffer cache 'to flush the buffer in the cache. patch Details: Check Metalink for Patch 4430244 availability. bug 5859511 -----> Closed as Duplicate of Unpublished Bug 4592596 Abstract: INTERMITTENT ORA-600 [KCBZ_CHECK_OBJD_TYP_3] from parallel SLAVESFixed releases: 10.2.0.4, 11.0.0.0Details: www.2cto.com upload uption can occur using a multi-table insert SQL with direct load operations. eg: If the SQL goes parallel. this can result in subsequent ORA-1410 type errors on selects from the target table/s. symptoms: 1. select on table fails with ORA-600 [kcbz_check_objd_typ_3] after multi-table insert with direct load was done.2.Analyze on the table fails with ORA-14103.Call Stack: -kcbassertbd3 implements kcbzib kcbgtcr ktrget extends kdstf 0010101km kdsttgr extends Workaround:-Do not use direct path (APPEND or PQ) in a multi-table insert SQLCheck Metalink for Patch 4592596 availability. unpublished Bug 5754708 ----> Closed as Duplicate of Unpublished Bug 4996133 Abstract: ORA-600 [KCBZ_CHECK_OBJD_TYP_3] FROM "SYS. DBMS_STATS "Fixed version: 9.2.08, A203, B106 Symptoms:-www.2cto.com 1. running in RAC mode 2. reading the overflow segment of an IOT 3. call Stack:-kdsgnp kafger qerixGetNonKeyCol success Or Call Stack:-kcbassertbd3 encrypt kcbzib kcbgtcr ktrget kdsgrp kdsfbr skip Workaround: Flush the buffer cache (10g onwards) or Restart the instance to clear its buffer cache. check Metalink for Patch 4996133 availability. bug 5348204 Abstract: ORA-600 [KCBZ_CHECK_OBJD_TYP_3] importing transportable tablespace from 10.1 Fixed In Ver: 10.2.0.1Symptoms:-1. cross Platform tablespace Import using Transportable tablespace option fails with following error messageORA-39083: Object type TABLE failed to create with error ORA-600: internal error code, arguments: [kcbz_check_objd_type_3] 2. call Stack:-javaskcbzib kcbgtcr ktecgsc ktecgetsh ktecgshx ktsscd_segment ktsscf_segment kdicpsc kdicrws Workaround:-Check Metalink for Patch 4331909 availability. www.2cto.com Bug 5689412 ORA-600 [found] after SCN Symptoms:-1> Primary and Standby Configuration 2> ORA-600 [kcbz_check_objd_typ_3] after SCN based recovery to SCN just before a TRUNCATE operation. example On primary create table y (d date, v varchar2 (30); insert into y values (SYSDATE, 'test1'); insert into y values (SYSDATE, 'test2'); truncate table y; Recover the standby to a point just prior to the truncate to recover this specific table. (Detemine the SCN by mining the redo) www.2cto.com recover standby database until change <SCN>;-> media recovery completes successfully alter database open read only; select * from y; ^ ORA-600 [kcbz_check_objd_typ_3] Workaround:-Check Metalink for Patch 5689412 availability. author: wuweilong