Explore >> Select a destination
|
You are here 
|
kerryosborne.oracle-guy.com | ||
| | | | |
tonyhasler.wordpress.com
|
|
| | | | | Note that there is a follow up to this post here that you should read after this post. Stored outlines were introduced in Oracle 9i as a way of helping stabilise execution plans. In 11gR1 these are deprecated in favour of enterprise-edition-only SQL Baselines (sorry standard edition users )-:) but as of 11gR2 neither facility... | |
| | | | |
savvinov.com
|
|
| | | | | Occasionally I encounter a situation when I need to affect a part of the plan that corresponds to a view, e.g.: Such situations are resolved using global hints. Oracle offers two ways to specify a global hint: via a query block identifier (system generated or user defined) or via view aliases. System-generated query block identifiers... | |
| | | | |
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... | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | [More on dbms_xplan.display_cursor()] If you're using 9i and haven't learned about the dbms_xplan package, then you should take a good look atit right away. It's(usually) a much better wayof getting execution plans from your system thanwriting yourown queries against the plan_table. If you'vebeen using dbms_xplan, and upgraded from 9i to 10g, make sure that you... | ||
