DB2 FOR LUW / DB2FORLUW / 970 - DB2

After the application is killed, its spawned transactions are 
still active in db and in executing state holding the locks 
required for their processing. 
 
They cant be forced off. DB2 need to be restarted in order to 
clean those orphaned transactions and clean all locks held. 
 
The stack dumps may look as follows: 
 
0x090000000A140660 sqljcReadUint16Split__FP10sqljCmnMgrPUs + 
0x188 
0x090000000A128EA8 
sqljsDrdaAsCBBindinPurgeExtDtas__FP14db2UCinterface + 0x1114 
0x090000000A124500 sqlribniLobCbDrda__FP14db2UCinterface + 0x1A4 
0x0900000008B24490 sqlribni__FP8sqlrr_cb + 0x2AC 
0x0900000008F93DC8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x24 
0x0900000008F6D478 sqlrr_process_execute_request__FP8sqlrr_cbib 
+ 0xDD4 
 
 
db2diag.log may contain the following message: 
 
 
2013-01-18-09.08.29.302570-300 I20572A686           LEVEL: 
Severe 
PID     : 9502930              TID : 34990          PROC : 
db2sysc 0 
INSTANCE: vpcinp01             NODE : 000           DB   : VPCDB 
APPHDL  : 0-937                APPID: 
169.69.30.99.46709.130118140841 
AUTHID  : VPC_USER             HOSTNAME: 
cto2a192n1.svr.us.jpmchase.net 
EDUID   : 34990                EDUNAME: db2agent (VPCDB) 0 
FUNCTION: DB2 UDB, runtime interpreter, sqlriCpcConvertLob2Long, 
probe:6037 
MESSAGE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC 
          "External Comm error" 
DATA #1 : String, 25 bytes 
sqlriCpcConvertLob2Long: 
DATA #2 : String, 33 bytes 
EXTDTA parsing failed on continue

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL users on DB2 V97 FP8 and lower                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V97 FP9                                       * 
****************************************************************

As a temporary workaround, restart db2: 
 
db2 force applications all 
db2stop force 
db2start

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
 

First Fixed in DB2 V97 FP9

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.03.2013
17.12.2013
17.12.2013

9.7.FP9