How To Fix SCTS_AIM060 - 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: 060

• 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), the owner has to declare all tables
the AIM 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_AIM060 - Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4 ?

  The SAP error message SCTS_AIM060 indicates a lock mode conflict for a specific database table. This error typically arises when there are concurrent attempts to access or modify the same database table in a way that is not allowed due to the current lock settings. Here’s a breakdown of the components of the error message and potential solutions:
  Cause
  
  Lock Mode Conflict: The error occurs when two or more transactions are trying to access the same table with incompatible lock modes. For example, one transaction may be trying to write to the table while another is trying to read it, or two transactions may be trying to write to the table simultaneously.
  AIM (Application Interface Management): The error is related to the Application Interface Management (AIM) and indicates that there is a conflict in the access modes for the specified table.
  SOBJ-type: The SOBJ-type refers to the type of object that is being accessed, which can affect how locks are managed.
  
  Solution
  
  Identify the Lock: Use transaction codes like SM12 to check for existing locks on the table. This will help you identify which user or process is holding the lock.
  Release Locks: If you find that a lock is being held unnecessarily, you can release it (if you have the necessary permissions) or ask the user holding the lock to release it.
  Review Code: If the error is occurring due to custom code or a specific transaction, review the code to ensure that it is not trying to access the table in conflicting ways.
  Adjust Locking Strategy: If possible, adjust the locking strategy in your application to minimize conflicts. This may involve changing the order of operations or using different transaction isolation levels.
  Batch Processing: If the error occurs during batch processing, consider scheduling jobs to run at different times to avoid conflicts.
  Consult Documentation: Refer to SAP documentation or support for specific guidance related to the AIM and the SOBJ-type in question.
  
  Related Information
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view locks), SM21 (to check system logs), and ST22 (to check dumps) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific error message or the tables involved.
  Performance Monitoring: Monitor the performance of your database and application to identify any patterns that lead to lock conflicts.
  
  By following these steps, you should be able to diagnose and resolve the lock mode conflict indicated by the SCTS_AIM060 error message.