Hi Listers,
Our customer have one job which runs daily and one of the sqls which
executes like 500 times had 5 odd executions where it runs slower and most
of the time is being spent on "SQL*Net more data to client" . Normal run
times are like few seconds and the longer run times are like 1 hour or so.
For other executions we dont see that wait event being a problem.
What kind of tracing can we do to go in depth of the issue. I want to be
sure before i suggest some tuning at SDU sizing level etc.
Because we cannot predict when the slow run of the query will happen we
cannot wait for it and then run strace etc exactly at that time ,Basically
we will have to automate the tracing step.
--
Cheers,
Kunwar
