Re: performance issue after upgrade to oracle 184.108.40.206 linux 32 bit.
Date: Tue, 3 Nov 2009 09:44:25 -0800 (PST)
On Nov 3, 8:22 am, Charles Hooper <hooperc2..._at_yahoo.com> wrote:
> On Nov 3, 10:29 am, lsllcm <lsl..._at_gmail.com> wrote:
> Note also that it is possible that the object statistics and optimizer
> parameters (FIRST_ROWS_n, for example) differ between the Oracle
> David's suggestion of a 10053 trace is a good one - just keep in mind
> that such traces only appear during a hard parse.
A bit of a stretch, but consider this: rownum is assigned after the predicate is processed, but before sorting is done. "Bug 6438892 : Suboptimal plan with ROWNUM predicate and NESTED LOOPS." is in the 220.127.116.11 patch set, bug not published. So maybe there is some mysterious optimizer bug here, set off by the order by even though rownum is not originally a predicate. Try patching beyond the base release and see if the problem is still there.
-- _at_home.com is bogus. Do not fart next to a cellphone. http://www.signonsandiego.com/news/2009/nov/02/wwwxconomycom48394/Received on Tue Nov 03 2009 - 11:44:25 CST