IBM Tivoli Monitoring for Databases:Sybase Server Agent 6.2.0-TIV-ITM_SYB-IF0010

Downloadable files


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.4. Updated 2014/06/03

Download Description

(C) Copyright International Business Machines Corporation 2012.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Databases: Sybase(R) Server
Agent, Version 6.2.0

Component ID: 5724B96SO

Interim Fix: 0010, 6.2.0-TIV-ITM_SYB-IF0010

Date: 10 July, 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: IV01440
Abstract: Collector process crashes with COLL_HOLD_SYSMON=1
Additional Information: The collector (koy12col or koy15col)
process crashes and core file are generated if COLL_HOLD_SYSMON
is set to 1.

APAR: IV12584
Abstract: koyserv dumps core
Additional Information: The koyserv program dumps core when
some lines are more than 1024 bytes in the Sybase log file.


2.2 Defects
--------------
Defect: 171641
Abstract: CT 4892: Wrong value of Sybase Log Summary attribute group
Maximum Private Log Cache Size (KB) attribute.
Additional Information: The Sybase Log Summary attribute group
Maximum Private Log Cache Size (KB) attribute displays a wrong value 0.

Defect: 174439
Abstract: CT 4892: Available database server cannot be auto-discovered.
Additional Information: When configuring the agent, the agent is unable to
discover running a 64-bit Sybase database server automatically.

Defect: 184386
Abstract: CT 5027: data in view "Devices" is not correct
Additional Information: For some database, the device information
is not correct. You can check the data on TEP by clicking on
Databases navigator node, selecting a database from
Databases Detail view in Databases workspace, right-clicking
Log and Space Information. Check Devices view
in Log and Space Information workspace.

Defect: 185601
Abstract: Unable to get 64-bit Sybase error log file on Windows
Additional Information: The agent is unable get a 64-bit Sybase
error log file on a Windows system. The following error message is in the
<install_dir>/logs/<hostname>_oy_<instance_id>_col.out collector log file:

>ESV0360E Unable to open Sybase error log file "<number>".
errno=2 (No such file or directory)

2.3 Enhancements
----------------------
Enhancement: internal 178525
Abstract: Remove old core files to avoid filling up file system
Additional Information: When a new core file is generated under
<install_dir>/tmp/<hostname>_oy_<instance_id>, the agent
removes old core files and then renames the generated
core file as core.<program>.<timestamp>.

2.4 Superseded fixes
-------------------------
6.2.0-TIV-ITM_SYB-IF0009
6.2.0-TIV-ITM_SYB-IF0008
6.2.0-TIV-ITM_SYB-IF0007
6.2.0-TIV-ITM_SYB-IF0006
6.2.0-TIV-ITM_SYB-IF0005
6.2.0-TIV-ITM_SYB-IF0004
6.2.0-TIV-ITM_SYB-IF0003
6.2.0-TIV-ITM_SYB-LA0002
6.2.0-TIV-ITM_SYB-LA0001

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.2.0-TIV-ITM_SYB-IF0009
-------------------------------
APAR: IZ89600
Abstract: KOYERR CORE DUMPS.
Additional Information: The koyerr program dumps core when the
next line after "server Error" has less than 60 characters.

APAR: IZ92214
Abstract: WRONG ATTRIBUTE SYBASE_STATISTICS_SUMMARY.CURRENT\LOGONS.
Additional Information: Log in to the Tivoli Enterprise Portal.
Click on the Servers navigator node,
and check the Server Statistics workspace, Statistics Summary view.
The value of 'Current\Logons' might be bigger than
'Max User\Connections\Allowed', and the value of
'Pct Max\Logons\Active' might be bigger than 100%. The value of
'Current\Logons' includes both system connections and user
connections, but it must include only user connections.

APAR: IZ94558
Abstract: KOYLOG CORE DUMPS.
Additional Information: The koylog program dumps core when the
Tivoli agent user does not have enough permission. The program stops
dumping core after granting permissoins by running koygrant.sql.

Enhancement: ER MR111510608
Abstract: Set Sybase_Segment_Detail.Segment_Name and
Sybase_Process_Detail.Database_Name attributes as display item
of situation.
Additional Information: After applying this fix, you can choose
Sybase_Segment_Detail.Segment_Name and
Sybase_Process_Detail.Database_Name attributes
as display items when defining a situation for a corresponding
attribute group.

6.2.0-TIV-ITM_SYB-IF0008
-------------------------------
APAR: IZ80068
Abstract: CURSOR SYSMON FAILS TO GET DATA AFTER RESTART THE SYBASE
SERVER.
Additional Information: After restarting the Sybase db server, cursor
SYSMON fails to get data. The agent reports 100%
Engine CPU_Busy_Percent and other incorrect attributes.

Defect: 134268
Abstract: Wrong attribute Sybase_Lock_Conflict_Detail.Time_Blocked.
Additional Information: The Sybase_Lock_Conflict_Detail.Time_Blocked
attribute value is incorrect.

Defect: 134269
Abstract: The agent does not pick up changes for the dynamic setting.
Additional Information: Change cursor KOYVSTAT behavior to pick up
the dynamic parameter change for the Sybase database.

Defect: 135511
Abstract: The situation with the
"*IF Sybase_Server_Enterprise_View.Server_Status *NE ACTIVE"
formula does not work.
Additional Information:

Defect: 137147
Abstract: Install CAP file.
Additional Information: With IBM Tivoli Monitoring 6.22 FP01 a new feature, Agent
Management Services expanded support, was introduced.
To monitor the agent using the watchdog, copy
koy_default.xml in %CANDLE_HOME%/TMAITM6/CAP on Windows systems
or $CANDLEHOME/config/CAP on Linux or UNIX systems.

6.2.0-TIV-ITM_SYB-IF0007
-------------------------------
APAR: IZ68094
Abstract: DISABLE SP_SPACEUSED FROM SYBASE AGENT
Additional Information: See Section 2.3 Enhancements before
applying this fix.

APAR: IZ70735
Abstract: NEGATIVE VALUE OF DATA\FREESPACE\PERCENT ATTRIBUTE
Additional Information: The Data\Freespace\Percent attribute
reports a negative value when the database size is
greater than 2147483647 KB.

APAR: IZ73216
Abstract: DATABASE SUMMARY VIEW IS INCONSISTENT WITH WITH
DATABASE DETAIL VIEW
Additional Information: When the agent accesses the database with
the problem, for example, suspect db, the Sybase stored
procedure reports an error without returning any data.
In this case, the "Database Detail" view shows
incorrect data for the corresponding database. The
number of Total DB In Error is correct, but no databases
are shown in Error Status.

APAR: IZ73258
Abstract: CANNOT RECOGNIZE THE CORRECT SYBASE SERVER NAME WHEN
CONFIGUREING THE AGENT
Additional Information: If there is a blank character after "-s"
in the Sybase "dataserver" process, the agent cannot
recognize the correct Sybase server name when
configuring the agent.

6.2.0-TIV-ITM_SYB-IF0006
-------------------------------
APAR: IZ66084
Abstract: DBCC MONITOR CLEAR THE SHARED METRIC DATA
Additional Information: The original code uses the following dbcc
command:
dbcc monitor("clear","all", "on" )
This command clears the Sybase performance counter value in
the master..sysmonitors table. Clearing this value causes the
other monitoring programs to have unexpected results. The new
solution uses a non-clear dbcc option to avoid problems
with other monitoring programs.

Note: The non-clear dbcc option requires at least an extra
5 MB of data space and 5 MB of log space on sybase tempdb for
caching midterm data.

APAR: IZ67060
Abstract: CTL MATH DECIMAL DOES NOT FUNCTION IN RUSSIAN LOCALE
Additional Information: This problem occurs in some European and
Latin American countries that use a "comma" and not a "dot"
for the decimal separator.

The Sybase agent does not correctly use the decimal separator in
European and Latin American locales, and the Server Status
attribute displays an incorrect value such as '1,500000'. In this
example, the attribute displays a "comma" (,) in the wrong value.

APAR: IZ67387
Abstract: DATABASE SUMMARY VIEW IS INCONSISTENT WITH DETAIL VIEW
Additional Information: When the database status bit 64 is set
(master..sysdatabases &64 = 64 ), the database
status is "recovery started for all databases to be recovered."
It fails to be counted in the "Total DB in Error" column in
"Database Summary," but in the "Database Detail" view, the
"Error Status" column is marked "Yes," which is an error
status.

Defect: 120035
Abstract: "Device Total Percent" displays wrong value
for Sybase 15
Additional Information: The "Device Total Percent" attribute in
the "Device Usage" table view, "Device Usage" workspace and
"Database" Node displays an incorrect percent value. Sybase 15
provides the device number directly for disk monitoring. This
number is different with Sybase 12 and causes the problem.

6.2.0-TIV-ITM_SYB-IF0005
-------------------------------
APAR: IZ61683
Abstract: ERRORLOG ALERT SUMMARY VIEW HANGS UP
Additional Information: After the Sybase error log has been
truncated, archived, or has not found a matched error message,
the Sybase "Errorlog Alerts" workspace and the "Alert Summary"
table view stop refreshing and the "Sample Timestamp" column
does not change.

APAR: IZ63991
Abstract: SYBASE AGENT STOPS COLLECTING DATA. NO DATA
Additional Information: When the Sybase error log has been
truncated or archived, or has not found a matched error message,
the Sybase agent stops collecting data, and no data is
displayed in the Tivoli Enterprise Portal.

Defect: 112364
Abstract: Add the cursor name in the error message for open pipe
error.
Additional Information: When an open pipe error message is created
in the Sybase agent *.out log file, the corresponding cursor
name is also reported.

For example:
CIR1880E (130107) Open Probe pipe errno= 2. Pipe=/opt/zyh/tmp/
tivj06_oy_TIVJ06/prb_TIVJ06_koy_tivj06_10130105_0018_pipe.
Cursor=KOYSTATS

Defect: 117245
Abstract: koyerr crashes on AIX if error log message is too long.
Additional Information: If entry text for a matched Sybase error
log message is longer than 360 bytes, a koyerr core dump is
created.

6.2.0-TIV-ITM_SYB-IF0004
-------------------------------
APAR: IZ56661
Abstract: SERVER SUMMARY VIEW HANGS UP WHEN SYBASE ERROR LOG
TRUNCATE
Additional Information: After the Sybase error log has been
truncated or archived, the Sybase agent Server Summary
table view stops refreshing and the "Sample Timestamp"
column does not change.

Defect: 106134
Abstract: Support Sybase 15 on Solaris 10 x86-64
Additional Information: Since 6.2.0-TIV-ITM_SYB-IF0004, the Sybase
15 database is supported on Solaris 10 Opteron for x86-64.
After applying IF0004 and following the common configuration
and starting and stopping processes, the Sybase 15 database
can be monitored and the Sybase agent is displayed in the
Tivoli Enterprise Portal.

6.2.0-TIV-ITM_SYB-IF0003
-------------------------------

APAR: IZ52285
Abstract: SYBASE AGENT HANG SOMETIMES ON WINDOWS OPERATING SYSTEM
Additional Information: On Windows(R) systems, sometimes no data
is displayed in the Tivoli Enterprise Portal,
because the process (kddos.exe/koysql.exe/koyerr.exe) has
stopped.

APAR: IZ51443
Abstract: PROCESS KOYSQL/KOYERR CRASHES IF UNABLE TO CREATE TEMP
FILE
Additional Information: On Windows(R)systems, the Monitoring Agent
for Sybase Server processes (koycoll.exe/koysql.exe/koyerr.exe)
stop if unable to create a temporary file.

APAR: IZ51109
Abstract: ITM6.2-SYBASE AGENT CREATES TEMP FILES IN %WINDIR%\TEMP
Additional Information: On Windows(R) systems, the Monitoring
Agent for Sybase Server creates temporary files in the
%WINDIR%\system32 directory, and does not delete them.

APAR: IZ49532
Abstract: SERVER SUMMARY VIEW DISPLAY NO DATA IF SYBASE DATABASE
LOG
Additional Information: There is no data in the portal "Server
Summary" view, if the Sybase database log file is empty.


6.2.0-TIV-ITM_SYB-LA0002
-------------------------------

APAR: IZ32259
Abstract: KDDSIGNL COREDUMPS ON LINUX
Additional Information: When stopping the Monitoring Agent for
Sybase Server, the following error occurs:

> ./itmcmd agent stop oy
*** glibc detected ***
/usr/local/Tivoli/IBM/ITM/tmp/winda1_or_MONIT/kddsignl:corrupted
double-linked list: 0x08077210
***

APAR: IZ31728
Abstract: ITM FOR DB 6.2 ORACLE AGENT GOES DOWN BY CTRL+C
ON SOLARIS.
Additional Information: This problem is also applicable to
the Monitoring Agent for Sybase Server.

APAR: IZ17115
Abstract: ORACLE AGENT (KORCOLL) USES >10% OF THE CPU
Additional Information: The performance tools show 10% utilization
on an AIX computer, though the performance report indicates
that the agent uses only about 0.2% of the CPU. This problem
is also applicable to the Monitoring Agent for Sybase Server.

Defect: 67530
Abstract: CT - Duplicate links in workspaces
Additional Information: Under the Monitoring Agent for Sybase
Server workspaces, the link icon shows duplicated links.
After applying this fix, run the BuildPresentation.bat script
in <CANDLEHOME>\CNPS to seed the new data to be inserted into
the Tivoli Enterprise Portal Server database.


Defect: 70401
Abstract: korcoll.exe intermittent crash in UTF8 conversion
Additional Information: This problem is intermittent. The
collector log shows a UTF-8 conversion failure, and sometimes,
the collector fails to start. This problem is also applicable
to the Monitoring Agent for Sybase Server.

Defect: 70931
Abstract: kddexec: Can't continue with the stop
Additional Information: This problem happens on Sun operating
systems. The ps -ef output on Sun operating systems is
truncated at 80 characters of description per command. The
problem is also applicable to the Monitoring Agent for Sybase
Server.

Defect: 71070
Abstract: CT-3116: ITMfDB Sybase 6.2 cannot be configured
completely
Additional Information: This problem happens only on Linux
systems. During the configuration, the following error
occurs:

Inventory of known Sybase Server servers before search:
X=Excluded I=Incomplete
TEST(I)
/opt/sybase/ASE-15_0/bin/dataserver: error while loading
shared libraries:
libbtsymbols.so: cannot open shared object file: No such file
or directory
Inventory of known Sybase Server servers after search:
X=Excluded I=Incomplete
TEST(I)

Defect: 77436
Abstract: CT-3246: The Sybase agent collection does not run
normally
Additional Information: This problem happens only on SUSE Linux
Enterprise Server 10.0 64-bit Itanium systems.

6.2.0-TIV-ITM_SYB-LA0001
-------------------------------

APAR: IZ05321
Abstract: CANDLEDBAGENT kills non-IBM Tivoli Monitoring processes
if RUNINFO PIDs are reused
Additional Information: When stopping the Monitoring Agent for
Sybase Server, you must wait at least 30 seconds before
restarting the agent to make sure all of the agent processes
have stopped normally.

APAR: IZ11539
Abstract: KDDOS.EXE error happens on large DB environment
Additional Information: None.

Defect: 50644
Abstract: KORFP1:SLES10 agent fails to start
Additional Information: Add support for SUSE Linux Enterprise
10 (SLES 10) and Red Hat Enterprise Linux 5 (RHEL 5) systems.

Defect: 65515
Abstract: Statically link the Rogue Wave libraries for Database
agents
Additional Information: None.

Defect: 67459
Abstract: itmcmd agent stop oy failed on AIX intermittently.
Additional Information: None.

Feature: 62380
Abstract: Support Sybase version 15.0
Additional Information: This change provides support for Sybase
Server version 15.0. The Monitoring Agent for Sybase Server
support for Sybase Server version 15 is limited to the
operating systems that the Sybase Server supports. The
following table shows which application versions and running
bit-modes are supported by the Monitoring Agent for Sybase
Server on the different operating system versions.
Sybase Server
Operating system version 15.0
---------------- -------------
Windows 2000 Advanced Server (32-bit) 32-bit
Windows 2000 Server (32-bit) 32-bit
Windows Server 2003 Data Center Edition
for x86-64 32-bit
Windows Server 2003 Data Center Edition
for x86-32 32-bit
Windows Server 2003 R2 SP2 for IA64 32-bit
Windows Server 2003 Standard Edition and
Enterprise Edition R2 SP2 for x86-32 32-bit
Windows Server 2003 Standard Edition and
Enterprise Edition R2 SP2 for x86-64 32-bit
Windows XP Professional (32-bit) 32-bit
AIX 5.2, 5.3 (32-bit) 32-bit
AIX 5.2, 5.3 (64-bit) 64-bit
Solaris 9 (32-bit) 32-bit
Solaris 9 (64-bit) 64-bit
Solaris 10 on SPARC (64-bit) 64-bit
Redflag 4.1 for x86 32-bit
Red Hat Enterprise Linux 3 for x86-32 32-bit
Red Hat Enterprise Linux 4 for x86-32 32-bit
Red Hat Enterprise Linux 4 for x86-64 64-bit
Red Hat Enterprise Linux 4 for System p 64-bit
SUSE Linux Enterprise Server 8 for x86-32 32-bit
SUSE Linux Enterprise Server 9 for x86-32 32-bit
SUSE Linux Enterprise Server 9 for x86-64 64-bit
SUSE Linux Enterprise Server 9 for System p 64-bit

Note: The Monitoring Agent for Sybase Server does not
support Sybase running on IA64 systems for
Linux or Solaris 10 Opteron for x86-64.

Note: All existing documentation in the IBM Tivoli
Monitoring for Databases: Sybase Server Agent
User's Guide that refers to Sybase Server
version 12 releases applies to Sybase Server
version 15.

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


3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring for Databases: Sybase Server Agent,
version 6.2.0.

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-TIV-ITM_SYB-IF0010.README - This README file
- 6.2.0-TIV-ITM_SYB-IF0010.tar - Fix archive .tar format
- 6.2.0-TIV-ITM_SYB-IF0010.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-TIV-ITM_SYB-IF0010/inst_prereq_itmpatch.exe.bat
- 6.2.0-TIV-ITM_SYB-IF0010/inst_prereq_patch.sh
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_aix523_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_aix526_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_li6243_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_li6263_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_lia266_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_lpp266_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_lx8266_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_sol283_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_sol286_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/kdd_sol606_tema_if0012.tar
- 6.2.0-TIV-ITM_SYB-IF0010/KDD_winnt_tema_if0012.cab
- 6.2.0-TIV-ITM_SYB-IF0010/koyaix523.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koyaix526.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koyli6243.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koyli6263.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koylia266.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koylpp266.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koylx8266.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koysol283.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koysol286.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koysol606.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/KOYWINNT.dsc
- 6.2.0-TIV-ITM_SYB-IF0010/koy_aix523_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_aix526_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_li6243_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_li6263_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_lia266_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_lpp266_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_lx8266_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_sol283_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_sol286_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_sol606_tema_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_tems_teps_tepd_if0010.tar
- 6.2.0-TIV-ITM_SYB-IF0010/koy_tems_teps_tepd_if0010.zip
- 6.2.0-TIV-ITM_SYB-IF0010/KOY_winnt_tema_if0010.cab
- 6.2.0-TIV-ITM_SYB-IF0010/koy_patchdepot.bat
- 6.2.0-TIV-ITM_SYB-IF0010/koy_patchdepot.sh
- 6.2.0-TIV-ITM_SYB-IF0010/oy_dd.properties
- 6.2.0-TIV-ITM_SYB-IF0010/oy_dd_062000010.xml

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 there is no uninstall utility for this fix,
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (6.2.0-TIV-ITM_SYB-IF0010
.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 extract utility on Windows systems. This step creates a
directory structure that contains fixes for all supported
operating systems.

3. Use the "itmpatch" command to install the included prerequisite
fix for the target agent operating system. For more information
about the "itmpatch" command, see section [6.2].

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0-TIV-ITM_SYB-IF0010/kdd_xxxxxx_tema_if0012.tar

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

In the following example, the file is
kdd_li6243_tema_if0012.tar:
> ./cinfo -i
Distributed Database common code
li6243 Version: 06.20.01.00

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0-TIV-ITM_SYB-IF0010\kdd_winnt_tema_if0012.cab

4. 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.2].

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0-TIV-ITM_SYB-IF0010/koy_xxxxxx_tema_if0010.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_li6243_tema_if0010.tar:
> ./cinfo -i
Monitoring Agent for Sybase Server
li6243 Version: 06.20.00.00

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0-TIV-ITM_SYB-IF0010\koy_winnt_tema_if0010.cab

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.0-TIV-ITM_SYB-IF0010
.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 extract utility on Windows systems. This step creates a
directory structure that contains fixes for all 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.0-TIV-ITM_SYB-IF0010:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.2.0-TIV-ITM_SYB-IF0010

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

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. From the <TEMP>/6.2.0-TIV-ITM_SYB-IF0010 directory, run the
appropriate script based on the operating system:

koy_patchdepot.bat - Windows
koy_patchdepot.sh <TEMS_Name> - UNIX

This script is provided to copy oy_dd_062000010.xml and
or_dd.properties files from the <TEMP>/6.2.0-TIV-ITM_SYB-IF0010
directory to the 062000000 version of the Tivoli Enterprise
Monitoring Server depot.

Note: The following error messages is displayed during
'tacmd addSystem' if the script is not executed.

================================================================
KUICAR010I: The agent type OY is being deployed.

KUICAR020E: The addSystem command did not complete because
a deployment error occurred. See the following error
returned from the server:

The property DBSETTINGS.db_extparms is invalid for version
062000010 of the OY agent.

The property name is not valid.
================================================================

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

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 062000010

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.

5.4 Agent support update
------------------------------

Fix 6.2.1-TIV-ITM_SYB-IF0009 included changes to the agent
support files that must 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 Portal Server or Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.0-TIV-ITM_SYB-IF0010
.tar 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
operating systems.

3. Expand the archive file (koy_tems_teps_tepd_IF0010.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 the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
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/<operating system>/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.

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, the check
boxes must be as follows:

un-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 Sybase
Server agent 06.20.00.10 support to complete the installation.

6. Because of defect 67530, run the following script to install a
new presentation definition:
On Windows systems, run
$CANDLEHOME\CNPS\BuildPresentation.bat

On UNIX or Linux systems, run
$CANDLEHOME/bin/itmcmd execute cq
$CANDLEHOME/$ARCH/cq/bin/InstallPresentation.sh

7. 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 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 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.3 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 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 (-t) component for the "tacmd listSystems" command is
specified as two characters (oy), not three characters (KOY).

When the agent update is successful, the version of Distributed
Database Common Code is 06.20.01.12, the version of the Sybase
Server agent is 06.20.00.10.

2. To verify that the agent support files were updated correctly,
use the "kincinfo" command on Windows systems or the "cinfo"
command on Linux or UNIX systems. The sample output below shows
the versions of the Tivoli Enterprise Portal Server, Tivoli
Enterprise Monitoring Server, or Tivoli Enterprise Portal
Desktop systems after this fix has been successfully applied.

Note: The displayed date of the build might not be accurate. This
is a known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i
*********** Tue Aug 31 11:02:24 BEIST 2010 ****************
User: root Groups: root bin daemon sys adm disk wheel
Host name : lnxsys Installer Lvl:06.20.00.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
Desktop update:

oy Monitoring Agent for Sybase Server
tps Version: 06.20.00.10

Monitoring Agent for Sybase Server updates:
dd Distributed Database Common Code
li6263 Version: 06.20.01.12

oy Monitoring Agent for Sybase Server
li6263 Version: 06.20.00.10

On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
*************** Tuesday, August 31, 2010 5:51:57 PM *************
User : Administrator Group Group : NA
Host Name : mywinbox Installer : Ver: 062000000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*****************************************************************
...Product Inventory
.
.
.
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
Desktop update:

OY Sybase Server Support
WINNT Version: 06.20.00.10 Build: 201207020000

OY Sybase Server Support
WINNT Version: 06.20.00.10 Build: 201207020000

Monitoring agent for Sybase Server update:

DD Distributed Database Common Code
WINNT Version: 06.20.01.12 Build:

OY Monitoring Agent for Sybase Server
WINNT Version: 06.20.00.10 Build:

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

1. 6.2.0-TIV-ITM_SYB-IF0010 for the Monitoring Agent for Sybase
Server provides new executables to support data collection from
Sybase ASE Server version 12 and Sybase ASE Server version 15.
The depot does not merge the limited availability fix updates
with the base Monitoring Agent for Sybase Server code. For this
reason, the base Monitoring Agent for Sybase Server code must be
in the depot to attempt a new remote deployment of the agent.

To deploy the agent, you must perform the following steps:
a. Deploy the base agent code to the target operating system. See
the IBM Tivoli Monitoring for Databases: Sybase Server Agent
User's Guide for more information on remotely deploying the
agent.
b. After the deployment completes, the agent must be updated for
this limited availability fix using "tacmd updateAgent" or
the GUI (see section 5.3).
c. If the target system is a Windows system, 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 about configuring the
agent.
2. As described in Note 1.c, if an existing Monitoring Agent for
Sybase Server for the Windows operating system is updated with
6.2.0-TIV-ITM_SYB-IF0010, the agent must be reconfigured so
that the Sybase agent collector service switches to using
the new executables.

7.0 Known problems and workarounds
=========================
- Problem: When running remote agent update, a task timeout occurs:

KDY0014E: A timeout occurred while waiting for an agent
task to complete on <hostname>. The agent task did not
complete within the configured time out period.

Workaround: Check if agent has been updated sucessfully by
"tacmd listSystems" on TEMS side or "cinfo -i" on agent side.
If the agent has been updated successfully, you can ignore
the timeout message.

- Problem: Remotely configure the agent from Tivoli Enterprise
Desktop Client after applying 6.2.0-TIV-ITM_SYB-0010, the
'Managed System Configuration' panel 'Settings' tab
does not display the 'Extended Parameters' field, and
the 'Agent' tab shows an incorrect agent version. This
problem occurs in some versions of IBM Tivoli Monitoring
environments.

Workaround: Use the tacmd utility to remotely configure the agent.

- Problem: When running the verification step in the
"itmcmd config -A oy" function on a SLES 9 64-bit system,
the following output from the verification program is
produced: "connect failed, probable cause is
Login/password".

Workaround: Issue "ps -ef | grep koyagent" to locate the
koyagent process and issue "kill -9" for that process.
Check the Navigator tree in the Tivoli Enterprise
Portal for an offline koyagent entry and clear the
offline entry. The Monitoring Agent for Sybase Server
that was configured by "itmcmd config" is unaffected by
this problem.

- Problem: When running the verification step in the "itmcmd
config -A oy" function on a Solaris 10 system, the
following output from the verification program is
produced: "user needs read authority to".

Workaround: Issue "ps -ef | grep koyagent" to locate the
koyagent process and issue "kill -9" for that process.
Check the Navigator tree in the Tivoli Enterprise
Portal for an offline koyagent entry and clear the
offline entry. The Monitoring Agent for Sybase Server
that was configured by "itmcmd config" is unaffected by
this problem.

- Problem: When running multiple remote deployments 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 computer 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 the "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 systems through remote deployment.

Workaround: If you are using WinZip for the fix installation for
the Tivoli Enterprise Monitoring Server on Windows, disable
the default "TAR file smart CR/LF conversion" option.

- Problem: If the Monitoring Agent for Sybase Server is uninstalled
after applying this fix, the KOY and KDD files are
removed, but the KDDWICMA.ver file with patch version
remains. The presence of this KDD .ver file prohibits the
Monitoring Agent for Sybase Server from being successfully
installed again.

Workaround: Delete KDDWICMA.ver manually to allow any new KDD to
be installed.

- 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
======================
This fix provides a mechanism to resolve performances issues
similar to the one listed in APAR IY68094. The default is that the changes
are NOT enabled. You must contact Level 2 support for
further information and recommendations for enabling these
changes after reading the following detailed information.

The cursors that are listed below collect data by calling Sybase
stored procedures. The stored procedures take longer to return
data and consume excessive system resources in some environments.
The agent provides a new 'Extended Parameters' field at
agent configuration time. Typing the cursor name in the field
means that the stored procedure in the cursor is not executed
by the agent when the agent runs. The relative numeric attributes
are set to zero, and the relative non-numeric attributes are set
to null.

These changes include three cursors. The following values can be
assigned in this new field:

DBD2,DBD15,KOYSEGD

Each comma-delimited, no white space, value represents a change
to the SQL cursor that is executed during data gathering operations
within the agent. The values are the SQL cursor name. For example,
setting the 'Extended Parameters' field to DBD15 means that the
DBD15 SQL cursor is enabled for 'Set DBDATAUSEDKB to zero',
'Set DBINDEXUSEDKB to zero', 'Set DBALLOCKB to zero', and
'Set DBUNALLOCKB to zero'. The SQL cursor name is case insensitive.

The 'Extended Parameters' values are saved in the following
locations by operating system:

UNIX(R) file: $CANDLEHOME/config/{hostname}_or_{instance name}.cfg
UNIX variable: db_extparms

Windows(R) Registry Entry: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\
Candle\KOY\610\{Oracle instance name}\
Environment\COLL_DISABLE_CURSORS

The new 'Extended Parameters' field has been added to the following
configuration operations:

1.) Remote deployment - a new GUI field labeled 'Extended Parameters'
and a new db_extparms flag on tacmd. See Section 5.3.
2.) Remote configuration - a new 'Extended Parameters' field is
available during remote manual configuration. See Section 5.3.

