Re: How can I "totally" capture the logoff trigger?

Jeff-

I am slightly confused. You want to prevent memory leaks from variables created by your application? If you create a variable in your session, presumably you are creating a pl/sql package variable, right? When your session ends, all variables you create are destroyed. I suppose if you use shared servers / mts you might encounter a UGA memory leak, but that would be an Oracle bug. Still, it would be weird to see a memory leak that was not cleaned up when a session terminated.

So, if I am off the mark, could you clarify your question?

• ricky

Jeff Chan wrote:
>
> Dear all,
>
> I have initialized some variable when a user logon the database.
> Originally, I decide to destroy such variable during the logoff trigger
> symmetrically. However, I found that under some situations, e.g. close the
> sqlplus window instead of typing disconnect in sqlplus, the logoff trigger
> will not be executed. How can I make my procedure clean so that no memory
> leak problem occur?
>
> Thanks in advance.
>
> Jeff.
Received on Tue Nov 06 2001 - 08:58:51 CST