\n <\/p>\n

Important Notice:<\/strong> 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.<\/p>\n<\/div>\n

<\/p>\n

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.<\/p>\n

Module data<\/h2>\n

(Information also attached as txt file).<\/p>\n

DB2 process monitoring<\/strong><\/p>\n

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.<\/p>\n

Main processes should monitored:<\/strong><\/p>\n

module_begin\u00a0\r\nmodule_name DB2Sys\u00a0\r\nmodule_type generic_proc\u00a0\r\nmodule_proc db2syscs.exe\u00a0\r\nmodule_description DB2 Primary database engine\u00a0\r\nmodule_end\u00a0\r\n<\/pre>\n
module_begin\u00a0\r\nmodule_name DB2Jds\u00a0\r\nmodule_type generic_proc\u00a0\r\nmodule_proc db2jds.exe\u00a0\r\nmodule_description The DB2 JDBC applet server service\u00a0\r\nmodule_end\u00a0\r\n<\/pre>\n
DB2 Performance counters<\/strong><\/p>\n
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.<\/p>\n
Memory Monitoring<\/strong><\/p>\n
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:<\/p>\n
$ db2mtrk -i -p -w -d -v\u00a0\r\nTracking Memory on: 2002\/12\/03 at 10:03:26\u00a0\r\n<\/pre>\n
Memory for instance<\/strong><\/p>\n
Database Monitor Heap has watermark of 180224 bytes\u00a0\r\nOther Memory has watermark of 5226496 bytes\u00a0\r\nTotal: 5406720 bytes\u00a0\r\n\r\n<\/pre>\n
Memory for database: GDMS0401<\/strong><\/p>\n
Backup\/Restore\/Util Heap has watermark of 16384 bytes\u00a0\r\nPackage Cache has watermark of 327680 bytes\u00a0\r\nCatalog Cache Heap has watermark of 81920 bytes\u00a0\r\nBuffer Pool Heap has watermark of 4341760 bytes\u00a0\r\nBuffer Pool Heap has watermark of 671744 bytes\u00a0\r\nBuffer Pool Heap has watermark of 409600 bytes\u00a0\r\nBuffer Pool Heap has watermark of 278528 bytes\u00a0\r\nBuffer Pool Heap has watermark of 212992 bytes\u00a0\r\nLock Manager Heap has watermark of 458752 bytes\u00a0\r\nDatabase Heap has watermark of 1540096 bytes\u00a0\r\nOther Memory has watermark of 0 bytes\u00a0\r\nTotal: 8339456 bytes\u00a0\r\n<\/pre>\n
Memory for agent 4157<\/strong><\/p>\n
Application Heap has watermark of 212992 bytes\u00a0\r\nApplication Control Heap has watermark of 16384 bytes\u00a0\r\nTotal: 229376 bytes\u00a0\r\n<\/pre>\n
For those that prefer a GUI interface, the DB2 Memory Visualizer provides a way to monitor DB2 memory usage over time.<\/p>\n
Text taken, from Article written by John Maenpaa
\nOriginal URL: http:\/\/www.cmg.org\/measureit\/issues\/mit14\/m_14_2.html<\/a><\/p>\n
Files:<\/h2>\n
db2_windows_monitoring.txt<\/a>[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
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 […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"
\r\n  \r\n  
Important Notice:<\/strong> 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.
\r\n<\/div>\r\n\r\n
\r\n\r\nThis 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.\r\n
Module data<\/h2>\r\n(Information also attached as txt file).\r\n\r\nDB2 process monitoring<\/strong>\r\n\r\nYou 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.\r\n\r\nMain processes should monitored:<\/strong>\r\n
module_begin\u00a0\r\nmodule_name DB2Sys\u00a0\r\nmodule_type generic_proc\u00a0\r\nmodule_proc db2syscs.exe\u00a0\r\nmodule_description DB2 Primary database engine\u00a0\r\nmodule_end\u00a0\r\n<\/pre>\r\n
module_begin\u00a0\r\nmodule_name DB2Jds\u00a0\r\nmodule_type generic_proc\u00a0\r\nmodule_proc db2jds.exe\u00a0\r\nmodule_description The DB2 JDBC applet server service\u00a0\r\nmodule_end\u00a0\r\n<\/pre>\r\nDB2 Performance counters<\/strong>\r\n\r\nDB2 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.\r\n\r\nMemory Monitoring<\/strong>\r\n\r\nThe 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:\r\n
$ db2mtrk -i -p -w -d -v\u00a0\r\nTracking Memory on: 2002\/12\/03 at 10:03:26\u00a0\r\n<\/pre>\r\nMemory for instance<\/strong>\r\n
Database Monitor Heap has watermark of 180224 bytes\u00a0\r\nOther Memory has watermark of 5226496 bytes\u00a0\r\nTotal: 5406720 bytes\u00a0\r\n\r\n<\/pre>\r\nMemory for database: GDMS0401<\/strong>\r\n
Backup\/Restore\/Util Heap has watermark of 16384 bytes\u00a0\r\nPackage Cache has watermark of 327680 bytes\u00a0\r\nCatalog Cache Heap has watermark of 81920 bytes\u00a0\r\nBuffer Pool Heap has watermark of 4341760 bytes\u00a0\r\nBuffer Pool Heap has watermark of 671744 bytes\u00a0\r\nBuffer Pool Heap has watermark of 409600 bytes\u00a0\r\nBuffer Pool Heap has watermark of 278528 bytes\u00a0\r\nBuffer Pool Heap has watermark of 212992 bytes\u00a0\r\nLock Manager Heap has watermark of 458752 bytes\u00a0\r\nDatabase Heap has watermark of 1540096 bytes\u00a0\r\nOther Memory has watermark of 0 bytes\u00a0\r\nTotal: 8339456 bytes\u00a0\r\n<\/pre>\r\nMemory for agent 4157<\/strong>\r\n
Application Heap has watermark of 212992 bytes\u00a0\r\nApplication Control Heap has watermark of 16384 bytes\u00a0\r\nTotal: 229376 bytes\u00a0\r\n<\/pre>\r\nFor those that prefer a GUI interface, the DB2 Memory Visualizer provides a way to monitor DB2 memory usage over time.\r\n\r\nText taken, from Article written by John Maenpaa\r\nOriginal URL: http:\/\/www.cmg.org\/measureit\/issues\/mit14\/m_14_2.html<\/a>\r\n
Files:<\/h2>\r\ndb2_windows_monitoring.txt<\/a>","_et_gb_content_width":"","footnotes":""},"categories":[15],"tags":[401],"_links":{"self":[{"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/posts\/1182"}],"collection":[{"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/comments?post=1182"}],"version-history":[{"count":2,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/posts\/1182\/revisions"}],"predecessor-version":[{"id":8389,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/posts\/1182\/revisions\/8389"}],"wp:attachment":[{"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/media?parent=1182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/categories?post=1182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pandorafms.com\/library\/wp-json\/wp\/v2\/tags?post=1182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}