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
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
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
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
