On Thu, Oct 17, 2013 at 9:48 AM, Chris Taylor < christopherdtaylor1994@xxxxxxxxx> wrote: > Hey, the other thing you could do, if you know some identifying > information for these sessions, like OSUSER, machine/terminal, client_info > etc, you could setup a LOGIN TRIGGER that enables a 10046 trace and capture > any/all SQL executed in the session. > > Some apps (like PeopleSoft) will populate client_info so it makes it > easier to trace one session instead of all the connected sessions. Maybe > you have something available to you that will enable you to create a > limited trace on a few sessions. > So far there doesn't seem to be any distinguishing info for the sessions, which would make it easy to separate them from other app-related connections. If I'm able to come up with something, however, I'll certainly consider doing this. Thanx! -- //www.freelists.org/webpage/oracle-l