I am trying to find an efficient way to trace a session in a database
in which all connections coming into the database are through a
middle-tier (web server, etc), and thus all logins to the database are
the same as well as the OSUSER. An example of this is Siebel, in which
all logins to the database is SIEBELSA and the osuser is LDAPUSER.
If a user is complaining about a slow session on a database with 1000+
concurrent sessions, how would you trace this session? Asking the user
to connect at a certain time to find a recently connected session does
not work because sessions connect/disconnect several hundred times per
minute. A logon trigger would also not work for the same reason.
Received on Tue Jun 21 2005 - 13:29:39 CDT
