How To Fix RZ384 - Server not started with enqueue process, number cannot be changed

RZ384 - Overview

• Message type: E = Error

• Message class: RZ - Messages for Computing Center Management System

• Message number: 384

• Message text: Server not started with enqueue process, number cannot be changed

What causes this issue?

This server was started according to the instance profile without
enqueue processes. In operation mode switching, it is not possible to
switch the number of enqueue processes from 0 to 1.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

If lock management is supposed to be active on this server, the
instance profile must be changed and the system restarted.

Error message extract from SAP system. Copyright SAP SE.

RZ384 - Details

• The SAP error message RZ384 indicates that the enqueue process is not started, which is crucial for managing locks in the SAP system. This error typically arises when the enqueue server is not running, which can lead to issues with data consistency and integrity in the SAP environment.
  
  Cause:
  
  Enqueue Server Not Started: The enqueue server process may not have been started due to various reasons, such as system configuration issues, server crashes, or manual intervention.
  
  Configuration Issues: Incorrect configuration in the instance profile or the SAP system settings can prevent the enqueue server from starting.
  Resource Limitations: Insufficient system resources (CPU, memory) can lead to the enqueue server failing to start.
  Database Issues: Problems with the database connection or database server can also prevent the enqueue server from functioning properly.
  
  
  Solution:
  
  
  Start the Enqueue Server:
  
  Use the SAP Management Console (SAP MMC) or transaction code SM51 to check the status of the enqueue server.
  If it is not