Interesting scenario - select stmts missing in trace

[former_member615325]

Hello..We are trying to trace a long running process in production instance and surprisingly found production instance (oracle) is behaving differently to Quality instance, for the similar data, when we traced a transaction in Q, we are seeing select statements (on a conditions table) and we are missing the same select statements in production trace. Not sure what might be the reason for this missing selects in trace for the same tables. Please elt us know.

[Former Member]

Is the runtime on both systems comparable? If both systems run that transaction more or less the same, there is probably no relation from trace difference to your problem.

There is quite a bunch of possibilities, like the ones Stefan already mentioned. It could be something simple like you executed the transaction twice on one system and only once on the other. Sometimes parts of the execution get forked to another workprocess/user and are not captured. Quite often there is a bug or reason the statement is not visible as well.

Especially the long running SQL statements are a problem, either because were they already started before the trace was turned on or the other way round.

You would have to make sure if the behavior is always like that with a couple of separate trace runs, or you would need to use the debugger to check if the selects are really executed on both systems. But honestly i am not sure if it is worth the trouble.

Cheers Michael

[former_member615325]

Thank you for the input, we really had tough week figuring out the cause between Q and P instances on their different behaviour, we did unbuffer some pricing tables and that did the trick. Thanks again for your valuable input.

[stefan_koehler]

Hi,

are you really missing it or are they just super fast on production and do not appear in the top area? Another possible reason for this (except different business logic) could be the ABAP table buffering: http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f244446011d189700000e8322d00/content.htm

You need to check the buffering attribute (technical settings) on your own as you have not mentioned the corresponding tables.

Regards

Stefan