Readme: IBM® Tivoli® Composite Application Manager Agent for DB2, Version 7.1.6 Interim Fix 4

• Release details
• Release highlights
• Problems fixed
• Architecture and prerequisites
• Image directory contents
• Installation instructions
• Additional installation information
• Known problems and workarounds
• Additional product information
• Download Package

• APAR DT363502: The DB2 agent prints "Not Found" messages in the agent logs. 
  Additional Information: Log file with name hostname_ud_instancename. Logs are flooded with "Not found" messages, filling up the log space and resulting in high disk space usage.
• APAR IJ46391: ITCAM DB2 AGENT 7.16.00 high CPU usage when KUD_DIAGLOG_BY_TABLE is SET TO N. When the DB2 agent is upgraded to 7.1.6-TIV-ITM_DB2-FP0000, CPU usage may be higher than expected if the variable KUD_DIAGLOG_BY_TABLE is set to 'N' in the ud.ini file. The agent log can be flooded with messages like:    

  (6459F286.467E-6: kumprmfr.c,473,"KUMP_ReadMonitorFileUnicodeRecord") ***** File record discarded <2023-05-09-09.11.37.122418+120 I36682714A572 LEVEL: Error 

• Defect 147303: In the v716 agent on RHEL 8.x pLinuxLE platform, when data is collected by parsing the db2diag.log file, then Diagnostic Messages data is NOT displayed on UI.
• Defect 147293: Agent Memory increases rapidly for 6-7 days, after that, it is stable at a very high level (around 350MB). When data is being collected by parsing the db2diag.log file and HDC is enabled for all AGs, set KUD_DIAGLOG_BY_TABLE=N in <candlehome>/config/ud.ini file. It has been observed that in HADR. Primary node v716 Agent Memory is increasing rapidly for 6-7 days, after that it is stable at a very high level (around 350 MB).   

Architecture and prerequisites

• This fix is supported on all operating systems listed in the IBM Tivoli Composite Application Manager Agent for DB2 V7.1.6.
• Refer to the IBM Software Product Compatibility Reports (SPCR) for the latest operating system certification information: https://www.ibm.com/software/reports/compatibility/clarity/index.html.

Prerequisites for this fix

• IBM Tivoli Composite Application Manager Agent for DB2 V7.1.6. https://www.ibm.com/support/pages/node/6619669.

Image directory contents

• 7.1.6-TIV-ITM_DB2-IF0004.README  - This README file
• 7.1.6-TIV-ITM_DB2-IF0004.tar.gz  - Fix archive TAR GZ format
• 7.1.6-TIV-ITM_DB2-IF0004.zip - Fix archive ZIP format

Before installing the fix

• The prerequisites listed in the "Prerequisites for this fix" section must be installed before this fix can be installed.
• For this README, the <CANDLEHOME> symbol is the IBM Tivoli Monitoring installation directory. The default value for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM' on Windows systems.
• If you have customized the Monitoring Agent for the DB2 ud.ini file on a UNIX system, this file should be backed up before the fix install. After this fix is installed, edit the latest ud.ini file, and merge your modifications into this ud.ini file.

Local agent update

1. Transfer the appropriate archive file (7.1.6-TIV-ITM_DB2-IF0004.tar.gz or .zip) to a temporary directory on the system that contains the agent code to be updated. For this README, the <TEMP> symbol represents the fully qualified path to this directory. 
   Note: On Windows systems, this path includes the drive letter.
2. Expand the archive file by using the "tar" command on UNIX systems or an extract utility on Windows systems. Expanding the file creates a directory structure that contains fixes for all the supported operating systems.
3. Use the "itmpatch" command to install the fix for the operating system of that agent. For more information on the "itmpatch" command, see section Additional information on using the "itmpatch" command.      
4. On a UNIX system, if the fix is expanded to <TEMP>/7.1.6-TIV-ITM_DB2-IF0004, use the following installation command:

   > itmpatch -h <CANDLEHOME> -i <TEMP>/7.1.6-TIV-ITM_DB2-IF0004/kud_xxxxxx_tema_if0004.tar

   Where,
   - xxxxxx corresponds to the value in the first column returned by the ./cinfo -i command. 
   In the following example, the file is kud_aix526_tema_if0004.tar. 

   > ./cinfo -i
   Monitoring Agent for DB2 aix526 Version: 07.16.00.04

5. On a Windows system, if the fix was expanded to <TEMP>\7.1.6-TIV-ITM_DB2-IF0004, use the following installation command:

   > itmpatch -h <CANDLEHOME> -i <TEMP>\7.1.6-TIV-ITM_DB2-IF0004\kud_wix64_tema_if0004.cab  

Remote agent update

1. Transfer the appropriate archive file (7.1.6-TIV-ITM_DB2-IF0004.tar.gz or .zip) to a temporary directory on the Tivoli Enterprise Monitoring Server system.  For this README, the <TEMP> symbol represents the fully qualified path to this directory. 
   Note: On Windows systems, this path includes the drive letter.
2. Expand the archive file by using the "tar" command on UNIX systems or an extract utility on Windows systems. Expanding the file creates a directory structure that contains fixes for all the supported operating systems.
3. To add the agent fix bundles into the remote deploy depot, use the "tacmd addBundles" command in $CANDLEHOME/bin on UNIX systems or in %CANDLE_HOME%\bin on Windows systems. For more information about the "tacmd addBundles" command, see the IBM Tivoli Monitoring Command Reference.
4. On UNIX systems, if the fix was expanded to <TEMP>/7.1.6-TIV-ITM_DB2-IF0004,

   > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/7.1.6-TIV-ITM_DB2-IF0004

5. On Windows systems, if the fix was expanded to <TEMP>\7.1.6-TIV-ITM_DB2-IF0004,

   > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\7.1.6-TIV-ITM_DB2-IF0004

   Where,
   -n indicates that prerequisite bundles are not automatically added. The -n parameter must be used because the fix directory does not contain any prerequisites that the fix might require. See Prerequisites for this fix section.
   -i is the directory that contains the deployment bundles to be added to the depot. 
6. 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 about the "tacmd login" and "tacmd updateAgent" commands, see the "IBM Tivoli Monitoring Administrator's Guide".    UNIX

7. > $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser>  -p <password>
   > $CANDLEHOME/bin/tacmd listSystems

   The output shows the list of Managed System Names 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 071600004

   Windows

   > %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password>           
   > %CANDLE_HOME%\bin\tacmd listSystems  

   The output shows the list of Managed System Names 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 071600004 

• The component (-t) for the "tacmd updateAgent" command is specified as two characters (ud), not three characters (kud).
• The node (-n) for the "tacmd updateAgent" command is the managed system name of the operating system (OS) agent to be updated. The target node for a "tacmd updateAgent" command is always an OS agent.      

Agent support update

Additional installation information

Patch upgrade on Windows machine

Additional information on using the "itmpatch" command

The "itmpatch" command has the following syntax:

itmpatch -h <installation home> [OPTIONS]
itmpatch -h <installation home> -t { <patch_file_directory> | <patch_file> }
itmpatch -h <installation home> -i { <patch_file_directory> | <patch_file> }

> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

Verifying the update

> $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password>
> $CANDLEHOME/bin/tacmd listSystems -t UD

> %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password>                          
> %CANDLE_HOME%\bin\tacmd listSystems -t UD

Download package

What is Fix Central?