|
Problem IT02052
|
Status: Closed |
POOR PERFORMANCE WITH SUBSEQUENT UPDATES IN A SINGLE UOW WITH COLUMN ORGANIZED TABLES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Performing multiple Update commands on a table within a single
UOW without doing a Commit causes slow performance on the
subsequent Update commands with a Column Organized (BLU) table.
For example, with a 40 million row test table the initial Update
will perform as expected taking 0.07 seconds. When another
Update is run before a Commit then this, and any subsequent
Update commands, will be significantly slower taking nearly 0.5
seconds. After running a Commit the next Update then performs as
expected taking 0.07 seconds. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Column Organized table users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW 10.5 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 LUW 10.5 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.05.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
