Updating the SAP kernel using a disruptive procedure

Edit online

If the SAP kernel (disp+work or one of its dynamically loaded modules) is to be updated, complete the steps that are documented in this topic.

The sequence is applicable for SAP application servers running on Linux® or AIX®:

  1. Save the old modules, which reside in the executable (exe/run) directory, and copy the new modules to this directory.
  2. Stop all application server instances, see Operating system or hardware maintenance. Wait until all application servers are stopped.
  3. Stop and restart the message server.

    With IBM Z System Automation, this is accomplished by issuing a STOP vote for the SAP Central Services group with the RESTART option set to YES.

  4. Start the application server instances again, see Operating system or hardware maintenance.
Note: On Windows, load modules cannot be replaced while they are in use. Therefore, first stop the application server instance before replacing the executable routines and dynamic load modules. On UNIX, shared objects (*.so) are locked and cannot be overwritten while they are in use. However, they can be renamed or moved to another directory.