Upgrading the Old Server with ASE Plug-in

Learn how to upgrade your server using ASE plug-in.

1. Back up your old server before performing an upgrade.
2. Right-click on the old-server icon in the tree view in the left pane and select Upgrade. A wizard opens.
3. 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.
4. Choose the maximum number of instances the cluster server will have. Click Next. The Upgrade wizard validates the cluster name and checks for available hosts.
5. 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.
6. Enter the administrator’s user name and password for the selected UAF agent. Click Next.
7. Enter the full release directory path for the old server, verifying that the Adaptive Server and OCS directories for the old server are correct. Click Next.
8. Enter the full quorum device path and name, such as /dev/raw/raw21. Click Next.
   Note: Sybase recommends that you use raw devices for the quorum; although it is possible to run the quorum on a file device, this is not supported.
9. 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 Cluster Users Guide for more information on parameters and traceflags. Click Next.
10. Accept the default port number of the range of interconnect ports; do not confuse these with instance query ports. See Chapter 19, “Setting Up Communications Across Networks” in the Users Guide to Clusters for more information on the latter. If you choose a different port number, starting with the port number you enter, the wizard validates the range of ports. If none are available, the wizard provides a list of all unavailable ports in the range.
    1. Check the box if a secondary network is available.
    2. Click Next.
11. 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 can specify start parameters and traceflags for each instance at the instance configuration page.

    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.

    Note: See the Adding an Instance to a Cluster topic for how to add more instances after upgrade is complete.
12. 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 you plan to add later, the device must be large enough to accommodate all local system temporary databases. Click Next. At the local system tempdb page, you can create a device on which to put the local system temporary databases by clicking the Create Device button and entering the path, name and size in the Create Device dialog.

    You can create local system temporary database only on shared disks. See Chapter 6, “Using temporary databases,” in Users Guide to Clusters for more information about using local disks for temporary data.

13. Check the box on the summary page if you wish to start the server once it is successfully upgraded. Click Next. The preupgrade check begins; this may take a while. If the server is not ready for upgrade, preupgrade returns errors, which you must fix according to the parameters specified by the wizard’s preupgrade check before you can perform a successful upgrade.
    Note: The wizard lets you change things such as your configuration options and database size, and correct most errors that require fixes without closing it.
    See the Users Guide to Clusters for information on cluster-specific configuration parameters and stored procedures. Also see the Adaptive Server version of the installation guide for your pre-existing Adaptive Server for information on fixing reported errors. These manuals are available at The Product Manual Download site
14. After you fix the reported errors, click Retry to run preupgrade again. If you see no errors, the Upgrade wizard upgrades the old server to a Cluster Edition server, and when finished, you see the icon for the new server instead of the icon for the old server in the tree view in the left pane.