To ensure a successful
upgrade, review and perform
the preupgrade tasks as necessary. Depending on the old server configuration, you may
not need to perform all preupgrade tasks.
Prerequisites
If you are upgrading Adaptive Server:
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.
Stored procedure text in the syscomments table
is required for upgrade.
Shut down the clusters that use an earlier version
of the Cluster Edition.
Install the Cluster Edition onto your system
in a new location.
Check system and upgrade
requirements.
Verify the name and location of the runserver file, as well as that you renamed it to RUN_servername, where servername is
the name of the old server, as it appears in the interfaces file.
The default RUN_servername file
for a server SYBASE is called RUN_SYBASE.
If the RUN_servername file for your
current server is named differently, use the actual name of your server during the upgrade process.
While the upgrade process for Adaptive Server requires that the previously
installed version of the server is running, the upgrade process for Backup Server, Historical Server, and XP Server, requires those servers to be shut down.
Verify that the text of all stored procedures you upgrade is available in syscomments by either:
Reinstalling the procedures with text, or,
Removing and reinstalling the procedures after the upgrade.
This step can allow you to inspect the stored procedures for any hidden or unwanted text.
Make sure reserved words use quoted identifiers.
Verify that users are logged off.
Use dbcc to check for database integrity.
Back up databases.
Dump the transaction log.
Verify that master is the default database for the "sa" user.
Prepare the database and devices for upgrade using the preupgrade utility:
Create a sybsystemdb database
if it does not already exist.
Disable auditing by running sp_configure 'auditing', 0.
Disable Job Scheduler.
Obtain the current audit settings for the pre-15.7 Adaptive
Server using sp_displayaudit; you use this saved information to reenable auditing after you complete the installation. See Reenabling Auditing.
Disable disk mirroring.
Note: Cluster Edition version 15.7 does not support disk
mirroring.
Verify that your SYBASE environment variable points
to the location of the new server software files you just
installed.
Fix any problems that preupgrade utility
reports.
You can safely ignore any warnings Adaptive Server issues about configuration parameters
not being set to the default, as these are only for your information.
If you are upgrading from a nonclustered 12.5.4, 15.0.2, or 15.5 server, and archive database access has been applied in the lower version server, disable the related functionality before upgrade.
If you are upgrading from a 12.5.3
installation with cache bindings on sybsystemdb, drop the cache bindings for sybsystemdb that
are bound to user-defined caches before running preupgrade.
If you do not do this, you see this error:
Current process... infected with 11
If you do receive this error, re-run preupgrade after you have dropped the cache bindings.
Ensure that the procedure cache size is at least 150 percent of the default procedure cache size, or between 53,248
and 2,147,483,647 2K pages.
Copy these files from earlier versions of the server to their corresponding Adaptive Server 15.x installation locations:
$SYBASE/interfaces
$SYBASE/$SYBASE_ASE/servername.cfg
– where servername is your server name.
$SYBASE/$SYBASE_OCS/config/libtcl.cfg
$SYBASE/SYSAM-2_0/licenses/license.lic
If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation.
Set the OLDSYBASE_ASE variable to the SYBASE_ASE
appropriate to your older server. If you are upgrading from 12.5
for example, it should be ASE-12_5.
When
you upgrade a server to the Cluster Edition, index and table-level statistics
become inaccurate, and must be updated. Execute update index statistics on these tables:
The sybprocsdev device
Sybase system procedures are stored in the sybsystemprocs database, which is stored in the sysprocsdev device. You may need to increase the size of sysprocsdev before upgrading Adaptive Server.