EBS Customizations (MOSC)

MOSC Banner

Disabling tracing from concurrent program definition window causing performance issue

edited Jan 3, 2012 7:13PM in EBS Customizations (MOSC) 5 comments
Hi,

There is something wierd about a couple of custom concurrent programs we are using. These jobs has Oracle Report as executable. Earlier these jobs use to take around one and a half hours on an average to get completed even if it is not processing any data at all. In order to trouble shoot the performance issues we enabled the trace option from the cuncurrent program defination window by checking the Enable Trace check box. Surprisingly the job got completed in less that a minute.
When we disabled the trace option then again it started executing for hours. We have enabled and disabled the tracing several times and it looks like whenever trace is enabled the job is performing as expected, but disabling the trace is causing the performance to go down whereas the reverse case might have been logical.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center