Oracle Consulting Oracle Training Oracle Support Development
Home
Catalog
Oracle Books
SQL Server Books
IT Books
Job Interview Books
eBooks
Rampant Horse Books
911 Series
Pedagogue Books

Oracle Software
image
Write for Rampant
Publish with Rampant
Rampant News
Rampant Authors
Rampant Staff
 Phone
 800-766-1884
Oracle News
Oracle Forum
Oracle Tips
Articles by our Authors
Press Releases
SQL Server Books
image
image

Oracle 11g Books

Oracle tuning

Oracle training

Oracle support

Remote Oracle

STATSPACK Viewer

Privacy Policy

 

 
 

Oracle Traceability

Article by Rampant Author Brian Carr

If you have a home-grown application that does not allow traceability from the application to the database this tip is for you.

If your application uses a "gateway/proxy" user to talk to the database the DBA is limited in his/her ability to track back a high-impact SQL to the user or module executing it.

Recommendation:
Populate additional information into DBA views to allow better traceability of queries in the database back to the user/module that is executing them. DBMS_APPLICATION_INFO provides a way of populating the V$SESSION and V$SQLAREA views with context information about application users. Oracle's eBusiness Suite uses this to allow DBAs to identify what module a user is in, what the current transaction is and what the context is. By using DBMS_APPLICATION_INFO the DBA will have better visibility to queries that are happening in the database and how these relate to application functionality.

 

 

 

   

 Copyright © 1996 -2016 by Burleson. All rights reserved.


Oracle® is the registered trademark of Oracle Corporation. SQL Server® is the registered trademark of Microsoft Corporation. 
Many of the designations used by computer vendors to distinguish their products are claimed as Trademarks