How can you obtain information about any changes that have been made by the Self-Tuning Memory Manager (STMM)?
A.
By using the change history event monitor.
B.
By using the DB2 problem determination tool.
C.
By examining the contents of the system catalog.
D.
By examining the DB2 administration notification log file.
Changes can be explicitly caused by a user. For example, an administrator might run a DDL statement that drops an index. Or, changes might occur implicitly or automatically without any user interaction. For example, the self-tuning memory manager (STMM) might change a configuration parameter, or automatic table reorganization might reorganize a table.
Manually tracking changes to the database server can be a difficult task. Historically, the information for different types of changes has been captured through different interfaces. For example, configuration updates are written to the diagnostic log files (for example, the db2diag log files), while utility progress is captured in the database history file. The change history event monitor provides you with a single interface that captures the events that change the behavior and performance characteristics of your database system. Using the event monitor tables, you can investigate any change events that are of interest.
0
0