Oracle Database In-Memory Licensing
- Separately licensed Oracle EE option.
- Required when enabling INMEMORY attributes on tables or using the In-Memory Column Store.
- Licensing metrics (Processor or NUP) must match EE database licenses.
- A license is required for all processors on servers using Database In-Memory.
- No license is required for Memoptimized Rowstore or setting INMEMORY_SIZE without activating tables.
Oracle Database In-Memory Licensing
Oracle Database In-Memory is an advanced option within Oracle Database Enterprise Edition (EE) designed to accelerate analytic query performance significantly.
Storing data in memory using a specialized columnar format drastically reduces response times for analytical workloads. Understanding the licensing requirements for Oracle Database In-Memory ensures organizations fully leverage its benefits while remaining compliant with Oracle licensing rules.
Read more about Oracle Database Options licensing.
What is Oracle Database In-Memory?
Oracle Database In-Memory provides a high-performance, in-memory column store to complement Oracle’s traditional row-based database structure. It allows databases to simultaneously store data in dual formats: the existing row format for efficient OLTP operations and an additional columnar format optimized for analytics and reporting.
Core Capabilities of Database In-Memory:
- Columnar Data Storage: Data stored in memory in a compressed columnar format, greatly accelerating analytic queries.
- Dual-Format Architecture: This architecture maintains both columnar (in-memory) and traditional row formats (on-disk), enabling efficient mixed workloads.
- Vectorized Query Processing: Dramatically speeds analytic operations by scanning compressed columns directly in memory.
- In-Memory Aggregation and Join Groups: Further enhances performance by pre-aggregating data and optimizing table joins.
- Automatic Data Management: Oracle transparently manages data placement and memory allocation, simplifying operations.
Licensing Requirements for Oracle Database In-Memory
Oracle Database In-Memory is not included by default with Oracle Enterprise Edition and is considered a premium, separately licensed option. Licensing this option explicitly is required whenever any in-memory features are activated.
Licensing Essentials:
- The Database In-Memory option must be explicitly licensed for each database server using its features.
- All processors on a database server employing the In-Memory Column Store must be fully licensed with Database In-Memory.
- Licensing metrics (Processor or Named User Plus (NUP)) must match your Enterprise Edition database licensing.
Read about Oracle Diagnostics Pack Licensing.
When is Oracle Database In-Memory Licensing Mandatory?
Licensing is specifically required if you enable or use any of the following features:
- Activating the INMEMORY attribute on any tables, partitions, or materialized views.
- Using the In-Memory Column Store (IMCS) for query acceleration.
- Utilizing advanced In-Memory features such as aggregation optimizations or join groups.
Simply setting the database parameter for the In-Memory Column Store (INMEMORY_SIZE) without marking any table as INMEMORY doesn’t trigger licensing, but practical usage typically involves explicitly marking tables or partitions.
Read about Oracle TimesTen Application-Tier Database Cache Licensing.
Licensing Metrics for Oracle Database In-Memory
Oracle Database In-Memory licensing strictly matches the metric chosen for Oracle EE licensing:
Processor-Based Licensing:
- Licensing is based on the total processor cores on each server utilizing the In-Memory Column Store.
- Each processor core of the database server employing In-Memory must be licensed.
Example:
- The database server has 16 processor cores licensed for EE.
- If this server enables In-Memory features, all 16 processor cores must also be licensed explicitly for Database In-Memory.
Named User Plus (NUP) Licensing:
- Licensing is based on total named users authorized to access the database.
- Oracle’s minimum of 25 Named User Plus licenses per processor core applies, though NUP licensing is less common for databases typically using In-Memory features (usually large analytic environments).
Example:
- Database with four cores enabling In-Memory.
- Minimum NUP licensing required: 4 cores × 25 users each = 100 NUP licenses.
Practical Licensing Scenario: Retail Real-Time Analytics
Clearly understanding licensing is best achieved through a practical example illustrating Oracle Database In-Memory’s application and licensing considerations.
Scenario Description:
A retail company runs an Oracle database that handles online transactions (OLTP). It also needs rapid analytic queries (e.g., sales dashboards and real-time trend analysis). Previously, analytic queries took up to 30 seconds, negatively impacting business intelligence users.
Implementation of Database In-Memory:
- Deploy Database In-Memory on their existing 16-processor Oracle EE server.
- Enable In-Memory features for key tables such as Products, Sales, and Inventory.
- Allocate 100GB of memory for the column store.
- Activate the INMEMORY attribute on targeted tables/partitions.
Licensing Implications:
- All 16 processor cores of the database server must be licensed explicitly for Database In-Memory.
- Licensing aligns exactly with their EE licensing metrics (processor-based).
Achieved Benefits:
- Query response times reduced dramatically from 30 seconds down to approximately 2 seconds.
- Real-time analytics capabilities significantly improved user experience and business responsiveness.
- Transparent dual-format architecture maintained OLTP performance without additional complexity.
Database In-Memory Licensing Reminders
Licensing Required When Using:
- INMEMORY Table Attributes: Explicitly marking any tables, partitions, or materialized views for in-memory storage.
- In-Memory Column Store: Activating the column store itself for analytical processing.
- In-Memory Aggregation and Join Groups: Using advanced analytical optimizations.
Licensing Scope:
- Licensing applies per database server: All processor cores on the server employing Database In-Memory features must be fully licensed.
- In RAC environments, each node utilizing the column store requires licensing separately.
No Licensing Needed For:
- INMEMORY_SIZE parameter alone without enabling any tables for in-memory storage.
- Memoptimized Rowstore feature: This is a separate functionality from Database In-Memory, intended for small lookup tables, and doesn’t require licensing.
Common Licensing Pitfalls to Avoid
Preventing common licensing mistakes ensures Oracle compliance and audit readiness:
- Enabling INMEMORY Attributes without Licensing: Even limited usage of INMEMORY attributes mandates full licensing of Database In-Memory.
- Partial Processor Licensing: Attempting to license only certain processors (cores) on a server—Oracle mandates licensing all processors if In-Memory is used.
- Confusing Memoptimized Rowstore with Database In-Memory: The separate Memoptimized Rowstore feature doesn’t require licensing; confusing these can lead to unnecessary licenses or accidental compliance breaches.
Oracle Licensing Audits and Database In-Memory Compliance
Due to its high-value and specialized features, Oracle frequently audits Database In-Memory licensing to ensure compliance:
Recommendations for Audit Preparedness:
- Document all databases where In-Memory features are activated.
- Regularly audit internally, verifying licensing precisely matches EE licensing metrics.
- Engage Oracle licensing experts proactively for assistance when implementing or expanding Database In-Memory deployments.
Cost Optimization Strategies for Database In-Memory Licensing
Oracle Database In-Memory licenses represent significant investments but can be cost-optimized:
- Targeted Deployment: Only enable in-memory features on databases that benefit from substantial analytic performance gains.
- Hardware Optimization: Consolidate analytic workloads on fewer high-core-density servers to reduce the licensing footprint.
- Selective Data Allocation: Enable the In-Memory attribute only for critical tables or partitions requiring extreme analytics performance, minimizing total license requirements.
Comparing Database In-Memory with Alternative Oracle Options
Understanding how Database In-Memory compares to other Oracle performance options helps clarify its distinct value:
Database In-Memory vs. TimesTen Application-Tier Database Cache:
- Database In-Memory: Integrated into the Oracle Database, ideal for analytic acceleration within Oracle environments.
- TimesTen Cache: This is a separate product licensed independently, which is best for application-tier caching requiring extremely low latency outside the traditional Oracle Database.
Choosing between them depends on architectural needs (in-database analytics vs. mid-tier caching).
Key Licensing Summary Points:
- Separately licensed Oracle EE premium option.
- Licensing is mandatory if INMEMORY table attributes, In-Memory Column Store, or advanced analytic features are enabled.
- Licensing metrics (Processor or NUP) must match EE licensing.
- Licensing applies per server: All processors utilizing In-Memory must be licensed.
- Primarily targeted for data warehouses, data marts, or mixed OLTP/analytic workloads needing high-speed analytics.
Conclusion
Oracle Database In-Memory significantly accelerates analytic query performance within Oracle Database Enterprise Edition environments. Proper licensing understanding is essential for leveraging its full benefits without compliance risks.
By carefully documenting deployments, proactively managing licensing compliance, and strategically leveraging Database In-Memory’s powerful features, organizations effectively balance performance gains with licensing costs, confidently achieving robust analytic performance and compliance.
