Skip Headers
Oracle® TimesTen In-Memory Database Release Notes
11g Release 2 (11.2.2)

E21630-49
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

  View PDF

Oracle® TimesTen In-Memory Database

Release Notes

11g Release 2 (11.2.2)

E21630-49

November 2013

This document provides late-breaking information for TimesTen 11.2.2.6.0, 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

http://www.oracle.com/technetwork/products/timesten/documentation/

Information about TimesTen 11.2.2 releases before 11.2.2.3.0 can be found at

http://www.oracle.com/technetwork/products/timesten/documentation/1122-historic-1886173.html

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/ in the installation, if you opted to install the TimesTen Documentation.

This document contains the following sections:

1 Changes in this release

This section lists changes between releases:

1.1 Changes for Release 11.2.2.6.0 from Release 11.2.2.5.0

Changes in this release include:

1.1.1 New Features

  • You can cancel and cleanly stop a ttLoadfromOracle operation with either the SQLCancel(hstmt) ODBC function or by pressing Ctrl-C in the ttIsql utility. For more information, see the Oracle TimesTen In-Memory Database Operations Guide.

  • You can manage the size of the transaction commit buffer for the cache agent used to process autorefresh. You can also manage the size of the transaction commit buffer for the replication agent when using an active standby pair replication scheme that includes autorefresh cache groups. For more details, see the Oracle In-Memory Database Cache User's Guide and the Oracle TimesTen In-Memory Database Reference.

  • This release includes the ttDbWriteConcurrencyModeSet and ttDbWriteConcurrencyModeGet built-in procedures. These procedures provide control over read optimization during periods of concurrent write operations. For more details, see the Oracle TimesTen In-Memory Database Operations Guide and the Oracle TimesTen In-Memory Database Reference.

  • Support is added for constant expressions, dynamic parameters, and null values in the values lists used for IN, ANY, SOME, or ALL. For more information, see the Oracle TimesTen In-Memory Database SQL Reference.

1.1.2 Bug Fixes

  • In previous releases, users could encounter an unexpected full autorefresh of readonly cache groups, due to truncated autorefresh change log tables. This has been fixed. (Bug DB 12331763)

  • A problem is fixed where the TimesTen Windows installer did not include the TimesTen JDBC .jar files. (BugDB 12385810)

  • In previous releases, TimesTen returned the wrong information in error message TT16045 when a user specified the ttRepAdmin -duplicate command without specifying the -localhost option. In this release, TimesTen returns useful and correct information in the error message. (Bug DB 12401395)

  • A problem existed where the documented path for the snmp.ini file was incorrect. In this release, the snmp.ini file is in install_dir/info/ on UNIX systems and install_dir\srv\info\ on Windows platforms. (BugDB 13546123)

  • A problem is fixed where certain join queries that contained a FIRST 1 or a FIRST N clause would take a long time to complete. (BugDB 16171204)

  • A CREATE ACTIVE STANDBY PAIR statement could fail on an asynchronous writethrough subscriber, when the replication scheme included a fail threshold and there was a backlog in the transaction log. This is fixed. (BugDB 16292638)

  • In previous releases, users were required to drop a Clusterware-managed active standby pair when changing the cache administrator or cache user password. In this release, you do not need to drop the active standby pair. The procedure for changing the cache administrator and cache user passwords is documented in the Oracle TimesTen In-Memory Database Replication Guide. (BugDB 16364233)

  • In previous releases, when the timeout value was too small in an active standby pair scheme that contained an asynchronous writethrough cache group, large transactions could cause the transmitter to fail without restarting immediately. In this case, writethrough to the Oracle database would not occur. This is fixed. (BugDB 16419027)

  • In previous releases, an assertion failure could occur in a TRUNCATE TABLE operation. This is fixed. (BugDB 16536874)

  • A problem is fixed where an assertion failure could occur with a SELECT query with the analytical function ROW_NUM, DENSE_RANK or RANK. (BugDB 16629624)

  • A problem is fixed where TimesTen changed the column names in the output of a query that contained an ORDER BY clause. (BugDB 16714127 and 17021410)

  • A problem is fixed where a query executed after calling the built in procedure ttIndexAdviceCaptureStart(1,0) would incorrectly return TimesTen error 805. (BugDB 16729095)

  • A deadlock could occur when an uncommitted foreign key value was updated while concurrently deleting one or more rows from the parent table. This is fixed. (BugDB 16805039)

  • A problem is fixed that could cause a uniqueness violation when a unique value that had been deleted was reused in the same transaction. (BugDB 16805056 and 16805068)

  • A performance regression for hash indexes that was seen in releases 11.2.2.4.4 and greater has been fixed. (BugDB 16818440)

  • Performance for queries involving left outer joins is improved in this release. (BugDB 16820660, 16843298 and 16895481)

  • This release includes diagnostics to gather more information on a spinlatch assertion. (BugDB 16855677)

  • When managing more than two applications with Oracle Clusterware, TimesTen would return a large number of error messages incorrectly. This is fixed. (BugDB 16859952)

  • In previous releases, when automatic client failover happened in the middle of a transaction, uncommitted updates from before the failure were silently discarded when the new connection was made. In this release, applications must specify the attribute RollbackRequiredOnFailover=1 in the client connection string, instead of the client DSN entry. TimesTen reports the potential loss and asks the application to roll back the transaction before proceeding. (BugDB 16892906)

  • In previous releases, an assertion failure could occur when a complex query created a temporary index on a base table. This is fixed. (BugDB 16892974)

  • A DELETE subquery could cause an out of temporary space error. This is fixed. (BugDB 16921854)

  • A deadlock error could occur during a dynamic load of a local dynamic cache group that had an aging policy defined on it. This is fixed. (BugDB 16928152)

  • A problem is fixed where the replication agent CPU usage could spike after the state of the subscriber was set to STOP. (BugDB 16951511 and 17246933)

  • If a latch assertion occurs, we now collect further information in the .inval file to help diagnose the root cause of the assertion. (BugDB 16955266)

  • TimesTen returns error message 15105 when a user other than the instance administrator attempts to create a database. The error can occur when there is a mismatch between the user ID and the password entered when the user attempts to create the database. In this release, the text for TimesTen error message 15105 is improved to better explain the cause of the error. (BugDB 16963720)

  • Daemon log messages for cache groups now contain the name of the cache group when the cache group is altered. (BugDB 17038478)

  • A problem is fixed where an assertion failure could occur during recovery of a database that contained tables with compressed columns. (BugDB 17038539 and 17038634)

  • A latch assertion failure could occur when an INSERT was made into a table that had a non-unique hash index after an application was killed or died during a SELECT operation on the same table. This is fixed. (BugDB 17039444)

  • An integer overflow could occur when using out-of-line columns. This is fixed. (BugDB 17047291)

  • A problem has been fixed where a SELECT query with a left outer join could result in a segmentation fault. (BugDB 17321103)

  • In previous releases, when specifying the -numthreads option with the ttMigrate utility when restoring a database that contained a replication scheme, TimesTen could return a TimesTen 8151 error. This is fixed. (BugDB 17056944)

  • An assertion failure could occur during a query that did an implicit data type conversion on a column that had a unique index. This problem is fixed. (BugDB 17259103)

  • A problem is fixed that could result in database incompatibility after adding a new subscriber to an existing replication scheme. (BugDB 17321440)

  • The following daemon log message would not print correctly: Could not find user count row for table tablename in CACHE_ADMIN.TT_06_LOG_SPACE_STATS. Any autorefreshed cache group containing table tablename will not be refreshed. This is fixed. (BugDB 17348602)

  • A core dump could occur with a client server application that connected, disconnected and did queries from multiple threads. This is fixed. (BugDB 17413183)

  • A problem is fixed where a query could return the wrong result when using out-of-line data types in a nested GROUP BY clause. (BugDB 17421433)

  • Dropping a read only cache group without first excluding it from an active standby pair replication scheme would cause an assertion failure. Now, TimesTen returns an error if a user attempts to drop the read only cache group before excluding it from the active standby pair replication scheme. (BugDB 17484944 and 17484956)

  • Timesten error 3017 would be issued when creating a table with a foreign key with ON DELETE CASCADE on a database containing an active standby pair replication scheme. This error should not be issued when DDLReplicationLevel is 2. This is fixed. (BugDB 17504656 and 17504720)

  • An assertion failure could occur for a query that used a subquery with aggregate or rownum. This is fixed. (BugDB 17512072)

  • This release includes some improvements to transaction list handling in the replication transmitter to avoid performance issues when a backlog is being processed in a bi-directional replication scheme. (BugDB 17554372)

  • A problem is fixed where the TimesTen installer would incorrectly determine that a port was already in use when configuring the TimesTen daemon or TimesTen Server. (BugDB 17576641)

  • A problem has been fixed where an UPDATE operation would run slowly and then fail with a constraint violation. (BugDB 17579344)

  • A problem is fixed where the status of the standby database in an active standby pair replication scheme changed to IDLE after migration using the ttMigrate utility. (BugDB 17577970 and 17577929)

  • The cache agent could falsely report the following error: The sequence number for table tablename had changed but the table was not refreshed. The cache group in data store database_name is out of sync. This is fixed. (BugDB 17610433)

  • An assertion failure could occur when one connection was trying to access a column with an index on it while another connection was altering the index. This is fixed. (BugDB 17641951)

  • A problem has been fixed where a SELECT query with multiple large IN clauses could run very slowly. (BugDB 17748750)

  • In previous releases, an assertion failure could occur with queries that contained a UNION subquery. This problem no longer occurs. (BugDB 17790311)

1.2 Changes for Release 11.2.2.5.0 from Release 11.2.2.4.5

Changes in this release include:

1.2.1 Behavior Changes

  • Beginning in Release 11.2.2.2.0, the PreparedStatement.setBoolean (int parameter, false) method sets the specified column to 0 irrespective of the data type. In previous releases, PreparedStatement.setBoolean (int parameter, false) set CHAR/VARCHAR/NCHAR/NVARCHAR columns to NULL.

  • In this release, the default TABLE DEFINITION CHECKING setting for databases in a replication scheme changes from the current default of EXACT to RELAXED.

  • In previous releases, TimesTen checked that all AWT cache groups had matching unique indexes and unique constraints with the corresponding Oracle database tables. If there were any missing constraints, TimesTen did not allow propagation to the Oracle database.

    In this release, TimesTen checks that all AWT cache groups have matching unique constraints and foreign key constraints with the corresponding Oracle database tables. If there are any missing constraints, TimesTen issues a warning and propagation to Oracle occurs automatically. However, updates to these TimesTen AWT cache group tables with the missing constraints are serially applied to the Oracle database, rather than being applied in parallel.

    You can manually initiate a check for missing constraints with the ttCacheCheck built-in procedure. See Oracle In-Memory Database Cache User's Guide and Oracle TimesTen In-Memory Database Reference.

1.2.2 New Features

1.2.2.1 Performance Enhancements
  • TimesTen has added the CommitBufferSizeMax connection attribute to allow users to configure the size of the transaction commit buffer to improve the performance of commit or rollback of large transactions. See details about the ttCommitBufferStats and ttCommitBufferStatsReset built-in procedures and the CommitBufferSizeMax connection attribute in the Oracle TimesTen In-Memory Database Reference. Also see the Oracle TimesTen In-Memory Database Operations Guide. See the Oracle TimesTen In-Memory Database SQL Reference for information on settings in the ALTER SESSION statement.

  • TimesTen now supports B-tree indexes. B-tree indexes and T-tree indexes both are referred to as Range Indexes. In some cases, B-tree indexes offer concurrency advantages over T-trees. The RangeIndexType data store connection attribute determines whether user-created range indexes are T-tree indexes or B-tree indexes. For details, see the Oracle TimesTen In-Memory Database SQL Reference and the Oracle TimesTen In-Memory Database Operations Guide for details.

  • In previous releases, TimesTen only supported hash indexes on primary key columns. You can use the CREATE [UNIQUE] HASH INDEX statement to create a hash index on the columns specified. For details, see the Oracle TimesTen In-Memory Database SQL Reference.

  • You can perform multiple concurrent inserts on table that has compressed columns. In previous releases, TimesTen held a table lock on tables that contained compressed columns, allowing only single inserts on these tables. For more information on compressed tables, see the Oracle TimesTen In-Memory Database SQL Reference.

1.2.2.2 Performance Monitoring
  • A new utility, ttStats, provides the ability to monitor TimesTen database activities. The ttStats utility supports real-time monitoring, capturing snapshots of system statistics, and generating user-friendly HTML reports for performance analysis. In addition, a new PL/SQL package TT_STATS is available for custom development of monitoring functions. The ttStats utility is a stand-alone facility for the TimesTen database. It is a complementary utility to the Enterprise Manager Plugin for TimesTen. See the Oracle TimesTen In-Memory Database Reference and the Oracle TimesTen In-Memory Database PL/SQL Packages Reference.

  • There is a new option, -logAnalyze, in the ttXactLog utility that analyzes the pending log records to be transmitted from the master to any receivers. This is useful, for instance, to determine how much is left to be replicated from a transmitter to a given receiver. See the Oracle TimesTen In-Memory Database Reference and the Oracle TimesTen In-Memory Database Operations Guide.

  • TimesTen added the ability to measure and display the execution time of SQL statements through the new built-in procedure ttSQLCmdCacheInfo2. For details, see the Oracle TimesTen In-Memory Database Reference and the Oracle TimesTen In-Memory Database Operations Guide.

1.2.2.3 Cache and Replication
  • The built-in procedure ttDBConfig supports a new parameter, CacheParAwtBatchSize. This parameter configures the maximum number or rows included in a single batch. The ability to configure the number of rows is useful for propagating large numbers of rows to the Oracle database from an AWT cache group. See the Oracle TimesTen In-Memory Database Reference.

  • TimesTen could potentially run out of temporary or permanent space when applying a large incremental autorefresh transaction. For these situations, you can configure an autorefresh transaction limit, where the large amount of data is broken up, applied, and committed over several smaller transactions. See ttCacheAutorefIntervalStatsGet and ttCacheAutorefreshXactLimit in the Oracle TimesTen In-Memory Database Reference. Also, see the Oracle In-Memory Database Cache User's Guide.

  • Users can manually initiate a check for missing constraints in AWT cache groups with the ttCacheCheck built-in procedure. See the Oracle In-Memory Database Cache User's Guide and the Oracle TimesTen In-Memory Database Reference.

  • Users can call the ttCacheAutorefreshLogDefrag built-in procedure to compact the trigger log space for a cache autorefresh table. See the Oracle TimesTen In-Memory Database Reference.

  • To prevent an unload operation from becoming a very large transaction, use the new COMMIT EVERY n ROWS clause in the UNLOAD CACHE GROUP statement to specify a commit frequency. See the Oracle TimesTen In-Memory Database SQL Reference and the Oracle In-Memory Database Cache User's Guide.

  • Oracle Database execution errors logged to the awterrs text file can now also be written in XML format. For more details, see Oracle In-Memory Database Cache User's Guide.

  • TimesTen has enhanced dynamic load of cache groups to handle more conditions. For more details, see the Oracle In-Memory Database Cache User's Guide.

  • You can specify the TABLE DEFINITION CHECKING clause as a StoreAttribute for both the CREATE ACTIVE STANDBY PAIR and the ALTER ACTIVE STANDBY PAIR statements. For details, see the Oracle TimesTen In-Memory Database SQL Reference.

1.2.2.4 SQL
  • TimesTen now supports statement level inline optimizer hints. See the Oracle TimesTen In-Memory Database SQL Reference and the Oracle TimesTen In-Memory Database Operations Guide for details.

  • For the WITH clause in the top-level query, you can now specify the set operator UNION, MINUS or INTERSECT. For details, see the Oracle TimesTen In-Memory Database SQL Reference.

  • You can specify the keyword ENABLE as part of the NOT NULL constraint in a column definition in a CREATE TABLE statement. For details, see the Oracle TimesTen In-Memory Database SQL Reference.

  • You can specify more than one subquery in the SET clause of the UPDATE statement. You can also specify a SELECT DISTINCT subquery in the SET clause of the UPDATE statement. For details, see the Oracle TimesTen In-Memory Database SQL Reference.

  • The DISTINCT modifier is now allowed in scalar subqueries.

  • A certain class of assertion errors that can occur during SQL compilation have been restructured from errors that invalidate the database to internal errors that only affect the statement that encountered the problem. These errors use the TT4053: Internal Error message. They are logged in the file database.assert in the same directory as the checkpoint files.

1.2.2.5 Operations
  • You can configure a range for all shared memory keys used by TimesTen with the -shmkeyrange daemon option. For details, see the Oracle TimesTen In-Memory Database Operations Guide.

1.2.3 Tools for Proof of Concepts

  • A new utility, ttImportFromOracle, analyzes the source tables in an Oracle database and generates scripts for importing the tables into a TimesTen database. It recommends space-efficient data types and compression candidates to reduce the memory requirement for storage in the TimesTen database. It also generates an optimized loader script that performs data loading in parallel. See the readme file ttImportFromOracle.pdf in the install_dir/support directory for details.

1.2.4 Bug Fixes

  • In previous releases, TimesTen did not check for disallowed characters in DSN names. In this release, TimesTen checks DSN names for disallowed characters and returns an error if any are found. (BugDB 9454764)

  • This release includes a new SNMP trap, ttRepStateChange, to track replication agent state changes in the case of active standby pairs. (BugDB 11061633)

  • In previous releases, when the replication agent applied changes from a remote node, if it ran into locking errors, it would treat the error as a permanent error and discard the transaction it was applying. This has been fixed to treat locking error as a transient error. (BugDB 13837176)

  • A problem is fixed where repeatedly calling a PL/SQL anonymous block with identical source text but parameters of different sizes could lead to excessive consumption of PL/SQL Shared Memory. (BugDB 14139020)

  • If the PL/SQL shared memory segment was full at connection time, additional memory was leaked. This problem is fixed. (BugDB 14271697)

  • A potential hang was fixed in TTClasses that could occur when an error was thrown during the TTConnectionPool::freeConnection method. (BugDB 14558534)

  • With a bi-directional replication scheme where only one store is receiving updates, transaction log files can build up on the receiving store if the transmitter on that store falls behind. In addition to the buildup of log files you may also see the transmitter thread(s) restarting periodically. The chances of encountering this issue can be reduced by:

    • Ensuring your workload doesn't exceed a rate that is sustainable by replication

    • Increasing the replication timeout parameter for the store

    • Configuring the largest log buffer that you can with the connection attribute LogBufMB

    These configuration changes allow the transmitter thread on the receiver to process the backlog as quickly as possible. (BugDB 14700079)

  • When a log file was deleted under certain conditions, replicated XLA would run into a memory leak and output an error message referencing an incorrect log file. Both the problem that generated the error and the incorrect error message are fixed. (BugDB 14713045)

  • Built-in procedures that take a table name as an input parameter might trigger an assertion when executed. Such built-ins include ttSize, ttOpStatsExport, and ttAgingScheduleNow. This problem is fixed. In this release, in the case of a problem, TimesTen returns an error. (BugDB 14750394)

  • In previous releases, for active standby pairs managed by Oracle Clusterware, in a failover scenario, propagation to Oracle would take a long time or fail after the standby database became the active database. This problem is fixed. (BugDB 14788796 and 14794358)

  • A bug was fixed which could cause a segmentation violation when a TTCmd object was prepared with a SQL statement that referenced a non-existent table or object. In this release, TimesTen returns an error message. (BugDB 15846108)

  • A problem with TTClasses TTConnectionPool class was fixed where, if a warning occurred while connecting to the database (SQL_SUCCESS_WITH_INFO), the connection would be left unusable in the connection pool. (BugDB 15873607)

  • In previous releases, the SYS.REPSTATS table would use more space than necessary, when there were many subscribers in the replication scheme. The problem is fixed. (BugDB 15933219)

  • Error messages encountered by the ttCWAdmin utility are improved in this release. (BugDB 15967128)

  • The performance of very large inserts in a master-master replication scheme is improved in this release. (BugDB 16077275)

  • In previous releases, after a master-master replication scheme was backed up and restored, using the ttBackup and ttRestore utilities, and the replicated pair was rebuilt using the ttRepAdmin -duplicate command, replication of transactions from the recovered master to the cloned master would proceed normally, but replication of transactions from the cloned master back to the original master would fail. This is fixed. (BugDB 16163788)

  • A problem is fixed where a table would appear to have either a corrupt row or index and access to certain rows failed with a segmentation fault. (BugDB 16222279)

  • An error in ttBulkCp error-handling code had the potential of causing a crash. This would happen when a non-ttBulkCp error appeared, for example a space exhausted error from ODBC. This problem is fixed. (BugDB 16239651)

  • After a TRUNCATE TABLE operation was terminated, cleanup and rollback of the operation would hang. This is fixed. (BugDB 16248444)

  • When using a multi-threaded server, the connection information was not properly associated with the client information, resulting in ttXactadmin reporting the wrong client machine for a transaction. This is fixed. (BugDB 16341580)

  • For UNIX systems, a problem is fixed where a client failover thread could crash if there were too many open file descriptors. (BugDB 16388256)

  • The grantCacheAdminPrivileges.sql is a script that is used to grant privileges on the Oracle database for the cache administrator. It granted CREATE ANY TYPE privilege when CREATE TYPE is sufficient. This is fixed. (BugDB 16390772)

  • An outer join query could return incorrect results if its inner table was a derived table with a SET operator and there was a non-join predicate on this derived table. This is fixed. (BugDB 16417289)

  • A problem is fixed where optimizer statistics were recorded incorrectly. (BugDB 16444228)

  • A rollback assertion on a replication subscriber could occur due to a temporary space transient error. This is fixed. (BugDB 16477586)

  • In this release, TimesTen returns error messages instead of assertions within the autorefresh validation code. In addition, the user can turn off autorefresh validation. (BugDB 16522421)

  • A problem has been fixed where a segmentation fault could occur when running a query with a subquery that contained an aliased analytic function column that was referenced in a WHERE clause but was not referenced in the selected columns. (BugDB 16531241)

  • A problem has been fixed where autorefresh cache groups that had more than 67 tables could cause a buffer overflow. (BugDB 16545934 and 16576353)

  • The very first call to setNull(int parameterIndex, Types.NULL) for DATE/TIMESTAMP fields would throw a restricted data type attribute violation. This is fixed. (BugDB 16619476)

  • A problem has been fixed where an assertion failure would occur if a table alias name was used. (BugDB 16628096)

  • In previous releases, the TimesTen startup file set the PATH variable to include the current directory. In this release, the startup script does not set the PATH variable. (BugDB 16684936)

  • In previous releases, when the cache agent stopped because it encountered an Oracle database error, the cache agent might not restart and no error would be thrown. This problem is fixed.(BugDB 16748309)

1.3 Changes for Release 11.2.2.4.5 from Release 11.2.2.4.4

  • A problem has been fixed where log files that were required by XLA were deleted prematurely. (BugDB 16543915)

  • A problem has been fixed where autorefresh cache groups that had more than 67 tables could cause a buffer overflow. (BugDB 16545637)

1.4 Changes for Release 11.2.2.4.4 from Release 11.2.2.4.3

  • A problem has been fixed where a cache group with many tables with long names could run into an assertion failure. (BugDB 16421159)

  • Operations such as cache autorefreshes that involve hash index lookups with deletes could get stuck in an infinite loop. This has been fixed. (BugDB 16436238)

1.5 Changes for Release 11.2.2.4.3 from Release 11.2.2.4.2

  • A problem has been fixed where needed transaction log files could be purged before transaction completion. This would have been observed as TimesTen error 649 “Log file has been purged” or possibly as an assertion from sbLogLRInfoRead. (BugDB 16285968)

1.6 Changes for Release 11.2.2.4.2 from Release 11.2.2.4.1

  • Under certain conditions after a restart of the replication agent, parallel replication would not make progress waiting for a dependent thread to commit. (BugDB 14700913)

  • A problem was fixed that prevented ODP.NET from connecting to TimesTen when using the ODP.NET 11.2.0.3.0 release with TimesTen 11.2.2.4.1. Either the connect or disconnect request would cause a fatal exception. This is fixed in 11.2.2.4.2 and ODP.NET 12.1 is not affected. (BugDB 14822105)

1.7 Changes for Release 11.2.2.4.1 from Release 11.2.2.4.0

  • An assertion failure that could occur with a large query that contained many complex CASE expressions has been fixed. (BugDB 14464140)

  • A problem is fixed where TimesTen would attempt to allocate an unnecessarily large amount of temporary space for hash-based GROUP BY queries, given only basic cardinality estimates. (BugDB 14634954)

  • A problem has been fixed where calls to some C utility library functions failed with TimesTen error 799 "Unable to connect to daemon; check daemon status" under certain conditions. The utility library functions that failed in this way were ttBackup, ttRamGrace, ttRamLoad, ttRamPolicy, ttRamUnload, and ttXactIdRollback. (BugDB 14676269)

  • In previous releases, TimesTen reported the daemon log message "sbLogFilesRemove: log file XXXX does not exist " when TimesTen cleaned up transaction log files as part of the TimesTen checkpoint operation. In this case, some log files that had previously been removed correctly were incorrectly marked for removal again during the checkpoint operation. This issue is fixed. (BugDB 14697667)

  • A problem has been fixed where, under specific conditions, the system appeared to hang as a result of an incorrect range of transaction log files being queued to be cleaned up during transaction log cleanup operations. The problem manifested itself by emitting a large number of the daemon log messages: "sbLogFilesRemove: log file .logXXX does not exist" (BugDB 14763756)

  • A problem has been fixed with TimesTen OCI that could cause a segmentation violation when calling a PL/SQL procedure or anonymous block that contains an OUT or IN/OUT parameter as the last parameter. (BugDB 14764365)

1.8 Changes for Release 11.2.2.4.0 from Release 11.2.2.3.5

Changes in this release include:

1.8.1 New Features

  • This release contains an Index Advisor that can be used to recommend a set of indexes that can improve the performance of a specific workload. For details, see the Oracle TimesTen In-Memory Database Operations Guide and the Oracle TimesTen In-Memory Database Reference.

  • You can now load a TimesTen table with the result of a query executed on an Oracle database. This feature does not require you to create a cache group. For details, see the Oracle TimesTen In-Memory Database Operations Guide and the Oracle TimesTen In-Memory Database Reference.

  • The TimesTen Cache Advisor provides recommendations on how to initially configure a cache schema, to identify porting issues and to estimate the performance improvement of a specific workload. The Cache Advisor is available on Linux x86-64. For details, see the Oracle In-Memory Database Cache User's Guide and the Oracle TimesTen In-Memory Database Reference.

  • This release contains the built-in procedure ttOptCmdCacheInvalidate that allows you to invalidate compiled statements. For details, see the Oracle TimesTen In-Memory Database Reference.

  • In this release, when performing a ttRepAdmin -duplicate operation, you can specify a local or remote IP address for the destination of the duplicate. For details, see the Oracle TimesTen In-Memory Database Reference and the Oracle TimesTen In-Memory Database Replication Guide.

1.8.2 Bug Fixes

  • In previous releases, if during installation you selected a secondary group for group restricted access and if the main TimesTen daemon is started or restarted by the root user, the daemon incorrectly starts with the primary group permission instead of the secondary group permission.

    This problem could manifest itself in at least one of the following known ways, which may prevent the database from being loaded:

    • TimesTen error 836: Cannot create data store shared memory segment, error error_number

    • An assertion failure, resulting in transaction log files being written: (Assertion failed: 0 [logfile.c:/main/21:sbLogFileCreate:780])

    • TimesTen error 906: Cannot change mode on logfile file_name, error error_details

    This problem is corrected. (BugDB 9966040)

  • When the DROP ACTIVE STANDBY PAIR statements was issued and there was no active standby pair replication scheme, TimesTen was returning error message: 8165: Replication schema is inconsistent. Now, TimesTen returns a more descriptive message: Error 8123: An ACTIVE STANDBY PAIR scheme does not exist. (BugDB 12427319)

  • During replication operations, an SNMP trap is triggered when TimesTen error 16082 is encountered, indicating a table could not be updated. During batch update operations, this trap could be generated for every failed operation, causing heavy SNMP traffic. To prevent this, the error and trap messages have been changed to only report the number of failures that occur within a batch update operation. These messages appear in the support log. (BugDB 13241883)

  • These replication daemon log messages that were previously incorrectly classified as errors now appear as warnings:

    • TT16290: Replication transmitters are stopping.

    • TT16293: Replication thread transmitter is exiting (exitLine line_number)

    • TT16999: Transmitter exiting isAwt

    • TT16999: Receiver exiting isAwt (BugDB 13726055)

  • Previously, when TTC_TIMEOUT was set to 1, SQLQueryTimeout was set to 0. Now, when TTC_TIMEOUT is set to 1, SQLQueryTimeout is also set to 1. See the Oracle TimesTen In-Memory Database Reference for discussion of valid values for these attributes. (BugDB 13796704)

  • This release includes enhanced query optimizations for columns that have numeric, date, time or timestamp types and that do not have a range index. This can improve performance for queries that have a range predicate on such columns. To benefit from this enhancement, you must update statistics. (BugDB 13824787)

  • A problem with computing the column name of a complex view has been fixed. (BugDB 13896607) The problem was manifested in these ways:

    • The ttIsql describe command could show the column name as being empty.

    • A JDBC application could receive a column not found exception when attempting to retrieve a column value from a ResultSet using the column name.

    • The ODBC SQLDescribeCol() function could return incorrect data.

  • In previous releases, when the ttCWAdmin -create command failed due to an error in the generated CREATE ACTIVE STANDBY PAIR statement, the cause was incorrectly identified in the ttCWAdmin output and in the message log as an authentication issue. Also, warnings were treated as errors. Now, when the CREATE ACTIVE STANDBY PAIR statement returns a warning, the active standby pair is created. If the statement generates warnings or errors, now they are displayed in both the output of the call and in the ttcw message log. (BugDB 13907153)

  • A problem is fixed where the replication peer failure state (TT_REPLICATION_INVALID), which is triggered by exceeding the replication threshold, was being reset on a database invalidation or unload. As a result, TimesTen issued the warning TT20100 instead of warning TT8025, after the reload. (BugDB 13915440)

  • Prior to this release, a silent install erroneously prompted the user to enter a server name during a client-only install. This problem is fixed. (BugDB 14057512)

  • A problem has been fixed in which propagation of changes to Oracle from a global cache group could not resume after an active standby failover occurred. (BugDB 14075830)

  • When a member of a grid is detached forcibly, all changes that have not been propagated to Oracle are discarded. In previous releases, global cache groups were unloaded. In this release, local AWT cache groups are also unloaded if any of the changes that were not propagated to Oracle belonged to a local AWT cache group. (BugDB 14076317)

  • TimesTen internal bookkeeping is improved to remove unneeded TimesTen objects left behind in an Oracle database once an autorefresh operation was completed. (BugDB 14115412)

  • A problem has been fixed in TimesTen support for Oracle Clusterware where, under certain conditions, the system would fail and trigger a failover when a user ran the ttCWAdmin -beginAlterSchema command and then ran the ttCWAdmin -status command before running ttCWAdmin -endAlterSchema. (BugDB 14217556)

  • A problem was fixed where the execution of a SQL statement would terminate unexpectedly when referencing a view in a derived table clause, if the view definition contained both a derived table and an ORDER BY clause. (BugDB 14127716)

  • When describing a table using the previous TimesTen 11.2.2 releases of ttIsqlCS and connecting to a TimesTen 11.2.1 instance, the describe command would attempt to access a non-existent column NUMCOMPRESS. This has been corrected. (BugDB 14157399)

  • A problem is fixed where attempting to add a subscriber to an existing replication configuration could result in the deadlock error TT6002. (BugDB 14179123)

  • A problem is fixed where a core dump could occur on the TimesTen server when using an automatic client failover configuration with Oracle Clusterware. The problem could occur even when the server was idle. (BugDB 14181234)

  • In rare instances, an assertion failure could invalidate the database when logs were being flushed to disk while concurrent operations were taking place in the database. (BugDB 14220901)

  • In previous releases, creating a temporary LOB outside a transaction would cause TimesTen to create a transaction that would be left open indefinitely. In this release, that transaction is committed when the temporary LOB is freed. (BugDB 14227570)

  • A message with AWTBatchId details (curAwtBatchId, awtBatchIdAtCrCGTime, awtXactsInBatch, awtStmtsInBatch) was being logged as an error although it might not indicate a problem. This message is now logged at the information level in the support log. (BugDB 14253983)

  • If the PL/SQL shared memory segment was full at connection time, additional shared memory was leaked. The problem has been corrected. (BugDB 14275478)

  • A problem has been fixed where ODP.NET 11.2.0.3 clients that connect to the TimesTen 11.2.2.3 server could fail due to an access violation. (BugDB 14331111)

  • A scalar subquery that contained an Oracle style outer join (+) on a derived table could return the wrong results. This has been corrected. (BugDB 14353684)

  • A problem has been fixed where an assertion failure would occur when a wrong data type was used in an INSERT SELECT statement with a UNION clause on a derived table. (BugDB 14369779)

  • When the active host of a TimesTen cluster configuration that used VIPs was rebooted, the standby host correctly became the active, but the original active host did not become the standby. This has been corrected. (BugDB 14372540)

  • The ttBulkCP utility could use too much permanent space during inserts, if it encountered uniqueness constraint violations. This problem is corrected. (BugDB 14373510)

  • A problem has been fixed where an assertion failure could occur in the TimesTen function sbMapIx_t when updating data. (BugDB 14379300)

  • If ttBackup is run when the database is being loaded and undergoing recovery, the user credentials cannot be checked. Previously TimesTen returned an internal "encrypt failed" error. Now TimesTen returns a more meaningful error. (BugDB 14458502)

  • A problem was fixed in the initCacheAdminSchema.sql script where creating an asynchronous writethrough cache group could cause an Oracle constraint violation and return TimesTen error message 5222. You must run the new version of this script to fix the problem. (BugDB 14511714)

  • A problem was fixed where a literal might be internally cast to an incorrect type when a SQL statement compared a column of TT_BIGINT data type with a string literal. (BugDB 14549475)

  • A potential hang was fixed in TTClasses that could occur when an error was thrown during the TTConnectionPool::freeConnection method. (BugDB 14558534)

  • Use of the built-in ttReplicationStatus can lead to lock timeouts in the replication agent. The effect of this is more pronounced when parallel replication is in use. The locking system that ttReplicationStatus uses has been adjusted so that it does not interfere with the replication agent. (BugDB 14582429)

  • Under certain conditions, executing SELECT statements in the PL/SQL package DBMS_SQL could return columns in the wrong order. This has been corrected. (BugDB 14583425)

  • Specifying multiple Oracle Clusterware managed applications for an active standby pair in the cluster.ini file resulted in a ttCWAdmin utility failure and inconsistent TimesTen Oracle Clusterware resources. This problem has been corrected. (BugDB 14621564)

1.9 Changes for Release 11.2.2.3.5 from Release 11.2.2.3.4

  • A problem is fixed where a SELECT operation could result in unnecessary dynamic loads of data from Oracle that already existed in the TimesTen cache group. This problem occurred when the workload included DML operations. (BugDB 14533454)

1.10 Changes for Release 11.2.2.3.4 from Release 11.2.2.3.3

  • A problem is fixed where a SELECT operation could result in multiple dynamic loads of data from Oracle. (BugDB 14499661)

  • A problem is fixed where the statistics for a local dynamic cache group were incorrectly reported in the sys.systemstats table as statistics for a global dynamic cache group. (BugDB 14504836)

1.11 Changes for Release 11.2.2.3.3 from Release 11.2.2.3.2

  • Previously, dynamic loads could be done only for queries with equality conditions on all columns in primary keys or on all columns in unique indexes. Now, dynamic loads will also be done with a mixture of equality or "is null" conditions on all columns in unique indexes provided that at least one equality condition is used.For more details on dynamic loads, see "Dynamically loading a cache group" in the Oracle In-Memory Database Cache User's Guide. (BugDB 14462078)

    For example:

    CREATE DYNAMIC ASYNCHRONOUS WRITETHROUGH CACHE GROUP cg FROM t1(x1 INT PRIMARY KEY, y1 INT, z1 INT);

    CREATE UNIQUE INDEX u1 ON t1(y1, z1);

    The following queries dynamically load data because all columns of the index are qualified with either an IS NULL condition or an equality with a constant or argument, and at least one column is qualified with an equality condition.

    SELECT * FROM t1 WHERE y1 IS NULL and z1=1;

    SELECT * FROM t1 WHERE y1=1 AND z1 IS NULL;

    SELECT * FROM t1 WHERE y1=1 AND z1=1;

    The following query does not dynamically load data because no column of the unique index was qualified with an equality condition:

    SELECT * FROM t1 WHERE y1 IS NULL AND z1 IS NULL;

1.12 Changes for Release 11.2.2.3.2 from Release 11.2.2.3.1

  • A problem has been fixed where an assertion failure could occur when an INSERT statement contained a UNION clause in a derived table or view. (BugDB 14369779)

  • A problem is fixed where a query that contained a left outer join could fail to dynamically load a writethrough cache group. (BugDB 14373623)

1.13 Changes for Release 11.2.2.3.1 from Release 11.2.2.3.0

  • In previous releases, when a DROP ACTIVE STANDBY operation failed, the ttCWAdmin -drop operation exited with 0, which is considered "success." The problem has been fixed so that ttCWAdmin retries the operation and returns a failure exit code when a DROP ACTIVE STANDBY operation fails. (BugDB 14147496)

  • An inconsistency in the temporary space block free list that could cause an assertion has been fixed. (BugDB 14075421)

  • In previous releases, an assertion failure could occur when performing an INSERT, DELETE or TRUNCATE operation on a table while updating column statistics on the same table. In this release, TimesTen returns an error. (BugDB 14159483 and 14198331)

  • A problem has been fixed on MontaVista Linux Carrier Grade Edition 6, where a TimesTen uninstall would reference an awk script in the wrong directory. (BugDB 14173419)

  • Connections that used global temporary tables or PrivateCommands=1 could take 10 seconds or more to disconnect. The efficiency of disconnect in these cases has been dramatically improved. (BugDB 14198260)

  • A problem has been fixed where a core dump could occur on the TimesTen server when using an automatic client failover configuration with Oracle Clusterware. The problem could occur even when the server was idle. (BugDB 14198318)

  • Previously, cache group operations, such as dynamic load, would fail when connecting to Oracle if the user or application passed an empty Oracle password or did not provide a password. When multiple TimesTen sessions concurrently attempted to connect without specifying the Oracle password, it resulted in a performance degradation for subsequent connection attempts. This is related to a new Oracle database 11.2.0.2 behavior, which is described in KM Doc ID 1309738.1. Currently, if a TimesTen user or application tries to connect passing an empty password, TimesTen does not connect and returns an error message indicating to the user that the password is either empty or not provided. (BugDB 14205374)

  • A problem has been fixed where TimesTen could return the wrong results when batch optimization and OR list optimization were applied to the same table scan. (BugDB 14210736)

  • In rare instances, an assertion failure could invalidate the database when logs were being flushed to disk while concurrent operations were taking place in the database. (BugDB 14217041)

  • A problem has been fixed where a deadlock could occur during an ALTER REPLICATION ... ADD SUBSCRIBER operation. (BugDB 14235264)

  • A long running transaction could hang when an asynchronous writethrough cache group encounters a unique constraint violation. (BugDB 14239972)

  • The maximum value for the cacheAWTParallelism connection attribute is now 31. (BugDB 14241071)

  • When processing batch asynchronous writethrough operations, if the first operation fails, it could result in subsequent operations not serializing properly and becoming inoperative in propagating to the Oracle database. Thus, the batch operation appears to hang. (BugDB 14241173)

  • A problem has been fixed where a previous connection's Oracle password would be used if an Oracle password was not specified for the current connection. (BugDB 14257660)

1.14 Changes for Release 11.2.2.3.0 from Release 11.2.2.2.2

Changes in this release include:

1.14.1 New Features

  • This release contains performance improvements to SQL queries typically occurring in business intelligence (BI) applications.

  • Beginning in 11.2.2.3.0, in the Windows 64-bit installer, there are options to install the 32-bit client.

  • The TimesTen ttjdbc6.jar has been certified to work with the Oracle Java 7 runtime environment (JRE).

1.14.2 Bug Fixes

  • A problem has been fixed where TimesTen returns the error message: repfailover.c(168): TT16067: Failed to retrieve next row for command: repfailover. The error message did not print out enough details about the cause of the failure or whether it was safe to continue. The daemon log now contains specific information by the cause of this error. This information is printed immediately after the error message. (BugDB 12994362)

  • TimesTen internal bookkeeping is improved to remove unneeded TimesTen objects left behind in an Oracle database once an autorefresh operation was completed. (BugDB 13443440)

  • A problem causing an assertion failure existed for active standby pairs in which an XLA replicated bookmark did not advance after an application called ttXlaAcknowledge. The problem is fixed. (BugDB 13642933/13644888)

  • A problem has been fixed where an assertion failure could occur when trying to execute a complex query on a view. (BugDB 13842678)

  • A problem has been fixed with queries that included N to M handling with aggregate queries. (BugDB 13903104)

  • A problem has been fixed where an assertion failure could occur in the deadlock detector of the subdaemon when certain combinations of concurrent serializable and read-committed transactions were active. While the problem combinations could occur in various circumstances, they would most likely occur with replication running. (BugDB 13922118)

  • A problem has been fixed where a query on a view that referenced another view could return TimesTen error 2210: Column reference of columnname is ambiguous. (BugDB 13923377)

  • A problem was fixed where an assertion failure could occur when trying to use showplan with a query. (BugDB 13935557)

  • A problem has been fixed where the ttSqlCmdQueryPlan built-in procedure could return a truncated query plan when the full plan should have been returned. (BugDB 13941976)

  • A problem has been fixed where a ttRepAdmin -duplicate operation would fail with TimesTen error 703 or 12116 if the kernel SEMMSL parameter was configured in the range 2155 to 2205. (BugDB 13952486)

  • A shutdown or failure of an underlying Oracle RAC instance could cause a process connected to TimesTen IMDB Cache to terminate abnormally. This included the replication agent and the cache agent processes. This problem is fixed. (BugDB 14002438)

  • A problem has been fixed where a memory leak could occur in an asynchronous writethrough cache group with CacheAWTMethod=0 (SQL array execution method). (BugDB 14055189)

  • Operations, such as cache autorefreshes, that involve hash index lookups with deletes could get stuck in an infinite loop. This has been fixed.(BugDB 14074535)

  • The ADMIN_OPTION column was incorrectly defined in the system views SYS.DBA_SYS_PRIVS and SYS.USER_SYS_PRIVS. This problem resulted in the value of the column always being 'NO'. This has been fixed. (BugDB 14088236)

2 Platforms and configurations

This section includes:

2.1 Platforms and compilers

Platform or operating system C/C++ compiler support JDK support
Linux x86-32 and x86-64:
  • Oracle Enterprise Linux 4, 5 and 6

  • Red Hat Enterprise Linux 4, 5 and 6

  • SUSE Enterprise Server 10 and 11

  • MontaVista Linux CGE 5.0 and 6.0xFoot 1 

  • Asianux 3.0

TimesTen supports Native POSIX threads but not LinuxThreads.

Intel icc 10.1, gcc 4.3 and 4.5

Oracle Linux 6 is tested and compiled with gcc 4.4.

Oracle JDK 5.0 and 6Foot 2 

JRockit JDK 5.0 and 6.0

IBM JDK 6.0.

NOTE: The IBM Java 6 SDK requires Java SE Version 6 SR9-FP2 or above for both Linux x86 and x86-64

Microsoft Windows x86-32 and x86-64:
  • Windows XP, Windows Vista, Windows Server 2003, Windows Server 2003 Release 2, Windows Server 2008, Windows 7

Visual Studio 2010, 2008 and 2005 for Windows Oracle JDK 5.0 and 6

JRockit JDK 5.0 and 6.0

Solaris SPARC 64-bit:
  • Oracle Solaris 10 and 11

Solaris Studio 12 for Solaris SPARC Oracle JDK 5.0 and 6

JRockit JDK 5.0 and 6.0

Solaris x86-64:
  • Oracle Solaris 10 and 11

Solaris Studio 12 for Solaris x86-64 Oracle JDK 5.0 and 6
IBM AIX 64-bit:
  • AIX 6.1 and 7.1

IBM Compiler for AIX IBM JDK 5.0 and 6.0
Solaris SPARC 32-bit (client only):
  • Oracle Solaris 10 and 11

Solaris Studio 12 for Solaris SPARC Oracle JDK 5.0 and 6
IBM AIX 32-bit (client only):
  • AIX 6.1 and 7.1

IBM Compiler for AIX 32-bit IBM JDK 5.0 and 6.0

Footnote 1 On MontaVista CGE Linux, TimesTen only supports IMDB core functionality and replication. The following features are not supported on this platform: IMDB Cache and cache grid, the OCI API, Pro*C, PL/SQL, Clusterware and connections from Windows clients.

Footnote 2 The TimesTen ttjdbc6.jar has been certified to work with the Oracle Java 7 runtime environment (JRE). TimesTen does not support JDBC 7 features. The ttjdbc7.jar file is a copy of the ttjdbc6.jar.

TimesTen is supported in virtual machines provided by Oracle VM.

2.2 Client/Server configurations

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

For configuration details see "Configuring TimesTen Client and Server" in the Oracle TimesTen In-Memory Database Operations Guide.

2.3 Oracle In-Memory Database Cache

Oracle In-Memory Database Cache (IMDB Cache) enables you to cache Oracle database data in TimesTen. The TimesTen installation includes Oracle Instant Client. The following Oracle server releases are supported with the IMDB Cache option:

  • Oracle Database 10g Release 2 (10.2.0.5.0 or above)

  • Oracle Database 11g Release 1 (11.1.0.7.0 or above)

  • Oracle Database 11g Release 2 (11.2.0.2.0 or above)

  • Oracle Database 12c

2.4 Replication configurations

TimesTen replication is supported only between identical platforms and bit-levels.

Oracle Clusterware 11.2.0.2 is supported with TimesTen active standby pair replication. For more details, see Oracle TimesTen In-Memory Database Replication Guide.

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:

  • Release Notes. This document (which you are now reading) covers late-breaking information not included in the formal documentation.

  • Oracle TimesTen Media Pack. The media pack includes the Oracle TimesTen libraries and executables, demo programs, utilities and online documentation. The documentation included on the media pack consists of:

    • Oracle TimesTen In-Memory Database Release Notes (Part Number E21630). See the description above.

    • Oracle TimesTen In-Memory Database Installation Guide (Part Number E21632). This guide provides information about installing and upgrading TimesTen.

    • Oracle In-Memory Database Cache Introduction (Part Number E21631). This guide describes the features of Oracle In-Memory Database Cache and provides information to help developers plan an IMDB Cache application.

    • Oracle TimesTen In-Memory Database Operations Guide (Part Number E21633). This guide provides information about configuring TimesTen and using the ttIsql utility to manage a database. It also provides a basic tutorial for TimesTen.

    • Oracle TimesTen In-Memory Database C Developer's Guide (Part Number E21637). This guide describes how to compile and link your C application with Oracle TimesTen and how to set up and work with Oracle TimesTen databases. It covers topics that include error handling, event management and performance tuning. It also provides a reference for C language-specific APIs.

    • Oracle TimesTen In-Memory Database Java Developer's Guide (Part Number E21638). This guide describes how to compile your Java application with Oracle TimesTen and how to set up and work with Oracle TimesTen databases. It covers topics that include error handling, event management and performance tuning. It also provides a reference for Java language-specific APIs.

    • Oracle TimesTen In-Memory Database TTClasses Guide (Part Number E21640). This guide describes the Oracle TimesTen C++ Interface Classes library. The library provides wrappers around the most common ODBC functionality.

    • Oracle TimesTen In-Memory Database PL/SQL Developer's Guide (Part Number E21639). This guide describes and explains how to use PL/SQL in the TimesTen database. It is intended for anyone developing PL/SQL-based applications for the Oracle TimesTen In-Memory Database.

    • Oracle TimesTen In-Memory Database PL/SQL Packages Reference (Part Number E21645). This guide provides a reference to all PL/SQL packages available for use with the TimesTen database. It is intended for anyone developing PL/SQL-based applications for the Oracle TimesTen In-Memory Database.

    • Oracle Data Provider for .NET Oracle TimesTen In-Memory Database Support User's Guide (Part Number E21641). ODP.NET support for Oracle TimesTen In-Memory Database (TimesTen) enables ADO.NET data access from .NET client applications to TimesTen databases. This document covers features specific to ODP.NET 11.2 support of and use with TimesTen.

    • Oracle Data Provider for .NET Oracle TimesTen In-Memory Database Support User's Guide (Part Number E38358). ODP.NET support for Oracle TimesTen In-Memory Database (TimesTen) enables ADO.NET data access from .NET client applications to TimesTen databases. This document covers features specific to ODP.NET 12.1 support of and use with TimesTen.

    • Oracle TimesTen In-Memory Database Reference (Part Number E21643). This guide provides a reference to all Oracle TimesTen utilities, built-in procedures, attributes and system limits. Also provides a reference to other features of TimesTen.

    • Oracle TimesTen In-Memory Database SQL Reference (Part Number E21642). This guide contains a complete reference to all TimesTen SQL statements, expressions and functions, including TimesTen SQL extensions.

    • Oracle TimesTen In-Memory Database Error Messages and SNMP Traps (Part Number E21646). This guide contains a complete reference to the TimesTen error messages and information about using SNMP traps with TimesTen.

    • Oracle TimesTen In-Memory Database System Tables and Views Reference (Part Number E21644). This document provides a reference for TimesTen system tables and views and replication tables.

    • Oracle TimesTen In-Memory Database Replication Guide (Part Number E21635). This guide provides background information to help you understand how Oracle TimesTen replication works and step-by-step instructions and examples that show how to perform the most commonly needed tasks. It includes information about TimesTen integration with Oracle Clusterware.

    • Oracle In-Memory Database Cache User's Guide (Part Number E21634). This guide provides background information to help you understand how to create and manage Oracle In-Memory Database Cache and cache grid.

    • Oracle TimesTen In-Memory Database Troubleshooting Guide (Part Number E21636). This guide describes how to troubleshoot some of the problems users encounter when using TimesTen.

    • Oracle TimesTen In-Memory Database JDBC Extensions Java API Reference (Part Number E21647) and Oracle TimesTen In-Memory Database JMS/XLA Java API Reference (Part Number E21648). These references describe TimesTen extensions to JDBC classes and interfaces and the TimesTen JMS/XLA package.

    • Oracle Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database Installation Guide (Part Number E21649) and Oracle Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database Release Notes (Part Number E21650). The guide and release notes describe the Oracle Enterprise Manager 11g Plug-in for TimesTen.

    • Oracle Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database User's Guide (Part Number E28645) and Oracle Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database Release Notes (Part Number E28646). The guide and release notes describe the Oracle Enterprise Manager 12c Plug-in for TimesTen.

If any of these items is missing, contact Oracle TimesTen support. See "Access to Oracle Support".

5 Advance notice

This section lists deprecated and removed items.

5.1 Deprecated items in Release 11.2.2.1.0

Using a deprecated item results in a warning.

  • The -repUpgrade option of ttMigrate has been changed to -exactUpgrade to be consistent with the replication STORE clause TABLE DEFINITION CHECKING EXACT. This is the default.

  • The -noRepUpgrade option of ttMigrate has been changed to -relaxedUpgrade to be consistent with the replication STORE clause TABLE DEFINITION CHECKING RELAXED.

  • The -rename option has been removed from the ttMigrate utility.

  • Features for XLA non-persistent mode have been deprecated and removed from the documentation. Use utilities and APIs for persistent XLA only.

  • Support has been removed for TTClasses methods that take a TTStatus object as the last argument and do not return exceptions.

6 Known problems and limitations

This section contains known problems and limitations in these categories:

6.1 New issues in this release

  • To use this release of the ttStats utility with databases created in previous releases of TimesTen, you must migrate the database to 11.2.2.6.0.

6.2 Cache Advisor

  • The list of known problems and limitations for the Cache Advisor is in the readme.html file in install_dir/ttcacheadv in your TimesTen instance (Linux x8664 only).

6.3 Client/Server

  • In the Windows ODBC Client DSN Setup dialog box, when the Server Name refers to a UNIX host, pressing 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.

  • 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 (127.0.0.1).

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

6.4 IMDB Cache

  • When using Oracle IMDB Cache, we recommend that you enable full core dumps by adding the line

    DIAG_RESTRICTED=FALSE
    

    in the sqlnet.ora file that is included with your Oracle Database client installation.

    This setting enables core dumps upon an assertion failure. For more details, see your Oracle Database Readme file.

  • You cannot use a hash (#) symbol in a table name in a cache group.

  • Dynamic load might not occur under the following condition: The query specifies more than one table of the cache group and the first table in the plan is a cache group table without a dynamic load condition. Such a plan is possible when the cache group is empty.

    This can be fixed by either:

    • Setting the join order so the table with the dynamic load condition is the left-most table of the join, or

    • Setting fake statistics so the tables without the dynamic load condition are not empty.

  • Global cache group operations are not supported on Windows systems.

  • In the following scenario:

    • There are multiple AWT cache groups.

    • There are pending DML operations to be applied to be propagated to Oracle for an AWT cache group.

    • The AWT cache group is dropped and then recreated.

    The expected behavior is that the pending DML will not be applied to the Oracle database. A problem exists where the pending DML is applied to Oracle. To work around this problem, do one of the following:

    • Drop all AWT cache groups before any cache group is recreated.

      OR

    • Call the ttRepSubscriberWait build-in procedure against the Oracle database to ensure that all pending DML are applied to Oracle before dropping the cache group.

  • If a foreign key on an Oracle database corresponds to cached tables, the foreign key must have an index on it. If there is no index on the foreign key, TimesTen returns an error at the time of cache group creation. This restriction applies for AWT cache groups when parallel propagation is enabled.

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

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

    See My Oracle Support 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. (BugDB 8243193)

  • 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. (BugDB 7033084)

  • 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. (BugDB 5735286)

6.5 Installing and uninstalling TimesTen

  • When upgrading to this release, TimesTen does not automatically check for missing constraints on AWT tables created in releases 11.2.2.1.x and earlier releases of 11.2.2.2.x. Run the ttCacheCheck built-in procedure after upgrading to this release.

  • For improved JDBC Performance on TimesTen, when using a XenNet virtual device with a Windows 2003 virtual machine on Oracle VM hypervisor, configure the LargeSendOffload parameter to FALSE. By default, the LargeSendOffload parameter is set to TRUE for the XenNet virtual device. You can modify this parameter in the Advanced tab of the XenNet properties dialog.

  • For databases on Linux systems where PermSize+TempSize+LogBufMB+20MB > 256 GB, you must have Large Pages configured to accommodate the size of the shared segment.

  • On Windows 64-bit systems, you need to compile the QuickStart TTClasses demos before you can use them.

  • 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 TimesTen on a new 64-bit Linux system, you may find that it is not enabled for 32-bit applications. Select the Compatibility Arch Support and Compatibility Arch Development Support packages to install architecture specific support for your 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.

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

    http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105065
    

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

    The root IBM APAR is: IZ10231: R27 OVERWRITTEN AFTER DLSYM EXECUTION APPLIES TO AIX 5300-06.

    See http://www-01.ibm.com/support/docview.wss?uid=isg1IZ10231.

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

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

6.7 ODBC

  • The ODBC SQLExtendedFetch function appears in TimesTen header files. However, TimesTen does not support this function.

6.8 PL/SQL

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

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

6.9 Replication

  • The default handling of cache groups when duplicating databases is inconsistent between the ttRepAdmin -duplicate command line utility and the ODCB ttRepDuplicateEX utility. When using ttRepAdmin, cache groups are converted to regular tables by default (-noKeepCG). When using ttRepDuplicateEX, cache groups are retained by default.

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

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

6.10 SQL, utilities and procedures

  • Foreign key constraints are not enforced by the execution of the ttLoadFromOracle built-in procedure. When using this built-in procedure (or the ttIsql command) to load rows into a table that is the referencing table (child table) of a foreign key, it is possible that a row without any matching parent is loaded. TimesTen does not detect this foreign key violation. If the data loaded from Oracle may violate a foreign key constraint, verify the foreign key constraint manually after loading both the child and the parent table.

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

  • Deleting rows from a table that has out-of-line columns and dropping that table in the same transaction results in an assertion failure when using DDLCommitBehavior=1. To work around this problem, add a commit between the DELETE statement and the DROP TABLE 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 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.

6.11 SQL*Plus

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

6.12 TimesTen integration with Oracle Clusterware

  • A problem exists with TimesTen support for Oracle Clusterware where killing the ttCRSMaster process of the active database results in a role switch.

  • TimesTen does not support Clusterware on Windows platforms.

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

6.13 TimesTen OCI support

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

6.14 TimesTen Pro*C/C++ Support

  • On Windows platforms, the 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 compiling a Pro*C/C++ demo, this message may appear: "System default option values taken from: install_dir/ttoracle_home/instantclient_11_2/precomp/admin/pcscfg.cfg." The path name may be incorrect.

6.15 TTClasses

  • The TTCmd::setParamNull() method cannot be used to set NULL LOB data in an Oracle Database table using passthrough. Instead, use literals in INSERT or UPDATE statements.

6.16 Upgrading TimesTen

  • The ttMigrate utility cannot migrate foreign key dependencies between objects owned by different users to TimesTen release 11.2.1 and later from release 7.0 and older 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 11.2.1 and later from release 7.0 and older 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.17 XLA and JMS/XLA

See Oracle TimesTen In-Memory Database C Developer's Guide for details about XLA (Transaction Log API). See Oracle TimesTen In-Memory Database Java Developer's Guide for details about JMS/XLA.

  • XLA and JMS/XLA return incorrect information for index types for a CREATE INDEX statement. The value reflected in the flag field of ttXlaCreateIndexTup_t in XLA and the INDEX_TYPE value of CREATE_INDEX in JMS/XLA are always R, indicating regular indexes, regardless of the actual index type.

  • This limitation applies to JMS/XLA, ODBC/XLA and TTClasses/XLA. When a modification of a LOB column is committed, XLA does not return the value of the LOB. XLA does indicate the following:

    • Whether the LOB has been inserted, updated or deleted

    • Whether the value of the LOB column is NULL or not NULL

    • Whether the length of the LOB is zero

    • Whether the value of the LOB is undefined

  • TimesTen does not generate an XLA record for CREATE MATERIALIZED VIEW LOG operations.

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

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

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


Oracle TimesTen In-Memory Database Release Notes, 11g Release 2 (11.2.2)

E21630-49

Copyright © 2013, 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 is software or related documentation that 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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware 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.