How To Fix SOI2364 - Classification type "Live Clone" changed to "Clone read only"

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI2 - SOI Messages

• Message number: 364

• Message text: Classification type "Live Clone" changed to "Clone read only"

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SOI2364 - Classification type "Live Clone" changed to "Clone read only" ?

  The SAP error message SOI2364 indicates that the classification type for a specific object has been changed from "Live Clone" to "Clone read only." This typically occurs in the context of SAP's Solution Manager or other SAP systems that utilize classification for managing objects, particularly in scenarios involving system copies or clones.
  Cause:
  
  
  System Copy or Clone Operation: The error usually arises during a system copy or cloning operation where the system attempts to create a live clone of an object. If the operation does not complete successfully or if there are restrictions on the object, the classification may automatically change to "Clone read only."
  
  
  Configuration Issues: There may be configuration settings in the SAP system that prevent the object from being treated as a live clone. This could be due to missing authorizations, incorrect settings in the system landscape, or issues with the underlying database.
  
  
  Data Consistency Issues: If there are inconsistencies in the data or if the object is not in a state that allows it to be cloned live, the system may revert to a read-only state.
  
  
  Solution:
  
  
  Check System Configuration: Review the configuration settings related to system cloning and classification types. Ensure that the system is set up correctly to allow live cloning.
  
  
  Review Authorizations: Ensure that the user performing the operation has the necessary authorizations to create live clones. Lack of permissions can lead to restrictions on object classification.
  
  
  Data Consistency Check: Perform a consistency check on the object in question. If there are any inconsistencies, resolve them before attempting to create a live clone again.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues related to cloning and classification.
  
  
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about why the classification changed. This can help in diagnosing the root cause.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide more detailed insights based on the specific configuration and version of your SAP system.
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for details on system cloning and classification types.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can share their solutions.
  Training and Best Practices: Consider training sessions or best practice guides on managing system clones and classifications in SAP environments.
  
  By following these steps, you should be able to identify the cause of the SOI2364 error and implement a solution to restore the desired classification type.