ITCAM Agent for DB2: 6.2.2.1-TIV-ITM_DB2-IF0003

Downloadable files


Abstract

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

Download Description

Copyright International Business Machines Corporation 2010. All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager Agent for DB2,
Version 6.2.2 FP1

Component ID: 5724B96D0

Fix: Interim Fix 0003 (6.2.2.1-TIV-ITM_DB2-IF0003)

Date: September 10, 2012


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 listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


2.0 Problems fixed
==================

The following problems are addressed by this fix:

2.1 APARs:
----------

APAR: IV23334
Abstract: IMPROVE THE AGENT PERFORMANCE TO MONITOR THE MULTI-PARTITION
Currently, the agent connects the instance for each partition,
so the agent connects an instance many times as the partition number, which causes
a performance problem.
By improving the agent to monitor multi-partition database performance, the agent
connects to an instance one time and takes a snapshot for each partition.

APAR: IV27659
Abstract: SYSTEM RESOURCE WORKSPACE IS EMPTY


2.2 Defects:
------------
Defects: 185483
Abstract: update the agent factory library file in next fix

Defects: 186714
Abstract: SQLExecDirect failed on linux platform


2.3 Enhancements:
-----------------

2.3.1 Improve query performance of the Tablespace attribute group for multiple partitions by APAR IV23334.
---------------------------------------------------
Typically, the DB2 agent collects data by using DB2 snapshot API. DB2 v9r7 and later provides
another way for table function to collect data. This ifix package adds table function to
collect data for the Tablespace attribute group. Two table functions, MON_GET_TABLESPACE
and MON_GET_CONTAINER, are used to collect data to substitute for the snapshot.
To change to the table function, the following special requirement and configuration steps are
required:

1) The monitored DB2 version must be 9.7 or later.
2) The user who starts the DB2 agent must have EXECUTION privileges on MON_GET_TABLESPACE
and MON_GET_CONTAINER for all databases. Some users (users with DBADM or SQLADM
authority) have EXECUTION privileges by default (Administrator on Windows systems, instance
owner on Linux and UNIX systems). If all users require access to the data, you can grant
EXECUTION privileges on the function to PUBLIC. Be careful with this option, because some monitor
functions contain sensitive data.
3) Set the KUD_T1_BY_SQL=Y trace parameters for the DB2 agent. After
reconfiguration, start the agent.


2.4 Superseded fixes:
---------------------
6.2.2.1-TIV-ITM_DB2-IF0001
6.2.2.1-TIV-ITM_DB2-IF0002

2.5 APARs and defects included from superseded fixes:
------------------------------------------------------
APAR: IV12361
Abstract: some attribute columns do not have the SORTBYINTERNAL option
Additional Information: The data for some columns in the default Tablespace
Summary attribute are sorted by character and string.

APAR: IV07850
Abstract: INCORRECT VALUE FOR SPACE USED DMS TABLE PCT IN SUPERSEDEDTABLE
Additional Information: The DB2 agent reports 1 instead of 100 when the table is
used 100% for the Space Used DMS Table Pct attribute. The value is incorrect in the
"Table Space(Superseded)" workspace and correct in the "Table Space" workspace.

APAR: IV04338
Abstract: Update GetNextDbDirEntry API from DB2 version 8 to 9
Additional Information: The following error is in the agent log:
SQL1650N The function invoked is no longer supported.

The following information is in the db2diag.log:
Application must be updated to call the db2DbDirGetNextEntry API
with a current version number in order to retrieve the database directory entry
for the database with alias because the downlevel API call is unable to
handle its path.

APAR: IV09403
Abstract: DB2 agent should not connect standby database
Additional Information: The following error is in the agent log:
SQL1776N The command is not supported on an HADR standby
database or on an HADR standby database with the current
configuration or state. Reason code = "1".

The following information is in the db2diag.log
MESSAGE: Connections are not allowed on a standby database.

APAR: IZ89283
Abstract: ITM DB2 Agent crash when stop

APAR: IZ99404
Abstract: POOL HIT RATIO DISPLAY 2147483647
Additional Information: The function for calculating pool hit ratio cannot
correctly handle a negative result. The result is a type change and
the 32-bit max value 2147483647 is displayed.

