---------------------------------------------------------------------------
Interim Fix: 0002, 6.2.0.2-TIV-ITM_SYB-IF0002
---------------------------------------------------------------------------

Date: 28 June, 2023

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 that are listed in the "Problems Fixed" section below. 

2.0 Problems fixed

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

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

4.0 Image directory contents

5.1 Before installing the fix 
-------------------------------
 - The prerequisites listed in section 3.1, '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.

 5.2 Local agent update
 --------------------------
 1. Transfer the appropriate archive file (6.2.0.2-TIV-ITM_SYB-IF0002 .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 by 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. 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.2, Additional information on using "itmpatch" command.      

 On UNIX systems, if the fix was expanded to <TEMP>/6.2.0.2-TIV-ITM_SYB-IF0002, the install command is as follows:
     
     > ./itmpatch -h <CANDLEHOME> 
       -i <TEMP>/6.2.0.2-TIV-ITM_SYB-IF0002/koy_xxxxxx_tema_IF0002.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_IF0002.tar: 
         > ./cinfo -i
          Monitoring Agent for Sybase Server

On Windows systems, if the fix was expanded to <TEMP>\6.2.0.2-TIV-ITM_SYB-IF0002, the install command is as follows:

     > itmpatch -h <CANDLEHOME> 
       -i <TEMP>\6.2.0.2-TIV-ITM_SYB-IF0002\koy_winnt_tema_IF0002.cab
               

5.3 Remote agent update
 -----------------------------
1. Transfer the appropriate archive file, 6.2.0.2-TIV-ITM_SYB-IF0002 .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 by 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 remote agent update of 6.2.0.2 Interim Fix 2, the prerequisite is to add 6.2.0 Fix Pack 2 agent bundles into remote deploy depot. 
 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.2-TIV-ITM_SYB-IF0002:
     > $CANDLEHOME/bin/tacmd addBundles -n 
       -i <TEMP>/6.2.0.2-TIV-ITM_SYB-IF0002

   

    On Windows systems, if the fix was expanded to <TEMP>\6.2.0.2-TIV-ITM_SYB-IF0002:
     > %CANDLE_HOME%\bin\tacmd addBundles -n 
       -i <TEMP>\6.2.0.2-TIV-ITM_SYB-IF0002
     
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, Prerequisites for this fix, 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 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
                -n <Managed system name>
                -v 062002002

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

                  -t oy
                              
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

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

 This fix (6.2.0.2-TIV-ITM_SYB-IF0002) does not include changes to the agent support files. 
   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 Additional information on using "itmpatch" command
 --------------------------------------------------------------
The "itmpatch" command has the following syntax:

  Usage: itmpatch -h <installation home> [OPTIONS]

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

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.2-TIV-ITM_SYB-IF0002 for the Monitoring Agent for Sybase Server provides new executables to support data collection from Sybase ASE Server version 15 and Sybase ASE Server version 16.
 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 deploy completes, the agent must be updated for this limited availability fix by 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 on configuring the agent.

2.) As described in point c, if an existing Monitoring Agent for Sybase Server for the Windows operating system is updated with 6.2.0.1-TIV-ITM_SYB-IF0002, then 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: On the non-windows platforms, the disabled cursor cannot be enabled. 

WORKAROUND: Pass non-existing cursor name

For example: test as extended parameter during configuration.

PROBLEM: Sybase Agent 6.2.0.2 Interim Fix 01 remote upgrade failed on Solaris 11 machine 

WORKAROUND: Apply 6.2.0.2 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 by 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 by 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: Workaround is not available.  

              

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

              export COLL_HOSTNAME=<short name>   

8.0 Additional product information

9.0 Notices

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.