How To Fix SOI1752 - Delete log tables and log history tables

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 752

• Message text: Delete log tables and log history tables

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 SOI1752 - Delete log tables and log history tables ?

  The SAP error message SOI1752 typically indicates that there is an issue related to the deletion of log tables and log history tables in the SAP system. This error can occur in various contexts, often related to data management, archiving, or system performance.
  Cause:
  
  Log Table Growth: Log tables can grow significantly over time due to extensive logging of transactions, which can lead to performance issues or storage limitations.
  Retention Policy: The system may have a retention policy that requires old logs to be deleted after a certain period, and if this process is not executed properly, it can lead to this error.
  Database Constraints: There may be constraints or locks on the log tables that prevent deletion.
  Configuration Issues: Incorrect configuration settings in the logging or archiving processes can lead to this error.
  
  Solution:
  
  Manual Deletion: If the system allows, you can manually delete the log tables and log history tables using transaction codes like SARA (Archive Administration) or SLG1 (Application Log).
  Archiving: Implement an archiving strategy to move old log data to archive storage, which can help in managing the size of log tables.
  Check for Locks: Use transaction SM12 to check for any locks on the log tables that might be preventing deletion. If locks are found, they may need to be released.
  Adjust Retention Settings: Review and adjust the retention settings for logs in the system configuration to ensure that logs are deleted in a timely manner.
  Database Maintenance: Perform regular database maintenance tasks, such as reorganization or cleanup, to ensure optimal performance and space management.
  Consult Documentation: Refer to SAP Notes or documentation related to your specific version of SAP for any known issues or patches that may address this error.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to the SOI1752 error. You can search for relevant notes in the SAP Support Portal.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA for archiving, SLG1 for application logs, and SM12 for lock entries.
  System Monitoring: Regularly monitor the size of log tables and set up alerts for when they reach certain thresholds to prevent future issues.
  Backup: Always ensure that you have a backup of your data before performing deletions or significant changes to the database.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.