Comments on: SQL Tracing in Self Service Applications (CRM) within Oracle Applications 11i

By: Gerwin Hendriksen

Gerwin Hendriksen — Fri, 05 Jan 2007 12:31:40 +0000

Thanks for your comments John. I only like to add that in most situations you will create a new test Apps user to do the specific job, you want to investigate. In that way you will not get the issue you describe.

By: John Kanagaraj

John Kanagaraj — Fri, 05 Jan 2007 02:18:07 +0000

Nice one. However, I would add a 'tracefile_identifier' to this SQL so that the tracefile is easily identified in the udump directory. Thus the deftrace command would be: BEGIN FND_CTL.FND_SESS_CTL('','','','','','ALTER SESSION SET EVENTS='||''''||' 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 '||''''|| ' TRACEFILE_IDENTIFIER = ' || '''' || '' || ''''); END; Also, be aware that this will turn on the trace for *ALL* processes executing for that user, including any scheduled concurrent processes... John Kanagaraj

By: ronald

ronald — Wed, 03 Jan 2007 09:39:07 +0000

Very nice, thanks!