Updating SAP ABAP Systems on UNIX and Linux: Oracle

Prerequisites and Introductory Information

This section provides information about starting and running the Software Update Manager.

Prerequisites

Before you run the Software Update Manager, make sure that the following prerequisites are fulfilled:

  • Make sure that the communication ports 1128 and 1129 of your system are open and not blocked by third-party software such as a firewall to ensure the correct operation of the SAP Host Agent. For more information, see TCP/IP Ports of All SAP Products.
  • Your system is up and running, including all system instances and all system processes. Do not stop the system manually. The Software Update Manager stops and starts it when needed.

  • You are logged on to the update host as user <SID>adm.

  • User <SID>adm has the required permissions:

    The <SID>adm user has to be the owner and have full (xrw) permissions on all files in the /usr/sap/<SID> and /sapmnt/<SID> directories. If symbolic links are used, <SID>adm has to be the owner of these links as well.

Introductory Information

Note the following:

  • All required planning and preparation actions have to be completed.
  • The Software Update Manager controls the entire procedure, from checking the system requirements and importing the necessary programs through stopping production operation until production operation is resumed. The procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into individual steps. The successful completion of a step is a precondition for the success of all subsequent steps.

    For a complete list of all steps, see the phaselist.xml file available in the directory <path to SUM directory>/SUM/abap/doc.

    Alternatively, you can use the Using the SUM Analysis Feature utility.

  • The Software Update Manager typically runs on the application server of the primary application server instance. However, you can also use an additional application server instance.

  • SPS Update: All customer implementations to SAP exit function modules within the SAP BASIS are disabled on the shadow instance at the beginning of the update procedure. They are re-enabled at the end of the downtime so that they can be used productively again in the updated system.

    The reason is, that SAP exit function modules with access to tables can be implemented within customer enhancement projects (R3TR CMOD). However, this could lead to errors during the update because these tables do not exist in the shadow system.

  • To monitor the procedure, you can use the logs created by the Software Update Manager. To open them use either the Logs item in the SUM menu bar, or the log tail viewer in the More menu (see also: SUM UI: Menu Bar). Alternatively, use the SUM Analysis utility (see: Using the SUM Analysis Feature).
  • Many steps require no user input. In the following chapters, you can find a description of all necessary user input.
  • User actions are also required when errors occur. If an error occurs, correct it and repeat the step in which the error has occurred. Once the step has been repeated successfully, you can continue with the update. For more information, see Troubleshooting.