DB2 - Problem description
Problem IT05147 | Status: Closed |
DB2'S I/O STRATEGY FOR LONG/LOB DATA MAY CAUSE PERFORMANCE DEGRADATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
DB2's strategy for LONG/LOB writes may cause an apparent slowdown in I/O within DB2 (not at the operating system level). This is because contention may occur in DB2's internal file management when file sync operations are performed at commit time. This strategy is followed during heavier LONG/LOB write activity where LONG/LOB writes may become buffered (not written immediately to disk). On systems where LONG/LOB data is stored in tablespaces with NO FILE SYSTEM CACHING (direct I/O), there is no advantage in this strategy as the writes will not be buffered. If long wait times on the SQLO_LT_SqlbFhdlHashEntry__hashEntryLatch latch can be observed via the MON_GET_EXTENDED_LATCH_WAIT monitoring routine, consider disabling this behavior as follows : db2set DB2_BUFFER_LONG_DATA_WRITES=OFF This takes effect when the database is deactivated/activated. Example: db2 "select total_extended_latch_wait_time from table(mon_get_extended_latch_wait(null)) where LATCH_NAME='SQLO_LT_SqlbFhdlHash Entry__hashEntryLatch'" | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2/Systems with heavy LOB I/O * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
If long wait times are observed on the SQLO_LT_SqlbFhdlHashEntry__hashEntryLatch latch are observed, disable buffered LONG/LOB writes with db2set DB2_BUFFER_LONG_DATA_WRITES=OFF (the database must be recycled) | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fix Pack 5 | |
Workaround | |
see Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.10.2014 23.07.2015 23.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |