QMF for Windows stores detailed object tracking data in the Q.OBJ_ACTIVITY_DTL table, and summarized data in the Q.OBJ_ACTIVITY_SUMM table. These two tables are created during the bind QMF for Windows packages process. These tables are always created but will not be used unless you tell QMF for Windows to actually collect data. You do this by activating object tracking for a resource group.
QMF for Windows adds a row to the Q.OBJ_ACTIVITY_DTL table for each use of an object. For example, if a user executes a query (object) 20 times, 20 rows are added to the table. Unlike the detail table, the summary table, Q.OBJ_ACTIVITY_SUMM, has only one row for each object. So in this example, the object usage count, a field in the table, would increase by 20, but no new rows are added. Rows are added to the summary table only when a new object is created and rows are automatically deleted when an object is deleted.
Since the summary table will not grow without boundaries and the detail table will; it is more important to perform maintenance on the detail table and its associated table space (RAADB.RAAIX2) and index (Q.RAAIX2) with greater frequency than the summary table.
The following are recommendations for optimum performance of the Q.OBJ_ACTIVITY_DTL table:
DELETE FROM Q.OBJ.ACTIVITY_DTL WHERE "DATE" < (CURRENT DATE - 30 DAYS)