That probably puts you in 10% of the world's Oracle developers.
I don't do much developing now, but do regard it as a requirement for good coding to instrument your code - clearly people can and do re-invent the wheel for instrumentation, but d_a_i does already allow you to do this.
I mentioned my implementation in my presentation to UKOUG last year, which sounds similar to Ryan's proposed solution, namely a wrapper package which also includes the ability to write to trace and - like any good debug tool - doesn't need to be switched on in production, unless you need it. However there was a much more appropriate presentation by Gerry Bowman at the same conference which talked in much more detail about this approach - covered a 10g specific bug that you should know about if you are using pl/sql and so on.
I don't know if Gerry hangs out here, but I'll point him at this discussion and see if he can make the presentation publicly available.
I use it for 90% of the code I write
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of ryan_gaffuri@xxxxxxxxxxx Sent: Monday, September 25, 2006 10: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.
-- Niall Litchfield Oracle DBA http://www.orawin.info -- //www.freelists.org/webpage/oracle-l