Preupgrade Tasks

To ensure a successful upgrade, review and perform preparatory tasks as necessary. Depending on the old server configuration, you may not need to perform all preparatory tasks.

Note: Follow these steps only if you are performing a major upgrade from an SAP ASE version earlier than 16.0.

Skip these preparatory tasks if you plan to use sqlupgrade, which performs these tasks automatically.

  1. Install SAP ASE 16.0 into the old ASE directory.
  2. Check system and upgrade requirements.
  3. Ensure that the directory to which your TEMP environment variable points exists.
  4. Verify the name and location of the runserver file, and that you have renamed it to RUN_servername as it appears in the interfaces file, where servername is the name of the old server.
    The default RUN_servername file for a server called SYBASE is 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.
  5. 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.
  6. Make sure reserved words use quoted identifiers.
  7. Verify that users are logged off.
  8. Use dbcc to check for database integrity.
  9. Back up databases.
  10. Dump the transaction log.
  11. Verify that master is the default database for the "sa" user.
  12. Prepare the database and devices for upgrade using the preupgrade utility. See preupgrade in the Utility Guide for more information. After preupgrade finds no errors by exiting with status 0 (zero):
    1. Create a sybsystemdb database if it does not already exist.
    2. Disable auditing by running sp_configure 'auditing', 0.
    3. Disable Job Scheduler.
    4. Obtain the current audit settings for the pre-16.0 SAP ASE using sp_displayaudit; use this saved information to reenable auditing after you complete the upgrade.
    5. If you made any site-specific changes to the permissions for system stored procedures, obtain the current permission settings for them using sp_helprotect; then use this saved information to reenable the permissions after you complete the installation. Pay special attention to
      • Any stored procedures that are not granted execute permission to public, such as sp_addauditrecord, sp_monitor, and sp_sysmon.
      • Any stored procedures where execute permission has been revoked from public.
    6. Disable disk mirroring.
    7. 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 SAP ASE issues about configuration parameters not being set to the default, as these are only for your information.

  13. If you are upgrading from a nonclustered 12.5.4, 15.0.2, 15.5, or 15.7 server, and archive database access has been applied in the lower version server, disable the related functionality before upgrading.
  14. 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 2KB pages.
  15. Copy these files from earlier versions of the server to their corresponding SAP ASE 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
  16. If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation.
  17. Set the environment variables by sourcing the SYBASE.[csh, sh, env] file.
    Warning!  Do not run the environment variable script more than once.
  18. Disable LDAP using:
    sp_configure 'enable ldap' , 0
Related tasks
Reenabling Auditing
Preparing to Install SAP ASE
Managing Java in the Database During Installations and Upgrades