|
You are here |
blog.toadworld.com | ||
| | | | |
oracleprof.blogspot.com
|
|
| | | | | SQL_ID and/or PLAN_HASH_VALUE are used almost globally across Oracle database to identify query. This is not a case for SPM mechanism using... | |
| | | | |
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).... | |
| | | | |
kerryosborne.oracle-guy.com
|
|
| | | | | ||
| | | | |
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.... | ||