How do I manually install an IBM Tivoli Systems Automation for Multiplaforms (Tivoli SA MP) fix pack on an IBM Smart Analytics System or on a Balanced Warehouse system?
If your system is installed with the IBM Smart Analytics System Control Console software, use an IBM Smart Analytics System fix pack available on Fix Central to update your software stack. If the Tivoli SA MP fix pack you need is not available in an IBM Smart Analytics System fix pack or your system does not have the control console software installed, use the instructions in this document to manually install a Tivoli SA MP fix pack on your IBM Smart Analytics System.
Before you begin
This document uses the following variables. Substitute the appropriate values for your environment.
|Variable name||Example name to use||Notes|
|MGMT, ADMIN, ADMIN_ALL, DATA, STANDBY||These variables refer to the role of the different servers. Replace each variable with the appropriate host names from your environment.
|new_path_to_fix_pack||TSAMP_220.127.116.11||Use a name that clearly labels the directory with the product, version, and build number (if you are applying a special build). If you need to install the product in the future, this naming convention will allow you to easily identify the product and correct version to install.|
Note: You can use any utility you prefer to issue remote commands to the servers in the cluster. If you choose not to use a remote command utility, you can log on to each server and run the commands locally.
1. Mount the installation media directory from the management node
a. If the installation media directory is not already mounted from the management node, mount it using the command that is appropriate for your system.
- For IBM Smart Analytics System 7600 or 7700, Balanced Warehouse E7100, or IBM Smart Analytics System 5600 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes:
- For Balanced Warehouse D5000 or D5100 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes:
Note: In newer configurations, the /BCU_share directory has replaced the /csminstall directory. If you mounted the /csminstall directory, substitute /csminstall for /BCU_share as you follow the instructions in this document. Alternatively, you can create a symbolic link.
b. For D5000 and D5100 environments only, you can optionally create a symbolic link. Issue the following command as root on MGMT, ADMIN_ALL, DATA, and STANDBY nodes:
ln -s /csminstall /BCU_share
2. Download the necessary files
a. Download the appropriate version of the installation media. If you are installing a generally available Tivoli SA MP fix pack, you can download the fix pack from the following URL:
For example, the activation zip file for IBM DB2 Enterprise Server Edition V9.5 is called “DB2_ESE_Auth_User_Activation_V95.zip”.
The activation zip file contains the “samXX.lic” files in the subdirectory "../ese_u/db2/license/".
- For v3.2.x.x, the license file is called “sam32.lic”
- For v3.1.x.x, the license file is called “sam31.lic”
- uncompress <filename> or gunzip <filename>
- tar xvf <filename>.tar
- On AIX 6.1, Tivoli SA MP v3.1 Fixpack 8, the subdirectory is called, "SAM3108MPAIX".
Note: Tivoli SA MP v3.1 Fixpack 8 is shown as 18.104.22.168 using the lslpp command.
- On Linux, Tivoli SA MP v3.1 Fixpack 8, the subdirectory is called, "SAM3108MPLinux".
- Copy the license file into the /<new_path_to_fix_pack>/<SAM<version>MP<OS>/license directory. If you're using Tivoli SA MP v3.1.x.x, copy “sam31.lic” into the “license” subdirectory of the extracted v22.214.171.124 fix pack install media:
i. Extract the files you downloaded. Run the following commands on the MGMT node:
3. Take a backup
Verify that you have a good backup image of the operating system using your normal backup procedures.
4. Copy the contents of the SApolicy directory
You must copy the SApolicy scripts before applying a fix pack or a special build. When you install the Tivoli SA MP fix pack, you also install updates to the Reliable Scalable Cluster Technology (RSCT) software . It is prudent to save the SApolicy scripts so that you can restore the original SApolicy scripts after you install the fix pack in step 7. The SApolicy scripts are the same on the ADMIN_ALL, DATA, and STANDBY nodes.
To copy the files on the administration node to a backup archive, perform the following steps:
a. Log in as root on the ADMIN node.
tar cvf /
5. Stop the resources
a. As root on the
ADMIN node, run the following command:
- On AIX, run this command only if the system is a 7600. It is not necessary to unmount this shared file system on a 7700 system.
mmumount all –a
- On Linux, run the following command:
b. Verify that the database partition resources are offline using the "hals" command or the "lssam" command. Note: It might take a few minutes before the resources are stopped.
d. Verify that the database partition resources and the NFS file system resources are offline using the "hals" command or the "lssam" command. Note: It may take a few minutes to stop the resources. If necessary, use the command "fuser -k /db2home" to disconnect users that are accessing the shared file system.
6. Disable critical resource monitoring and stop the peer domain
Disable the RSCT software to prevent an automated reboot from occurring.
a. Change the critical resource protection method so that the RSCT software will not reboot a node if a communication issue affects the cluster. Issue the following command as root on the ADMIN node:
chrsrc -c IBM.PeerNode CritRsrcProtMethod=5
b. Verify the that the critical resource protection method has changed:
lsrsrc -c IBM.PeerNode CritRsrcProtMethod
c. Stop the domain using the following command:
If the domain does not stop, you can force it offline by running the "stoprpdomain -f bcudomain" command.
d. Verify that the domain is offline:
e. Verify that each node in the domain is offline:
f. Wait until the operational state of the domain (OpState) displays a status of "Offline" in the lsrpdomain command output and the lsrpnode command output before you proceed to the next step.
7. Install the Tivoli SA MP fix pack
Installing the fix pack updates both the RSCT software and the Tivoli SA MP software. You must migrate each component to complete the installation.
a. Log in as root on
b. Set the CT_MANAGEMENT_SCOPE environment variable to the value "2" by running the following command:
c. Install the fix pack on ADMIN_ALL, DATA, and STANDBY nodes by issuing the following command on each ADMIN_ALL, DATA, and STANDBY node:
8. Restore the SApolicy scripts
After you install the fix pack, replace the scripts in /usr/sbin/rsct/sapolicies/DB2/ with the SApolicy scripts you copied in step 4.
a. Log in as the root user on the
b. Change to the following directory:
c. Extract the tar file you created in step 4c:
tar xvf /BCU_share/sapolicies.save.tar
9. Start the domain
a. Start the domain by running the following command:
- Sample output for the lsrpdomain command:
Name OpState RSCTActiveVersion MixedVersions TSPort GSPort
bcudom Online 126.96.36.199 Yes 12347 12348
- Sample out for the lsrpnode command:
Name OpState RSCTVersion
node01 Online 188.8.131.52
node02 Online 184.108.40.206
node03 Online 220.127.116.11
- No red is displayed
- All "Pending" states are cleared
- All "Failed offline" states are cleared
- All nominal states are "Offline"
- There are no "Sacrificed" states
- There are no "Unknown" states
- To reset all resources using the HA Management Toolkit, issue the following command:
This command will take all resources offline and then attempt to reset the resources. If you specify the command with the "nooffline" argument, it will not take the resources offline before attempting to reset them.
- To reset a resource using the resetrsrc command:
resetrsrc –s 'Name = "ResourceName"' ResourceClass
b. Issue the lsrpdomain command and the lsrpnode command to verify that all nodes that have restarted in the domain are online
The MixedVersions value should be "Yes". If the MixedVersions value is not "Yes", wait a few minutes and rerun the lsrpdomain command until the MixedVersions value is "Yes".
c. Run the lssam command and verify that the following checkpoint conditions are satisfied in the lssam output.
All resource groups contain the following:
Use the following sample command as a model:
resetrsrc -s "Name = 'db2mnt-db2path_bcuaix_NODE0004-rs'" IBM.Application
a. Login as root on the
b. Set your environment by running the following command:
c. Complete the migration for RSCT:
runact -c IBM.PeerDomain CompleteMigration Options=0
Verify that you receive the following success message before proceeding:
"Resource Class Action Response for CompleteMigration"
d. Verify the migration is complete and that the MixedVersions value is "No":
e. Complete the migration for Tivoli SA MP:
At the prompt to continue, enter "Y".
f. Verify that the Tivoli SA MP update completed successfully.
Check that the Active Version Number (AVN) matches the Installed Version Number (IVN) for Tivoli SA MP by running the following command:
lssrc –ls IBM.RecoveryRM |grep VN
11. Enable the critical resource protection and high availability
a. Change the critical resource protection method to the default value. Issue the following command as root on the
chrsrc -c IBM.PeerNode CritRsrcProtMethod=1
b. To verify the change completed successfully:
lsrsrc -c IBM.PeerNode CritRsrcProtMethod
a. Stop the domain using step 6c to step 6f.
b. Backup the resource model. As root on each ADMIN_ALL, DATA, and STANDBY node, issue the following command:
Note: You must specify the full path to the command.
ls -l /var | grep ct.backup
d. Start the domain using the commands in step 9.
13. Start the resources
a. Mount the shared /db2home file system.
- On AIX, as root on the ADMIN node, issue the following command:
mmmount all –a
- On Linux, issue the following command as root on each node:
b. On Linux, verify that the NFS resources are online by running either the hals command or the lssam command.
c. Start the database partition resources. Issue the following command as root on the ADMIN node:
d. Verify that the database partition resources are online. Note: It might take a few minutes for the resources to come online.
Run either the hals command or the lssam command to verify the status of the resources.
|Information Management||InfoSphere Balanced Warehouse||Balanced Warehouse||AIX, Linux||9.5, 9.1, 9.7|
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.