From the Oracle doco...
"v$rowcache: This view displays statistics for data dictionary activity.
Each row contains statistics for one data dictionary cache. "
This view shows the information which can be used to calculate the hit ratios for each area of the data dictionary cache.
Here are some links to various doco on both dictionary cache and utlbstat/utlestat
Rule of thumb bad hit ratios may be a symtom of either a
1) too small shared pool
2) frequently used stored procedure not pinned.
3) Too much parsing i.e lack of bind variables.
I would suggest u gather Aggregates instead of individual parameters from V$ROWCACHE.
SELECT SUM (GETS-GETMISSES)/SUM (GETS) * 100 AS HIT RATIO FROM V$ROWCACHE;
Hit ratio for dictionary cache should be 85% or higher.If its low, you need to address the problem. I suggest tuning the Library Cache first.
(PS: You should collect data only after your database has been running for quite sometime).
I dont think you need to run UTLBSTAT to gather data from V$ROWCACHE view. Utilities like UTLBSTAT (followed by UTLESTAT) collect data from these dynamic performance views.
Bookmarks