Download
Abstract
This fix resolves the APARs and defects listed in the "Problems Fixed" section below. This fix also includes the superseded fixes listed in section 2.3.
Download Description
Copyright International Business Machines Corporation 2016.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager Agent for
DB2, Version 7.1.0
Component ID: 5724B96DO
Fix: Interim Fix 0005 (7.1.0-TIV-ITM_DB2-IF0005)
Date: September 01, 2016
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
1.0 General description
========================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.3.
2.0 Problems fixed
==================
2.1 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: 105295
Abstract: Final patch build packaged as tar.gz (GZIPPED).
Additional information: Changed the patch build package format from
.tar to .tar.gz for UNIX/LINUX environment.
Example: 7.1.0-TIV-ITM_DB2-IF0005.tar.gz
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.
2.2 Superseded fixes:
---------------------
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.3 APARs and defects included from superseded fixes
----------------------------------------------------
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.4 and 7.5 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.4 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.4 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.
Defects:
------------
Defect: 48301
Abstract: The ODI definition problem for attribute Time-zone
Displacement.
Additional Information: The data type of attribute 'Timezone
Displacement' in KUD_DB2_Diagnostic_Log attribute group,
was set as I,2 but maximum value allowed enum for it was
set as Value_Exceeds_Maximum=2147483647. This maximum
value was not matching with corresponding Type's size and
it should be set to correct value as 32767.
Defect: 56614
Abstract: Format character ^M is shown in IF1 build files.
Additional information: A lot of error messages were shown in the
agent log, reporting 'Table name <KUD4238000^M> exceeded
maximum length, truncated.'
Defect: 56617
Abstract: Agent factory parse log error.
Additional information: Agent factory was reporting the error
'Attribute Message pattern (^.*$)|MESSAGE : (.*) has a
replace with group number 2 which exceeds or equals group
count 2 in the regular expression. Ignoring group 2.'
in agent log.
Defect: 62060
Abstract: IBM Tivoli Monitoring Portal changes required for Java 6
and Java 7 security.
Additional information: Application was getting blocked because of
Java security error messages. Refer to the ITM Tech-note
about this problem:
http://www-01.ibm.com/support/docview.wss?uid=swg21659560
Defect: 61728
Abstract: Monitor standby read enabled database in the HADR
environment.
Additional information: DB2 agent customized SQL feature didn't work
on read enabled standby database in the HADR environment.
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.4 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.4 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: 25092
Abstract: Unexpected "" in product_description in ud_dd_.xml and
product_description lost from ud_dd.properties.
Additional Information: In the "ud_dd_071000000.xml" file used for
xmlConfig, double quotes were given around the title string
which was resulting showing unexpected double quotes on
title bar. And another issue was "product_description" was
not defined in the ud_dd.properties file.
Defect: 28381
Abstract: No Data appeared in the workspace Archive Log History.
Additional Information: For Suse 10 sp4 on zLinux with DB2 ESE 10.1
FP1 server, data was not appeared in the Archive log
History workspace after configuring LOGARCHMETH1
configuration parameter to DISK in database manager.
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.
Defect: 32359
Abstract: SDA install fails when the KUDv7.1 agent is installed alone.
Additional information: Add this information to the DB2 agent 7.1
Troubleshooting Guide.
Defect: 30165
Abstract: Manual DB Scripts running steps are missing in the DB2
agent v7.1 Installation and Configuration Guide.
Additional information: Add this information to the DB2 agent 7.1
Installation and Configuration Guide.
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.
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.4 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.
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
==================================
This fix is supported on all operating systems listed in the detailed
system requirements report for the DB2 V7.1 agent:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1362385527606&duComponent=Server_3887E8D0114A11E38F7D228059AF1569
See the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
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.
IBM Tivoli Composite Application Manager Agent for DB2 7.1 Software
Product Compatibility Report link:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1362385527606&duComponent=Server_3887E8D0114A11E38F7D228059AF1569
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.0-TIV-ITM_DB2-IF0005.README - This README file
- 7.1.0-TIV-ITM_DB2-IF0005.tar.gz - Fix archive .tar.gz format
- MD5:469ae63c909396ea7d0a957235c96962
- 7.1.0-TIV-ITM_DB2-IF0005.zip - Fix archive .zip format
- MD5:13ffa6affe895d80271d9b47ee9271e8
Note: The .tar.gz and .zip files are identical in content. Use the .tar.gz
file if you are working in a UNIX(R) environment; use the .zip file
if you are working in a Windows(R) environment.
The fix archive file contains the following files:
- 7.1.0-TIV-ITM_DB2-IF0005/kud_aix523_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_aix526_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_hpi116_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_li6263_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_ls3263_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_ls3266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lia266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lpp266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lx8266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol283_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol286_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol606_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_tems_teps_tepd_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_winnt_tema_if0005.cab
- 7.1.0-TIV-ITM_DB2-IF0005/kud_wix64_tema_if0005.cab
- 7.1.0-TIV-ITM_DB2-IF0005/kud_tems_teps_tepd_if0005.zip
- 7.1.0-TIV-ITM_DB2-IF0005/kudaix523.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudaix526.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudhpi116.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudli6263.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudls3263.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudls3266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlia266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlpp266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlx8266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol283.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol286.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol606.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudwinnt.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudwix64.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/inst_prepreq_patch.sh
- 7.1.0-TIV-ITM_DB2-IF0005/ud_dd_071000005.xml
- 7.1.0-TIV-ITM_DB2-IF0005/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 under 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.
Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
5.2 Local agent update
----------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_DB2-IF0005.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.
2. Expand the archive file 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.3.
On a UNIX system, if the fix is expanded to
<TEMP>/7.1.0-TIV-ITM_DB2-IF0005, use the following installation
command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.0-TIV-ITM_DB2-IF0005/kud_xxxxxx_tema_if0005.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_aix523_tema_if0005.tar.
> ./cinfo -i
Monitoring Agent for DB2
aix523 Version: 07.10.00.05
Note: There is a known upgrade problem on AIX 7.1, please refer to
point 7.2 in section 7.0 entitled "Known problems and workarounds".
On a Windows system, if the fix was expanded to
<TEMP>\7.1.0-TIV-ITM_DB2-IF0005, use the following
installation command:
For 32 bit Agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005\kud_winnt_tema_if0005.cab
For 64 bit Agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005\kud_wix64_tema_if0005.cab
5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_DB2-IF0005.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 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.0-TIV-ITM_DB2-IF0005:
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/7.1.0-TIV-ITM_DB2-IF0005
On Windows systems,
if the fix was expanded to <TEMP>\7.1.0-TIV-ITM_DB2-IF0005:
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005
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. Please 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".
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 071000005
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 071000005
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.
- There's known upgrade problem on AIX 7.1, please refer to
point 7.2 in section 7.0 "Known problems and workarounds".
5.4 Agent support update
------------------------
This fix 7.1.0-TIV-ITM_DB2-IF0005 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.0-TIV-ITM_DB2-IF0005.tar.gz
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.
2. Expand the archive file 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_if0005.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop 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" 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 above, one
of the following additional steps must be performed:
1. Acquire a platform-specific pre-packaged 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.
-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.
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: Using the silent installation option for Linux(R) and
zLinux operating systems requires the following files that are
contained in Interim Fix 6.2-TIV-ITM_ASI-IF0002:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
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:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the DB2 agent
07.10.00.05 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.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.
6.2 Installation instructions for agent baroc file
-----------------------------------------------------
[This fix (7.1.0-TIV-ITM_DB2-IF0005) 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> }
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.
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.
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.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-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.
When the agent update is successful, the agent version is
displayed as 07.10.00.05.
7.0 Known problems and workarounds
===================================
7.1 Two new column name are not globalized:
- DB2 Agent 7.1 ifix1 adds two new columns, Page Size and Table
Space Type, into the Auto Resize attribute group. In the English
language environment ,Tivoli Enterprise Portal, these two columns
might display normally. But, in other languages on the Tivoli
Enterprise Portal, these two columns are also display in English.
7.2 agent not restart after upgrading on AIX 7.1:
- Although the agent instance is running, the itmpatch cannot
restart agent instance on AIX 7.1. This affects both remote
update and local update. In patchlogs/itmpatch.log file following
lines will be logged,
TRACE 02:01:15 (patchprocessor.cpp,1252):
PatchProcessor::stopDependents() entry
TRACE 02:01:15 (itmcomponentregistry.cpp,74):
ITMComponentRegistry::getInstalledComponent entry
TRACE 02:01:15 (itmcomponentregistry.cpp,89):
ITMComponentRegistry::getInstalledComponent exit
TRACE 02:01:15 (patchprocessor.cpp,1413):
No running instances of kud found
- Workaround: Restart the agent manually and agent will function
normally.
7.3 ITM APAR IV59268:
- Remote Deploy and local installation of the KUD agent into an
IBM Tivoli Monitoring 6.30.02 and above environment fails on
AIX 6.1 and 7.1 64 bit. For more information, refer the following
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21661263
7.4 Replace failed errors in agent logs:
- There are some errors in the agent log when monitoring
db2diag.log on DB2 9.x. For example:
Replace failed for pattern [(^.*$)|NODE :
(.*)([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|DB :
(.*)([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|IMPACT :
(.*)\s([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|FUNCTION:
(.+?, .+?, .+?, probe:.*)([\s.]*.)*] using original
input string []
- These replace failed information are caused by the agent factory,
but it doesn't impact the db2diag.log monitoring.
7.5 Fix for APAR IV81552:
- To surmount memory leak issue, data collection can be diverted
to SQL query option by setting KUD_LOCKCONFLICT_BY_SQL=Y.
Refer section 2.4 for more details.
- Lock Wait Time attribute value won't be collected when user
switch to SQL query option for locking conflict attribute group.
7.6 Data not collected for 'System Resources' attribute group:
- If data is not collected for 'System Resources' attribute
group then it is necessary 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.ENV_GET_SYS_RESOURCES()
TO USER <username>
Where, <username>: for Windows – SYSTEM is default user,
for UNIX - instance owner is user.
8.0 Additional product information
===================================
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
============
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.
Microsoft, Windows, and Windows Server are trademarks of Microsoft
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.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Other company, product, or service names may be trademarks or service
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.
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:
- 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.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager Agent for
DB2, Version 7.1.0
Component ID: 5724B96DO
Fix: Interim Fix 0005 (7.1.0-TIV-ITM_DB2-IF0005)
Date: September 01, 2016
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
1.0 General description
========================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.3.
2.0 Problems fixed
==================
2.1 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: 105295
Abstract: Final patch build packaged as tar.gz (GZIPPED).
Additional information: Changed the patch build package format from
.tar to .tar.gz for UNIX/LINUX environment.
Example: 7.1.0-TIV-ITM_DB2-IF0005.tar.gz
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.
2.2 Superseded fixes:
---------------------
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.3 APARs and defects included from superseded fixes
----------------------------------------------------
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.4 and 7.5 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.4 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.4 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.
Defects:
------------
Defect: 48301
Abstract: The ODI definition problem for attribute Time-zone
Displacement.
Additional Information: The data type of attribute 'Timezone
Displacement' in KUD_DB2_Diagnostic_Log attribute group,
was set as I,2 but maximum value allowed enum for it was
set as Value_Exceeds_Maximum=2147483647. This maximum
value was not matching with corresponding Type's size and
it should be set to correct value as 32767.
Defect: 56614
Abstract: Format character ^M is shown in IF1 build files.
Additional information: A lot of error messages were shown in the
agent log, reporting 'Table name <KUD4238000^M> exceeded
maximum length, truncated.'
Defect: 56617
Abstract: Agent factory parse log error.
Additional information: Agent factory was reporting the error
'Attribute Message pattern (^.*$)|MESSAGE : (.*) has a
replace with group number 2 which exceeds or equals group
count 2 in the regular expression. Ignoring group 2.'
in agent log.
Defect: 62060
Abstract: IBM Tivoli Monitoring Portal changes required for Java 6
and Java 7 security.
Additional information: Application was getting blocked because of
Java security error messages. Refer to the ITM Tech-note
about this problem:
http://www-01.ibm.com/support/docview.wss?uid=swg21659560
Defect: 61728
Abstract: Monitor standby read enabled database in the HADR
environment.
Additional information: DB2 agent customized SQL feature didn't work
on read enabled standby database in the HADR environment.
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.4 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.4 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: 25092
Abstract: Unexpected "" in product_description in ud_dd_.xml and
product_description lost from ud_dd.properties.
Additional Information: In the "ud_dd_071000000.xml" file used for
xmlConfig, double quotes were given around the title string
which was resulting showing unexpected double quotes on
title bar. And another issue was "product_description" was
not defined in the ud_dd.properties file.
Defect: 28381
Abstract: No Data appeared in the workspace Archive Log History.
Additional Information: For Suse 10 sp4 on zLinux with DB2 ESE 10.1
FP1 server, data was not appeared in the Archive log
History workspace after configuring LOGARCHMETH1
configuration parameter to DISK in database manager.
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.
Defect: 32359
Abstract: SDA install fails when the KUDv7.1 agent is installed alone.
Additional information: Add this information to the DB2 agent 7.1
Troubleshooting Guide.
Defect: 30165
Abstract: Manual DB Scripts running steps are missing in the DB2
agent v7.1 Installation and Configuration Guide.
Additional information: Add this information to the DB2 agent 7.1
Installation and Configuration Guide.
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.
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.4 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.
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
==================================
This fix is supported on all operating systems listed in the detailed
system requirements report for the DB2 V7.1 agent:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1362385527606&duComponent=Server_3887E8D0114A11E38F7D228059AF1569
See the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
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.
IBM Tivoli Composite Application Manager Agent for DB2 7.1 Software
Product Compatibility Report link:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1362385527606&duComponent=Server_3887E8D0114A11E38F7D228059AF1569
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.0-TIV-ITM_DB2-IF0005.README - This README file
- 7.1.0-TIV-ITM_DB2-IF0005.tar.gz - Fix archive .tar.gz format
- MD5:469ae63c909396ea7d0a957235c96962
- 7.1.0-TIV-ITM_DB2-IF0005.zip - Fix archive .zip format
- MD5:13ffa6affe895d80271d9b47ee9271e8
Note: The .tar.gz and .zip files are identical in content. Use the .tar.gz
file if you are working in a UNIX(R) environment; use the .zip file
if you are working in a Windows(R) environment.
The fix archive file contains the following files:
- 7.1.0-TIV-ITM_DB2-IF0005/kud_aix523_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_aix526_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_hpi116_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_li6263_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_ls3263_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_ls3266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lia266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lpp266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_lx8266_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol283_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol286_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_sol606_tema_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_tems_teps_tepd_if0005.tar
- 7.1.0-TIV-ITM_DB2-IF0005/kud_winnt_tema_if0005.cab
- 7.1.0-TIV-ITM_DB2-IF0005/kud_wix64_tema_if0005.cab
- 7.1.0-TIV-ITM_DB2-IF0005/kud_tems_teps_tepd_if0005.zip
- 7.1.0-TIV-ITM_DB2-IF0005/kudaix523.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudaix526.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudhpi116.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudli6263.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudls3263.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudls3266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlia266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlpp266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudlx8266.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol283.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol286.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudsol606.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudwinnt.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/kudwix64.dsc
- 7.1.0-TIV-ITM_DB2-IF0005/inst_prepreq_patch.sh
- 7.1.0-TIV-ITM_DB2-IF0005/ud_dd_071000005.xml
- 7.1.0-TIV-ITM_DB2-IF0005/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 under 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.
Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
5.2 Local agent update
----------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_DB2-IF0005.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.
2. Expand the archive file 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.3.
On a UNIX system, if the fix is expanded to
<TEMP>/7.1.0-TIV-ITM_DB2-IF0005, use the following installation
command:
> itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.0-TIV-ITM_DB2-IF0005/kud_xxxxxx_tema_if0005.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_aix523_tema_if0005.tar.
> ./cinfo -i
Monitoring Agent for DB2
aix523 Version: 07.10.00.05
Note: There is a known upgrade problem on AIX 7.1, please refer to
point 7.2 in section 7.0 entitled "Known problems and workarounds".
On a Windows system, if the fix was expanded to
<TEMP>\7.1.0-TIV-ITM_DB2-IF0005, use the following
installation command:
For 32 bit Agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005\kud_winnt_tema_if0005.cab
For 64 bit Agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005\kud_wix64_tema_if0005.cab
5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_DB2-IF0005.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 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.0-TIV-ITM_DB2-IF0005:
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/7.1.0-TIV-ITM_DB2-IF0005
On Windows systems,
if the fix was expanded to <TEMP>\7.1.0-TIV-ITM_DB2-IF0005:
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\7.1.0-TIV-ITM_DB2-IF0005
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. Please 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".
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 071000005
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 071000005
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.
- There's known upgrade problem on AIX 7.1, please refer to
point 7.2 in section 7.0 "Known problems and workarounds".
5.4 Agent support update
------------------------
This fix 7.1.0-TIV-ITM_DB2-IF0005 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.0-TIV-ITM_DB2-IF0005.tar.gz
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.
2. Expand the archive file 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_if0005.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop 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" 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 above, one
of the following additional steps must be performed:
1. Acquire a platform-specific pre-packaged 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.
-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.
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: Using the silent installation option for Linux(R) and
zLinux operating systems requires the following files that are
contained in Interim Fix 6.2-TIV-ITM_ASI-IF0002:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
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:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the DB2 agent
07.10.00.05 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.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.
6.2 Installation instructions for agent baroc file
-----------------------------------------------------
[This fix (7.1.0-TIV-ITM_DB2-IF0005) 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> }
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.
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.
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.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-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.
When the agent update is successful, the agent version is
displayed as 07.10.00.05.
7.0 Known problems and workarounds
===================================
7.1 Two new column name are not globalized:
- DB2 Agent 7.1 ifix1 adds two new columns, Page Size and Table
Space Type, into the Auto Resize attribute group. In the English
language environment ,Tivoli Enterprise Portal, these two columns
might display normally. But, in other languages on the Tivoli
Enterprise Portal, these two columns are also display in English.
7.2 agent not restart after upgrading on AIX 7.1:
- Although the agent instance is running, the itmpatch cannot
restart agent instance on AIX 7.1. This affects both remote
update and local update. In patchlogs/itmpatch.log file following
lines will be logged,
TRACE 02:01:15 (patchprocessor.cpp,1252):
PatchProcessor::stopDependents() entry
TRACE 02:01:15 (itmcomponentregistry.cpp,74):
ITMComponentRegistry::getInstalledComponent entry
TRACE 02:01:15 (itmcomponentregistry.cpp,89):
ITMComponentRegistry::getInstalledComponent exit
TRACE 02:01:15 (patchprocessor.cpp,1413):
No running instances of kud found
- Workaround: Restart the agent manually and agent will function
normally.
7.3 ITM APAR IV59268:
- Remote Deploy and local installation of the KUD agent into an
IBM Tivoli Monitoring 6.30.02 and above environment fails on
AIX 6.1 and 7.1 64 bit. For more information, refer the following
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21661263
7.4 Replace failed errors in agent logs:
- There are some errors in the agent log when monitoring
db2diag.log on DB2 9.x. For example:
Replace failed for pattern [(^.*$)|NODE :
(.*)([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|DB :
(.*)([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|IMPACT :
(.*)\s([\s.]*.)*] using original input string []
Replace failed for pattern [(^.*$)|FUNCTION:
(.+?, .+?, .+?, probe:.*)([\s.]*.)*] using original
input string []
- These replace failed information are caused by the agent factory,
but it doesn't impact the db2diag.log monitoring.
7.5 Fix for APAR IV81552:
- To surmount memory leak issue, data collection can be diverted
to SQL query option by setting KUD_LOCKCONFLICT_BY_SQL=Y.
Refer section 2.4 for more details.
- Lock Wait Time attribute value won't be collected when user
switch to SQL query option for locking conflict attribute group.
7.6 Data not collected for 'System Resources' attribute group:
- If data is not collected for 'System Resources' attribute
group then it is necessary 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.ENV_GET_SYS_RESOURCES()
TO USER <username>
Where, <username>: for Windows – SYSTEM is default user,
for UNIX - instance owner is user.
8.0 Additional product information
===================================
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
============
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.
Microsoft, Windows, and Windows Server are trademarks of Microsoft
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.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Other company, product, or service names may be trademarks or service
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.
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:
- 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.
Prerequisites
IBM Tivoli Composite Application Manager Agent for DB2, Version 7.1
IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 or above
IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 or above
Installation Instructions
Please refer to the README contained in the Description section above for general installation instructions.
On
[{"DNLabel":"7.1.0-TIV-ITM_DB2-IF0005","DNDate":"01-Sep-16","DNLang":"US English","DNSize":"158240209","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":"http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=Tivoli%2BComposite%2BApplication%2BManager&product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.1.0-TIV-ITM_DB2-IF0005","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"ITCAM Agent for DB2 - 5724B96DO","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Product Synonym
DB2 agent
Was this topic helpful?
Document Information
Modified date:
01 March 2019
UID
swg24042674