The TOracleEvent requires an extra session because it needs to wait for events (dbms_signal.wait), and a session can only do one thing at a time. So either the session waits for events, or it does something else, but not both. Version 3.4 does not change this.

I am not sure about the alert log warnings. If there are a lot of users and it does indeed happen that people turn of the PC or kill the process of your application, you would expect that the corresponding session eventually times out. This could still lead to errors though.

------------------
Marco Kalter
Allround Automations