Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76437 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.5 FixPack 9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC76636 IC76637 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.05.2011
22.03.2012
22.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList