Contents

3.0 Enhancements

• Added 6.3.0.7-TIV-ITM-SP0012 ITM support for Db2 agent.
• Added the KudGrantPermission script that auto-assigns all the required permissions to Db2 servers, tables, functions, and objects.

• Added currency support for Windows server 2022.
• Added currency support for AIX 7.3.
• Removed SUSE 10 and SUSE 11 support from V716 release onwards.
• Added the KudGrantPermission script that auto-assigns all the required permissions to Db2 servers, tables, functions, and objects.

4.0 Defect Fixes

5.0 Architecture and prerequisites

6.0 Image directory contents

• AUTORUN.INF
• DeployLnk.sh
• [InstallITM]
• [REPORTS]
• install.sh
• [license]
• notices
• silent_install.txt
• [Deploy]
• README.TXT
• [WINDOWS]
• kcirunas.cfg
• non_ibm_license
• silent_config.txt
• [unix]

Note: If you are working in a UNIX environment, use install.sh file to install. If you are working in a Windows environment, you can choose setup.exe in the directory [WINDOWS].

• You can locally install on a system that already hosts a licensed copy of IBM Tivoli Monitoring for Databases.
• You can locally install on a system that does not already host a licensed copy of IBM Tivoli Monitoring for Databases.
• You can populate agents to the depot.
• You can remotely deploy agents to existing or new installations.

• For this readme file, the symbol ‹ CANDLEHOME › is the IBM Tivoli Monitoring installation directory.

• The default value for ‹ CANDLEHOME › is '/opt/IBM/ITM' on Unix or Linux systems.

  The default value for ‹ CANDLEHOME › is 'C:\IBM\ITM' on Windows systems.

• If you customized the Monitoring Agent for Db2 ud.ini file on Unix/Linux system, this file needs be backed up before the fix installation. After this fix is installed, edit the latest ud.ini file and merge your modifications into this ud.ini file.

1. Transfer the appropriate archive file (M076PML.tar.gz or .iso) to a temporary directory on the system that contains the agent code to be updated. For this readme, the symbol <TEMP> represents the fully qualified path to this directory.
    Note: On Windows, the path includes the drive letter. 

2. Expand the archive file by using the tar command on UNIX systems or an unzip utility on Windows systems. It creates a directory structure that contains fixes for all of the supported platforms.

3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.3 Installation and Setup Guide" to install the agent.

4. Use the procedures in the specific Database Monitoring Agent User's Guide to complete the installation and configuration.
 
5. The bit of agent binary after upgrade remains the same as pre-upgrade on x86 and 64bit Windows. It does not support 32bit upgrade to 64bit binary.

Note: Support for 32bit Db2 Agent on Windows is obsoleted.
The installer for current version can only be used to install or upgrade 64bit Windows Db2 Agent.

1. Transfer the appropriate archive file (M076PML.tar.gz or .iso) to a temporary directory on the IBM Tivoli Enterprise Monitoring Server system. In this readme file, the symbol <TEMP> represents the fully qualified path to this directory.
Note: On Windows, the path includes the drive letter. 

2. Expand the archive file by using the tar command on UNIX systems or an unzip utility on Windows systems. It creates a directory structure that contains fixes for all the supported operating systems.

3. To add these bundles into the remote deploy depot, use the tacmd addBundles command found in $CANDLEHOME/bin on UNIX systems or in %CANDLE_HOME%\bin on Windows systems.

For more information on the tacmd addBundles command, see Appendix A. Commands reference of the "IBM Tivoli Monitoring Administrator's Guide."

On a UNIX system: the fix is expanded to <TEMP>/ M076PML:
     > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/M076PML/WINDOWS/Deploy -t ud -f
     > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/M076PML/unix -t ud -f 
     where:
        -i is the directory that contains the deployment bundles to be added to the depot.
        -t is the product code of the product to add, in this case ud represents the Monitoring Agent for Db2
        -f performs the actions without asking for confirmation

 On a Windows system: the fix is expanded to <TEMP>/M076PML:
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\M076PML\WINDOWS\Deploy -t ud -f
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\M076PML\unix -t ud -f 
     where:
        -i is the directory that contains the deployment bundles to be added to the depot. 
        -t is the product code of the product to add, in this case ud represents the Monitoring Agent for Db2
        -f performs the actions without asking for confirmation

4. To log in to the Tivoli Enterprise Monitoring Server and deploy the fix to the appropriate nodes where the agent is running, use the following tacmd commands.

For more information on the tacmd login and updateAgent commands, see Appendix A. Command reference of the "IBM Tivoli Monitoring Administrator's Guide."

On a UNIX system: 
    > $CANDLEHOME/bin/tacmd login -s <server>
                                -u <itmuser> 
                                -p <password>
                                   
    > $CANDLEHOME/bin/tacmd listSystems
    
The output shows the managed system name for the OS agent on the remote system to be updated. Use this value as the target of the tacmd updateAgent command.                                    
                                   
    > $CANDLEHOME/bin/tacmd updateAgent -t ud 
                                      -n <Managed system name>
                                      -v 07160000

On a Windows system:
    > %CANDLE_HOME%\bin\tacmd login -s <server>
                                    -u <itmuser> 
                                    -p <password>

    > %CANDLE_HOME%/bin/tacmd listSystems

The output shows the managed system name for the OS agent on the remote system to be updated. Use this value as the target of the tacmd updateAgent command.   
                                    
    > %CANDLE_HOME%\bin\tacmd updateAgent -t UD 
                                        -n <Managed system name>
                                        -v 07160000
                                          
If there are not prior version kud agent on remote system, then use the following tacmd addSystem command.
    
    > %CANDLE_HOME%\bin\tacmd addSystem -t UD 
                                      -n <Managed system name> 
                                      -p INSTANCE="<Db2 instance name>"                                   
Note:
- The <Db2 instance name> is the Db2 instance name to be monitored on remote system.
- The component (-t) for the updateAgent command is specified as two characters (ud), not three characters (kud).
- The node (-n) for the updateAgent command is the managed system name of the operating system (OS) agent to be updated. The target node for an updateAgent command is always an OS agent.

-The following error might occur when executing the updateAgent command on Linux and UNIX endpoints; however, the agent is successfully updated. This error does not occur on Windows endpoints.

         KUICUA011I: Updating the UD agents.

         KUICUA015E: The updateAgent command did not complete because an error occurred.
         Refer to the following error returned from the server:

         The monitoring server encountered an error while updating the
         managed system type.

         The kuiras1.log file may provide more information about this error. 
         If you require further assistance resolving the error, contact IBM Software
         Support.

         A timeout occurred while waiting for an agent task to complete on
         {node name}.

         The agent task did not complete within the configured time out period.

         Verify that the target system is online. Increase the time out value and try the operation again.

 1. Transfer the appropriate archive file (M076PML.tar.gz or .iso) to the Tivoli Enterprise Monitoring Servers, IBM Tivoli Enterprise Portal Servers or Tivoli Enterprise Portal desktops. 
    
 2. Expand the archive file by using the tar command on UNIX systems or an unzip utility on Windows systems. 
On Unix/Linux systems,
      > tar -xvf M076PML.tar.gz

This step creates a directory structure that contains fixes for all of the supported platforms.

 3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.3 Installation and Setup Guide."

 4. Use the procedures in the specific Database Monitoring Agent User's Guide to complete the installation and configuration.

 5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a Hub Tivoli Enterprise Monitoring Server), then restart the Tivoli Enterprise Monitoring Server.