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 IC76437 Status: Closed

INTERRUPTING CLIENT MIGHT LEAD TO ENGINE HANG DUE TO AGENT STUCK IN
SEMOP().

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
In this example 'db2look' was used as the client. 
After interrupting 'db2look' using CTRL-C 
we can see that the 'db2look' process is gone 
as it does not appear in the 'ps' output anymore. 
 
$ ps -ef | grep db2look | grep -v grep 
 
However, db2look still appears in the list of applications. 
$ db2 list applications 
 
Auth Id  Application    Appl.      Application Id 
                                 DB       # of 
         Name           Handle 
                                 Name    Agents 
-------- -------------- ---------- 
-------------------------------------------------------------- 
-------- ----- 
E95Q7A   db2look        97         *LOCAL.e95q7a.110408030010 
                                 SAMPLE   1 
 
$ db2pd -db sample -locks 
 
Database Partition 0 -- Database SAMPLE -- Active -- Up 0 days 
00:04:13 -- Date 04/05/2011 13:34:33 
 
Locks: 
Address            TranHdl    Lockname                   Type 
   Mode Sts Owner      Dur HoldCount  Att  ReleaseFlg 
0x07000000303505C0 2          4442324C32473032E3E6718241 
Internal P ..S  G   2          1   0          0x00 0x40000000 
0x0700000030350E80 2          00000001000000010001240056 
Internal V ..S  G   2          1   0          0x00 0x40000000 
0x0700000030350A80 2          00000005000000000000000054 Table 
   .IN  G   2          1   1          0x00 0x40000000 
0x0700000030351C80 2          00000061000000000000000054 Table 
   .IN  G   2          1   1          0x00 0x40000000 
0x0700000030351A80 2          0000000C000000000000000054 Table 
   .IN  G   2          1   1          0x00 0x40000000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In this example 'db2look' was used as the client.            * 
* After interrupting 'db2look' using CTRL-C                    * 
* we can see that the 'db2look' process is gone                * 
* as it does not appear in the 'ps' output anymore.            * 
* However, as the outputs show below, the associated           * 
* application is still here and the locks db2 acquired are     * 
* still here as well and might cause the engine to hang.       * 
*                                                              * 
* $ ps -ef | grep db2look | grep -v grep                       * 
*                                                              * 
* However, db2look still appears in the list of applications.  * 
*                                                              * 
* $ db2 list applications                                      * 
*                                                              * 
* Auth Id  Application    Appl.      Application Id            * 
*                                 DB      # of                 * 
*         Name          Handle                                 * 
*                                 Name    Agents               * 
* -------- -------------- ----------                           * 
* ------------------------------------------------------------ * 
* --                                                           * 
* -------- -----                                               * 
* E95Q7A  db2look        97        *LOCAL.e95q7a.110408030010  * 
*                                 SAMPLE  1                    * 
*                                                              * 
* And here we see the locks that db2look acquired. Those locks * 
* will                                                         * 
* not be freed and can cause the engine to hang.               * 
*                                                              * 
* $ db2pd -db sample -locks                                    * 
*                                                              * 
* Database Partition 0 -- Database SAMPLE -- Active -- Up 0    * 
* days                                                         * 
* 00:04:13 -- Date 04/05/2011 13:34:33                         * 
*                                                              * 
* Locks:                                                       * 
* Address            TranHdl    Lockname                  Type * 
*   Mode Sts Owner      Dur HoldCount  Att  ReleaseFlg         * 
* 0x07000000303505C0 2          4442324C32473032E3E6718241     * 
* Internal P ..S  G  2          1  0          0x00 0x40000000  * 
* 0x0700000030350E80 2          00000001000000010001240056     * 
* Internal V ..S  G  2          1  0          0x00 0x40000000  * 
* 0x0700000030350A80 2          00000005000000000000000054     * 
* Table                                                        * 
*   .IN  G  2          1  1          0x00 0x40000000           * 
* 0x0700000030351C80 2          00000061000000000000000054     * 
* Table                                                        * 
*   .IN  G  2          1  1          0x00 0x40000000           * 
* 0x0700000030351A80 2          0000000C000000000000000054     * 
* Table                                                        * 
*   .IN  G  2          1  1          0x00 0x40000000           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.5 fixpack 9.                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.5 FixPack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC76636 IC76637 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.05.2011
22.03.2012
22.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList