Find out what part of Siebel (e.g., view, applet, workflow, or script) initiated a specific SQL Id
Hi All,
We have identified several SQL IDs in the AWR report, but we're currently unable to determine which Siebel object or process (such as a view, applet, workflow, or script) is responsible for executing these SQL statements. What is the best approach to trace a specific SQL ID back to the originating Siebel component or functionality?
Thanks,
Pradeep K