DXE Execution plan in OBIEE

DXE Execution means “Data Transformation Engine which handles post-processing of the BIServer results within OBIPS”.

The post-processing can involve resorting, filtering, aggregating, and/or indexing the original BIServer result set so that the data can be consumed by a view’s renderer. Some of this was occurring in 10g as well but in 11g we moved this processing logic into our workflow engine so that

1) it can be automatically kicked off when the BIServer query finishes and
2) the renderer thread can now wait for the BIServer query and the post-processing to both complete.

This allows the end user to now cancel the post-processing (which may take considerable time) and allows us to give better feedback to the user (basically indicating that we are still working on the results).

The queued status generally means it is waiting on the parent BIServer query to finish. There’s an ER to give a different status when it is waiting on a parent as queued can also mean there is just no threads available to handle the job.

It is exposed mainly for support purposes. There may be several processing jobs based on the same BIServer result and each one may be consuming CPU and memory. It wouldn’t be very indicative if these jobs were not shown. Also each individual job can be independently cancelled.”In this particular case DXE Execution is not taking long to run.  It is a thread for Presentation Services processing of the data sent from the OBI server which is covered by the session log.  The DXEExecution performs no work until the session log is completely done, so it will always take longer than the session log, but it is only doing work once the OBI server is done.