|
Problem IC89783
|
Status: Closed |
AFTER AN APPLICATION IS BEING KILLED, ITS SPAWNED TRANSACTIONS ARE LEFT IN EXECUTING STATE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 V101 FP2 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v101 FP3 *
**************************************************************** |
| Local Fix: |
As a temporary workaround, restart db2:
db2 force applications all
db2stop force
db2start |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in Db2 v101 FP3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC91062
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.01.2013
18.10.2013
18.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
