DB2 FOR LUW / DB2FORLUW / 950 - DB2

When a Get Snapshot (or equivalent snapshot table function) is 
executed, in rare scenarios when lock information is being 
collected, and locks are being manipulated by other 
applications, or other applications are performing 
connect/connect-reset operations, a segmentation violation trap 
is possible.  The stack trace will contain sqlpm_write_locks() 
as the violating function, like this example: 
 
sqlpm_write_locks 
 
sqlpm_write_appl_locks 
 
sqm_snap_appl_locks 
 
sqm_snap_db_locks 
 
sqlmonssagnt 
 
[...]

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This is a timing issue possibly produced when a get Snapshot * 
* agent is context-switched out just before it acquires        * 
* internal latch for transaction information, an application   * 
* switched in releases it's transaction (connect reset) and    * 
* when get Snapshot agent is switched back in, the internal    * 
* structures that it is pointing to have been already          * 
* released.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 and Fix Pack xx                   * 
****************************************************************

DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 9.5 and Fix Pack xx

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

29.09.2010
30.06.2011
30.06.2011

9.5.