An alternate option
A reader, February 15, 2011 - 8:34 am UTC
In Enterprine Manager, click on the SID. This will bring up the "Session Details" page. Select the "General" link. Under "Client" section, there are details on who the user is, which terminal the user is logged in from and lot of other useful information about what that SID is doing.
February 15, 2011 - 8:43 am UTC
I don't have EM in front of me right now - does it show the connect proxy user information?
Using TOAD no 'PROXY AUTHENTICATION ONLY'
Apps Dba, December 18, 2012 - 5:44 am UTC
Hi Tom,
First post but many reads ... of books, magazine and asktom, due to the excellent information and the quantifiable approach to everything.
I came open this post when investigating an idea we have to use proxy users to give audited access to the main database application user (APPS for EBS) to some people from the development teams: conn DEVGUY[APPS]. And also to prevent them from needing to know the password.
When testing with connections from TOAD I note that there are two connections set up but none of them has the ACTION_NAME "PROXY AUTHENTICATION ONLY" unlike the case for SQL*Plus. Any idea why this may be the case?
For extracting audit information I don't think this matters since I can always use just the join on PROXY_SESSIONID and SESSIONID to distinguish proxied actions for a given user (developer).
Thanks.
December 18, 2012 - 1:16 pm UTC
... Any idea why this may be the case? ...
ask quest maybe? we don't do toad....