Explore >> Select a destination
|
You are here 
|
jonathanlewis.wordpress.com | ||
| | | | |
tanelpoder.com
|
|
| | | | | 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)| ------------... | |
| | | | |
hourim.wordpress.com
|
|
| | | | | The last Jonathan Lewis post on RAC Planswhich finished by the following phrases: "If you're going to hard-code hints into a query then take a look at the outline it generates when it does the right thing, and that will tell you about the 15 or so hints you've missed out. (Better still, consider generating... | |
| | | | |
tonyhasler.wordpress.com
|
|
| | | | | When a table is accessed by multiple members of a parallel query server set, the execution plan may show the use of block range granules (PX BLOCK ITERATOR) or partition granules (PX PARTITION [RANGE|LIST|HASH] ITERATOR or PX PARTITION [RANGE|LIST|HASH] ALL). The basic ideas surrounding these concepts are discussed in numerous blogs and books, including my... | |
| | | | |
nenadnoveljic.com
|
|
| | | Oracle's heuristics previously avoided considering fixed tables for Join Predicate Pushdown (JPPD) transformation, leading to suboptimal plans. Enforcing predicate pushing into the view with the PUSH_PRED hint was a workaround. Oracle addressed this in the 21c release, evaluating fixed tables for JPPD. | ||
