Re: stored outlines - cursor sharing

Well, you have to remember that most
of the people at Oracle are just mere
mortals, fumbling around and using trial and error, just like the rest of us.

Every document on metalink that talks about mixing stored outlines and cursor sharing shows quite clearly that the authors haven't quite figured out what's going on.

As you point out - you can create stored outlines with cursor_sharing = force -
so anyone who write 'cursor_sharing = force disables the creation of stored outlines' is clearly wrong.

cursor_sharing = force
DOES NOT disable the creation of
stored outlines. It just makes the
'create or replace ..' option behave
in a slightly counter-intuitive way.

I don't think anyone would say that
cursor_sharing = force disables the
use of explain plan. It's the same
problem, it's not so obvious with
explain plan.

Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html Public Appearances - schedule updated Dec 23rd 2004

"Oradba Linux" <techiey2k3_at_comcast.net> wrote in message news:i-Sdnb9oNtJ_eH3cRVn-ig_at_comcast.com...
> Oracle 9204 - RHES3.0
>
>
> Cursor_sharing = force disables creation of stored outlines. Refer to the
> metalink documentation bug Bug.2976681. This is a change from Oracle 8i
> behavior. But the following example works by setting cursor_sharing =force
> and the stored_outline is getting used.
>
>
Received on Sun Jan 09 2005 - 03:37:29 CST