Readme for 7.1.4-TIV-ITM_DB2-FP0000

Component: IBM(R) Tivoli(R) Composite Application Manager for Applications V7.2.1.2: Tivoli(R) Composite Application Manager Agent for DB2 07.14.00.00

Component ID:

5724B96DO

Publication Date: 30 June 2021

Last modified date: 19 December 2023

Contents:

 

1.0 General description

==================
This fix provides the enhancements that are listed in the "Problems Fixed" section. 
This fix also includes the superseded fixes listed in section 3.3.

2.0 Download Package

 

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

            

3.0 Problems fixed

===============
  3.1 Enhancements and Fixes:
  ---------------------------------
  3.1.1 Currency support for new versions of OS platforms
  -----------------------------------------------------------------

   - Revamped the regular expression evaluation for existing platforms for better precision in OS detection.

                

  ----------------------------------

  APARs:

  -------

   - APAR: IJ32200

       Abstract: Db2 agent cause false alert for user-defined situation defined on KUD_Customized_SQL_Detail.String_Value_1 attribute
       144373: Fix false alert for a situation running vs CUSTOM SQL DB2 agent query

       Additional information: Due to the data being sent to the framework function in a non-conforming format for the attribute KUD_Customised_SQL_Detail.String_Value_1 after situation evaluation, false alert was getting raised. It was fixed by adhering the expected format.

  Defects:

  --------

   - Defect 144260:

      Abstract: Fix crash issue in PPCLE environment and change process exit flow

   - Defect 144403:

      Abstract: DB2 agent prerequisite failed on Suse15 zLinux environment for v713 release

   - Improved tooltip description at several places.
       

   - Defect 144610:

      Abstract: Tooltip help for Peer Wait Limit cannot show

   

   - Defect 144535:

     Abstract: Memory-Related attribute values are confusing, in System resource attribute group

   

   - Defect 144532:

     Abstract: Incorrect Listener port attribute value Displaying For network info attribute group on windows server 2019

       

   - Defect 144413:

     Abstract: "HADR Log Gap" and "Peer Wait Limit" attributes the tooltips must be updated as value is displayed in kilobytes and Seconds respectively. There are no units present in tooltip.

  - Defect 144585:

    Abstract: Remove-32 bit Windows Support from Db2 Agent

  3.2 Superseded fixes:
  ------------------------
  

  7.1.3-TIV-ITM_DB2-FP0000

 
  
  3.3 APARs and defects included from superseded fixes:
  ---------------------------------------------------------------

   7.1.3-TIV-ITM_DB2-FP0000

    For details of this release, follow the link:

    https://www.ibm.com/support/pages/node/6243016
  

 

4.0 Architecture and prerequisites

===========================
 The following link is the Tivoli operating system and application support matrix. Refer to this matrix for the latest certification information.
 https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html

 4.1 Prerequisites for this fix
 --------------------------------
  None

    

5.0 Image directory contents

======================
Electronic Part Number: ITCAM Apps Agent for Db2 G01FXML

This fix image contains the following files and directories:

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 under directory [WINDOWS].

6.0 Installation instructions 

======================

