DB2 - Problem description
Problem IT37690 | Status: Closed |
SPACE USED BY LOBS IN SOME EVENT MONITORS NOT REUSED WHEN THOSE LOBS ARE DELETED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Under certain conditions, space used by lobs in some event monitor tables will not reused when those lobs are deleted. This may cause the table spaces containing those event monitor tables to become full. Note that this APAR impacts only the following event monitor types: * Activity event monitor * Unit of work event monitor * Package cache event monitor * Locking event monitor * Statistics event monitor * Change history event monitor * Threshold violations event monitor | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP7 or later * **************************************************************** | |
Local Fix: | |
Periodically deactivate and reactivate event monitors. This will allow freed lob storage to be reused. Alternatively if the LOB columns in the event monitor target tables do not capture any data of interest, create the event monitor tables without those columns. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP7 or later * **************************************************************** | |
Comment | |
Upgrade to 11.5 FP7 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.07.2021 22.11.2021 22.11.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |