| Oracle® TimesTen In-Memory Database Operations Guide Release 11.2.1 Part Number E13065-03 |
|
|
View PDF |
| Oracle® TimesTen In-Memory Database Operations Guide Release 11.2.1 Part Number E13065-03 |
|
|
View PDF |
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.
This guide has information about the following new features:
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:
Access control is always on. You can no longer install TimesTen with access control disabled.
Only the instance administrator can create and destroy databases.
Separate databases within an instance can have different users.
Every object must have an owner that is a user in the database. You cannot create object bob.t1 unless user bob exists in the database.
Every object owner has access to their own objects. A user does not have access to objects owned by other users unless explicitly granted access by the object's owner or by a user with ADMIN privilege. Also, if the PUBLIC role has been granted access to a given object, then all database users have access to that object.
Privileges are checked at prepare and when the statement is first executed. Subsequent executions of a statement require further privilege checks only when a revoke operation is executed in the database.
You cannot create or alter a user by executing the CREATE USER user IDENTIFIED BY PASSWORD password or ALTER USER user IDENTIFIED BY PASSWORD password SQL statements across a client/server connection.
You cannot drop a user with existing objects.
Many of the utilities and built-in procedures require a certain privilege in order to execute. In addition, in order to modify or connect with certain first connection attributes, certain privileges are required. The required privilege for each is described with the utility, built-in procedure or first connection attribute description in the Oracle TimesTen In-Memory Database Reference.
Only the instance administrator can execute the ttRepAdmin -duplicate utility. The instance administrator must have the same operating system user name on both source and target machines to execute ttRepAdmin -duplicate. For more details, see Oracle TimesTen In-Memory Database Reference.
In previous versions, users could create an object with any owner name, even though no such user existed. For example, user terry could create the object pat.table1 even though there was no user pat in the database. However, since every object now has an owner, when restoring from a TimesTen database from a release before 11.2.1 using the ttMigrate utility, TimesTen automatically creates the user pat for this object. The user pat will have no privileges and will have an internally generated password. For more information, see "Data Store Upgrades" in the Oracle TimesTen In-Memory Database Installation Guide.
If you are using the ttMigrate utility to save or restore the entire TimesTen database, you must have the ADMIN privilege. However, if you are using ttMigrate to save or restore a few database objects, then you need only the privileges required to read or create those database objects. For more information, see the description for ttMigrate in the Oracle TimesTen In-Memory Database Reference.
For details on creating users and assigning privileges for access to database objects, see Chapter 4, "Managing Access Control".
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".
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".
TimesTen supports bitmap indexes. See "Overview of index types".
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 data store size, as described in "Changing data store size". Use the LogBufMB to configure performance, as described in "Increase LogBufMB if needed".
You can configure automatic client failover for data stores that have active standby pair replication schemes. This enables the client to fail over automatically to the server on which the standby data store resides. See "Configuring automatic client failover".
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 "Using OUT parameters".
You can use the ttIsql utility to display PL/SQL objects. See "Displaying information about PL/SQL objects".
Use the RecoveryThreads first connection attribute to increase performance of active standby pairs. See "Increase replication throughput for active standby pairs".
|
 Copyright © 2006, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
