How To Fix /SEHS/DG_DGA390 - Log messages were deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /SEHS/DG_DGA -

• Message number: 390

• Message text: Log messages were deleted

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 /SEHS/DG_DGA390 - Log messages were deleted ?

  The SAP error message /SEHS/DG_DGA390 Log messages were deleted typically indicates that log messages related to a specific process or transaction have been deleted from the system. This can occur for various reasons, such as system cleanup processes, manual deletion, or retention policies that are configured in the system.
  Causes:
  
  Retention Policy: The system may have a configured retention policy that automatically deletes log messages after a certain period.
  Manual Deletion: Users with the appropriate permissions may have manually deleted the log messages.
  System Cleanup Jobs: Scheduled jobs or background processes may be set up to clean up old log entries to free up space.
  Database Maintenance: Regular database maintenance activities might also lead to the deletion of log messages.
  
  Solutions:
  
  Check Retention Settings: Review the retention settings for log messages in the relevant configuration. Adjust the settings if necessary to retain logs for a longer period.
  Review User Permissions: Ensure that only authorized users have the ability to delete log messages. This can help prevent accidental or unauthorized deletions.
  Audit Logs: If available, check audit logs to see if there are records of who deleted the log messages and when.
  Backup and Restore: If the log messages are critical, consider implementing a backup strategy that includes log files, allowing you to restore them if needed.
  Consult Documentation: Refer to SAP documentation or support for specific guidance related to the module or process that generated the log messages.
  
  Related Information:
  
  Transaction Codes: You may want to check transaction codes related to log management, such as SLG1 (Application Log) to view existing logs or SLG2 to manage log settings.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional context or solutions.
  System Monitoring: Implement monitoring tools to keep track of log message generation and deletion, which can help in identifying patterns or issues.
  
  If the issue persists or if the log messages are critical for your operations, consider reaching out to SAP support for further assistance.