|
Problem IC71637
|
Status: Geschlossen |
DB2TOP EXITS WITHOUT SHOWING ANY DATA WHEN PLAYING WITH COLLECTED FILE IN REPLAY MODE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
DB2TOP exits without showing any of the data collected:
-------------start collection-----------------
db2top -d gp001001 -f /tmp/collect.bin.3 -C -m 10 -P 1
[03:45:14] Starting DB2 snapshot data collector, collection
every 2 second(s), max duration 10 minute(s), max file
growth/hour 100.0M, hit <CTRL+C> to cancel...
[03:45:17] Writing to '/tmp/collect.bin.3', should I create a
named pipe instead of a file [N/y]? N
[03:45:23] Creating '/tmp/collect.bin.3' as a normal file
[03:45:23] Increasing snapshot interval from 2 to 7 to limit
volume of collection
[03:45:30] 9.1M written, time 16.093, 2.0G/hour
[03:50:54] Increasing snapshot interval from 7 to 11 to limit
volume of collection
[03:51:05] 18.3M written, time 350.987, 189.1M/hour
[03:55:23] Max duration reached, 18.3M bytes, time was
608.780...
[03:55:23] Snapshot data collection stored in
'/tmp/collect.bin.3'
Exiting...
----------------------replay
mode-----------------------------------------
$ db2top -d gp001001 -f /tmp/collect.bin.3 -b l -A -P 1
*** End of input stream reached, size was 19279506...
No performance data to analyze for option 'l'
Exiting...
Problem is because the stream size limit is 100M/hour.
The above output show that db2top is estimating at
[03:51:05] the collection rate is 189.1M/hour and db2top
collected 18.3M in
about 10 minutes. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* B2TOP exits without showing any of the data collected: *
* *
* YOu see something like the following *
* *
* *
* -------------start collection----------------- *
* *
* db2top -d gp001001 -f /tmp/collect.bin.3 -C -m 10 -P 1 *
* *
* Starting DB2 snapshot data collector, collection e *
* very 2 second(s), max duration 10 minute(s), max file *
* growth/hour 100.0M, hit <CTRL+C> to cancel... *
* *
* Writing to '/tmp/collect.bin.3', should I create a named *
* pipe instead of a file [N/y]? N *
* *
* Creating '/tmp/collect.bin.3' as a normal file *
* *
* Increasing snapshot interval from 2 to 7 to limit volume of *
* collection *
* 9.1M written, time 16.093, 2.0G/hour *
* *
* Increasing snapshot interval from 7 to 11 to limit volume of *
* collection *
* 18.3M written, time 350.987, 189.1M/hour *
* *
* Max duration reached, 18.3M bytes, time was 608.780... *
* *
* Snapshot data collection stored in '/tmp/collect.bin.3' *
* Exiting... *
* *
* *
* ----------------------replay *
* mode--------------------------------- *
* $ db2top -d gp001001 -f /tmp/collect.bin.3 -b l -A -P 1 *
* *
* *** End of input stream reached, size was 19279506... *
* No performance data to analyze for option 'l' *
* *
* Exiting... *
* *
* Problem is because the stream size limit is 100M/hour. *
* *
* *
* The above output show that db2top is estimating at the *
* collection rate is 189.1M/hour and db2top collected 18.3M *
* in about 10 minutes. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.5 Fixpack 8 *
**************************************************************** |
| Local-Fix: |
If problem happens in replay mode, increase stream size by
adding streamsize=###M to .db2toprc file and rerun.
To estimate the size to of 'streadmsize' to use in .db2toprc use
the info from the previous attempt.
In the example above it shows 18.3M within 10 minutes.
Estimate the streamsize by taking the 18.3M * 6=110M/hour. Since
the volume
of captured snapshot data can flucturate leave a big margin
size. Increase 4-5 times the
size estimated. In this case set streamsize=500 in .db2toprc
file |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Fixed starting in V9.5 Fixpack 8 |
| Workaround |
If problem happens in replay mode, increase stream size by
adding streamsize=###M to .db2toprc file and rerun. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 01.10.2010
24.03.2011
24.03.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP8
|
| Problem behoben lt. FixList in der Version |
| 9.5.0.8
|
 |
