Changes to the Oracle 11g Optimizer That Affect Tuning
Learn about some signiticant changes to the Oracle 11g optimzer that can affect SQL query tuning.
Read More
Learn about some signiticant changes to the Oracle 11g optimzer that can affect SQL query tuning.
Read More
While Oracle’s cost-based optimizer generally suppresses poor indexes, problems can still develop when a bad index is used at the same time as a good index. Learn why.
Read More
Choosing to use an index in Oracle depends on how the data and indexes are architected, how the data is distributed within the blocks, and how it is accessed.
Read More
The Oracle command AUTOTRACE executes the query (in the way TRACE does) and automatically queries the plan table, and the EXPLAIN PLAN command does neither. Learn more.
Read More
The EXPLAIN PLAN command allows you to view the query execution plan and can be helpful in improving the performance of SQL statements. Learn more.
Read More
See one expert’s list of the 25 most important Oracle initialization parameters, in order of importance.
Read More
The Oracle cost-based optimizer has two modes of operation: normal mode and tuning mode. Learn when to use these modes.
Read More
The initialization parameters DB_CACHE_SIZE, DB_KEEP_CACHE_SIZE, and DB_RECYCLE_CACHE_SIZE are the determining factors for memory used to store data in Oracle.
Read More
Setting Oracle initialization parameters incorrectly can result in performance issues that show up as general “waits” or “latch waits” in a STATSPACK report. Learn more.
Read More
For optimal performance, keep the Oracle library cache reload ratio at zero and the library cache hit ratio greater than 95 percent. Learn more.
Read More
The Oracle data dictionary cache is a key area to tune because the dictionary is accessed so frequently, but it should be monitored only after the system has been up for a while and stabilized.
Read More
To ensure optimal use of the shared SQL area in Oracle, use stored procedures as much as possible. Learn more.
Read More