| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC76308 | Status: Closed |
LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS SPLIT PER HOSTNAME AND/OR HOSTNAME/NODENAME. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
If lock timeout capturing is being done (db2set DB2_CAPTURE_LOCKTIMEOUT=YES) and lock timeout issues occur, DB2 generates lock timeout reports in diagnostics path defined by DIAGPATH dbm cfg parameter which have the following format: db2locktimeout.par.AGENTID.yyyy-mm-dd-hh-mm-ss, where par is the database partition number. In non-partitioned database environments, par is set to 0. AGENTID is the agent ID. yyyy-mm-dd-hh-mm-ss is the time stamp, consisting of the year, month, day, hour, minute, and second. However, when diagnostics path is split per hostname and/or hostname/nodename on DPF environments, then lock timeout reports stop being generated thus no lock timeout information is logged. EX: db2 update dbm cfg using DIAGPATH '"<path> $h"' or db2 update dbm cfg using DIAGPATH '"<path> $h$n"' When lock timeout occurs, and db2 can not write to lock timeout report file due to having $h or $h$n in DIAGPATH value, the following error is logged in db2diag.log: 2011-05-03-16.45.40.808485-240 I235231A523 LEVEL: Warning PID : 2199742 TID : 5428 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : SAMPLE APPHDL : 0-93 APPID: *N0.anik.110503204458 AUTHID : db2inst1 EDUID : 5428 EDUNAME: db2agntp (SAMPLE) 1 FUNCTION: DB2 UDB, lock manager, sqlpLockTimeoutInfo, probe:70 MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path" DIA8514C An invalid file path, "", was specified. With this APAR fix, the lock timeout reports will be generated and logged. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using split DIAGPATH per hostname and/or * * hostname/nodename * **************************************************************** * PROBLEM DESCRIPTION: * * LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS * * SPLIT PER HOSTNAME AND/OR HOSTNAME/NODENAME. * **************************************************************** * RECOMMENDATION: * * Apply DB2 V97 FP5 * **************************************************************** | |
| Local Fix: | |
As a temporary workaround before the fix for this APAR is applied, stop using splitting the diag path perf hostname or hostname/nodename. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
| Solution | |
The Problem was first fixed in db2 v97 fp5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.05.2011 22.12.2011 22.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 |
|