DB2 - Problem description
Problem IT18310 | Status: Closed |
ADDITIONAL CALLS IN AGENT BREATHING POINT CAUSE POOR PERFORMANCEIN LOAD UTILITY | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Excessive looping in Agent Breathing Point causes poor performance in the LOAD utility and may make the utility appear to hang. To identify, threads may be in this stack: 0x0900000068096D0C sqldReadTemp__FP13SQLD_DFM_WORKl + 0x38C 0x09000000677F8E94 @114@sqldFetchNext__FP13SQLD_DFM_WORK + 0x18 0x0900000068312C24 sqldfrd__FP13SQLD_DFM_WORK + 0x1188 0x0900000067971C74 sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT 3P12SQLD_ID_LISTP9SQLP_LSN8 + 0x374 0x09000000656E6284 sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc@OL@23909 + 0x700 0x090000006708ABF4 sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc + 0xA4 0x0900000066A5EDD4 sqluDMSortFetch__FPUcP4svalT1Pii + 0x80C and Trace timings will show that LOAD is in the INDEX BUILD phase. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Fix Pack 2 * **************************************************************** | |
Local Fix: | |
We can set DB2_ROWCOMP_TEMP=disable=util and it will avoid this area of looping. Please keep in mind that setting this variable will make some changes in the internal compression used in utilities such as LOAD and REORG. While their overall performance will be the same, setting this variable will mean that they require additional TEMP space. | |
available fix packs: | |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 11.1 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.12.2016 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |