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

Download Description

(C) Copyright International Business Machines Corporation 2017.
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.11.00.00

Component ID: 5724B96D0

Date: 8 December, 2017

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.5. This fix pack contains only updates for the
Monitoring Agent for DB2.

You can download the IBM Tivoli Composite Application Manager Agent for
DB2 07.11.00.00 files 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 fix pack image is downloaded from the IBM Software Support Web site
or from Passport Advantage, these rules apply:
* You can locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases.
* You can locally install the fix pack 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 : 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.

2.2 Defects
-----------
Defect : 125974
Abstract : DB2 server 9.1 out of support.
Additional Information : DB2 Agent no longer supports DB2 server 9.1.

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.4 for more details
about KUD_CONNECT_TO_STANDBYDB variable.

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.


2.3 Enhancements:
-----------------
2.3.1 Added new attributes, Table Name (New Unicode) and
Table Schema (New Unicode), in DB2 Table, DB2 Application00 and
DB2 Locking Conflict attribute groups.
---------------------------------------------------
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.


2.3.2 RFE 87986 : ITCAM for DB2 should have default view that shows
long running SQL queries.
---------------------------------------------------
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 behaviour
can be changed using KUD_TOP_RUNNING_SQL and KUD_SQL_ORDERBY
environment variables.
Refer section 2.4 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.4 for more details about environment variables.

2.3.3 Currency support for new versions of OS platforms
---------------------------------------------------
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

2.3.4 Support for new OS platforms:
---------------------------------------------------
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 ].

2.3.5 Improvement in DB2_Table attribute group data collection algorithm.
---------------------------------------------------
The source SQL queries used for data collection of
DB2_Table attribute group are optimized to improve
data collection time.

2.3.6 Introducing a way to set time-out value for SQL query execution:
-----------------------------------------------------
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.4 for more details about environment variable.

2.3.7 Providing support for data collection from all partitions:
-----------------------------------------------------
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.4 for more details about environment variable.

2.4 Additional Settings :
-----------------------
Environment Variables:
-----------------
Support for following environmental variables is included in this
release. 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


2.5 Superseded fixes:
---------------------
IBM Tivoli Composite Application Manager Agent for DB2.
7.1.0-TIV-ITM_DB2-IF0005
7.1.0-TIV-ITM_DB2-IF0004
7.1.0-TIV-ITM_DB2-IF0003
7.1.0-TIV-ITM_DB2-IF0002
7.1.0-TIV-ITM_DB2-IF0001


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

7.1.0-TIV-ITM_DB2-IF0005
------------------------
Defects:
---------------------
Defect: 105043
Abstract: UD agent should provide currency support for DB2 server
11.1 version.
Additional information: Added tolerance support for DB2 server v11.1
in UD agent.

Defect: 105994
Abstract: Updating dummy value for attribute group KUDINFO00 and
KUDSYSINFO.
Additional information: Data collection failure for attribute groups
KUDINFO00 and KUDSYSINFO was resulting in sending default
value as 0 for all numeric attributes. As 0 could be valid
value in some cases, this was creating confusion for user.
Updated default values for all numeric attributes from
0 to -4 ( Not Applicable ).

Defect: 105996
Abstract: UD agent generates multiple unexpected alert for
situation 'UDB_Agent_DB_Standby.
Additional information: While executing any SQL query, agent was
trying to find the connectable database name by checking
the roles of all the databases present on the DB2 server.
And for each database having role standby, it was sending
an event. This event was resulting in triggering many
unexpected alert for situation 'UDB_Agent_DB_Standby' in
customer environment.


7.1.0-TIV-ITM_DB2-IF0004
-------------------
APARs:
----------
APAR: IV81552
Abstract: Memory leak in KUD DB2 agent on AIX platform, when
Historical Data Collection is enabled on DB2 Locking
Conflict attribute group.
Additional Information: The data collection for Locking Conflict
attribute group was done using DB2 snapshot method. This
DB2 method was causing memory leak internally when called
to get relevant locking conflict data. To avoid this leak,
another data collection method by using SQL query is
implemented. This new data collection way can
be used by setting environmental variable
KUD_LOCKCONFLICT_BY_SQL. Refer section 2.7 for
more details.

