Fix Readme
Abstract
Readme document for 7.1.3-TIV-ITM_DB2-FP0000 release.
Content
(C) Copyright International Business Machines Corporation 2020.
All rights reserved.
All rights reserved.
Component:
Component: IBM(R) Tivoli(R) Composite Application Manager for
Applications V7.2.1.2: Tivoli(R) Composite Application Manager Agent
for DB2 07.13.00.00
Applications V7.2.1.2: Tivoli(R) Composite Application Manager Agent
for DB2 07.13.00.00
Component ID:
5724B96DO
Date:
June 26, 2020
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
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 provides enhancements listed in the "Problems Fixed" section below.
This fix also includes the superseded fixes listed in section 2.3.
You can download the IBM Tivoli Composite Application Manager Agent for
DB2 07.13.00.00 file from IBM Passport Advantage website using part number CC6UTML.
DB2 07.13.00.00 file from IBM Passport Advantage website using part number CC6UTML.
When this image file is downloaded from the IBM Software Support Web site
or from Passport Advantage, following rules apply:
or from Passport Advantage, following rules apply:
- You can install this image file locally on a system that already hosts a licensed copy of IBM Tivoli Monitoring for Databases.
- You can install this image file locally 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 deploy agents remotely to the existing or new installations.
2.0 Problems fixed
===============
2.1 Enhancements:
-----------------
2.1.1 Currency support for new versions of OS platforms
---------------------------------------------------
Added currency support for following platforms :
- Windows Server 2019
- RHEL 8.x x86-64
- RHEL 8.x zLinux
- SLES 15 x86-64
- SLES 15 pLinux
- SLES 15 zLinux
- Ubuntu 18.04 zLinux
2.1.2 Support for new DB2 server
---------------------------------------------------
Added support for DB2 server 11.5.
2.2 Superseded fixes:
---------------------
7.1.2-TIV-ITM_DB2-IF0002
7.1.2-TIV-ITM_DB2-IF0001
2.3 APARs and defects included from superseded fixes
----------------------------------------------------
7.1.2-TIV-ITM_DB2-IF0002
------------------------
APARs:
----------
APAR: IJ22068
2.3 APARs and defects included from superseded fixes
----------------------------------------------------
7.1.2-TIV-ITM_DB2-IF0002
------------------------
APARs:
----------
APAR: IJ22068
Abstract: On some Unix based platforms DB2 agent goes down after couple of hours.
Additional Information: After the UD agent is started, it works normally with expected
KPIs showed on TEPS. After a few hours, the agent goes down and the portal appears in gray.
It does not report data with cinfo command that the process not running. Due to
unlocking of a free resource, this issue on some Unix based platforms. This is
fixed in the APAR.
Defects:
--------
Defect:140761
Abstract: On Unix/Linux platform, ensure that the filepath to db2set is set correctly.
Defect:140944
Abstract: Improve logging when getting the connectable databases.
7.1.2-TIV-ITM_DB2-IF0001
------------------------
APARs:
----------
APAR:IJ03816
Abstract: ITCAM Agent for DB2 shipped with certificates in 'kud_resources.jar'
that are signed with unsupported MD5 algorithm. JAR files signed with MD5
algorithms were treated as unsigned JARs due to java security change
KPIs showed on TEPS. After a few hours, the agent goes down and the portal appears in gray.
It does not report data with cinfo command that the process not running. Due to
unlocking of a free resource, this issue on some Unix based platforms. This is
fixed in the APAR.
Defects:
--------
Defect:140761
Abstract: On Unix/Linux platform, ensure that the filepath to db2set is set correctly.
Defect:140944
Abstract: Improve logging when getting the connectable databases.
7.1.2-TIV-ITM_DB2-IF0001
------------------------
APARs:
----------
APAR:IJ03816
Abstract: ITCAM Agent for DB2 shipped with certificates in 'kud_resources.jar'
that are signed with unsupported MD5 algorithm. JAR files signed with MD5
algorithms were treated as unsigned JARs due to java security change
Additional Information: The file is signed with JAVA version 8 or 9
that used SHA256 signature algorithm for signing.
that used SHA256 signature algorithm for signing.
Defects:
---------------------
Defect:136586
Abstract: DB2 agent logs showed repeated error message "Trying to open
SQL Connection with NULL user", while creating the SQL connection agent
using uninitialized database name string for the data collection of
attribute groups.
---------------------
Defect:136586
Abstract: DB2 agent logs showed repeated error message "Trying to open
SQL Connection with NULL user", while creating the SQL connection agent
using uninitialized database name string for the data collection of
attribute groups.
Additional Information: Fixed at code level to initialize the database
name before processing.
Defect:136291
Abstract: ITCAM Agent for DB2 agent incorrectly interpreted ROS as enabled
when DB2_HADR_ROS is set to ON, and interpreted ROS as disabled for all other values.
name before processing.
Defect:136291
Abstract: ITCAM Agent for DB2 agent incorrectly interpreted ROS as enabled
when DB2_HADR_ROS is set to ON, and interpreted ROS as disabled for all other values.
Additional Information: ROS is enabled when DB2_HADR_ROS parameter is set
to ‘ON’ / ‘YES’ / ‘Y’ / ‘TRUE‘ / ‘1’. ROS is disabled when DB2_HADR_ROS
parameter is set to ‘OFF’ / ‘NO’ / ‘FALSE’ / ‘N’ / ‘0’ or is not set.
Enhancements:
---------------------
RFE 125878: Allow user to disable Active Connections monitoring in Databases Status.
----------------------------------------------------------------------------------------
In ITCAM Agent for DB2 agent, to monitor healthy databases having zero active connections,
a new database state is defined as "Stopped". The database with at least one active connection
is considered as "Active".
The following predefined situations are deprecated in this patch release.
- UDB_DB_Status_Warn.
- UDB_DB_Cat_Cache_Hit_Rat_Crit.
- UDB_DB_BP_Hit_Ratio_Low.
The following new predefined situations are introduced in this patch release:
New predefined situations:
- UDB_DB_Status_Warn_2
Declares a warning condition when the monitored database is not
in active status.
- UDB_DB_Cat_Cache_Hit_Rat_Crit_3
Declares a critical condition when Pct catalog cache hit ratio
drops below the critical threshold or cat cache hit ratio is between
0 to 80 percent.
to ‘ON’ / ‘YES’ / ‘Y’ / ‘TRUE‘ / ‘1’. ROS is disabled when DB2_HADR_ROS
parameter is set to ‘OFF’ / ‘NO’ / ‘FALSE’ / ‘N’ / ‘0’ or is not set.
Enhancements:
---------------------
RFE 125878: Allow user to disable Active Connections monitoring in Databases Status.
----------------------------------------------------------------------------------------
In ITCAM Agent for DB2 agent, to monitor healthy databases having zero active connections,
a new database state is defined as "Stopped". The database with at least one active connection
is considered as "Active".
The following predefined situations are deprecated in this patch release.
- UDB_DB_Status_Warn.
- UDB_DB_Cat_Cache_Hit_Rat_Crit.
- UDB_DB_BP_Hit_Ratio_Low.
The following new predefined situations are introduced in this patch release:
New predefined situations:
- UDB_DB_Status_Warn_2
Declares a warning condition when the monitored database is not
in active status.
- UDB_DB_Cat_Cache_Hit_Rat_Crit_3
Declares a critical condition when Pct catalog cache hit ratio
drops below the critical threshold or cat cache hit ratio is between
0 to 80 percent.
- UDB_DB_BP_Hit_Ratio_Low_3
Declares a warning condition when Buffer pool hit ratio is low or
Buffer pool hit ratio is between 0 to 65 percent.
Declares a warning condition when Buffer pool hit ratio is low or
Buffer pool hit ratio is between 0 to 65 percent.
3.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
3.1 Prerequisites for this fix
-----------------------------
None.
4.0 Image directory contents
=============================
Electronic Part Number: ITCAM Apps Ag for DB2 CC6UTML
This fix image contains the following files and directories:
AUTORUN.INF [Deploy] DeployLnk.sh
[InstallITM] README.TXT [db2-agent]
[WINDOWS] install.sh kcirunas.cfg
[license] non_ibm_license notices
silent_config.txt silent_install.txt [unix]
[REPORTS] smai-db2-07.13.00.00-win-x86_64.zip
AUTORUN.INF [Deploy] DeployLnk.sh
[InstallITM] README.TXT [db2-agent]
[WINDOWS] install.sh kcirunas.cfg
[license] non_ibm_license notices
silent_config.txt silent_install.txt [unix]
[REPORTS] smai-db2-07.13.00.00-win-x86_64.zip
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].
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].
5.0 Installation instructions
==============================
When this image file is downloaded from the IBM Software Support Web
site or from Passport Advantage, these rules apply:
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 "Prerequisites
for this fix" must be installed.
-----------------------------
- The prerequisites listed under section 3.1 entitled "Prerequisites
for this fix" must be installed.
- 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/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.
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on Unix/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.
5.2 Local agent install and update (including silent installation)
--------------------------------------------------------------
1. Transfer the appropriate archive file (CC6UTML.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.
--------------------------------------------------------------
1. Transfer the appropriate archive file (CC6UTML.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.
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.
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
----------------------------------------
1. Transfer the appropriate archive file (CC6UTML.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.
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."
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>/CC6UTML:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CC6UTML/WINDOWS/Deploy -t ud -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CC6UTML/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
<TEMP>/CC6UTML:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CC6UTML/WINDOWS/Deploy -t ud -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CC6UTML/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>/CC6UTML:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CC6UTML\WINDOWS\Deploy -t ud -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CC6UTML\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
<TEMP>/CC6UTML:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CC6UTML\WINDOWS\Deploy -t ud -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CC6UTML\unix -t ud -f
where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case ud
represents the Monitoring Agent for DB2
-f performs the actions without asking for confirmation
4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information on the
tacmd login and updateAgent commands, see Appendix A. Command
reference of the "IBM Tivoli Monitoring Administrator's Guide."
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information on the
tacmd login and updateAgent commands, see Appendix A. Command
reference of the "IBM Tivoli Monitoring Administrator's Guide."
On a UNIX system:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems
The output shows the managed system name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.
> $CANDLEHOME/bin/tacmd updateAgent -t ud
-n <Managed system name>
-v 071300000
> $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 071300000
On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %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 071300000
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.
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 071300000
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.
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.
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.
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}.
{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 (CC6UTML.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.
On Unix/Linux systems,
> tar -xvf CC6UTML.tar.gz
This step creates a directory structure that contains fixes for all of the
supported platforms.
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.
On Unix/Linux systems,
> tar -xvf CC6UTML.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."
Installation and Setup Guide."
4. Use the procedures in the specific database monitoring agent user's
guide to complete the installation and configuration.
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.
(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"
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.
----------------------------
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.
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 .
-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 .
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.13.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.
- 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:
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.
*********** Thu Jun 25 07:46:23 EDT 2020 ******************
User: root Groups: root
Host name : misae Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/FinalBuild_713/ITM
***********************************************************
...Product inventory
This command offers you four options on the CINFO menu shown in
the example that follows. Choose the option that meets your needs.
*********** Thu Jun 25 07:46:23 EDT 2020 ******************
User: root Groups: root
Host name : misae Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/FinalBuild_713/ITM
***********************************************************
...Product inventory
ax IBM Tivoli Monitoring Shared Libraries
lpl266 Version: 06.30.07.00
lpl266 Version: 06.30.07.00
gs IBM GSKit Security Interface
lpl266 Version: 08.00.50.69
lpl266 Version: 08.00.50.69
jr Tivoli Enterprise-supplied JRE
lpl266 Version: 07.09.50.00
lpl266 Version: 07.09.50.00
ud IBM Tivoli Composite Application Manager Agent for DB2
lpl266 Version: 07.13.00.00
lpl266 Version: 07.13.00.00
ue Tivoli Enterprise Services User Interface Extensions
lpl266 Version: 06.30.07.00
lpl266 Version: 06.30.07.00
ui Tivoli Enterprise Services User Interface
lpl266 Version: 06.30.07.00
lpl266 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.13.00.00 Build: 01741
WIX64 Version: 07.13.00.00 Build: 01741
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
WINNT Version: 06.30.07.00 Build: 201612161149
7.0 Known problems and workarounds
===================================
===================================
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 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: 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
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 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: 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: DB2 agent prerequiste fails on Suse 15 SP1 zLinux platform
Workaround: By skipping prerequiste check DB2 agent can install/config.
Problem: When DB2 07.11.00.00 agent is pointed to ITM setup having DB2 07.13.00.00 support,
HADR details workspace shows no data on UI.
Workaround: Upgrade DB2 agent from 07.11.00.00 to 07.13.00.00.
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: DB2 agent prerequiste fails on Suse 15 SP1 zLinux platform
Workaround: By skipping prerequiste check DB2 agent can install/config.
Problem: When DB2 07.11.00.00 agent is pointed to ITM setup having DB2 07.13.00.00 support,
HADR details workspace shows no data on UI.
Workaround: Upgrade DB2 agent from 07.11.00.00 to 07.13.00.00.
Problem: When adding bundles for all Unix/Linux platforms in DB2 07.13.00.00, prerequisite action
fails for HP-UX platform (hpi116) platform.
Workaround: Use tacmd addBundles command with -n.
For example, all platforms use: tacmd addBundles -n -i <Installer>\unix -t ud
Problem: The command tacmd addBundles fails for Windows platform in DB2 07.13.00.00 with 'File not
found error' for the file AC_Silent_Install.txt
Workaround: Change the name of AC_Silent_Install.txt file to ACX64_Silent_Install.txt in
<Installer>\WINDOWS\Deploy\KACWIX64.dsc file.
8.0 Additional product information
===================================
None.
===================================
None.
9.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.
10.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.
------------------------------------
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
IBM Tivoli Composite Application Manager Agent for DB2 07.13.00.00 can be downloaded from IBM Passport Advantage website using part number CC6UTML.
IBM Tivoli Composite Application Manager for Applications V7.2.1.2 : IBM Tivoli Composite Application Manager Agent for DB2 v7.1.3, Multiplatform, Multilingual (CC6UTML)
Product Synonym
UD
KUD
DB2 Agent
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
27 July 2021
UID
ibm16243016