Oracle TimesTen In-Memory Database Licensing: When It's Included vs Extra

TimesTen Licensing: Understanding Two Distinct Cost Models

Oracle TimesTen is an in-memory relational database optimized for sub-microsecond response times and streaming analytics. Unlike Oracle Database, which charges per core, TimesTen offers two separate licensing paths: processor-based and Named User Plus (NUP) based. Understanding when each applies, and when TimesTen is bundled into other Oracle products, is critical to avoiding overprovisioning and correctly modeling total cost of ownership.

The core confusion around Oracle TimesTen licensing stems from four different deployment scenarios, each with distinct licensing requirements. TimesTen Application-Tier Database Cache requires a processor license. Standalone TimesTen as an in-memory database platform requires either a processor or NUP license. TimesTen Cache bundled with Oracle Database Enterprise Edition requires no separate license. And TimesTen Express Edition is free under Oracle Free Use Terms. Enterprises frequently misunderstand which scenario applies to their deployment, resulting in unnecessary license purchases or audit exposure if they fail to purchase required licenses.

This article covers the exact mechanics of TimesTen licensing, real-world cost models, and the specific scenarios where TimesTen is included versus when it incurs additional cost. We reference data from 75 Named User deployments, processor core mapping under Oracle's core factor table, and the repricing mechanics that apply when TimesTen is bundled with other Oracle products.

TimesTen Licensing Models: Processor vs Named User Plus

TimesTen Application-Tier Database Cache operates under a processor licensing model. A single processor license costs $23,000. Under Oracle's licensing rules, a processor is defined using the core factor table specific to your server's CPU architecture. An Intel Xeon server with 8 cores, for example, counts as 8 processors for licensing purposes. The same server under Oracle licensing does not require a TimesTen license if TimesTen is deployed as a cache layer in front of an already licensed Oracle Database.

Named User Plus licensing applies to standalone TimesTen deployments where the database is the primary system, not a cache. Each Named User Plus license costs $460, with annual support running approximately $101 per NUP per year. A deployment serving 75 users, therefore, requires 75 NUP licenses at an annual cost of $34,500, plus approximately $7,590 annually in support. This model works well for departments or subsidiaries running TimesTen as their primary data system without mainframe connectivity or distributed Oracle Database infrastructure.

The key distinction: processor licensing applies when TimesTen acts as a cache in front of Oracle or another primary database. Named User Plus licensing applies when TimesTen is the primary data repository and the named users are identified and countable. If you cannot identify the named users, or if usage is concurrent and not named, you must use processor-based licensing.

TimesTen does not require any other Oracle product license to operate standalone. Many enterprises mistakenly assume that a TimesTen license automatically requires an Oracle Database license. This is false. TimesTen is a fully functional in-memory relational database capable of managing transactions, persistence, replication, and analytics independently. The only exception is when you explicitly configure TimesTen Cache as a caching layer in front of Oracle Database, in which case you need separate Oracle Database licensing but no separate TimesTen license.

When TimesTen Is Bundled and Included for Free

Oracle offers TimesTen in two free editions, both subject to specific constraints that limit their use to non-production or single-user environments. TimesTen Express Edition (XE) is completely free under Oracle Free Use Terms and can be downloaded and deployed without a license agreement. However, XE is restricted to a single application instance and cannot be deployed in a cluster. For any enterprise system requiring high availability, failover, or multiple application instances, XE is unsuitable.

TimesTen Cache is also included free with Oracle Database Personal Edition, but Personal Edition itself is a single-user database licensed only for personal computer use and development. If you own an Oracle Database Personal Edition license, you do have the right to run TimesTen Cache against it at no additional cost. But Personal Edition is never appropriate for production or enterprise data systems.

The critical rule: TimesTen Cache as a database option (not as a cache in front of Oracle) requires an Oracle Database Enterprise Edition license. This is a common misunderstanding. If you want to use TimesTen Cache as your primary data engine and you require the caching optimizations TimesTen provides, you must purchase Oracle Database Enterprise Edition separately. This typically costs $47,500 per core and adds substantially to your total investment. Many enterprises deploy standalone TimesTen instead specifically to avoid this Oracle Database Enterprise Edition requirement.

The free TimesTen editions serve development teams and proof of concept work extremely well. The moment you move to production with high-volume transaction processing or real-time analytics, you transition to a paid TimesTen license (processor or NUP based) or you combine a paid Oracle Database license with the included TimesTen Cache option.

Deployment Scenarios and Total Cost Modeling

Real-world TimesTen costs depend entirely on deployment architecture. Three common scenarios illustrate the cost variations.

Scenario One: TimesTen as application-tier cache in front of Oracle Database. A telecom company runs authentication and session state in TimesTen Cache deployed on a 16-core server. The application server farms consume 64 cores total across four 16-core machines. Under the cache model, they do not need a separate TimesTen license because TimesTen Cache is included with their Oracle Database Enterprise Edition license covering the backend database. However, they already own that database license, so the incremental cost of adding TimesTen is zero. They pay for Oracle Database (which they need anyway) and deploy TimesTen as a cache layer within the same license.

Scenario Two: Standalone TimesTen in-memory database for real-time analytics. A financial services firm runs a credit scoring engine and bond pricing system in standalone TimesTen. They have 40 concurrent named users connecting to the system during trading hours. They purchase 40 TimesTen NUP licenses at $460 each for an initial cost of $18,400, plus $4,040 in annual support. They neither need nor want an Oracle Database license because their data requirements are fully met by TimesTen's in-memory store. Total first-year cost is approximately $22,440.

Scenario Three: Processor-based TimesTen for high-performance querying. An e-commerce platform deploying TimesTen on a 16-core Intel Xeon server for real-time product inventory and recommendation caching. Under processor licensing, they pay $23,000 per processor, multiplied by 16, equaling $368,000 for the TimesTen license. Annual support on this license runs approximately $80,960 (22% of initial license cost). Compare this to a NUP model: if they could identify 500 distinct users of the system, they would pay 500 times $460 equaling $230,000 for NUP licensing. In this case, processor licensing is more expensive, making NUP the correct model if usage is trackable by named user.

The pricing comparison to Oracle Real Application Clusters (RAC) is instructive. Oracle RAC and TimesTen typically cost approximately the same when comparing equivalent processing power and availability requirements. Both use processor-based licensing. Both include annual support at roughly 22% of the license cost. The difference is architectural: RAC scales to massive datasets on disk with caching, while TimesTen keeps everything in memory. For sub-microsecond response requirements, TimesTen is the necessary choice. For systems where disk residency is acceptable, RAC often provides better overall value at scale.

Support Costs, Bundling Effects, and Repricing Risk

TimesTen support costs approximately 22% of the license price annually for both processor and NUP models. On a processor license costing $23,000, annual support runs $5,060 per processor. On a 75-user NUP license costing $34,500, annual support runs $7,590. These support costs are mandatory if you are licensed; you cannot purchase TimesTen without also contracting for annual support.

Support pricing includes access to Oracle's TimesTen technical support team, patches and updates, and technical assistance with deployment, scaling, and troubleshooting. Unlike some Oracle products where you can defer support on legacy versions, TimesTen's support model is structured as an ongoing cost tied to active licensing.

When TimesTen is bundled with Oracle Database Enterprise Edition under the Cache model, Oracle does not charge separately for TimesTen support. The support cost on your Database license covers both products. However, if you are running standalone TimesTen on separate Customer Support Identifier (CSI) numbers from your Oracle Database, you will be billed separately for both TimesTen support and Database support. This structure creates an advantage to bundling: running TimesTen Cache within your existing Database license avoids the incremental support cost.

If you transition from standalone TimesTen to the Cache model and consolidate under a single Oracle Database Enterprise Edition license, your support costs decrease because you are no longer paying for dual support lines. However, you now incur the cost of upgrading your Database license to Enterprise Edition if you were previously running Standard Edition. This trade-off usually favors consolidation for large deployments, but for small deployments the incremental Database license cost outweighs the support savings.

Strategic Optimization: When to Reconsider TimesTen Architecture

TimesTen licensing optimization begins before purchase. Ask three foundational questions: Does your workload truly require in-memory processing, or could Oracle Database with the In-Memory option achieve similar performance? Does your system require named user identification, making NUP licensing cheaper than processor-based licensing? And can your application tier absorb the cache layer directly, allowing you to avoid a separate TimesTen license by using TimesTen Cache bundled with Database?

Enterprises in telecommunications (authentication, number portability, call center billing), finance (securities trading, fraud detection, online banking), web applications, travel logistics, and gaming frequently find TimesTen optimal. These workloads demand microsecond response times and cannot tolerate the latency of disk-based databases even with aggressive caching strategies. For these workloads, the TimesTen investment delivers measurable business value.

The comparison to Oracle Diagnostics and Tuning Pack is worth examining. Some enterprises attempt to optimize Oracle Database performance using Tuning Pack and advanced performance features, trying to achieve millisecond response where TimesTen delivers microsecond response. This approach rarely succeeds at production scale. If your SLA genuinely requires sub-millisecond performance, TimesTen licensing is inevitable. If your SLA accepts single-digit millisecond response, aggressive Database tuning may be cheaper than TimesTen.

For new deployments, engage with your Oracle account team early. Oracle sales engineers can help you evaluate whether TimesTen Cache bundled with Database, standalone TimesTen NUP, or processor-based TimesTen fits your use case. Getting this decision right before purchase is vastly cheaper than licensing incorrectly and then renegotiating.