Using the following steps to upgrade high availability-enabled Adaptive Server in active-active configuration:
Drop the high availability companionship. On the secondary server, use isql:
sp_companion <primary_server_name>, "drop" go
Use the cluster system command to stop monitoring resources associated with Adaptive Server on each cluster node.
Follow the upgrade steps in “Upgrading to Adaptive Server 15.0” to upgrade each of the Adaptive Servers separately.
Run the new Adaptive Server installmaster script against the newly upgraded Adaptive Servers.
Run the new Adaptive Server installhasvss script against the newly upgraded Adaptive Servers.
In the new Adaptive Server installation area, follow the instructions in Using Sybase Failover in A High Availability System to configure the permission and ownership for $SYBASE/$SYBASE_ASE/bin/sybha and $SYBASE/$SYBASE_ASE/install/sybhauser.
In the new Adaptive Server installation area, modify high availability-related files such as the RUN_server_file, and the SYBASE.csh and SYBASE.sh files, if those files are required on that cluster platform.
Reconfigure each resource associated with Adaptive Server depending on platform-specific requirements. For example, on Veritas Cluster, the HAase resource properties, the RUN_server_file, and Sybase_home need to be updated.
Manually restart Adaptive Server on each cluster node with trace flag 2209. Use the Adaptive Server command-line option -T2209.
WARNING! Do not use trace flag 2209 after the Adaptive Server companionship is re-established.
Use the cluster system command to restart monitoring resources associated with Adaptive Server on each cluster node.
Re-establish companionship by using isql to issue:
sp_companion <primary_server_name>, configure go
If user databases exist on the secondary server, warning message may display on the console. There is no need to take any action. You can safely ignore them. The messages look similar to:
Msg 18739, Level 16, State 1:
Server 'svr2', Procedure 'sp_hacmpcfgvrfy', Line 102:
Database 'svr2_db1': a user database exists. Drop this
database and retry the configuration again.
Use the cluster command to offline and then online resource associated with Adaptive Server. Use isql to connect to each Adaptive Server and enter the command to verify the correct server companionship:
sp_companion go
Console output on primary server is similar to the following:
Server 'svr1' is alive and cluster configured. Server 'svr1' is configured for HA services. Server 'svr1' is currently in 'Primary normal' mode. (return status = 0)
Console output on secondary server is similar to the following:
Server 'svr2' is alive and cluster configured. Server 'svr2' is configured for HA services. Server 'svr2' is currently in 'Secondary normal' mode. (return status = 0)
Use the following steps to upgrade high availability-enabled Adaptive Servers in active-passive configuration:
Use the cluster system command to offline Adaptive Server.
Use the cluster system command to stop monitoring resources associated with Adaptive Server.
Follow the upgrade steps provided in “Upgrading to Adaptive Server 15.0” to upgrade the Adaptive Server to the new version.
Run the new Adaptive Server installmaster script against the newly upgraded Adaptive Server.
In new Adaptive Server installation area, modify the high availability-related files such as the RUN_server_file, and the SYBASE.csh and SYBASE.sh files, if those files are required on that cluster platform.
Use the cluster system command to reconfigure resource properties associated with Adaptive Server to reflect the new Adaptive Server installation location.
Manually restart Adaptive Server.
Use the cluster system command to restart monitoring resource associated with Adaptive Server.
Use the cluster command to offline and then online resource associated with Adaptive Server on the same node. Use the cluster command to switch resource associated with Adaptive Server to another node and then switch back.
