What's New

This section summarizes new features and functionality of TimesTen Release 22.1 that are documented in this guide, providing links into the guide for more information.

New features in Release 22.1.1.18.0

• The checkAdminPrivileges.sql script checks that the cache administration user has been granted the required privileges to automatically create Oracle Database objects used to manage the caching of Oracle Database data when particular cache group operations are performed. This script checks that the privileges granted are those that are granted with the grantCacheAdminPrivileges.sql script.

  See The checkAdminPrivileges.sql Script.

New features in Release 22.1.1.17.0

• Previously, you could only provide cache administration user credentials by providing the cache administration user name and both of its passwords to the TimesTen and Oracle databases individually in a client DSN or using connection attributes. Now, you can specify cache administration user credentials within an Oracle Wallet where the wallet location is provided when opening a connection. The preferred method of specifying the cache administration user name and both passwords is by storing them in an Oracle Wallet.

  See Providing Cache Administration User Credentials.

• You must register the Oracle database cache administration user name and password internally in the TimesTen database before any cache group operation can be issued. Before you register the Oracle cache administration user and password internally within the TimesTen database, you must decide if you want to save these credentials in an Oracle Wallet (recommended) or within memory (the default). To save the credentials within an Oracle Wallet, ensure that the CacheAdminWallet connection attribute is set to 1 (likely in your DSN). This directs that the registration of the Oracle cache administration user name and password is stored in an Oracle Wallet.

  See Registering the Cache Administration User Name and Password.

New features in Release 22.1.1.1.0

• You can use cache operations in both TimesTen Classic and TimesTen Scaleout. TimesTen Scaleout supports static read-only cache groups with incremental autorefresh. See Using Cache Groups in TimesTen Scaleout.

• A hybrid cache group is a dynamic read-only cache group where the root table is created in the TimesTen database and does not exist in the Oracle database. See Hybrid Cache Group.

• You can set the TT_DynamicPassthrough optimizer hint to notify TimesTen Classic to pass through qualified SELECT statements to the Oracle database. See Automatic Passthrough of Dynamic Load to the Oracle Database.

• You can dynamically load multiple cache instances, see Dynamically Loading Multiple Cache Instances.

• You may prefer to use Oracle GoldenGate to refresh data from the backend Oracle database to a TimesTen cache instead of using the built-in native cache refresh mechanism of TimesTen. See Using Oracle GoldenGate as an Alternative Cache Refresh Mechanism.

• There are now two LRU aging policies for TimesTen Classic:

  • LRU aging based on set thresholds for the amount of permanent memory in use.

  • LRU aging based on row thresholds for a specified root tables of your cache groups.

  See LRU Aging in TimesTen Classic.

• As a result of changes in the Oracle Database, the privileges required for cache operations have been updated. See Required Privileges for Cache Administration User for Cache Operations.

• An additional table and trigger were added for cache operations. The TT_version_CACHED_COLUMNS table stores list of columns that are cached. And instead of a single trigger, there are now two triggers to handle different aspects of autorefresh operations. See Managing a Cache Environment with Oracle Database Objects.