title: Tagging sql statements for tracing and debugging
body: <p>We have a large enterprise consisting of many apps both old and new backed by Oracle 10G.  When blocking sessions or deadlocks occur and we get trace reports it would be super handy to be able to have embedded some details in the sql so that we know both what app, and specifically where it was executed from.  In addition to helping speed up the resolution time, it can help us find places where business processes were stepping on each other.  We have a few thoughts on how this could be achieved, but I am curious if this is already a solved problem.  Any thoughts or details on any successful (or otherwise) attempts would be appreciated.</p>