This is true. But you can capture the OS user if you need
to. We have done that in a few instances. The clients comes
into the application using a generic Oracle userid, but we
need to trap who made particular changes in the system. We
capture the OS_user from the SYS_CONTEXT function.
- Daniel Fink <Daniel.Fink_at_Sun.COM> wrote:
> You also need to take the application layers into
> account. If the user
> authentication occurs at the app/web level and the
> database login is a
> 'generic' account or connection pooling is used, you
> might not be able
> identify the user at the database level.
>
> Regards,
> Daniel Fink
>
> Rachel Carmichael wrote:
>
> > As far as I know, there is nothing within the database
> that will log
> > last sign on. Rather than turn on auditing, what about
> a login trigger
> > that records the userid and date in a table?
> >
> > You can collect more information that way -- machine
> they logged in
> > from, program they used etc..
> >
> > Rachel
>
>
>
> Please see the official ORACLE-L FAQ:
> http://www.orafaq.com
>
> To unsubscribe send email to:
> oracle-l-request_at_freelists.org
> put 'unsubscribe' in the subject line.
> --
> Archives are at
> http://www.freelists.org/archives/oracle-l/
> FAQ is at
> http://www.freelists.org/help/fom-serve/cache/1.html
>
>
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Fri Jun 25 2004 - 09:11:19 CDT
