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 IC77172 Status: Geschlossen

A SINGLE MONITORING EVENT, SUCH AS A DEADLOCK, CAN CREATE A FILE LARGER
THAN WHAT IS SPECIFIED BY MAXFILESIZE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Currently, a single monitoring event will be written to a new 
file if it does not fit in the current .evt file based on 
MAXFILESIZE.  However, the new file will be as large as needed 
to record the entire single event in one file.  This can result 
in a very large event file. 
 
The fix for this APAR provides an option to force an event 
record to fit into the target event file, up to the size defined 
by the MAXFILESIZE setting specified while creating the event 
monitor, by truncating the event record if necessary. So, for 
example, if a deadlock event dumps out a very large listing of 
locks, this information will be truncated to MAXFILESIZE.  The 
registry setting can be turned on and off by: 
 
db2set DB2_SYSTEM_MONITOR_SETTINGS=ENFORCE_MAX_FILE_SIZE:TRUE 
db2set DB2_SYSTEM_MONITOR_SETTINGS=ENFORCE_MAX_FILE_SIZE:FALSE 
 
db2stop 
db2start 
 
The default behavior will continue to be writing the entire 
event record into a single file without any truncation of data, 
thus allowing the size of the target .evt file to grow beyond 
the MAXFILESIZE setting.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6.                       * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 9.7 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.06.2011
02.08.2012
02.08.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList