How To Fix SQLM090 - &1 RTMP orphan records deleted (runtime &2 seconds)

SAP Error Message - Details

• Message type: E = Error

• Message class: SQLM - SQL Monitor messages to the world

• Message number: 090

• Message text: &1 RTMP orphan records deleted (runtime &2 seconds)

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 SQLM090 - &1 RTMP orphan records deleted (runtime &2 seconds) ?

  The SAP error message SQLM090 indicates that orphan records in the Runtime Monitoring and Performance (RTMP) database have been deleted. This message is typically related to the SQL Monitor (SQLM) functionality in SAP, which is used for monitoring and analyzing SQL statements executed in the system.
  Cause:
  The cause of this message is usually related to the cleanup process of the SQL Monitor. Orphan records are entries in the SQL Monitor database that no longer have a valid reference or are not associated with any active sessions or transactions. This can happen due to various reasons, such as:
  
  Session Termination: If a session that was being monitored is terminated unexpectedly, it may leave behind orphan records.
  Database Cleanup: Regular maintenance tasks or cleanup jobs that remove outdated or irrelevant data can lead to the deletion of orphan records.
  Configuration Changes: Changes in the configuration of the SQL Monitor or related components may also lead to orphan records being created.
  
  Solution:
  The message itself is informational and does not indicate a critical error. However, if you are concerned about the frequency of this message or if it is impacting system performance, you can consider the following steps:
  
  Monitor SQLM Configuration: Ensure that the SQL Monitor is configured correctly and that the cleanup jobs are running as expected.
  Check for Session Issues: Investigate if there are frequent session terminations or issues that might be causing orphan records to accumulate.
  Database Maintenance: Regularly perform database maintenance tasks to ensure that orphan records are cleaned up and that the database remains healthy.
  Review Logs: Check the system logs for any related errors or warnings that might provide more context about the orphan records and their deletion.
  
  Related Information:
  
  SQL Monitor (SQLM): This is a tool in SAP that allows you to monitor the performance of SQL statements executed in the system. It provides insights into execution times, resource usage, and potential performance bottlenecks.
  Performance Tuning: If you are experiencing performance issues, consider using the SQL Monitor to identify long-running queries or resource-intensive operations that may need optimization.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address specific issues related to SQLM or orphan records.
  
  In summary, the SQLM090 message is a normal part of the SQL Monitor's operation, indicating that orphan records have been cleaned up. Regular monitoring and maintenance can help ensure that the SQL Monitor functions effectively without accumulating unnecessary data.