Re: throwing exception in parallel pipelined table function
From: Frank Bergemann <FBergemann_at_web.de>
Date: Mon, 12 Dec 2011 02:56:19 -0800 (PST)
Message-ID: <cbe72fee-0ca4-48ad-936b-197f75286066_at_a17g2000yqj.googlegroups.com>
On Dec 8, 6: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
Date: Mon, 12 Dec 2011 02:56:19 -0800 (PST)
Message-ID: <cbe72fee-0ca4-48ad-936b-197f75286066_at_a17g2000yqj.googlegroups.com>
On Dec 8, 6: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 found it out myself meanwhile
In case of MULTIPLE parallel sessions started via pipelined table
functions, there is given a dedicated exception to the main thread:
ORA-12801: error signaled in parallel query server <string>
... instead of the concrete exception(s) raised by the individual
worker thread(s).
regards,
Frank
Received on Mon Dec 12 2011 - 04:56:19 CST