1. Cache Guide
  2. Defining Cache Groups
  3. User Managed Cache Group

User Managed Cache Group

If the system managed cache groups (read-only, AWT, SWT) do not satisfy your application's requirements, you can create a user managed cache group that defines customized caching behavior.

Create a user managed cache group with customized caching behavior with one or more of the following cache table attributes:

Only TimesTen Classic supports user-managed cache groups.

Note:

When TimesTen manages operations for user managed cache groups, it connects to the Oracle database using the current user's credentials provided on the connection string. The current user's credentials can be provided with an Oracle Wallet pointed to by the PwdWallet connection attribute or with the UID, PWD, and OraclePwd connection attributes. TimesTen does not connect to the Oracle database with the Oracle cache administration user name and password registered with the ttCacheUidPwdSet built-in procedure when managing SWT cache group operations. See Providing Cache Administration User Credentials When Connecting and Registering the Cache Administration User Name and Password..

  • You can specify the READONLY Cache Table Attribute on individual cache tables in a user managed cache group to define read-only behavior where the data is refreshed on TimesTen from the Oracle database at the table level.

  • You can specify the PROPAGATE cache table attribute on individual cache tables in a user managed cache group to define synchronous writethrough behavior at the table level. The PROPAGATE Cache Table Attribute specifies that committed changes on the cache table are automatically and synchronously propagated to the cached Oracle Database table.

  • You can define a user managed cache group to automatically refresh and propagate committed changes between the Oracle and TimesTen databases by using the AUTOREFRESH cache group attribute and the PROPAGATE cache table attribute. Using both attributes enables bidirectional transmit, so that committed changes on the TimesTen cache tables or the cached Oracle Database tables are propagated or refreshed to each other.

    See Automatically Refreshing a Cache Group for more information about defining an autorefresh mode, interval, and state.

  • You can use the LOAD CACHE GROUP, REFRESH CACHE GROUP, and FLUSH CACHE GROUP statements to manually control the transmit of committed changes between the Oracle and TimesTen databases.

    See Manually Loading and Refreshing a Cache Group for more information about the LOAD CACHE GROUP and REFRESH CACHE GROUP statements. See Flushing a User Managed Cache Group for more information about the FLUSH CACHE GROUP statement.

  • You can cache Oracle Database materialized views in a user managed cache group that does not use either the PROPAGATE or AUTOREFRESH cache group attributes. The cache group must be manually loaded and flushed. You cannot cache Oracle Database views.

The following sections provide more information about user managed cache groups: