DB2 - Problem description
Problem IC99540 | Status: Closed |
db2top in background replay mode ignores the first snapshot stream data | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - 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 in replay mode * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.5 Fix Pack 4 * **************************************************************** | |
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. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
First fixed in version 10.5 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.02.2014 09.09.2014 09.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |