Bug 5219489: ORA-600 [KOKLISMEM2: INSUFFICIENT LOCATOR]/[KOKLISMEM111: BFILE LOCATOR] ON LOB
--------------------------------------------------------------------------------
Bug Attributes
--------------------------------------------------------------------------------
Type B - Defect Fixed in Product Version -
Severity 2 - Severe Loss of Service Product Version 10.1.0.5
Status 96 - Closed, Duplicate Bug Platform 212 - IBM AIX on POWER Systems (64-bit)
Created 11-May-2006 Platform Version 5.3
Updated 02-Oct-2007 Base Bug 3320704
Database Version 10.1.0.5
Affects Platforms Generic
Product Source Oracle
Related Products
--------------------------------------------------------------------------------
Line Oracle Database Products Family Oracle Database
Area Oracle Database Product 5 - Oracle Server - Enterprise Edition
Hdr: 5219489 10.1.0.5 RDBMS 10.1.0.5 DICTIONARY PRODID-5 PORTID-212 ORA-600 3320704Abstract: ORA-600 [KOKLISMEM2: INSUFFICIENT LOCATOR]/[KOKLISMEM111: BFILE LOCATOR] ON LOB*** 05/11/06 12:27 am ***TAR:----PROBLEM:-------- ORA-600 [koklismem2: insufficient locator], [0], [86], [], [], [], [], []or ORA-600 [koklismem111: BFILE locator], [], [], [], [], [], [], []occurs during update table which has LOB column such as: update testtab set c2 = nvl2(c3, 1, 9) where c1 = 1 (c3 is LOB column, please refer blow testcase)DIAGNOSTIC ANALYSIS:--------------------The ORA-600 reproduced when - with WHERE clause using PK or unique column) - using LOB column in function (for example, NVL2 or LENGTH)It reproduces on 9.2/10.1, not reproduces on 10.2Thanks.WORKAROUND:-----------not foundRELATED BUGS:-------------bug 4696268bug 5205837REPRODUCIBILITY:----------------Y 9.2.0.7 Solaris32Y 10.1.0.5 AIX5LY 10.1.0.5 Linux32Y 10.1.0.5 Solaris64N 10.2.0.1 Linux32N 10.2.0.2 Linux32TEST CASE:----------drop table testtab;create table testtab (c1 number primary key, c2 number, c3 clob);insert into testtab values (1, 0, 'A');commit;alter system flush shared_pool;update testtab set c2 = nvl2(c3, 1, 9) where c1 = 1;# reproducibility is almost 100%STACK TRACE:------------ksedmp kgerinv kgeasnmierr koklismem updprhc updgrh upduaw kdusru kauupdupdrow qerupRowProcedure qerupFetch updaul updThreePhaseExe updexe opiexekpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o mainSUPPORTING INFORMATION:-----------------------I will upload trace files later24 HOUR CONTACT INFORMATION FOR P1 BUGS:----------------------------------------DIAL-IN INFORMATION:--------------------IMPACT DATE:------------*** 05/11/06 12:32 am *** (CHG: Sta->16)*** 05/11/06 12:32 am ****** 05/11/06 12:38 am *** (CHG: Asg->NEW OWNER OWNER)*** 05/14/06 06:54 pm ****** 05/15/06 10:58 pm *** (CHG: Sta->11 SubComp->LOB ACCESS)*** 05/15/06 10:58 pm ****** 05/15/06 10:59 pm *** (CHG: Asg->NEW OWNER OWNER)*** 05/15/06 10:59 pm ****** 05/17/06 02:35 pm *** (CHG: DevPri->4)*** 05/17/06 02:35 pm *** (CHG: Confirmed Flag->Y)*** 05/17/06 02:35 pm ****** 11/10/06 09:52 am *** (CHG: Asg->NEW OWNER OWNER)*** 04/13/07 07:26 am *** (CHG: SubComp->RAM LOBS)*** 04/13/07 07:26 am ****** 04/13/07 07:28 am *** (CHG: Asg->NEW OWNER OWNER)*** 04/13/07 07:28 am ****** 04/17/07 12:38 pm *** (CHG: Asg->NEW OWNER OWNER)*** 04/17/07 12:38 pm ****** 05/09/07 04:57 pm *** (CHG: DevPri->2)*** 05/09/07 04:57 pm *** (CHG: Sta->36)*** 05/09/07 04:57 pm ****** 05/09/07 04:57 pm *** (CHG: SubComp->DICTIONARY)*** 05/09/07 05:07 pm ****** 10/02/07 07:03 am *** (CHG: Sta->96)