Updating SAP ABAP Systems on UNIX and Linux: Oracle

Quick Guide

The quick guide contains lists with actions to perform so that you can use it as check list.

The actions are in chronological order so that you can work through them like a checklist. For more information, follow the links to the descriptions of the actions. You can also use the checklist to gain a quick overview of the update procedure.

Required SAP Notes and SAP Documentation

This document is enhanced and updated by SAP Notes. These SAP Notes are an important source of information when you plan and prepare your update, and also help you perform the actual update. The SAP notes are available on the SAP Support Portal (http://support.sap.com/notesInformation published on SAP site).

Furthermore, you require additional documentation before, during, and after the update, such as SAP NetWeaver documentation. The documentation is available on the SAP Help Portal at http://help.sap.com.

  1. You request the current SAP Notes. You require at least the following SAP Notes:
    • Central Software Update Manager Note 3146834 Information published on SAP site
    • The relevant database-specific SAP Note 2976852 Information published on SAP site

  2. You make sure that you can access the Further Required Documentation.

Basic Concepts and SUM Tool Overview

  1. You decide on the sequence of updates in your SAP system group.

  2. Release upgrade only: You plan the upgrade schedule.

    Start your preparations for the upgrade at the latest two weeks before you upgrade your system. Each language that you import increases the minimum duration of the import by about 30 minutes.

    SPS update: You plan the update schedule.

  3. If you require more detailed information, see Technical Details of the Upgrade Procedure or Technical Details of the Update Procedure.
  4. You familiarize yourself with the Software Update Manager tool, its features, and user interface.

Update Planning

Before you start the actual update, plan it carefully so that downtime is reduced to a minimum and the update runs as efficiently as possible.

  1. You familiarize yourself with the Initial Dialogs for the Scenario Specification (Get Roadmap). With the information from these dialogs, the Software Update Manager assembles the roadmap for the wanted scenario.
  3. Release upgrade only: You can upgrade the front-end software as soon as you receive the software package.
  4. Before you start the upgrade, you check the database-specific aspects and include them in your upgrade schedule, if necessary.

  5. Archive Sizes: We recommend 21 GB up to the DOWNCONF_DTTRANS phase and 26 GB to the end of the upgrade. However, these sizes are only estimations based on sample data.

    Archive Sizes, for SAP ERP only: We recommend 35 GB up to the DOWNCONF_DTTRANS phase and 43 GB to the end of the upgrade. However, these sizes are estimations based on sample data.

  6. Release upgrade only: You plan data management measures to reduce the amount of data, if necessary.

  7. You plan the customizing of the Prepare new environment profiles.

  8. You plan the modification and enhancement adjustment for ABAP, if necessary.
  9. Release upgrade only: You meet the requirements for importing additional languages for ABAP, if necessary.
  10. Release upgrade only: You plan the handling of customer-specific translations and languages in ABAP during the upgrade.
  11. You plan to exclude customer-specific languages.
  12. Release upgrade only: You check the support package or patch level of the components included in the upgrade export.
  13. You plan the update of distributed and high-availability systems.
  14. You check whether your system is an MCOD system.
  15. Release upgrade only: If you want to import a support package before an upgrade, you check that you meet the requirements.
  16. You inform yourself about the integration of customer transports into the update procedure.
  17. You inform yourself about the ASCS instance split during the update procedure.
  18. You familiarize yourself with the ASCS Instance Move.
  19. You familiarize yourself with the Switch to Standalone Enqueue Server 2.

Update Preparation

You can perform the preparations while the system is in production operation. The Software Update Manager supports you here by making most of the necessary checks automatically.

  1. You choose the host for the preparations.

  2. You check the hardware requirements:

    • CPU, main memory, disk and swap space - see https://www.sap.com/about/benchmark/sizing.htmlInformation published on SAP site

      The minimum swap space is 20 GB.

    • Disk space in the file system for the SUM directory, the download directory, and directory DIR_TRANS. The space required depends on the product you are updating. For more information, see the document with additional product-specific information, which is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product. We recommend at least 40 GB free space for the SUM directory as well as for the download directory, and 20 GB for the directory DIR_TRANS.

    • Space requirements for the database:

      The Software Update Manager calculates the space requirements for the database. The free space required is in the range from 50 to 200 GB.

  3. You check the software requirements:

  4. You make the preparations at the database level.

  5. You check the Central Services requirements for ABAP:

    You call transaction RZ10 to check the values of the profile parameters rdisp/mshost and rdisp/wp_no_vb.

  6. You call transaction RZ04 to set the operation mode for the update.
  7. Enhancement package installation and SPS update: You check the number of background processes.
  8. Source release SAP NetWeaver 7.0 or 7.0 EHP1 only: You make the preparations in the monitoring area.
  9. You make sure that the requirements for the modification adjustment have been met.

  10. You release and confirm open repairs and request.

  11. You fill the download directory.
  12. You perform the specific preparations for distributed and high availability systems.

Running the Software Update Manager

Working with the SUM Tool
  1. You familiarize yourself with the Prerequisites and Introductory Information.
  2. You meet the requirements for the SUM directory.

  3. You download and unpack the Software Update Manager on the host where you want to run the Software Update Manager. Typically, this is the host on which the primary application server instance is running. However, you can also use an additional application server instance.

  4. You register SUM in SAP Host Agent.
  5. You start or restart the Software Update Manager.
  6. You can start the SUM Observer Monitor in a second browser window or on a mobile device.
  7. You can use the MailNotifier during the update procedure.
  8. You can reset the update if needed.
  9. You can use breakpoints during the update.
  10. You can verify the digital signature of the software archives in the download directory.
  11. You can run an update procedure with integrated customer transports.

  12. You can perform a prerequisite check

  13. Release upgrade only: If you need extra software after starting the upgrade, you import or install it now.

  14. If needed, you can correct and update information about the installed software instances in your SAP system.

Actions During the Roadmap Steps

For a complete list of all phases, see Using the ABAP Phase List for the Update.

Get Roadmap: Initial Dialogs for the Scenario Specification (Get Roadmap)

  1. You specify the Scenario to get the roadmap, either by

Roadmap Step Extraction

  1. You enter the password of user DDIC.
  2. You check the configuration of sapcpe.
  3. Enhancement package installation and SPS update: You implement the SAP Notes that the Software Update Manager displays.
  4. You check the SPAU fill level display and confirm all obsolete notes, reset all non-adjusted objects with active SAP version to SAP standard versions, carry out the outstanding modification adjustments.

Roadmap Step Configuration

  1. Release upgrade only: You decide about using the RASUVAR<x> reports to save variants.
  2. You enter the password for user SYSTEM.
  3. Release upgrade only: You check the tool versions of the SAP kernel, tp, and R3trans.
  4. Release upgrade only: You check the SAP Notes for the add-ons.
  5. Release upgrade only: If you are running an MCOD system, confirm the question.
  6. You enter several paths and parameters. This includes the following:
  7. Moreover, you specify the software that you want to include in the update:
    • Release upgrade only: You enter mount directories for the languages.
    • You check the SPAM version.
    • You enter the path to the stack configuration file.
    • You decide about the add-ons.
    • You confirm the support packages, if necessary.
    • You include support packages.
    • You enter the request for the modification adjustment, if necessary.

Shadow instance installation

  1. You make entries for the shadow instance installation.

Roadmap Step Checks

  1. Release upgrade only: You start the application-specific upgrade toolbox.
  2. If prompted, you remove the CNV_FLAG field.
  3. You check the results of the system check.
  4. If an error message is displayed during the check for database triggers (SLT) on exchange tables, you correct the error.

  5. You evaluate the results of the preparation roadmap steps in the window that appears after the Checks roadmap step has completed.

Roadmap Step Preprocessing

  1. You check the Software Update Manager Note, the application-specific SAP Note, and your database-specific SAP Note for new information and changes.
  2. You confirm any unconfirmed support packages.
  3. You check the list of ABAP Dictionary objects with active SAP versions, which have been modified but not yet adjusted, before they will be reset automatically to the SAP standard versions.
  4. Release upgrade only: You enter the passwords for add-ons, if necessary.
  5. Release upgrade only: If applicable, you examine and process the results of the consistency checks for custom software components and ABAP repository objects that SUM will rescue for the ABAP repository of the target system.

  6. Release upgrade only: You upgrade your operating system or database to the required version now at the latest, or you import any software you still need.

  7. Release upgrade only: You remove conflicts between customer tables and new views by deleting the customer tables.
  8. You release the locked objects and confirm repairs in phase REPACHK2.
  9. You clean up outstanding updates. You have to do this in the JOB_RSVBCHCK_R or JOB_RSVBCHCK_D phase at the latest.
  10. You make sure that you can recover the old SAP kernel if this becomes necessary.

  11. You lock the ABAP Workbench.

    Release upgrade only: For scenario strategy mode Standard or Downtime-optimized: You lock the ABAP Workbench in phase REPACHK2.

    Enhancement package installation and SPS update: For scenario strategy Standard or Downtime-optimized: You lock the ABAP Workbench in phase REPACHK_EHPI.

  12. You process any incomplete conversion requests and restart logs.
  13. Modifications: You confirm the request, if necessary.
  14. Release upgrade only: As of phase START_SHDI_FIRST, you can only log on with front-end software that is compatible with the target release.
  15. You now clean up outstanding updates, RFC calls, and open data extraction orders as well at the latest.
  16. Release upgrade only: Modifications: If you selected the scenario strategy Standard or Downtime-optimized in the initial dialogs, adjust modified SAP objects with the SAP standard versions.

    Enhancement package installation and SPS update: Modifications: You adjust modified SAP objects with the SAP standard versions.

  17. You check if SUM has generated and exported an safety transport request for objects adjusted with SPDD.
  18. You check the RSINDCRE.<SID> log file for any errors that may have occurred during the creation of secondary database indexes.

  19. You perform necessary actions that prepare your SAP system for the downtime.

  20. You ensure that digitally signed SAP Notes can be downloaded and consumed in the shadow system.

Prepare Downtime and Isolate PAS
  1. You perform actions to prepare your SAP system for the downtime, among which you are asked to isolate the primary application server instance and back up the /usr/sap/<SID> directory including the complete SUM directory. You may also need a backup of the home directory of user <SID>adm.
Roadmap Step Execution
  1. After the shutdown, you reimport the current version of the profile into your SAP system to adjust the instance profile by using transaction RZ10.

  2. Release upgrade only: Modifications: If you selected scenario strategy Single System in the initial dialogs, you adjust modified SAP objects with the SAP standard versions.

  3. Changes made to the environment of user <SID>adm before the update are saved. You can repeat them after the update, if necessary.

  4. If you are running the ASCS instance on a separate host, and the operating system on this host is different from that on the primary application server instance, you will be prompted by the Software Update Manager to install the latest SAP kernel on the separate host with the ASCS instance.

  5. The Software Update Manager asks you to perform the following actions:

    • You back up the database.

    • You change the database recovery mode.

Roadmap Step Postprocessing

  1. Release upgrade only: You configure the automatic start of the SAP start service with the start of the operating system, if required.

  2. If prompted, you can now start to generate loads for your SAP system.

  3. You remove the P errors.

  4. You take into account that the Software Update Manager performs a temporary renaming of SPAU transport request owner and client if you carry out the modification adjustment during the update.

  5. You can perform the modification adjustment for repository objects now and use the related transport request during subsequent updates.

  6. The Software Update Manager performs cleanup activities in the background. However, you can already use the system again.

  7. You take into account that the Software Update Manager saves selected log files and control files in different directories, which SAP Support can use for error analysis if there are problems after the update.

Options After the SUM Run

  1. You evaluate the Software Update Manager.

  2. You make preparations to run the Software Update Manager for another update.

  3. If you want to perform a subsequent SUM run on an identical system without re-entering parameter value, you generate a configuration file.

  4. You stop the Software Update Manager completely.

Follow-Up Activities

The Software Update Manager stops at the latest in the MODPROFP_UPG phase and prompts you to start the follow-up activities. The Software Update Manager then executes the last phases and completes the update. At the same time you can perform the follow-up activities specified by the Software Update Manager.

Actions Before Restarting Production Operation

  1. You solve all remaining P-errors.

  2. You perform the follow-up activities for SAP profiles.

  3. You perform the follow-up activities for user root.

  4. You perform the database-specific actions: Among others, you create or update the SAPDBA role, check the environment variables for BR*Tools, and back up the database.

  5. You perform follow-up activities in the monitoring area.

  6. You perform follow-up activities for the SAP kernel.

  7. You reimport additional programs such as RFC-SDK or CPIC-SDK from the SAP NetWeaver Presentation DVD, if necessary.

  8. You call transaction SPAU and - if applicable - transaction SPAU_ENH to adjust modifications to Repository objects, if necessary.

  9. You update the where-used list in the ABAP Workbench, if necessary.

  10. Release upgrade only: You adjust the Customizing settings.

  11. You adjust your own developments, if necessary.

  12. You perform follow-up activities for SAP Solution Manager.

  13. You adjust the user and role administration.

  14. You check the system time zone settings.

  15. You perform follow-up activities for SAP Profiles

  16. You perform the follow-up activities for user root.

  17. You perform follow-up activities in the monitoring area.

  18. Release upgrade only: You perform follow-up activities for SAP Solution Manager.

  19. For data protection and privacy reasons, you delete log files that are not needed anymore.
Actions After Restarting Limited Production Operation

You can perform the following follow-up activities during limited production operation of the system.

  1. You perform actions for the Cost-Based Optimizer.

  2. You reschedule background jobs that were locked when you isolated the primary application server instance.

  3. You generate loads using transaction SGEN and report RSGENINVLAS.

  4. You perform follow-up activities for Application Link Enabling (ALE).

  5. You carry out manual actions for upgrading additional application server instances.

  6. Enhancement package installation and SPS update: You check if indexes that are unknown to the SAP system exist in your database.

Actions After Restarting Production Operation

You can perform the following follow-up activities during normal production operation of the system.

  1. You delete old tablespaces.

  2. You import support packages, if necessary.

    If you want to install additional languages in your ABAP system, you import them before you import the support packages as described in the language transport documentation.

  3. Transport Management System (TMS): You distribute the configuration to all systems in the transport domain.

  4. Language transport: You copy glossary and terminology data from container tables to database tables.

  5. You save files for subsequent updates and you make a backup of the subdirectory that contains the shadow instance profiles, if necessary.

  6. You delete log files.