Oracle TimesTen In-Memory Database Licensing

What Is Oracle TimesTen In-Memory Database?

Oracle TimesTen In-Memory Database (IMDB) is a fully relational, ACID-compliant database that resides entirely in main memory at runtime. Unlike Oracle Database's In-Memory Column Store option — which caches data structures in memory to accelerate analytics on a disk-based database — TimesTen is a standalone database product designed from the ground up for memory-resident storage and processing.

TimesTen delivers response times in the sub-millisecond to microsecond range, making it the platform of choice for applications that demand the highest possible transaction throughput: prepaid telecommunications billing, real-time fraud detection, securities trading platforms, online gaming, and network element management systems that process millions of records per second.

TimesTen can be deployed in two distinct modes. The first is as a standalone in-memory database of record, where all data lives in memory with disk checkpointing for persistence and recovery. The second is as a cache layer in front of Oracle Database — the Oracle TimesTen Application-Tier Database Cache (IMDB Cache) configuration — where TimesTen caches hot data subsets from an Oracle Database backend, providing memory-speed access while transparently propagating updates to and from the underlying Oracle Database.

Licensing Metrics: Processor vs Named User Plus

Oracle TimesTen In-Memory Database is available under two standard Oracle licensing metrics: Processor and Named User Plus (NUP). The correct metric depends on the size and nature of your user population and the commercial context of the deployment.

Processor Licensing

Processor licensing is the dominant model for TimesTen deployments in high-volume, external-facing, or large-enterprise environments. Under the Processor metric, you licence every physical processor core on the servers where TimesTen is installed, after applying Oracle's core factor. The list price for a TimesTen Processor licence is $23,000 per processor.

Oracle's core factor is applied to the raw physical core count to calculate the number of processor licences required. For most modern Intel and AMD x86 processors, the core factor is 0.5, meaning a server with 32 physical cores requires 16 Processor licences. For Intel Xeon with Intel's Hyper-Threading, only physical cores are counted — logical threads do not increase the licence count. IBM POWER processors use a core factor of 1.0, so each core counts as one full Processor licence.

The practical implication of Processor licensing is that all users and applications connecting to the TimesTen database can do so without individual user counting. The Processor metric is therefore the appropriate model when the number of end-users is large, unknown, variable, or when the system serves anonymous external consumers such as subscribers to a telecommunications network or participants in a financial market.

Named User Plus Licensing

Named User Plus (NUP) licensing is the appropriate model when the number of users accessing TimesTen is relatively small, well-defined, and stable. Under NUP, each individual person or automated device that accesses TimesTen must be counted as a named user. The list price is $460 per Named User Plus licence.

A critical constraint that organisations frequently overlook is Oracle's minimum NUP requirement for TimesTen: 25 Named User Plus licences per Processor. This floor prevents cost arbitrage in environments with very few users but high-core-count servers. In practice, this means that NUP licensing is only cost-advantageous when the user count is materially lower than the 25-per-processor floor — typically in environments with modest hardware and a small, defined user base.

For example, a four-core server (two Processor licences at 0.5 core factor) requires a minimum of 50 NUP licences. If the organisation has 30 actual named users, the NUP cost is 50 × $460 = $23,000, compared to the Processor cost of 2 × $23,000 = $46,000. NUP licensing wins here. If the organisation has 200 named users, Processor licensing at $46,000 is far more cost-effective than 200 × $460 = $92,000.

Application-Tier Database Cache (IMDB Cache) Licensing

The TimesTen Application-Tier Database Cache variant — sometimes referred to as IMDB Cache or Oracle In-Memory Database Cache — follows the same Processor and NUP metrics but is licensed separately from the standalone TimesTen product. The IMDB Cache product is specifically the configuration where TimesTen acts as a cache in front of Oracle Database.

An important and frequently misunderstood aspect of IMDB Cache licensing is the relationship between TimesTen and the underlying Oracle Database licence. When you use TimesTen as a cache for Oracle Database, you must have appropriately sized Oracle Database Enterprise Edition licences in place for the Oracle Database that TimesTen caches. The TimesTen IMDB Cache licence does not include or substitute for the Oracle Database licence — both products require independent licence coverage.

Furthermore, if your Oracle Database is licensed using the Named User Plus metric, your TimesTen IMDB Cache licence must also be on the NUP metric, with at least as many NUP licences as the Oracle Database deployment. Metric consistency between the cache layer and the underlying database is a contractual requirement, not an advisory suggestion.

Virtualisation and Soft Partitioning

Oracle's virtualisation licensing rules apply to TimesTen in the same manner they apply to Oracle Database. Oracle classifies most mainstream hypervisors — VMware vSphere, Microsoft Hyper-V, KVM, and others — as soft partitioning technologies. Under Oracle's policy, soft partitioning does not limit licence requirements.

This means that if TimesTen is installed in a virtual machine that can potentially migrate to any host within a cluster, Oracle requires licensing of all physical processor cores across every host in that cluster — regardless of the VM's current location or whether it has ever run on certain hosts. The licence requirement is not determined by actual usage, but by the potential mobility of the workload.

The only virtualisation technology Oracle recognises as hard partitioning — where the licence requirement is limited to the physical resources allocated to a specific partition — is Oracle VM for SPARC (LDOMs), IBM LPAR with Dynamic System Domains disabled, and Oracle Solaris Zones in specific configurations. Standard enterprise virtualisation platforms do not qualify.

Organisations that have deployed TimesTen in VMware clusters without licensing all hosts in the cluster are in the most common TimesTen audit risk position. The remediation typically requires either purchasing additional Processor licences for all uncounted hosts, migrating TimesTen to a hard-partitioned or bare-metal environment, or committing to a constrained VM configuration that limits host mobility through contractual arrangements with Oracle.

Support Fees and the 8% Annual Increase

Oracle's annual support fee for TimesTen is 22% of the net licence purchase price. This baseline itself compounds: Oracle exercises an annual support fee increase of 8% per year, meaning that support costs for TimesTen grow by 8% annually from the baseline established at the time of initial purchase. Over five years, this produces a cumulative support cost increase of approximately 47% above the initial support fee level. Over ten years, the compounding effect more than doubles the original annual support bill.

For organisations with large TimesTen Processor licence estates — common in telecommunications companies with multi-host deployments serving subscriber management systems — the compounding support cost can represent millions of dollars per year. This trajectory makes support cost management an important part of the TimesTen total cost of ownership calculation, particularly for organisations with no near-term plans to upgrade or migrate away from TimesTen.

Strategies for managing TimesTen support costs include: negotiating a multi-year support price cap at renewal, exploring third-party support coverage for TimesTen where available, and assessing whether the TimesTen workload can be migrated to an alternative in-memory data platform (such as Oracle Database's In-Memory option, Redis Enterprise, or Apache Ignite) as part of a broader infrastructure modernisation programme.

Common Licensing Pitfalls

Based on advisory engagements across telecommunications, financial services, and manufacturing sectors, the most frequently encountered TimesTen licensing problems are:

• VMware cluster under-licensing: TimesTen installed in a VMware environment where only the current host's cores have been licensed, rather than all hosts in the cluster. This is the most common and largest-value compliance gap.
• Metric mismatch with Oracle Database: TimesTen licensed on Processor while the underlying Oracle Database EE is on Named User Plus. Oracle requires metric consistency in IMDB Cache deployments.
• Minimum NUP floor not applied: Organisations that selected NUP licensing but counted only actual users without applying the 25-per-processor minimum, resulting in an under-licenced position.
• TimesTen instances on additional servers: Development, QA, staging, and disaster recovery environments where TimesTen has been installed without corresponding licence coverage. Oracle requires licences for all installations regardless of environment type, unless the installation qualifies under a specific restricted-use licence.
• No Oracle Database licence for IMDB Cache: Organisations that licensed the TimesTen IMDB Cache product but did not maintain adequate Oracle Database EE licences for the Oracle Database being cached. Both products require independent coverage.

Cost Optimisation Strategies

For organisations seeking to reduce their Oracle TimesTen licensing spend without compromising technical capabilities, several optimisation strategies merit evaluation.

Metric review: Validate that the current licensing metric (Processor or NUP) is actually the most cost-effective model for the current deployment. User populations and server configurations change over time, and a metric that was optimal at initial purchase may no longer represent the best value.

Deployment consolidation: Assess whether multiple TimesTen instances can be consolidated onto fewer servers without performance impact. Fewer Processor licences required — and lower annual support fees — result directly from reduced physical core count. Cloud or containerised deployments using Oracle-approved hard partitioning may offer further consolidation opportunities.

Negotiate at renewal: TimesTen support renewal is a negotiation opportunity. Oracle has demonstrated willingness to agree multi-year support price caps, particularly for customers with large installed bases and no immediate migration plans. Engaging a specialist Oracle licensing advisor ahead of the renewal creates commercial leverage that self-managed renewals rarely achieve.

Alternative platform assessment: For organisations whose TimesTen deployment is being renewed primarily due to technical inertia rather than architectural necessity, an objective assessment of alternative in-memory data platforms may reveal migration paths that reduce total cost of ownership while maintaining or improving performance characteristics.