Updating SAP ABAP Systems on UNIX and Linux: IBM Db2 for Linux, Unix, and Windows

Upgrading Operating System and Database

When you update the SAP system, you may have to upgrade your operating system and database to a new version.

Context

For more information about which versions are currently supported, see the Product Availability Matrix on SAP Support Portal at http://support.sap.com/pamInformation published on SAP site . The Software Update Manager only checks the minimum versions required for the update.

If you need to upgrade an operating system or database, or migrate a database, then the timing and the sequence of the individual upgrades is of great importance. The procedure differs according to the database you use. The following text provides an overview of the main process steps for upgrading the operating system and database system for each database.

Procedure

  1. You migrate the database to the required version if you have not already done so.

    For more information, the Product Availability Matrix (PAM) on SAP Support Portal at http://support.sap.com/pamInformation published on SAP site. The migration guide is a PDF document on the data carrier that contains the required version of the database.

  2. Source release SAP NetWeaver 7.0 to 7.02: Make sure that you have a 64-bit system.

    Verify the word size of your Db2 for Linux, UNIX, and Windows instance using the Db2 LUW command db2level.

    If you have not already migrated your database instance to 64-bit, follow the instructions in SAP Note 356828 Information published on SAP site.

  3. Source release SAP NetWeaver 7.0 to 7.02: Install the new client connectivity.

    If your SAP system is not yet using the new client connectivity, the upgrade introduces a change to the client connectivity setup. Instead of a locally installed runtime client, CLI-based applications like the ABAP kernel or tools use the new Db2 CLI Driver. JDBC-based applications load the JDBC driver from a central network location. This change eliminates the need for local installations of Db2 LUW client software and enables you to maintain your client connectivity in one central place.

    You install the new client connectivity using the tool db6_update_client. This tool installs the new Db2 LUW client connectivity under subdirectory db6 of directory $(DIR_GLOBAL).

    db6_update_client creates the following files and directories:

    Folder

    File

    Contains

    $(DIR_GLOBAL)/db6

    db2cli.ini

    CLI config and database directory

    $(DIR_GLOBAL)/db6/jdbc

    db2jcc.jar

    JDBC connectivity

    db2jcc4.jar

    db2jcc_license_cu.jar

    jdbcdriver.lst

    $(DIR_GLOBAL)/db6/db2dump

    CLI driver diagnostic log

    $(DIR_GLOBAL)/db6/<OS>

    clidriver.lst

    CLI driver for platform <OS>

    db6_clidriver
    You need to have approximately 50 MB free disk space per operating system platform that you use with your SAP system.

    1. Log on as user <sid>adm on the database host.

    2. Mount the archive with the Db2 CLI/JDBC driver corresponding to your database version and Fix Pack level on the <CLI/JDBC mount>. Note that this archive may be labeled CLI/JDBC-Driver or Client.

    3. Change to directory <CLI/JDBC mount>/CLIENT.

    4. Run script db6_update_client.sh from this directory as follows:

      db6_update_client.sh -c <OS LIST>

      <OS LIST> is one or more (separated by a space) of the following:

      AIX_64, HPIA64, LINUXPPC64_64, LINUXX86_64, SUNOS_64, WINDOWS_AMD64, WINDOWS_IA64

  4. Run the Software Update Manager up to the Checks roadmap step and analyze the results.
  5. Upgrade the system with your selected scenario strategy.
    All scenario strategies are supported.