The upcoming now available version of Mumbai will have has “execution plans on steroids” and graphical execution plans.

To create an execution plan you can click on the tree-like icon in the console window:

Here you have the option to either use EXPLAIN PLAN or actually execute (and optionally fetch all rows) and then use DBMS_XPLAN.DISPLAY_CURSOR to generate the execution plan. You can also temporarily set the parameters STATISTICS_LEVEL and _ROW_SOURCE_SAMPFREQ to generate more accurate timing values (see Jonathan Lewis’ “Heisenberg” post for a discussion of the implications.

Further, you can decide if you want to show the execution plan in the lower part of the console window or in a separate window. Only the later option will let you see the graphical tree representation for the execution plan.

Once you click “Ok” the execution plan will show up. For the example SQL in the screenshot above, it might look like this:

Besides the textual execution plan, you can see a graphical tree representation for your execution plan:

A few hints for using this graphical execution plan:

Use the navigation tree on the upper right side to navigate in large execution plans. Clicking on a node in the navigation tree will select the node in the main tree.

Filter and access predicates are indicated by little icons on the lower right of the nodes. The hint for a node will show the actual predicates.

A node might be marked with one or two colored dots of five different colors. These dots are based on the TCF, A-Time/Bufs/Reads/Write Self Graph columns in the execution plan and let you quickly spot possible problematic row source nodes.

Which of the colored dots is shown can be set by the buttons in the toolbar.

You can quickly see the details for an object referenced in a row source by right clicking on the node (see screenshot below)

On the toolbar are additional buttons for rotating the tree and for a condensed view which helps with large trees and looks like this:

Hope you like it and that it helps in your performance analysis quests.

have you created a user only or have you created the complete Mumbai42 schema from within the Mumbai42 interface? There is a button “Create Schema” on the Connection tab in the main window. This will ask for sys user’s password, connect as sys, create the user/schema Mumbai42 and all necessary schema objects and disconnect. After that the extended functionality, like alert.log retrieval should be available.