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

db2top in background replay mode ignores the first snapshot stream data

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
db2top utility when used in background replay mode does not 
generate an output file if the captured snapshot file contains 
only one iteration of data. 
 
Reproduction : 
 
Gathering the snapshot using the following command will have 
db2top run in collector mode for 2 minutes duration and collects 
snapshot data every 2 minutes ( 120 seconds) thus gathering only 
one iteration of data: 
 
db2top -d sample -f db2snap-sample-AIX64.out -C -m 2 -i 120 
 
When trying to read this stream in background mode, it yields no 
output in file "myoutput" below. In fact, the output file is not 
created. Notice the absence of messages relating to the output 
file: 
 
$ db2top -d sample -f db2snap-sample-AIX64.out -b l -o myoutput 
*** End of input stream reached, size was 20696821... 
Exiting...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All using db2top                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 9.7 fix pack 10                           * 
****************************************************************
Local Fix:
Run db2top in collector mode longer ( or with shorter interval 
such as using its default 2 seconds interval ), so that there 
are at least two iterations of snapshot stream data were 
collected.
Solution
First fixed in version 9.7 fix pack 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC99539 IC99540 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.02.2014
10.11.2014
10.11.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList