Overview of the upgrade process

You can upgrade to Adaptive Server 15.0 from any of these versions:

NoteAdaptive Server version 15.0 does not support upgrade from Adaptive Server version 12.5.3a.

For a server installation 11.5.x and older, Sybase recommends that you upgrade to version 12.0, then upgrade to version 15.0.

Only upgrades to and from the same page size are supported. Changing the server schema from one page size to another is a database migration. See sybmigrate in the Utility Guide for information about migration.

Upgrading Adaptive Server consists of three processes:

  1. Install the new server into its own installation directory.

    NoteYou must have both the old installation and the new installation to perform an upgrade.

  2. From the new server installation, perform the pre-upgrade checks on the old server using the preupgrade utility which is located at $SYBASE/ASE-15_0/upgrade. If necessary, fix any problems that pre-upgrade process reports.

  3. preupgrade runs against the old servers. It checks that all required databases exist and that they are large enough. It verifies that stored procedures have the text required for upgrade, and that configuration parameters are correct for the new server and for upgrading. It verifies that datatype definitions do not conflict with the new server’s requirements. When preupgrade runs without reporting any errors, you can then:

    NoteAdvisory warnings are issued when configuration parameters are not set to the default. These do not require any action.

The preupgrade and upgrade utilities are internally called by sqlupgrade or sqlupgraderes.

Each new version of Adaptive Server contains features that introduce new parameters, commands, reserved words, and so on. For this reason, preupgrade is for preparing the old server for upgrade.

sqlupgrade, sqlupgraderes, or preupgrade runs various checks to determine how much space you must add to the old server to successfully upgrade.

As part of the pre-upgrade tasks, sqlupgrade, sqlupgraderes, or preupgrade scans all databases and catalogs and determines how much free space is required to upgrade successfully. sqlupgrade,sqlupgraderes, or preupgrade searches for the largest catalog, then calculates the required free space by doubling the size of the largest catalog, and adding 10 percent for logging the upgrade changes for each catalog.

During the pre-upgrade process, sqlupgrade, sqlupgraderes, or preupgrade returns informational messages as it checks the old server. You must fix all reported problems, and run sqlupgrade, sqlupgraderes, or preupgrade cleanly before beginning the upgrade process. Once the old server is eligible to be upgraded, sqlupgrade, sqlupgraderes, or preupgrade shuts down the old server, starts the new server against the existing databases, and begins the upgrade process.