ODBC produces logoff event?

[puppet_sock@hotmail.com]

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

[Justin Cave]

Re: ODBC produces logoff event?

puppet_sock@hot mail.com wrote in message news:<c7976c46. 0312181439.762b 6fe7@posting.go ogle.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 programmaticall y 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