DB2 - Problem description
| Problem IC95254 | Status: Closed | 
| POSSIBLE HANG IN INDEX CLEANUP LOGIC WHEN MULTIPLE ASYNCHRONOUS CLEANUP OPERATIONS ARE ACTIVE ON THE SAME TABLE | |
| product: | |
| DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
| If a partitioned table has a global index and multiple partitioned are detached at once, then the Asynchronous Background Processing will start a number of db2taskp EDUs to perform the Asynchronous Index Cleanup. It is possible that these EDUs will start contending with each other over a particular area of the index and they get stuck in an endless loop. Taken call stacks repeatedly should show a pattern where these stacks can be seen : sqloWaitEDUWaitPost sqlplWaitOnWP sqlplMakeNewRequestNonSD sqlplrq sqlilidx sqliTryToMerge sqliCleanupKeysOnLeaf procLeaf2Del ... | |
| Problem Summary: | |
| **************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.3. * **************************************************************** | |
| Local Fix: | |
| temporarily limit the number of ABP tasks to 1 by setting : db2set DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:1 | |
| available fix packs: | |
| DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
| The problem is first fixed in DB2 version 10.5.0.3. | |
| Workaround | |
| not known / see Local fix | |
| Timestamps | |
| Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 02.12.2013 02.12.2013 | 
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.3 |  | 
| 10.5.0.3 |  | 







 
