home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76194 Status: Geschlossen

LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS SPLIT PER
HOSTNAME AND/OR HOSTNAME/NODENAME.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using split diagpath on DB2 v95 FP8 and earlier.   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS * 
* SPLIT PER HOSTNAME AND/OR HOSTNAME/NODENAME.                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V95 FP9                                       * 
*                                                              * 
* or                                                           * 
*                                                              * 
* As a temporary wokaround, stop using split diagpath.         * 
****************************************************************
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.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First Fixed in DB2 v95 FP9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC76308 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.05.2011
13.03.2012
13.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList