Show TOC

Procedure documentationImporting Patches Locate this document in the navigation structure


If there are problems with the standalone enqueue server or with any other program in the system environment, it may be necessary to import a patch.

You can find all the programs needed for operating the standalone enqueue server with the replication server in the enserver package on SAP Service Marketplace.


You have obtained the enqueue packages from SAP Service Marketplace (   Entry by Application Group   Additional Components   (right column) SAP Kernel).

Here you choose the kernel suitable for your platform and then SAP KERNEL 7.20. On your platform you can find the #Database independent node. On the download page you can find the package enserver. Download this package.

The package contains the following files:





Under Windows the package contains the following additional files:




Note Note

You can find out the package version by executing each program with the option -v (z.B. enserver -v). Each program outputs the entire information about the version and patch level.

End of the note.


  1. Swap the mentioned above files in the executable directory (UNIX: /sapmnt/<sid>/exe, Windows: \\<SAPGLOBALHOST>\sapmnt\<SID>\SYS\exe\<n>uc\<platform>, where SAPGLOBALHOST is the host on which the SCS instance is running).

    Caution Caution

    Make sure that both programs enserver(.exe) and enrepserver(.exe) are always from the same package. You are not allowed to have different versions.

    sapcpe is used to make sure that the files are copied to the local executable directories at restart.

    For more information, see The sapcpe Program

    End of the caution.
  2. Trigger a failover of the SCS instance. The exact procedure depends on your cluster solution. In an emergency you can also terminate the process enserver at operating system level.

    The standalone enqueue server is shut down. Then the new version of the enqueue server is started on the host with the replication server. The enqueue server uses the existing replication table to create the new lock table.

    The replication server then closes down and restarts on a new host. This is how the new version is started.

    Caution Caution

    If you are using HA Polling and many replication servers are running on different hosts, you have to restart them all manually. During this short space of time, there is no high availability.

    End of the caution.