By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,426 Members | 1,729 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,426 IT Pros & Developers. It's quick & easy.

ODBC produces logoff event?

P: n/a
Does the breaking of an ODBC connection produce a logoff event?
I can't seem to get it to.

What I was hoping was to use a trigger to do automatic cleanup
of session specific data. But the closing of the ODBC does not
fire the logoff trigger, even though closing sqlplus does.

Is there something I'm missing here? Is there a better way to
cleanup session specific data when connecting through ODBC?
I'm concerned with the case where the other end (a VB app)
gets abnormally terminated.
Socks
Jul 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
pu*********@hotmail.com wrote in message news:<c7**************************@posting.google. com>...
Does the breaking of an ODBC connection produce a logoff event?
I can't seem to get it to.
Are you talking about a normal or an abnormal connection closure (i.e.
are you programmatically closing the connection or are you simulating
an application crash by pulling the cable?
What I was hoping was to use a trigger to do automatic cleanup
of session specific data. But the closing of the ODBC does not
fire the logoff trigger, even though closing sqlplus does.
What sort of session-specific data are you cleaning up? Unless you're
doing something odd, session-specific data should be cleaned up by
Oracle automatically when the Oracle session is terminated.
Is there something I'm missing here? Is there a better way to
cleanup session specific data when connecting through ODBC?
I'm concerned with the case where the other end (a VB app)
gets abnormally terminated.


Oracle will eventually notice that the client application has died and
close the session in this case...

Justin Cave
Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.