Installation guide

Context

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.

Procedure

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):

a) Create a sybsystemdb database if it does not already exist.

b) Disable auditing by running sp_configure 'auditing', 0.

c) Disable Job Scheduler.

d) 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.

e) 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.

Installation Guide for Linux

SAP ASE Upgrades