What version? 9205: SQL_TEXT EXECUTIONS CPU_TIME ELAPSED_TIME ---------------------------------------------------------------------------- ----------------- ---------- ---------- ------------ BEGIN DBMS_APPLICATION_INFO.SET_MODULE(null, null); END; 16010775 3398890000 3371185213 BEGIN DBMS_APPLICATION_INFO.SET_MODULE(:1,NULL); END; 146026 54510000 57240101 BEGIN DBMS_APPLICATION_INFO.SET_MODULE(module_name => :module, action_name => :action); END; 2040799 473040000 471813754 So, 3398890000/16010775 = 212 54510000/146026 = 373 473040000/2040799 = 231 Some overhead, but not much on the server. Also, see note: https://metalink.oracle.com/metalink/plsql/f?p=130:3:11377674459850224176::: :p3_database_id,p3_docid,p3_show_header,p3_show_help,p3_black_frame,p3_font: NOT,311105.1,1,1,1,helvetica and other bugs. ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of ryan_gaffuri@xxxxxxxxxxx Sent: Monday, September 25, 2006 8:38 PM To: oracle-l@xxxxxxxxxxxxx Subject: How extensively do you use dbms_application_info ? Would you use dbms_application_info for every single pl/sql procedure? Even ones that just run a single query? I was thinking about floating this idea at work. This is how I would do it. Module: PL/SQL Package and Functional Module(this would be an internal name) Action: Procedure, plus any values that would go into bind variables. -- //www.freelists.org/webpage/oracle-l