• Description
• Documentation
  • Commandline parameters
  • Modi
  • Preparation of the database
• Examples
  • Using environment variables
• Installation
• Download
• Changelog
  • Copyright
  • Autor

Description

check_db2_health is a plugin, which is used to monitor various parameters of a DB2 database.

Documentation

Commandline parameters

• –database <DB-Name> The name of the database. (If it was catalogued locally, this parameter is the only you need. Otherwise you must specify database, hostname and port)
• –hostname <hostname> The database server
• –port <port> The port, where DB2 listens
• –username <username> The database user
• –password <password> The database password
• –mode <modus> With the mode parameter you tell the plugin what you want it to do. (See the list of possible values in the table below)
• –name <objektname> You can limit the checks to a specific database object by using the name parameter (e.g. tablespace, buffercache). It is also used for a custom sql statement with –mode sql
• –name2 <string> If you use –mode sql, the statement appears in the output and the performance data. Use –name2 to specify a custom string.
• –warning <range> The warning threshold.
• –critical <range> The critical threshold.
• –environment <variable>=<wert> You can pass environment variables to the plugin by using this parameters. It can be used multiple times.
• –method <connectmethode> This tells the plugin how to connect to the database. The only method implemented yet is “dbi” which is the default. (It means, the plugin uses the perl module DBD::DB2).

• *–units <%

  KB

  MB

  GB>* When using –mode sql you can specify a unit which will appear in the output and the performance data.

Using the –mode parameter with the following arguments tells the plugin what it should monitor.

Modi

Thresholds are set according to the plugin developer guidelines +
“10” means “Alert, if > 10” and +
“90:” means “Alert, if < 90” +

Preparation of the database

In order for the plugin to retrieve the necessary information from the database, a (OS-)user “nagios” (with group nagios) is needed. Maybe it already exists because the database server is monitored with check_nrpe or check_by_ssh.

The Monitoring Switches need to be set:

update dbm cfg using dft_mon_bufpool on
update dbm cfg using dft_mon_lock on
update dbm cfg using dft_mon_timestamp on

The nagios-user (to be exact: the nagios-group. Be careful, the usr nagios has to belong to a group nagios. The nagios in the following sql-statement is the group, not the user) gets the necessary privileges:

db2inst1$ db2 update dbm cfg using sysmon_group nagios
db2inst1$ db2 grant select,update on table SYSTOOLS.STMG_DBSIZE_INFO to nagios
db2inst1$ db2stop; db2start

For version 10.5 (Caution, 10.x is not officially supported. You have to pay for the implementation) you also need the following command:

db2inst1$ db2 grant execute on function sysproc.MON_GET_DATABASE to nagios

Examples

nagsrv$ check_db2_health --mode connection-time
WARNING - 1.61 seconds to connect as DB2INST1 |  connection_time=1.6084;1;5

nagsrv$ check_db2_health --mode connected-users
OK - 3 connected users |  connected_users=3;50;100

nagsrv$ check_db2_health --mode list-databases
TOOLSDB
OK - have fun

nagsrv$ check_db2_health --mode database-usage
OK - database usage is 31.29% |  'db_toolsdb_usage'=31.29%;80;90

nagsrv$ check_db2_health --mode tablespace-usage
CRITICAL - tbs TEMPSPACE1 usage is 100.00%, tbs TBSP32KTMP0000 usage is 100.00%, tbs TBSP32K0000 usage is 100.00%, tbs USERSPACE1 usage is 5.08%, tbs SYSTOOLSPACE usage is 1.86%, tbs SYSCATSPACE usage is 80.37% |  'tbs_userspace1_usage_pct'=5.08%;90;98 'tbs_userspace1_usage'=16MB;288;313;0;320 'tbs_tempspace1_usage_pct'=100.00%;90;98 'tbs_tempspace1_usage'=0MB;0;0;0;0 'tbs_tbsp32ktmp0000_usage_pct'=100.00%;90;98 'tbs_tbsp32ktmp0000_usage'=0MB;0;0;0;0 'tbs_tbsp32k0000_usage_pct'=100.00%;90;98 'tbs_tbsp32k0000_usage'=61MB;55;60;0;61 'tbs_systoolspace_usage_pct'=1.86%;90;98 'tbs_systoolspace_usage'=0MB;28;31;0;32 'tbs_syscatspace_usage_pct'=80.37%;90;98 'tbs_syscatspace_usage'=51MB;57;62;0;64

nagsrv$ check_db2_health --mode list-tablespaces
SYSCATSPACE
SYSTOOLSPACE
TBSP32K0000
TBSP32KTMP0000
TEMPSPACE1
USERSPACE1
OK - have fun

nagsrv$ check_db2_health --mode tablespace-usage --name SYSCATSPACE
OK - tbs SYSCATSPACE usage is 80.37% |  'tbs_syscatspace_usage_pct'=80.37%;90;98 'tbs_syscatspace_usage'=51MB;57;62;0;64

