Oracle Data Integrator (ODI) is an enterprise Extract-Load-Transform (ELT) tool in Oracle's Fusion Middleware suite, used to integrate data across diverse sources and deliver high-performance transformations for data warehouses, big data platforms, and enterprise applications. This advisory covers the complete licensing structure, NUP vs Processor models, editions and pricing, common compliance pitfalls including restricted-use traps, and optimisation strategies for ITAM professionals.
This guide is part of our Oracle Middleware licensing series. For the broader Fusion Middleware framework, see Oracle Fusion Middleware Licensing. For WebLogic licensing, see Oracle WebLogic Server Licensing. For database licensing, see Oracle Database Licensing Guide.
Oracle Data Integrator (ODI) is part of Oracle's Fusion Middleware suite. It is used to integrate data across diverse sources (relational databases, flat files, big data platforms, cloud applications, and enterprise systems) and deliver high-performance data transformations for data warehouses, business intelligence platforms, and operational applications.
Oracle Data Integrator licensing is separate from Oracle Database or other Oracle products. Organisations must purchase specific licences to deploy ODI in their environment. Unlike some Oracle products bundled with hardware or cloud services, on-premises ODI requires dedicated software licences.
ODI's core components (ODI Studio, ODI Agents both Standalone and JEE, the ODI repository hosted in an Oracle Database, and the ODI Console) must all be licensed for the environments where they run. Managing these licences is critical because ODI often runs on multiple servers and interacts with other Oracle software, introducing hidden licensing requirements.
First step: create an inventory of all ODI deployments (development, testing, staging, and production) and their associated components. This sets the foundation for choosing the right licensing model and avoiding compliance gaps.
Oracle Data Integrator is one of those products where the licensing complexity is disproportionate to what people expect. It is "just an ETL tool," but it comes with restricted-use WebLogic licences, optional add-ons for big data, a management pack for Enterprise Manager, and minimum NUP thresholds that catch people off guard. Because ODI interacts with databases, middleware, and often cloud services, the licensing boundary questions get complicated fast. We regularly find ODI compliance issues during assessments, not because clients were careless, but because the licensing rules are genuinely non-obvious.
Licences are based on the number of distinct users who have access to ODI, including human users and any automated process or service account that logs into ODI. Oracle enforces a minimum of 25 Named User Plus licences per processor on the server running ODI, regardless of how many users actually exist. For example, if ODI is installed on a server with two processors, at least 50 NUP licences are required, even if only 5 people use the system.
NUP licensing is typically cost-effective for development environments or small teams where user counts are low and well-defined.
Licences are based on the processing cores where ODI software is installed and running. This model allows an unlimited number of users on that server. Oracle uses the Processor Core Factor Table to determine how many licences are needed per core based on CPU type. Most x86 processors have a 0.5 core factor, meaning two cores count as one licence. Every physical or virtual core running an ODI agent or ODI server must be accounted for.
Processor licensing is ideal for high-throughput or broad deployments where user counts are large, undefined, or difficult to track reliably.
| Factor | Named User Plus | Processor |
|---|---|---|
| Best for | Small teams, development environments, well-defined user populations | Large deployments, high user counts, undefined or variable user populations |
| Cost driver | Number of named users (subject to 25/processor minimum) | Number of CPU cores multiplied by core factor |
| User limit | Only licensed users may access ODI | Unlimited users |
| Break-even point | Approximately 30 to 40 users per processor. Above this, Processor licensing is typically more cost-effective | |
| Tracking burden | Requires ongoing user count management and documentation | Simpler. No user tracking needed, but core counts must be accurate |
In VMware environments, Oracle typically requires licensing all physical cores in the host server, not just the vCPUs allocated to the VM running ODI. If ODI is deployed on VMware without proper hard partitioning, the licensing exposure can extend to the entire physical host, dramatically increasing costs under the Processor model. This is the single largest hidden cost risk for ODI deployments. Before deploying ODI on VMware, evaluate whether hard partitioning (Oracle VM, Solaris Zones) can limit the licensing scope to assigned resources.
Oracle Data Integrator is sold primarily as ODI Enterprise Edition, but Oracle offers several variations and add-ons that ITAM teams must be aware of. Each has distinct licensing implications.
| Product | Metric | List Price (USD) | Notes |
|---|---|---|---|
| ODI Enterprise Edition | Processor / NUP | $30,000 per processor; $900 per NUP | Core ODI functionality: Studio, agents, console, repository. The standard licence most enterprises need. Approximately 22% annual support on top |
| ODI for Oracle Business Intelligence | Processor / NUP | $23,000 per processor; $690 per NUP | Restricted to Oracle BI-related data loads only. Using it for general-purpose ETL violates the terms |
| ODI Advanced Big Data Option | Processor only | $3,000 per processor | Add-on for Hadoop, Spark, Hive, and Pig integration. Required if using ODI's big data features. Not covered by base ODI EE |
| Management Pack for ODI | Processor / NUP | $6,900 per processor; $205 per NUP | Optional pack for monitoring/managing ODI through Oracle Enterprise Manager. Must be licensed if the ODI plugin is enabled in OEM |
| Oracle Data Integration Suite | Processor only | $70,000 per processor | Bundle including ODI EE plus Oracle Enterprise Data Quality and additional integration tools. Cost-effective if you need both ODI and data quality |
Prices are Oracle list prices and do not reflect typical enterprise discounts. Always refer to Oracle's Global Price List for current figures. Oracle also offers Oracle Data Integrator Cloud Service as part of Oracle Cloud Infrastructure, licensed on a subscription model (OCPUs per hour or monthly) or via BYOL.
The most common ODI licensing mistake we see is the restricted-use violation. Organisations licence ODI for Oracle Business Intelligence at the lower price point, then gradually start using it for general-purpose ETL outside the BI context. Oracle's audit team knows exactly how to spot this. The price difference between $23K and $30K per processor might seem small, but when Oracle determines you have been using the wrong licence across a 20-processor environment for three years, with back-support, the true-up conversation gets very expensive very quickly. If you hold ODI for BI licences, audit your usage patterns to confirm they are strictly limited to BI-related data integration.
| Pitfall | What Happens | How to Avoid It |
|---|---|---|
| Undercounting processors or users | Licensing only the database servers that ODI pulls data from, while forgetting to licence the actual servers where ODI is installed. Or failing to count service accounts and missing the 25 NUP per processor minimum | Licence based on the ODI installation environment, not where data resides. Count every user and service account. Verify the 25 NUP minimum per processor is met |
| Violating restricted-use terms | ODI EE includes a restricted-use WebLogic Server Standard Edition licence intended only for the ODI web console. Using it for additional applications or HA clustering requires a separate full WebLogic licence. Similarly, the ODI for BI licence is restricted to Oracle BI-related data loads only | Document exactly which WebLogic features ODI is using. Never deploy the ODI-bundled WebLogic for non-ODI workloads. If using the ODI for BI licence, ensure it is strictly limited to BI data integration |
| Missing optional component licences | Using ODI's Hadoop/Spark integration without the Big Data Option ($3,000/processor). Or managing ODI through Oracle Enterprise Manager without the Management Pack licence ($6,900/processor) | Audit which ODI features are actually enabled and in use. Cross-reference against your licence entitlements. Disable features you have not licensed or procure the required add-ons |
| HA and DR oversights | ODI JEE agent clusters or multiple agents on different servers for load balancing: each active node must be fully licensed. Oracle's DR policy allows a backup site to run unlicensed for up to 10 days/year in failover, but active-active setups require full licensing on all nodes | Document your ODI architecture: every active node, standby, and failover configuration. Licence all active nodes. If using cold standby, ensure strict compliance with Oracle's 10-day DR policy |
| Assuming dev/test is free | Oracle requires a licence for any installed instance regardless of environment. Oracle Technology Network (OTN) licences are for personal learning only, not enterprise use. Many enterprises mistakenly believe development instances "do not count" | Licence every environment where ODI is installed unless specific contract terms (such as a ULA) provide coverage. Never assume dev/test is automatically free |
The WebLogic Server Standard Edition bundled with ODI is strictly for the ODI web console. If your team has deployed additional applications on that WebLogic instance, even "just one small app," you need a full WebLogic Server licence. Oracle's audit scripts will identify additional deployments on the application server. This is the single most common ODI compliance finding in Oracle audits. Conduct a quick check: list all applications deployed on the WebLogic instance that hosts the ODI Console. If anything beyond ODI is running there, you have a compliance exposure that needs immediate attention.
You do not need a single licensing model across all environments. Processor licensing for production (unlimited scalability) combined with NUP licensing for a small development environment with a handful of developers can yield significant savings. Maintain clear segregation between environments.
If your organisation uses multiple Oracle products, consider negotiating an enterprise agreement or ULA that includes ODI. Oracle sometimes bundles ODI in larger deals, particularly as part of the Data Integration Suite or with Oracle Analytics packages. Including ODI in a ULA allows unlimited deployment during the agreement term, but requires careful tracking and proper certification at exit.
Consolidating ODI processes onto fewer servers directly reduces processor licence requirements. If you have many small ODI installations, centralising them can be substantially cheaper, though performance and availability trade-offs must be evaluated. Conversely, ensure idle standby nodes qualify for Oracle's free failover allowance (cold standby, properly documented).
Track ODI users and installations using licence management tools or scripts. Reclaim licences when users depart or projects are retired. Staying on top of actual usage positions you better during Oracle contract renewals. You will know exactly what you need and what you do not.
Plan ODI licence purchases or true-ups to coincide with Oracle's fiscal year or quarter-end dates. Oracle sales teams may offer more generous discounts at these times. Maintain clear records of current licences and usage to support negotiations, and consider terminating support on unused licences to reduce ongoing costs.
The most impactful cost reduction for ODI licensing is server consolidation. Every server where ODI is installed requires its own set of licences (Processor or NUP). Reducing the number of servers from six to three halves the processor licence requirement. This is straightforward to calculate and often straightforward to implement, since ODI agents can typically be consolidated without significant architectural changes. Before purchasing additional ODI licences, evaluate whether consolidation can eliminate the need entirely.
| Recommendation | Detail |
|---|---|
| Map your ODI landscape | Create a detailed map of all ODI installations: versions, hardware, CPU core counts, and environment type (dev/test/prod). This is the foundation for correct licensing |
| Document user counts and access | Maintain a registry of Named Users with access to ODI, including service accounts and automated processes. Update regularly as people join or leave projects |
| Apply the Core Factor Table correctly | For Processor licensing, calculate required licences using Oracle's official Core Factor Table. Verify hardware core counts and types are correctly factored. This prevents both under-licensing and over-purchasing |
| Segregate environments | Use technical controls to prevent cross-environment usage. An unlicensed ODI component in test should never run production jobs. NUP licences in one environment should not be violated by usage in another |
| Review contracts for special clauses | Check Oracle agreements for ODI-specific terms: limited-use clauses, discounted bundling, or negotiated terms that could save money or create audit risk |
| Train your teams | Educate IT and development teams about what is included in ODI licences. Ensure they know that using big data features, certain connectors, or the WebLogic instance for non-ODI purposes requires additional licensing |
| Use monitoring tools | Implement scripts or tools that track ODI usage metrics: user logins, jobs run, agent uptime. This data supports compliance, capacity planning, and identification of unused licences that could be reassigned |
| Audit before Oracle audits | Conduct internal licence audits annually. Simulate an Oracle audit for ODI: verify licence counts, gather evidence, and proactively address gaps. Being audit-ready eliminates scrambling when the official notice arrives |
| Plan for growth | If expanding ODI usage (new projects, increased data volume, additional servers), incorporate licensing into planning. Switching models (NUP to Processor) or negotiating expansion in advance is more cost-effective than ad hoc purchases |
1. Inventory your ODI installations. List every server (physical or virtual) where ODI components are installed. Include CPU details (core counts and types), ODI version, and whether the server is production, test, development, or staging.
2. Count and classify your users. Identify all individuals and service accounts that access ODI. Determine active user counts. This informs whether NUP licensing is viable and ensures you meet the 25 NUP per processor minimum.
3. Validate current licences versus usage. Cross-check your inventory against purchased ODI licences. Are you licensed for the correct number of processors and/or users in each environment? Note any shortfalls or excess.
4. Review feature usage. Check: Are you using ODI for big data integrations (Spark/Hadoop) without the Big Data Option? Is ODI managed via Enterprise Manager without the Management Pack? Is the bundled WebLogic being used for more than just the ODI Console? Flag any usage that is not properly licensed.
5. Develop a remediation or optimisation plan. For gaps: procure additional licences or adjust usage. For excess: discuss with Oracle about optimising support fees or transitioning models. Implement governance so change management considers licence impact when adding ODI servers or enabling features.
The most expensive way to acquire Oracle licences is through an audit finding. List price with no volume discounts, plus backdated support, plus the loss of negotiating leverage. The five steps above take a few days of effort. They routinely identify six-figure compliance gaps and optimisation opportunities. Completing them before Oracle initiates an audit is the single highest-ROI compliance activity for any organisation running ODI.
ODI can be licensed by Named User Plus (per named user with a 25-user-per-processor minimum) or by Processor (per CPU core, applying Oracle's Core Factor Table). Most large deployments choose Processor licensing for unlimited users. Smaller teams may find NUP more cost-effective. The break-even point is typically around 30 to 40 users per processor.
Yes. Oracle requires a licence for any installed instance of ODI regardless of environment. Development, test, QA, and production all need coverage. Oracle Technology Network (OTN) developer licences are for personal learning only, not enterprise use. If you have an Oracle ULA or special agreement that covers multiple environments, verify the specific terms. The safe approach: licence every environment where ODI is installed.
ODI needs an Oracle Database (usually Enterprise Edition) to host the ODI repository. That database requires its own licence. For high availability, running the JEE agent on Oracle WebLogic Server with clustering requires licences for WebLogic Server Enterprise Edition and potentially Oracle Coherence. These are not included with ODI. If using big data connectors, you need the ODI Advanced Big Data Option. Account for all of these in your licence planning.
Optimise your licence model (NUP vs Processor) for each environment. Consolidate ODI deployments to fewer servers where feasible. Negotiate volume discounts or include ODI in an enterprise agreement. Terminate support on retired ODI instances to avoid ongoing fees. Stay compliant. Non-compliance penalties and forced audit purchases are always the most expensive way to acquire licences.
Oracle's auditors will request details on where ODI is installed, how many users have access, and evidence of licence purchases. They will verify server specifications (processor counts), check for unlicensed options (Big Data Option, Management Pack), and examine whether the restricted-use WebLogic is being used beyond its permitted scope. Having deployment diagrams, user lists, and licence purchase records ready makes the process far less painful. See our Oracle Audit Defence Service.
No. ODI includes a restricted-use WebLogic Server Standard Edition licence intended solely for the ODI web console. Deploying any additional applications on that WebLogic instance, even small or internal tools, requires a separate full WebLogic Server licence. This is one of the most common ODI compliance findings in Oracle audits. Check what is deployed on your ODI WebLogic instance immediately.
Oracle's VMware licensing policies apply to ODI just as they do to other Oracle products. In soft-partitioned environments like VMware, Oracle typically requires licensing all physical cores in the host server, not just the vCPUs allocated to the ODI VM. This can dramatically increase the licensing footprint. Hard partitioning (Oracle VM, Solaris Zones) is required to limit the licensing scope to the assigned resources. Before deploying ODI on VMware, evaluate the full licensing exposure.
Not sure whether your ODI, WebLogic, Coherence, or other Fusion Middleware deployments are fully compliant? Our licensing assessment identifies every Oracle product in use, quantifies compliance exposure, and develops optimisation strategies before Oracle's audit team does.
Oracle Licence ManagementIndependent licensing assessment. Compliance verification. Cost optimisation. Audit defence. 100% vendor-independent.