InfoScale™ 9.0 Cluster Server Agent for Sybase Installation and Configuration Guide - AIX

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: AIX
  1. Introducing the Cluster Server agent for Sybase
    1.  
      About the Cluster Server agent for Sybase
    2.  
      Supported software for the VCS agent for Sybase
    3.  
      How the agent makes Sybase highly available
    4.  
      How the Sybase and SybaseBk agents support intelligent resource monitoring
    5. About the Sybase agent functions
      1.  
        Sybase agent functions
      2.  
        SybaseBk agent functions
      3.  
        Using the IPC Cleanup feature for the Sybase agent
    6.  
      Monitoring options for the Sybase agent
    7.  
      Action function for the VCS agent for Sybase
    8.  
      Typical Sybase configuration in a VCS cluster
  2. Installing and configuring Sybase
    1. VCS requirements for installing Sybase
      1.  
        Sybase installation directory
      2.  
        SYBASE directory on shared disks
      3.  
        System Group and User for Sybase home directory
      4.  
        Database dbspaces
      5.  
        Transparent TCP/IP failover
      6.  
        Changes required in Sybase RUN_Server file for AMF offline monitoring
      7.  
        Language settings for the Sybase agent
      8.  
        AMF kernel driver limitation for process offline event notification
    2.  
      Installing Sybase in a VCS environment
    3.  
      Configuring Sybase for detail monitoring
  3. Installing, upgrading, and removing the agent for Sybase
    1.  
      Before you install or upgrade the agent for Sybase
    2.  
      Installing the agent for Sybase
    3.  
      Disabling the agent for Sybase
    4.  
      Removing the agent for Sybase
    5.  
      Upgrading the agent for Sybase
  4. Configuring VCS service groups for Sybase
    1.  
      About configuring service groups for Sybase
    2. Before configuring the service group for Sybase
      1.  
        Importing the SybaseTypes.cf file
    3.  
      Configuring the service groups for Sybase
    4.  
      Configuring the service group for Sybase from Cluster Manager (Java console)
    5.  
      Configuring the service group for Sybase using the command line
    6.  
      Encrypting passwords for Sybase
    7. About setting up detail monitoring for the agent for Sybase
      1.  
        Enabling detail monitoring for the agent for Sybase
      2.  
        Disabling detail monitoring for the agent for Sybase
    8.  
      Enabling and disabling intelligent resource monitoring (IMF) for agents
    9.  
      Administering the AMF kernel driver
  5. Administering VCS service groups for Sybase
    1.  
      About administering service groups for Sybase
    2.  
      Bringing the Sybase service group online
    3.  
      Taking the Sybase service group offline
    4.  
      Switching the Sybase service group
    5.  
      Modifying the Sybase service group configuration
    6.  
      Viewing the agent log for Sybase
  6. Appendix A. Resource type definitions for Sybase
    1.  
      About the resource type and attribute definitions for Sybase
    2. Sybase resource type
      1.  
        Type definition for the Sybase agent
      2.  
        Attribute definitions for the Sybase agent
    3. SybaseBk resource type
      1.  
        Type definition for the SybaseBk agent
      2.  
        Attribute definitions for the SybaseBk agent
  7. Appendix B. Sample configurations for Sybase
    1.  
      About the sample configuration for the Sybase agent
    2.  
      Resource dependency graph for the Sybase agent
    3.  
      Sample configuration for a Sybase service group on AIX systems

AMF kernel driver limitation for process offline event notification

On AIX platform , the pattern registered with AMF kernel driver for offline monitoring must appear within first 79 characters of the process command line. For offline IMF monitoring, Sybase agent registers the Sybase server binary name (dataserver/backupserver) and instance name with the AMF kernel driver. hence for IMF offline monitoring to provide event notification correctly, Sybase instance name must appear in the first 79 characters of the process command line.

A process having a longer pathname is truncated in the table, making it unrecognizable. The Sybase home directory ($SYBASE) could possibly have such a long pathname. In this case, you can create a soft link to the $SYBASE directory and use it in place of the long file name in the appropriate Sybase installation files.

Using a soft link pathname avoids the problems that arise due to the long pathname.

After creating the soft link on each system, you must edit the following files by making the appropriate substitutions:

  • The file RUN_Server in the directory $SYBASE/$SYBASE_ASE/install.

  • The file RUN_Server_back in the directory $SYBASE/$SYBASE_ASE/install.

If you are using RUN_Server files from non-default location, edit the respective files.

The following example demonstrates how to replace a $SYBASE pathname with a soft link.

To replace a $SYBASE pathname with a soft link

  1. On each system in the cluster, create a soft link to the long path name.
    # ln -s /opt/apps/sybase/home/directory/is/longer/than\
eighty/characters/sybase /opt/link_to_longpath

    Now the process is invoked with the short pathname of the soft link.

  2. Edit the RUN_Server file.

    Example: The file RUN_Server resembles the following before the change:

    /opt/apps/sybase/home/directory/is/longer/than/eighty
/characters/sybase/ASE-12_5/bin/dataserver\
-d/dev/vx/rdsk/db_dg1/vol2\
-e/opt/apps/sybase/home/directory/is/longer
/than/eighty /characters/sybase/install/fw17i.log\
-M/opt/apps/sybase/home/directory/is/longer/than/eighty
/characters/sybase\
-sfw17i\
After the replacement, the file resembles as follows:
/opt/link_to_longpath/ASE-12_5/bin/dataserver\
-sfw17i\
-d/dev/vx/rdsk/db_dg1/vol2\
-e/opt/link_to_longpath/install/fw17i.log\
-M/opt/link_to_longpath\

  3. Make sure that the -s option and its argument (fw17i in the example) are the first to be listed. It must be placed within the first eighty characters of the file.

    For example, if you do not put the -s option and the argument in the first eighty characters, the command string that will be considered is as follows: 

    /opt/apps/sybase/home/directory/is/longer/than/eighty
/characters/sybase/ASE-12_5/

    In this case, the -s option is omitted and the AMF kernel driver fails to match the registered pattern and does not notify the process creation event. However, if you move the -s to be the first option, the first 80 characters of the command string for the same example appear as follows:

    /opt/link_to_longpath/ASE-12_5/bin/dataserver\
-sfw17i\
-d/dev/vx/rdsk/db_dg1/vol2

    In this case, the -s option is among the first eighty characters.