APAR: IV83419
Abstract: DB monitoring agent fails to report any read activity.
Additional Information: DB2 agent was not able to collect data for
'System Resources' attribute group when any read request
arrives during TCR reporting.

APAR: IV82595
Abstract: Logsecond value is shown as 65535 in TEPS, if set
-1(infinite) in DB2.
Additional Information: DB2 agent was not able to collect correct
data for attributes like 'Log Second', 'Total Log Used Pct'
,'Total Log Available' after setting value of Log second
as -1(infinite).

APAR: IV85375
Abstract: kud_kcj.sql is missing the updates for the KFWTMPLST.
Additional Information: In the kud_kcj.sql file, entry for
'Customized SQLs' navigator item was not added in
KFWTMPLSTA table. So, even after stopping the DB2 agent,
the 'Customized SQLs' navigator item was not getting
greyed out on TEP.

7.1.0-TIV-ITM_DB2-IF0003
-------------------
APARs:
----------
APAR: IV73496
Abstract: TBSP_Utilization is calculated for SMS table space.
Additional Information: IN DB2 agent, TBSP_utilization was getting
calculated for the SMS table space. As per the description
of TBSP_utilization present in DB2 server user guide, it
should be only available for DMS table space.
TBSP_utilization will have some value for SMS table space
only if the monitor switch of the buffer pool is enabled.
Otherwise it will be 0.

APAR: IV09403
Abstract: Connect HADR standby database failed info generated in
agent logs.
Additional Information: DB2 agent was trying to connect the HADR
standby database, resulted in logging many error messages
like 'Connections are not allowed on a standby database'
or 'The command is not supported on an HADR standby
database' in log file.

APAR: IV72172
Abstract: Agent attach instance failed if first partition node
number is not 0.
Additional Information: DB2 agent failed to connect to DB2 instance
with error message 'node 0 is not specified in
db2nodes.cfg', when DB2 partition number start value was
changed from 0 to 1.

APAR: IV78347
Abstract: Fix for failing ASN queries for database 01, database 01
(superseded) attribute groups.
Additional information: DB2 agent was firing ASN queries on server
irrespective of their presence. This was resulting in
failure of query execution. The execution of ASN queries
can be avoided by setting environmental variable
KUD_REPLICATION_ON. Refer section 2.7 for more details.

APAR: IV78644
Abstract: Errors in DB2 agent log for db2nodes.cfg when wrong
DFTDBPATH is specified.
Additional information: DB2 agent was reporting
'File not found error' error for db2nodes.cfg file when
DB2 manager DFTDBPATH parameter didn't point to the DB2
instance home path.

APAR: IV78019
Abstract: DB2 agent passport advantage part incorrect.
Additional information: Customer could not find passport advantage
part number for ITCAM DB2 monitoring agent. The part
number for ITCAM monitoring agent for DB2 database has
been refreshed to include the fix for APAR. The part
number is CIN1CML; and it is included in eAssembly
CRKT6ML.

Defects:
---------------------
Defect: 88000
Abstract: About the ITM630 FP6 Java Cert Refresh for DB2 Agent
Additional information: Refreshed Java certification used by DB2
agent.

Enhancements:
---------------------
RFE 74725
Abstract: DB2 diagnostics log monitoring alternate (SQL Query result)
for DB2 9.x or below.
Additional information: The diagnostics logs were getting monitored
only by parsing the physical file db2diag.log. An
alternative way for monitoring diagnostics logs is
available by using SQL queries which is comparatively fast
and easy to use. This alternative method can be used by
setting environmental variable KUD_DIAGLOG_BY_TABLE. Refer
section 2.7 for more details.



