How could I completely disable STMM log messages

Problem(Abstract)

After disabling Self Tuning Memory (ie. SELF_TUNING_MEM =OFF in DB CFG), the STMM log file is still updated with messages every 3 minutes.

Symptom

Note from DB CFG that STMM is disabled:

$ db2 get db cfg |grep -i self_tuning_mem
Self tuning memory                    (SELF_TUNING_MEM) = OFF

From stmm.log file we can see events like the following still being dumped:

2013-05-24-09.34.38.373583-180 I195993E593         LEVEL: Event
PID     : 2961                 TID  : 139972652820224PROC : db2sysc 0
INSTANCE: db2inst2             NODE : 000          DB   : INTERSEC
APPHDL  : 0-8                  APPID: *LOCAL.DB2.130524032237
AUTHID  : DB2INST2
EDUID   : 25                   EDUNAME: db2stmm (INTERSEC) 0
FUNCTION: DB2 UDB, Self tuning memory manager, stmmMemoryTunerMain, probe:0
MESSAGE : ZRC=0x0000067F=1663
DATA #1 : String, 115 bytes
Going to sleep for 180000 milliseconds.
Interval = 185, State = 1, intervalsBeforeStateChange = 10, lost4KPages = 0

2013-05-24-09.37.38.365898-180 I196587E454         LEVEL: Event
PID     : 2961                 TID  : 139972652820224PROC : db2sysc 0
INSTANCE: db2inst2             NODE : 000          DB   : INTERSEC
APPHDL  : 0-8                  APPID: *LOCAL.DB2.130524032237
AUTHID  : DB2INST2
EDUID   : 25                   EDUNAME: db2stmm (INTERSEC) 0
FUNCTION: DB2 UDB, Self tuning memory manager, stmmMemoryTunerMain, probe:1528
MESSAGE : Starting New Interval

Cause

Turning OFF STMM via DB CFG parameter disables STMM feature, however it does not disable STMM logging.

Diagnosing the problem

Check whether SELF_TUNING_MEM parameter is disabled or not into DB CFG configuration.

db2 get db cfg |grep -i self_tuning_mem

SELF_TUNING_MEM parameter must be set to OFF like below:

Self tuning memory                    (SELF_TUNING_MEM) = OFF

Check the last events from stmm.log file in order to confirm that it is still being updated.

Resolving the problem

In order to completely disable STMM set the following DB2 registry variable as follows:

db2set DB2STMM=OFF

Run db2stop / db2start 

The stmm.log file will not have further updates with new messages.

http://www-01.ibm.com/support/docview.wss?uid=swg21640056