(No Ratings Yet)
Loading...Update in: 5 March 2024
Important Notice: This plugin is no longer actively maintained or updated. We strongly advise you to explore alternative plugins available in our library for the latest features and support.
This is a brief article on how to monitor a DB2 server in Windows plattform. Could be used also on how to monitor DB2 on Unix because has some of the same parameters/commands/processes.
Module data
(Information also attached as txt file).
DB2 process monitoring
You should see several DB2 processes in the Task Manager window, including db2sec.exe, db2rcmd.exe, db2licd.exe, db2jds.exe, and db2syscs.exe. Most of these processes correspond to services available in the Services management console. The db2syscs.exe process is the primary database engine and db2syscs.exe processes are the DB2 agent processes. If agents are the primary resource users here, then the problem may be in the application SQL statements or in the database configuration. High resource usage in the other DB2 processes would likely indicate a problem in the database configuration.
Main processes should monitored:
module_begin module_name DB2Sys module_type generic_proc module_proc db2syscs.exe module_description DB2 Primary database engine module_end
module_begin module_name DB2Jds module_type generic_proc module_proc db2jds.exe module_description The DB2 JDBC applet server service module_end
DB2 Performance counters
DB2 makes its performance information available to the Performance Monitor tool. From the tool you can collect information on the DB2 Database Manager, DB2 Databases and DB2 Applications.
Memory Monitoring
The db2mtrk command is the DB2 tool used to display information on the memory usage of agents and memory pools owned by a DB2 instance. This command is available on both Windows and UNIX-like platforms. Scripts that use this to collect information may provide a historical view of memory activity. UNIX-style scripts could even run on Windows if you use Cygwin. Here is a sample of the output from the db2mtrk command:
$ db2mtrk -i -p -w -d -v Tracking Memory on: 2002/12/03 at 10:03:26
Memory for instance
Database Monitor Heap has watermark of 180224 bytes Other Memory has watermark of 5226496 bytes Total: 5406720 bytes
Memory for database: GDMS0401
Backup/Restore/Util Heap has watermark of 16384 bytes Package Cache has watermark of 327680 bytes Catalog Cache Heap has watermark of 81920 bytes Buffer Pool Heap has watermark of 4341760 bytes Buffer Pool Heap has watermark of 671744 bytes Buffer Pool Heap has watermark of 409600 bytes Buffer Pool Heap has watermark of 278528 bytes Buffer Pool Heap has watermark of 212992 bytes Lock Manager Heap has watermark of 458752 bytes Database Heap has watermark of 1540096 bytes Other Memory has watermark of 0 bytes Total: 8339456 bytes
Memory for agent 4157
Application Heap has watermark of 212992 bytes Application Control Heap has watermark of 16384 bytes Total: 229376 bytes
For those that prefer a GUI interface, the DB2 Memory Visualizer provides a way to monitor DB2 memory usage over time.
Text taken, from Article written by John Maenpaa
Original URL: http://www.cmg.org/measureit/issues/mit14/m_14_2.html