Autorefresh Not Refreshing Cache at Specified Interval

The following table shows possible causes for autorefresh problems.

Possible cause	What to do
Cache agent is not started with a cache administration user.	Specify a cache administration user ID and password when starting the cache agent, as shown in Starting the Cache Agent in the Oracle TimesTen In-Memory Database Cache Guide. Also see ttCacheStart in Oracle TimesTen In-Memory Database Reference and Registering the Cache Administration User Name and Password in Oracle TimesTen In-Memory Database Cache Guide.
Object ID of the base table has changed.	See Recover and Reset Autorefresh for Oracle Database Objects for information.
Autorefresh trigger not enabled.	See Recover and Reset Autorefresh for Oracle Database Objects for information.
Current log sequence number recorded in the TT_version_USER_COUNT table is less than to the maximum log sequence number in the autorefresh log table.	See Recover and Reset Autorefresh for Oracle Database Objects for information.
There is no row in the TT_version_USER_COUNT table with usercount > 0 for every active incremental autorefresh table.	See Recover and Reset Autorefresh for Oracle Database Objects.
Change log table is empty.	See Recover and Reset Autorefresh for Oracle Database Objects.
User count is less than 0 or any TT_version_USER_COUNT log sequence anomalies.	See Recover and Reset Autorefresh for Oracle Database Objects.
Autorefresh log table, trigger, or sequence associated with a cached table does not exist or is not valid.	Check whether the cache agent was started with the correct cache administration user ID. If the cache administration user ID is correct, follow the procedure described in Recover and Reset Autorefresh for Oracle Database Objects. Check the user error log for messages about "fatal anomalies". This indicates corrupt or missing Oracle database objects.
TT_version_USER_COUNT table is missing.	Check whether the cache agent was started with the correct cache administration user ID. If the cache administration user ID is correct, follow the procedure in Recover and Reset Autorefresh for Oracle Database Objects. Check the user error log for messages about "fatal anomalies". This indicates corrupt or missing Oracle database objects.
Current log sequence number in the TT_version_USER_COUNT table changes and is different from the bookmark, and the associated cached table is not refreshed by the next committed autorefresh.	Restart the cache agent. If that does not work, follow the procedure in Recover and Reset Autorefresh for Oracle Database Objects.
If autorefresh occurs at the same time you alter the autorefresh mode, state, or interval, you may potentially cause a lock timeout as both actions modify the same table.	Stop the cache agent before altering the autorefresh mode, state, or interval. See Avoid a Lock Timeout Condition When Modifying Autorefresh.
There is a resource problem.	Restart the cache agent.