nagsrv$ check_db2_health --mode tablespace-free --name SYSCATSPACE
OK - tbs SYSCATSPACE has 19.63% free space left |  'tbs_syscatspace_free_pct'=19.63%;5:;2: 'tbs_syscatspace_free'=12MB;3.20:;1.28:;0;64.00

nagsrv$ check_db2_health --mode tablespace-free --name SYSCATSPACE --units MB
OK - tbs SYSCATSPACE has 12.55MB free space left |  'tbs_syscatspace_free_pct'=19.63%;7.81:;3.12: 'tbs_syscatspace_free'=12.55MB;5.00:;2.00:;0;64.00

nagsrv$ check_db2_health --mode tablespace-free --name SYSCATSPACE --units MB --warning 15: --critical 10:
WARNING - tbs SYSCATSPACE has 12.55MB free space left |  'tbs_syscatspace_free_pct'=19.63%;23.44:;15.62: 'tbs_syscatspace_free'=12.55MB;15.00:;10.00:;0;64.00

nagsrv$ check_db2_health --mode bufferpool-hitratio
CRITICAL - bufferpool IBMDEFAULTBP hitratio is 53.60%, bufferpool BP32K0000 hitratio is 100.00% |  'bp_ibmdefaultbp_hitratio'=53.60%;98:;90: 'bp_ibmdefaultbp_hitratio_now'=100.00% 'bp_bp32k0000_hitratio'=100.00%;98:;90: 'bp_bp32k0000_hitratio_now'=100.00%

nagsrv$ check_db2_health --mode list-bufferpools
BP32K0000
IBMDEFAULTBP
OK - have fun

nagsrv$ check_db2_health --mode bufferpool-hitratio --name IBMDEFAULTBP
CRITICAL - bufferpool IBMDEFAULTBP hitratio is 53.60% |  'bp_ibmdefaultbp_hitratio'=53.60%;98:;90: 'bp_ibmdefaultbp_hitratio_now'=100.00%

nagsrv$ check_db2_health --mode bufferpool-data-hitratio --name IBMDEFAULTBP
CRITICAL - bufferpool IBMDEFAULTBP data page hitratio is 64.35% |  'bp_ibmdefaultbp_hitratio'=64.35%;98:;90: 'bp_ibmdefaultbp_hitratio_now'=100.00%

nagsrv$ check_db2_health --mode bufferpool-index-hitratio --name IBMDEFAULTBP
CRITICAL - bufferpool IBMDEFAULTBP index hitratio is 38.89% |  'bp_ibmdefaultbp_hitratio'=38.89%;98:;90: 'bp_ibmdefaultbp_hitratio_now'=100.00%

nagsrv$ check_db2_health --mode index-usage
CRITICAL - index usage is 0.71% |  index_usage=0.71%;98:;90:

nagsrv$ check_db2_health --mode synchronous-read-percentage
OK - synchronous read percentage is 100.00% |  srp=100.00%;90:;80:

nagsrv$ check_db2_health --mode asynchronous-write-percentage
CRITICAL - asynchronous write percentage is 0.00% |  awp=0.00%;90:;80:
nagsrv$ check_db2_health --mode deadlocks
OK - 0.000000 deadlocs / sec |  deadlocks_per_sec=0.000000;0;1

nagsrv$ check_db2_health --mode lock-waits
OK - 0.000000 lock waits / sec |  lock_waits_per_sec=0.000000;10;100

nagsrv$ check_db2_health --mode lock-waiting
OK - 0.000000% of the time was spent waiting for locks |  lock_percent_waiting=0.000000%;2;5

Using environment variables

The parameters –hostname, –username, –password and –port can be omitted, if the corresponding data are available via environment variables. Since version 3.x of nagios, service definitions can have custom attributes, which can be used to specify login data. During the plugin execution they are available as environment variables .

Die Environmentvariablen heissen:

• NAGIOS__SERVICEDB2_HOST (_db2_host in the service definition)
• NAGIOS__SERVICEDB2_USER (_db2_user in the service definition)
• NAGIOS__SERVICEDB2_PASS (_db2_pass in the service definition)
• NAGIOS__SERVICEDB2_PORT (_db2_port in the service definition)
• NAGIOS__SERVICEDB2_DATABASE (_db2_database in the service definition)

Installation

This plugin requires the installation of the Perl-Module DBD::DB2 .

After unpacking the tar archive you have to run ./configure. With ./configure –help you get the list of possible options.

• –prefix=BASEDIRECTORY The base directory of the Nagios installation (default: /usr/local/nagios). The final destination for check_db2_health will be the libexec subdirectory.
• –with-nagios-user=SOMEUSER The owner of check_db2_health. (default: nagios)
• –with-nagios-group=SOMEGROUP The group of check_db2_health. (default: nagios)
• –with-perl=PATHTOPERL A non-standard perl interpreter. (default: perl found in PATH)