When this image file is downloaded from the IBM Software Support website or from Passport Advantage, these rules apply:

 6.1 Before installing the fix
 -------------------------------
  - The prerequisites listed under section 4.1 entitled "Prerequisites for this fix" must be installed.

  - For this README, the symbol <CANDLEHOME> is the 
    IBM Tivoli Monitoring installation directory. The default value for CANDLEHOME is '/opt/IBM/ITM' on Unix or Linux systems and 'C:\IBM\ITM' on Windows systems.
    
  - If you have customized the Monitoring Agent for Db2 ud.ini file on Unix/Linux system, this file should 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.

 6.2 Local agent install and update (including silent installation)
 -------------------------------------------------------------------------
 1. Transfer the appropriate archive file (G01FXML.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, this includes the drive letter.  

 2. Expand the archive file using the tar command on UNIX systems or an unzip utility on Windows systems. This 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 should be the same as pre-upgrade on x86 and 64-bit Windows. Does not support 32-bit upgrade to 64bit binary.
     Note: Support for 32-bit Db2 Agent on Windows has been removed.
     The installer for this version can only be used to install / upgrade 32 bit Windows Db2 Agent.

 6.3 Remote agent update
 -----------------------------
 1. Transfer the appropriate archive file (G01FXML.tar.gz or .iso ) to a temporary directory on the IBM Tivoli Enterprise Monitoring Server system. For the purpose of this README, the symbol <TEMP> represents the fully qualified path to this directory.
     Note: On Windows, this includes the drive letter. 

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

 3. To add the this 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: if the fix was expanded to 
     <TEMP>/G01FXML:
     > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/G01FXML/WINDOWS/Deploy -t ud -f
     > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/G01FXML/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: if the fix was expanded to 
    <TEMP>/G01FXML:
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\G01FXML\WINDOWS\Deploy -t ud -f
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\G01FXML\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 update Agent 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 07140000

    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 07140000
                                          
    If there are not prior version kud agent on remote system, then use below 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 with 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 or 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.

 6.4 Agent support update
 ------------------------------
 Use the following steps to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop:

 1. Transfer the appropriate archive file (G01FXML.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 using the tar command on UNIX systems or an unzip utility on Windows systems. 
      On Unix/Linux systems,
      > tar -xvf G01FXML.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.

7.0 Additional installation information

=============================

 7.1 Verifying the update
 ----------------------------
 1. To verify that the agent was updated correctly, use the "tacmd" command to view the current version of the agent after the agent is restarted. You are required to log in to a Tivoli Enterprise 
      Monitoring Server before viewing the agent version. 

      For example:
      On Unix/Linux systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation directory. The default location is /opt/IBM/ITM. 

      > $CANDLEHOME/bin/tacmd login -s <server>
                                -u <itmuser> 
                                -p <password>
       where:
              <server> is the fully qualified hostname or IP address of the TEMS host
              <itmuser> is the user account on the TEMS host having sysadmin privileges
              <password> is the itmuser password .

      > $CANDLEHOME/bin/tacmd listSystems -t ud

     

      On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring installation directory, the default location is C:\IBM\ITM. 
      > %CANDLE_HOME%\bin\tacmd login -s <server>
                                  -u <itmuser> 
                                  -p <password>
      where:
              <server> is the fully qualified hostname or IP address of the TEMS host
              <itmuser> is the user account on the TEMS host having sysadmin privileges
              <password> is the itmuser password .

      > %CANDLE_HOME%\bin\tacmd listSystems -t ud

      When the agent update is successful, the agent version will be 07.14.00.00

      Note:
      - The component (-t) for the tacmd listSystems command is specified as two characters (ud), not three characters (kud).
 
 2. To verify that the agent support files were updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux or UNIX systems to dump the component versions on each of the following systems: Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring Server, and Tivoli Enterprise Portal desktop.  

     

      Note: The kincinfo and cinfo command output examples in the sections that follow show all components that can be updated.  If you do not have all of these components installed, then components that are not installed are not displayed in the output of these commands.     
    
    Sample output for the cinfo command on a UNIX or Linux systems
    --------------------------------------------------------------------------
    To validate that all components have been installed, run the following command:

     ./cinfo
     
    This command offers you four options on the CINFO menu shown in the example that follows.  Choose the option that meets your needs.
      

   Sample output of the kincinfo command on a Windows System
   ----------------------------------------------------------------------
   To validate that all components have been installed, run the following command:
    
       For example:
       > %CANDLE_HOME%\InstallITM\kincinfo -i
    
   >kincinfo -i

   kincinfo output:

   Windows: Monitoring Agent for DB2:

    UD        KUD(64-bit) CMA/IBM Tivoli Composite Application Manager Agent for DB2
          WIX64 Version: 07.14.00.00 Build: 11741

    UE        KUE(32-bit) CMA/Tivoli Enterprise Services User Interface Extensions
          WINNT Version: 06.30.07.09 Build: d1071a

    UI        KUI(32-bit) CLI/Tivoli Enterprise Services User Interface
          WINNT Version: 06.30.07.13 Build: 202103261420

8.0 Known problems and workarounds

==============================

   Problem: Remote deploy/upgrade of Db2 Agent on AIX platform fails (tacmd addSystem) with below error -

   Error message : KDY0021W: The management agent for system <target_hostname> is either offline or not installed. The management agent for the specified system must be installed and online in order for the command to process successfully.

   Workaround: Locally install/upgrade the Db2 Agent on AIX platform.

   Problem: tacmd addBundles command fails for Solaris platform with command "./tacmd addBundles -i <installer_directory>/unix -t ud -p sol286"

   Workaround: Use the command "./tacmd addBundles -i <installer_directory>/unix -t ud -p sol286 -n"

   Problem: When the Db2 agent is stopped abruptly, the watchdog process fails to start the Db2 agent.
   Workaround: Start the Db2 agent manually.
 
   Problem: Warning message appears when upgrading DB2 Agent 7.1.0 on RHEL 7.3 as : 
   cut: fields and positions are numbered from 1 Try 'cut --help' for more information. 
   CandleAgent failure: KCI0766E could not find arch "" in a JRE version file
   Workaround: Currency support for RHEL 7.3 is provided from DB2 Agent 7.1.1
   So, if DB2 Agent 7.1.0 was installed by running 
   "setarch $(uname -m) --uname-2.6" command before installation, 
   this message will appear when upgrading to 7.1.1.
   However, this warning is harmless and expected. So, it can be ignored.

   Problem: Cannot find 32 bit UD component after upgrading DB2 Agent 7.1.0 to 7.1.1 on 64 bit AIX platform. 
   Workaround: User can upgrade Db2 agent from 7.1.0 to 7.1.3. 

   
   Problem: Installation of DB2 Agent 7.1.1 may fails on HP-UX platform.
   Workaround: Replace the JRE version.
   In jrhpi116.dsc file, replace 
   <Command>|DEPOTDIR|/ci/DeployLnk.sh |DEPOTDIR| jr hpi116 070950000 </Command>
      with
   <Command>|DEPOTDIR|/ci/DeployLnk.sh |DEPOTDIR| jr hpi116 061630000 </Command>
   
   Replace release level from jrhpi116.ver file.
      # Release level.
      ver = 709
      rel = 100
      # Alternate Directory for Agent Version Parity
      altDir=tmaitm6
      VRMF = 07095000
      
      with 
      
     # Release level.
     ver = 616
     rel = 100

     # Alternate Directory for Agent Version Parity
     altDir=tmaitm6
     VRMF = 06163000
   
   Problem: DB2 Agent configuration with instance owner fails in case of installation is
   secured by secureMain and agent configuration is done by root user for the first time.
   The agent configuration fails with following error:
   **********
   KCIIN0524E Error attempting to build a merge file
   java.io.FileNotFoundException: /opt/IBM/ITM/tmp/.ud.rc (Permission denied)
   **********
   KCIIN0230E Unable to prompt for input...   
   Workaround: When installation is secured by secureMain, manually assign write
   permission to the owner and the Db2 admin group for file .ud.rc.

   Problem: If Customized SQL query contains the “order by” clause, then the relevant workspace does not show data and the Db2 server logs the following error in log file.
   The statement or command failed because it requires functionality that is not supported on a read-enabled HADR standby database. 
   Reason code = "5".
   Workaround: DB2 v11.1.0.0 server, or below does not support order by clause on standby. Hence Db2 agent cannot collect data for customized SQL workspace.
   To overcome this problem upgrade to DB2 v11.1.2.2 server that provides support for “order by” clause on standby. For more information, see 
   http://www-01.ibm.com/support/docview.wss?uid=swg1IT22612  
     
   Problem: When DB2 07.11.00.00 agent is pointed to ITM setup having DB2 07.14.00.00 support, 
   HADR details workspace shows no data on UI.
   Workaround: Upgrade DB2 agent from 07.11.00.00 to 07.14.00.00.
 

9.0 Additional product information

===========================
 None

 

10.0 Copyright and trademark information

================================
 A current list of IBM trademarks is available on the web at "Copyright
 and trademark information" at www.ibm.com/legal/copytrade.shtml.

 

11.0 Notices

==========
This information was developed for products and services offered 
in the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult 
your local IBM representative for information on the products and 
services currently available in your area. Any reference to an 
IBM product, program, or service is not intended to state or imply 
that only that IBM product, program, or service may be used. Any 
functionally equivalent product, program, or service that does not 
infringe any IBM intellectual property right may be used instead. 
However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document 
does not grant you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or 
any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION 
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, 
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to you.

Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of 
International Business Machines Corporation in the United States, other 
countries, or both. If these and other IBM trademarked terms are marked 
on their first occurrence in this information with a trademark symbol, 
these symbols indicate U.S. registered or common law trademarks owned by 
IBM at the time this information was published. Such trademarks may also 
be registered or common law trademarks in other countries. A current list 
of IBM trademarks is available on the Web at "Copyright and trademark 
information" at http://www.ibm.com/legal/copytrade.shtml.
Java and all Java-based trademarks and logos are trademarks or registered 
trademarks of Sun Microsystems, Inc. in the United States, other 
countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of 
Microsoft Corporation in the United States, other countries, or both.
Unix is a registered trademark of The Open Group in the United States 
and other countries.
Other company, product, or service names can be trademarks or service 
marks of others.

Document change history