TOracleEvent and the duplicate session.

[Arvid]

According to the docs, the TOracleEvent duplicates a connection to avoid interfering with the main session.

Our client have a limited number of oracle session available (300). We would like to introduce TOracleEvent in our application, however this will result in 2 sessions from every instance of our program - something that most likely will lead to disaster since our client have 150-175 users.

Is there any way of not duplicating the connection? What's the cost?

 

[Marco Kalter]

To wait for an event, the session will be stuck in a call to dbms_alert.waitany or sys.dbms_pipe.receive_message. This session cannot do anything else while it is waiting. So, unless your application does not need to access Oracle in any other way while wating for these events, you will need 2 sessions.