DB2 - Problem description
| Problem IT02731 | Status: Closed |
DEAD LATCH WHEN RUNNING TRUNCATE TABLE OPERATION AND ANOTHER AGENT LOOKS TO FLUSH THE BUFFERPOOL | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
A deadlatch situation can occur when running TRUNCATE TABLE operation and another EDU tries to FLUSH the BUFFERPOOL, either via the FLUSH BUFFERPOOL statement, or a command that also requires the BUFFERPOOLs to be FLUSHED (e.g. Online Backup). db2pd -latches may show : a lot of Waiters on latch : SQLO_LT_SQLB_BufferPool__prevBPDCachingLatch and the EDU holding this latch, waiting on SQLO_LT_SQLB_BPD__bpdLatch_SX. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1fp5 * **************************************************************** | |
| Local Fix: | |
| Solution | |
First fixed in DB2 10.1fp5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.06.2014 09.05.2017 09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|