/explore
|
You are here 
|
tonyhasler.wordpress.com | ||
| | | | |
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... |
|
| | | | | ||
| | | | |
orastory.wordpress.com
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).... |
|
| | | | | ||
| | | | |
jonathanlewis.wordpress.com
Following yesterday's note on SQL Profiles, someone asked how I detect that an opt_estimate hint had been used - with specific reference to the "index_scan" option. The reason for this particular choice is that other opt_estimate hints have a highly visible impact in the 10053 trace files, but this one doesn't. Here are a few... |
|
| | | | | ||
| | | | |
tanelpoder.com
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. |
|
| | | |||
