To upgrade an Adaptive Server in a high availability configuration, you must temporarily break the companionship between the primary and secondary companion, and disable monitoring of the Adaptive Server Resource Groups. You can shutdown or restart either Adaptive Server independently during the upgrade process without triggering unexpected failovers by the SunCluster subsystem.
You cannot add, delete, or modify any databases, objects,
users, or logins during the upgrade process. Making these changes
after the companionship is dropped and before it is reestablished
may cause the upgrade to fail or destabilize the cluster by causing
inconsistencies between servers.
Stop the monitoring service and drop companionship
Halt the monitoring service and stop management for the Adaptive Server resource groups on both nodes in the cluster.
As root, issue these commands to bring the SunCluster resource group associated with Adaptive Server offline, and shut down Adaptive Server:
scswitch -F -g primary_resourcegroup_name scswitch -u -g secondary_resourcegroup_name
On both node, disable high availability:
sp_configure 'enable HA', 0
Restart Adaptive Server for this change to take effect.
Alternatively, if the companions are shut down, edit
their server configuration files (server_name.cfg),
changing the value of enable HA to 0
Follow the instructions in the Installation Guide to upgrade each server.
Reenable high availability on both nodes:
sp_configure 'enable HA', 2
You must restart Adaptive Server for the change to take effect. See the Configuration Guide for your platform.
Verify:
Changes are properly reflected in the resource group and resource properties (for example, Sybase_Home, runserver files, Dataserver_login_file, and so on) in the $SYBASE installation location, or any related files related to high availability in the new installation
You have performed all actions required for establishing companionship described “Preparing Adaptive Server for active-passive setup” and "“Configuring the Sun Cluster subsystem” and the system maintains these changes after the upgrade is complete.
Reestablishing companionship and resuming resource
monitoring
Start the resource group (which starts Adaptive Server, if it is not already started) and restore the monitoring service
As root, issue:
scswitch -z -g ase_resourcegroup_name -h primary_node
Failover the primary companion by relocating the associated resource group to secondary node. As root, issue:
scswitch -z -g ase_resourcegroup_name -h secondary_node
Verify Adaptive Server is properly running on the secondary node by checking for the Adaptive Server operating system process and by logging into Adaptive Server with isql.
Failback Adaptive Server by relocating its associated resource group to primary node. As root, issue:
scswitch -z -g ase_resourcegroup_name -h primary_node
Verify Adaptive Server is properly running on the primary node by checking for the Adaptive Server operating system process and by logging into Adaptive Server with isql.
