Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
11g Release 1 (11.1.1)

Part Number E14849-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

B Oracle TimesTen Database Guidelines

DAC supports Oracle TimesTen In-Memory Database (TimesTen) as a data warehouse database type. This appendix describes usage guidelines specific to TimesTen databases.

This appendix contains the following topics:

About TimesTen as a Database Type

Oracle TimesTen In-Memory Database (TimesTen) operates on databases that fit entirely in physical memory (RAM). Therefore, because memory is limited, you should make sure a data warehouse that resides in a TimesTen database holds only the necessary tables and columns and that the columns are of an optimal size. For example, you could store a full set of data warehouse tables in an Oracle database, and then move a subset of the tables to a TimesTen database.

The In Memory check box in the Tables tab and Columns subtab of the Design view is a flag that controls whether DAC designates the tables and columns as In Memory. Only In Memory tables and columns will be created and upgraded in the TimesTen database. If a table is In Memory, by default all of its columns are also In Memory. You can individually deselect a column's In Memory check box if you do not want the column to be In Memory.

In Memory tables and columns are created, updated, and dropped on a TimesTen database in the same way they are for Oracle, SQL Server, and DB2 databases. For instructions on managing data warehouse schemas, including a schema on a TimesTen database, see Chapter 10, "Managing Data Warehouse Schemas."

Setting Up an ODBC Connection Between DAC and TimesTen Databases

DAC communicates with TimesTen databases using an ODBC connection.

Pruning Tables and Columns for TimesTen Databases

If there are tables or columns that you do not need for analytical reporting, you can prune them in DAC so that they are not created in the TimesTen database.

Pruning Tables

To ensure a table is not created in a TimesTen database, do one of the following:

Pruning Columns

You can prune columns for TimesTen databases in the following ways:

About DAC Support for Indexes in TimesTen Databases

Consider the following points about DAC support for indexes in TimesTen databases:

Customizing How Tables Are Analyzed in TimesTen Databases

The customsql.xml file, located in the <DAC_Config_Location>\CustomSQLs directory, contains the default syntax DAC uses for analyzing tables on all database types, including a TimesTen database. You can edit the customsql.xml file to change the default behavior. For instructions, see "Customizing customsql.xml to Drop and Create Indexes and Analyze Tables".

TimesTen Data Types

When a DAC table column is converted to a TimesTen table column:

Table B-1 Conversion of Types from DAC to TimesTen for Non-Unicode Databases

DAC Data Type TimesTen Data Type

CHAR

TT_CHAR

VARCHAR

TT_VARCHAR

NUMBER

NUMBER

See "About the Number Data Type When Precision Is Zero".

TIMESTAMP

TT_TIMESTAMP

DATE

TT_DATE


Table B-2 Conversion of Types from DAC to TimesTen for Unicode Databases

DAC Data Type TimesTen Data Type

CHAR

TT_NCHAR

VARCHAR

TT_NVARCHAR

NUMBER

NUMBER

See "About the Number Data Type When Precision Is Zero".

TIMESTAMP

TT_TIMESTAMP

DATE

TT_DATE



About the Number Data Type When Precision Is Zero

To reduce memory usage, when the data type is number and the precision is zero, the following conditions apply: