DB2 - Problem description
Problem IC62753 | Status: Closed |
PERFORMANCE PROBLEMS WHEN VERY LONG RUNNING TRANSACTIONS CREATE GLOBAL TEMP TABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When a long running transaction issues many statements refering to a declared global temporary table that has been created in the current transaction - or for which an index has been created in the current transaction, then the statements are inserted in the package cache and are not able to be removed from the package cache until the transaction ends. This can cause the package cache to overflow and use up additional memory on the system This causes slow execution of queries. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using GLOBAL TEMP TABLES. * **************************************************************** * PROBLEM DESCRIPTION: * * PERFORMANCE PROBLEMS WHEN VERY LONG RUNNING TRANSACTIONS * * CREATE * * GLOBAL TEMP TABLES. Commit DDL associated with declared * * global temporary tables * * before long running transactions * **************************************************************** * RECOMMENDATION: * * PERFORMANCE PROBLEMS WHEN VERY LONG RUNNING TRANSACTIONS * * CREATE * * GLOBAL TEMP TABLES. Commit DDL associated with declared * * global temporary tables * * before long running transactions * **************************************************************** | |
Local Fix: | |
commit DDL associated with declared global temporary tables before long running transactions | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
PERFORMANCE PROBLEMS WHEN VERY LONG RUNNING TRANSACTIONS CREATE GLOBAL TEMP TABLES. Commit DDL associated with declared global temporary tables before long running transactions | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.08.2009 21.12.2009 21.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |