What's New

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

New features in Release 11.2.1.6.0

If your application has predictable transactional dependencies and does not require the commit order on the target data store be the same as the order on the source data store, then you can increase replication throughput by configuring parallel replication. See "Increasing replication throughput for other replication schemes".

New features in Release 11.2.1.5.0

Add or remove spare hosts using the following ttCWAdmin options: -addMasterHosts, -delMasterHosts, -addSubscriberHosts, -delMasterHosts. See "Adding a host to the cluster" and "Removing a host from the cluster".

New features in Release 11.2.1.4.0

This section summarizes new features in Release 11.2.1.4.0 that are documented in this guide.

• You can use the -switch and -relocate options of the ttCWAdmin utility to change the configuration of a cluster. See "Reversing the roles of the master data stores" and "Moving a data store to a different host".

• Use the -ocrConfig option of ttCWAdmin to register a TimesTen cluster with the Oracle Cluster Registry. See "Register the TimesTen cluster information".

• From a subscriber data store, you can verify that the subscriber has received all updates from the master data store. See "Verifying that a subscriber has received and applied all updates".

New features in Release 11.2.1.1.0

This section summarizes new features in Release 11.2.1.1.0 that are documented in this guide.

Oracle Clusterware integration

TimesTen integrates with Oracle Clusterware to manage failure recovery for active standby replication schemes. See Chapter 6, "Using Oracle Clusterware to Manage Active Standby Pairs" and Chapter 7, "TimesTen Configuration Attributes for Oracle Clusterware".

Replicating tables with different definitions

You can replicate tables that have columns in different positions or tables that have a different number of partitions. See "Replicating tables with different definitions".

Increased column size

VARCHAR2, NVARCHAR2, VARBINARY and TT_VARCHAR columns in replicated tables can have a size of 4 megabytes. See "Table requirements and restrictions for replication schemes".

Increased throughput for active standby pairs

You can configure increased throughput for active standby pairs. See "Increasing replication throughput for active standby pairs".