How To Fix BRAIN726 - CATT: Trace termination (short dump) when recording

SAP Error Message - Details

• Message type: E = Error

• Message class: BRAIN -

• Message number: 726

• Message text: CATT: Trace termination (short dump) when recording

What causes this issue?

The trace has been terminated. There are several possible reasons for
this:
The trace has been made unusable by changes made to the OLAP processor
interface.
The queries terminated because of a program error.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If queries terminate in mode M (Master), check in the Dump analysis
(ST22) to see if the termination was caused by function group RRX2. If
this is the case, the trace has become unusable due to changes made in
the interface. Execute the trace again. If the cause of the error is
somewhere else, check whether there is a corresponding OSS note and send
an error message.
If you cannot find an error in the dump analysis, go to transaction
RSRCATTTRACE and run your trace in ' ' mode.
When an error occurs, the program runs until a breakpoint. In the
debugger, choose 'Calls'. The termination occurs in a part of the
program that is three steps above the part of the program containing the
breakpoint. Using this program, look for OSS notes and send an error
message.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BRAIN726 - CATT: Trace termination (short dump) when recording ?

  The SAP error message BRAIN726 indicates that there was a trace termination (short dump) when using the Computer Aided Test Tool (CATT) for recording. This error can occur due to various reasons, and addressing it typically involves a few steps to identify and resolve the underlying issue.
  Possible Causes:
  
  System 
  Configuration Issues: There may be misconfigurations in the SAP system that affect the CATT functionality.
  Authorization Problems: The user executing the CATT may not have the necessary authorizations to perform the actions being recorded.
  Technical Errors: There could be bugs or technical issues in the SAP system, such as memory issues or problems with the application server.
  Data Consistency Issues: Inconsistent or corrupt data in the system can lead to unexpected behavior during recording.
  CATT Script Errors: If the CATT script being recorded has errors or is trying to access non-existent objects, it may lead to a dump.
  
  Solutions:
  
  Check Short Dump Analysis: Use transaction code ST22 to