Before you begin the upgrade process, install the Cluster Edition onto your system in a new location.
The upgrade process modifies the sysaudits tables
in the sybsecurity database. Sybase recommends
that you archive any auditing data and truncate these tables before
you upgrade. This reduces the chances of a failed upgrade due to
lack of space in the sybsecurity database.
To ensure a successful upgrade, review this list of pre-upgrade tasks and perform them as necessary. Depending on the old server configuration, you may not need to perform all pre-upgrade tasks:
Check system and upgrade requirements. See “Checking system and upgrade requirements”.
Check the location of the RUN_server file. See “Checking the runserver file location”.
If you are upgrading Adaptive Server, the previously installed version of the server must be running. If you are upgrading Backup Server, Historical Server, Monitor Server, or XP Server, those servers must not be running.
Stored procedure text in the syscomments table is required for upgrade. See “Procedure text is required for upgrade”.
Resolve reserved words using quoted identifiers. See “Reserved words”.
Verify users are logged off.
Check for database integrity.
Back up the databases.
Dump the transaction log.
Ensure that master is the default database for the “sa” user.
Prepare the database and devices for upgrade.
Disable auditing
Archive auditing data and truncate auditing tables.
Disable disk mirroring.
Adaptive Server Enterprise 15.0.1 Cluster Edition ESD #1
does not support disk mirroring.
Verify that your $SYBASE environment variable points to the location of the new Adaptive Server software files you just unloaded.
If the $SYBASE directory is not the same as the old $SYBASE directory, copy the following files from earlier versions of Adaptive Server to their corresponding Cluster Edition installation:
$SYBASE/interfaces
$SYBASE/<servername>.cfg
$SYBASE/$SYBASE_OCS/config/libtcl.cfg
