Upgrading from an earlier version using Adaptive Server plug-in

You can upgrade to the Cluster Edition from:

Adaptive Server 12.5 through 12.5.3 ESD #6
Adaptive Server 15.0 through 15.0.1 ESD #4

To log in to Adaptive Server plug-in, see instructions starting with “Setting the environment and starting the Unified Agents”.

To upgrade:

The Dataserver for the pre-existing server must be on the same system as the cluster UAF agent is running,
You must be able to reach the install files for the Cluster Edition and the pre-existing server from the system on which the UAF agent is running.

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

If you cannot connect to a server or view it in the tree view in the left pane, confirm that the Connection profile—in the toolbar under Tools | Connect—contains the port number associated with the server in the interfaces file (sql.ini for PC-Client).

After you install the Cluster Edition, start the Adaptive Server 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

Back up your old server before performing an upgrade.

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. See the Users Guide to Clusters for more information on parameters and traceflags. Click Next.

Accept the default port number of the range of interconnect ports, which are not to be confuesd with instance query ports (see Chapter 19, “Setting Up Communications Across Networks” in the Users Guide to Clusters for mroe information on the latter).

The wizard validates the range of ports starting with the port number you enter. If none are available, the wizard provides a list of all unavailable ports in the range. Check the box if a secondary network is available.

Click Next.

Enter a name for the instance in the cluster created in the upgrade process. After the cluster is created, you can add instances up to the number of instances you specified as the maximum for the cluster. You have the option to specify start parameters and traceflags for each instance at the instance configuration page.

If you want to specify start parameters and traceflags for the cluster, enter those at the cluster configuration page. 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 system temporary database name and size or accept the default. If you plan to create all local system temporary databases including those for instances to be added later, the device must be large enough to accommodate all local system temporary databases. 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.

You can create local system temporary database on shared disks only. See Chapter 6, “Using temporary databases” in Users Guide to Clusters for more information about using local disks for temporary data.
Check the box on the summary page if you wish to start the server once it is successfully upgraded. Click Next.

The preupgrade check will begin. This may take a while. 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 upgrade can be performed.

The wizard lets you change things such as your configuration options and database size, and correct most errors that require fixes without closing it.

For information on cluster specific configuration parameters and stored procedures see the Users Guide to Clusters. 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 left pane.