It must be possible to profile based on other logging modules than DBUG_PROFILER.

[gpaulissen]

When you activate the channelPROFILER via DBUG.ACTIVATE('PROFILER') you will get profiling. However when other channels like 'LOG4PLSQL' are activated you should be able to determine profiling info as well.

Therefore you must replay the enter/leave actions in the other channel logging thru DBUG_PROFILER.

First step is to add timestamps (Oracle function SYSTIMESTAMP) to other channel logging so you determine the time elapsed. Next step is to enhance the packages DBUG_*:

• DBUG_PROFILER should have an enter/leave with a timestamp added.
• DBUG_<other channel> must have some feed procedure to invoke DBUG_PROFILER based on its own logging.

[gpaulissen]

See DBUG_PROFILER.ENTER, DBUG_PROFILER.LEAVE and DBUG_LOG4PLSQL.FEED_PROFILER. Table TLOG altered with two new columns: LSESSION and UTC_TIMESTAMP.