IBM Support

IBM Tivoli Composite Application Manager for Applications V7.2.1.2 : Sybase Agent 6.2.0.1-TIV-ITM_SYB-IF0001

Downloadable files


Abstract

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

Download Description


(C) Copyright International Business Machines Corporation 2017.
All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager for
Applications V7.2.1.2: Tivoli(R) Composite Application Manager Agent
for Sybase(R) ASE 6.2.0 Fix Pack 1

Component ID: 5724B96SO

Interim Fix: 0001, 6.2.0.1-TIV-ITM_SYB-IF0001

Date: 10 May, 2017

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.


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
--------------
APAR : IV94152
Abstract: Sybase Agent SDA support seeding failed, when agent installed
on non-windows platforms
Additional Information: Sybase agent support seeding failed because
variables TEMA_SDA and ITM_MANIFEST_PATH were not set.

APAR : IV93213
Abstract: Error while verifying Sybase agent configuration on
non-windows agent
Additional Information: Syntax error encountered while verifying Sybase
agent configuration using CandleDBConfig command option 5. Syntax error
in kddivp.sh script line 20.

APAR : IV94269
Abstract: Sybase Agent 6.2 interval collection failure for cursor DBCCON
Additional Information: Sybase agent logs an error for DBCCON cursor when
the sa_role is not granted.The cursor uses Sybase trace flag 8399,
which require sa_role for successful execution.
Error occurs because user don't have sufficient permissions (roles).

APAR : IV94705
Abstract : Sybase Agent 6.2 col_function failure error for cursor KOYLOCKS
Aditional Information : Sybase agent logs an error for KOYLOCKS cursor as
Col_function failed to load. The cursor uses LOCKTYPE attribute and fails
if column length of LOCKTYPE is greater than 256.

2.2 Defects
--------------
Defect: 117682
Abstract: Sybase agent configuration failed on Solaris 11 platform
Additional Information:On Solaris 11 Operating system, Sybase agent
configuration script shows incorrect Sybase server name.
Sybase Agent configuration file was created with wrong name.

Defect: 118130
Abstract: Fix vulnerability found in SEF scan report.
Additional Information: Agent should able to collect data
with minimum required access rights i.e. GENERIC_ALL access right.

Defect: 117683
Abstract: Sybase memory leak fixes
Additional Information: Memory leak was observed because of some
dynamically allocated memory variables in the Sybase agent.

2.3 Enhancements
----------------------
None.

2.4 Superseded fixes
-------------------------
None.

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
None.

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM Tivoli
Monitoring for Databases: Sybase Server Agent User's Guide, version 620FP1.
For information about system requirements, go to the software product
compatibility reports website, and search for the ITCAM for Applications
product:
(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 for
Applications V7.2.1.2: Tivoli Composite Application Manager Agent
for Sybase ASE 6.2.0 Fix Pack 1

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

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.0.1-TIV-ITM_SYB-IF0001.README - This README file
- 6.2.0.1-TIV-ITM_SYB-IF0001.tar - Fix archive .tar format
- 6.2.0.1-TIV-ITM_SYB-IF0001.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.0.1-TIV-ITM_SYB-IF0001/koyaix523.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koyaix526.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koyli6263.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koylpp266.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koylx8266.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koysol283.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koysol286.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koysol606.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/KOYWINNT.dsc
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_aix523_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_aix526_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_li6263_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_lpp266_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_lx8266_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_sol283_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_sol286_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_sol606_tema_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_tems_teps_tepd_IF0001.tar
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_tems_teps_tepd_IF0001.zip
- 6.2.0.1-TIV-ITM_SYB-IF0001/koy_winnt_tema_IF0001.cab
- 6.2.0.1-TIV-ITM_SYB-IF0001/oy_dd.properties
- 6.2.0.1-TIV-ITM_SYB-IF0001/oy_dd_062001001.xml

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 symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

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 (6.2.0.1-TIV-ITM_SYB-IF0001
.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 symbol <TEMP> 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
an extract utility on Windows systems. This step 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 on the "itmpatch"
command, see section [6.3].

On UNIX systems, if the fix was expanded to
<TEMP>/6.2.0.1-TIV-ITM_SYB-IF0001, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0.1-TIV-ITM_SYB-IF0001/koy_xxxxxx_tema_IF0001.tar

where:
- xxxxxx corresponds to the value in the first column
returned by the ./cinfo -i command.

In the following example, the file is
koy_lx8266_tema_IF0001.tar:
> ./cinfo -i
Monitoring Agent for Sybase Server
lx8266 Version: 06.20.01.01

On Windows systems, if the fix was expanded to
<TEMP>\6.2.0.1-TIV-ITM_SYB-IF0001, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0.1-TIV-ITM_SYB-IF0001\koy_winnt_tema_IF0001.cab

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.0.1-TIV-ITM_SYB-IF0001
.tar or .zip) to a temporary directory on the IBM Tivoli
Enterprise Monitoring Server system. For the purpose of this
README, the symbol <TEMP> represents the fully qualified path to
this directory. Note: On Windows 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. This step 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 on the "tacmd addBundles" command,
see the IBM Tivoli Monitoring Administrator's Guide.

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

On Windows systems,
if the fix was expanded to <TEMP>\6.2.0.1-TIV-ITM_SYB-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.2.0.1-TIV-ITM_SYB-IF0001

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


4. To login to the Tivoli Enterprise Monitoring Server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "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 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 oy
-n <Managed system name>
-v 062001001

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 oy
-n <Managed system name>
-v 062001001

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (oy), not three characters (koy).
- 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.


6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix.
No additional installation steps are required.

6.2 Installation instructions for Sybase Agent SDA support seeding
----------------------------------------------------------------
1. Perform remote agent update. For more information, see section [5.3].


2. Login to the Tivoli Enterprise Monitoring Server.
Use the tacmd addSdaInstallOptions command to add a version to product
versions configured to be allowed for Self-Describing Agent(SDA) install.
For more information on the "tacmd addSdaInstallOptions" command,
see the IBM Tivoli Monitoring Command Reference guide.

On UNIX systems:

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

Run the following command to enable SDA installation for
the ITM620 FP1 sybase agent :

> $CANDLEHOME/bin/tacmd addSdaInstallOptions
-t oy
-v 06200100

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

Run the following command to enable SDA installation for
the ITM620 FP1 sybase agent :

> %CANDLE_HOME%\bin\tacmd addSdaInstallOptions
-t oy
-v 06200100


3. Use the tacmd configureSystem command to reconfigure the
installed sybase agent.
On UNIX systems:
> $CANDLEHOME/bin/tacmd configureSystem
{-m|--system} SYSTEM
{-p|--property} SECTION.NAME=VALUE...

where:
-m|--system
Identifies the agent (managed system) for which to update
the configuration

On Windows systems:
> %CANDLE_HOME%\bin\tacmd configureSystem
{-m|--system} SYSTEM
{-p|--property} SECTION.NAME=VALUE...

4. Restart the installed sybase agent remotely using commands
"tacmd stopagent" and "tacmd startagent".For more information see the
IBM Tivoli Monitoring Command Reference guide.

Stop sybase agent remotely:

On UNIX systems:
> $CANDLEHOME/bin/tacmd stopAgent -t oy -n <MANAGED-OS>

On Windows systems:
> %CANDLE_HOME%\bin\tacmd stopAgent -t oy -n <MANAGED-OS>

Start sybase agent remotely:

On UNIX systems:
> $CANDLEHOME/bin/tacmd startAgent -t oy -n <MANAGED-OS>

On Windows systems:
> %CANDLE_HOME%\bin\tacmd startAgent -t oy -n <MANAGED-OS>


5. verify application support installation records using
"tacmd listappinstallrecs".

On UNIX systems:
> $CANDLEHOME/bin/tacmd listappinstallrecs -t oy

The output lists the application support installation records for
the specified product.


On Windows systems:
> %CANDLE_HOME%\bin\tacmd listappinstallrecs -t oy

The output lists the application support installation records for
the specified product.


6.3 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 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
----------------------------
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 login to a Tivoli Enterprise
Monitoring Server prior to 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 dd
> $CANDLEHOME/bin/tacmd listSystems -t oy

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 dd
> %CANDLE_HOME%\bin\tacmd listSystems -t oy

Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (oy), not three characters (KOY).

When the agent update is successful, the version of the Sybase
Server agent is 06.20.01.01.


6.5 Additional Notes on Remote Deployment
-------------------------------------
If you have applied any preceding fixes and already performed the
following steps, you can skip this section.

To deploy the agent, you must perform the following steps:
a. For remote agent update of 6.2.0.1 Interim Fix 1, prerequisite
is to add 6.2.0 Fix Pack 01 base agent bundles into remote deploy
depot. For more information on the "tacmd addBundles" command,
see the IBM Tivoli Monitoring Administrator's Guide.
b. After the deploy completes, the agent must be updated for
this interim fix using "tacmd updateAgent".
c. The agent must be reconfigured so that the Monitoring Agent
for Sybase Server collector service switches to using the
new executables.
See the IBM Tivoli Monitoring for Databases: Sybase Server
Agent User's Guide for more information on configuring the
agent.

7.0 Known problems and workarounds
=========================
- Problem: Sybase Agent 6.2.0.1 Interim Fix 01 remote upgrade failed on
Solaris 11 machine

Workaround: Apply 6.2.0.1 Interim Fix 01 patch locally and configure
the instance with ITM.

- Problem: Registry entries are not cleared when agent is uninstalled on
64 bit windows platform.

Workaround: Delete registry entries manually from path:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Candle\KOY\610\

- Problem: When running multiple remote deploys and agent upgrades, a task
timeout occurs during either the remote deployment or the
agent upgrade.

Workaround: Restart the OS Agent following the task timeout and before
performing the next remote deployment or agent upgrade.

- Problem: If you are installing this fix into a depot on a Windows computer,
and WinZip(R) is used to extract this fix, text files in the depot
might contain CTRL-Ms. When this fix is remotely deployed to a UNIX
machine from the Tivoli Enterprise Monitoring Server or depot
on Windows, the installation fails. The CTRL-Ms are caused by
extracting the fix using WinZip with "TAR file smart
CR/LF conversion" option enabled. This extraction causes WinZip
to put CTRL-Ms in text files when they are extracted on UNIX
through remote deployment.

Workaround: If you are using WinZip for the fix installation for the Tivoli
"TAR file smart CR/LF conversion" option.

- Problem: After remote deployment using the GUI, it is not clear that the
latest available fix has been installed.
The "Install Updates" button is not greyed out and the text
indicates that the latest patch level is not installed.

Workaround: No workaround is needed.

- Problem: In the Tivoli Enterprise Portal, the instance name is displayed
instead of the host name in the Navigation tree.
For example the Navigation tree might look like this,
MySid
Sybase
Alert Log
...
instead of this,
MyHost
Sybase - MySid
Alert Log
...

The problem is that the length of the managed node name,
<SID>:<HOSTNAME>:SYB,exceeds the length supported by the portal.
A possible cause is that the fully-qualified host name is being
used. If 'uname -n' on the Monitoring Agent for Sybase Server
computer returns a fully-qualified host name, then this host name
is the cause.

Workaround: Override the host name with an appropriate shorter name
by adding the following line to oy.config:
export COLL_HOSTNAME=<short name>


8.0 Additional product information
======================
None.

9.0 Notices
=======
This information was developed for products and services offered in
the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any IBM
intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to
you.

Trademarks and service marks
------------------------------------

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM 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.

Prerequisites

IBM Tivoli Composite Application Manager for Applications V7.2.1.2: Tivoli Composite Application Manager Agent for Sybase ASE 6.2.0 Fix Pack 1, IBM Tivoli Monitoring V6.2.2 FP2

Installation Instructions

Please refer to the README contained in the Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)?
What is DD?
6.2.0.1-TIV-ITM_SYB-IF0001 10 May 2017 English 92831318 FC DD

Product Alias/Synonym

Sybase Agent

Problems (APARS) fixed
IV94152, IV93213, IV94269, IV94705

Document information

More support for: Tivoli Composite Application Manager for Applications
ITCAM Agent for SYBASE - 5724B96SO

Software version: 6.2.0.1

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 4043619

Modified date: 10 May 2017