Skip Headers
Oracle® In-Memory Database Cache Introduction
Release 11.2.1

Part Number E14261-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

What's New

This section summarizes the new features of Oracle TimesTen In-Memory Database release 11.2.1 that are described in this guide. It provides links to more information.

New features in Release 11.2.1.8.0

ODP.NET support for Oracle TimesTen In-Memory Database (TimesTen) provides ADO.NET data access from .NET client applications to TimesTen databases. See "ODP.NET support".

New features in Release 11.2.1.7.0

You can create explicitly loaded global cache groups. See "Global and local cache groups".

New features in Release 11.2.1.1.0

This section lists new features for Release 11.2.1.1.0 that are described in this guide.

PL/SQL support

TimesTen supports PL/SQL. See "SQL and PL/SQL functionality".

OCI and Pro*C support

TimesTen supports OCI and Pro*C. See "OCI and Pro*C/C++ Precompiler support".

Cache grid

A cache grid consists of one or more grid members each backed by an Oracle In-Memory Database Cache (IMDB Cache). Grid members cache tables from a central Oracle database or Real Application Cluster (Oracle RAC). See "Cache grid".

Dynamic cache groups

In a dynamic cache group, new data is loaded into IMDB Cache tables on demand or manually. See "Dynamic cache groups and explicitly loaded cache groups".

Oracle Clusterware

You can use Oracle Clusterware to manage recovery of a TimesTen active standby pair. See "Replication failover and recovery".

Bitmap indexes

TimesTen supports bitmap indexes. See "Indexes".

Automatic client failover

You can configure automatic client failover for databases that have active standby pairs with client/server connections. See "Replication failover and recovery".

Asynchronous materialized views

You can create a materialized view whose maintenance is deferred until after a transaction has been committed on the detail tables. See "Materialized views and XLA".