I, too, have a situation whereby all users access the db via third party app
with single credentials - haven't found a way around it, other then
application-side logging
-bill
-Original Message-
Sent: Wednesday, May 22, 2002 11:34 AM
To: Multiple recipients of list ORACLE-L
Hello
Denham Eva wrote:
Hello Listers,
I have what I hope is challenging problem.
I am trying to create a procedure that execs from a trigger on a table.
Simple enough.
But I want to capture the OSUSER value from v$session so that the there is a
history of changes to the table and by whom.
One thing that is possible to get a unique system id you can allways do
the following:
When the user logs into your application, place a record in a table stating
all the pertinent info like application, machine id, date/time, etc.
Allowing with this info use the DBMS_SESSION package and
you can also get the sid directly (if you don't want to use any packages)
from the steve adams script:
select
p.pid,
s.sid,
s.serial#
from
sys.v_$session s,
sys.v_$process p
where
s.sid = (select sid from sys.v_$mystat where rownum = 1) and
p.addr = s.paddr
/
from this you can
