DB2 - Problem description
Problem IC71574 | Status: Closed |
GET SNAPSHOT SEGMENTATION FAULT WHILE COLLECTING LOCK INFORMATION IN SQLPM_WRITE_LOCKS() | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
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 [...] | |
Problem Summary: | |
**************************************************************** * 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 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 9.5 and Fix Pack xx | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.09.2010 30.06.2011 30.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.8 |