Aging and Replication

There are rules that apply to the interaction with replication when a table or cache group is configured with least recently used (LRU) or time-based aging.

• The aging configuration on replicated tables and cache groups must be identical on every peer database.

• If the replication scheme is an active standby pair, then aging is performed only on the active database. Deletes that result from aging are then replicated to the standby database. The aging configuration must be set to ON on both the active and standby databases. TimesTen automatically determines which database is actually performing the aging based on its current role as active or standby.

• In a replication scheme that is not an active standby pair, aging is performed individually in each database. Deletes performed by aging are not replicated to other databases.

• When an asynchronous writethrough cache group is in a database that is replicated by an active standby pair, delete operations that result from aging are not propagated to the Oracle database.