How To Fix TB680 - Analysis incomplete! Old log tables still contain entries.

SAP Error Message - Details

• Message type: E = Error

• Message class: TB - SM31 table maintenance messages

• Message number: 680

• Message text: Analysis incomplete! Old log tables still contain entries.

What causes this issue?

As of Release 4.0 table changes are logged in a new table. Only the new
table will be analyzed, that is logs in the old log table will not
become visible.

How to fix this error?

If you require a complete overview of earlier logs as well (that is
before Release 4.0), then, before this report, start the program
<DS:RE.RSDBLOGCONV40>RSDBLOGCONV40</> in the background. This deletes
logs from the old log table and writes them to the new one.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TB680 - Analysis incomplete! Old log tables still contain entries. ?

  The SAP error message TB680, which states "Analysis incomplete! Old log tables still contain entries," typically occurs in the context of the SAP system's transport management or during the execution of certain background jobs related to data analysis or transport logs. This message indicates that there are still entries in the log tables that need to be processed or cleared before the analysis can be considered complete.
  Cause:
  
  Incomplete Analysis: The analysis process that was supposed to clean up or process the log entries did not complete successfully.
  Database Locking Issues: There may be locks on the log tables that prevent the analysis from completing.
  System Performance Issues: If the system is under heavy load, it may not be able to process the log entries in a timely manner.
  Configuration Issues: There may be configuration settings that are preventing the proper execution of the analysis.
  
  Solution:
  
  Check Log Tables: Use transaction codes like SE11 or SE16 to check the contents of the relevant log tables (e.g., TBTCO, TBTCP) to see if there are entries that need to be addressed.
  Run Analysis Again: Sometimes, simply re-running the analysis can resolve the issue. You can do this through the appropriate transaction or program.
  Clear Old Entries: If the log entries are no longer needed, consider clearing them out. This can often be done through specific SAP transactions or programs designed for log management.
  Check for Locks: Use transaction SM12 to check for any locks on the log tables. If there are locks, you may need to resolve them before proceeding.
  System Performance: Monitor system performance and ensure that there are sufficient resources available for the analysis to complete.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), SM12 (Lock Entries), and ST22 (Dump Analysis).
  SAP Notes: Regularly check for updates or patches that may address known issues related to this error.
  Documentation: Review SAP documentation related to transport management and log analysis for best practices and troubleshooting steps.
  Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it impacts critical business processes.
  
  By following these steps, you should be able to address the TB680 error and ensure that the analysis process completes successfully.