Re: What hint would you try?
From: Chris Dunscombe <cdunscombe_at_yahoo.com>
Date: Fri, 10 Jun 2011 09:26:36 +0100 (BST)
Message-ID: <264355.67066.qm_at_web29701.mail.ird.yahoo.com>
Date: Fri, 10 Jun 2011 09:26:36 +0100 (BST)
Message-ID: <264355.67066.qm_at_web29701.mail.ird.yahoo.com>
And another Amen. There have been, and I'm sure there still are and will be in the future, a number of bugs in this area with hints/optimizer and ANSI SQL. I ran into one of these a couple of years ago when working with SAS generated SQL. (But the details have been paged out of limited my brain capacity, oh how I need a memory uopgrade). Chris ________________________________ From: Kerry Osborne <kerry.osborne_at_enkitec.com> To: breitliw_at_centrexcc.com Cc: post.ethan_at_gmail.com; oracle-l <oracle-l_at_freelists.org> Sent: Thursday, June 9, 2011 22:10:53 Subject: Re: What hint would you try? Amen to the second suggestion brother. Kerry Osborne Enkitec blog: kerryosborne.oracle-guy.com On Jun 9, 2011, at 3:52 PM, Wolfgang Breitling wrote: > For hints NO_UNNEST and NO_MERGE come to mind. > > I would also try what you get when you replace the ANSI join syntax with the >"traditional" Oracle join syntax. The optimizer doesn't speak ANSI very well. > > On 2011-06-09, at 2:28 PM, Ethan Post wrote: -- http://www.freelists.org/webpage/oracle-l
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jun 10 2011 - 03:26:36 CDT