New in Ignite 6.5

Top Plans and Top Objects

Confio Igniter Suite™ Version 6.5 includes two major new features for Confio Ignite™ for Oracle.

• Top Plans identifies the wait time associated with each Explain Plan for a specific SQL. This feature is available for Oracle 10g and higher monitored databases.
• Top Objects captures the wait time generated by database objects including indexes and tables. Top Objects is visible for Oracle 9i and higher monitored databases.

Top Plans

Ignite for Oracle 6.5 monitors the Explain Plans that Oracle uses to execute each monitored SQL statement. For Oracle 10g and higher monitored databases, a “Top Plans” dimension now appears in the Ignite tree showing a list of “plan hash” values (similar to a SQL hash). For example, expanding a SQL hash node and then expanding the Top Plans node will show the plans used to execute the SQL statement during the specified time interval.

Top Plan chart ranks wait time with wait events for each execution plan on a given SQL.

For a detailed analysis of each plan, Ignite identifies the objects and cost associated with each step, including sample predicates for each operation.

Top Plans details cost of each step of the Explain Plan

Top Objects

Ignite for Oracle 6.5 monitors the database objects (e.g. table, indexes, etc.) that are in-use as a monitored SQL statement executes. For Oracle 9i and higher monitored databases, a “Top Objects” dimension now appears in the Ignite tree showing a list of objects, each showing their schema owner, object type and, if applicable, the partition.

Top Objects Illustrates Historical Trends for Object Creating End User Waits

New in Ignite for Oracle 6.4

Identify Source of Blocking and Locking

Ignite for OracleVersion 6.4, now available for download, provides expanded detail into sources of blocking wait time due to lock contention. This feature enables the DBA to identify the database activity for sessions that are blocking other sessions. This will in turn enable the DBA to get to the root cause of time wasted waiting for locks to be released. By improving the performance of blocking sessions, end user wait time wasted by lock contention will be correspondingly reduced.

For the locking family of wait events, most notably Enqueue, a new level of expanded detail is available in Ignite. By expanding a locking wait event in the client, Ignite shows performance information for active blocking sessions. Ignite will also list the blocking sessions that are idle during a period of lock contention.

Example 1:  Expanded Locking Detail

Enqueue Wait Events are now expanded to show Blocking Sessions, total blocking Wait Time, and Blocked Users, Programs and more. 

Example 2:  Is Blocking a Serious Problem? 

Ignite for Oracle 6.4 now specifically identifies the SQL statements causing blocking and the amount of Wait Time they impose across the system. Is this blocking a problem for your database?   Wait Time impact will help you be the judge.

Example 3:  Who Are My Offending Blockers? 

Ignite now identifies the specific sessions blocking other sessions, and the total Wait Time they are creating for others users.  Now you can determine the interdependency between sessions and identify the “offenders”. 

To try these for yourself, download Ignite for Oracle now.