Aging Feature

In TimesTen Classic, records can be automatically aged out of a TimesTen database, and cache instances can be automatically aged out of a TimesTen database. Aging can be usage-based or time-based.

You can configure both usage-based and time-based aging in the same system, but you can define only one type of aging on a specific cache group.

Dynamic load can be used to reload a requested cache instance that has been deleted by aging.

For more information about aging in cache groups, see Implementing Aging in a Cache Group in TimesTen Classic in Oracle TimesTen In-Memory Database Cache Guide. For information about aging in tables that are not in cache groups, see Implementing Aging Policy in Your Tables in Oracle TimesTen In-Memory Database Operations Guide.