How To Fix PERFTRAC090 - Log GUID text & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: PERFTRAC - Messages on Global Performance Analysis

• Message number: 090

• Message text: Log GUID text & does not exist

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 PERFTRAC090 - Log GUID text & does not exist ?

  The SAP error message "PERFTRAC090 Log GUID text & does not exist" typically relates to performance tracing or logging issues within the SAP system. This error indicates that the system is trying to access a log entry identified by a GUID (Globally Unique Identifier), but it cannot find the corresponding log entry in the database.
  Causes:
  
  Log Deletion: The log entry may have been deleted or purged from the database, either manually or through a scheduled job that cleans up old logs.
  Incorrect GUID: The GUID being referenced may be incorrect or malformed, leading the system to search for a non-existent log.
  Database Issues: There may be issues with the database that prevent the retrieval of the log entry.
  Configuration Issues: The performance tracing or logging configuration may not be set up correctly, leading to inconsistencies in log generation and retrieval.
  
  Solutions:
  
  Check Log Existence: Verify if the log entry with the specified GUID exists in the database. You can do this by querying the relevant log tables directly (e.g., TST03 for performance traces).
  Review Deletion Policies: If logs are being deleted automatically, review the configuration settings for log retention and adjust them if necessary to retain logs for a longer period.
  Validate GUID: Ensure that the GUID being referenced is correct. If it was generated by a specific process, check that the process completed successfully and that the GUID is valid.
  Database Health Check: Perform a health check on the database to ensure there are no underlying issues affecting data retrieval.
  Reconfigure Logging: If the logging configuration is incorrect, reconfigure it according to best practices and ensure that the necessary components are enabled for logging.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like ST01 (System Trace), ST05 (SQL Trace), or ST22 (Dump Analysis) to gather more information about the issue.
  Performance Tracing: Familiarize yourself with how performance tracing works in SAP and the relevant tables involved in logging.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.