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

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

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
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:
available fix packs:
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

Solution
Problem was first fixed in Version 9.5 FixPak 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68268 IC68269 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.04.2010
07.10.2010
07.10.2010
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)