Download

check_db2_health-1.1.3.tar.gz

Changelog

• 1.1.3 - 2021-07-09
  add –nosms
• 1.1.2.2 - 2018-03-29
  fix a bug in database-usage where sysdummy1 returns an empty result
• 1.1.2.1 - 2018-03-26
  add
  –nutzediedrecksalteversionwegengroberunfaehigkeitderadministratorenaffen
  and
  –nddavwgudaa
• 1.1.2 - 2018-03-11
  enhance database-usage, don’t use SYSTOOLS.STMG_DBSIZE_INFO
• 1.1.1.4 - 2017-10-25
  use sysibmadm.applications for connected-users also for newer db2 versions
• 1.1.1.3 - 2017-10-14
  catch sql errors and return them as unknown
• 1.1.1.2 - 2016-08-19
  bugfix in last-backup (Thanks Volker Maibaum)
• 1.1.1.1 - 2015-09-09
  bugfix in bufferpool (perl-error)
• 1.1.1 -2015-08-10
  fix bufferpool-modes for 10.x (Thanks Phlippe)
• 1.1 - 2015-04-23
  add rfc3986-encoded passwords
• 1.0.9.2 - 2014-08-21
  fix mode last-backup again
  report sql/permission-errors
• 1.0.9.1 - 2014-08-19
  fix mode last-backup
• 1.0.9 - 2014-08-18
  fix mode last-backup for 10.x
• 1.0.8 - 2014-07-07
  fix mode dms-tablespace-settings
  add mode application-usage
• 1.0.7 - 2014-04-14
  add mode dms-tablespace-usage/free which checks only non-automatic dms
  tablespaces
  add mode dms-tablespace-settings which checks automatic dms tablespaces’
  auto/increase settings
  bugfix in connected-users, db2-internal users are not counted any more
• 1.0.6.3 - 2014-04-01
  implement –negate old_level=new_level
  output also ok-messages for my-modes
• 1.0.6.2 - 2014-03-26
  fix perfdata in bufferpool-usage&lookback
  thresholds can now be floating point numbers
• 1.0.6.1 - 2013-01-01
  fix for newer perl versions
• 1.0.6 - 2012-11-29
  implemented all sorts of thresholds
  add mode sql-runtime
• 1.0.5.3 - 2012-11-29
  fixed a bug in tablespace-usage/free (null-values in fs_total_size_kb/fs_used_size_kb of sms tbsp_type mean: unused)
• 1.0.5.2 - 2012-05-16
  connected-users no longer counts internal db2 processes (appl_name like db2fw%)
• 1.0.5.1 - 2012-02-28
  exceptions in mode duplicate-packages are possible (–name=’^(?!(DUPPATTERN$)|(DUPPATTERN2$))’ –regexp)
• 1.0.5 - 2012-02-23
  add capture-latency, subscription-set-latency
  add invalid-objects
  add duplicate-packages
  bugfix in timeout-alarm handling under windows
• 1.0.4 - 2011-09-29
  fix a bug in save_state with capital letters in statefilesdir
  single ticks around the –name argument under Windows CMD will be removed automatically
  1.0.3.3 - 2011-07-01
  change stale-table-runstats so there are less unnecessary alerts (Thanks Niko v. Koeckritz)
• 1.0.3.2 - 2011-06-03
  sites in an OMD (http://omdistro.org) environment have now private statefile directories
• 1.0.3.1 - 2011-01-03
  bugfix in –mode sql (numeric vs. regexp result)
• 1.0.3 - 2010-12-20
  fixed a bug in connected-users. Thanks Alexander Titze
  mode sql can now have a non-numerical output which is compared to a string/regexp
  new parameter –dbthresholds
  new mode report can be used to output only the bad news (short,long,html)
• 1.0.2 - 2010-09-29
  bufferpool-hitratio now uses hitratio_now to calculate the exitcode when –lookback is used.
  add mode last-backup
  add mode sort-overflows
  add mode sort-overflow-percentage (Thanks Birger Schmidt, Niko v. Koeckritz)
  index-usage takes delete- and insert-statements into account
• 1.0.1 - 2010-06-10
  bugfix for connected-users (only status CONNECTED was counted, but there are more). Thanks Niko
  update in the README file. You need to grant select/update on SYSTOOLS.STMG_DBSIZE_INFO. Thanks Niko
• 1.0 - 2009-04-20

Copyright

Gerhard Lausser
Check_db2_health is released under the GNU General Public License.http://www.gnu.de/documents/gpl.en.html[GPL]

Autor

Gerhard Laußer (mailto:gerhard.lausser@consol.de[gerhard.lausser@consol.de]) will gladly answer your questions.