-
Note: this is the continuation of the previous post. The natural question arises: how can I set a trap for any specific SQL_ID which causes issues. Update: near the end of this part3 I have also included some immediate solutions to mitigate the problem supported by two other posts. The goal is to intercept an…
All tags
- 10046 (1)
- 10046 event (1)
- 10046 trace (1)
- 10053 (1)
- 10053 event (1)
- 10053 trace (1)
- 10200 event (1)
- Active Session History (1)
- Analysis of costing of joins in 10053 (1)
- AUTOTRACE (1)
- AVG_DATA_BLOCKS_PER_KEY (1)
- AVG_LEAF_BLOCKS_PER_KEY (1)
- Batched I/O (1)
- buffer cache (1)
- cardinality (1)
- Cartesian Join (2)
- CBO (1)
- CBO 10053 trace (2)
- CBO costing (3)
- CLUF (4)
- Clustering Factor (4)
- Converting of CPU costing in 10053 (1)
- Cost Based Optimizer (1)
- CPU (1)
- CPU_COST in 10053 trace (1)
- Exadata (4)
- FC HBA utilization (1)
- FC host (1)
- Flash (1)
- Flash disk (1)
- FTS (1)
- Full Table Scan (1)
- Hash Join (2)
- HBA (1)
- I/O throughput (1)
- index leaf block dump (2)
- Index Range Scan (1)
- index tree dump (1)
- large SGA (1)
- Linux (1)
- LRU (1)
- Nested Loop (1)
- NSMTIO (3)
- Offload (4)
- optimizer (1)
- Oracle CBO (1)
- Oracle performance (1)
- Oracle Performance Tuning (1)
- Oracle SQL optimization (1)
- Oracle tuning (1)
- oradebug (2)
- Parallel Query (1)
- Performance Tuning (3)
- Resc (1)
- Resp (1)
- session_trace_enable (1)
- smart scan (3)
- Sort Merge Join (1)
- SQL Performance Tuning (1)
- SQL Plan (2)
- SQL Tuning (1)
- sql_id (1)
- system statistics (1)
- Temp tablespace (1)
Latest posts
- Converting of CPU Costing in the Cost Based Optimizer 10053 Trace File
- Why this extra physical read while performing index scan?
- Clustering Factor (CLUF) – the anatomy and its impact on performance – part4
- Clustering Factor (CLUF) – the anatomy and its impact on performance – part3
- Clustering Factor (CLUF) – the anatomy and its impact on performance – part2
- Clustering Factor (CLUF) – the anatomy and its impact on performance – part1
- Resp in the CBO 10053 Trace File
- Cartesian Join – the usual suspect (part2)
- Cartesian Join – the usual suspect (part1)
- Calculations of I/O cost in 10053 trace vs. SQL Plan