home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC84138 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 / A10 - 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 on DB2 v10 GA                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 FP1                                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 V10 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList