1. Operations Guide
  2. What's New

What's New

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

New features in Release 22.1.1.17.0

  • Previously, you could only provide credentials when opening a connection to the TimesTen database by providing the user name and password individually in a client DSN or using connection attributes. Now, you can provide user credentials within an Oracle Wallet where the wallet location is provided when opening a connection. The preferred method is storing credentials in an Oracle Wallet.

    See Providing User Credentials When Connecting.

New features in Release 22.1.1.3.0

  • If an application process wants to use both direct and client/server TimesTen drivers, then it should link with an ODBC driver manager. In this release, a TimesTen-specific driver manager is provided. The TimesTen driver manager is a transparent, low overhead option designed specifically for this use case and supports all TimesTen functionality. See Connecting Using an ODBC Driver Manager.

New features in Release 22.1.1.1.0

  • Executing a SELECT statement returns a result set (if there is one). The client driver stores a maximum number of rows from the result set that fits into a result set buffer. You can improve performance by adjusting the maximum size of the result set buffer or the maximum number of rows that can be stored into a result set buffer. See "Sizing the Client Result Set Buffer" for details.

  • There are now two LRU aging policies for TimesTen Classic:

    • LRU aging based on set thresholds for the amount of permanent memory in use.

    • LRU aging based on row thresholds for a specified root tables of your cache groups.

    See "Usage-Based Aging" and "Defining LRU Aging Based on Row Thresholds for Tables" for details.

  • The ttPageLevelTableInfo built-in procedure shows the page allocation for each table to determine when TimesTen is reusing empty slots and freeing empty pages or if new pages are allocated to store new rows. See "Determining the Effectiveness of Aging" for details.

  • There is a new RAM policy of enduring. In addition to being able to manually load and unload data from the database (the same as the manual RAM policy), you can also attach, detach, and free the shared memory segment. When you detach, theshared memory segment still exists and can be reused when you attach to it. See "Specifying a RAM Policy" and "Detaching, Attaching, and Freeing the Shared Memory Segment" for details.

  • For TimesTen Classic, the root user can set up systemd to use for automatic management (including starting and stopping) of the TimesTen daemon. See "Automatically Starting the TimesTen Daemon" and "Using systemd to Automatically Manage the TimesTen Daemon" for details.