In the command line for your Siebel application startup, use the /s filename
option. This will begin spooling all of the SQL that Siebel generates to an
output file named filename. If filename does not include an absolute path, it is
placed in the Siebel bin directory. If you are not familiar with the SQL output,
you may want to run Siebel once, up to the point of executing action with poor
performance, but not actually performing the action. Then exit and save the
output file. Restart the Siebel client and follow the same process, except that
you should execute the poor performance action this time and then exit
The difference between the output files is the SQL with poor performance.
Often this will consist of multiple SQL statements, although frequently it is
only one of the statements actually causing the poor performance. If several
statements are included for the action with poor performance, perform your
tests using all of them until you are able to isolate the ones causing the
In order to run the generated SQL through db2batch, you will need to edit the
output file to select just the desired portion of code.
In addition, you can use DB2 Event Monitor to get a summary of activity at the
completion of events such as statement execution, transaction completion, or
when an application disconnects.This is applicable for the thick clients only.