Re: different query performance cluster nodes
- From: Greg Rahn <greg@xxxxxxxxxxxxxxxxxx>
- To: eglewis71@xxxxxxxxx
- Date: Thu, 28 Apr 2011 13:31:43 -0700
System stats only exist for a database, not an instance so that
shouldn't be the issue.
What if you cause a hard parse on both nodes - what plans do you get -
the same ones?
What may be the issue is that stats changed and there was an existing
cursor and it has not been invalidated which could explain different
plans on different nodes. The other thing to check is that there are
no differences in parameters across instances.
On Thu, Apr 28, 2011 at 11:39 AM, Edward Lewis <eglewis71@xxxxxxxxx> wrote:
> We have a 2 node rac cluster.
> When I run a query on node 1, it executes in 1-2 seconds.
> When I run the same query on the node 2, it takes over
> 2 minutes.
> The query plans are different with node 1 using an index,
> and node 2 doing a full table scan.
> The first server has around 583K consistent gets, and
> 6400 physical reads. The second server has 284 consistent gets, and
> 88 physical reads.
> Don't know if this is an issue, but I run system statistics,
> but only on 1 node. I haven't been able to find anything on running
> system stats in a cluster. Is it necessary to run system stats
> on both servers ?
--
Regards,
Greg Rahn
http://structureddata.org
--
//www.freelists.org/webpage/oracle-l
Other related posts:
