Comments on: Tracking Oracle Logons

By: Nice Smile

Nice Smile — Mon, 16 Apr 2007 06:46:57 +0000

Interesting article, but I have a problem with abnormally terminated client sessions, which don’t trigger the logoff trigger. I need to catch those errors for many reasons.

By: Jon

Jon — Wed, 08 Mar 2006 16:49:37 +0000

UPDATE: I have found that the old version of this resulted in an ORA-1427 error when someone made an internal connection. The problem also came up when dbms_jobs were run. The code now ignores internal connections (where the session id is 0).

By: Jon

Jon — Wed, 09 Nov 2005 21:41:56 +0000

Nice tip Gary. I’ve got a similar problem that when users connect through Oracle Forms the forms server shows up instead of the host they are sitting at. It seems like the only way we can track the host down is by cross-referencing the web log on the Forms server. At least we can track it down if we need to.

Thanks for the feedback!

By: Gary

Gary — Wed, 09 Nov 2005 18:38:42 +0000

Very nice! When I set this up on my test server I found that logins from network machines that weren’t “hosts” did not populate the host column. I modified the login trigger as follows to catch the v$session.terminal field if sys_context(’USERENV’,'HOST’) is null
since both fields are char(30).

…
case
when sys_context(’USERENV’,'HOST’) is not null then sys_context(’USERENV’,'HOST’)
else
(SELECT TERMINAL FROM v$session
WHERE sys_context(’USERENV’,'SESSIONID’) = AUDSID)
end,
…

Thank you.