IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with monitoring components in a System Automation for Multiplatforms environment > Set up a cluster for Tivoli Monitoring > Predefined Tivoli System Automation for Multiplatforms Cluster for Tivoli Monitoring > Building a Tivoli System Automation for Multiplatforms Cluster for the portal server and Tivoli Data Warehouse components
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Install/Configuring DB2
Use the DB2 Enterprise Server Edition.
If you are running Linux on zSeries , install the 31-bit version of DB2 (regardless of whether you are running in 31-bit or 64-bit mode).
Procedure
- Install DB2 locally on each cluster node into the same directory.
This step ensures that the start, stop, and control scripts for the cluster work without modifications.
- Make sure that you create the DB2 user IDs with the same GUUID and UUID on each node.
- During the installation, create the same instance on both nodes.
- Switch off the automatic startup of DB2 after the installation on each node:
Switch to the instance owner user: su – <instance_owner>, and run:
db2iauto –off <instance>
- Because Warehouse Proxy Agent and Summarization and Pruning Agent use JDBC on UNIX and Linux, the TCP/IP listener for DB2 has to be configured correctly on both nodes.
To do so, runs for the appropriate instance:
db2set -i instance_name DB2COMM=tcpip
db2 update dbm cfg using SVCENAME port_number
db2stop
db2start
- Change back to root.
- Edit the /etc/inittab file on both nodes and comment out the following line:
fmc:2345:respawn:/opt/IBM/db2/V9.1/bin/db2fmcd #DB2 Fault Monitor Coordinator
- Stop DB2 on each node. To do so, switch to the user ID of the instance owner and run the command: db2stop
Parent topic:
Building a Tivoli System Automation for Multiplatforms Cluster for the portal server and Tivoli Data Warehouse components