4 Monitoring and Troubleshooting TimesTen Cache

The following sections in this chapter describe how to monitor and troubleshoot problems you may encounter when using TimesTen Cache:

• Monitoring Cache Groups with Autorefresh

• Unable to Create a Cache Group

• Unable to Start or Stop Cache Agent

• Unable to Resolve Oracle Service Name

• Unable to Resolve Connect Identifier

• Incompatible Oracle Database Server and Client Versions

• Unable to Validate Oracle Database User Name and Password

• OCI Initialization Failed

• Unsupported Data Type Mapping

• Null Constraint Does Not Match Oracle Database

• DDL on Cached Oracle Database Tables May Cause Failure

• Changes Not Visible After Updating Object in Cache Group

• Load or Refresh Fails

• Optimize Performance for TimesTen Cache

• Check Large Batch Jobs on Oracle Database Tables

• Autorefresh Not Refreshing Cache at Specified Interval

• Incremental Autorefresh Not Progressing

• Incremental Autorefresh Becomes Full Autorefresh

• Poor Autorefresh Performance

• Declaring NOVALIDATE on Constraints Causes Cache Group Failure

• AWR Report Shows Lock Contention with DBMS_LOCK

If you are having problems with an AWT cache group, see Troubleshooting AWT Cache Groups for information.

Note:

Error log messages from the cache agent are designated by CAC in the message, as shown in several examples in this chapter. These messages are enabled unless you disable the CACHE component of the ttDaemonLog utility. See ttDaemonLog in Oracle TimesTen In-Memory Database Reference for information about ttDaemonLog options for Windows and Linux or UNIX systems.