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

db2pd -latches output reports incorrect latch holder information.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This error was occurring even when there really were holders 
traced by comparing the edu stack trace dump file, which showed 
edu was holding a latch, but db2pd -latch output says there were 
0 holders of that latch. 
 
$ db2pd -latch 
 
Database Member 0 -- Active -- Up 0 days 00:00:46 -- Date 
04/27/2011 13:12:18 
 
Latches: 
Address                     Holder     Waiter     Filename 
  LOC    LatchType 
No latch holders. 
0x00002AAAB6333A24    0          26         sqle_agent.C  4246 
 SQLO_LT_xmlcStringCache__LRULatch 
0x00002AAAB6333A2C   0          41         sqle_agent.C   4239 
 SQLO_LT_xmlcStringCache__stringLatch
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms affected.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Starting with v95fp6, db2pd -latches has been returning      * 
* wrong results: holders were displayed as all 0's.            * 
* This error was occurring even when there really were holders * 
* traced by comparing the edu stack trace dump file, which     * 
* showed edu was holding a latch, but db2pd -latch output says * 
* there were 0 holders of that latch.                          * 
*                                                              * 
* $ db2pd -latch                                               * 
*                                                              * 
*                                                              * 
* Database Member 0 -- Active -- Up 0 days 00:00:46 -- Date    * 
*                                                              * 
* 04/27/2011 13:12:18                                          * 
*                                                              * 
* Latches:                                                     * 
*                                                              * 
* Address                         Holder    Waiter    Filename * 
* LOC     LatchType                                            * 
*                                                              * 
* No latch holders.                                            * 
*                                                              * 
* 0x00002AAAB6333A24     0          26        sqle_agent.C     * 
* 4246    SQLO_LT_xmlcStringCache__LRULatch                    * 
*                                                              * 
* 0x00002AAAB6333A2C     0          41        sqle_agent.C     * 
* 4239   SQLO_LT_xmlcStringCache__stringLatch                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Customer should upgrade to V97FP5 and upper                  * 
* releases/fix-packs.                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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

Solution
The problem has been fixed for V97FP5 and will be done on upper 
releases as well.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.06.2011
08.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList