IBM Support

IBM Tivoli Composite Application Manager for Applications V7.2.1.2: Tivoli Composite Application Manager Agent for DB2 07.12.00.00

Download


Abstract

This fix resolves the APARs and defects and provides the enhancements listed
in the "Problems Fixed" section below.

Download Description

(C) Copyright International Business Machines Corporation 2018.
 All rights reserved.

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


Component ID: 5724B96D0
       
Date: 28 August, 2018

Table of contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices

1.0 General description
=======================
This fix resolves the APARs and defects and provides the enhancements listed
in the "Problems Fixed" section below. This fix also includes the superseded
fixes listed in section 2.4. This contains only updates for IBM Tivoli Composite Application Manager Agent for
DB2.

You can download the IBM Tivoli Composite Application Manager Agent for
DB2 07.12.00.00 file from Passport Advantage(R) or from the
Downloads section of the IBM Software Support Web site:
https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html

When this image file is downloaded from the IBM Software Support Web site
or from Passport Advantage, these rules apply:
 * You can locally install this on a system that already hosts a
   licensed copy of IBM Tivoli Monitoring for Databases.
 * You can locally install this 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.

2.0 Problems fixed
==================
 The following problems are addressed by this release.

 2.1 APARS:
 ----------
   APAR     : IJ03816 
   Abstract : ITCAM Agent for DB2 ships with certificates in 'kud_resources.jar' that are signed
   with unsupported algorithm.
   Additional Information: 'kud_resources.jar' file was not shipped with expired certificate but
   signed with MD5 algorithm, JAR files signed with MD5 algorithms was treated as unsigned JARs
   due to java security change. This file is now signed with recent level of JAVA version to
   use SHA256 signature algorithm for signing.
  
   APAR     : IJ03077  
   Abstract : ITCAM Agent for DB2 does not display date correctly in Log Manager Workspace.
   Additional Information: The 'Diagnostic Messages' workspace, for 'DB2 Diagnostic Log'
   attribute group, displayed the Timestamp attribute as date & time string instead of
   displaying in proper format.
   For example :- It displayed 117111619015600 instead of 11/16/2017 19:01:56. 
         
 2.2 Defects
 -----------
   Defect : 133824
   Abstract : ITCAM Agent for DB2 did not send/update support files to the
   support directory in TEMA to support SDA in AIX.
   Additional Information: when db2 agent was remotely upgraded via depot,support directory
   in TEMA were cleaned up and all the support files for instance: KUDJSTPW.jar,KUDJSTPS.jar
   and KUDJSTMS.jar and KUDMSMAN.txt in support directory were also removed.
  
   Defect : 133889
   Abstract : ITCAM Agent for DB2 prerequisite scan failed on RHEL 6.5 platform.
   Additional Information: when db2 agent was installed on RedHat Enterprise Linux 6.5 OS platform
   prerequisite scans displayed status as FAIL during installation.
  
   Defect : 134346
   Abstract : Customized SQL attribute group for ITCAM DB2 agent displayed "Not_Available"
   for 5th number value only, not for all column where data was not present.
   Additional Information: DB2 agent used to display "Not_Available" for numeric value column only and blank
   for other columns when data is not present for those columns.In this release this issue is fixed and now
   db2 agent will display "Not_Collected" in each columns for customized SQL attribute group when custom SQL
   executes with error(excluding primary key and filter columns).If custom SQL executed successfully and returns
   no records then the respective result view will be blank with no row. And if custom SQL executes successfully
   and returns data for few columns,   say 2 string and 2 numeric columns then rest of the columns will display
   "Not_Applicable" and "Not_Available" as – 
   String/Numeric/Date Column Name = Not_Applicable.
   String/Numeric/Date Column Value = Not_Available.
  
   Defect : 134328
   Abstract : ITCAM Agent for DB2 Take Action command ‘Update DB Manager Configuration' failed to
   update DBM configuration.
   Additional Information: DB2 agent constructed Take Action command with invalid syntax that
   failed to execute at db2 server and produced error.
  

 2.3 Enhancements:
 -----------------
  2.3.1 RFE 122645 :ITCAM Agent for DB2HADR Monitoring Capabilities for multiple standbys.
        ----------------------------------------------------------------
        To monitor HADR status of all primary and standby databases configured in DB2 server,
        one new attribute group, one workspace and three predefined situation is introduced in this release.
  To have this enhancement working, agent start user should have an execute authority
  for table function SYSPROC.MON_GET_HADR.
  Following are details:
       
  New attribute group:
  DB2 HADR01.
       
  New default workspace:
  Database HADR Details under Database navigator item.This workspace is linked to Database HADR workspace.
  When clicked any of the database listed in Database HADR workspace,Database HADR Details workspace will be
  opened and display information about all primary/standby databases configured for selected database.
              
  New views:
  The views displays the status of HADR attributes and information about Primary and
  Standby databases.
        following are newly introduced views. 
        - HADR Flag Status. 
        - Log Shipping Statistics.  
        - Primary/Standby Details.
  - Database Configuration Information.  
         
  New predefined situations:
  -   UDB_HADR_Receive_Blocked_Crit
            Declares a critical condition when the receiving logs are blocked on the standby database.
   
  -   UDB_HADR_State_Disconnect_Warn
            Declares a warning when the High Availability Disaster Recovery (HADR) database is not
   connected to its partner node.

        -   UDB_HADR_Key_Rotation_Err_Crit
            Declares a critical condition when the standby database encounters a master key rotation error.   

 2.4 Superseded fixes:
 ---------------------
  IBM Tivoli Composite Application Manager Agent for DB2.
  7.1.1-TIV-ITM_DB2-FP0000
 

 2.5 APARS and defects included from superseded fixes
 ----------------------------------------------------

  7.1.1-TIV-ITM_DB2-FP0000
   ------------------------
    APAR:
 ---------------------
 APAR: IV98243
 Abstract: ITCAM for DB2 7.1 agent fails install on RHEL 7.
 Additional information: DB2 agent install to pass prerequisite checking
    on a Red Hat Enterprise Linux Server release 7.3.
 
 Defects:
 ---------------------
   
    Defect : 107921
    Abstract : Reading DB2_HADR_ROS parameter to avoid connection to
    standby databases.
    Additional Information: DB2 agent checks the value of DB2 server parameter
    DB2_HADR_ROS and agent environment variable KUD_CONNECT_TO_STANDBYDB.
    If DB2_HADR_ROS =ON and KUD_CONNECT_TO_STANDBYDB =Y are set, then
    agent connects to standby database, otherwise standby database is
    skipped during data collection. Refer section 2.6 for more details
    about KUD_CONNECT_TO_STANDBYDB variable.
 
 Defect : 125974
    Abstract : DB2 server 9.1 out of support.
    Additional Information : DB2 Agent no longer supports DB2 server 9.1.
 
 Defect : 124892
 Abstract : DB2 agent should read correct CF node setting while parsing
 DB2_CF_PARTITION_NUMS.
 Additional Information : DB2_CF_PARTITION_NUMS variable is used by agent
 to exclude CF nodes from data collection algorithm in pureScale environment.
 Value passed to this variable was not parsed correctly by agent , hence was
 resulting in unexpected behavior.
  
    Enhancements:
 ---------------------
 
 Abstract: Currency support for new versions of OS platforms.
    Additional Information: Added currency support for following platforms:
    Windows Server 2016, Windows Server 2012 R2 data-centre edition ,
    Window Server 2008 R2 data-centre edition, AIX 7.2 (64 bit) ,
    RHEL 7.3, SLES 12.

    Abstract: Support for new OS platforms: 
    Additional Information: Support for following OS platforms is newly introduced in
 this release:
    ZLinux on Ubuntu 16.04.2, zLinux RHEL 7.3 , zLinux on SUSE 12,
    Plinux little-endian platform [ PPC64LE ].
  
    Abstract: Improvement in DB2_Table attribute group data collection algorithm.
    Additional Information: The source SQL queries used for data collection of
    DB2_Table attribute group are optimized to improve 
    data collection time.
  
    Abstract: Introduced a way to set time-out value for SQL query execution.
    Additional Information: DB2 agent uses SQL queries as data source for many attribute groups.
    In this release new variables, KUD_QUERY_TIMEOUT, is introduced
    to set time-out value for execution of each query.
    Refer section 2.6 for more details about environment variable.
  
    Abstract: Provided support for data collection from all partitions:
    Additional Information: New environment variable, KUD_MULTIPARTITION_DATA, is introduced
    in this release to support data collection from all partitions
    in multi- partition environment.
    Refer section 2.6 for more details about environment variable.
 
 Abstract: Added new attributes, Table Name (New Unicode) and
    Table Schema (New Unicode), in DB2 Table, DB2 Application00 and
    DB2 Locking Conflict attribute groups.
    Additional information: In DB2 maximum allowed length for table name and table schema is
    128 characters. To comply with 128 characters long table name and
    table schema , 6 new attributes are added with size of 128 characters.
 
 RFE: 87986
 Abstract: ITCAM for DB2 should have default view that shows
    long running SQL queries.
 Additional information: To monitor long running SQL queries in DB2 server,
    one new attribute group, one default workspace and one predefined
    situation is introduced in this release. Following are details:
       
  New attribute group      : DB2 Current SQL.
       
  New default workspace    : Current Running SQL workspace under
     Database navigator item. This workspace shows top 20 long running
           SQL statements for each database, sorted based on value of
           ‘Elapsed Time in Seconds’ attribute. This default behavior
           can be changed using KUD_TOP_RUNNING_SQL and KUD_SQL_ORDERBY
           environment variables.
           Refer section 2.6 for more details about environment variables.
       
  New predefined situation : UDB_Current_SQL_Status_Crit
           Formula : Status of query = critical.
           The value for status attribute is evaluated as below :
           - For situation request with condition on attributes other than
             status and DB Name, status is always critical. 
           - For all other request types, Status of query is evaluated on the
             basis of sorting criteria defined in KUD_SQL_ORDERBY environment
             variable and threshold value defined in KUD_SQL_THRESHOLD
             environment variable.
             Refer section 2.6 for more details about environment variables.
 
 
 
   2.6 Additional Settings included from superseded fixes:
 ------------------------------------------------------
 Environment Variables:
 -----------------
 Support for following environmental variables is included in this
 fix. To use particular variable on UNIX systems, add it in
 $CANDLEHOME/config/ud.ini file. And to use it on windows systems,
 add it in %CANDLE_HOME%\<agent_install_dir>\KUDENV_<InstanceName>
 file.

 KUD_CONNECT_TO_STANDBYDB:
      - Usage: Can be used to allow/deny making connection on standby
               database.
               Set KUD_CONNECT_TO_STANDBYDB=Y in agent
               configuration file and DB2_HADR_ROS =ON in DB2 server
               to enable connection to standby DB. 
      - Default value : 'N'.
      - Possible values : [KUD_CONNECT_TO_STANDBYDB=Y],
               [KUD_CONNECT_TO_STANDBYDB=N].

    KUD_QUERY_TIMEOUT:
      - Usage: Can be use to set time-out parameter for individual query
               used in attribute group for data collection.
      - Default value : 45 seconds.
      - Possible values : Valid range lies in between 20 - 300 seconds.
               Out of range time-out value will result in considering
               default value.
 
    KUD_MULTIPARTITION_DATA:
      - Usage: Can be used to set data collection algorithm for attribute
               groups in multi-partition environment. This variable contains
               comma separated list of attribute groups. And for all the
               attribute groups added in this list, data will be collected
               from all partitions.
               Currently support is provided only for 2 attribute groups :
               DB2_Tablespace_Auto-resize [KUDRESIZ] and
               Table Space [KUDTBLSPACE]
      - Default value : No default value.
               In this case data will be collected for current partition only.
      - Possible values : [KUD_MULTIPARTITION_DATA=KUDTBLSPACE,KUDRESIZ],
               [KUD_MULTIPARTITION_DATA=KUDRESIZ] ,
               [KUD_MULTIPARTITION_DATA=KUDTBLSPACE].  
 
 KUD_SQL_ORDERBY:
      - Usage: Can be used to set sorting criteria for data collection of
               'DB2_Current_SQL’ attribute group .
      - Default value : 'ELAPSED_TIME’.
      - Possible values : [KUD_SQL_ORDERBY=ELAPSED_TIME],
               [KUD_SQL_ORDERBY=CPU_TIME].
 
    KUD_SQL_THRESHOLD:
      - Usage: Can be use to set the threshold value for the sorting criteria
               selected through KUD_SQL_ORDERBY variable.
      - Default value : 300 (seconds).
      - Possible values : Valid range lies from 0 to No Limit.
 
   KUD_TOP_RUNNING_SQL:
      - Usage: Can be used to set limit on number of rows retrieved by
              'DB2_Current_SQL’ attribute group. Value of this variable is
               ignored for situation requests.
      - Default value : Default value of this variable is '20'.
      - Possible values : Valid range lies from 1 to 50. Out of range value
               will result in considering default value
 
 KUD_LOCKCONFLICT_BY_SQL:
   - Can be used to set Locking Conflict attribute group data
     collection method.
   - Set KUD_LOCKCONFLICT_BY_SQL=Y to do data collection using
     SQL method.
     To collect data by using SQL method, DB2 version must be
     9.7 FP1 or later.
     If data is not collected using SQL method then it is
     required to explicitly grant required user permissions by
     running following statements on DB2 console for *EACH*
     database.

    CONNECT TO <database_name>
    GRANT EXECUTE ON FUNCTION
       SYSPROC.SNAP_GET_APPL_INFO_V95(VARCHAR(128),INTEGER)
       TO USER <username>
      
       GRANT SELECT ON
       SYSIBMADM.MON_LOCKWAITS
       TO USER <username>
      
       GRANT EXECUTE ON FUNCTION
       SYSPROC.MON_GET_APPL_LOCKWAIT
       TO USER <username>
      
       GRANT SELECT ON
       SYSIBMADM.TBSP_UTILIZATION
       TO USER <username>
      
       GRANT EXECUTE ON FUNCTION
       SYSPROC.MON_GET_LOCKS(CLOB(),INTEGER)
       TO USER <username>
      
       Where, <username>: for Windows – SYSTEM is default user,
       for UNIX - instance owner is user.
      
       - Set KUD_LOCKCONFLICT_BY_SQL=N to do data collection
         using snapshot.
       - Default value of this variable is 'Y'.
      
      
     KUD_REPLICATION_ON:
       - Can be used to avoid execution of ASN queries.
       - Set KUD_REPLICATION_ON=Y to execute all ASN queries
         irrespective of the ASN schema presence.
       - Set KUD_REPLICATION_ON=N to exclude the ASN queries
         from execution.
       - Default value of this variable is 'Y'.
      
     DB2_CF_PARTITION_NUMS:
       - Can be used to exclude CF nodes from data
         collection algorithm in pureScale environment.
       - Set DB2_CF_PARTITION_NUMS=<CF node number>.
       - No default value is set for this variable.
      
     KUD_T1_BY_SQL:
       - Can be used to set tablespace attribute group
         collection method.
       - Set KUD_T1_BY_SQL=Y to do data collection by using
         SQL queries.
         To collect data by using SQL queries, DB2 version must
         be 9.7 or later,
         and the user who starts the DB2 agent must have
         EXECUTION privileges on MON_GET_TABLESPACE and
         MON_GET_CONTAINER for all databases.
       - Set KUD_T1_BY_SQL=N to do data collection by using
         snapshot.
       - Default value of this variable is 'N'.
      
     KUD_T1_DISABLE:
       - Can be used to disable tablespace attribute group
         collection.
       - Set KUD_T1_DISABLE=Y to disable data collection.
       - Set KUD_T1_DISABLE=N to enable data collection.
       - Default value of this variable is 'N'.
      
     KUD_DIAGLOG_BY_TABLE:
       - Can be used for DB2 version 10 and above to collect
         diagnostic log by table query,
       - Set KUD_DIAGLOG_BY_TABLE=Y to start data collection
         using SQL query.
       - Set KUD_DIAGLOG_BY_TABLE=N to start data collection
         by parsing diagnostic logs.
       - Default value of this variable is 'Y'.
      
     KUD_DISABLE_DIAGLOG:
       - Can be used to disable diagnostic log attribute group
         collection.
       - Set KUD_DISABLE_DIAGLOG=Y to disable data collection.
       - Set KUD_DISABLE_DIAGLOG=N to enable data collection.
       - Default value of this variable is 'N'.
      
     KUD_SNAPSHOT_DUMPOUT:
       - Can be used to trace DB2 snapshot buffer of specific
         attribute group.
       - Set KUD_SNAPSHOT_DUMPOUT=Y to dump snapshot buffer data
         into file.
       - Set KUD_SNAPSHOT_DUMPOUT=N to disable snapshot buffer
         dump data feature.
       - There is no default value set for this variable.
      
     KUD_SNAPSHOT_READIN:
       - Can be used to trace agent with DB2 snapshot buffer of
         specific attribute group,
       - Set KUD_SNAPSHOT_READIN=Y to enable tracing.
       - Set KUD_SNAPSHOT_READIN=N to disable the tracing.
       - There is no default value set for this variable.
 

