Oracle TimesTen In-Memory Database

Transcription

1 Oracle TimesTen In-Memory Database Release Notes 11g Release 2 (11.2.2) E January 2014 This document provides late-breaking information for TimesTen , as well as information that is not yet part of the formal documentation. The latest version of this document is the readme.html file in your installation directory. Release notes may also be updated from time to time in the documentation library at Information about TimesTen releases before can be found at historic 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: Changes in this release Platforms and configurations Software requirements Deliverables Advance notice Known problems and limitations Documentation Accessibility 1 Changes in this release This section lists changes between releases: Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release

2 Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release Changes for Release from Release A problem is fixed where a SELECT on a synchronously maintained materialized view table would not reflect the recent INSERT operations into the detail tables. (BugDB # ) 1.2 Changes for Release from Release The ttmigrate -r -numthreads command can now take the new -delayfkeys parameter. Using this parameter enables parallel restore operations to defer creation of a table's foreign keys until after all rows in that table have been restored. This can greatly improve the performance of restore operations for tables with foreign keys. (BugDB # ) A problem has been fixed where a database connection could fail with TimesTen error 6003: Lock request denied because of time-out, during user authentication. (BugDB # ) When altering the replication schema for classic replication, there was a degradation in performance when the ROUTE clause was used. An unnecessary check was made when adding subscribers. This problem has been fixed. (BugDB # ) A problem has been fixed where dropping a table that had a foreign key contstraint from an active standby pair replication scheme would result in TimesTen error 8192, even when replication of DDL was enabled. (BugDB # ) A query that includes multiple outer joins fails. The outer join definition uses Oracle syntax (+) to designate the outer join. This problem has been fixed. (BugDB # ) A problem has been fixed where an assertion failure could occur in client server mode during a SELECT statement. (BugDB # ) The query optimizer chose a non-performant query plan when evaluating a join query that contains more than 11 tables. This problem has been fixed. (BugDB # ) When using active standby pairs with a twosafe service, sometimes a small percentage of XLA messages on the active database are not returned to XLA or JMS/XLA readers. This problem has been fixed. (BugDB # ) 2

3 1.3 Changes for Release from Release Changes in this release include: New Features Bug Fixes 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 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 ) A problem is fixed where the TimesTen Windows installer did not include the TimesTen JDBC.jar files. (BugDB ) In previous releases, TimesTen returned the wrong information in error message TT16045 when a user specified thettrepadmin -duplicate command without specifying the -localhost option. In this release, TimesTen returns useful and correct information in the error message. (Bug DB ) 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 ) 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 ) 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 ) 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 3

4 changing the cache administrator and cache user passwords is documented in the Oracle TimesTen In-Memory Database Replication Guide. (BugDB ) 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 ) In previous releases, an assertion failure could occur in a TRUNCATE TABLE operation. This is fixed. (BugDB ) 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 ) A problem is fixed where TimesTen changed the column names in the output of a query that contained an ORDER BY clause. (BugDB and ) A problem is fixed where a query executed after calling the built in procedure ttindexadvicecapturestart(1,0) would incorrectly return TimesTen error 805. (BugDB ) 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 ) 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 and ) A performance regression for hash indexes that was seen in releases and greater has been fixed. (BugDB ) Performance for queries involving left outer joins is improved in this release. (BugDB , and ) This release includes diagnostics to gather more information on a spinlatch assertion. (BugDB ) When managing more than two applications with Oracle Clusterware, TimesTen would return a large number of error messages incorrectly. This is fixed. (BugDB ) 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 ) In previous releases, an assertion failure could occur when a complex query created a temporary index on a base table. This is fixed. (BugDB ) A DELETE subquery could cause an out of temporary space error. This is fixed. (BugDB ) 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 ) A problem is fixed where the replication agent CPU usage could spike after the state of the subscriber was set to STOP. (BugDB and ) 4

5 If a latch assertion occurs, we now collect further information in the.inval file to help diagnose the root cause of the assertion. (BugDB ) TimesTen returns error message 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 is improved to better explain the cause of the error. (BugDB ) Daemon log messages for cache groups now contain the name of the cache group when the cache group is altered. (BugDB ) A problem is fixed where an assertion failure could occur during recovery of a database that contained tables with compressed columns. (BugDB and ) 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 ) An integer overflow could occur when using out-of-line columns. This is fixed. (BugDB ) A problem has been fixed where a SELECT query with a left outer join could result in a segmentation fault. (BugDB ) 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 ) 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 ) A problem is fixed that could result in database incompatibility after adding a new subscriber to an existing replication scheme. (BugDB ) 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 ) A core dump could occur with a client server application that connected, disconnected and did queries from multiple threads. This is fixed. (BugDB ) 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 ) 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 and ) 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 and ) 5

