I've noticed that v$session.osuser is null when the session in question is
running a dbms_job--maybe you can use that (possibly in conjunction with
other clues).
On 10/6/05, Charlotte Hammond <charlottejanehammond_at_yahoo.com> wrote:
>
> Hi All,
>
> We have an after logon trigger on our database. This
> trigger also gets fired by DBMS_JOBs whenever they run
> which we don't want.
>
> Is there a neat way to prevent this? I was thinking
> of checking V$SESSION.TYPE within the trigger to
> detect the BACKGROUND processes but it seems to be
> null at the time the trigger fires. Another option
> was to check V$SESSION.PROGRAM but this was getting
> messy. Any better ideas?
>
> Thanks
> Charlotte
>
> PS. Oracle 9.2
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
> --
> http://www.freelists.org/webpage/oracle-l
>
--
Paul Baumgartel
paul.baumgartel_at_aya.yale.edu
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Oct 06 2005 - 11:42:09 CDT
