How To Fix SOI1349 - Table &1: Check if current table changes allow live clone

SOI1349 - Overview

• Message type: E = Error

• Message class: SOI1 - Safe Online Import/Upgrade Messages continued

• Message number: 349

• Message text: Table &1: Check if current table changes allow live clone

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 SOI1349 - Table &1: Check if current table changes allow live clone ?

  The SAP error message SOI1349 indicates that there is an issue with the ability to perform a live clone of a table in the SAP system. This error typically arises when certain conditions related to the table's structure or its current state do not permit a live clone operation.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Table Structure Changes: If there have been recent changes to the table structure (like adding or removing columns, changing data types, etc.), these changes may not be compatible with live cloning.
  
  
  Locking Issues: If the table is currently locked by a transaction or if there are ongoing operations that prevent a consistent snapshot of the table, this can lead to the error.
  
  
  Replication Settings: The settings for data replication or the configuration of the database may not support live cloning for the specific table.
  
  
  Database Constraints: Certain constraints or dependencies related to the table may prevent it