APAR: IV14961
Abstract: Instance Name value is not saved when DB2 stopped
Additional Information: If a DB2 instance stopped, the following information
is displayed: instance_name not displayed when situation on
System Overview attribute is triggered.

APAR: IV15352
Abstract: UOW_Lock_Wait_Time attribute description is incorrect
Additional Information: UOW_Lock_Wait_Time attribute description used seconds
as the unit for this attribute value, but the agent shows that milliseconds is the unit
for the collected value from DB2.

Defects: 155019
Abstract: Some condition of tablespace situation with wrong definition

Defects: 160992
Abstract: Unexpected KUICEW026W in exportworkspaces output
Additional Information: The KUICEW026W Message is displayed when running the
'tacmd exportworkspaces' command:
KUICEW026W:The workspace <Variable formatSpec="{0}">WORKSPACE</Variable>
could not be exported because an error occurred while requesting the object from
the Tivoli Enterprise Portal Server.

Defects: 170846
Abstract: Failed to parse db2diag.log on 9.7
Additional Information: The following information is in the agent log:
*****Error: uregex_reset failed for pattern (^.*$)|NODE : (.*)([\s.]*.)* string <>,
status 8 <U_INDEX_OUTOFBOUNDS_ERROR>
Replace failed for pattern [(^.*$)|NODE : (.*)([\s.]*.)*]
using original input string []
By fixing this defect, the field of the Message in Diagnostic Log attribute displays a
truncated message, and works as expected.

Defects: 178203
Abstract: Open failed for temporary metafile
Additional Information: The following error is in the agent logs:
***Error: Open failed for temporary metafile
***** Input string is NULL
*** Unable to open metafile .\work\ - Errno 2, ErrorText <No such file or directory>
*** Unable to open metafile .\work\.MDL - Errno 3, ErrorText <No such process>
Could not find any kumpmsg resource bundles in directory .\rb.
*** Unable to open MetaFile

APAR: IZ96116
Abstract: UNABLE TO LOAD THE DML BOOK WITH ITCAM DB2 AGENTS 6.2.2 FP1

APAR: IZ92738
Abstract: DB2NODES.CFG PATH NOT FOUND IN CODEPAGE 943

APAR: IZ91425
Abstract: "System Overview" new attribute group cannot be shown on
the System Overview subnode when creating a new situation

APAR: IZ89283
Abstract: DB2 AGENT CRASH PROBLEM WHEN STOPPING

APAR: IZ74758
Abstract: ITMFORDBS 6.2 / KUDDB2 DAEMON DIES OUT SOON.
Additional Information: "kuddb2" crashes immediately after the DB2 agent starts.
The call stack shows the following information:
(gdb) where
#0 0x00000200025a63dc in strcpy () from /lib64/libc.so.6
#1 0x000000008010e4dc in translateSigns ()
#2 0x000000008010de64 in ReorgCheckIndex ()
#3 0x000000008010cf70 in checkReorg ()
#4 0x00000000801099ca in kud00_kudtable_agent::TakeSample ()
#5 0x000002000160376c in ctira::DriveDataCollection () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#6 0x000002000160c5d6 in TableManager::checkForExpiredRequests () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#7 0x000002000160cb7a in TableManager::timeout () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#8 0x00000200015c998c in CTRA_timer_base::TimerCallbackHandler () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#9 0x00000200015c8076 in Handler_base () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#10 0x00000200015cb572 in CTRA_timer_task () from
/opt/IBM/ITM/tmaitm6/ls3266/lib/libkra.so
#11 0x000002000005b02a in start_thread () from /lib64/libpthread.so.0
#12 0x00000200025feb86 in thread_start () from /lib64/libc.so.6
......

APAR: IZ84996
Abstract: Tablespace type value is reported incorrectly on HP-UX IA64
Additional Information: The DB2 agent reports TABLESPACE TYPE as "Database managed
space" in the Tivoli Enterprise Portal when the correct table space type is
"System managed space".

Defects: 144825
Abstract: ICOC: DB2 DLA does not reconcile with sensor

Defects: 139637
Abstract: Invalid data in DLA book from DB2 agent
Additional Information: The data in the DLA book from the DB2 agent is not valid.

