beautypg.com

Upgrading high availability – Sybase ADAPTIVE 15.0.2 User Manual

Page 99

background image

CHAPTER 5 Upgrading Adaptive Server

Installation Guide

83

Upgrading high availability

Using the following steps to upgrade high availability-enabled Adaptive
Server in active-active configuration:

1

Drop the high availability companionship. On the secondary server, use

isql

:

sp_companion <primary_server_name>, "drop"

go

2

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

3

Follow the upgrade steps in “To assist with the upgrade process, Sybase
recommends you set the OLDSYBASE, OLDSYBASE_ASE, and
OLDSYBASE_OCS environment variables to point to the old
installation of Adaptive Server. If you set these environment variable to
the old installation of the Adaptive Server, the upgrade utility
automatically populates input fields with the correct information as you
upgrade.” on page 65
to upgrade each of the Adaptive Servers separately.

4

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

5

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

6

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.

7

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.

8

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.

9

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.