InfoScale™ 9.0 Cluster Server Agent for Sybase Installation and Configuration Guide - AIX
- Introducing the Cluster Server agent for Sybase
- About the Sybase agent functions
- Installing and configuring Sybase
- VCS requirements for installing Sybase
- VCS requirements for installing Sybase
- Installing, upgrading, and removing the agent for Sybase
- Configuring VCS service groups for Sybase
- Before configuring the service group for Sybase
- About setting up detail monitoring for the agent for Sybase
- Administering VCS service groups for Sybase
- Appendix A. Resource type definitions for Sybase
- Appendix B. Sample configurations for Sybase
Changes required in Sybase RUN_Server file for AMF offline monitoring
On AIX platform, the pattern registered with AMF kernel driver for offline monitoring must appear within first 79 characters of the process command line. Due to this AMF kernel driver limitation, the changes required in Sybase RUN_Server file for AMF offline monitoring are described below.
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 first 79 character of the process command line.
A process having a longer pathname is truncated in the table, making it unrecognizable. However, the Sybase home directory ($SYBASE) may have such a long pathname. In this case, you can create a soft link to the $SYBASE directory and use the same soft link instead of the long pathname in the appropriate Sybase installation files. Therefore, 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:
- On each system in the cluster, create a soft link to the long pathname.
For example:
# ln -s /opt/apps/sybase/home/directory/is/longer/than\ eighty/characters/sybase /opt/link_to_longpath
The process gets invoked with the short pathname of the soft link.
- 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\
- 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 79 characters of the file.
For example, if you do not put the -s option and the argument in the first 79 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 79 characters of the command string for the same example will be 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 79 characters.