DB2 - Problembeschreibung
Problem IC99539 | Status: Geschlossen |
db2top in background replay mode ignores the first snapshot stream data | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * all using db2top * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.1 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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
first fixed in version 10.1 fix pack 4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.02.2014 03.06.2014 03.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |