Glossary
ADO policy
A policy that specifies a rule and condition for Automatic Data Optimization (ADO). For example, an ADO policy may specify that an object is marked
NOINMEMORY (action) 30 days after creation (condition). Specify ADO policies using the ILM clause of CREATE TABLE and ALTER TABLE statements.
Automatic Data Optimization (ADO)
A technology that creates policies, and automates actions based on those policies, to implement an Information Lifecycle Management (ILM) strategy.
Bloom filter
A low-memory data structure that tests membership in a set. The database uses Bloom filters to improve the performance of hash joins.
Column Compression Unit (CU)
Contiguous storage for a column in an In-Memory Compression Unit (IMCU).
columnar data pool
The subpool in the In-Memory Area that stores columnar data. It is also known as the 1 MB pool.
columnar format
The column-based format for objects that reside in the In-Memory Column Store. The columnar format contrasts with the row format used in data blocks.
common dictionary
A segment-level, instance-specific set of master dictionary codes, created from local dictionaries. A local dictionary is a sorted list of dictionary codes specific to a Column Compression Unit (CU). A join group uses a common dictionary to optimize joins.
compression tiering
The application of different levels of compression to data based on its access pattern. For example, administrators may compress inactive data at a higher rate of compression at the cost of slower access.
dense grouping key
A key that represents all grouping keys whose grouping columns come from a particular fact table or dimension.
dense join key
A key that represents all join keys whose join columns come from a particular fact table or dimension.
double buffering
A repopulation mechanism in which background processes create new In-Memory Compression Unit (IMCU) versions by combining the original rows with the latest modified rows. During repopulation, the stale IMCUs remain accessible for queries.
expression
A combination of one or more values, operators, and SQL functions that resolves to a value.
Expression Statistics Store (ESS)
A repository maintained by the optimizer to store statistics about expression evaluation. For each segment, the ESS monitors statistics such as frequency of execution, cost of evaluation, timestamp evaluation, and so on. The ESS is persistent in nature and also has an SGA representation for fast lookup of expressions.
FastStart area
A designated tablespace to which the database periodically writes In-Memory columnar data.
Heat Map
Heat Map shows the popularity of data blocks and rows. Automatic Data Optimization (ADO) to decide which segments are candidates for movement to a different storage tier.
home location
The database instance in which an IMCU resides. When auto DOP is enabled on Oracle RAC, the parallel query coordinator uses home location to determine where each IMCU is located, how large it is, and so on.
IM aggregation
An optimization that accelerates aggregation for queries that join from a single large table to multiple small tables. The transformation uses
KEY VECTOR and VECTOR GROUP BY operators, which is why it is also known as VECTOR GROUP BY aggregation.
IM column store
An optional SGA area that stores copies of tables and partitions in a columnar format optimized for rapid scans.
IM expression
A SQL expression whose results are stored in the In-Memory Column Store. If
last_name is a column stored in the IM column store, then an IM expression might be UPPER(last_name).
IMCU mirroring
In Oracle RAC, the duplication of an IMCU in multiple IM column stores. For example, the IM column stores on instance 1 and instance 2 are populated with the same
sales table.
IMCU pruning
In a query of the In-Memory Column Store, the elimination of IMCUs based on the high and low values in each IMCU. For example, if a statements filters product IDs greater than 100, then the database avoids scanning IMCUs that contain values less than 100.
IM storage index
A data structure in an IMCU header that stores the minimum and maximum for all columns within the IMCU.
In-Memory Advisor
A downloadable PL/SQL package that analyzes the analytical processing workload in your database. This advisor recommends a size for the IM column store and a list of objects that would benefit from In-Memory population.
In-Memory Compression Unit (IMCU)
A storage unit in the In-Memory Column Store that is optimized for faster scans. The In-Memory Column Store stores each column in table separately and compresses it. Each IMCU contains all columns for a subset of rows in a specific table segment.
A one-to-many mapping exists between an IMCU and a set of database blocks. For example, if a table contains columns c1 and c2, and if its rows are stored in 100 database blocks on disk, then IMCU 1 might store the values for both columns for blocks 1-50, and IMCU 2 might store the values for both columns for blocks 51-100.
In-Memory Coordinator Process (IMCO)
A background process whose primary task is to initiate background population and repopulation of columnar data.
In-Memory Expression Unit (IMEU)
A container that stores the computed result of an In-Memory Expression (IM expression). Each IMEU is linked to its own parent In-Memory Compression Unit (IMCU).
In-Memory FastStart
A feature that significantly reduces the time to populate data into the IM column store when a database instance restarts.
In-Memory virtual column
A virtual column that is eligible to be populated in the In-Memory Column Store.
Information Lifecycle Management (ILM)
A set of processes and policies for managing data throughout its useful life.
join group
A user-defined object that specifies the columns that join two or more tables in a query. Join groups are only supported when
INMEMORY_SIZE is a nonzero value.
metadata pool
A subpool of the In-Memory Area that stores metadata about the objects that reside in the IM column store. The metadata pool is also known as the 64 KB pool.
on-demand population
When
INMEMORY PRIORITY is set to NONE, the IM column store only populates the object when it is accessed through a full scan. If the object is never accessed, or if it is accessed only through an index scan or fetch by rowid, then it is never populated.
OZIP
A proprietary compression technique that offers extremely fast decompression. OZIP is tuned specifically for Oracle Database.
partition exchange load
A technique in which you create a table, load data into it, and then exchange an existing table partition with the table. This exchange process is a DDL operation with no actual data movement.
population
The operation of reading existing data blocks from data files, transforming the rows into columnar format, and then writing the columnar data to the IM column store. In contrast, loading refers to bringing new data into the database using DML or DDL.
priority-based population
When
PRIORITY is set to a value other than NONE, Oracle Database adds the object to a prioritized population queue. The database populates objects based on their queue position, from CRITICAL to LOW. It is “priority-based” because the IM column store automatically populates objects using the prioritized list whenever the database re-opens. Unlike in on-demand population, objects do not require a full scan to be populated.
repopulation
The automatic refresh of a currently populated In-Memory Compression Unit (IMCU) after its data has been significantly modified. In contrast, population is the initial creation of IMCUs in the IM column store.
service
The logical representation of an application workload that shares common attributes, performance thresholds, and priorities. A single service can be associated with one or more instances of an Oracle RAC database, and a single instance can support multiple services.
Snapshot Metadata Unit (SMU)
A storage unit in the In-Memory Area that contains metadata and transactional information for an associated In-Memory Compression Unit (IMCU).
Space Management Worker Process (Wnnn)
A process that populates or repopulates data in the IM column store on behalf of In-Memory Coordinator Process (IMCO).
staleness threshold
An internally set percentage of entries in the transaction journal for an IMCU that initiates repopulation.
storage tiering
The deployment of data on different tiers of storage depending on its level of access. For example, administrators migrate inactive data from high-performance, high-cost storage to low-cost storage.
threshold-based repopulation
The automatic repopulation of an IMCU when the number of stale entries in an IMCU reaches an internal staleness threshold.
transaction journal
Metadata in a Snapshot Metadata Unit (SMU) that keeps the IM column store transactionally consistent.
trickle repopulation
A supplement to threshold-based repopulation. The In-Memory Coordinator Process (IMCO) may instigate trickle repopulation automatically for any IMCU in the IM column store that has stale entries but does not meet the staleness threshold.