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

DB2 GET SNAPSHOT FOR ALL APPLICATION GLOBAL DOES NOT COLLECT TP INFORMATION
ON ALL NODES.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
You may encounter missing TP Monitor information, if you execute 
get snapshot with global from a node that does not have TP 
Monitor information. 
 
The following is an example of information being returned 
properly from a node having TP monitor infomation -- 
 
TP Monitor client user ID           = AAAA 
TP Monitor client workstation name  = BBBB 
TP Monitor client application name  = CCCC 
TP Monitor client accounting string = DDDD 
 
However, if you execute get snapshot with global on other nodes 
not having TP Monitor data locally, the information will be 
missed -- 
 
TP Monitor client user ID           = 
TP Monitor client workstation name  = 
TP Monitor client application name  = 
TP Monitor client accounting string =
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Can not get TP variables via snapshot.                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See the APAR description.                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 1.                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.7 Fixpack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
23.02.2010
23.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList