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

DB2TOP COLLECTOR MODE (-C) STOPS IF 2GB OUTPUT FILE SIZE IS REACHED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Using db2top collector mode (-C) stops with error if output file 
exceeds 2GB size. 
 
Following is an example of the command line output of the db2top 
utility: 
 
db2top -d sample -C -i 30 -m 120 
[13:23:11] Starting DB2 snapshot data collector, collection 
every 30 second(s), max duration 120 minute(s), max file 
growth/hour 500.0G, hit <CTRL+C> to cancel... 
[13:23:13] Overridding previous occurence of 
'db2snap-sample-Linux64.bin' 
[13:23:43] 26.7M written, time 32.835, 2.9G/hour 
[13:24:15] 53.5M written, time 64.587, 2.9G/hour 
<...> 
[14:10:52] 1.8G written, time 2861.044, 2.3G/hour 
[14:14:16] 1.9G written, time 3065.507, 2.3G/hour 
[14:15:47] 16777215.9T written, time 3156.310, 16777215.9T/hour 
Warning: The current snapshot collection was skipped, because: 
The estimated file growth/hour, 2305873.2T , is greater than the 
max file growth/hour: 500.0G 
Therefore, the collected file, 'db2snap-sample-Linux64.bin' , 
may not be usable. Here are some recommendations: 
1) Increase the max file growth/hour by specifying 'streamsize' 
parameter in .db2toprc to at least: streamsize=2305873.2T 
2) Or increase the snapshot collection interval time by 
specifying option: -i
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem Fixed In 10.5.0.3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
04.03.2014
04.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList