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 IT00302 Status: Closed

DB2SUPPORT WRONGLY ASSUMES SHARED PATH IF DB2DIAGPATH IS NOT SPLIT AND HAS
THE SAME VALUE ON MULTIPLE NODES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If db2support sees the same value for non-split DB2DIAGPATH on 
different nodes/hosts then it assumes that the path is shared 
while indeed it could be simply an identical path on different 
machines. It seems that  db2support should check 
that the shared path is valid before assuming it is. 
 
As a result of this, diagnostic data in DIAGPATH can be missing 
for some nodes located on different hosts when running 
db2support 
because db2support will not be able to find data for other nodes 
as they do not reside on the same host.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpak 4                                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fix included in v10.1 Fixpak 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.03.2014
09.06.2014
09.06.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 FixList