Oracle Pools Used to Store the Actual Data in Memory
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 MoreMost Popular Performance Tuning
Oracle Waits and Latches Related to Initialization Parameters
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 MoreBest Settings for Oracle Library Cache Reload and Library Cache Hit Ratios
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 MoreBest Settings for Oracle Data Dictionary Cache Hit Ratio
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 MoreOptimal Use of the Shared SQL Area in Oracle
To ensure optimal use of the shared SQL area in Oracle, use stored procedures as much as possible. Learn more.
Read MoreBest Setting for Oracle DB_BLOCK_SIZE
The Oracle DB_BLOCK_SIZE is the default data block size when the database is created. A separate cache memory allocation must be made for each different database block size, and choose wisely.
Read MoreAvoid Chaining in Oracle by Setting PCTFREE Correctly
Row chaining can occur in Oracle when there isn’t enough room in the data blocks to store a single row or the most recent changes to a row, and can impact performance.
Read MoreImpact of Clustering Factor on SQL Statements in Oracle 11g
The clustering factor In Oracle 11g is a measure of the ordered-ness of an index in comparison to the table that it is based on, and can impact database performance.
Read MoreAbout Oracle 11gR2 Automatic SQL Tuning
Oracle 11g runs the SQL Tuning Advisor against SQL statements determined to be of high impact based on statistics from the Automatic Workload Repository (AWR).
Read MoreUnderstanding Oracle Write Complete Waits
If a session spends a lot of time waiting on the Oracle write complete waits event, it is usually due to a slow I/O subsystem, the MTTR is too short or the DBWR write batch size is too large.
Read MoreUnderstanding Oracle Free Buffer Wait Events
Oracle free buffer waits are caused by inefficient SQL statements, not enough DBWR processes, slow I/O subsystems, delayed block cleanouts and/or small buffer caches.
Read MoreUnderstanding Oracle Log Buffer Space Wait Events
The Oracle log buffer space wait event can indicate that the log buffer in the SGA is too small or the LGWR process is too slow.
Read More