Updating SAP ABAP Systems on UNIX and Linux: SAP ASE

Preparing the Update of High Availability Systems

This chapter deals with preparatory activities if you want to update your high availability (HA) system.

Context

To update an HA system, implement an HA system configuration as recommended by SAP to create a reliable starting point for the update.

Furthermore, move the cluster group SAP <SAPSID>HA to the cluster node, if the primary application server instance runs on such a node.

Procedure

Create an optimal starting point.

To create a reliable starting point for the update, it is crucial that you implement an HA system configuration as recommended by SAP. Below you can find problems resulting from different configurations and possible solutions:

  • Manually set up standalone enqueue server

    The following only applies to standalone enqueue servers (separately started enqueue server process), not to officially supported ASCS instances.

    If you have set up a standalone enqueue server manually, revert this configuration before the execution of the downtime steps of the update. Revert this configuration before the kernel switch step at the latest. The Software Update Manager is unable to detect a manual setup of standalone enqueue servers and, therefore, cannot update them. This can cause problems when the system is started for the first time after the kernel switch.

  • Maintain the profile directory.

    • Remove any old, unused profiles and backup copies. The directory must contain only active profile files.

    • Do not use links to local profiles with different names. The Software Update Manager can only work with physical profile files.