DB2 - Problem description
Problem IT19568 | Status: Closed |
WHEN A DATABASE IS ORACLE COMPATIBLE, A STATEMENT HEAP CAN GROW ENORMOUSLY WHEN A QUERY HAS A LOT OF REFERENCES TO DUAL TABLE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
This can only happen when Oracle Compatibility is enabled. When one query uses a lot of DUAL (for instance, with UNION ALL clause), compiling that query can drive a statement heap to a enormous size. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
The workaround is to replace DUAL with SYSIBM.SYSDUMMY1. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT07703 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.03.2017 03.05.2017 16.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |