Re: throwing exception in parallel pipelined table function

From: Mark D Powell <Mark.Powell2_at_hp.com>
Date: Fri, 9 Dec 2011 09:40:54 -0800 (PST)
Message-ID: <5b906e19-7a8a-4891-80dd-bf9f8c15e8d0_at_h5g2000yqk.googlegroups.com>

On Dec 8, 12:42 pm, Frank Bergemann <FBergem..._at_web.de> wrote:
> what happens to such?
> In my application it seems, it is catched by the main thread .
> But i wonder how this can work if MULTIPLE parallel pipelined table
> functions raise exception at different location of the code - e.g. for
> user abort of main session(?!)
>
> - many thanks!
>
> regards,
> Frank

I take it you mean the error is "caught" by the main session. Normal default error handling is to stop processing and pass the error back to the caller. If the caller does not handle the error it will be terminated and in the case of session running SQL in parallel so would the PQO slave sessions.

As far as if Oracle will run an SQL statement that makes use of a pipelined function in parallel I would have to test since we have so few of both that I am not sure I have ever seen an attempt to use both features together.

HTH -- Mark D Powell -- Received on Fri Dec 09 2011 - 11:40:54 CST