Custom Tables Trace missing via Tcode ST12

[SAPSupport]

Hi Team,

As part of performance testing for one of the feature deployment, collecting the trace for the RFC function module via Transaction Code ST12. Observed few of the custom tables traces are missing in SQL summary(traces).

Thanks.

Regards,

Suvarchala C

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

There could be several reasons when some traces were not found from the collected ST12 trace.
Most of them is caused by the setting for the ST12 trace.
　
1. No. trace activations
If a trace is collected in a dialog mode with the option 'User/Trasks', all processes executed by the specified user will be the target of the trace.
And in case of ST12, only 1 trace will be activated at one time so the first process which is caught by the trace demon will be the target.

Let's say, a ST12 trace is collected with a user name "A" in a dialog mode(not a scheduled mode by '>Schedule' button) and value 5 is configured for 'No. trace activations'.
In this case, 5 traces will be activated for processes executed by the specified user.
So the 5 processes which are caught by the trace demon in order will be traced but the traces for other processes will be not collected.
　
As mentioned in the section 'Trace for - User/Task' of the KBA 2436955, enough values of 'No. trace activations' need to be configured. Maximum 99 traces can be activated.
　
2. Size & Duration
There are limitations with the ST12 trace.
Regardless how many traces are activated, if the total time of trace reaches to the maximum time or the size of collected traces reaches to the maximum size, the trace will be stopped.
　
The time and size is configured in the section 'Size & Duration' of ST12 screen.
It is set to Large (20MB/4200 sec max.) by default.
But if the trace you are going to collect is big or if you don't know how big it is, it is recommended to set it to 'Max' with '99BM/4200 sec max.'.
It is same in a dialog mode or in a scheduled mode by '>Schedule' button. Details also can be checked from the KBA 2511272.
　
3. Processes which were not finished before the trace was stopped
The trace will collect the processes which was started after the trace was started (In a scheduled mode by the button '>Schedule>', I recommend to set the start time of the trace at least 5 minutes before the targer processes are started.).
　
And the trace which were started after the trace was started but not finished before the trace was stopped, it will not be included in the trace. Especially, long SQL executions which were not finished before the trace was stopped, its trace will not be recorded in the result.
　
With all above points in mind, I recommend you to collect ST12 trace once again.