Re: SESSION INFO VIA AUDITING + LOGON TRIGGERS

kumar_929_at_yahoo.co.uk (AMIT) wrote in message news:<6f94b59f.0403160327.38b3bf87_at_posting.google.com>...
> But the problem is that, the information will not be deleted from the
> client info table , if the user logoff abnormally from the database.
> How to overcome this issue?
> I heard that if we use views instead of the table
> &#8220;client_info&#8221;, which I am using, we could manage this
> issue.
> Could someone explain how should we do that?
>
> I am using auditing + logon and logoff trigger in order manage the
> session info.

> 'INSERT INTO client_info(session_id,client_name,sid,
> serial#,workstation,host_name,logon_time , description)
> select a.sessionid,a.username , b.sid, b.serial#, a.os_username,
> b.machine,b.logon_time,a.comment_text from user_Audit_trail a ,
> V$session b
> where a.sessionid = b.audsid
> and a.username = b.username
> and a.sessionid=userenv(''sessionid'')';

Is true that your solution is probably not the best imaginable. I think that the suggestion with a view means, that you're basically doing a join between two tables and inserting the result into the other table.
So a better way is just to create a view based on the same query and when you will have to look at currently logged users, just select from this view, where only actual data are going to be stored. This is much more sensible than your trigger stuff.

--
Dusan Bolek

Email: spambin_at_seznam.cz
Pls add "Not Guilty" to the subject, otherwise your email is going to
be burnt as a SPAM.