How To Fix SOI779 - Error creating Log and Log history tables

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI - Safe Online Import/Upgrade Messages

• Message number: 779

• Message text: Error creating Log 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 SOI779 - Error creating Log and Log history tables ?

  The SAP error message SOI779, which indicates an issue with creating Log and Log history tables, typically arises in the context of the SAP Solution Manager or other SAP applications that utilize logging mechanisms. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  Database Permissions: The user account that is being used to create the log tables may not have the necessary permissions to create tables in the database.
  Database Configuration: There may be issues with the database configuration, such as insufficient space or incorrect settings that prevent table creation.
  Existing Tables: If the log tables already exist and there is a conflict with the creation process, this error may occur.
  Transport Issues: If the system is in a transport process, it may be locked or restricted from making changes to the database schema.
  System Configuration: Incorrect configuration settings in the SAP system or the Solution Manager can lead to this error.
  
  Solutions:
  
  
  Check Database Permissions:
  
  Ensure that the database user has the necessary permissions to create tables. You may need to grant the appropriate privileges.
  
  
  
  Verify Database Space:
  
  Check the database for available space. If the database is full, you may need to free up space or increase the database size.
  
  
  
  Check for Existing Tables:
  
  Use database tools or SQL queries to check if the log and log history tables already exist. If they do, you may need to drop them or rename them before attempting to create new ones.
  
  
  
  Review System Configuration:
  
  Check the configuration settings in the SAP system or Solution Manager. Ensure that all necessary parameters are set correctly.
  
  
  
  Transport Management:
  
  If the system is in a transport process, wait until the transport is completed before attempting to create the tables again.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates available that resolve the issue.
  
  
  
  Check Logs:
  
  Review the application logs and system logs for more detailed error messages that can provide additional context for troubleshooting.
  
  
  
  Related Information:
  
  SAP Support Portal: Utilize the SAP Support Portal to search for specific notes related to the SOI779 error.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered and resolved similar issues.
  Documentation: Refer to the official SAP documentation for your specific version of the software for guidance on logging and database management.
  
  If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.