How To Fix RT788 - Performance attribute: roll time (transaction-specific)

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 788

• Message text: Performance attribute: roll time (transaction-specific)

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 RT788 - Performance attribute: roll time (transaction-specific) ?

  The SAP error message RT788, which refers to "Performance attribute: roll time (transaction-specific)," typically indicates that there is an issue related to the performance of a transaction in the SAP system, specifically concerning the roll time. Roll time is the time taken to manage the rollback of database transactions, which can be critical for maintaining data integrity and performance.
  Cause:
  
  
  High Rollback Time: The error suggests that the time taken for rollbacks during transaction processing is higher than expected. This can be caused by:
  
  Long-running transactions that require significant resources.
  Inefficient database operations or poorly optimized SQL queries.
  Lock contention or deadlocks in the database.
  Insufficient system resources (CPU, memory, I/O) leading to slow performance.
  Large volumes of data being processed in a single transaction.
  
  
  
  Configuration Issues: Incorrect configuration settings in the SAP system or database can also lead to performance issues.
  
  
  Database Performance: Issues with the underlying database, such as fragmentation, lack of indexing, or other performance bottlenecks.
  
  
  Solution:
  
  
  Analyze Transaction Performance:
  
  Use transaction ST05 (SQL Trace) to analyze the SQL statements executed during the transaction and identify any long-running queries.
  Check transaction ST22 for dumps that might provide insights into performance issues.
  
  
  
  Optimize SQL Queries:
  
  Review and optimize any SQL queries that are taking too long to execute.
  Ensure that appropriate indexes are in place to speed up data retrieval.
  
  
  
  Monitor System Resources:
  
  Use transaction SM66 or ST03N to monitor system performance and identify any resource bottlenecks.
  Check for high CPU or memory usage and consider scaling resources if necessary.
  
  
  
  Database Maintenance:
  
  Perform regular database maintenance tasks such as reorganization, indexing, and statistics updates to improve performance.
  Check for and resolve any database locks or deadlocks.
  
  
  
  Configuration Review:
  
  Review SAP and database configuration settings to ensure they are optimized for performance.
  Adjust parameters related to rollback segments and memory allocation if necessary.
  
  
  
  Transaction Design:
  
  If possible, redesign transactions to be smaller and more efficient, breaking them into smaller units of work to reduce rollback time.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to performance issues and RT788 for any specific recommendations or patches.
  Performance Monitoring Tools: Utilize SAP's performance monitoring tools like SAP Solution Manager to get insights into system performance.
  Database Logs: Review database logs for any errors or warnings that might indicate underlying issues affecting performance.
  
  By addressing the underlying causes of the high roll time, you can improve the performance of the affected transactions and reduce the occurrence of the RT788 error message.