This section summarizes new features and functionality of TimesTen Release 18.1 that are documented in this guide, providing links into the guide for more information.
You can now set a time interval for how often to perform the calculation of the fragmentation percentage of the change log tables on the Oracle database. Use the ttCacheConfig built-in procedure providing the AutorefreshLogMonitorInterval as the value parameter. See "Defragmenting change log tables in the tablespace" for details.
Cache group autorefresh interval set to 0 milleseconds enables continuous autorefresh, where the next autorefresh cycle is scheduled immediately after the last autorefresh cycle has ended. See "AUTOREFRESH cache group attribute overview" and "Minimizing delay for cached data with continuous autorefresh" for details.
Applications can have multiple dynamic load requests to the Oracle database, which could result in too many open connections to the back-end Oracle database. However, for client/server applications with multiple connections per server, you can configure TimesTen to use the cache connection pool for all connections to the Oracle database. The cache connection pool can only be utilized by an application using a client/server connection as the pooled connections are shared across all client/server connections. See "Managing a cache connection pool to the Oracle database for dynamic load requests" for details.
If you notice that your application is timing out because of a lock contention between autorefresh and dynamic load requests, you can set the CacheCommitDurable cache configuration parameter to 0 with the ttCacheConfig built-in procedure. This reduces the occurrence of lock contention between autorefresh and dynamic load requests in the same application. See "Reducing lock contention for read-only cache groups that use autorefresh and dynamic load" for details.
You can reduce contention between autorefresh and dynamic load operations for dynamic read-only cache groups with incremental autorefresh by enabling the DynamicLoadReduceContention database system parameter. See "Reducing contention on TimesTen for dynamic read-only cache groups with incremental autorefresh" for details.
Some applications choose incremental autorefresh instead of full autorefresh mode for performance reasons. However, a full autorefresh could still be requested in some situations. You can set the DisableFullAutorefresh cache configuration parameter to 1 to disallow any full autorefresh requests for all cache groups defined with incremental autorefresh. See "Disabling full autorefresh for cache groups" for details.
Oracle TimesTen In-Memory Database in classic mode or TimesTen Classic refers to single-instance environments and databases as in previous releases. TimesTen Cache is available with TimesTen Classic.
TimesTen Cache is supported on multiple platforms. See "Platforms and configurations" in Oracle TimesTen In-Memory Database Release Notes (README.html) in your installation directory for specific platform versions supported by TimesTen.
TimesTen Cache works with asynchronous Oracle Active Data Guard. You can cache tables from an Oracle Active Data Guard with the asynchronous redo transport mode into read-only cache groups. The read-only cache groups are replicated within an active standby pair replication scheme. The Active Data Guard configuration includes a primary Oracle database that communicates over an asynchronous transport to a single physical standby Oracle database. See "TimesTen Cache works with asynchronous Active Data Guard" for full details.
Cache grid and all its components are removed in this release.
Cache Advisor is removed from TimesTen in this release.