Upgrading Adaptive Server configured with high availability

To upgrade high-availability-enabled Adaptive Server in an active-active configuration:

  1. Drop the high availability companionship.

  2. Use the appropriate command for your cluster system to stop monitoring resources associated with Adaptive Server on each cluster node.

  3. Log in to the server using isql. Disable HA by entering:

    sp_configure 'enable HA', 0 
    go 
    
  4. To complete the change, shut down and restart the Adaptive Server.

  5. Upgrade each Adaptive Server Enterprise separately, following the instructions in the appropriate upgrade chapter of the installation guide for your platform.

  6. Run the new Adaptive Server Enterprise installmaster script against the newly upgraded Adaptive Servers.

  7. Enable the ASE HA property on the new server. Log in to the server using isql and configure the server to enable HA by entering:

    > sp_configure 'enable HA', 1 
    > go 
    
  8. To complete the change, shut down and restart the Adaptive Server.

  9. Run the new Adaptive Server Enterprise installhasvss script against the newly upgraded Adaptive Servers.

  10. 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.

  11. 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 the cluster platform.

  12. Reconfigure each resource associated with Adaptive Server Enterprise, depending on platform-specific requirements. For example, on Veritas Cluster, update the HAase resource properties, the RUN_server_file, and Sybase_home.

  13. Manually restart Adaptive Server Enterprise on each cluster node using trace flag 2209. Use the Adaptive Server Enterprise command line option -T2209.

    WARNING! Do not use trace flag 2209 after the Adaptive Server Enterprise companionship is reestablished.

  14. Use the appropriate command for your cluster system to restart monitoring resources associated with Adaptive Server Enterprise on each cluster node.

  15. Reestablish companionship by using isql to issue:

    sp_companion <primary-server-name>, configure
    go
    

    If user databases exist on the secondary server, you may see one or more warning messages. You can safely ignore these messages, which 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.

  16. Use the appropriate cluster command to take offline, then bring back online, each resource group associated with Adaptive Server Enterprise. Use isql to connect to each Adaptive Server Enterprise and verify the correct server companionship:

    sp_companion 
    go
    

    The output you see on the 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)
    

    The output you see on the 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)
    

To upgrade high-availability-enabled Adaptive Servers in an active-passive configuration:

  1. Use the appropriate cluster system command to take Adaptive Server Enterprise offline.

  2. Use the appropriate cluster system command to stop monitoring resources associated with Adaptive Server Enterprise.

  3. Disable the HA on the server by entering:

    sp_configure 'enable HA', 0 
    go 
    
  4. To complete the change, shut down and restart the Adaptive Server.

  5. Follow the steps in the appropriate upgrade chapter of the installation guide for your platform.

  6. Run the new Adaptive Server Enterprise installmaster script against the newly upgraded Adaptive Server Enterprise.

  7. Log in to the server using isql and configure the server to enable HA by entering:

    sp_configure 'enable HA', 1 
    go 
    
  8. To complete the change, shut down and restart the Adaptive Server.

  9. 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 the cluster platform you are using.

  10. Use the appropriate cluster system command to reconfigure resource properties to reflect the new Adaptive Server Enterprise installation location.

  11. Manually restart Adaptive Server Enterprise.

  12. Use the appropriate cluster system command to restart monitoring resource associated with Adaptive Server Enterprise.

  13. Use the appropriate cluster command to take resources associated with Adaptive Server Enterprise offline on the same node, then bring them back online. Use the cluster command to switch resources associated with Adaptive Server Enterprise to another node and then switch back.