Hello Tom, Your books, Effective Oracle By Design and Expert Oracle (the original edition and volume one of the new edition), press home the importance of incorporating the ability to provide runtime trace and profiling information when required.
Much thought has been through my mind regarding a simple, consistent design of such functionality, applicable to most programming environments.
the instrumentation should always be there it should always be infinitely detailed but most of the time, it shouldn't be executed.
dbms-application-info - call it upon procedure entry maybe (major routine entry) but not every other line of code, every time - that is too much. February 14, 2011 - am UTC they would be insufficient.
Maybe using the code behind Ask Tom, if it's not a cheeky request? If the application was written in plsql - I might be using our developed "debug.f" routine In C, I used a debugf macro...