To enhance the performance and increase the system throughput, you should configure Monitor database as well as the DB2 Instance hosting it by adjusting the following configuration settings with the following values, and then restart the DB2 instance:
Run the following database commands from the command line to set the following instance parameters:
db2set DB2_RR_TO_RS=YES
db2set DB2_HASH_JOIN=Y
db2set DB2_EXTENDED_OPTIMIZATION=ON
Adjust the following Database configuration parameters with the following values:
Parameter Name |
DB2 Parameter Name |
Parameter Location |
Value |
Maximum Storage for Lock list |
LOCKLIST |
Performance Tab/Section |
50000 |
Application Heap Size |
APPLHEAPSZ |
Performance Tab/Section |
4096 |
Application Control Heap Size |
APP_CTL_HEAP_SZ |
Performance Tab/Section |
4096 |
Maximum Lock per application |
MAXLOCKS |
Application Tab/Section |
50 |
Lock timeout |
LOCKTIMEOUT |
Application Tab/Section |
60 |
Group commit count |
MINCOMMIT |
Logs Tab/Section |
3 |
Increasing the minimum commit count requires increasing the size of the transaction log to hold the transactions in the memory.
In order for the above parameters to take effect, you must bounce the DB2 instance for the instance parameters and restart WebSphere Application Server for the database parameters.