Running Extended SQL Traces On OWB Process Flows

If you've been following my work on putting an OWB Performance Tuning Framework together, and you read yesterday's article on running an event 10046 extended trace on a mapping, you might be interested in some more work I've now done on running an extended SQL trace on an entire OWB process flow.

The approach I ended up using was to use DBMS_IDENTIFIER.SET_IDENTIFIER to set a common client ID for each mapping, then use DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE to enable trace for this particular client ID, then use trcsess to "weave" the separate trace files together. I've written up the approach and findings in "Using DBMS_MONITOR To Trace OWB Process Flows" and if anyone's got any feedback or additional ideas, please let me know.