Loading and Unloading the Database from Memory
TimesTen is an in-memory database. As such, a database must first be loaded into memory from the file system to be available for connections.
When a database is loaded into memory, the contents of the permanent memory region are read from checkpoint files stored on the file system. The temporary memory region is created when a database is loaded into memory and is destroyed when it is unloaded. See Specifying the Memory Region Sizes of a Database for more details on permanent and temporary memory.
In TimesTen, RAM policies specify how and when a database is loaded into memory, including whether to automatically reload the database into memory if the database is unloaded unexpectedly. See Specifying a RAM Policy for full details on the different RAM policies.
By default, TimesTen automatically loads an idle database (which is a database with no connections) into memory when a first connection is made to it. See Loading a Database into Memory for TimesTen.
After a database loads into memory, you may need to explicitly start the
cache and replication agents for the database, depending on the functionality you are
using and on which cache and replication policies you set with the
ttAdmin utility.
Note:
Instead of loading and unloading the database, you can detach or attach the shared memory segment leaving the shared memory segment in memory. This is significantly faster than loading and unloading a database. See Detaching, Attaching, and Freeing the Shared Memory Segment.
Loading and unloading the database from memory for TimesTen is described in these sections: