Walker News

How to remove ITMA Installed By DB2 9.7 On Redhat Enterprise Linux?

Unless sysadmin installs the IBM DB2 9.7 using a response file that set INSTALL_ITMA keyword to NO, you’ll find out that IBM Tivoli Monitoring Agent (ITMA) is automatically included even it’s not needed at all on an optimized production system.

What’s that ITMA?
According to documentation, ITMA is used for supplying monitoring information to the IBM InfoSphere Optim Database Administrator Health and Availability monitoring feature. If you’re not using this feature, chance is you won’t need ITMA. Indeed, ITMA is obsolete and being replaced by the IBM InfoSphere Optim Database Administrator (thus, it’s not installed by default in DB2 9.8 Fix Pack 3 and newer products).

How to uninstall ITMA from RHEL?

Login as db2 instance user:

1. Stop ITMA by executing “DB2_DIR/itma/bin/itmcmd agent -o INST_NM stop ud” where DB2DIR is the DB2 installation directory (usually, this is /opt/ibm/db2/V9.x) and INST_NM is DB2 instance name. For example:
/opt/ibm/db2/V9.7/itma/bin/itmcmd agent -o mydb2inst stop ud

NOTE: If you’ve multiple DB2 instances created on single Linux system, you must stop all of them (i.e. make sure all kuddb2 processes are gone).

Login as root:

2. Uninstall ITMA by executing “DB2DIR/itma/bin/uninstall.sh REMOVE EVERYTHING”, e.g.:
/opt/ibm/db2/V9.7/itma/bin/uninstall.sh REMOVE EVERYTHING

3. Check if the /etc/init.d/ITMAgents1 has removed successfully during ITMA uninstalling process. If it isn’t removed, just delete this file and all of its soft links appear in /etc/rcx.d directory (where x is 0 to 6 that corresponding to Linux runlevel). Alternatively, just simply empty the file, e.g. :>/etc/init.d/ITMAgents1.

If there is no exception observed during the removal process, then you’ve successfully uninstalled ITMA, that “useless” agent in your perspective :).

NOTE: With reference to official guide, the procedure is slightly different if to apply on DB2 9.5.

Custom Search

2014  •  Privacy Policy