What's New

This section summarizes the new features and functionality of Oracle TimesTen In-Memory Database Release 18.1 that are documented in this guide, providing links into the guide for more information.

New features in release 18.1.4.1.0

  • In TimesTen Classic, automatic client failover is no longer limited to scenarios that include an active standby pair replication scheme. The client can automatically fail over from one database to another using generic automatic client failover. This is especially useful if you are using a read-only cache groups. See "Using automatic client failover" for more details.

New features in release 18.1.3.1.0

  • When critical events (such as invalidations) occur, TimesTen collects the daemon log entries at the moment of the critical event to help when diagnosing critical failures. See "Critical event logging" for details.

  • You open and close a database in order to direct whether users may connect to that database. For an application to be able to connect to a database, the database needs to be open to accept user connections. See "Opening and closing the database for user connections" for details.

  • Open source languages interact with TimesTen through the Oracle Database Programming Interface for C (ODPI-C). The languages currently supported are Python and Node.js. See "Connecting to TimesTen with ODBC and JDBC drivers" for more information.

  • You can now control how long a SQL statement executes before timing out in either seconds or milliseconds with SQLQueryTimeout or SQLQueryTimeoutMSec. See "Choose SQL and PL/SQL timeout values" for details.

New features in release 18.1.2.1.0

  • You can gracefully shut down the database by disconnecting applications in an orderly fashion. The new forced disconnect option asynchronously disconnects all connected applications from the database, including those that are idle or unresponsive. See "Disconnecting from a database" for full details.

  • The ttCkptHistory built-in procedure was updated to add information about the number of actual transaction log files purged by this checkpoint and the reason for a transaction log hold. See "Displaying checkpoint history and status" for full details.

New features in release 18.1.1.1.0

  • There are now two modes for Oracle TimesTen In-Memory Database.

    Oracle TimesTen In-Memory Database in grid mode (TimesTen Scaleout) is a grid of interconnected hosts running TimesTen Scaleout instances that work together to provide fast access, fault tolerance, and high availability for in-memory data. A grid contains one or more databases and each database is distributed across all instances of the grid. TimesTen Scaleout delivers these features by distributing the data for each in-memory database in the grid across multiple hosts. See the Oracle TimesTen In-Memory Database Scaleout User's Guide for full details.

    Oracle TimesTen In-Memory Database in classic mode or TimesTen Classic refers to single-instance environments and databases and referred to as TimesTen alone in previous releases.

    Now, when the documentation refers to TimesTen alone (without TimesTen Classic or TimesTen Scaleout), the statement applies to both single-instance and multiple-instance, such as in references to TimesTen utilities, releases, distributions, installations, actions taken by the database, and functionality within the database.

  • TimesTen Scaleout is only supported on the Linux platform, while TimesTen Classic is supported on multiple platforms. See the Oracle TimesTen In-Memory Database Release Notes (README.html) in your installation directory for specific platform versions supported by TimesTen.

  • You can use the -directload option of the ttBulkCp utility to perform faster copies from large ASCII files to a TimesTen table. For more information see "Copying data from an ASCII file into a TimesTen table".