You can upgrade to Adaptive Server 15.0.3 from any of these versions:
12.5.x (except 12.5.3a)
15.x (except 15.0.1 Cluster Edition)
Adaptive Server version 15.0.3 does not support upgrade
from Adaptive Server version 12.5.3a.
For a server installation 12.0.x and older, Sybase recommends that you upgrade to version 12.5.4, then upgrade to version 15.0.3.
You can upgrade Adaptive Server from a 32-bit version to a 64-bit version, but you cannot move from a 64-bit version to a 32-bit version. Likewise, you can upgrade only from an earlier version of Adaptive Server to a more recent version.
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:
Install Adaptive Server 15.0.3 into the %SYBASE% directory along with the old version of Adaptive Server.
You must have both the old installation and the new
installation to perform an upgrade.
If your server is a pre-15.x version then, from the 15.0.3 server installation, perform the pre-upgrade checks on the old server using the preupgrade utility, which is located at %SYBASE%\%SYBASE_ASE%\upgrade. If necessary, fix any problems that pre-upgrade 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.
preupgrade runs against the pre-15.0.x 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:
Shut down the pre-15.0.x server.
Copy the server entry from the old interfaces file to the new interfaces file
copy the <server_name>.cfg file from old directory to new $SYBASE
Start 15.0.3 server with the old master device
Run the upgrade process. If problems occur, fix them and then run the upgrade process again.
Reinstall Sybase-supplied stored procedures to prevent any errors caused from changes to system catalogs.
Adaptive Server issues advisory warnings when configuration parameters
are not set to the default. These do not require any action.
The preupgrade and upgrade utilities are internally called by syconfig.exe or sybatch.exe.
Only sybatch.exe supports an upgrade from a 32-bit server to a 64-bit server. syconfig.exe does not support an upgrade from a 32-bit server to a 64-bit server.
Each new version of Adaptive Server contains features that introduce new parameters, commands, reserved words, and so on. For this reason, preupgrade is needed to prepare the old server for upgrade. It is not necessary to start the server before running sqlupgrade. sqlupgrade starts the server when needed. However, if you are running preupgrade, then you must manually stop and start the server.
syconfig.exe, sybatch.exe, or preupgrd.exe runs various checks to determine how much space you must add to the old server to successfully upgrade the old server to the new.
As part of the pre-upgrade tasks, syconfig.exe, sybatch.exe, or preupgrd.exe scans all databases and catalogs and determines how much free space is required to upgrade successfully. Essentially, syconfig.exe, or sybatch.exe searches for the largest catalog, then calculates the required free space by doubling the size of the largest catalog, and adding approximately 10 percent for logging the upgrade changes for each catalog.
During the pre-upgrade process, syconfig.exe, sybatch.exe, or preupgrd.exe returns informational messages as it checks the old server. You must fix all reported problems, and run syconfig.exe, sybatch.exe, or preupgrd.exe cleanly before beginning the upgrade process. Once the old server is eligible to be upgraded, syconfig.exe, or sybatch.exe, shuts down the old server, starts the new server against the existing databases, and begins the upgrade process.
Following an upgrade to other platforms, Adaptive Server internally rebuilds procedures from the text in syscomments the first time Adaptive Server is executed. The procedure may not execute properly if it has 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.
