DB2 - Problem description
Problem IC73778 | Status: Closed |
ADMIN_MOVE_TABLE STORED PROCEDURE PERFORMANCE ENHANCEMENT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
ADMIN_MOVE_TABLE uses COALESCE for triggers and replaying rows if the index that is used for replaying values has nullable columns . COALESCE affects the query optimizer decision not to choose an equal start/stop predicate. In addition, double binding the same value twice in statements that have parameter markers also suppress this query optimization as the optimizer cannot know that the parameter marker point to the same value. Not using the start/stop predicate cause significant performance penalty if nullable columns are involved. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * ADMIN_MOVE_TABLE uses COALESCE for triggers and replaying * * rows * * if the index that is used for replaying values has nullable * * * * columns . * * * * COALESCE affects the query optimizer decision not to * * choose an * * equal start/stop predicate. In addition, double binding the * * * * same value twice in statements that have parameter markers * * also * * suppress this query optimization as the optimizer cannot * * know * * that the parameter marker point to the same value. Not using * * the * * start/stop predicate cause significant performance penalty * * if * * nullable columns are involved. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 FixPak 5 * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v 9.7 FixPak 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.01.2011 06.02.2012 06.02.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |