Monitoring Autorefresh Operations on Cache Groups

TimesTen offers several mechanisms to obtain information and statistics about autorefresh operations on cache groups.

See Monitoring Cache Groups with Autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.

This example explains how to check and interpret the statistics of log-based AUTOREFRESH cache groups in Oracle TimesTen by using the SYS.V$CACHE_GROUP_LOG_STATS view and the ttCacheLogStats() procedure.

Command> describe sys.v$cache_group_log_stats;
> View SYS.V$CACHE_GROUP_LOG_STATS:
> Columns:
> CACHE_GROUP_OWNER VARCHAR2 (30) INLINE
> CACHE_GROUP_NAME VARCHAR2 (30) INLINE
> NUMINSERTS TT_BIGINT
> NUMUPDATES TT_BIGINT
> NUMDELETES TT_BIGINT
> NUMNOOPS TT_BIGINT
> NUMLOADWAITS TT_BIGINT
> ELEMENTID TT_INTEGER NOT NULL

The same output is:

Command> call ttCacheLogStats();
< CACHEUSER, CG0, 1, 0, 0, 0, 0 >
< CACHEUSER, CG1, 2, 1, 2, 0, 0 >
2 rows found.

This output means:

For cache group CG0 owned by CACHEUSER:

• 1 insert operation was processed.
• 0 updates, deletes, no-ops, or load waits occurred.

For cache group CG1 owned by CACHEUSER:

• 2 inserts, 1 update, and 2 deletes were processed.
• No no-op events or load waits occurred.

Query output is:

select * from sys.v$cache_group_log_stats order by cache_group_name;
< CACHEUSER, CG0, 1, 0, 0, 0, 0, 1 >
< CACHEUSER, CG1, 2, 1, 2, 0, 0, 1 >
2 rows found.

This output shows the same information but includes the ELEMENTID (value 1 here for both groups), which uniquely identifies the element internally.