Note: Remote configuration from the Tivoli Enterprise Desktop Client
does not show the 'Extended Parameters' field in some environments.
Use the tacmd utility. See Section 7.0.

3.) UNIX local configuration - itmcmd or CandleConfig prompts for a
new 'Extended Parameters' field during manual configuration.
4.) Windows Local configuration - From Tivoli Enterprise Monitoring
Services, 'Configure Using Defaults' has a new 'Extended
Parameters' field in the Monitoring Agent for Sybase Server
Template.

The Monitoring Agent for Sybase Server must be restarted to
recognize these changes to the 'Extended Parameters' value.

In the following paragraphs, each cursor is described in detail.
Using the name of the cursor, you can look in the koycoll.ctl
file for the modification that is made when the cursor is
enabled. The koycoll.ctl file is located in $CANDLEHOME/misc on UNIX
and %CANDLE_HOME%\TMAIMT6 for Windows.

When these cursors are enabled, the Monitoring Agent for Sybase
Server displays default attribute values for these cursors in the
Tivoli Enterprise Portal. The Monitoring Agent for Sybase Server no
longer monitors the attributes of the enabled cursors. For each
cursor, the workspace and column names that are affected are listed.

SQL Cursor: DBD2 - Obtain information from sp_helpdb for each
database.
SQL:
script koy##sql
-logon [KOYV.LOGONID
-rdbms [KOYV.SERVERID
1 " " sp_helpdb [DBD1.DBD1_DBNAME_L;

Enabled:
Attribute Group:
Sybase_Database_Summary (KOYDBS)
Attribute:
set MINDBFREE (Minimum\Pct Data\Freespace) to zero
set MINLOGFREE (Minimum\Pct Log\Freespace) to zero
Attribute Group:
Sybase_Database_Detail (KOYDBD)
Attribute:
Set DBSIZE (Data\Size\(MB)) to zero
Set DBFREE (Data\Freespace\(MB)) to zero
Set LOGSIZE (Log\Size\(MB)) to zero
Set LOGFREE (Log\Freespace\(MB)) to zero
Set PCTDBFREE (Data\Freespace\Percent) to zero
Set PCTLOGFREE (Log\Freespace\Percent) to zero

Navigation tree:
Databases navigator node -> Databases (default)
Workspace:
Databases workspace -> Databases Summary view (table view)
Column:
Minimum\Pct Data\Freespace = 0.00
Minimum\Pct Log\Freespace = 0.00
Situation:
Sybase_DB_Freespace_Critical is always true.
Sybase_Log_Freespace_Critical is always true.

Navigation tree:
Databases navigator node -> Databases (default)
Workspace:
Databases workspace -> Databases Detail view (table view)
Databases workspace -> Percent Freespace (bar chart view)
Column:
Data\Freespace\Percent = 0.00
Log\Freespace\Percent = 0.00
Situation:
No product provided navigator situation.

Navigation tree:
Databases navigator node -> Log and Space Information
Workspace:
Log and Space Information workspace -> Log and Space
Information view
Column:
Data\Size\(MB) = 0.00
Data\Freespace\(MB) = 0.00
Log\Size\(MB) = 0.00
Log\Freespace\(MB) = 0.00
Data\Freespace\Percent = 0.00
Log\Freespace\Percent = 0.00
Situation:
No product provided navigator situation.

--------------------------------------------------------------------

SQL cursor: DBD15 - Obtain information from sp_spaceused for each
database.
SQL:
script koy##sql
-logon [KOYV.LOGONID
-rdbms [KOYV.SERVERID
5 " " sp_spaceused [DBD1.DBD1_DBNAME_L;

Enabled:
Attribute Group:
Sybase_Database_Detail (KOYDBD)
Attribute:
Set USEDSIZE (Used_Size\In_KB) to zero
Set INDEXSZ (Index_Size\In_KB) to zero
Set ALLOCSZ (Allocated\Size_In_KB) to zero
Set UNALLOCSZ (Unallocated\Size_In_KB) to zero

Navigation tree:
Workspace:
No product provided navigator workspace.
Situation:
No product provided navigator situation.

--------------------------------------------------------------------

SQL cursor: KOYSEGD - Obtain segment detail from sp_helpsegment for
each database.
SQL:
script koy##sql
-logon [KOYV.LOGONID
-rdbms [KOYV.SERVERID
6 " " sp_helpsegment [DBLIST.DBNAMES;

Enabled:
Attribute Group:
Sybase_Segment_Detail (KOYSEGD)
Attribute:
Set SEGNAME (Segment\Name) to NULL
Set TOTPAGES (Number of\Total Pages) to zero
Set FREEPAGES (Free\Pages) to zero
Set USEDPAGES (Used\Pages) to zero
Set DBNSEG (Database And\Segment Name) to NULL
Set PCTFREE (Percent\Free Space) to zero

Navigation tree:
Workspace:
No product provided workspace.
Situation:
No product provided situation.

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.

Created/Revised by Date of Creation/Update Summary of Changes
Lisa Li 06 July, 2012 Document created
Lisa Li 07 August, 2012 Revised README file in English, and added translated README files for other 6 languages
Lisa Li 03 June, 2014 Withdraw it, as it had been superseded by 6.2.0-TIV-ITM_SYB-IF0011 and later interim fixes.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is DD?
6.2.0-TIV-ITM_SYB-IF0010.README 20 Jul 2012 English 58484 DD
6.2.0-TIV-ITM_SYB-IF0010.zip 6 Jul 2012 English 39106005 DD
6.2.0-TIV-ITM_SYB-IF0010.tar 6 Jul 2012 English 110356480 DD

Product Alias/Synonym

Sybase Monitoring Agent

Problems (APARS) fixed
IZ05321, IZ11539, IZ17115, IZ31728, IZ32259, IZ49532, IZ51109, IZ51443, IZ52285, IZ56661, IZ61683, IZ63991, IZ66084, IZ67060, IZ67387, IZ68094, IZ70735, IZ73216, IZ73258, IZ80068, IZ89600, IZ92214, IZ94558, IV01440, IV12584

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

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

Software version:

6.2

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

4033006

Modified date:

2014-06-03

Translate my page

Machine Translation

Content navigation