How To Fix GT553 - Scan of table & is restarted

SAP Error Message - Details

• Message type: E = Error

• Message class: GT - Database utilities

• Message number: 553

• Message text: Scan of table & is restarted

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 GT553 - Scan of table & is restarted ?

  The SAP error message GT553, which states "Scan of table & is restarted," typically occurs during the execution of a database operation, such as a report or a transaction that involves reading a large table. This message indicates that the system has encountered an issue while scanning the specified table, and as a result, the scan process has been restarted.
  Causes:
  
  Database Locking: The table may be locked by another transaction, causing the scan to be interrupted.
  Timeouts: Long-running queries may exceed the allowed execution time, leading to a restart of the scan.
  Memory Issues: Insufficient memory allocation for the database operation can cause the scan to fail and restart.
  Database Configuration: Certain database settings or configurations may lead to inefficient scanning of large tables.
  Corrupted Data: There may be issues with the data in the table, such as corruption or inconsistencies.
  
  Solutions:
  
  Check Locks: Use transaction codes like SM12 to check for locks on the table and resolve any conflicts.
  Optimize Queries: Review and optimize the SQL queries or reports that are causing the issue. Ensure that they are efficient and make use of appropriate indexes.
  Increase Timeout Settings: If timeouts are an issue, consider increasing the timeout settings in the database or application server.
  Memory Allocation: Ensure that the system has adequate memory allocated for database operations. This may involve adjusting parameters in the database configuration.
  Database Maintenance: Perform regular database maintenance tasks, such as reorganization or rebuilding indexes, to improve performance.
  Check for Corruption: Use database tools to check for and repair any data corruption issues in the table.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SM21 (to check system logs), and ST22 (to check dumps).
  SAP Notes: Search for SAP Notes related to GT553 for any specific patches or updates that may address this issue.
  Performance Monitoring: Use tools like ST03N to monitor performance and identify long-running queries or resource bottlenecks.
  Database Logs: Review database logs for any errors or warnings that may provide additional context for the issue.
  
  If the problem 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.