|
|
|
![]() |
|
|
|
|
|
Tip of the Week
(Archived) Several weeks ago I did a tip on use of the PGA_AGGREGATE_TARGET, The PGA_AGGREGATE_TARGET or Memory Management Made Easy(ier) (pdf). Oracle has also provided new ways of evaluating the effectiveness of the shared pool and the data cache with two new "advice" tables. This week let's look at the data cache. The "advice" table providing information on the data cache is v$db_cache_advice. Below is a query of that table and the results from one of the databases I am managing. SELECT name,
size_for_estimate, size_factor, estd_physical_reads Note: The initialization parameter statistics_level must be set to either TYPICAL or ALL, and db_cache_advice set to ON for this information to be available. This information is based on statistics collected during database operation. The columns contain the following information:
Oracle provides estimates for cache sizes from 10% to 200% of the current cache size, tracking up to 20 different estimated values. Use the ESTD_PHYSICAL_READS column to determine if a change would benefit the database. In this case, the value for the current cache size is 775,526. Based on these estimates, increasing the cache will result in fewer physical reads, with a significant improvement occurring at 448MB. After first ensuring that the SGA_MAX_SIZE is set high enough to allow the change, I would recommend making that change, with the following command: ALTER SYSTEM SET db_cache_size=448M SCOPE=BOTH; After allowing the database workload to adjust to the new cache, the above query can be rerun to determine the effectiveness of the change and if any other adjustments are necessary. Note: This tip was tested on Oracle9i. Was this tip useful? Did you find any errors? Do you have any suggestions? Do you care? Click here for the tip feedback page. Thank you. |
|
|
|
|