Preupgrade Tasks

You must have SA privileges to perform an upgrade.

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.
Note: 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.
  1. Install the Cluster Edition onto your system in a new location.
  2. Check system and upgrade requirements. See the Checking System and Upgrade Requirements topic.
  3. Check the location of the RUN_server file. See the Checking Runserver File Location topic.
  4. 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.
  5. Stored procedure text in the syscomments table is required for upgrade. See the Procedure Text is Required for Upgrade topic.
  6. Resolve reserved words using quoted identifiers. See the Reserved Words topic.
  7. Verify users are logged off.
  8. Check for database integrity.
  9. Back up the databases.
  10. Dump the transaction log.
  11. Ensure that master is the default database for the “sa” user.
  12. Prepare the database and devices for upgrade. Follow these steps.
    1. Disable auditing
    2. Disable Job Scheduler by ensuring the “enable Job Scheduler” is off.
    3. Archive auditing data and truncate auditing tables.
    4. Disable disk mirroring.
      Note: Cluster Edition version 15.5 does not support disk mirroring.
    5. Verify that your $SYBASE environment variable points to the location of the new Adaptive Server software files you just unloaded.
  13. If you are upgrading to a private installation see Upgrading to a Private Installation.
  14. If the upgrade is from 12.5.4 or 15.0.2 or 15.5 non-clustered server, and archive database access has been applied in the lower version server, disable the related functionality before upgrade.
  15. 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 cache before running preupgrade.
    If you do not do this prior to running preupgrade you will recieve this error: 
    Current process... infected with 11
    . If you do recieve this error, rerun the preupgrade utility after you have dropped the cache bindings.
  16. 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
  17. If the Java in database feature is enabled, create sybpcidb database. The sybpcidb database stores configuration information for the Pluggable Component Interface (PCI) and all Pluggable Component Adapter (PCA) components. This database is used by installpcidb script. For example: 
    1> disk init
2> name = "sybpcidb_dev",
3> physname = "/dev/raw/raw20",
4> size = '24MB'
5> go
1> create database sybpcidb on sybpcidb_dev = 24
2> go
    Note: The installpci script must only be run on the first node and not on any other nodes in the cluster. In addition only create the PCI device on the first node. A single instance of the PCI configuration is shared between the nodes of a Cluster.
Parent topic: Upgrading the Server