DB2 - Problem description
Problem IC98138 | Status: Closed |
GLOBAL LOCK SNAPSHOT CAN TRAP WHEN INDOUBT TRANSACTIONS ARE PRESENT IN A DB2 ENVIRONMENT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
During the processing of a GLOBAL LOCK SNAPSHOT in a DB2 system, The Instance may trap, if an indoubt transaction exists. If DPF environment is used, then indoubt transaction can be present on one or more members. The db2diag.log file should show the following probes: <TIME INFORMATION> LEVEL: Warning PID : <PID> TID : <TID> PROC : db2sysc 0 INSTANCE: <Instance Name> NODE : <Node No> DB : APPHDL : <Value> APPID: <Value> AUTHID : <Value> EDUID : <EDU ID> EDUNAME: db2agent (instance) 0 FUNCTION: DB2 UDB, database monitor, sqm___sqm_snap_db_locks, probe:100 MESSAGE : Lock monitoring output may be incomplete. If DIAGLEVEL is set to 4, db2diag.log will show this two probes, For Example: 2013-10-16-12.36.38.564496-240 I889695E390 LEVEL: Warning PID : 22924 TID : 139830738544384 PROC : db2sysc 1 INSTANCE: svtdbm2 NODE : 001 APPHDL : 0-1319 HOSTNAME: svtlnx3 EDUID : 366 EDUNAME: db2agntp 1 FUNCTION: DB2 UDB, database monitor, sqm___sqm_snap_db_locks, probe:100 MESSAGE : Lock monitoring output may be incomplete. : 2013-10-16-12.36.39.070500-240 I10775916E602 LEVEL: Error PID : 22936 TID : 140683243415296 PROC : db2sysc 0 INSTANCE: svtdbm2 NODE : 000 DB : APPHDL : 0-1319 APPID: *N0.svtdbm2.131016163643 AUTHID : SVTDBM2 HOSTNAME: svtlnx3 EDUID : 534 EDUNAME: db2agent (instance) 0 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x00007FF35E80F952 : 0000 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 V10 users of DPF environment * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to product version V10.1 fp4 * **************************************************************** | |
Local Fix: | |
Fetch LOCK snapshot data separately, in Serial setup, make sure no indoubt transactions exist. In DPF environment fetch each member's LOCK snapshot data separately by specifying "AT MEMBER" to direct a series of snapshots to particular members, Rather than specifying "GLOBAL" on the GET SNAPSHOT command. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
When running Global lock snapshots in db2 v10.1, and indoubt transactions are present in DPF environment, DB2 may trap | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.12.2013 02.06.2014 05.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |