Using Oracle GoldenGate as an Alternative Cache Refresh Mechanism

You may prefer to use Oracle GoldenGate to refresh data from the backend Oracle database to TimesTen instead of using the built-in native cache refresh mechanism of TimesTen.

You can use GoldenGate instead of the native cache refresh mechanism of TimesTen to provide the equivalent of static read-only cache groups. All other types of cache functionality must use the TimesTen native cache mechanism.

The following are the advantages when using GoldenGate as your cache refresh mechanism:

  • GoldenGate provides a lighter weight change data capture pipeline on the Oracle database, especially if you have multiple TimesTen databases caching data from the same Oracle database.

  • The triggers and tracking tables that are required by TimesTen for cache operations in an Oracle Database are not required.

  • You can cache data from multiple Oracle databases into a single TimesTen database.

  • You can cache data from a backend database that is not an Oracle database if the database supported by GoldenGate.

See Using GoldenGate as an Alternative to Native Read-Only Cache Groups.