Skip Headers
Oracle® TimesTen In-Memory Database Release Notes
Release 11.2.1

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

  PDF · Mobi · ePub

Oracle® TimesTen In-Memory Database

Release Notes

Release 11.2.1


January 2011

This document provides late-breaking information for TimesTen release, 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 may also be updated from time to time in the documentation library at

Information about TimesTen 11.2.1 releases before can be found at

To install the Oracle TimesTen In-Memory Database, run setup from the installation media pack. For installation information, see Oracle TimesTen In-Memory Database Installation Guide. This guide can be accessed from install_dir/doc/ at the root of the installation media pack.

This document contains the following sections:

1 Changes in this release

This section lists changes between releases:

1.1 Changes for Release from Release

1.1.1 New features in Release

  • You can create or drop a table, index or synonym in an active standby pair without stopping the replication agent. You can choose to have these statements replicated to the standby database. You can include a table in an active standby pair when the table is created. Use the DDLReplicationLevel and DDLReplicationAction connection attributes to control what is replicated. See Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

  • When using Oracle Clusterware, you can add or drop a global cache group while the active database in an active standby pair is attached to a grid. See Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

  • Users of the ttBulkCp utility can write null values as empty strings by using the -nullFormat option. See Oracle TimesTen In-Memory Database Reference. (BugDB 9822277)

  • Enhanced messages about final and recovery checkpoints are displayed in the ttmesg.log file. (BugDB 9794314)

  • ODP.NET support for Oracle TimesTen In-Memory Database and Oracle In-Memory Database Cache is available in the latest release of Oracle Data Access Components (ODAC) This release of ODAC supports TimesTen releases or later on Microsoft Windows 32-bit and 64-bit platforms.

  • TimesTen has been tested with the following application servers and ORM (Object-Relational Mapping) frameworks:

    J2EE (EJB 3.0) application servers:

    • Oracle WebLogic Server 11g Release 1 (10.3.3)

    • Oracle GlassFish Server 3

    • JBoss Application Server 5

    • WebSphere Application Server 7

    ORM frameworks:

    • JPA with EclipseLink 2

    • Hibernate 3

    • JPA with Hibernate 3.5.6

    • JPA with OpenJPA 2

  • Oracle Clusterware and TimesTen processes report messages to the ttcwmsg.log file that indicate missing checkpoint files or other causes of database invalidation.

1.1.2 Bug fixes in Release

  • The values set by the ttAgingLRUConfig built-in procedure are persistent across daemon restarts. (BugDB 10162337)

  • The TimesTen daemon sometimes reported that the cache agent or replication agent was running when it was not. Attempts to stop or start either agent resulted in messages that the agent was already started or already stopped. This problem has been fixed. (BugDB 10014011)

  • Oracle error ORA-06550 could occur under these conditions:

    • An AWT cache group is used and the cacheAWTMethod connection attribute is set to 1 (PL/SQL execution method)

    • One or more of the columns in the AWT cache table mapped to an Oracle LOB

    • The primary key contained a column with one of the following data types: CHAR, VARCHAR2, TIMESTAMP, DATE

    This problem has been fixed. (BugDB 10305926)

  • In TimesTen OCI, calling OCIServerVersion() from a multithreaded program could lead to a segmentation violation. This problem has been fixed. (BugDB 9844710)

  • In TimesTen Pro*C, executing a SELECT statement with a cursor and fetching an array of values multiple times could lead to bad results. In particular, the second and subsequent executions of the same array select statement could produce incorrect values, whereas the first execution would produce correct values. A symptom of this problem is that the values that should have been last in the array were placed first, with the other values being empty or zero. (BugDB 10238977)

  • A SELECT statement could generate a different plan when executed within a view than when it was executed directly on a table. This has been fixed. (BugDB 10161402)

  • A scaling issue with frequent updates to the SYS.SYSTEMSTATS table was fixed. (BugDB 10271481)

  • A read performance issue caused by an internal instrumentation of the JDBC driver has been fixed. (BugDB 10236300)

  • A read-only cache group was not being automatically refreshed after inserts to the Oracle table for CHAR data. This problem has been fixed. (BugDB 10334320)

  • When the owner of a view containing a subquery did not have the ADMIN privilege, the owner was unable to select from the view. This problem has been fixed. (BugDB 10270657)

  • Manually refreshing a cache group with multiple tables that is replicated in an active standby pair failed with a foreign key violation. This problem has been fixed. (BugDB 10363168)

  • A query could give incorrect results if the query had an outer join and a subquery with an IN clause and a SET operator in the IN clause. (BugDB 10152127)

  • A PreparedStatement.setNull(parameterIndex,Types.NULL) before any non-null PreparedStatement.setXXX() could fail. This problem has been fixed. (BugDB 10407225)

  • When using the -record option for the instance home directory, options 1 and 2 create invalid answer files which cause the -batch option (silent install) to not work as expected. This problem has been fixed. (BugDB 10207746)

  • The output of the query with IN(value) clause and IN(subquery) clause gave different results, even though the subquery returned the same values as the hardcoded values. This problem has been fixed. (BugDB 10164510)

  • In a configuration that is managed by Oracle Clusterware, failover could be triggered by the active database being out of perm space. This has been fixed. (BugDB 11057224)

  • See "TimesTen to TimesTen Replication" for information about cross-release migration and manual parallel replication.

  • A performance regression for a full table scan was fixed. (BugDB 9622365)

  • A REFRESH CACHE GROUP operation could result in errors 16090 (failed to check constraints) or 3001 (foreign key violation). This problem has been fixed. (BugDB 10428647)

  • The optimizer chose table locks when processing SELECT statements with parameterized FIRST n or ROWS m TO n clauses or a ROWNUM condition. It now chooses row locks in these situations unless the use of a table lock is forced by an optimizer hint. (BugDB 1166474)

1.2 Changes for Release from Release

  • A problem with the log reader has been fixed. This problem could cause replicated databases to go out of sync. It also could cause TimesTen to return error 16211: "No matching v* value found for table". (BugDB 10226676)

  • This release supports cross-release replication and migration from a database that does not have manual parallel replication enabled to a database that does have parallel replication enabled. (BugDB 10232988)

    See "TimesTen to TimesTen Replication" for more information about cross-release migration and manual parallel replication.

    The following is an example of migrating a database to a manually configured parallel replication scheme.

    1. Start with two TimesTen databases from a release earlier than Consider two databases, rep1 and rep2, with the following scheme:

      STORE rep1 PORT 12345 
      STORE rep2 PORT 12346;
    2. Set the replication state to pause on rep1.

      ttRepAdmin -state pause rep1
    3. Stop replication on database rep2:

      ttAdmin -repStop rep2
    4. Create a migration file and destroy database rep2:

      ttMigrate -c -repUpgrade rep2 rep2.mig ttDestroy rep2
    5. Set environment to

    6. Edit rep2 DSNs to include ReplicationApplyOrdering=1, ReplicationParallelism=n

      At this stage no parallelism is in use on database rep2, but you have configured it and the database will have parallel replication once it is communicating with another parallel replication database.

      Bidirectional replication is possible between databases rep1 and rep2 after you perform these steps. An ALTER TABLE operation on database rep1 will be applied to database rep2. However, an ALTER TABLE operation on a database that has parallel replication enabled is not permitted. The ALTER TABLE operation on database rep2 fails.

    7. On TimesTen restore database rep2 with parallel replication from the migration file:

      ttMigrate -r rep2 rep2.mig
    8. Start replication on database rep2:

      ttAdmin -repstart rep2
    9. Set the replication state on rep1 to start.

      ttRepAdmin -state start rep1
    10. Apply a similar procedure to database rep1 to bring both databases up to the latest TimesTen version and to enable parallel replication between both databases. You can use ttRepAdmin -duplicate to upgrade rep1 instead of using ttMigrate.

      Bidirectional replication is possible between databases rep1 and rep2 should now be possible and user defined replication through multiple tracks can be used.

    Once you have enabled parallel replication between two databases, it is not possible to downgrade one side to a non-parallel version and replicate to the parallel-enabled side.

  • A read performance issue caused by an internal instrumentation of the JDBC driver has been fixed. (BugDB 10236300)

  • A scaling issue with frequent updates to the SYS.SYSTEMSTATS table was fixed. (BugDB 10271481)

  • A problem has been fixed in which a TTClasses application that calls the overloaded TTCmd method setParam(char*), setParam(void*, int) or setParam(SQLWCHAR*, int) with a parameter whose length is greater than 4000 bytes long could encounter a memory fault, memory corruption or incorrect result. (BugDB 10275365)

  • In a bidirectional replication scheme that includes sequences, the memory usage of the replication agent on the "passive" database could appear to grow unbounded when the other database was updated. This problem has been fixed. (BugDB 10282229)

  • In previous releases, a replication agent could encounter an assertion failure: EOLCNT == LOGC->USEDSTRANDCNT. This problem has been fixed. (Bug 10332533)

1.3 Changes for Release from Release

The behaviorchanges.txt file is no longer included in the installation directory. Behavior changes are included in this document.

1.3.1 Behavior changes in Release

  • Previous behavior: If SUBSTR() result is longer than the target column, the result is silently truncated and an insert or update succeeds with the truncated string.

    New behavior: If the result of SUBSTR() is longer than the target column in an insert or update statement, the operation fails with error 982: "String exceeds column width". For example, if column x is of type CHAR(4), SET x=SUBSTR('abcdefg',2) results in error 982. SUBSTRB() in a multibyte character set continues to silently truncate the string, and insert or update continues to succeed with the truncated string.

1.3.2 New features and changes in Release

See the "What's New" prefaces in the documentation to see the new features documented in a specific guide.

  • You can create an explicitly loaded global cache group in a cache grid. If the cache tables on the local grid member do not contain data that satisfies a query, then the cache instance is transferred from other grid members to the local grid member in a grid data transfer operation. If the grid does not contain the cache instance that satisfies the query, data is not loaded from the Oracle tables and the query returns no results. See Oracle In-Memory Database Cache User's Guide.

  • Oracle Data Provider for .NET is available for Oracle TimesTen In-Memory Database. It enables fast data access for .NET applications using ADO.NET. This data provider supports TimesTen release or later on Microsoft Windows 32-bit and 64-bit platforms. It supports the .NET 2.0, 3.0 and 3.5 frameworks with Microsoft Visual Studio 2005 or later, and .NET 4.0 with Visual Studio 2010. The Oracle Data Provider for .NET is available for download on Oracle Technology Network:

    For more information, see Oracle Data Provider for .NET Oracle TimesTen In-Memory Database Support User's Guide.


    Oracle Data Provider for .NET supports Oracle TimesTen In-Memory Database only. A future release of Oracle Database Provider for .NET will support both Oracle Database and Oracle TimesTen In-Memory Database.
  • TimesTen now supports CALL syntax from any of its programming interfaces to call PL/SQL procedures and functions. TimesTen's name resolution for the CALL statement may differ from Oracle's name resolution for the CALL statement. See Oracle TimesTen In-Memory Database SQL Reference for information about the CALL statement.

  • The SYS_CONTEXT expression can be used to retrieve the connection ID. See Oracle TimesTen In-Memory Database SQL Reference.

  • Tables with aging are not supported with track-based parallel replication. In this release, TimesTen prevents the user from including a table with aging from being part of a replication scheme when ReplicationApplyOrdering=1.

  • TimesTen is supported for SUSE 11 on Linux x86-64.

  • The default value for the -maxsupportlogsize daemon option has been changed from 1 to 10 MB. See Oracle TimesTen In-Memory Database Operations Guide.

  • Aging statistics have been added to the SYS.SYSTEMSTATS system table. See Oracle TimesTen In-Memory Database System Tables and Limits Reference.

  • Using TimesTen with IBM Java SDK 1.6 for 32-bit and 64-bit on Linux x86 is supported. To use this Java SDK, a fix from IBM is required, published as APAR IZ76406, which is included in Java 6 SR8 FP1.

  • The ScriptInstallDir attribute is not required to configure Oracle Clusterware with TimesTen. The attribute is deprecated in this release.

1.3.3 Bug fixes in Release

  • The ttMigrate utility returns exit codes. See Oracle TimesTen In-Memory Database Reference. (BugDB 8637795)

  • In previous releases, ttBulkCp failures returned an incorrect code. This problem has been fixed. (BugDB 9414206)

  • In previous releases, the -showdate daemon option was not enabled for the Server process. This problem has been fixed. (BugDB 9722055)

  • A CREATE VIEW statement fails if the view definition contains a union, and one side of the union is a query that selects from a derived table that is a join. In this release, TimesTen returns an error message that describes the problem. (BugDB 9864076)

  • Create cache group checks if the user has the appropriate Oracle privilege. For example, it checks if the user has SELECT ON privileges on each table in the cache group. In the release, the code checks for individual privileges, as well as those granted through a role. In earlier releases, it was not checking against role privileges. (BugDB 9873532)

  • When grid failed to allocate memory a message will be logged to the daemon log to indicate this fact. The message will have the following format: Member 'memberName' failed to allocate temp space, errorcode='errNo' - 'errMessage'. (BugDB 9893472)

  • Public access to TimesTen objects in the Oracle database that are used for cache operations is no longer allowed. (BugDB 9957021)

  • In previous releases, the fractional second field of an Oracle TIMESTAMP value contained in a PL/SQL variable buffer was inadvertently modified when it was prepared for conversion into the TimesTen TT_TIMESTAMP format. This problem has been fixed. (BugDB 9903966)

  • SQL operations executed internally by PL/SQL may generate warnings, for example, because of low memory or replication failures. In previous releases these warnings could cause ORA-0600 errors to be emitted. In this release ORA-0600 errors do not result from these temporary warning conditions. (BugDB 9916812)

  • In a client/server configuration, errors in starting child server processes resulted in an "unexpected server exit" and no additional information. Now startup errors are reported. (BugDB 9934387)

  • Internal trace buffers are now flushed when the database is loaded into memory. Previously, trace data left over from a prior load of the database could interfere with new traces, causing errors that could result in database invalidation. (BugDB 9939628)

  • In previous releases, a call to the ttOptEstimateStats built-in procedure could result in an assertion when a concurrent transaction committed after deleting a large number of rows. In this release, TimesTen returns an error if TimesTen cannot perform the estimate. The new error has the form: "Estimate statistics on owner.table failed due to too some concurrent operation; try again." (BugDB 9954300)

  • In previous releases, altering a cache group could cause a core dump when the TimesTen configuration tables on the Oracle database were empty. This problem has been fixed. (BugDB 9956288)

  • The message for error 6226 has been changed to replace the obsolete LogBuffSize connection attribute name with LogBufMB. (BugDB 9961676)

  • The stability of TimesTen PL/SQL after unexpected application failures is improved. (BugDB 10011855)

  • In previous releases, a master-master replication scheme with two-safe enabled could create a backlog of replication records that were never sent to a subscriber database. This problem has been fixed. (BugDB 10029655)

  • In previous releases, calls to the ttOptSetFlag built-in procedure incorrectly reset the values set by the ttOptUseIndex built-in procedure. This problem has been fixed. (BugDB 10034510)

  • Dynamic load operations use the SQL command cache more efficiently than in previous releases. (Bug DB 10036720)

  • Dynamic load operations no longer cause a round trip to the Oracle database when the parent row is already in the IMDB Cache. (BugDB 10036751)

  • The log.commit.file.reads statistic in the SYS.SYSTEMSTATS system table. keeps track of how often TimesTen reads from the file system during commit processing. In previous releases, this statistic was higher than log.file.reads, which keeps track of total file system reads. The log.commit.file.reads statistic is now calculated correctly. (BugDB 10134912)

  • In previous releases, a replication agent or an XLA application could encounter an assertion failure blklen <= startIdMap->offset in the sbLogBufLRNextLocate function. This problem has been fixed. (BugDB 10145152)

  • A problem has been fixed in which the replication agent would crash with the assertion failure "SbBlkNoInStrandCmp(strandInfo.startBlkNo, blkNo )<=0" or "blklen <= startIdMap->offset" when reading near the end of the logs. This problem is specific to the SPARC architecture. (BugDB 10194728 and 10196227)

  • A problem has been fixed where an assertion could occur while executing SELECT statement through a procedure from a JDBC application. (BugDB 10167873)

  • In previous releases, the replication agent could crash and invalidate the database when the replication agent was reading close to the end of the in-memory logs. This problem could occur when the value of the connection attribute LogBufParallelism was greater than 1. In that case, one particular log record could cause a log strand reader to block and cause other strand-readers to read records in an incorrect order. This problem has been fixed. (BugDB 10174319 and 10176689)

  • In previous releases, a bad pointer caused an assertion in the sblogCtnWrapComplete function. This problem has been fixed. (BugDB 10176825)

  • A problem has been fixed where timing issues after a ttCWAdmin -init operation could generate false positives. (BugDB 10208113)

  • In previous releases, global dynamic AWT cache groups checked the Oracle tables for unique primary keys when inserts were performed on the TimesTen cache tables. This uniqueness check no longer occurs, which enables inserts to take place in TimesTen cache tables when the Oracle database is not available. (BugDB 10211940)

  • In previous releases, when a direct-linked application was terminated abnormally, other active connections or subsequent connections could cause database invalidation. This problem has been fixed. (BugDB 10008657 and 10214446)

  • An assertion could occur when parallel replication was enabled. The transmitter would crash when reading close to the end of the log, causing an incorrect check that failed when a connection changed its replication track number. This problem has been fixed. (BugDB 10218953)

  • A problem has been fixed where parallel replication would hang while running ttrepadmin -dsn DSN -receiver list. (BugDB 10223328)

2 Platforms

Environment 32-bit 64-bit Compiler notes
Microsoft Windows 2000, Windows XP, Windows Vista and Windows Server 2003 and 2008 for Intel IA-32 and EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 8.

VS .NET 2003, VS 2005 and VS 2008 are also supported.

To use the TimesTen debug library, you must use VS .NET 2003.

Asianux 2.0 and 3.0 for Intel IA-32 and EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 9.1.

gcc 3.4.6 and 4.1.0 are also supported.

Solaris 9 and 10 for UltraSparc CPUs. Yes Yes 64-bit compiled with Sun Studio 11.

32-bit shipped with a TimesTen client library compiled with gcc 3.4.6 and a client library compiled with SunStudio 11.

Solaris 10 for x86-64. No Yes Compiled with Sun Studio 10. Tested on AMD64 CPUs.
SUSE Linux Enterprise Server 10 for Intel IA-32 and EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 9.1.

gcc 3.4.6 and 4.1.0 are also supported.

SUSE Linux Enterprise Server 10 for Itanium2 CPUs. No Yes Compiled and tested with Intel 9.1.

gcc 3.4.5 and 4.1.0 are also supported.

SUSE Linux Enterprise Server 11 for Linux x86-84 No Yes gcc 4.3
Red Hat Enterprise Linux 4 and 5 for Intel Itanium2 CPUs. No Yes Compiled and tested with Intel 9.1.

gcc 3.4.5 and 4.1.0 are also supported.

Red Hat Enterprise Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 9.1.

gcc 3.4.6 and 4.1.0 are also supported.

Oracle Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 9.1.

gcc 3.4.6 and 4.1.0 are also supported.

Monta Vista Linux Carrier Grade Edition Release 4.0 and 5.0 for Intel IA-32, EM64T and AMD64 CPUs. Yes Yes Compiled and tested with Intel 9.1.

gcc 3.4.6 and 4.1.0 are also supported.

HP-UX 11i v2 and 11iv3 for PA-RISC. Yes Yes Compiled and tested with the HP compiler.
HP-UX 11i v2 and 11iv3 for Itanium2. Yes Yes Compiled and tested with the HP compiler.
AIX 5L 5.3 and 6.1 for POWER CPUs. Yes Yes Compiled and tested with the AIX compiler.
Mac OS X 10.6 Yes No Compiled and tested with gcc 4.2.1.

TimesTen is supported on Oracle VM guest x86 and x86-64 operating systems on Oracle Linux 4 and 5 or Red Hat Enterprise Linux 4 and 5 systems.

3 Software requirements

For software requirements, refer to Oracle TimesTen In-Memory Database Installation Guide.

4 Deliverables

You should receive the following with your copy of the Oracle TimesTen In-Memory Database:

If any of these items is missing, contact Oracle TimesTen support. See "Contacting support".

5 Advance notice

This section lists deprecated and removed items and desupport of platforms, Oracle releases, JDK releases and compilers.

5.1 Deprecated items in Releease

The MonInterval Clusterware attribute

5.2 Deprecated items in Release

The ScriptInstallDir Clusterware attribute

5.3 Removed items in Release

The -lsn option of the ttXactAdmin utility

5.4 Deprecated items in Release

  • LogBuffSize attribute. Use LogBufMB instead. The units have changed from kilobytes to megabytes.

  • Including sequence values in a CREATE VIEW statement is deprecated.

5.5 Removed items in Release

  • Authenticate attribute

  • It is not possible to set the Logging attribute to 0. The only possible value is 1.

  • Built-in procedures: ttCommitLSN, ttLogBufPrint, ttuser, ttUserPrivileges

  • The -at and -af options of the ttXactLog utility have been removed.

5.6 Deprecated items in Release

  • The GroupRestrict and Authenticate attributes are deprecated. They are scheduled to be removed in a later release.

5.7 Removed items in Release



  • The ttCacheAgingMemoryThresholdSet and ttCacheAgingIntervalSet built-in procedures

  • The TransparentLoad attribute and the TT_TRANSPARENT_LOAD ODBC option have been removed. Use dynamic cache groups instead.

  • The OracleID attribute has been removed. Use OracleNetServiceName instead.

  • The ExclAccess attribute has been removed.

  • The Cache Administrator (web-based user interface) has been removed.

  • TimesTen no longer supports these platforms: AIX 5.2, HP-UX 11i v1, RedHat 3, Solaris 8 (Sparc), Solaris 10 x86 32-bit, SUSE Linux 9 and TRU 64.

  • TimesTen no longer supports Oracle9i or Oracle 10.1.0.x.

  • TimesTen no longer supports JDK 1.4.x on all platforms. Also, classes15.jar and classes16.jar have been removed.

  • TimesTen no longer supports the gcc 3.2.3 compiler, Visual C++ 6.0, Visual Studio .NET 2002 and Sun Studio 10.

6 Known problems and limitations

This section contains known problems and limitations.

6.1 Installing and uninstalling TimesTen

  • TimesTen is not supported with these Oracle Linux 5 kernels: Oracle Linux 5 GA with virtualization option (2.6.18-8.el5xen), Oracle Linux 5 Update 1 with virtualization option (2.6.18-53.el5xen), Oracle Linux 5 Update 2 with virtualization option (2.6.18-92.el5xen).

    TimesTen is supported with these Oracle Linux 5 kernels: Oracle Linux 5 kernel version 2.6.18* without the xen suffix and without the virtualization option, Oracle Linux 5 Update 4 with virtualization option (2.6.18-164.el5xen), Oracle Linux 5 Update 5 with virtualization option (2.6.18-194.el5xen).

    The uname -r Linux command displays the Linux kernel version.

  • If you are installing Oracle TimesTen on a new 64-bit RedHat Linux system, you may find that it is not enabled for 32-bit applications. According to the Redhat Enterprise Linux installation guide: 'Users of AMD64, Intel(R) EM64T, and Itanium systems who want support for developing or running 32-bit applications are encouraged to select the Compatibility Arch Support and Compatibility Arch Development Support packages to install architecture specific support for their systems.'

  • On Windows 64-bit systems, TimesTen 32-bit and 64-bit instances cannot coexist on the same system.

  • On Windows systems, you cannot perform a modified or incremental installation. For example, if you originally installed only the Oracle TimesTen Client and later wanted to install the Oracle TimesTen Data Manager, you need to uninstall TimesTen and reinstall all of the components you wish to have on your system.

  • When uninstalling TimesTen on Windows, the oci.dll file shipped with the TimesTen installation sometimes cannot be removed because it is in use by a process that is not part of TimesTen.

  • To run TimesTen 32-bit on AIX, you must install the appropriate fix or higher mentioned at:

    Without this operating system patch, core dumps or other serious problems may occur when running TimesTen.



  • For releases and later, you must relink applications on AIX after installing TimesTen. Failure to do so results in an application execution error similar to the following:

    Could not load program _application_:
    Dependent module _tt_inst_dir_/lib/libtten.a( could not be loaded.
    File _tt_inst_dir_/lib/libtten.a is not an archive or the file could not be read properly.
    System error: Exec format error
  • When re-installing TimesTen on UNIX, existing sys.odbc.ini and sys.ttconnect.ini files are optionally saved as sys.odbc.ini.old and sys.ttconnect.ini.old files and new demo files are installed. In this case, you must manually merge any additional DSNs that may have been defined after reinstalling.

6.2 Upgrading TimesTen

  • The ttMigrate utility cannot migrate foreign key dependencies between objects owned by different users to TimesTen release and later without a workaround. To work around this problem, first restore the parent tables. Then grant the owner of the child tables the appropriate REFERENCES privileges on its parent tables. Finally, restore the child tables.

  • The ttMigrate utility cannot migrate materialized views to TimesTen release and later without a workaround. To work around this problem, first restore the detail tables referenced by the materialized view. Then grant the owner of the materialized view SELECT privileges on every detail table. Finally, restore the materialized view.

6.3 Log Files

  • Support log files do not rotate properly on Windows operating systems. When the MaxSupportLogFiles limit is reached, new log files should overwrite old files in the order they were created. On Windows systems, new log files randomly overwrite the old files.

6.4 PL/SQL

  • PL/SQL is not supported on Solaris x86 and Linux Itanium systems.

  • PLSQL_CODE_TYPE=NATIVE can be specified, but it is implemented as INTERPRETED.

  • JRockit on 32-bit Linux allocates a default heap that is 50 percent of available physical memory up to 1 gigabyte. Users of JRockit on 32-bit platforms may need to choose a value for PLSQL_MEMORY_ADDRESS other than the default (10000000). Consider values such as B0000000, which ensures that the PL/SQL shared memory is not part of the JRockit heap.

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

  • The EXECUTE IMMEDIATE statement cannot be used to execute a PL/SQL anonymous block.

  • UTL_FILE access is limited to a temporary directory located in install_dir/plsql/utl_file_temp. The instance administrator can grant access to UTL_FILE to specific database users. Users can reference the directory using UTL_FILE if and only if they provide the string 'UTL_FILE_TEMP' for the location parameter string.

  • With Java 6 on 32-bit AIX, connections to a PL/SQL-enabled database using the TimesTen direct driver may fail because of a memory address conflict between the Java memory segment and the TimesTen PL/SQL memory segment. Such a failure is reported as error TT8517:

    SQLException: [TimesTen][TimesTen ODBC Driver][TimesTen]TT8517:
    Cannot attach PL/SQL shared memory; 
    PLSQL_MEMORY_ADDRESS not valid or already in use

    The conflict can be resolved by specifying a smaller Java memory maximum size using the -Xmx option to java or the IBM_JAVA_OPTIONS environment variable. For example: java -Xmx64M. Use java -verbose:sizes to see the current default Java memory size.

    An alternative solution is to explicitly set the TimesTen PLSQL_MEMORY_ADDRESS connection attribute to a value that does not conflict with the Java segment. Potential good values for PLSQL_MEMORY_ADDRESS may include 0xe0000000 and 0xa0000000, depending on the environment and other factors. See the AIX documentation for a complete discussion of how Java uses memory on AIX.

6.5 TimesTen OCI support

See "Oracle Call Interface Support" in Oracle TimesTen In-Memory Database C Developer's Guide for detailed information about known problems and limitations.

  • TimesTen OCI is not supported on Solaris x86 or Linux Itanium systems.

  • Certain PL/SQL blocks with OUT parameters, when executed against TimesTen OCI, can generate an ORA-12899 error when the data coming back from the PL/SQL block overflows the bound output buffer. This occurs only when the parameters are bound with the UTF16 character set.

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

  • When an INSERT or UPDATE statement is executed which has an array of structures bound as parameters (using OCIBindArrayofStruct), the first execution of the statement succeeds. Subsequent executions may result in a numeric overflow error, a uniqueness constraint violation or a truncation error.

6.6 TimesTen support for Oracle Pro*C/C++ Precompiler

See "TimesTen Support for Oracle Pro*C/C++ Precompiler" in Oracle TimesTen In-Memory Database C Developer's Guide for detailed information about known problems and limitations.

  • TimesTen Pro*C/C++ is not supported on Solaris x86 or Linux Itanium systems.

  • The windows link line for a Pro*C application that uses SQLLIB functions should include both OCI.LIB and ORASQL11.LIB. The correct order is OCI.LIB first, then ORASQL11.LIB. Reversing the order can lead to the SQLLIB functions not working.

  • When a variable is declared as long long on 32-bit Solaris and 32-bit HP-UX platforms, Pro*C generates its size as long.

  • When compiling a Pro*C/C++ demo, this message may appear: "System default option values taken from: install_dir/ttoracle_home/instantclient_11_1/precomp/admin/pcscfg.cfg." The path name may be incorrect.

6.7 JDBC

  • On HPUX 11 systems, 32-bit JDBC client and direct drivers cannot coexist in one JVM due to some problems with loading shared libraries.

  • If a JDBC application running in a time zone that has Daylight Savings Time selects a non-existent 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'.

  • JDBC applications may see some memory leak if JDBC objects are not properly closed and have not been garbage collected before the corresponding Connection is closed.


  • TimesTen does not generate an XLA (Transaction Log API) record for CREATE MATERIALIZED VIEW LOG operations. See Oracle TimesTen In-Memory Database C Developer's Guide for other details about XLA.

  • JMS/XLA depends on the Oracle GDK for internationalization support. TimesTen distributions include a version of orai18n.jar in install_dir/lib that JMS/XLA is tested against. JMS/XLA may work with other versions of orai18n.jar but those versions are not supported. See Oracle TimesTen In-Memory Database Java Developer's Guide for other details.

  • To achieve the highest throughput, JMS/XLA applications running on Linux should follow performance guidelines presented in the section entitled "Handling high event rates" in Oracle TimesTen In-Memory Database Java Developer's Guide to work around these issues.

6.9 Cache grid

  • If an insert of a new instance in one grid node does not propagate to the Oracle database before a dynamic load operation for the same instance is executed on a child table in another grid node, then the dynamic load operation results in "0 rows found".

6.10 IMDB Cache

  • When trying to create a global cache group, the database can become invalidated if there are more than 15 errors in the cache group definition. This only happens when connecting to the Oracle Server. The workaround is to use Oracle Server release 10g, 11gR1, or an 11gR2 release higher than

  • There is a known issue (BugDB 9359437) that during a FLUSH CACHE GROUP operation, TimesTen may lock the tables and rows in the cache group tables. This can cause blocking or a deadlock if your application attempts to update the rows concurrently.

  • If an application performs more than one UNLOAD BY ID operation on a cache group, there is potential for a deadlock with the autorefresh transaction executed by the cache agent. The deadlock occurs only if those same rows are being updated on the Oracle database at the same time.

  • CREATE, ALTER and DROP CACHE GROUP statements are not supported in serializable isolation mode.

  • If DDL tracking is enabled on the Oracle database, destroying a database that has cache groups may result in the DDL trigger on a cached table not being dropped from the Oracle database. The user must manually drop each of these triggers using the DROP TRIGGER statement on the Oracle database. The DDL trigger name of a table with an Oracle object with identifier X is TT_X_DDL_T. The object identifier of an Oracle table can be retrieved from the V$ALL_OBJECTS view on the Oracle database.

  • For autorefresh cache groups, after a transaction that executes several DML operations on an Oracle base table (for example in a bulk insert), we recommend that you coalesce the autorefresh log table index (the logseq column in the change table). Use ALTER INDEX index_name COALESCE.

  • Oracle server bug 7512227 causes TimesTen autorefresh to miss inserts and updates on the Oracle base table. Autorefresh does not miss deletes. The Oracle Server bug applies to Oracle 10g releases and above but does not occur in Oracle Database 11g. There are two solutions:

    • Set the CURSOR_SHARING Oracle server parameter to EXACT.

    • Install the appropriate Oracle patch for Oracle release or above.

    See Metalink document 793948.1.

  • Caching an Oracle synonym that is owned by a different user results in error 5140: Could not find owner.synonym in Oracle. May not have privileges. The workarounds are:

    • The owner of the synonym can create the cache group.

    • Create a new private synonym that points to the original synonym and then create the cache group. The user who owns the cache group that caches the synonym must match the owner of the synonym.

  • For IMDB Cache to work correctly, the value returned by the hostname command and the uname -n command (UUCP address) must be the same. If hostname and uname -n return different values, IMDB Cache may report constraint violation failures on Oracle. Alternatively, you can use uname -s to make sure that the Internet and the UUCP addresses are the same.

  • Set SQLNET.SEND_TIMEOUT and SQLNET.RCV_TIMEOUT to a value large enough to avoid unnecessary timeouts during normal operations. For example, setting each parameter to 100 seconds forces any communication call from TimesTen to Oracle to time out within 200 seconds.

  • With Passthrough=3, if a JDBC application calls setTimestamp() on a passthrough statement when binding more than one field, the session NLS_TIMESTAMP_FORMAT is lost. You can work around this issue by changing the SQL statement to use TO_TIMESTAMP(?, 'syyyy-mm-dd hh24:mi:ss.ff9') and TO_DATE(?,'syyyy-mm-dd hh24:mi:ss').

  • The description of the PassThrough general connection attribute in Oracle TimesTen In-Memory Database Reference should include this statement: "Passthrough execution of DDL statements does not result in commits on TimesTen."

  • Nullable foreign keys can result in rows without a corresponding parent row. The rows may become stale and may not be refreshed properly through a manual refresh or autorefresh operation. They may not get removed through unload or aging operations, and they may not be updated on Oracle through a flush statement.

  • When using IMDB Cache, the following JDBC methods are not supported with Oracle pass-through modes 1 through 3: PreparedStatement.setAsciiStream(), PreparedStatement.setUnicodeStream(), PreparedStatement.setBinaryStream(), PreparedStatement.setCharacterStream().

6.11 TimesTen integration with Oracle Clusterware

  • When you perform one of these actions:

    • Answer the prompt for which host should be designated as the host for the active database.

    • Enter the ttCWAdmin -create command.

    You receive the message:

    "Warning!! Data store on host(s) host list may be destroyed in Order to be duplicated from active after the roll out. Please back up this data store manually if necessary, before executing ttCWAdmin -start".

    If a database with the specified DSN exists on the host for the standby database, the old database will be destroyed and replaced with the database that is created by the ttCWAdmin -create command.

    The warning has no meaning if there is no database with the specified DSN on the standby host.

  • The TimesTen integration with Oracle Clusterware is not available on these platforms: Solaris 32-bit SPARC, HP-UX PA-RISC, HP-UX Itanium 32-bit, AIX 32-bit, Linux Itanium and Windows 64-bit.

  • Spurious internal errors in the logs may be generated during TimesTen Clusterware operations. These errors are benign. Run ttCWAdmin -status to verify the status of the system.

6.12 TimesTen to TimesTen Replication

  • Cross-release replication and migration from a database that does not have manual parallel replication enabled to a database that does have manual parallel replication enabled does not work when one of the databases is release or Migration from a database without manual parallel replication to a database with manual parallel replication is possible for the following release combinations:

    • Before to

    • Before to or later

    • or later to or later

    To migrate from an or database without manual parallel replication to a database with manual parallel replication, upgrade each database to without manual parallel replication first.

  • Replication for an altered table can fail if the replication agent is stopped immediately after the ALTER TABLE statement has been issued and the agent has not advanced past the end of the ALTER TABLE transaction. This problem can occur regardless of return service policy. If you need to stop the replication agent after an ALTER TABLE transaction, issue a ttRepSubscriberWait call to ensure that the replication agent restart point has advanced beyond the alter table operation.

  • TimesTen can return error message TT6003 when using master-subscriber two-safe replication and autorefresh cache groups. This can occur, specifically, if the first replicated two-safe transaction has either a LOAD CACHE GROUP or an ALTER CACHE GROUP SET AUTOREFRESH STATE operation on an autorefresh cache group. To work around this problem, either avoid doing a LOAD or ALTER on the first replication transaction or use active standby pair replication.

  • Access to the NEXTVAL SQL function of a sequence is not supported in a query on a standby node of an active standby pair.

  • If the first operation in a two-safe user session is an ALTER TABLE operation, the ALTER TABLE is not replicated. The workaround is to do some other operation on the table in the same session before altering the table.

  • Under very rare circumstances, it is possible for a pair of replicated detail tables and their corresponding materialized view to diverge. This divergence can only happen if the materialized view satisfies both of the following conditions:

    • The view definition has two or more predicates.

    • One of the predicates contains an expression that can generate an exception such as numeric overflow, division by zero or string truncation.

    Replicating an update to a detail table can cause divergence if differences in the order of predicate evaluation on the two databases cause a predicate to be evaluated and generate an exception only on the receiving database. The store then rejects the update, resulting in divergence of the detail table and the materialized view. To prevent such divergence, users should avoid replicating materialized views that have predicates that can generate exceptions during expression evaluation. The SQL CAST operator can be used in some cases to avoid arithmetic overflow.

  • Foreign key and uniqueness constraints cannot be checked at the statement level if ttXlaApply is used to implement replication.

  • For replication to work efficiently, it must be able to quickly translate host names of peers into IP addresses. For this to happen efficiently on Windows, make sure that a Windows system is set up to query either a valid WINS server or a valid DNS server that has correct information about the hosts on the network. In the absence of such servers, static HOST-to-IP entries can be entered in either a %windir%\system32\drivers\etc\hosts or %windir%\system32\drivers\etc\lmhosts file.

    Without any of these four options, a Windows system resorts to broadcasting, which is extremely slow, to detect peer nodes. Also, if the Windows system cannot communicate with a defined WINS server or DNS server, or if incorrect information is stored on those servers, the hostname resolution will be extremely slow. Use the ping command to test whether a host can be efficiently located. The ping command should immediately respond if host name resolution is set up properly.

  • When changing the state of a replication receiver (that is, to start or stop) when replication has been configured to use a secondary IP address, a misconfiguration of the /etc/hosts file may cause ttRepAdmin to print the error: Alter replication with 'ALTER REPLICATION...port 0' failed: TT0907: Unique constraint (REPSTORESIX) violated. This error is caused by replication not recognizing the local database. This situation can be confirmed by the following query:

    SELECT * FROM ttrep.ttstores WHERE is_local_store <> 0x0;

    If this query returns no rows, or returns a row with the main host name of the database set to the result of the hostname command rather than the host you specified, you have encountered a configuration problem with /etc/hosts.

    To correct the problem, you must make sure that the special host name you are using is defined in /etc/hosts and that there is an IP address in common between your special host name and the result of the hostname command.

    Example: your hostname command returns softswitch and your system has two Ethernet cards with the addresses and Then the IP addresses defined for softswitch should include both IP addresses.

6.13 SQL*Plus

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

6.14 SQL, utilities and procedures

  • Timesten does not update the following statistics because of scalability issues caused by updating them frequently: db.table.rows_read, db.table.rows_inserted, db.table.rows_updated, db.table.rows_deleted, db.index.hash.inserts, db.index.hash.deletes, db.index.hash.rows_fetched.count, db.index.range.inserts.count, db.index.range.deletes, db.index.range.updates, db.index.range.rows_fetched.count, db.index.temporary.rows_fetched.count.

  • Executing a query against multiple outer joins with the set operators UNION, MINUS or INTERSECT can result in abnormal termination. To work around this problem, define a view to encapsulate each of the outer joins. Then execute the query against the views.

  • When using scalar functions that accept TIME, DATE or TIMESTAMP data types as arguments, you must prefix the function with a literal indicating the data type. For example:

    SELECT GREATEST (TIME '10:10:10', TIME '12:12:12' ) FROM DUAL; 

    If you do not specify the datetime literal, TimesTen treats the data type as CHAR. Functions that accept datetime literals as arguments are: GREATEST, LEAST, ROUND and ADD_MONTHS.

  • The ORDER BY clause is not supported in a CREATE TABLE AS SELECT statement.

  • 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.

  • SQL query strings 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 query to avoid non-database character set characters in the query text.

  • The TO_CHAR SQL function provides inconsistent results (truncates or rounds) when applied to BINARY_FLOAT and BINARY_DOUBLE values. TO_CHAR also truncates some NUMBER values that should instead be rounded.

  • If an application process on HP-UX is connected to a TimesTen database and if the application process calls the ttXactIdRollback utility API for a transaction associated with the same database, the call may fail due to the inability to attach to the shared memory segment for the database.

  • The fourth argument (stats) to the ttOptSetColIntvlStats built-in procedure is a compound structure that cannot be parameterized using ODBC functions. This means that a statement such as the following fails:

    SQLPrepare(hstmt, "call ttOptSetColIntvlStats('t1', 'c1', 1, ?)", SQL_NTS);

    Similarly, the ttIsql describe command fails because the "stats" argument does not have one of the known types.

6.15 TTClasses

  • A problem with TTClasses causes NCHAR or NVARCHAR2 parameters and columns to be bound incorrectly. This results in parameter and column data being transferred to or from the database without a null terminator.

  • When recompiling TTClasses on AIX 5.3, ensure that the C++ compiler is at least version 8, patch release 13 (8-feb2007). Older versions may cause programs to fail to connect to TimesTen.

6.16 Client/Server

  • In the Windows ODBC Client DSN Setup dialog box, when the Server Name refers to a UNIX host, the Refresh button to get the list of DSNs on that server sometimes fails to obtain the list. Enter a known DSN in the Server DSN field to create the client DSN entry successfully. TimesTen connections from Windows using that client DSN work normally.

  • When setting multiple client connections to a TimesTen server, do not set the stack size (using the -ServerStackSize daemon option or ServerStackSize attribute) to less than 64KB on 64-bit systems and 48KB on 32-bit systems. If the stack size is too small, the TimesTen Server dies with SIGSEGV on most UNIX system, or SIGBUS on HP-UX. The default stack size is 128 KB on 32-bit systems and 256 KB on 64-bit systems.

  • On UNIX, when using ttlocalhost, a client of one TimesTen instance cannot connect with a server of another TimesTen instance. For example, a 32-bit TimesTen client cannot connect to a 64-bit TimesTen server when using ttlocalhost. The workaround is to use ttShmHost (shared memory IPC) or localhost (

  • While using shared memory as IPC, the application may see the error message 24 from the client driver if the application reaches the system-defined, per process file descriptor limit. This may happen during a connect operation to the Client DSN when the shmat system call fails because the application has more open file descriptors than the system-defined per-process file descriptor limit.

7 Contacting support

For information about obtaining technical support for Oracle TimesTen products, go to the following Web address:

8 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

Oracle TimesTen In-Memory Database Release Notes, Release 11.2.1


Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.