3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in
the IBM Tivoli Composite Application Manager Agent for DB2 V6.2.2 FP1
User's Guide.

The following link is for the Tivoli operating system and application
support matrix. Please 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
-----------------------------
The prerequisite level for this fix is as follows:

- IBM Tivoli Composite Application Manager Agent for DB2 6.2.2 FP1.

Because this fix is cumulative, it can be installed on any fix level for
this version, release, and modification level later than the prerequisite.

4.0 Image directory contents
=============================

This fix image contains the following files:

- 6.2.2.1-TIV-ITM_DB2-IF0003.README - This README file
- 6.2.2.1-TIV-ITM_DB2-IF0003.tar - Fix archive .tar format
- 6.2.2.1-TIV-ITM_DB2-IF0003.zip - Fix archive .zip format

Note: The .tar and .zip files are identical in content. Use the .tar
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:

- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_aix523_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_aix526_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_hpi116_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_li6263_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_ls3243_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_ls3246_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_ls3263_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_ls3266_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_lia266_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_lpp266_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_lx8266_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_sol283_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_sol286_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_sol606_tema_if0003.tar
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_winnt_tema_if0003.cab
- 6.2.2.1-TIV-ITM_DB2-IF0003/kud_wix64_tema_if0003.cab
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudaix523.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudaix526.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudhpi116.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudli6263.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudls3243.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudls3263.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudls3246.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudls3266.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudlia266.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudlpp266.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudlx8266.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudsol283.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudsol286.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudsol606.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudwinnt.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/kudwix64.dsc
- 6.2.2.1-TIV-ITM_DB2-IF0003/inst_prepreq_patch.sh
- 6.2.2.1-TIV-ITM_DB2-IF0003/ud_dd_062201003.xml
- 6.2.2.1-TIV-ITM_DB2-IF0003/ud_dd.properties.


5.0 Installation instructions
==============================
This fix can be installed only 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 CANDLEHOME environment
variable to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because no uninstall utility for this fix exists,
back up your environment before installing this fix.

5.2 Local agent update
----------------------

1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_DB2-IF0003.tar
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 unzip utility on Windows systems. Expanding the file creates a directory
structure that contains fixes for all of the supported operating systems.

3. Use the itmpatch command to install the fix for the operating
system of that agent. For more information about the itmpatch command,
see section 6.1.

On a UNIX system, if the fix was expanded to <TEMP>/6.2.2.1-TIV-ITM_DB2-IF0003,
the install command is

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.1-TIV-ITM_DB2-IF0003/kud_xxxxxx_tema_if0003.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_if0003.tar.
> ./cinfo -i
Monitoring Agent for DB2
aix523 Version: 06.22.01.03

On a Windows system, if the fix was expanded to
<TEMP>\6.2.2.1-TIV-ITM_DB2-IF0003, the install command is

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.2.1-TIV-ITM_DB2-IF0003\kud_winnt_tema_if0003.cab
A known issue exists regarding updating the DB2 agent that is installed on
a Windows 64-bit OS platform. See the workaround for the third known
issue listed in section 7.0.

5.3 Remote agent update
------------------------

1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_DB2-IF0003.tar)
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 unzip utility on Windows systems. Expanding the file creates a directory
structure that contains fixes for all of the supported operating systems.

3. To add the agent fix 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 about the tacmd addBundles command, see the IBM Tivoli
Monitoring Command Reference.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.2.1-TIV-ITM_DB2-IF0003:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.1-TIV-ITM_DB2-IF0003

On a Windows system,
if the fix was expanded to <TEMP>\6.2.2.1-TIV-ITM_DB2-IF0003:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.1-TIV-ITM_DB2-IF0003

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. See Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring Server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information about the tacmd
login and updateAgent commands, see the IBM Tivoli Monitoring
Command Reference.

On UNIX systems:
> $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 062201003

On Windows systems:
> %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 062201003