6 An assertion failure could occur for a query that used a subquery with aggregate or rownum. This is fixed. (BugDB ) 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 ) 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 ) A problem has been fixed where an UPDATE operation would run slowly and then fail with a constraint violation. (BugDB ) 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 and ) 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 ) 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 ) 1.4 Changes for Release from Release Changes in this release include: Behavior Changes New Features Tools for Proof of Concepts Bug Fixes Behavior Changes Beginning in Release , 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. 6

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

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

9 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 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 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 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 ) This release includes a new SNMP trap, ttrepstatechange, to track replication agent state changes in the case of active standby pairs. (BugDB ) 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 ) 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 ) If the PL/SQL shared memory segment was full at connection time, additional memory was leaked. This problem is fixed. (BugDB ) A potential hang was fixed in TTClasses that could occur when an error was thrown during the TTConnectionPool::freeConnection method. (BugDB ) 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 9

10 These configuration changes allow the transmitter thread on the receiver to process the backlog as quickly as possible. (BugDB ) 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 ) 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 ) 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 and ) 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 ) 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 ) 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 ) Error messages encountered by the ttcwadmin utility are improved in this release. (BugDB ) The performance of very large inserts in a master-master replication scheme is improved in this release. (BugDB ) 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 ) 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 ) 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 ) After a TRUNCATE TABLE operation was terminated, cleanup and rollback of the operation would hang. This is fixed. (BugDB ) 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 ) For UNIX systems, a problem is fixed where a client failover thread could crash if there were too many open file descriptors. (BugDB ) 10

11 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 ) 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 ) A problem is fixed where optimizer statistics were recorded incorrectly. (BugDB ) A rollback assertion on a replication subscriber could occur due to a temporary space transient error. This is fixed. (BugDB ) 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 ) 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 ) A problem has been fixed where autorefresh cache groups that had more than 67 tables could cause a buffer overflow. (BugDB and ) 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 ) A problem has been fixed where an assertion failure would occur if a table alias name was used. (BugDB ) 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 ) 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 ) 1.5 Changes for Release from Release A problem has been fixed where log files that were required by XLA were deleted prematurely. (BugDB ) A problem has been fixed where autorefresh cache groups that had more than 67 tables could cause a buffer overflow. (BugDB ) 1.6 Changes for Release from Release A problem has been fixed where a cache group with many tables with long names could run into an assertion failure. (BugDB ) Operations such as cache autorefreshes that involve hash index lookups with deletes could get stuck in an infinite loop. This has been fixed. (BugDB ) 11

12 1.7 Changes for Release from Release 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 ) 1.8 Changes for Release from Release Under certain conditions after a restart of the replication agent, parallel replication would not make progress waiting for a dependent thread to commit. (BugDB ) A problem was fixed that prevented ODP.NET from connecting to TimesTen when using the ODP.NET release with TimesTen Either the connect or disconnect request would cause a fatal exception. This is fixed in and ODP.NET 12.1 is not affected. (BugDB ) 1.9 Changes for Release from Release An assertion failure that could occur with a large query that contained many complex CASE expressions has been fixed. (BugDB ) 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 ) 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 ) 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 ) 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 ) 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 ) 1.10 Changes for Release from Release Changes in this release include: New Features Bug Fixes 12

13 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 x 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 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 ) 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 ) During replication operations, an SNMP trap is triggered when TimesTen error 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 ) 13

14 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 ) 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 ) 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 ) A problem with computing the column name of a complex view has been fixed. (BugDB ) 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 ) 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 ) 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 ) 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 ) 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 ) 14

