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 IT00383 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB v10.5 Fixpak 3                            * 
****************************************************************
Local-Fix:
Lösung
Problem first fixed in v10.5 Fixpak 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.03.2014
06.10.2014
06.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList