Upgrading a pre-existing server to the Cluster Edition

You can upgrade to the Cluster Edition from:

Adaptive Server 12.5 through 12.5.3 ESD #6 and,

Adaptive Server 15.0 through 15.0.1 ESD #3.

You cannot use Sybase Central, (ASE plug-in) to upgrade to the Cluster Edition from any server later than 15.0.1 GA or any server version that is not specified in the above list.

The requirements for upgrading are:

that the dataserver for the pre-existing server be on the same system as the cluster UAF agent is running,

and that the install files for the Cluster Edition and the pre-existing server are reacheable from the system on which the UAF agent is running.

This entails that the old server must run on the same system on which the UAF agent for the Cluster Edition runs and on which the newly upgraded cluster will reside.

If you have difficulty connecting to a server or viewing it in the tree view in the left pane, check to make sure the Connection profile found in the toolbar under Tools | Connect contains the port number associated with the server in the interfaces file. If you are using PC-Client on windows you will find the port numbers associated with the server in the sql.ini file.

After you have installed the Cluster Edition for your platform on your computer start ASE plug-in and make sure you can view the old server icon in the left pane. Connect to the old server the same way you would connect to a Cluster Server see “Connecting to a cluster”.

Upgrading your old server

Backup your old server before performing an upgrade. See the Installation Guide for information on backing up your server.

Right click on the old server icon found in the tree view in the left pane and select Upgrade. A wizard opens. Click Next to proceed.

To change the server name enter the new name in the field for Cluster name. The default name is the same name as that of the old server.

Choose the maximum number of instances the cluster server will have. Click Next. The Upgrade wizard will validate the cluster name and check for available hosts.

Select the correct host from the list of available hosts. If no agents for that host are shown, check the protocol settings using the Discovery Settings button.

Enter the administrator’s user name and password for the selected UAF agent. Click Next.

Enter the full release directory path for the old server. Verify that the Adaptive Server and OCS directories for the old server are correct. Click Next.

Enter the full quorum device path and name. For example: /dev/raw/raw21. Click Next.

Sybase recommends that raw devices be used for the quorum. While it is possible to run the quorum on a file device it is not supported.

Check to make sure the paths to the new cluster release area are correct.

You have the option to enter parameters and traceflags. Refer to the Users Guide for more information on parameters and traceflags. Click Next.

Accept the default port number or enter a new one. The wizard will validate the port numbers you enter. If they are not available the wizard will provide a list of available ports from which to select. Check the box if a secondary network is available. Click Next.

Enter name for the instance in the cluster. You have the option to specify start parameters and traceflags for each instance at the instance configuration page. If you want to spcify start parameters and traceflags for the cluster enter those at the cluster configuration page. The port number for the instance is automatically chosen. Accept the default path for the instance log file or enter a new one. Click Next.

To add more instances after upgrade is complete follow the instructions in the section “Adding an instance to a cluster”.

Specify the local temporary database name and size or accept the default. Click Next. At the local system temp db page you can create a device on which to put the LSTDB's. To do this click the Create Device button and enter the path, name and size in the Create Device dialog

Check the box on the summary page to start the server once it is successfully upgraded. Click Next.

The preupgrade check will begin. This may take awhile. If the server is not ready for upgrade preupgrade will return errors. You must fix the errors according to the parameters specified by the wizard’s preupgrade check. This must be done before an uprade can be performed. For information on cluster specific configuration parameters and stored procedures see the Users Guide for the Cluster Edition. Also see the Adaptive Server version of the Installation Guide for your pre-existing Adaptive Server for information on fixing reported errors. You can find these manuals online at the Product Manual Download site.

After you have fixed the reported errors click Retry to run the preupgrade check again. If no errors are returned the Upgrade wizard will upgrade the old server to a Cluster Edition server.

You will see the icon for the new server instead of the icon for the old server in the tree view in the right pane.