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

PERFORMANCE ENHANCEMENT TO MEMORY ALLOCATION CODE FOR CONCURRENT
INSERT/UPDATE WITH CODE PAGE CONVERSION

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
It was determined that during heavy concurrent insert/update 
operations involving code page conversion into a unicode 
database that the malloc'ing of memory from the OS can become a 
bottleneck during the code page conversion process. 
 
environment: 
 
1. DB2 9.5 and up 
2. The database codepage is UTF. 
3. The application codepage is not. 
4. There are frequent and concurrent insert/update to the 
database. 
 
this was uncovered during a customer PMR with 50-100 concurrent 
import jobs against the same table.  After a certain point the 
percentage of time spent in ossLockGetConflict() reaches 75% 
trying to malloc and free memory.
Problem-Zusammenfassung:
Users Affected: Any doing heavy concurrent insert/update 
operations with code page conversion. 
Problem Description: During a heavy concurrent insert / update 
with code page conversion, perfomance can be affected by memory 
operations 
Problem Summary: see above.
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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
Problem was first fixed in Version 9.5 FixPak 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68268 IC68269 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.04.2010
07.10.2010
07.10.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version