Skip Headers
Oracle® TimesTen In-Memory Database Operations Guide
Release 11.2.1

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

Go to previous page
Previous
Go to next page
Next
View PDF

What's New

This section summarizes the new features and functionality of Oracle TimesTen In-Memory Database Release 11.2.1 that are documented in this guide, providing links into the guide for more information.

New features in release 11.2.1.9.0

New features in release 11.2.1.8.0

This section lists new features for Release 11.2.1.6.0 that are documented in this reference and provides cross-references to additional information:

New features in release 11.2.1.6.0

This section lists new features for Release 11.2.1.6.0 that are documented in this reference and provides cross-references to additional information:

New features in release 11.2.1.4.0

Synonym support

You can create synonyms within TimesTen, as long as you have been granted the appropriate privileges.

A synonym is an alias for a database object. Synonyms are often used for security and convenience, because they can be used to mask object name and object owner. In addition, you can use a synonym to simplify SQL statements. Synonyms provide independence in that they permit applications to function without modification regardless to which object a synonym points. Synonyms can be used in DML statements and some DDL and IMDB cache statements.

For details on synonyms, see "Understanding synonyms". For details on the privileges necessary when creating and using synonyms, see "Object privileges for synonyms".

Privileges necessary for materialized views

The owner must have SELECT privileges on each table referenced by the materialized view, also known as detail tables, when the materialized view is created. If the owner loses the SELECT privilege on any of the detail tables, the materialized view is invalid. For details on all privileges necessary for materialized views and how to recover invalid materialized views, see "Object privileges for materialized views".

View explain plan and SQL command using ttIsql

Using the ttIsql utility, you can view commands in the SQL command cache or explain plans for commands in the SQL command cache. See "Viewing commands and explain plans from the SQL Command Cache" for details.

PL/SQL connection attributes

As shown in Figure 1-8, "PL/SQL Attributes", there are first connection attributes and general connection attributes for PL/SQL.

New features in release 11.2.1.0

This guide has information about the following new features:

Access control

Oracle TimesTen In-Memory Database release 11.2.1 has a new access control model. The previous TimesTen access control model has been removed. There is no backwards compatibility between the two models.

Users are defined at the database level rather than at the installation level. Privileges are defined at the object level. The system privileges in TimesTen release 7.0 and previous releases have been replaced with system privileges that are similar to Oracle database system privileges.

The main changes to access control in this release are as follows:

For details on creating users and assigning privileges for access to database objects, see Chapter 4, "Managing Access Control".

Asynchronous materialized views

Materialized views can be refreshed asynchronously at either a specified time or through manual initiation. You can either have the deferred transactions updated incrementally or with a complete refresh. A materialized view log is created and associated with the asynchronous materialized view to facilitate the incremental refresh of data from the detail tables. For full details, see "Understanding materialized views" and "Working with materialized views".

SQL command cache

All commands executed—SQL statements, built-in procedures, and so on—are stored in the SQL Command Cache, which uses temporary memory. The commands are stored up until the limit of the SQL Command Cache is reached, then the new commands are stored after the last used commands are removed. You can retrieve one or more of these commands that are stored in the SQL Command Cache. For full details on the SQL command cache, see "Viewing SQL commands stored in the SQL Command Cache".

You can also view the query plan information to monitor and troubleshoot your queries. For details, see "Viewing query plans associated with commands stored in the SQL Command Cache".

Bitmap indexes

TimesTen supports bitmap indexes. See "Overview of index types".

Transaction log buffer file size

The configuration for the transaction log buffer file size has been modified from LogBuffSize, which was defining the size in KBs, to LogBufMB, which defines the transaction log buffer size in MBs. This affects how you configure the database size, as described in "Specifying the size of a database". Use the LogBufMB to configure performance, as described in "Increase LogBufMB if needed".

Automatic client failover

You can configure automatic client failover for databases that have active standby pair replication schemes. This enables the client to fail over automatically to the server on which the standby database resides. See "Configuring automatic client failover".

PL/SQL support

You can specify values for PL/SQL connection attributes in a data source name (DSN). See "Specifying PL/SQL connection attributes in a DSN".

You can use the ttIsql utility to create and execute PL/SQL blocks. See "Creating and executing PL/SQL blocks" and "Pass data from PL/SQL using OUT parameters".

You can use the ttIsql utility to display PL/SQL objects. See "Listing database objects by object type".

Replication performance

Use the RecoveryThreads first connection attribute to increase performance of active standby pairs. See "Increase replication throughput for active standby pairs".