3.0 Architecture and prerequisites
==================================
 The following link is for the Tivoli operating system and application
 support matrix. Refer to this matrix for the latest certification
 information.

 http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

 3.1 Prerequisites for this fix
 -----------------------------
  None.
 

4.0 Image directory contents
============================
Electronic Part Number: ITCAM Apps Ag for DB2 CNV16ML

This fix image contains the following files and directories:
AUTORUN.INF          [Deploy]             DeployLnk.sh
[InstallITM]         README.TXT           [WIA64]
[WINDOWS]            install.sh           kcirunas.cfg
[license]            non_ibm_license      notices
silent_config.txt    silent_install.txt   [unix]
[REPORTS]

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] or [WIA64] according to your Windows platform.


5.0 Installation instructions
=============================

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

 * You can locally install this on a system that already hosts a
   licensed copy of IBM Tivoli Monitoring for Databases.
 * You can locally install this 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.


 5.1 Before installing the fix
 -----------------------------
  - The prerequisites listed under section 3.1 entitled 'Upgrade
    prerequisites for this fix' must be installed when for upgrade.

  - For the purpose of this README, the symbol <CANDLEHOME> 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 DB2
    ud.ini file on 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.


 5.2 Local agent install and update (including silent installation)
 --------------------------------------------------------------
 1. Transfer the appropriate archive file (CNV16ML.tar.gz or .iso) to a
    temporary directory on the system that contains the agent code to be
    updated. 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 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 64bit Windows. Does not support 32bit upgrade to 64bit binary.


 5.3 Remote agent update and installation
 ----------------------------------------
 1. Transfer the appropriate archive file (CNV16ML.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>/CNV16ML:
    > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNV16ML/WINDOWS/Deploy -t ud -f
    > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNV16ML/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>/CNV16ML:
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNV16ML\WINDOWS\Deploy -t ud -f
    > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNV16ML\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. Commands
    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 071200000

    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 071200000
                                         
    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.

 

 5.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 (CNV16ML.tar.gz or .iso) to
    the IBM 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.

 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.


6.0  Additional installation information
========================================

 6.1 Verifying the update
 ------------------------
  1. To verify that the agent was updated correctly, use the tacmd to
    view the current version of the agent.  You are required to login
    to a Tivoli Enterprise Monitoring Server prior to viewing the agent
    version. 
                
    For example:
    On a UNIX system, 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>
    > $CANDLEHOME/bin/tacmd listSystems -t ud

    On a Windows system, 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>
    > %CANDLE_HOME%\bin\tacmd listSystems -t UD

    When the agent update is successful, the agent version will be
    07.12.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.
     
*********** Tue Aug 21 18:02:46 IST 2018 ******************
User: root Groups: root db2iadm1
Host name : FVSESX1-DB2-T-2      Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/ITM/v712/Build4/Final/Test
***********************************************************
...Product inventory

ax      IBM Tivoli Monitoring Shared Libraries
         lx8266  Version: 06.30.07.00

gs      IBM GSKit Security Interface
         lx8266  Version: 08.00.50.69

jr      Tivoli Enterprise-supplied JRE
         lx8266  Version: 07.09.50.00

ud      IBM Tivoli Composite Application Manager Agent for DB2
         lx8266  Version: 07.12.00.00

ue      Tivoli Enterprise Services User Interface Extensions
         lx8266  Version: 06.30.07.00

ui      Tivoli Enterprise Services User Interface
         lx8266  Version: 06.30.07.00


   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.12.00.00 Build: 82061


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

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


7.0 Known problems and workarounds
==================================
 - 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: When the Db2 agent is stopped abruptly, the watchdog process fails to start the Db2 agent.
   Workaround: Start the Db2 agent manually.  
 
 - Problem: Data is not displayed for “Current Running SQL” workspace
   because of permission issue.
   Workaround: Data shall be displayed for “Current Running SQL” workspace
   after providing below permission to instance user.
   db2 GRANT SELECT ON SYSIBMADM.MON_CURRENT_SQL TO USER <instance_User>.

 - 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 prior to installation,
   this message will appear when upgrading to 7.1.1.
   However, this warning is harmless and expected. So, it can be ignored.


 - Problem: Can not find 32 bit UD component after upgrading DB2 Agent
   7.1.0 to 7.1.1 on 64 bit AIX platform.
   Workaround: Both 32 and 64 bit UD components were installed for
   DB2 Agent 7.1.0 on 64 bit AIX platform.From DB2 Agent 7.1.1, components
   are installed based on machine architecture.So, for 64 bit AIX platform,
   only 64 bit UD component will get upgraded to 7.1.1 and
   32 bit component will be removed.

 - 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: 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


       
8.0 Additional product information
==================================
None.


9.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 may be trademarks or service
marks of others.

Installation Instructions

Please refer to the README contained in the Description section above for general installation instructions.

Download Package

DB2 Agent 07.12.00.00 installer can be downloaded from IBM passport advantage using part number CNV16ML.

IBM Tivoli Composite Application Manager for Applications V7.2.1.2 : IBM Tivoli Composite Application Manager Agent for DB2 v7.1.2, Multiplatform, Multilingual (CNV16ML )

Off
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"Component":"5724B96D0","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF006","label":"CentOS"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF031","label":"Ubuntu"},{"code":"PF033","label":"Windows"}],"Version":"07.12.00.00","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

Db2 Agent

Document Information

Modified date:
11 September 2018

UID

ibm10729659