How To Fix SZDM_CC_CHKS_DETAILS104 - R3TR TABL or LIMU TABD &1: Table &2 cannot be set to read only.

SAP Error Message - Details

• Message type: E = Error

• Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes

• Message number: 104

• Message text: R3TR TABL or LIMU TABD &1: Table &2 cannot be set to read only.

What causes this issue?

INCLUDE SZDM_CC_GENERAL_INTRO OBJECT DOKU ID TX
Reason: In order to execute an upgrade in parallel with the productive
application, the ZDO procedure locks tables of the productive
application to ensure data consistency. In this case<(>,<)> table &v1&
will be converted. Therefore<(>,<)> the ZDO upgrade procedure has to
switch the table to the read-only mode during the upgrade. Since table
&v2& is frequently updated in a typical production system, frequently
used application transactions will become unavailable.
&PROCEDURE&
Do not deliver the changes that force the conversion of the table &v1&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SZDM_CC_CHKS_DETAILS104 - R3TR TABL or LIMU TABD &1: Table &2 cannot be set to read only. ?

  The SAP error message SZDM_CC_CHKS_DETAILS104 indicates that there is an issue with setting a database table to read-only mode. This error typically occurs when you are trying to modify the properties of a table (specifically a database table) in the Data Dictionary (SE11) or during a transport request, and the system is unable to set the table to read-only due to certain conditions.
  Causes:
  
  Table in Use: The table might be currently in use by other processes or transactions, preventing it from being set to read-only.
  Database Lock: There may be a lock on the table at the database level, which can occur if another user or process is accessing the table.
  Transport Request Issues: If you are trying to transport changes related to the table, there might be issues with the transport request itself.
  Table Attributes: The table might have attributes or settings that prevent it from being set to read-only.
  Authorization Issues: The user attempting to make the change may not have the necessary authorizations to modify the table properties.
  
  Solutions:
  
  Check for Locks: Use transaction code SM12 to check for any locks on the table. If you find locks, you may need to wait for them to be released or contact the user who has locked the table.
  Check Active Sessions: Use transaction code SM66 to see if there are any active sessions that might be using the table.
  Review Transport Request: If this error occurs during a transport, ensure that the transport request is correctly configured and that there are no issues with the transport itself.
  Table Attributes: Review the table attributes in SE11 to ensure that there are no settings that would prevent it from being set to read-only.
  User Authorizations: Ensure that the user has the necessary authorizations to modify the table properties. You may need to consult with your SAP security team if there are authorization issues.
  System Restart: In some cases, a system restart may help clear any lingering locks or issues.
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with the following transaction codes:
  
  SE11: Data Dictionary for viewing and modifying table definitions.
  SM12: To check and manage database locks.
  SM66: To monitor active processes in the system.
  SE09/SE10: For managing transport requests.
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  
  
  Documentation: Review SAP documentation regarding database table management and transport processes for additional context and best practices.
  
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.