LOGON/LOGOFF Trigger Issue

2004-01-11 Thread Sami
Hi I am trying to maintain currently connected users list using LOGON/LOGOFF triggres. But I am experiencing some unexpected behavior for SYS user. CREATE OR REPLACE TRIGGER SCOTT.LOGON_TRIG AFTER LOGON ON DATABASE BEGIN insert into logon_info

Re: LOGON/LOGOFF Trigger Issue

2004-01-11 Thread Mladen Gogala
What happens is that you have a database wide logon trigger, not just a trigger on scott.schema which needs an execution context. A pseudo session with a SID=0 is established and the trigger is executed. Personally, I would use auditing (audit session or audit session by scott), not a database

RE: LOGON/LOGOFF Trigger Issue -(CLOSED)

2004-01-11 Thread Sami
Dear Mladen, Thanks for your response. SYS and REPADMIN users are keep on LOGGING-IN and LOGGING-OUT periodically in the background. That is why SYS user got deleted(when automatic LOG-OUT happens). Anyway I'll try auditing feature as you suggested. Thanks again, Sami -Original

RE: LOGON/LOGOFF Trigger Issue

2004-01-11 Thread Sami
Dear Mladen, Thanks for your response. SYS and REPADMIN users are keep on LOGGING-IN and LOGGING-OUT periodically in the background. That is why SYS user got deleted(when automatic LOG-OUT happens). Anyway I'll try auditing feature as you suggested. Thanks again, Sami -Original

RE: LOGON/LOGOFF Trigger Issue

2004-01-11 Thread Jamadagni, Rajendra
Correct me if I am wrong ... but Oracle *does* maintain a list of currently connected users ... it is called v$session. Why are you trying to do the same manually? Raj Rajendra dot Jamadagni at nospamespn dot com