You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
One of the most powerful ways to identify a session is based on its client identifier. This column resides in v$session and can be set by the dbms_session.set_identifier procedure. Increasingly, applications are setting the client identifier in addition to the module and action.
If sessions are not persistent (that is, they connect, run SQL, and disconnect), then combining a logon trigger with setting the client identifier may enable you to pinpoint a specific user or group of users. Figure 5-20 shows a working logon trigger used for just such an occasion.
Figure 5-20. This actual working logon trigger can be used as a template to set a session's client identifier based on an amazing array of possibilities.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|