7.1.0-TIV-ITM_DB2-IF0002
-------------------
APARs:
-------------
APAR: IV59674
Abstract: Current Secondary Log Used Percent value calculates
incorrectly.
Additional Information: Current Secondary Log Used Percent value is
a ratio of Current secondary log used and Log Second.
This value was reported as 100% when Log Second was
set to 0.

APAR: IV60628
Abstract: Application Support mismatch error on TEP client.
Additional Information: After installing the DB2 agent 7.1 IF1
application support (either using SDA or installing
manually), a support mismatch was reported in the TEP
client with the warning message 'An application support
version mismatch detected'.

APAR: IV65093
Abstract: TBSP_Name of Auto-resize attribute group is missing the
Primary key in the ODI file.
Additional Information: While displaying the data of Auto-resize
attribute group using plot chart, if attributes across
multiple rows are selected then data was not displayed
by the table space name because tbsp_name attribute was
not marked as primary key in ODI file.

APAR: IV64946
Abstract: Agent is down when calling the DB2 API db2CfgGet.
Additional Information: Core dump was generated by DB2 agent after
calling db2CfgCall API.

APAR: IV64960
Abstract: Agent does not stop normally.
Additional Information: Failure while calling IRA_Shutdown(1)
function through agent resulted in abnormal termination of
agent with error message, 'Product ud was not stopped. You
can use /opt/IBM/ITM/bin/itmcmd agent stop command with
option -f to force the stop product ud'.

APAR IV68158
Abstract: DB2 instance monitoring situation false alerts sometimes.
Additional Information: False alert was generated by the DB2 instance
status monitoring situation resulted in creating confusion
for DBAs.

Enhancements:
-----------------
RFE 56278
Abstract: Write Suspend database status monitoring.
Additional information: When the database was placed in the write
suspend mode, the database status was shown as 'Inactive'
in the TEP. This enhancement was opened for V10.x. To have
this enhancement working, agent start user should have an
execute authority for table function
SYSPROC.MON_GET_TABLESPACE.

RFE: 45849
Abstract: Prevent errors for the CF node in the db2diag.log in DB2
pureScale.
Additional information: DB2 agent was monitoring the CF node in the
same way as normal node. This was resulting in logging
errors in db2diag.log files like, 'SQL1610N The Database
System Monitor input parameter "" is invalid' and
'ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt invalid
size" DIA8563C An invalid memory size was requested'.
To fix this issue new environmental variable
DB2_CF_PARTITION_NUMS variable is introduced. Refer section
2.7 for more details.


7.1.0-TIV-ITM_DB2-IF0001
-------------------
APARs:
-------------
APAR: IV23334
Abstract: Improve the agent performance to monitor the multi
partition database.
Additional Information: Agent was connecting to the instance
separately for each partition. So it was connecting to the
instance as many times as the number of partitions which
was resulting in performance issue. This issue is fixed by
changing data collection method to SQL query. This new
method can be used by setting environmental variable
KUD_T1_BY_SQL. Refer section 2.7 for more details.

APAR: IV38612
Abstract: Attributes 'USING AUTO STORAGE' and 'USED DISK PCT' values
are incorrect.
Additional Information: The values for 'use auto storage' was shown
as not collected instead of Y or N. And value for
'used disk pct' was shown as not collected or N/A instead
of actual disk usage percentage. To monitor the table
space, it is recommended to use 'TBSP_Utilization' instead
of using 'USED DISK PCT'.

APAR: IV42319
Abstract: DB2 agent crashes frequently.
Additional Information: While monitoring DB2 v9.7 FP7, DB2 agent was
getting crashed because of failure during parsing the data
for lock conflict attribute group.

APAR: IV46209
Abstract: DB2 agent fails when MSGID filter is set to *
Additional Information: This problem has been observed on Linux and
Windows platform, when agent was configured to monitor
db2diag.log and KUD_DIAGLOG_MSGID_FILTER=*.

Defects:
---------------------
Defect: 32773
Abstract: Memory leak in long run on Windows 2008 when monitor
DB2 10.1 FP2
Additional information: This problem was related to DB2 APAR IC92173,
which was fixed in DB2 10.1 FP3.

