Manually Upgrading SAP ASE
Datasets / SAP ASE Environments and Data Sources / Manually Upgrading SAP ASE

Upgrading Manually

Prerequisites

After installing a new version of SAP ASE source in SYBASE.csh to set up new environment variables.

Procedure

Use the upgrade executable located in $SYBASE/ASE-new_version_0/bin.

  1. Shut down: the old SAP ASE instance.
  2. If the new version of SAP ASE is installed into a directory other than the old SAP ASE directory, then copy the server entry from the old interfaces file to the new interfaces file.
  3. Copy the server_name.cfg file from the old directory to the new $SYBASE directory.
  4. Start the new SAP ASE instance with the old master device from the old server.
  5. Run the upgrade executable.

Upgrading Interactively Using sqlupgrade

Use the interactive sqlupgrade tool to upgrade the old SAP ASE instance using an X-Windows or Motif GUI.

Prerequisites

  • Set the old SYBASE_ASE variable to the SYBASE_ASE that is appropriate to your older server. For example, if you are upgrading from 15.7 to 16.0, the old SYBASE_ASE should be ASE-15_0.
  • Set the old SYBASE, and SYBASE_OCS environment variables to point to the old version installation of SAP ASE, so the upgrade utility that is run from the new $SYBASE directory automatically populates input fields with the correct information as you upgrade.
  • Source in SYBASE.csh before running sqlupgrade utility.

Make sure the old ASE instance is running. 

Procedure

  1. Back up all the databases, and bcp out some of the system tables such as sysdatabases, sysdevices, sysservers, syslogins and sysremotelogins from master database, and click Next.
  2. Enter:
    $SYBASE/$SYBASE_ASE/bin/sqlupgrade
    Here are options for sqlupgrade:
    • -s sybase_dir – specifies the value to use for the SYBASE environment variable.
    • -r resource_file – executes with the specified resource file.
    • -D data_directory – specifies a working directory that differs from the default $SYBASE directory. This allows users other than sa to configure and use SAP ASE without the need to have access permission to the $SYBASE directory. If you do not use -D option, ASE uses $SYBASE as the default.
    • -v – prints the version number for sqlupgrade.
  3. In the Specify Sybase Directories dialog, enter:
    • The full path of the new SAP ASE release directory.
    • The full path of the data directory for the new SAP ASE instance. This field allows you to specify a working directory that differs from the default $SYBASE directory, which allows users other than sa to configure and use SAP ASE without the need to have access permission to the $SYBASE directory.
    • The name of the component directory that contains the new SAP ASE version.
    • The full path of the old release directory.
    • The name of the component directory that contains the earlier version of SAP ASE.
    • The name of the component directory that contains the earlier version of Open Client/Server Library.
  4. Click OK.
  5. Select the server to upgrade from the list of servers.
  6. Enter the password for the sa login, then click OK.
  7. Specify an upgrade option, then click OK. sqlupgrade performs a pre-upgrade review to verify that your current server meets the requirements for upgrade to the new version.
    If your current server fails the pre-upgrade review, fix the problem based on the information from the results of the test.
  8. Click OK to upgrade your server.
    Check the upgrade progress by viewing the sqlupgrade log in $SYBASE/$SYBASE_ASE/init/logs/sqlupgradeMMDD.NNN, where:
    • MM – is the month.
    • DD – is the date.
    • NNN – is a three-digit number identifying the sqlupgrade server upgrade session.
  9. After all pre-upgrade checks are successful, sqlupgrade shuts down the old SAP ASE instance and starts the new SAP ASE dataserver binary on the old master device.

When the upgrade completes successfully:

  • Click OK to specify another server to upgrade, or
  • Exit sqlupgrade and perform post-upgrade tasks.

The upgrade process:

  • Creates the RUN_servername file, which contains the information required to restart the server
  • Runs the installmaster script from the new installation directory to create all the system procedures

To verify that the upgrade was successful, log in to the server and run:

  • select @@version.
  • sp_configure "upgrade version".