Re: Tuning pipeline table function queries

From: Anurag Varma <avdbi_at_hotmail.com>
Date: Tue, 21 Oct 2003 05:52:21 GMT
Message-ID: <pQ3lb.13051$Rv5.1521@news01.roc.ny>

"Richard Kuhler" <noone_at_nowhere.com> wrote in message news:ReWkb.57734$th6.21460_at_twister.socal.rr.com...
> When using a pipeline table function in a query, it appears that Oracle
> uses the default statistics for that source (nothing surprising about
> that). Unfortunately, this often leads it to make some bad decisions
> about the execution plan. I could of course use the well documented
> hints to explicitly tell the optimizer which join methods to use, table
> order, etc... However, I'd rather not interfere with the optimizer any
> more than I have to. Along that line, I've tested things using the
> undocumented CARDINALITY hint and that gets things back on track nicely.
> Obviously, using an undocumented feature has it's own risks.
>
> What's your opinion?
> Any other suggestions?
>
> --
> Richard Kuhler
>

Richard,

Can you give a working example of the problem you are talking about?

It might be easier to comment on that.

Anurag Received on Tue Oct 21 2003 - 00:52:21 CDT