home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC94011 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FixPack 3                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 FixPack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.07.2013
04.10.2013
04.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList