Incremental Autorefresh Not Progressing

If incremental autorefresh is not progressing, verify that:

Inspect the support log for the conditions described in the following table:

Table summary is in the first heading cell.

Condition	What to do
Oracle Database server connection errors or warnings	See Troubleshooting Client/Server Problems for information about resolving connection problems.
Lock timeout errors or warnings on TimesTen	This usually occurs because of an open DDL transaction on the cache group. Commit the DDL transaction so that autorefresh can get the necessary locks.
Insufficient permanent memory region errors on TimesTen	Increase `PermSize`.
Autorefresh Oracle Database object validations errors or warnings	See Recover and Reset Autorefresh for Oracle Database Objects for information.
Cache agent unexpected exit	Contact TimesTen Customer Support.
Core files in main daemon directory	Contact TimesTen Customer Support.
Warnings about incremental autorefresh becoming full refresh	See Incremental Autorefresh Becomes Full Autorefresh for information.
Warnings that autorefresh has not finished for a long time	The autorefresh transaction can take a long time if many transactions have occurred since the last autorefresh. Note: Cache groups with the same autorefresh interval are autorefreshed in one transaction.