DB2 - Problembeschreibung
Problem IC76937 | 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 / 950 - 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 Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 Fix Pack 9 to be able to use the new * * option to limit the size of the target .evt files to the * * MAXFILESIZE setting. * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in Version 9.5 Fix Pack 9 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Kommentar | |
Please get in touch with service to enable the new option. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC77172 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2011 08.03.2012 08.03.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP9 | |
Problem behoben lt. FixList in der Version | |
9.5.0.9 |