DB2 - Problem description
Problem IT17841 | Status: Closed |
LATCHES SUCH AS SQLO_LT_SQLP_DBCB__READBUFSEM ARE NOT BEING REPORTED IN MON_GET_EXTENDED_LATCH_WAIT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The MON_GET_EXTENDED_LATCH_WAIT table function isn't reporting all latches that have been involved in extended latch waits. For example, the following stack shows an EDU involved in a wait: <Stack> sqloXlatchConflict sqloxltc_track sqlpgrlg sqlpReadLogForCC sqldGetCurrentlyCommitted sqliLockUncond sqldRowFetch sqldRowFetch sqldRowFetch sqlritaSimplePerm sqlritaSimplePerm sqlritaSimplePerm sqlriSectInvoke sqlrr_process_fetch_request sqlrr_open sqljsParseRdbAccessed sqljsSqlam sqljsSqlam sqljsSqlam sqljsDriveRequests sqljsDrdaAsInnerDriver RunEDU RunEDU EDUDriver sqloEDUEntry </Stack> <LatchInformation> Waiting on latch type: (SQLO_LT_SQLP_DBCB__ReadBufSem) - Address: (0xa00030000199140), Line: 1553, File: sqlpgrlg.C </LatchInformation> However the ReadBufSem latch isn't reported by MON_GET_EXTENDED_LATCH_WAIT. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users on or before db2 v10.5 FP7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Once fixed, upgrade to fixpack which contains it. * **************************************************************** | |
Local Fix: | |
Use "db2pd -latches" to see current latch information. | |
Solution | |
Next fixpack will include the fix. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.11.2016 27.09.2017 27.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |