DB2 - Problem description
Problem IT39279 | Status: Closed |
Db2 hangs with many EDUs waiting on logTailHeartBeatLatch | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Db2 hangs with many EDUs waiting on logTailHeartBeatLatch. This problem only occurs on database using HADR feature. It is caused by abnormal termination of "db2pd -hadr" command, where the db2pd process was killed while holding this particular latch. The problem can be identified with db2hadrp thread having the following stack: 0x090000006C2C0C98 sqloXlatchConflict + 0x8F8 0x090000006E089910 sqlpGetLogTailHeartBeat__FP9SQLP_DBCBP17SQLPG_LOG_TAIL_HB + 0x370 0x090000006DDB9FF0 hdrStoreLocMonElements + 0xAF0 0x090000006DDBA478 hdrStoreReceivedMonElements__FP8HDR_DBCBP11HDR_HDR_MSG + 0x58 0x090000006DDFF428 hdrEduP__6hdrEduFCbPUl + 0x2968 0x090000006DE160E0 hdrEduEntry__6hdrEduFv + 0x1DA0 Waiting on latch type: (SQLO_LT_SQLP_DBCB__logTailHeartBeatLatch) - Address: (0xa0002000009e2e8), Line: 6632, File: sqlputil.C | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * HADR * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to db2 version 11.1.4.7 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * HADR * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to db2 version 11.1.4.7 * **************************************************************** | |
Comment | |
Update to db2 version 11.1.4.7 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.12.2021 17.04.2022 17.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |