Show TOC

Procedure documentationEvaluating Transaction Correctness in a Managed System

 

The transactional correctness evaluation performed directly in a managed system consists of three steps. As the transaction correctness tool evaluates performance traces, you have to record a trace of the transaction you want to evaluate, before using the tool.

Procedure

Step 1: Recording a Performance Trace

  1. In the managed system, go to transaction ST05.

  2. Select SQL Trace and Enqueue Trace.

  3. Choose Activate Trace.

  4. Execute the transaction or step that you want to analyze.

  5. Choose Deactivate Trace.

Step 2: Using the Transaction Correctness Tool

  1. Start the transaction correctness tool by calling report /SDF/DCC_TC.

    The system displays the selection screen for the trace records that can be evaluated. If you have captured an RFC call in the trace, enter the RFC type under RFC Type for Evaluation:

    • NUNI for no RFC or un-identified RFC type

    • SRFC for synchronous RFC

    • ARFC for asynchronous RFC

    • QRFC for queued RFC

  2. Select the performance trace you have recorded, and choose Continue.

    The system lists all database changes in your performance trace, with comments indicating where transactional correctness is at risk.

Step 3: Displaying Results

  1. Check the results of the evaluation.

    The results window contains the following information:

    Field

    Description

    Record no.

    Number of evaluated database trace record

    Trace date

    Timestamp (date) of the recorded trace

    Trace time

    Timestamp (time) of the recorded trace

    Transaction

    Transaction the trace was executed from

    Process Type

    Work process type in which the action was executed

    Program

    Executing program

    Table

    Table the statement was performed on

    Statement

    Type of the analyzed statement.

    Note Note

    The tool only analyzes and lists INSERT, UPDATE, UPSERT, and DELETE statements, and COMMITs and ROLLBACKs. For the analysis of enqueues and dequeues, ENQUEUE, DEQUEUE, and DEQUEUE ALL statements are also considered.

    End of the note.

    Comment

    If transactional correctness is at risk, a warning message is displayed.

  2. Handle the results depending on the content of the warning message. For more information, see Handling Transaction Correctness Warning Messages.

More Information

For more information, in the SAP NetWeaver documentation at http://help.sap.com/netweaverInformation published on SAP site, search for Performance Trace.