Planning the Installation and its Deployment

This section is applicable for full installations and full instances. Client-only installations and instances are irrelevant. For planning purposes, consider the information in these sections:

Locations of Database Files and User Files

These are the TimesTen requirements and recommendations regarding locations of databases and other user files:

Storing database files (checkpoint and log files) or any other user files anywhere under the TimesTen installation path is not supported. The installation is immutable—do not add, change, or remove anything.
It is strongly advised to not store database files or other user files under the instance home. Anything in or under the instance home will be removed if the instance is destroyed.
For performance reasons, it is advisable to store TimesTen checkpoint files (the DataStore location in the database definition) on a different device from TimesTen transaction log files (the LogDir location).

Once you have a TimesTen installation, you can estimate the size of your database and the disk space required. Refer to Storage Provisioning for TimesTen in Oracle TimesTen In-Memory Database Operations Guide.

Locations of the Databases and the Applications

Consider:

Unless there are concerns about resource contention between your application and TimesTen Classic, it is best to have your application on the same host as the databases in TimesTen Classic. This allows the application to use direct connections, which offer much better response time and throughput than client/server connections, due primarily to avoidance of network round trips.
To use TimesTen Cache, it is best to have the TimesTen Classic and Oracle databases on different hosts, to avoid resource contention between them.

Note:

These are general guidelines only, not necessarily suitable for every particular situation.