Use SQL collection type for your pipelined function return type, it
will work. SQL types seem to have fewer problems/restrictions. For a
non-pipelined table function, you will not be able to get data out of
it from SQL, since you need to type cast the table function. You can
not use type in a package for type casting.
Richard Kuhler <noone_at_nowhere.com> wrote in message news:<mDsFa.80026$x67.3598734_at_twister.socal.rr.com>...
> Jusung Yang wrote:
> >
> > Hmm... You sure? Can you show me the bugs? From this simple test, I
> > did not see the problem you described. Here, using parallel enabled
> > pipelined function, I want to transform data from 1 column based on
> > the condition on another column. Namely
>
> <snip>
>
> The primary bug I was referring to is (BUG 2982476). Here's a
> demonstration ...
>
>
> create or replace package pkg_pipeline_source as
>
> type ttab is table of number;
>
> function f_pipeline
> return ttab
> pipelined;
>
> end pkg_pipeline_source;
> /
>
> Package created.
>
> SQL> show errors
> No errors.
>
> SQL> alter package pkg_pipeline_source compile;
> alter package pkg_pipeline_source compile
> *
> ERROR at line 1:
> ORA-00600: internal error code, arguments: [17012], [0x2493199C], [],
> [], [],[], [], []
>
> SQL> drop package pkg_pipeline_source;
> drop package pkg_pipeline_source
> *
> ERROR at line 1:
> ORA-00600: internal error code, arguments: [4814], [5], [0], [0], [],
> [], [],[]
>
>
>
> Richard
Received on Wed Jun 11 2003 - 00:18:26 CDT
