How To Fix SCTS_AIM024 - Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4

SAP Error Message - Details

• Message type: E = Error

• Message class: SCTS_AIM - Messages for the AIM meta data repository

• Message number: 024

• Message text: Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4

What causes this issue?

For each after import method (AIM) and XPRA program, the owner has to
declare all tables the AIM or XPRA reads from or writes to. Furthermore,
for each of these tables, the owner of the AIM or XPRA has to declare if
and how the content of these tables is protected against write access by
the productive application running in parallel with the ZDO upgrade. The
owner provides this information by assigning a "LOCK_MODE" to each of
these tables. The possible values of the LOCK_MODE and their meanings
are described
<DS:DE.OB_LOCK_MODE>here.</>

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

If different AIMs or XPRAs declare access to the same table and use
different values of LOCK_MODE then the system will compute a common
value which is suitable for both AIMs or XPRAs. Some combinations of
LOCK_MODE values are, however, incompatible to each other. In this case,
the system will report an error.
The pairs of compatible and incompatible lock modes can be depicted in
the following matrix:
||' '| X | P | R | U | W
------------------------------------
' '||' '| ! | ! | ! | ! | !
X || ! | X | P | R | U | !
P || ! | P | P | R | ! | ! (! represents a pair of
R || ! | R | R | R | ! | ! incompatible lock modes)
U || ! | U | ! | ! | U | !
W || ! | ! | ! | ! | ! | W
In the current case, table &V1& is declared with two incompatible lock
modes (&V2& and &V3&). The conflicting value is declared for the AIM of
transport object type &V4& (see transaction SOBJ, navigate to the method
declarations, select button "AIM details" and navigate to "used database
tables").

System Response

In a ZDO upgrade, the tables cannot be correctly classified. This can
lead to a failure of the upgrade.

How to fix this error?

Adjust the LOCK_MODE values for table &V1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCTS_AIM024 - Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4 ?

  The SAP error message SCTS_AIM024 indicates a lock mode conflict for a specific database table. This error typically arises in the context of the SAP Change and Transport System (CTS) when there are conflicting lock requests for the same table by different processes or users. Here’s a breakdown of the components of the error message:
  
  &1: The name of the table that is experiencing the lock conflict.
  &2: The lock mode of the first process (e.g., exclusive, shared).
  &3: The lock mode of the second process that is conflicting with the first.
  &4: The SOBJ-type (object type) related to the lock.
  
  Cause
  The lock mode conflict occurs when:
  
  One process is trying to access a table in a mode that is incompatible with the mode in which another process is accessing the same table.
  For example, if one process has an exclusive lock on a table, another process trying to obtain a shared lock on the same table will encounter this conflict.
  
  Solution
  To resolve the lock mode conflict, you can take the following steps:
  
  
  Identify the Processes: Use transaction codes like SM12 (to view and manage locks) to identify which processes are holding locks on the table in question. Look for the user sessions that are causing the conflict.
  
  
  Release Locks: If it is safe to do so, you can manually release the locks held by the conflicting processes. This can be done in SM12 by selecting the relevant lock entries and deleting them.
  
  
  Check for Long-Running Transactions: Investigate if there are any long-running transactions that are holding locks for an extended period. If possible, terminate or complete these transactions.
  
  
  Review Code and Processes: If this error occurs frequently, review the code or processes that are accessing the table to ensure that they are not trying to access the same data in conflicting modes simultaneously.
  
  
  Adjust Locking Strategy: If applicable, consider adjusting the locking strategy in your application to minimize conflicts. This may involve changing the way locks are acquired or the order in which tables are accessed.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to this error.
  
  
  Related Information
  
  
  Transaction Codes: 
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for any related issues.
  ST22: To analyze dumps that may provide insight into the problem.
  
  
  
  Documentation: Review SAP documentation related to the Change and Transport System and database locking mechanisms for more detailed information.
  
  
  Performance Monitoring: Regularly monitor system performance and locking behavior to proactively address potential conflicts.
  
  
  By following these steps, you should be able to resolve the lock mode conflict and prevent it from recurring in the future.