Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC76598 Status: Closed

ON DPF IF DIAGPATH IS SPLIT PER HOSTNAME OR PER HOSTNAME/NODENAM E, ALL
QUERY PATROLLER (QP) DIAGNOSTICS LOGS STOP BEING GENERATE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
ON DPF environments, when DB2 diagnostics path is split per 
hostname: 
 
db2 update dbm cfg using diagpath '"/home/db2inst1/ $h"' 
 
or 
 
per hostname/nodename: 
 
db2 update dbm cfg using diagpath '"/home/db2inst1/ $h$n"' 
 
all query patroller (QP) logs stop being generated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using DB2 v95 FP8 and earlier                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ON DPF IF DIAGPATH IS SPLIT PER HOSTNAME OR PER              * 
* HOSTNAME/NODENAME, ALL QUERY PATROLLER (QP) DIAGNOSTICS LOGS * 
* STOP BEING GENERATE                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v95 FP9                                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 V95 FP9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79816 IC84138 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.05.2011
13.03.2012
13.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList