This document provides late-breaking information for TimesTen, as well as information that is not yet part of the formal documentation.

The latest version of this document is the README.html file in your installation directory. Release notes also are updated in the documentation library.

You can find the Oracle TimesTen In-Memory Database documentation set on the TimesTen documentation website.

To install Oracle TimesTen In-Memory Database, unzip the distribution file. See Overview of the Installation Process in TimesTen Classic in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide or Prerequisites and Installation of TimesTen Scaleout in Oracle TimesTen In-Memory Database Scaleout User's Guide.


TimesTen release numbers are reflected in items such as TimesTen utility output, file names, and directory names. These are subject to change with every minor or patch release, and the documentation cannot always be up to date. The documentation seeks primarily to show the basic form of output, file names, directory names, and so on. You can confirm the current release number by executing the ttVersion utility.

TimesTen XE

Oracle TimesTen In-Memory Database Express Edition (TimesTen XE) is a free version of TimesTen. The latest release of TimesTen XE is TimesTen XE includes all features and bug fixes available in TimesTen, but is subject to the restrictions listed in Oracle TimesTen In-Memory Database Quick Start Guide for Express Edition.

This document contains the following topics:

Changes for Release From Release

  • This release is an unrestricted version of TimesTen and includes all features and bug fixes available in release

Changes for Release From Release

New Features

Bug Fixes

  • A problem is fixed where XLA applications were able to read two-safe transactions before other database connections. (BugDB # 34761059)

    To enable this fix, set the value of the XlaReaderWaitTxnVisible parameter to 1:

    CALL ttDBConfig('XlaReaderWaitTxnVisible','1');
  • This release improves the handling of replicated VARCHAR2 out-of-line data in the receiving replication agent. (BugDB #34773132)

Changes for Release From Release

  • The ttSchema utility now selects only objects within the current schema by default when a user without ADMIN privilege runs the utility. This change avoids access errors when the user tries to describe objects without the appropriate privileges. The user can still attempt to describe objects by including a different selection pattern argument. The pattern % will revert to the previous behavior, but using patterns that include objects in other schemas may result in access errors. (BugDB #34223037)

  • In previous releases, when a classic replication scheme included multiple masters, the replication agent while trying to apply transactions from different databases could run into improperly handled deadlocks. The replication operation would hang as a result. This issue is fixed. (BugDB #34592144 - Forward port of BugDB #34577070)

  • A problem is fixed where a CREATE CACHE GROUP statement would lock some Oracle objects to create the metadata objects even if the objects already existed. (BugDB #34644529 - Forward port of BugDB #34641177)

  • In previous releases, the TimesTen Kubernetes Operator used the Leader-for-life method to determine which operator would manage TimesTen. In this release, the Operator uses the Leader-with-lease method. (BugDB #34650236)

  • A problem is fixed with the ZooKeeper client for TimesTen Scaleout where frequent DNS calls to resolve hostnames could overload DNS servers with requests. (BugDB #34716434)

  • A problem is fixed where creating a view from a synonym was not working properly. (BugDB #34741197)

  • A problem is fixed where unnecessary permision checks on connects could sometimes result in spurious errors: User username does not have group permision to connect to the database. (BugDB #34747548)

  • A problem is fixed with excessive and misleading daemon log messages relating to aging. (BugDB #34777457)

  • A problem with memory allocation for insert or update operations is fixed. (BugDB #34779479 - Forward port of BugDB #34676797)

Changes for Release From Release

  • The logic to handle transactions not tracked by XLA bookmarks is improved. (BugDB #34352710 - Forward port of BugDB #33968191)

  • This release no longer returns an error when the cipher suite specified for encrypted client/server connections is supported by the Oracle libraries but is not one of the two suites supported by TimesTen, SSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and SSL_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384. (BugDB #34353105)

  • A problem is fixed with parallel index creation on compiled commands. (BugDB #34570931)

  • When running Java 8 after Oracle JDK 8u301 (JDK-8153005), the creation of certificates failed with a "Could not derive key" error. This release updates the version of the cryptoj.jar file to fix the issue. (BugDB #34630389)

Changes for Release From Release

  • A problem is fixed where, under certain circumstances, updating the replication statistics caused an assertion failure. (BugDB #34224577 - Forward port of BugDB #31382397)

  • A problem is fixed where a Commit Ticket Number (CTN) wraparound could invalidate the database or cause a failed transmitter thread restart. (BugDB #34237513)

  • A problem with interval statistics on columns without range index was fixed. (BugDB #34285000)

Changes for Release From Release

  • In previous releases, a heap assertion due to not switching to system transaction for the permanent heap invalidated the database during the reclaim phase of recovery. The problem is fixed. (BugDB #33828964)

  • A problem is fixed where daemon log files would either not be rotated and a single file would grow beyond the maximum specified size or the files would stop being written. (BugDB #34032225)

  • This release adds new rows in the v$repstats view to track the read position in the transaction log of the transmitter thread for replication. (BugDB #34119463 - Forward port of BugDB #32989457)

  • A memory leak while using REF CURSOR variables for OCI, ProC, or ODPI based languages has been fixed. (BugDB #34131513 and BugDB #34190418)

Changes for Release From Release

  • This release is an unrestricted version of TimesTen and includes all features and bug fixes available in release

Changes for Release From Release

Changes in this release include:

New Features

  • This release is a TimesTen XE release. See Oracle TimesTen In-Memory Database Quick Start Guide for Express Edition.

  • This release supports the TimesTen driver manager (TTDM). TTDM is a lightweight ODBC driver manager that is designed and optimized for use with TimesTen databases. It provides access to TimesTen-specific features, extensions, and ODBC API support, offering 100% equivalent functionality to using the TimesTen direct driver or client driver directly. TTDM allows an application to use TimesTen direct and client connections concurrently. See Introduction to the TimesTen Driver Manager in Oracle TimesTen In-Memory Database C Developer's Guide.

  • This release contains updates to the TimesTen Kubernetes Operator. The Operator includes significant new functionalities, including:

    • The TimesTenScaleout object type, which enables the Operator to easily deploy grids from TimesTen Scaleout.

    • Support for the TimesTen Prometheus Exporter.

    • Simplified installation process. Only one container image is required both to run the Operator and to run TimesTen itself.

    • Ability to work with Oracle-supplied container images. Container images of TimesTen and all its prerequisites are available at https://container-registry.oracle.com. The Operator can directly be executed using these images.

    • Ability to change the user and group used to run TimesTen.

    These new functionalities resulted in a number of changes to the way that the Operator is packaged, and in the image formats that it supports.

    • By default, TimesTen and Operator now run as the timesten user.

    • The directory locations of various items are changed.

    The Operator can automatically upgrade TimesTen Classic databases associated with TimesTenClassic objects from one patch release of TimesTen to another. However, because of the changes described above, it is not possible to automatically upgrade a deployed active/standby pair of TimesTen Classic databases from a release previous to this one. Similarly, downgrades from this release to previous releases are not supported. TimesTen deployments created by the Operator in this release can be upgraded to subsequent TimesTen patch releases without issue.

    See Overview of the Oracle TimesTen Kubernetes Operator in Oracle TimesTen In-Memory Database Kubernetes Operator User's Guide.

Bug Fixes

  • Read-only cache groups and the ttLoadFromOracle built-in procedure can now work with NCHAR or NVARCHAR2 columns from an Oracle database when the national character set is UTF8. (BugDB #33541824)

  • A problem is fixed where the values for the activePermInUse and standbyPermInUse metrics were reported incorrectly. (BugDB #33652345)

  • The TTClasses library linked against TTDM, libttclassesTTDM.so, is now included and supported on all TimesTen server distributions. (BugDB #33668736)

  • A problem is fixed where, for certain SSL configurations, users of the TimesTen Kubernetes Operator were unable to configure SSL certificates issued by a certificate authority. (BugDB #33890625)

  • A problem is fixed where the ttRepAdmin -duplicate command and other replication operations failed when the hostname of the sender (or master) database is mapped multiple times in the /etc/hosts file. (BugDB #34013653 - Forward port of BugDB #31857874)

Changes for Release From Release

Changes in this release include:

New Features

  • TimesTen Scaleout now supports read-only cache groups with incremental autorefresh. See Using Cache Groups in TimesTen Scaleout in Oracle TimesTen In-Memory Database Scaleout User's Guide.

  • You can now create a grid with a K-safety level up to 5. See K-Safety in Oracle TimesTen In-Memory Database Scaleout User's Guide.

  • Global indexes now are supported in TimesTen Scaleout. See Understanding Indexes in Oracle TimesTen In-Memory Database Scaleout User's Guide.

  • PLSQL packages, procedures and functions are now supported in TimesTen Scaleout. See Overview of PL/SQL in Oracle TimesTen In-Memory Database Scaleout User's Guide.

  • You can use Oracle GoldenGate instead of the native cache refresh mechanism of TimesTen to provide the equivalent of static read-only cache groups for both TimesTen Classic and TimesTen Scaleout. All other types of cache functionality must use the native cache mechanism of TimesTen. See Using Oracle GoldenGate as an Alternative Cache Refresh Mechanism in Oracle TimesTen In-Memory Database Cache Guide.

  • You can perform a fast patch upgrade with TimesTen Classic. This involves performing operations to modify a TimesTen instance to point to a new installation while ensuring the shared memory segment remains in memory. See About Performing a Fast Patch Upgrade in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.

  • For TimesTen Scaleout, you can now perform online upgrades to patch-compatible releases. This release adds the ttGridAdmin gridUpgrade command to simplify online and offline upgrade operations. See Upgrading a Grid in Oracle TimesTen In-Memory Database Scaleout User's Guide.

  • TLS certificate management is now supported in TimesTen Scaleout. See Certificates for Transport Layer Security in Oracle TimesTen In-Memory Database Security Guide.

  • The TimesTen Prometheus Exporter together with Grafana tools enables you to monitor the health and operation of your databases. See The TimesTen Prometheus Exporter in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.

  • You can now configure the client/server buffer size. This can improve performance when retrieving large result sets on slower networks. See Sizing the Client Result Set Buffer in Oracle TimesTen In-Memory Database Operations Guide.

  • SQL Profiles now support password complexity check functions. See CREATE PROFILE in Oracle TimesTen In-Memory Database SQL Reference.

  • On Linux platforms, TimesTen Classic now supports SNMP version 1, 2, and 3 through Net-SNMP. This replaces the prior SNMP version 1 implementation and its snmp.ini configuration file. See Diagnostics Through SNMP Traps in Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.

  • You can now control LRU aging based on a number of rows. See Usage-Based Aging in Oracle TimesTen In-Memory Database Operations Guide.

  • For certain query types, TimesTen can now dynamically load multiple cache instances. See Dynamically Loading Multiple Cache Instances in Oracle TimesTen In-Memory Database Cache Guide.

  • You can set the TT_DynamicPassthrough optimizer hint to notify TimesTen Classic to pass through qualified SELECT statements to the Oracle database. See Automatic Passthrough of Dynamic Load to the Oracle Database in Oracle TimesTen In-Memory Database Cache Guide.

  • A new type of cache group is added to this release. Hybrid cache group is a dynamic read-only cache group where the root table is created in the TimesTen database and does not exist in the Oracle database. See Hybrid Cache Group in Oracle TimesTen In-Memory Database Cache Guide.

  • On Linux platforms that use systemd, you can use systemd to automatically manage the TimesTen daemon for TimesTen Classic. See Using systemd to Manage a TimesTen Service in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.

  • This release now supports multiple OUT refcursors in PL/SQL. See PL/SQL REF CURSORs in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.

  • As aging deletes rows, TimesTen frees empty pages and reuses empty slots on non-full pages. 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 in Oracle TimesTen In-Memory Database Operations Guide.

  • You can define a readiness probe to tell Kubernetes that a TimesTen (tt) container is ready. See Readiness Probes in Oracle TimesTen In-Memory Database Kubernetes Operator User's Guide.

Behavior Changes and Deprecated Features

  • The ResultSet returned when calling the ttSQLCmdCacheInfo built-in procedure has two new columns.

  • The directory name of the directory for the bundled Oracle Instant Client is changed.
  • The -setMasterRepStart option is now the default for ttRepAdmin -duplicate command.

  • These features are deprecated in this release:

    • Scaleout PhysicalGroups
    • Temporary databases
    • Static autorefresh cache groups with legacy replication
    • The TTC_RollbackRequiredOnFailover client connection attribute
    • Local shared memory ipc for client/server connections.
  • The -list all | userinfo option of the ttSchema utility now prints user information, such as CREATE PROFILE, CREATE USER, and GRANT statements. CREATE USER statements are printed with the PASSWORD EXPIRE and ACCOUNT LOCK parameters specified and the password for the IDENTIFIED BY parameter is replaced with DISABLED: followed by a random set of characters.

Bug Fixes

  • In TimesTen Scaleout, a problem is fixed where the eviction process would suspend when a replica set was down. (BugDB #29586987)

  • On Linux 64-bit platforms, in previous releases compiling TTClasses source could result in a compiler warning and possible loss of data. This problem is fixed. (BugDB #29626001)

  • The rownum parameter for the ttSize built-in procedure is now of type BIGINT. Previously it was type INT. (BugDB #31645887)

  • In previous releases, a SELECT COUNT (*) operation could fail when a table has a very large number of rows. (BugDB #32620599)

  • In this release, the default value of TT_DYNAMICLOADMULTIPLEPKS optimizer hint is 1 . (BugDB #32690444)

  • In TimesTen Scaleout, in previous releases the loghold bookmark was updated during a backup procedure. This caused an assertion. In this release the bookmark update is conditional. (BugDB #32800967)

  • In this release the ttGridAdmin backup, restore, import and export commands accept a new option to specify the directory for temporary files. (BugDB #32801316)

  • An issue has been fixed that caused an overflow when creating a unique index on a large table. (BugDB #32874657)

  • In this release, the number of daemon log messages for rollback is reduced. (BugDB #32995755)

  • In a previous release, a rare edge case when multiple databases were caching the same tables with different cache admin users could lead to the wrong bookmarks being used. This problem is fixed. (BugDB #33360774)

Platforms and Compilers

Platform or operating system C/C++ compiler support JDK support(1)

Linux x86-64:

  • Oracle Linux 7.4 or later and 8.2 or later

  • Red Hat Enterprise Linux 7.4 or later and 8.2 or later

  • SUSE Enterprise Server 12 and 15

Intel icc, gcc 4.4.7 or later

Oracle JDK 8, 11 and 17

OpenJDK 8, 11 and 17

Solaris SPARC 64:

  • Solaris 11.3 and 11.4

Solaris Studio 12.6 for Solaris SPARC

Oracle JDK 8 and 11

Solaris x86-64:

  • Solaris 11.3 and 11.4

Solaris Studio 12.6

Oracle JDK 8

Microsoft Windows x86-64 (Client only):

  • Windows Server 2019

  • Windows Server 2016

  • Windows Server 2012 R2

  • Windows 11

  • Windows 10

Intel Compiler 17

Visual Studio 2017 (VC11)

Oracle JDK 8, 11 and 17

OpenJDK 8, 11 and 17

IBM AIX Power PC 64-bit:

  • AIX 7.1, 7.2 and 7.3

IBM xlC 13.1.0 Compiler for AIX


IBM Semeru Runtime Certified Edition, Version 11

macOS 64-bit (Client only):

  • 12 Monterey

  • 11 Big Sur

  • 10.15 Catalina

Apple Xcode 12.0.5

Oracle JDK 8, 11 and 17

Footnote 1 TimesTen ttjdbcn.jar files generally include the JDBC driver for use with the JRE version that corresponds to the number in the file name. In the current release, ttjdbc11.jar and ttjdbc17.jar are copies of ttjdbc8.jar, implementing JDBC 4.2 (Java 8) only.

TimesTen is supported in virtual machines provided by Oracle VM.

Oracle Database

TimesTen ships the Oracle Database 19c version of Instant Client. In addition, TimesTen PL/SQL, OCI, Pro*C/C++, and other internal components are based on Oracle Database 19c.

Client/Server Configurations

A TimesTen client on any supported platform can connect to a TimesTen server on any platform where TimesTen is supported.

See Configuring TimesTen Client and Server in Oracle TimesTen In-Memory Database Operations Guide.


Cache in TimesTen enables you to view and modify data pulled from an Oracle database into a TimesTen database. The TimesTen installation includes Oracle Instant Client.

The following Oracle server releases are supported for cache in TimesTen:

  • Oracle Database Release

  • Oracle Database Release 12c

  • Oracle Database Release 19c

Replication Configurations

TimesTen only supports replication between identical platforms. Replication is supported with TimesTen Classic only.

Active standby pair replication is supported with Oracle Clusterware 19c.

See Overview of TimesTen Replication in Oracle TimesTen In-Memory Database Replication Guide.

Kubernetes Operator

TimesTen and the TimesTen Kubernetes Operator are supported on Kubernetes 1.22, 1.23 and 1.24.

We have tested TimesTen and the TimesTen Kubernetes Operator in AWS EKS and OCI OKE.

Other Kubernetes environments are supported if they meet the requirements listed in Prerequisites in Oracle TimesTen In-Memory Database Kubernetes Operator User's Guide.

Oracle GoldenGate

TimesTen is supported as a delivery target with GoldenGate 21.3 or later. GoldenGate parallel Replicat is supported for increased apply performance.

See Using GoldenGate as an Alternative to Native Read-Only Cache Groups in Oracle TimesTen In-Memory Database Cache Guide.

Apache ZooKeeper

TimesTen ships a modified version of ZooKeeper 3.8.0, to address various CVEs and other problems. Please refer to installation_dir/tt22. for details.

TimesTen Scaleout supports the following versions of ZooKeeper:

  • Any ZooKeeper version included in any TimesTen release within the same TimesTen major release cycle.

  • Any ZooKeeper version downloaded from Apache that meets the following criteria:

    • The ZooKeeper release is marked as Stable.

    • The ZooKeeper release is of the same ZooKeeper release line as a ZooKeeper version included in the TimesTen major release cycle.

TimesTen Driver Manager

TTDM is supported on TimesTen (or later) and on all platforms with TimesTen server support.

See Introduction to the TimesTen Driver Manager in Oracle TimesTen In-Memory Database C Developer's Guide.

Software Requirements

For software requirements, refer to:

Known Problems and Limitations

This topic contains known problems and limitations in these categories:


  • Restoring a grid backup (using the ttGridAdmin dbRestore command) succeeds only when all instances in the grid are running.


  • ttLoadFromOracle may fail with error message ORA-01466, can't flashback because table definition too new. This problem may be the result of a missing patch in Oracle Database (Bug 6598432). This bug leads to ORA-01466 when the Oracle database timezone and the system timezone are different. If the user hits this problem, verify that the corresponding patch is applied.


  • On Oracle Linux 8 and Red Hat Enterprise Linux 8 systems, TimesTen requires these libraries or packages:

    • /usr/lib64/libnsl.so.1

    • ncurses-compat-libs

    To install both, run:

    sudo yum install libnsl ncurses-compat-libs
  • On IBM AIX, the ttCreateCerts utility may fail with the following error:

    ewallet.p12 not present at rootWallet
    PKI-02003: Unable to load the wallet at: rootWallet

    This is a problem with IBM JDK As a workaround, use IBM JDK or earlier.


  • TimesTen does not support Positioned Updates and Deletes. Calls to setCursorName and getCursorName methods are ignored.

  • If a JDBC application running in a time zone that has Daylight Savings Time selects a nonexistent time using ResultSet.getTimestamp(), it gets a time that is an hour behind. For example, in Pacific Standard Time, on the day when the time changes from Standard to Daylight Savings Time, the time between 2:00 a.m. and 2:59 a.m. does not exist. So, if a JDBC application running in Standard Time selects a value of '2002-04-07 02:00:00' using getTimestamp() it gets '2002-04-07 01:00:00'.

  • SQL statements in JDBC applications should contain only characters from the database character set. Unicode characters not in the database character set are converted to replacement characters during parsing of the query. Potential workarounds include:

    • Using AL32UTF8 as the database character set.

    • Parameterizing the statement to avoid characters that are not in the database character set in the query text.

  • On macOS, if you are running TimesTen JDBC applications, ensure that you include the following in the Java command line: ‑Djava.library.path=${TIMESTEN_HOME}/install/lib

Oracle Call Interface

  • If NLS_LANG is set to a value that is not supported by TimesTen, spurious errors such as "Cannot connect" may result.

  • Due to the TimesTen upgrade to Oracle Database 19c, customers using Pro*C or Oracle Call Interface (OCI) and APIs based on OCI will need to relink their applications with the new OCI library due to a name change. You may also need to update your Makefiles accordingly.


  • Using q' (quoting syntax) is not supported.

  • This sequence of operations involving PL/SQL and CLOBs or NCLOBs does not work correctly.

    1. Create a temporary CLOB.

    2. Set the temporary CLOB value.

    3. Assign the value of the temporary CLOB to another CLOB variable.

    4. Free the temporary CLOB.

    5. Try to use the temporary CLOB.

    At step 5, an error ORA-22275 is supposed to be generated, and an exception is supposed to be raised. In TimesTen 22.1.1, the correct error is generated, but no exception is raised.


  • TimesTen does not support SQL*Plus connections to TimesTen databases. Use ttIsql.

SQL, Utilities and Procedures

  • When SQL query timeouts are used (SQLQueryTimeout or SQLQueryTimeoutMsec), TimesTen behavior is on a best-effort basis. It is not possible to guarantee that the timeout will actually occur within the specified time. (BugDB #29671762)

  • TimesTen BINARY_DOUBLE and BINARY_FLOAT are approximate data types. When storing and retrieving data of these types, the least significant digits may be rounded or truncated. You should avoid using columns of these types in primary keys, unique keys and foreign keys.

  • When the same column alias name is used in a view definition and a query that references the view, TimesTen might incorrectly issue the TT2210: Column reference of XXX is ambiguous error. The workaround is to explicitly assign a different column alias name to the column.

  • In TimesTen Scaleout, the ALTER SESSION statement should return an error when attempting to alter an unsupported feature. Instead, no error is returned.

  • The maximum sum of the total number of tables specified in a query and all temporary aggregates needed to handle the query is 32. A temporary aggregate is needed to handle scalar or aggregate subqueries. A query fails with the message Statement that needs more than 31 nesting levels has not been implemented when the sum of tables and temporary aggregates in a query is greater than 32.

  • COUNT DISTINCT with CHAR type uses binary sorting order and binary comparison semantics even when the NLSSORT attribute was set to a value different than binary.

  • When the NLS_SORT session parameter is set to a multilingual sort (for example, FRENCH_M), the LIKE operator may produce incorrect results when the pattern match wild-card symbols are applied to the space character.

  • If you execute an ALTER SESSION statement anytime after the initial connection, you must re-execute the statement after a failover. (BugDB #29444131)

TimesTen Scaleout

  • TimesTen Scaleout supports a maximum of 64 data instances in this release.

  • Instances in a grid connect with each other over TCP/IP using ports within the dynamic port range. For this reason any active firewall needs to be configured to allow TCP/IP traffic over all possible ports in each host's dynamic port range. On Linux, you can determine the port range as follows:

    $ cat /proc/sys/net/ipv4/ip_local_port_range
    9000    65500 

    In this case, the host may allocate ports in the range 9000 through 65500.

  • Each process connected to a TimesTen Scaleout database keeps at least one operating system file descriptor open. Additional file descriptors may be opened for a connection when the connection commits or rolls back a transaction. If you receive an error that all file descriptors are in use when attempting to connect to a database, increase the allowable number of file descriptors. (BugDB #25815090)

  • If two instances (including managements instances) are added to a distribution map using ttGridAdmin dbDistribute command but the hosts to which they belong cannot communicate through SSH, the ttGridAdmin dbDistribute command fails with error TT3701.

  • If you restore a database backup with cache groups into a grid with a larger topology, you must set the cache administration user name and password for the database (using the ttGridAdmin dbCacheCredentialSet command) before redistributing the data to all replica sets (using the ttGridAdmin dbDistribute command). Otherwise, you will be unable to set the cache credentials for the cache groups.


  • Enhancements to the replication protocol mean that to perform an online upgrade between and 22.1, the release must be or later. If you are using a version prior to the, you must upgrade to a newer release and then perform an online upgrade to this release using the documented online upgrade steps.

  • On TimesTen Classic, if you are on 18.1.2, you must first upgrade to or later before upgrading to this release. If you are on 18.1.3, you must first upgrade to or later before upgrading to this release.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.