Updating SAP ABAP Systems on UNIX and Linux: SAP ASE

Important Entries for the Postprocessing Roadmap Step

This chapter deals with the roadmap step Postprocessing, in which the Software Update Manager saves the log files and prompts you to start with certain follow-up activities.

In the following, we go into detail of some important phases in which you enter information or confirm the existing values when prompted by the Software Update Manager:

Configuration of SAP Start Service (Phase REQSTARTSRV)

The upgrade does not configure the SAP start service (sapstartsrv) to start automatically as a daemon when you start the operating system. If you want to set up the automatic start, you have to perform some manual actions.

For more information about setting up the automatic start of the SAP start service during the operating system startup, see SAP Note 823941 Information published on SAP site.

Load Generation (Phase REQ_GENLD)

You can now start to generate loads for your SAP system.

For more information, see Generating Loads.

Solution of P-Errors (Phase CHK_POSTUP)

Some of the problems, which occur during an update, can be tackled after you have completed the update but before you start the productive system. This type of problem is indicated by a P in the second column of the .ELG logs.

You can find a complete list of these P messages in the CHK_POSTUP phase in the LONGPOST.LOG file.

To remove an error, proceed as described in the long text of the message. You have two options to access the message long text in your SAP system: Either using transaction SE91 (Message Maintenance), or using transaction UPG_SHOW_LOGFILE (Display a SUM LOG File).

The transaction UPG_SHOW_LOGFILE displays only log files located in the subdirectory DIR_PUT/log of the SUM directory. It is provided by the Software Update Manager and remains in the SAP system after the update.

  • Using transaction SE91:

    1. Identify the appropriate message class and the message number. In general, the message class is indicated by the letters after the Px, followed by message number, and the message short text. The system is the following: P<message language><message class><message number>

    2. In your SAP system, choose transaction SE91 and fill in the fields Message Class and Number accordingly. Then choose Display.

    3. Select the message in the list and choose Long Text. The long text with further information appears. Note that no long text is displayed when the checkbox Self-Explanatory is selected. In this case, the short text describes the issue sufficiently.

  • Using transaction UPG_SHOW_LOGFILE:

    1. In your SAP system, choose transaction UPG_SHOW_LOGFILE, and enter the log file name. Possible log file names are LONGPOST.LOG or <file name>.<SID> (for example, SAPA731ESI.S41).

    2. Select a level of detail to which you want to expand the list of messages.

    3. In the displayed message list, an icon before a message indicates that a long text exists in addition. To open the associated long text, double-click the message.

Any messages that you do not handle immediately must be handled at the next opportunity.

Temporary Renaming of SPAU Transport Request Owner and Client (Phase UEXP_SPAU)

If you carry out the modification adjustment during the update, note that the Software Update Manager performs the following in phase UEXP_SPAU:

  • The owner of the modifications transport request changes temporarily to user DDIC.

  • The client changes temporarily to client 000.

After this phase, the Software Update Manager revokes the changes so that the client has the original number and the transport request has the original owner again.

If the Software Update Manager aborts during this phase and you have to look for the transport request, bear in mind that the request owner is user DDIC. The number of the transport request remains unchanged.

If you restart the Software Update Manager, it uses the original client and transport request owner again.

Modification Adjustment of Repository Objects (Phase SPAUINFO)

If you modified programs, screens or user interfaces, you have to adjust them with transaction SPAU and - if applicable - transaction SPAU_ENH. You can either do the modification adjustment now or after you have finished the update. If you adjust the modifications now, the Software Update Manager exports the related transport request to the transport directory and registers it for transport in the umodauto.lst file. Using this file, the Software Update Manager can integrate the transport into subsequent updates.

To use this automatic registration of the transport in the umodauto.lst file, proceed as follows:

  1. If needed, close the browser window or the browser tab page with the SUM UI.

  2. Perform the modification adjustment.

  3. Restart the update and choose Adjustment completed.

If you want to finish the update without adjusting modifications, choose Continue.

For more information, see Adjusting Repository Objects.

Starting Cleanup Processing (Phase REQ_UP_FINAL)

In this phase, the Software Update Manager informs you that it will start as a next step performing cleanup activities. While it is doing this, you can carry out the necessary manual post-processing activities.

Note that imports of customer transports and additional software installations are still possible until phase REQ_FINISH_IMPORT. In this phase, you must confirm that such imports are no longer running or being started. Imports of this type are then only possible again after the update.

Finishing Imports (Phase REQ_FINISH_IMPORT)

Before you continue with this phase, make sure and confirm that all imports of customer transports and additional software installations are completed, and that no such further imports are started until the end of the procedure. Imports of this type are only possible again after the update.

Saving Log Files (Phase SAVELOGS)

The Software Update Manager saves selected log files and control files. If there are problems after the update, SAP Support can use these files for error analysis. The files are saved in the following directory:

/usr/sap/trans/sum/<SID>/<target release of SAP Basis>