![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
On Dec 8, 6:42*pm, Frank Bergemann <FBergem... (AT) web (DOT) 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |