| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC95405 | Status: Closed |
SQL STATEMENT MAY HANG DUE TO A DEADLATCH WHEN PROCESSING SUBSECTIONS OF A ZIG ZAG JOIN PLAN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
The hang can be observed in db2pd -latches e.g. : Database Member 1 -- Active -- Up 0 days 05:21:19 -- Date 2013-03-21-09.49.47.079454 Latches: Address Holder Waiter Filename LOC LatchType HoldCount 0x07000000200147A8 11117 11374 |B9 8574 SQLO_LT_SQLD_APP_CB__inDMSlatch 1 0x0700000030CB55D8 11374 11117 c 207 SQLO_LT_SQLP_SAVEPOINTS__spLatch 1 i.e. the holder of both latches wait on each other to release their latch. both EDUs are subagents running the same SQL statement. The stack for both subagents may look like : sqloXlatchConflict sqlpGetSPLatch sqlpSpReq sqldRowInsert sqlrinsr sqlritib2 sqldEvalDataPred sqldReadNorm sqldFetchNext sqldfrd sqldRowFetch sqlritaSimplePerm sqlriZZOpenDims sqlriZZInit sqlriZigZagJoin sqlriSectInvoke sqlrr_dss_router sqlrr_subagent_router Subagent 2 has : getConflictComplex getConflict sqldRowInsert sqlrinsr sqlriisr sqlriSectInvoke sqlrr_dss_route sqlrr_subagent_router Once the hang occurs, the instance will need to be restarted by running db2_kill ( db2stop force will hang ) | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to v10.5 Fix Pack 3 or higher. * **************************************************************** | |
| Local Fix: | |
disable the use of of Zig Zag joins : db2set DB2_REDUCED_OPTIMIZATION="ZZJN OFF" | |
| available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
This problem was first fixed in v10.5 Fix Pack 3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 27.02.2014 27.02.2014 |
| 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 |
|
| 10.5.0.4 |
|