st05,activate trace

[Former Member]

can anyone explain how to activate the trace for va01 transaction

[Former Member]

call the transcation in separate mode, i.e /ost05

and activate it

[Former Member]

Goto ST05 ---> Active Trace.

then goto VA01 perform whatever you want to do then again ST05 ---> Trace Off

Click on Display trace you can see all possible scenarios.

Thanks,

Sree

Edited by: t sree on Feb 28, 2008 4:15 PM

[Former Member]

SQL Trace – ST05

It provides the developer with the ability to analyse database select statements. Simply execute ST05

to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05 and click on list trace to view the details.

Starting the Trace:

To analyze a trace file, do the following:

...

Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.

Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).

If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter.

Typical filter criteria are: the name of the user, transaction name, process name, and program name.

Now run the program to be analyzed.

Stopping the Trace:

To deactivate the trace:

...

Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.

Select the trace functions that you want to switch off.

Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-

Analyzing a Sample trace data:

PREPARE: Prepares the OPEN statement for use and determines the access method.

OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.

FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

[Former Member]

Steps

1. Goto ST05 Transaction and select trace on ..

2. Now enter ur transaction VA01 and run the transaction..

3. Once you done transaction and then come back to ST05 - Trace off and display list.

[Former Member]

> PREPARE: Prepares the OPEN statement for use and determines the access method.

> OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.

Please be aware that a good trace does not contain PREPARE and OPEN statements, because you should always run your program at least once beofre you run the trace.

If you do so, then your trace will only contain REOPENs.

This sound like a small change, but the changes in all measured time will be substantial !!

Don't interpret the detailed trace but the summary, see here :

/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

Siegfried

[Former Member]

Hi Raghunandan,

Additionally make sure that no one else is logged into the system with the same user ID and password that you are using while performing SQL trace, else all the operations performed by the other users will be recorded along with your's.