Outer Web | Explore

Explore >> Select a destination

You are here		blog.jooq.org How to get Oracle execution plans with Starts, E-Rows, A-Rows and A-Time columns - Java, SQL and jOOQ.
\|	\|	tanelpoder.com Where does the Exadata storage() predicate come from? \| Tanel Poder Consulting	10.2 parsecs away Travel
\|	\|	On Exadata (or when setting cell_offload_plan_display = always on non-Exadata) you may see the storage() predicate in addition to the usual access() and filter() predicates in an execution plan: SQL> SELECT * FROM dual WHERE dummy = 'X'; D - X Check the plan: SQL> @x Display execution plan for last statement for this session from library cache... PLAN_TABLE_OUTPUT ------------------------------------------------------------------------------------------------------------------------ SQL_ID dtjs9v7q7zj1g, child number 0 ------------------------------------- SELECT * FROM dual WHERE dummy = 'X' Plan hash value: 272002086 ------------------------------------------------------------------------ \| Id \| Operation \| Name \| E-Rows \|E-Bytes\| Cost (%CPU)\| ------------...	10.2 parsecs away Travel
\|	\|	jonathanlewis.wordpress.com Plans in Memory \| Oracle Scratchpad	8.6 parsecs away Travel
\|	\|	In an earlier articleI described how dbms_xplan.display_cursor() could be used to query memory to find the execution plans (and row source statistics) of recently executed SQL. In 9i, you have to use your own SQL to get the equivalent results. If you do, you should avoid using the "traditional" hierarchical type of query that you...	8.6 parsecs away Travel
\|	\|	savvinov.com DBMS_XPLAN.DISPLAY_CURSOR - Oracle Diagnostician	9.4 parsecs away Travel
\|	\|	In this post, I continue on the topic of examining SQL plans. I will talk about one DBMS_XPLAN function, DISPLAY_CURSOR (because it's probably the most useful one when troubleshooting ongoing performance issues, and also because other functions have a lot of similiarity to it). I will discuss frequently used options and some common problems. Preparation...	9.4 parsecs away Travel
\|	\|	orastory.wordpress.com SQL_IDs and baselines \| OraStory	23.0 parsecs away Travel
\|		There have been some interesting posts from Marcin Przepiorowski and Kerry Osborne about mapping sql plan management (spm) baselines to a corresponding sql id. The key to sql plan baselines (DBA_SQL_PLAN_BASELINES) is SIGNATURE. And why signature? It's not just another change to the key to identifying sql statements (HASH_VALUE -> (NEW_)HASH_VALUE / OLD_HASH_VALUE -> SQL_ID)....	23.0 parsecs away Travel