|
You are here |
savvinov.com | ||
| | | | |
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... | |
| | | | |
alexzeng.wordpress.com
|
|
| | | | | Outline is the oldest way to fix SQL plan. It based on hints like use_nl etc. It's a road map. It still can be used in 11.2 although oracle said it's deprecated. Finally, it is free. SQL profile is trying to impact CBO by adding cost estimation hints. You need pay extra money to use... | |
| | | | |
dincosman.com
|
|
| | | | | The performance issue with an SQL query was resolved by using the /*+ PARALLEL(2) */ hint, reducing execution time from 180-200 seconds to milliseconds. The decision to perform a direct read from disk to memory instead of reading blocks from disk was made by the database engine and is controlled by the hidden "_serial_direct_read" parameter.... | |
| | | | |
blog.tanelpoder.com
|
|
| | | Hello all fellow Oracle geeks and technology enthusiasts! Long time no see ;-) In the hacking session about Oracle full table scans and direct path reads I explained how the direct path read decision is not done by the optimizer, but instead during every execution, separately for every single segment (partition) scanned in the query. I also explained how the _small_table_thresholdparameter and theX$KCBOQH.NUM_BUF(which keeps track of how many buffers of any segment are currently cached) are used for determining whether to scan using direct path reads or not. - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | ||