Download
Version
DB2, Version 7.1.6 Interim Fix 0001
Abstract
This fix resolves the APARs and defects listed in the "Problems Fixed" section below.
Download Description
Copyright International Business Machines Corporation 2023.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager Agent for DB2, Version 7.1.6All rights reserved.
Component ID: 5724B96DO
---------------------------------------------------------------------------
Interim Fix: 0001 (7.1.6-TIV-ITM_DB2-IF0001)
---------------------------------------------------------------------------
Interim Fix: 0001 (7.1.6-TIV-ITM_DB2-IF0001)
---------------------------------------------------------------------------
Date: November 07, 2023
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 Copyright and trademark information
10.0 Notices
Abstract: ITCAM DB2 AGENT 7.16.00 HIGH CPU USAGE WHEN KUD_DIAGLOG_BY_TABLE SET TO N
Additional Information: When DB2 agent is upgraded to 7.1.6-TIV-ITM_DB2-FP0000 the CPU usage can be higher than expected, if variable KUD_DIAGLOG_BY_TABLE is set to N in ud.ini file. The agent log can be flooded with messages like:
(6459F286.467E-6:kumprmfr.c,473,"KUMP_ReadMonitorFileUnicodeReco
rd") ***** File record discarded <2023-05-09-09.11.37.122418+120
I36682714A572 LEVEL: Error
2.2 Defects
------------------
Defect: 147303
Abstract: In v716 agent on RHEL 8.x pLinuxLE platform, when data is collected by parsing db2diag.log file, then Diagnostic Messages data is NOT displayed on UI.
Additional information: libkududp library which is required for parsing logs from db2diag.log was missing from the <candle-home>/lpl266/ud/lib.
Defect: 147293
Abstract: Agent Memory increasing rapidly for 6-7 days, after that it is stable at very high level (around 350MB).
Additional information: When data is being collected by parsing db2diag.log file and HDC is enabled for all AGs and 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 very high level (around 350 MB). However, in standalone setup Memory was stable in below 50MB.
2.4 APARs and defects included from superseded fixes
--------------------------------------------------------------
None
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'.
3.1 Prerequisites for this fix
-------------------------------
The prerequisite level for this fix is as follows:
-------------
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 Copyright and trademark information
10.0 Notices
1.0 General description
=======================
This fix resolves the APARs and defects that are listed in the "Problems Fixed" section below.
2.0 Problems fixed
==============
2.1 APARs
-------------
APAR: IJ46391-------------
Abstract: ITCAM DB2 AGENT 7.16.00 HIGH CPU USAGE WHEN KUD_DIAGLOG_BY_TABLE SET TO N
Additional Information: When DB2 agent is upgraded to 7.1.6-TIV-ITM_DB2-FP0000 the CPU usage can be higher than expected, if variable KUD_DIAGLOG_BY_TABLE is set to N in ud.ini file. The agent log can be flooded with messages like:
(6459F286.467E-6:kumprmfr.c,473,"KUMP_ReadMonitorFileUnicodeReco
rd") ***** File record discarded <2023-05-09-09.11.37.122418+120
I36682714A572 LEVEL: Error
2.2 Defects
------------------
Defect: 147303
Abstract: In v716 agent on RHEL 8.x pLinuxLE platform, when data is collected by parsing db2diag.log file, then Diagnostic Messages data is NOT displayed on UI.
Additional information: libkududp library which is required for parsing logs from db2diag.log was missing from the <candle-home>/lpl266/ud/lib.
Defect: 147293
Abstract: Agent Memory increasing rapidly for 6-7 days, after that it is stable at very high level (around 350MB).
Additional information: When data is being collected by parsing db2diag.log file and HDC is enabled for all AGs and 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 very high level (around 350 MB). However, in standalone setup Memory was stable in below 50MB.
2.3 Superseded fixes
------------------------
None
------------------------
None
2.4 APARs and defects included from superseded fixes
--------------------------------------------------------------
None
2.5 Additional Settings
--------------------------
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.
--------------------------
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_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 by using SQL method.
To collect data by using SQL method, DB2 version must be 9.7 FP1 or later.
If data is not collected by using SQL method, then it is required to explicitly grant the required user permissions by running the following statements on DB2 console for *EACH* database.
- Can be used to set Locking Conflict attribute group data collection method.
- Set KUD_LOCKCONFLICT_BY_SQL=Y to do data collection by using SQL method.
To collect data by using SQL method, DB2 version must be 9.7 FP1 or later.
If data is not collected by using SQL method, then it is required to explicitly grant the required user permissions by running the 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 EXECUTE ON FUNCTION
SYSPROC.SNAP_GET_APPL_INFO_V95(VARCHAR(128),INTEGER)
TO USER <username>
GRANT SELECT ON
SYSIBMADM.MON_LOCKWAITS
TO USER <username>
SYSIBMADM.MON_LOCKWAITS
TO USER <username>
GRANT EXECUTE ON FUNCTION
SYSPROC.MON_GET_APPL_LOCKWAIT
TO USER <username>
SYSPROC.MON_GET_APPL_LOCKWAIT
TO USER <username>
GRANT SELECT ON
SYSIBMADM.TBSP_UTILIZATION
TO USER <username>
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.
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 by using snapshot.
- Default value of this variable is 'Y'.
- 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'.
- 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 by using SQL query.
- Set KUD_DIAGLOG_BY_TABLE=N to start data collection by parsing diagnostic logs.
- Default value of this variable is 'Y'.
- 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 by 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.
- 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
===========================
This fix is supported on all operating systems listed in the detailed system requirements report for the DB2 V7.1 agent:https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html
See the IBM Software Product Compatibility Reports (SPCR) for the latest operating system certification information:
See the IBM Software Product Compatibility Reports (SPCR) for the latest operating system certification information:
3.1 Prerequisites for this fix
-------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Composite Application Manager Agent for DB2 7.1.6.
IBM Tivoli Composite Application Manager Agent for DB2 7.1.6. Software Product Compatibility Report link: https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html
As this fix is cumulative, it can be installed on any fix level for this version, release, and mod level above the prerequisite.
Use the following steps to install this fix.
5.1 Before installing the fix
------------------------------
- The prerequisites listed in section 3.1 entitled "Prerequisites for this fix" must be installed before this fix can be installed.
5.2 Local agent update
-------------------------
On a Windows system, if the fix was expanded to <TEMP>\7.1.6-TIV-ITM_DB2-IF0001, use the following installation command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.6-TIV-ITM_DB2-IF0001\kud_wix64_tema_if0001.cab
5.3 Remote agent update
-----------------------------
1. Transfer the appropriate archive file (7.1.6-TIV-ITM_DB2-IF0001.tar.gz or .zip) to a temporary directory on the Tivoli Enterprise Monitoring Server system. For the purpose of this README, the
<TEMP> symbol represents the fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.
Follow the installation instructions that are contained in the "6.2-TIV-ITM_ASI-IF0002.README."
On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]
On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli Monitoring installation directory.
-r <response file> - Required. Customized response file name. The default response.txt file in the CD-ROM directory can be copied and modified for your environment. Do not update the response.txt file.
-j <JAVAHOME> - Optional. The fully qualified path to the "bin" directory where Java(R) is installed. The location of Java on your system might vary.
6.2 Installation instructions for agent baroc file
-----------------------------------------------------
[This fix (7.1.6-TIV-ITM_DB2-IF0001) includes changes to the agent baroc files that must be reinstalled. [If you have already installed these baroc files, there are no additional installation steps. If not, see the version of the IBM Tivoli Monitoring Installation and Setup Guide that is appropriate for your installation. See "Installing monitoring agent baroc files on the event server" in the "Installing the IBM Tivoli Enterprise Console Event Synchronization" section for more information.
6.3 Additional information on using the "itmpatch" command
----------------------------------------------------------------------
The "itmpatch" command has the following syntax:
6.4 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.
"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 jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.
IBM Tivoli Composite Application Manager Agent for DB2 7.1.6. Software Product Compatibility Report link: https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html
As this fix is cumulative, it can be installed on any fix level for this version, release, and mod level above the prerequisite.
4.0 Image directory contents
=======================
This fix image contains the following files:
- 7.1.6-TIV-ITM_DB2-IF0001.README - This README file
- 7.1.6-TIV-ITM_DB2-IF0001.tar.gz - Fix archive .tar.gz format
- 7.1.6-TIV-ITM_DB2-IF0001.zip - Fix archive .zip format
- 7.1.6-TIV-ITM_DB2-IF0001.tar.gz - Fix archive .tar.gz format
- 7.1.6-TIV-ITM_DB2-IF0001.zip - Fix archive .zip format
Note: The .tar.gz and .zip files are identical in content. Use the .tar.gz file, if you are working on a UNIX(R) environment; use the .zip file if you are working on a Windows(R) environment.
The fix archive file contains the following files:
- 7.1.6-TIV-ITM_DB2-IF0001/kud_aix526_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_hpi116_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_li6263_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_ls3266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lpp266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lpl266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lx8266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol283_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol286_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol606_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_tems_teps_tepd_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_wix64_tema_if0001.cab
- 7.1.6-TIV-ITM_DB2-IF0001/kud_tems_teps_tepd_if0001.zip
- 7.1.6-TIV-ITM_DB2-IF0001/kudaix526.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudhpi116.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudli6263.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudls3266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlpl266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlpp266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlx8266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol283.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol286.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol606.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudwix64.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kud_hpi116_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_li6263_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_ls3266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lpp266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lpl266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_lx8266_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol283_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol286_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_sol606_tema_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_tems_teps_tepd_if0001.tar
- 7.1.6-TIV-ITM_DB2-IF0001/kud_wix64_tema_if0001.cab
- 7.1.6-TIV-ITM_DB2-IF0001/kud_tems_teps_tepd_if0001.zip
- 7.1.6-TIV-ITM_DB2-IF0001/kudaix526.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudhpi116.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudli6263.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudls3266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlpl266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlpp266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudlx8266.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol283.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol286.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudsol606.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/kudwix64.dsc
- 7.1.6-TIV-ITM_DB2-IF0001/inst_prereq_patch.sh
- 7.1.6-TIV-ITM_DB2-IF0001/ud_dd_071600001.xml
- 7.1.6-TIV-ITM_DB2-IF0001/ud_dd.properties
- 7.1.6-TIV-ITM_DB2-IF0001/ud_dd_071600001.xml
- 7.1.6-TIV-ITM_DB2-IF0001/ud_dd.properties
5.0 Installation instructions
=======================
This fix can only be installed over an existing installation. Use the following steps to install this fix.
5.1 Before installing the fix
------------------------------
- The prerequisites listed in section 3.1 entitled "Prerequisites for this fix" must be installed before this fix can be installed.
- For the purpose of 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 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.
- 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 update
-------------------------
1. Transfer the appropriate archive file (7.1.6-TIV-ITM_DB2-IF0001.tar.gz or .zip) to a temporary directory on the system that contains the agent code to be updated. For the purpose of this README, the <TEMP> symbol represents the fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.
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 6.2.
On a UNIX system, if the fix is expanded to <TEMP>/7.1.6-TIV-ITM_DB2-IF0001, use the following installation command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.6-TIV-ITM_DB2-IF0001/kud_xxxxxx_tema_if0001.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_if0001.tar.
> ./cinfo -i
Monitoring Agent for DB2
aix526 Version: 07.16.00.01
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 6.2.
On a UNIX system, if the fix is expanded to <TEMP>/7.1.6-TIV-ITM_DB2-IF0001, use the following installation command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.6-TIV-ITM_DB2-IF0001/kud_xxxxxx_tema_if0001.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_if0001.tar.
> ./cinfo -i
Monitoring Agent for DB2
aix526 Version: 07.16.00.01
On a Windows system, if the fix was expanded to <TEMP>\7.1.6-TIV-ITM_DB2-IF0001, use the following installation command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.6-TIV-ITM_DB2-IF0001\kud_wix64_tema_if0001.cab
5.3 Remote agent update
-----------------------------
1. Transfer the appropriate archive file (7.1.6-TIV-ITM_DB2-IF0001.tar.gz or .zip) to a temporary directory on the Tivoli Enterprise Monitoring Server system. For the purpose of 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.
On UNIX systems, if the fix was expanded to <TEMP>/7.1.6-TIV-ITM_DB2-IF0001:
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/7.1.6-TIV-ITM_DB2-IF0001
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/7.1.6-TIV-ITM_DB2-IF0001
On Windows systems, if the fix was expanded to <TEMP>\7.1.6-TIV-ITM_DB2-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\7.1.6-TIV-ITM_DB2-IF0001
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 Section 3.1 for the prerequisites for this fix.
-i is the directory that contains the deployment bundles to be added to the depot.
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\7.1.6-TIV-ITM_DB2-IF0001
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 Section 3.1 for the prerequisites for this fix.
-i is the directory that contains the deployment bundles to be added to the depot.
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 about the
"tacmd login" and "tacmd updateAgent" commands, see the "IBM Tivoli Monitoring Administrator's Guide".
"tacmd login" and "tacmd updateAgent" commands, see the "IBM Tivoli Monitoring Administrator's Guide".
On UNIX systems:
> $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 071600001
> $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 071600001
On Windows systems:
> %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 071600001
Note:
- 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 an "tacmd updateAgent" command is always an OS agent.
5.4 Agent support update
-----------------------------
This fix (7.1.6-TIV-ITM_DB2-IF0001) includes changes to the agent support files that must be installed. Use the following steps to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.
> %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 071600001
Note:
- 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 an "tacmd updateAgent" command is always an OS agent.
5.4 Agent support update
-----------------------------
This fix (7.1.6-TIV-ITM_DB2-IF0001) includes changes to the agent support files that must be installed. 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 (7.1.6-TIV-ITM_DB2-IF0001.tar.gz or .zip) to the Tivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops.
2. Expand the archive file by using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.
3. Expand the archive file (kud_tems_teps_tepd_if0001.tar or .zip) that contains the updates for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop by using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that includes a subdirectory called CD-ROM, with the necessary updates.
2. Expand the archive file by using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.
3. Expand the archive file (kud_tems_teps_tepd_if0001.tar or .zip) that contains the updates for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop by using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that includes a subdirectory called CD-ROM, with the necessary updates.
4. Use one of the following options to install the application support files.
A. Use the self-describing agent (SDA) capability.
With the self-describing agent capability, new or updated IBM Tivoli Monitoring agents that are using IBM Tivoli Monitoring V6.2.3 or later can become operational after installation without having to perform additional product support installation steps. To take advantage of this capability, see "Enabling self-describing agent capability at the hub monitoring server" topic in the IBM Tivoli Monitoring Installation and Setup Guide. Also, see "Self-describing monitoring agents" in the IBM Tivoli Monitoring Administrator's Guide.
With the self-describing agent capability, new or updated IBM Tivoli Monitoring agents that are using IBM Tivoli Monitoring V6.2.3 or later can become operational after installation without having to perform additional product support installation steps. To take advantage of this capability, see "Enabling self-describing agent capability at the hub monitoring server" topic in the IBM Tivoli Monitoring Installation and Setup Guide. Also, see "Self-describing monitoring agents" in the IBM Tivoli Monitoring Administrator's Guide.
Skip agent support update steps 5 and 6 if you use the self-describing agent capability.
B. Use the Application Support Installer script to launch either GUI installation or silent installation of the application support files.
Note: For IBM Tivoli Monitoring Version 6.3 or later, one of the following additional steps must be performed:
1. Acquire a platform-specific prepackaged JRE version of the Application Support Installer (ASI). See IBM Tivoli Monitoring Application Support Installer, 6.2-tiv-itm_asi-IF0002 at http://www-01.ibm.com/support/docview.wss?uid=swg24034924 for download and installation instructions.
2. Specify the -j javahome parameter with the path to a 32-bit java(r) 1.5 or java 1.6 installation when running the itmasi.sh or itmasi.bat script described below.
GUI installation option
--------------------------
The Application Support Installer can be started by using one of the following commands from within the CD-ROM directory where the setup.jar file is located:
On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]
On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli Monitoring installation directory.
--------------------------
The Application Support Installer can be started by using one of the following commands from within the CD-ROM directory where the setup.jar file is located:
On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]
On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli Monitoring installation directory.
-j <JAVAHOME> - Optional. The fully-qualified path to the "bin" directory where Java(R) is installed.
The location of Java on your system might vary.
When prompted by the Application Support Installer for the installable media directory, select the CD-ROM directory, not the component directory. The installer can install updates for multiple components at the same time.
The location of Java on your system might vary.
When prompted by the Application Support Installer for the installable media directory, select the CD-ROM directory, not the component directory. The installer can install updates for multiple components at the same time.
Silent installation option
---------------------------
To use the silent installation option, use one of the following commands from within the CD-ROM directory where the setup.jar file is located.
Note: Agent support upgrade for IBM Tivoli Monitoring Version 6.3 or above on Linux, zLinux, Solaris, and windows operating systems requires the following files contained in interim fix 6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and silent installation option of agent support upgrade.
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
- Solaris: setupSolaris.bin
- Windows: setupwin32.exe
---------------------------
To use the silent installation option, use one of the following commands from within the CD-ROM directory where the setup.jar file is located.
Note: Agent support upgrade for IBM Tivoli Monitoring Version 6.3 or above on Linux, zLinux, Solaris, and windows operating systems requires the following files contained in interim fix 6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and silent installation option of agent support upgrade.
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
- Solaris: setupSolaris.bin
- Windows: setupwin32.exe
Follow the installation instructions that are contained in the "6.2-TIV-ITM_ASI-IF0002.README."
On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]
On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli Monitoring installation directory.
-r <response file> - Required. Customized response file name. The default response.txt file in the CD-ROM directory can be copied and modified for your environment. Do not update the response.txt file.
-j <JAVAHOME> - Optional. The fully qualified path to the "bin" directory where Java(R) is installed. The location of Java on your system might vary.
5. The next panel presented by the Application Support Installer asks for the selection of Tivoli Monitoring components to which you want to add application support. The Application Support Installer detects which IBM Tivoli Monitoring components are installed.
For this fix, check or clear the check boxes as follows:
For this fix, check or clear the check boxes as follows:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the DB2 agent 07.16.00.01 support to complete the installation.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal Browser was running when the update was installed, it must be restarted.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal Browser was running when the update was installed, it must be restarted.
6.0 Additional installation information
=============================
6.1 Patch upgrade on Windows machine
---------------------------------------------
On Windows machine, different agent binaries are used for different instances of DB2 server that are configured for monitoring.
Installing patch by following the steps mentioned in section 5.2 and 5.3 will replace only template agent binary and will not replace instance specific binary. So latest agent binary will not be used for monitoring.
To use latest binary after patch upgrade, unconfigure the already configured DB2 instances and configure those again.
---------------------------------------------
On Windows machine, different agent binaries are used for different instances of DB2 server that are configured for monitoring.
Installing patch by following the steps mentioned in section 5.2 and 5.3 will replace only template agent binary and will not replace instance specific binary. So latest agent binary will not be used for monitoring.
To use latest binary after patch upgrade, unconfigure the already configured DB2 instances and configure those again.
6.2 Installation instructions for agent baroc file
-----------------------------------------------------
[This fix (7.1.6-TIV-ITM_DB2-IF0001) includes changes to the agent baroc files that must be reinstalled. [If you have already installed these baroc files, there are no additional installation steps. If not, see the version of the IBM Tivoli Monitoring Installation and Setup Guide that is appropriate for your installation. See "Installing monitoring agent baroc files on the event server" in the "Installing the IBM Tivoli Enterprise Console Event Synchronization" section for more information.
6.3 Additional information on using the "itmpatch" command
----------------------------------------------------------------------
The "itmpatch" command has the following syntax:
Usage: 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> }
-t { <patch_file_directory> | <patch_file> }
itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }
where:
-h Specifies the IBM Tivoli Monitoring installation directory.
-i Specifies the path to the directory or patch file to be installed.
-t Generates a report of the actions to be taken by the patch.
-i Specifies the path to the directory or patch file to be installed.
-t Generates a report of the actions to be taken by the patch.
For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring installation directory. On Windows systems, this path must include the drive letter.
<TEMP> represents the fully qualified directory specification where the fix is located. On Windows systems, this must include the drive letter.
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring installation directory. On Windows systems, this path must include the drive letter.
<TEMP> represents the fully qualified directory specification where the fix is located. On Windows systems, this must include the drive letter.
6.4 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 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>
> $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.
On UNIX 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>
> $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>
> %CANDLE_HOME%\bin\tacmd listSystems -t UD
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t UD
Note:
- The component (-t) for the tacmd listSystems command is specified as two characters UD, not three characters KUD.
- The component (-t) for the tacmd listSystems command is specified as two characters UD, not three characters KUD.
When the agent update is successful, the agent version is displayed as 07.16.00.01.
7.0 Known problems and workarounds
==============================
7.1 Problem: The Application Support for Db2 v716IF01 is not getting installed through GUI method on Linux platform.
Workaround: Either use silent method or SDA to install application support for Db2 v716F01 patch.
Workaround: Either use silent method or SDA to install application support for Db2 v716F01 patch.
8.0 Additional product information
===========================
None9.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.shtml10.0 Notices
===========
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 jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
registered trademarks of Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
other countries, or both.
Other company, product, or service names may be trademarks or service
marks of others.
marks of others.
Third-Party License Terms and Conditions, Notices and Information
----------------------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.
----------------------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.
Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.
Prerequisites
IBM Tivoli Composite Application Manager Agent for DB2, Version 7.1.6
Installation Instructions
Please refer to the README contained in the Description section above for general installation instructions.
Problems Solved
IJ46391
On
[{"DNLabel":"7.1.6-TIV-ITM_DB2-IF0001","DNDate":"12 Nov 2023","DNLang":"US English","DNSize":"71161 KB","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":"https://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=7.1.6-TIV-ITM_DB2-IF0001&source=SAR","DNURL_FTP":"","DDURL":null}]
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"ARM Category":[{"code":"a8m500000008b8sAAA","label":"ITCAM-for-Applications-\u003EDB2 Agent Internal"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]
Product Synonym
DB2 agent;
Problems (APARS) fixed
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
27 November 2023
UID
ibm17067974