/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 blog.tanelpoder.com
Optimizer statistics-driven direct path read decision for full table scans (_direct_read_decision_statistics_driven) | Tanel Poder Blog
| | afatkulin.blogspot.com
Alex Fatkulin's Blog: 11G adaptive direct path reads - what is the cached/dirty blocks threshold?
1.3 parsecs away

Travel
| | 11G's ability to do direct path reads during full table scans without utilizing PQ was covered in a number of places already (see this post ...
| | tanelpoder.com
Manual "before" and "after" snapshot support in Snapper v4 | Tanel Poder Blog
1.0 parsecs away

Travel
| | Snapper used to require access to DBMS_LOCK, so it could sleep for X seconds between the "before" and "after" performance data snapshots. Now it is possible to get away without using DBMS_LOCK. Instead you will run Snapper twice, once for taking the "before" snapshot, then run your workload and then run Snapper again for taking the "after" snapshot and print the output. So, the usual way of running snapper is this: - Linux, Oracle, SQL performance tuning and troubleshooting training & writing.
| | tanelpoder.com
Advanced Oracle SQL Tuning Training | Tanel Poder Blog
1.6 parsecs away

Travel
| | Training overview This training session is entirely about making Oracle SQL execution run faster and more efficiently, understanding the root causes of SQL performance problems and Cost Based Optimizer misbehavior. Instead of looking into increasing system utilization (by using more buffer cache or more parallelism) as a first "tuning" choice, this class is mostly about decreasing resource usage of SQL execution plans by improving their shape and available access paths. - Linux, Oracle, SQL performance tuning and troubleshooting training & writing.
| | dioncho.wordpress.com
v$sql_shared_cursor | Dion Cho - Oracle Performance Storyteller
25.0 parsecs away

Travel
| I hit following OTN forum article which was a discussion on typical SQL sharing problem. There are so many reasons why Oracle does not share the same statement. Oracle records the reason in v$sql_shared_cursor view. In my local 10.2.0.1 database, v$sql_shared_cursor has 53 reasons of unshareability. But I have a big complaint on v$sql_shared_cursor view....