How To Fix SZDM_CC_CHKS_DETAILS095 - R3TR OBJA &1: Table &2 read by XPRA &3 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: 095

• Message text: R3TR OBJA &1: Table &2 read by XPRA &3 cannot be set to read only.

What causes this issue?

INCLUDE SZDM_CC_LAT_DET_INTRO_PROC OBJECT DOKU ID TX
In this case the owner of the XPRA report &v3& has specified that the
XPRA report accesses table &v2& and that this table shall be read only
for the productive application during the ZDO upgrade. (See ABAP
transaction SLAPI. Choose the "Position..." button to find your XPRA
metadata definition &v1&. Select this entry and choose "Used Database
Tables".)
INCLUDE SZDM_CC_LAT_DET_RO_IMPOSSIBL OBJECT DOKU ID TX

How to fix this error?

As an alternative to setting the complete table to the read-only mode,
the application needs to make sure that only the key ranges accessed by
the XPRA report become read-only while all other table entries are still
writeable for the productive application.

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_DETAILS095 - R3TR OBJA &1: Table &2 read by XPRA &3 cannot be set to read only. ?

  The SAP error message SZDM_CC_CHKS_DETAILS095 indicates that there is an issue with a specific table being accessed by an XPRA (a type of program that performs database changes during an upgrade or support package installation). The error message states that the table cannot be set to read-only, which is typically required during certain operations to ensure data integrity.
  Cause:
  
  Table Locking: The table in question may be locked by another process or transaction, preventing it from being set to read-only.
  Database Constraints: There may be constraints or dependencies that prevent the table from being modified or set to read-only.
  Incorrect Configuration: The XPRA may be incorrectly configured or may not have the necessary permissions to modify the table.
  Data Consistency Issues: There may be data consistency issues that need to be resolved before the table can be set to read-only.
  
  Solution:
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the table. If there are locks, you may need to wait for the locks to be released or resolve them.
  Review XPRA Logs: Check the logs for the XPRA that is causing the issue. This can provide more context on what is failing and why.
  Database Consistency Check: Run consistency checks on the database to ensure that there are no issues with the data that could be causing the problem.
  Permissions: Ensure that the user executing the XPRA has the necessary permissions to modify the table.
  Manual Intervention: If the issue persists, you may need to manually intervene by setting the table to read-only or adjusting the XPRA settings.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on how to resolve it.
  
  Related Information:
  
  XPRA Programs: These are programs that are executed during system upgrades or support package installations to make necessary changes to the database schema or data.
  Transaction Codes: Familiarize yourself with transaction codes like SE11 (Data Dictionary), SE38 (ABAP Program), and SM37 (Job Monitoring) to help diagnose and resolve issues.
  SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for assistance, providing them with the error message and any relevant logs.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.