home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71365 Status: Closed

DB2 instance may crash when extended Indicator is on

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If the extender indicator is enabled (JCC driver is enabled by 
default) DB2 could be crashed on the following callstack. 
 
 
Here's a partial callstack showing 
sqlraExtIndCheckColAuthPriv(). 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002BA0802F793F ossDumpStackTraceEx + 0x01ef 
        (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00002BA0802F2706 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc 
        (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00002BA07D60CE0D sqlo_trce + 0x03fb 
        (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002BA07D6513FB sqloEDUCodeTrapHandler + 0x0243 
        (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00000030AB60EB10 address: 0x00000030AB60EB10 ; dladdress: 
0x00000030AB600000 ; offset in lib: 0x000000000000EB10 ; 
        (/lib64/libpthread.so.0) 
0x00002BA07D904E8A 
_Z27sqlraExtIndCheckColAuthPrivP8sqlrr_cbP25sqlra_sql_context_si 
bling 
+ 0x0128 
        (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002BA07C1F0E3F _Z29sqlrr_process_execute_requestP8sqlrr_cbi 
+ 0x1a73 
        (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
or 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000010B5CB90 
sqlraExtIndCheckColAuthPriv__FP8sqlrr_cbP25sqlra_sql_context_sib 
ling + 0x264 
0x090000000F4D2D68 sqlrr_process_execute_request__FP8sqlrr_cbi + 
0x3D0 
0x09000000129D9C08 
.sqlrr_execute.fdpr.clone.1979__FP14db2UCinterfaceP9UCstpInfo + 
0xB8 
0x09000000129D994C 
.sqljs_ddm_excsqlstt.fdpr.clone.224__FP14db2UCinterfaceP13sqljDD 
MObject + 0xA94 
0x09000000129D87A4 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0xE8 
0x09000000129D8C24 
.sqljsParse.fdpr.clone.136__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x260 
0x0900000012934450 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0xB44 
0x0900000012B95E98 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 
0x0900000012B95C5C 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x268 
0x0900000012B95688 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xE4 
0x0900000012B29CC0 RunEDU__8sqeAgentFv + 0x7C 
0x0900000012B21898 EDUDriver__9sqzEDUObjFv + 0xDC 
0x0900000012B2177C sqlzRunEDU__FPcUi + 0x14 
0x0900000012B1C58C sqloEDUEntry + 0x264 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 and JCC users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 may crash if the extender indicator is enabled.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP4 or higher                             * 
****************************************************************
Local Fix:
Workaround the issue using one of the two options: 
 
1) grant DBADM to the application user 
 
or 
 
2) disable extended Indicator in JCC application. 
 
  String url = "jdbc:default:connection"; 
Properties prop = new Properties(); 
prop.put("enableExtendedIndicators", "2"); // public final 
static int NO = 2 
 
    try { 
      con = DriverManager.getConnection(url, prop);
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This APAR is first fixed on DB2 Version 9.7 Fix Pack 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73393 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.09.2010
29.04.2011
24.02.2012
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList