RE: SQL faster "direct" than CM

From: Mark W. Farnham <>
Date: Mon, 25 Apr 2011 18:12:05 -0400
Message-ID: <10ac01cc0395$d09b4970$71d1dc50$>

Different plans?  

And if different plans, then why?  

Since they run differently at the same time, it seems reasonable to conclude that either:  

  1. You have different session parameters in the two sessions
  2. TOAD is a direct connection to the database server and there is a pathologically bad connection between the application server on which the CM resides and the database server
  3. You didn't mention whether you are RAC, some aspect of #2 above could relate to the TOAD session being against an instance where all the data the job needs is cached versus a CM connected to a different instance.

That's all I can think of at the moment for an abstract undefined job from the different tools or sessions. There are probably additional reasons, but first I'd check those, which should not be too tough.  

Good luck,  


From: [] On Behalf Of Stephen Andert
Sent: Monday, April 25, 2011 5:50 PM
To: Stephane Faroult
Subject: Re: SQL faster "direct" than CM  

Yes, it is on a SAN. Not sure what other machines may be doing at the same time, but even when the CM job and the TOAD job are run at the same time, the TOAD job runs faster.         

On Mon, Apr 25, 2011 at 2:52 PM, Stephane Faroult <> wrote:

Running on a SAN and other machines connected to the same computing their stats at the same time?

Stephane Faroult
RoughSea Ltd <>
Konagora <>
RoughSea Channel on Youtube <>

On 04/25/2011 10:51 PM, Stephen Andert wrote:

Do you have any ideas on why this would run in Toad in 2 minutes and take over 4 hours running through the concurrent manager? Actually up until this past week, 4 minutes is the usual run time for this job.  

I have looked at StatsPack for one of the 4 hour runs and other than about 75% of the time being I/O related. did not see anything out of line.  

Financials 11.5.8


(what am I missing?)  

Received on Mon Apr 25 2011 - 17:12:05 CDT

Original text of this message