Explore >> Select a destination
|
You are here 
|
www.dbaglobe.com | ||
| | | | |
kerryosborne.oracle-guy.com
|
|
| | | | | ||
| | | | |
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
|
|
| | | | | Here's a simple detail about bind peeking (during optimisation) that makes a big difference to "fetch first/next" queries. The optimizer knows about your bind types, and can peek at the bind values - but that doesn't mean it will do something sensible with them. Here's a little model to demonstrate the problem - starting with... | |
| | | | |
chandlerdba.com
|
|
| | | Photo by Brian Patrick Tagalog on Unsplash July 2024. Oracle 19c, 23ai There are 3 main types of SQL Plan Management: SQL Profile SQL Plan Baseline SQL Patch So first some quick background info about the 3 options and then I'll tell you about my mistake. SQL Profile A SQL Profile is a collections of... | ||