15 TimesTen internal bookkeeping is improved to remove unneeded TimesTen objects left behind in an Oracle database once an autorefresh operation was completed. (BugDB ) 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 ) 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 ) When describing a table using the previous TimesTen releases of ttisqlcs and connecting to a TimesTen instance, the describe command would attempt to access a non-existent column NUMCOMPRESS. This has been corrected. (BugDB ) A problem is fixed where attempting to add a subscriber to an existing replication configuration could result in the deadlock error TT6002. (BugDB ) 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 ) 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 ) 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 ) 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 ) If the PL/SQL shared memory segment was full at connection time, additional shared memory was leaked. The problem has been corrected. (BugDB ) A problem has been fixed where ODP.NET clients that connect to the TimesTen server could fail due to an access violation. (BugDB ) A scalar subquery that contained an Oracle style outer join (+) on a derived table could return the wrong results. This has been corrected. (BugDB ) 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 ) 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 ) The ttbulkcp utility could use too much permanent space during inserts, if it encountered uniqueness constraint violations. This problem is corrected. (BugDB ) 15

16 A problem has been fixed where an assertion failure could occur in the TimesTen function sbmapix_t when updating data. (BugDB ) 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 ) 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 You must run the new version of this script to fix the problem. (BugDB ) 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 ) A potential hang was fixed in TTClasses that could occur when an error was thrown during the TTConnectionPool::freeConnection method. (BugDB ) 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 ) 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 ) 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 ) 1.11 Changes for Release from Release 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 ) 1.12 Changes for Release from Release A problem is fixed where a SELECT operation could result in multiple dynamic loads of data from Oracle. (BugDB ) 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 ) 1.13 Changes for Release from Release 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 16

17 used.for more details on dynamic loads, see "Dynamically loading a cache group" in the Oracle In-Memory Database Cache User's Guide. (BugDB ) 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.14 Changes for Release from Release 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 ) A problem is fixed where a query that contained a left outer join could fail to dynamically load a writethrough cache group. (BugDB ) 1.15 Changes for Release from Release 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 ) An inconsistency in the temporary space block free list that could cause an assertion has been fixed. (BugDB ) 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 and ) 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 ) 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 ) 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 ) 17

18 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 behavior, which is described in KM Doc ID 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 ) 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 ) 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 ) A problem has been fixed where a deadlock could occur during an ALTER REPLICATION... ADD SUBSCRIBER operation. (BugDB ) A long running transaction could hang when an asynchronous writethrough cache group encounters a unique constraint violation. (BugDB ) The maximum value for the cacheawtparallelism connection attribute is now 31. (BugDB ) 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 ) 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 ) 1.16 Changes for Release from Release Changes in this release include: New Features Bug Fixes New Features This release contains performance improvements to SQL queries typically occurring in business intelligence (BI) applications. Beginning in , 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) 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 18

19 now contains specific information by the cause of this error. This information is printed immediately after the error message. (BugDB ) TimesTen internal bookkeeping is improved to remove unneeded TimesTen objects left behind in an Oracle database once an autorefresh operation was completed. (BugDB ) 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 / ) A problem has been fixed where an assertion failure could occur when trying to execute a complex query on a view. (BugDB ) A problem has been fixed with queries that included N to M handling with aggregate queries. (BugDB ) 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 ) 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 ) A problem was fixed where an assertion failure could occur when trying to use showplan with a query. (BugDB ) 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 ) A problem has been fixed where a ttrepadmin -duplicate operation would fail with TimesTen error 703 or if the kernel SEMMSL parameter was configured in the range 2155 to (BugDB ) 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 ) 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 ) Operations, such as cache autorefreshes, that involve hash index lookups with deletes could get stuck in an infinite loop. This has been fixed.(bugdb ) 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 ) 2 Platforms and configurations This section includes: Platforms and compilers Client/Server configurations 19

20 Oracle In-Memory Database Cache Replication configurations 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.0x 1 Asianux 3.0 TimesTen supports Native POSIX threads but not LinuxThreads. Microsoft Windows x86-32 and x86-64: Windows XP, Windows Vista, Windows Server 2003, Windows Server 2003 Release 2, Windows Server 2008, Windows 7 Solaris SPARC 64-bit: Oracle Solaris 10 and 11 Solaris x86-64: Oracle Solaris 10 and 11 Intel icc 10.1, gcc 4.3 and 4.5 Oracle Linux 6 is tested and compiled with gcc 4.4. Visual Studio 2010, 2008 and 2005 for Windows Solaris Studio 12 for Solaris SPARC Solaris Studio 12 for Solaris x86-64 Oracle JDK 5.0 and 6 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 Oracle JDK 5.0 and 6 JRockit JDK 5.0 and 6.0 Oracle JDK 5.0 and 6 JRockit JDK 5.0 and 6.0 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 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. 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. 20