Defect: 28575
Abstract: Failed to stop agent by using the GUI mode.
Additional Information: After installing package
6.2.3.1-TIV-ITM-IP0001-IV29900 for DB2 Agent 7.1, agent was
getting configured and started without any issue from GUI
but while stopping agent, it was getting failed with error
'KCIN1165E cannot execute IBM Tivoli composite Application
Manager Agent for DB2 stop script'. However agent was
stopped with any issue by using 'stopagent' from ITM
machine, and "itmcmd agent -o db2inst1 stop ud" command
from local machine

Enhancements:
-----------------
RFE: 33271
Abstract: Add 'Page Size' and 'Tablespace Type' attributes into
Tablespace Auto-Resize attribute group
Additional information: Two new attributes , new query on TEP and a
new situation are added to monitor the 'Page Size' and
'Tablespace Type'. DB2 agent doesn't collect historical
data on these two new attributes. After upgrading, the
historical data could display the new attribute columns,
but without any data. So, 'null' or '0' in page size and
blank in tablespace type are valid.

RFE: 36594
Abstract: Dump DB2 snapshot buffer to a binary log file for analyze.
Additional information: Following two configuration variables are
added to analyze the DB2 server snapshot command output.
KUD_SNAPSHOT_DUMPOUT:
By default, its value is N.
After executing DB2 corresponding snapshot command,
if problems occurred such as no data on TEP or an agent
core dump occurred in a workspace, set
KUD_SNAPSHOT_DUMPOUT=Y and restart the agent. Navigate
to the problematic workspace or refresh the workspace.
As a result, a file named
[instance_name] SNAPSHOT_DUMPOUT is created in the log
directory. Send the file to IBM Support for further
analysis.
KUD_SNAPSHOT_READIN:
By default, its value is N.
The IBM Support team can set the parameter to Y to
analyze {instance_name] SNAPSHOT_DUMPOUT for DB2 agent.
Copy the {instance_name] SNAPSHOT_DUMPOUT file to local
environment and change the name to
[instance_name]_SNAPSHOT_READIN. Then, navigate to your
problematic workspace where data is displayed on the
Tivoli Enterprise Portal. This information helps the
Support team to recreate your problem.
It is better to refresh the problematic workspace or
attribute group on the TEP only once to dump the binary
snapshot buffer. This will avoid an file overwrite.


2.7 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_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 CNN24ML

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 fix pack image is downloaded from the IBM Software Support Web
site or from Passport Advantage, these rules apply:

* You can locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases.
* You can locally install the fix pack 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 (CNN24ML.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 (CNN24ML.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 fix pack 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>/CNN24ML:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN24ML/WINDOWS/Deploy -t ud -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN24ML/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>/CNN24ML:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNN24ML\WINDOWS\Deploy -t ud -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNN24ML\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 071100000

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 071100000

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 (CNN24ML.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.11.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 Nov 14 16:44:01 IST 2017 ******************
User: db2hadr2 Groups: db2iadm1
Host name : pts00606-vm16 Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/ITM
***********************************************************

-- CINFO Menu --
1) Show products installed in this CandleHome
2) Show which products are currently running
3) Show configuration settings
4) Exit CINFO
1

*********** Tue Nov 14 16:44:47 IST 2017 ******************
User: db2hadr2 Groups: db2iadm1
Host name : pts00606-vm16 Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory

ax IBM Tivoli Monitoring Shared Libraries
lpl266 Version: 06.30.07.00

gs IBM GSKit Security Interface
lpl266 Version: 08.00.50.69

jr Tivoli Enterprise-supplied JRE
lpl266 Version: 07.09.50.00

ud IBM Tivoli Composite Application Manager Agent for DB2
lpl266 Version: 07.11.00.00

ue Tivoli Enterprise Services User Interface Extensions
lpl266 Version: 06.30.07.00

ui Tivoli Enterprise Services User Interface
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.11.00.00 Build: 72991

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