|
Problem IT10392
|
Status: Closed |
APPLICATION STILL SHOWS AS "UOW EXECUTING" WHEN THE LOCAL CLIENT IS TERMINATED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Sometime, when a local client application is terminated(by
CTRL-C or kill), "db2 list application" and "db2pd -app" still
shows the corresponding application for ever, the associated
agents never be released.
In one known case, when the user canceled a perl script
connecting to a local DPF server by pressing CTRL-C, the
application hangs there:
$ db2 list application
Auth Id Application Appl. Application Id
DB # of
Name Handle
Name Agents
-------- -------------- ----------
--------------------------------------------------------------
-------- -----
AD920634 perl5.x.x 125 *LOCAL.ad920634.150720055030
SAMPLE 1
The coord-agent is waiting for ipc from the client:
0x09000000001F9040 semop + 0xC0
0x09000000A4B174F0 .sqloSSemP.fdpr.clone.4704 + 0x1C0
0x09000000A4B170A4
.sqlccipcrecv.fdpr.clone.3609__FP17SQLCC_COMHANDLE_TP12SQLCC_CON
D_T + 0x344
0x09000000A4B16A78 sqljcReceive__FP10sqljCmnMgr + 0x794
The sub-agents are wating for a reply from the coord-agent:
0x09000000001180B8 thread_wait + 0x98
0x09000000A4C70990 sqloWaitEDUWaitPost + 0x524
0x09000000A6054100
WaitSendReady__11sqkfChannelFiN21P10sqkfBuffer + 0x16B0
0x09000000A5E8F4E4
SendDataBuffer__11sqkfChannelFRP10sqkfBufferiT2 + 0x1428
0x09000000A605CA48
sqlkqsnd__FP8SQLKQ_CBP8sqeAgentiPP10sqkfBufferT3Us + 0x1300
0x09000000A2F3212C sqlktsnd__FP9sqlri_taoiUs + 0x210
0x09000000A39D85C0
sqlkt_pack_tuple__FP10SQLD_FIELDP9sqlri_taolPP10SQLD_VALUEP5sqlc
aUsP8sqeAgent + 0x1608
0x09000000A43FD00C
sqlktins__FP7sqlr_dbP8sqeAgentP10sqlri_iudoP5sqlcaUs + 0x730
0x09000000A43924E4 sqlritqb__FP8sqlrr_cb + 0x698
0x09000000A4BBB0C8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x34 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 FIXPACK 7. *
**************************************************************** |
| Local Fix: |
Force off the application manually:
db2 "FORCE APPLICATION(<APPHDL>)" |
| Solution |
The problem is firstly fixed on V10.5 FIXPACK 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.07.2015
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