Note:
- 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.
5.4 Agent support update
------------------------
This fix (6.2.2.1-TIV-ITM_DB2-IF0003) includes changes to the agent
support files that must to be installed. If you have already
installed these updates, there are no additional installation steps.
Otherwise, 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 (on UNIX systems
6.2.2.1-TIV-ITM_DB2-IF0003.tar and on Windows systems
6.2.2.1-TIV-ITM_DB2-IF0003.zip) 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. Expanding the file creates a
directory structure that contains fixes for all of the supported platforms.

3. Expand the archive file (kud_tems_teps_tepd_if0003.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 unzip utility
on Windows systems. Expanding the file creates a directory structure that
includes a subdirectory called CD-ROM with the necessary updates.

4. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located:

On UNIX systems:
> $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar

On Windows systems:
> <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar

where <"C:\Program Files\IBM\Java142"> is the default drive
and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
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.
One known problem exists with the update support file by 64-bit Java. See
section 7.0 Known problems and workarounds for detailed information.

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. For this fix, select 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
06.22.01.02 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 Additional information on using 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, this path must include the drive
letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, this must include the drive letter.


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




7.0 Known problems and workarounds
===================================
1. When parsing a large db2daig.log file, the DB2 agent might fail to
stop and result in a failure to update remotely.
Workarounds:
Move the db2daig.log, so the remote update can pass.


2. The following defect is known: 173839 - Build info will be lost when
update agent to 6.2.2 fp1 fix1. The build number for the support file is not updated.
This problem exists only on Windows system.
Confirm the upgrade status by viewing the version number in the output of the
kincinfo -i command:

UD IBM Tivoli Composite Application Manager Agent for DB2
WINNT Version: 06.22.01.02 Build:

3. Remote deployment of the DB2 agent on a Windows platform failed,
when a Windows service named kudcma_<DB2 instance name> was
created during DB2 Server installation. The root cause is that the
DB2 image packaged with the old version of DB2 agent causes a
failure to create a Windows service during remote deployment.
For information about the difference between the DB2 agent 6.22 Fix Pack 1
and the older DB2 agent packaged in the DB2 image, see
https://www-304.ibm.com/support/docview.wss?uid=swg21383741

Workaround: Use the following steps to solve this problem:
1. Open a command line window.
2. Run "sc delete kudcma_<DB2 instance name>".
3. Try remote deployment again.

4. Update the agent support file with 64-bit Java. One
Java exception is displayed in the command line, for example:

>C:\IBM\ITM\java\java50_x64\jre\bin\java -jar setup.jar
Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: libwinjni
(C:\IBM\ITM\java\java50_x64\jre\bin\libwinjni.dll is not a valid Win32 applicat
ion. )
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:995)
at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:959)
at java.lang.System.loadLibrary(System.java:453)
at com.ibm.tivoli.itm.install.appsupport.WinJni.<clinit>(WinJni.java:18)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

Workaround: Update to the 32-bit Java support file.

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(R) are trademarks or registered trademarks
of International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or
other companies. A current list of IBM(R) trademarks is available on the
Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

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.

Installation Instructions

Please refer to the 6.2.2.1-TIV-ITM_DB2-IF0003.README contained in the Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is DD?
6.2.2.1-TIV-ITM_DB2-IF0003.zip 7 Sep 2012 English 32462339 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.tar 7 Sep 2012 English 92497920 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README 7 Sep 2012 English 31146 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.DE 7 Sep 2012 German 35697 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.FR 7 Sep 2012 French 34741 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.JP 7 Sep 2012 Japanese 36977 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.PT 7 Sep 2012 Brazilian Portuguese 32856 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.SP 7 Sep 2012 Spanish 33319 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.zh_CN 7 Sep 2012 Simplified Chinese 27871 FTP DD
6.2.2.1-TIV-ITM_DB2-IF0003.README.zh_TW 7 Sep 2012 Traditional Chinese 28610 FTP DD

Product Alias/Synonym

ITCAM Agent for DB2 Database

Problems (APARS) fixed
IV04338, IV07850, IV09403, IV12361, IV14961, IV15352, IZ74758, IZ84996, IZ89283, IZ91425, IZ92738, IZ96116, IZ99404, IV23334, IV27659

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring for Databases
ITM Agent DB2 V6

Software version:

6.2.2

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

4033405

Modified date:

2014-09-11

Translate my page

Machine Translation

Content navigation