Preparing to Upgrade

You must have system administrator privileges to perform an upgrade.

Note:

If your server has replicated databases, consult Upgrading Servers with Replicated Databases, before starting the preupgrade tasks.

Also, if you are upgrading from Adaptive Server 12.5.4 or earlier, execute the upgrade sequence from the same node on which the database resides.

If your server is already at a 15.x level, do not upgrade using sqlupgrade or sqlupgraderes. The message “Adaptive Server is already at version 15.0” appears if you are already at a 15.0 level. All required changes happen automatically while the first time you start the new server. The preupgrade and upgrade utilities are internally called by sqlupgrade or sqlupgraderes.

Each new server version contains features that introduce new parameters, commands, reserved words, and so on. preupgrade prepares the old server for upgrade by checking to make sure all necessary directories and settings are correct for the upgrade. When running preupgrade, manually stop and start the server. It is not necessary to start the server before running sqlupgrade. sqlupgrade starts the server when needed.

  1. Install Adaptive Server 15.5 into its own installation directory.
  2. If you are upgrading from a 12.5.3 installation with cache bindings on sybsystemdb, before running preupgrade, drop the cache bindings for sybsystemdb that are bound to a user-defined cache.
  3. If your server is a pre-15.x version then, from the 15.5 server installation, perform the preupgrade checks on the old server using the preupgrade utility, which is located at $SYBASE/ASE-15_0/upgrade. If necessary, fix any problems that preupgrade process reports. If your server is already at Adaptive Server 15.x or later most of this process is automatic when you install the new server.
  4. When preupgrade runs without reporting any errors, you can then:
    1. Shut down the pre-15.x server.
    2. Copy the server entry from the old interfaces file to the new interfaces file.
    3. copy the <server_name>.cfg file from old directory to the new $SYBASE directory.
    4. Start the 15.5 server with the old master device from the old server.
    5. Run the upgrade process. If problems occur, fix them and then re-run the upgrade process.
    6. Reinstall the Sybase-supplied stored procedures to prevent any errors caused from changes to the system catalogs.
    Note:

    Adaptive Server issues advisory warnings when configuration parameters are not set to the default. No action is required.

  5. Following an upgrade to other platforms, the server internally rebuilds procedures from the text in syscomments the first time the server is executed. The procedure may not execute properly if it contains code that drops an existing object and recreates it. This is a problem when the object already exists at the time the procedure is first executed. To avoid problems, manually drop the object prior to executing the procedure for the first time.

As part of the preupgrade tasks, preupgrade scans all databases and catalogs and determines how much free space is required to upgrade successfully. 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.