DB2 misconfigurations can lead to process leaks & exceptions in SRM logs

Content

You need to make sure your DB2 is configured correctly to avoid both of these issues. We recommend configuring these DB2 settings whether you hit this problem or not.

1) Since these parameters are specific to a DB2 instance, you need to set your instance first. It is critical you set this for the correct instance. Make sure you know your instance instead of just assuming it is the same as this example. For example, on Windows:
set DB2INSTANCE=CTGINST1

2) To resolve MON_HEAP_SZ exception, set the MON_HEAP_SZ DB2 dbm variable to AUTOMATIC on the CTGINST1 instance. Run these commands from the DB2 command prompt opened in step 1:
get dbm cfg (to see the current settings)
If using DB2 9.5 or later using this command:
update dbm cfg using MON_HEAP_SZ AUTOMATIC
If using earlier versions of DB2, then use this command:
update dbm cfg using MON_HEAP_SZ <largest value your DBA will allow>

3) To resolve the db2fmp.exe process leak, set the KEEPFENCED db2 dbm variable to NO. Run this command from the DB2 command prompt opened in step 1:
update dbm cfg using KEEPFENCED NO