InfoScale™ 9.0 Cluster Server Agent for Sybase Installation and Configuration Guide - Solaris
- Introducing the Cluster Server for Sybase
- About the Cluster Server for Sybase
- Supported software for the VCS agent for Sybase
- How the agent makes Sybase highly available
- How the Sybase and SybaseBk agents support intelligent resource monitoring
- About the Sybase agent functions
- Monitoring options for the Sybase agent
- Action function for the VCS agent for Sybase
- Typical Sybase configuration in a VCS cluster
- Installing and configuring Sybase
- Installing, upgrading, and removing the agent for Sybase
- Configuring VCS service groups for Sybase
- About configuring service groups for Sybase
- Before configuring the service group for Sybase
- Configuring the service groups for Sybase
- Configuring the service group for Sybase from Cluster Manager (Java console)
- Configuring the service group for Sybase using the command line
- Encrypting passwords for Sybase
- About setting up detail monitoring for the agent for Sybase
- Enabling and disabling intelligent resource monitoring (IMF) for agents
- Administering the AMF kernel driver
- Administering VCS service groups for Sybase
- Appendix A. Resource type definitions for Sybase
- Appendix B. Sample configurations for Sybase
- About the sample configuration for the Sybase agent
- Resource dependency graph for the Sybase agent
- Sample configuration for agent for Sybase on Solaris systems
- Sample main.cf files for Sybase ASE CE configurations
- Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
- Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
- Sample main.cf for a primary CVM VVR site
- Sample main.cf for a secondary CVM VVR site
- Sample configuration for the Sybase agent in Solaris zones
Upgrading the agent for Sybase
This section describes the procedure to upgrade the VCS agent for Sybase in a Cluster Server (VCS) cluster. Execute the following steps on each node of the VCS cluster.
Note:
For details on the supported upgrade paths for the agent, refer to the Configuration and Upgrade Guide for your product.
To upgrade the VCS agent for Sybase
- Save the VCS configuration and stop the VCS engine.
# haconf -dump -makero # hastop -all -force
- Back up the configuration file, main.cf to a location on the cluster node.
- Based on your current VCS Agent version for Sybase, perform the appropriate steps on all systems that have the agent installed:
To
Perform the following steps
Upgrade the VCS agent from a version earlier than 5.1
Remove the VCS agent for Sybase, by using the following command:
# pkgrm VRTSvcssy
If you installed the Japanese language package, use the following command:
# pkgrm VRTSjacss
Take backup of SybaseTypes.cf
# mv /etc/VRTSvcs/conf/config/SybaseTypes.cf /etc/VRTSvcs/conf/config/SybaseTypes.cf_bkp
Navigate to the directory that contains the packages:
# cd pkgs
Install the VCS agent for Sybase by running the following command:
Caution:
If you run the following command, the VCS agents for Oracle and DB2 are also upgraded.
# pkgadd -d VRTSvsea
Upgrade the VCS agent from 5.1 or later
Remove the VCS agent for Sybase using the following command:
# pkgrm VRTSvcsea
If you have installed the Japanese language package, run the following command:
# pkgrm VRTSjacse
Take backup of SybaseTypes.cf
# mv /etc/VRTSvcs/conf/config/SybaseTypes.cf /etc/VRTSvcs/conf/config/SybaseTypes.cf_bkp
Navigate to the directory that contains the packages:
# cd pkgs
Install the VCS agent for Sybase by running the following command:
Caution:
If you run the following command, the VCS agents for Oracle and DBw are also upgraded.
# pkgadd -d VRTSvsea.pkg
- Make sure that you have copied the SybaseTypes.cf file from the /etc/VRTSagents/ha/conf/Sybase/ directory to /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied SybaseTypes.cf file with all the type-level changes that you had made to the older SybaseTypes.cf file.
For example, if you had changed the value of the MonitorInterval attribute from the default 60 to 120 seconds, the SybaseTypes.cf file gets updated. You must apply these type-level changes manually to the newly copied SybaseTypes.cf file.
- Copy the main.cf file from the backed up location to /etc/VRTSvcs/conf/config directory.
Edit the main.cf file located under /etc/VRTSvcs/conf/config.
If you configured detail monitoring, make sure the Monscript attribute of the Sybase resource type is properly configured.
Remove the Monscript attribute for the SybaseBk resource type, if configured.
Replace the password specified for the SApswd attribute (of Sybase and SybaseBk resources) and UPword attribute (of Sybase resource) with encrypted passwords.
Save the main.cf file.
- Verify the configuration.
# cd /etc/VRTSvcs/conf/config # hacf -verify
- Start VCS on the local node.
- Start VCS on the other nodes.