This section summarizes the new features of Oracle TimesTen In-Memory Database 11g Release 2 (11.2.2) that are documented in this guide and provides links to more information.
The DDLReplicationLevel and DDLReplicationAction connection attributes control what objects that are created or dropped by DDL statements are automatically replicated to the databases involved in an active standby pair replication scheme. For this release, a new level of 3 (not the default) for the DDLReplicationLevel connection attribute adds replication of the CREATE VIEW or DROP VIEW statements, the CREATE SEQUENCE or DROP SEQUENCE statements, and the result of running the UidPwdSet built-in procedure to set the Oracle password for the cache manager for an active standby pair. See "DDLReplicationAction", "DDLReplicationLevel", "ttCacheUidPwdSet", and "ttAdmin" for details.
There is a new user error log message designation RECOVERY, for messages that report on TimesTen automatic recovery status. This is not a category that you can control through the ttDaemonLog utility; the messages cannot be disabled.
When using Oracle Clusterware, you must execute the new ttCWAdmin -reauthenticate command after modifying any user name or password to enable Oracle Clusterware to store these new user names and passwords. For full details, see "Changing user names or passwords when using Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide. Also, see "ttCWAdmin".
You can use the ttIsql edit command to edit a file or edit ttIsql commands in a text editor. The ttIsql edit command starts a text editor such as emacs, gedit, or vi. For more information, see "Using the ttIsql edit command" in the Oracle TimesTen In-Memory Database Operations Guide. Also, see "ttIsql".
The ttIsql utility now also includes the command waitforresult. The command is similar to the waitfor command, except that the result can have 1 or more columns. See "ttIsql".
You can manage the size of the reclaim buffer for the cache agent used to process autorefresh. You can also manage the size of the reclaim buffer for the replication agent when using an active standby pair replication scheme that includes autorefresh cache groups. See "ttDBConfig".
Tools have been added to enable control over read optimization during periods of concurrent write operations. For more details, see "ttDbWriteConcurrencyModeGet" and "ttDbWriteConcurrencyModeSet."
The ttStats utility is added to TimesTen to support collection and comparison of snapshots of database metrics.
You can now set the value for the cacheAWTMethod first connection attribute and with the ttDBConfig built-in procedure. You can set the CacheParAwtBatchSize parameter to configure a threshold value for the number of rows included in a single batch. See "ttDBConfig".
At certain times, you may execute large transactions, such as for the end of the month, the end of a quarter, or the end of the year transactions. You may also have situations where you modify or add a large amount of data in the Oracle database over a short period. For read-only, autorefresh cache groups, TimesTen could potentially run out of permanent space when an autorefresh operation applies either one of these cases. Therefore, 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".
Prolonged use or a heavy workload of the change log tables can result in fragmentation of the tablespace. To prevent degradation of the tablespace from fragmentation of the change log tables, TimesTen calculates the fragmentation for the tablespace and provides a way to defragment the tablespace and reclaim the space. For more details, see "ttCacheAutorefreshLogDefrag".
In this release you can specify the amount of memory to allocate in the transaction commit buffer for reclaim records. For details, see the connection attribute "CommitBufferSizeMax" and the built-in procedures "ttCommitBufferStats" and "ttCommitBufferStatsReset".
In this release, you can use the AutorefreshLogDefrag built-in procedure to compact the trigger log space for a cache autorefresh table. See "ttCacheAutorefreshLogDefrag".
In a ttRepAdmin -duplicate operation, now you can specify a local or remote IP address for the destination of the duplicate, using the options -localIP and -remoteIP. See "Duplicate a database".
You can use the new Index Advisor to receive recommendations about indexes that could improve the performance of a specific SQL workload. The Index Advisor consists of several built-in procedures. The procedures that comprise the Index Advisor are:
A new tool, the TimesTen Cache Advisor, enables Oracle Database customers to determine whether the performance of an existing Oracle Database application can be improved if the application is used with TimesTen Cache. Cache Advisor generates recommendations of TimesTen cache group definitions based on the SQL usage in the Oracle Database application. For more information, see ttCacheAdvisor.
New tools have been added that enable you to load the results of a SQL query from a back-end Oracle database into a single table on TimesTen without creating a cache grid, cache group, and cache table to contain the results. TimesTen provides the tools that execute a user provided SELECT statement on an Oracle database and load the result set into a table on TimesTen. The ttIsql utility is enhanced to include the LoadFromOracle command. In addition, two new built-in procedures are in this release as part of this feature:
The ttIsql utility now supports autovariables, showcurrenttime as a set/show attribute, the IF command, and WHENEVER error handling. See more details in the description of the ttIsql utility.
The new Automatic parallel replication allows for the parallel replication and application of transactions changes to the receiving nodes in a replication scheme. See Chapter 1, "Connection Attributes" for more details on parallel replication.
The ability to determine the current space usage of a table using the ttComputeTabSizes built-in procedure.
The new Automatic parallel replication allows for the parallel replication and application of transactions changes to the receiving nodes in a replication scheme. See Chapter 1, "Connection Attributes" for more details on parallel replication.
You can configure parallel propagation of changes in AWT cache tables to the corresponding Oracle database tables. See Chapter 1, "Connection Attributes" for more details on parallel propagation.
The maximum value of the LogBufMB and LogFileSize connection attributes has increased to 64 GB on 64-bit systems.