ODI Editions: Standard vs. Enterprise
Oracle Data Integrator is available in two distinct editions, each with different capabilities and licensing models. Understanding which edition you have licensed is fundamental to ensuring compliance, because the restrictions and use case boundaries differ significantly between them.
ODI Standard Edition is the entry-level offering. It provides core extract-transform-load (ETL) functionality for integrating data between databases, data warehouses, and business applications. Standard Edition is suitable for organizations with straightforward integration requirements, moderate data volumes, and simple data transformation logic. The licensing is priced at approximately $30,000 per processor at list price, or $900 per Named User Plus (NUP) with a 25-user minimum per processor.
ODI Enterprise Edition is the advanced offering that includes additional capabilities beyond Standard Edition. Enterprise Edition provides access to advanced big data connectors, complex transformation logic, performance optimization features, and enhanced integration with the broader Oracle ecosystem. Enterprise Edition is priced at a premium above Standard Edition—approximately $50,000 per processor at list price, depending on negotiation.
The critical compliance risk with ODI editions is that many organizations license Standard Edition for straightforward ETL use cases, then gradually expand their use of ODI to include capabilities that actually require Enterprise Edition. This expansion often happens incrementally and without explicit license procurement, which creates significant audit exposure when Oracle discovers the mismatch.
Licensing Metrics: NUP vs. Processor
ODI licensing is available under two distinct metrics: Named User Plus (NUP) and per-processor. Organizations must choose one metric and cannot mix metrics across the same deployment, though they can choose different metrics for different ODI instances in different geographical regions or business units.
NUP licensing is based on the number of named users who access the ODI system. At list price, NUP licenses cost approximately $900 per user for Standard Edition. The minimum purchase is 25 users per processor, which means that even if you have only 5 users, you must purchase 25 NUP licenses. This minimum is important for cost planning—a small pilot deployment with just a few users will still incur the cost of licensing 25 users.
Processor-based licensing is the alternative metric. At list price, Standard Edition costs approximately $30,000 per processor. A processor is a unit of measurement that generally aligns with the physical cores on the server where ODI runs, with some exceptions for virtualization. Processor licensing makes sense for large-scale deployments with many concurrent users, because the cost per user decreases as user count increases.
The decision between NUP and processor licensing depends on expected user scale and cost sensitivity. For small teams with fewer than 25 users, NUP licensing is likely more economical because you pay for 25 users regardless. For large teams with 100+ concurrent users, processor licensing becomes more attractive. Annual support costs escalate at 8 percent per year on net license fees, so the total cost of ownership compounds significantly over time.
The Automated Process Licensing Trap
One of the most significant ODI compliance risks is the treatment of automated processes that run without human intervention. Many organizations deploy ODI with scheduled jobs, batch processes, and automated integrations that run on timed schedules or event triggers. When these processes access the ODI system and execute within the ODI scheduler, they are considered named users for licensing purposes.
This means that if you have 20 scheduled jobs running nightly, and those jobs require separate ODI agent logins with separate credentials, you have potentially licensed 20 additional named users—even though no human being is viewing the ODI interface or manually initiating those jobs. The automation itself consumes licenses.
Many organizations do not realize this rule until they receive an Oracle audit notice. At that point, if they have 50 nightly jobs running under separate ODI logins, they owe back-license fees for 50 users worth of named user licensing, potentially spanning multiple years. The cost can reach hundreds of thousands of dollars for large-scale automated deployments.
The only way to avoid this exposure is to consolidate automated jobs to run under a single shared ODI agent login, or to ensure that your processor-based licensing is adequate to cover the scale of automation you are deploying. Documenting the design decision and your cost-benefit analysis of consolidation is critical for audit defense.
Restricted-Use WebLogic Server — and Its Boundaries
ODI Enterprise Edition includes a restricted-use license for WebLogic Server Standard Edition. This inclusion is significant because it allows organizations to deploy ODI on WebLogic infrastructure without purchasing separate WebLogic licenses. However, the word "restricted" is critical—you cannot use this WebLogic license for purposes outside the scope of running ODI itself.
The restricted-use WebLogic license permits you to install and run WebLogic Server solely to host the ODI web console and ODI application components. You cannot use it to deploy other applications, host custom Java applications, or run third-party software on the same WebLogic instance. If you attempt to use the WebLogic license for general application deployment, you have violated the licensing agreement and must retroactively license the full WebLogic Server platform for all prior use.
This restriction creates a common audit trap: organizations often discover during development or testing that they need WebLogic for other purposes, or they gradually expand their use of the WebLogic instance to host additional components. By the time an audit occurs, they have unwittingly expanded beyond the restricted-use boundary and owe full WebLogic licensing retroactively.
The safe approach is to treat ODI's included WebLogic license as a dedicated, single-purpose platform. If you need WebLogic for other purposes, purchase a separate full WebLogic Server license. Keep your ODI WebLogic instance logically and physically separated from any other WebLogic usage to minimize audit dispute risk.
ODI for BI vs. General ETL: Scope Risks
ODI is positioned as an ETL and data integration platform. However, depending on your ODI implementation approach, you may be using it in ways that technically extend beyond pure ETL and into business intelligence (BI) territory. Understanding the scope boundaries of your license is essential for compliance.
If you purchase ODI with the intent of using it for business intelligence analytics, reporting, or OLAP cube building, you need to ensure that your license specifically includes BI rights. Standard ODI licensing focuses on data movement and transformation. If you are using ODI primarily for BI purposes, you may need to license additional components or a different product altogether.
This becomes particularly relevant when organizations use ODI to populate data marts for analytics. If the purpose is purely to transform raw operational data and load it into a target database, that is standard ETL and within scope. But if the purpose is to populate a BI analytics database that drives business intelligence reporting, oracle may argue that your license scope should be different.
Documentation of your intended use case at the time of license purchase is critical audit defense. If you purchased ODI as an ETL platform and are using it solely for ETL purposes, that is defensible. If your use has shifted toward BI, you need to either adjust your licensing or realign your implementation to fit within your existing license scope.
ODI Advanced Big Data Option
ODI Advanced Big Data Option is a separately licensed component that provides native connectors and optimizations for Hadoop, Spark, and other big data platforms. If your ODI implementation includes connectivity to Hadoop clusters or Spark environments for data movement or transformation, you must determine whether you have properly licensed the Advanced Big Data Option.
Many organizations deploy ODI with Hadoop or Spark connectors without realizing that these are not included in standard ODI licensing. When an audit occurs, Oracle identifies the usage of these advanced connectors and claims that licensing for the Advanced Big Data Option was required from the moment of first use. The cost of retroactive licensing can reach tens of thousands of dollars, depending on deployment scale and duration.
If you are using or planning to use big data platform integrations, confirm explicitly with Oracle licensing that your implementation includes the Advanced Big Data Option. If not, either purchase the additional license or redesign your architecture to avoid direct ODI-to-Hadoop connectivity.
Repository Database Licensing
ODI requires a repository database to store metadata about integrations, job configurations, and execution history. This repository database must be licensed separately—the ODI license does not include the database itself. Most commonly, organizations use an Oracle Database repository, which requires its own Enterprise Edition or Standard Edition license.
This is a straightforward licensing requirement, but it is sometimes overlooked in cost calculations. A small ODI deployment might require only 2 processors of Oracle Database Standard Edition to host the repository, but many organizations underestimate repository database sizing and end up needing more capacity than anticipated. The repository database license cost can be as much as or greater than the ODI license itself, depending on repository size and performance requirements.
Document your repository database configuration and ensure that it is properly licensed. If you are using Oracle Database Enterprise Edition for your repository, that cost should be factored into your total cost of ownership for ODI.
ODI on Oracle Cloud (OCI)
Oracle Data Integrator is available as a managed service on Oracle Cloud Infrastructure (OCI). The licensing model for OCI-deployed ODI is different from on-premises ODI. OCI pricing is typically subscription-based and includes software licensing as part of the compute cost. Understanding the boundaries between included services and premium add-ons is critical for cloud cost management.
Some OCI ODI deployments include basic data integration capability at standard compute costs, while others require additional per-unit charges for advanced connectors or big data integration options. The pricing model and included capabilities vary by OCI service tier and configuration, so you should review your OCI contract and service terms to understand exactly what ODI capabilities are included in your subscription.
Common ODI Audit Triggers
ODI audits typically begin with Oracle's review of your ODI system logs, which record user authentication, job execution, and feature usage. Oracle's audit team will examine these logs to determine the number of named users, the frequency of automated job executions, and the use of advanced features like big data connectors.
Specific audit triggers include discovery of scheduled jobs with undisclosed user credentials, evidence of real-time BI queries against ODI-populated databases, usage of Hadoop or Spark connectors without Advanced Big Data Option licensing, and deployment of multiple ODI instances with overlapping processor counts across different geographic regions.
Priority Actions for ODI Compliance
1. Document your ODI edition and licensing metric. Create a spreadsheet that lists each ODI instance, its edition (Standard or Enterprise), its licensing metric (NUP or processor), and the number of licenses purchased. Cross-reference this against your Oracle ULA or license purchase agreements.
2. Inventory all named users and automated processes. Query your ODI system logs to identify every named user who has authenticated to ODI in the past year. Additionally, identify all scheduled jobs and automated processes that run under ODI agent credentials. Count both categories and ensure you have sufficient named user licenses for both.
3. Verify big data connector usage. If your ODI implementation connects to Hadoop or Spark environments, confirm that you have licensed the Advanced Big Data Option. If not, either purchase it or redesign your data integration architecture.
4. Separate your ODI WebLogic instance. Ensure that your ODI-inclusive WebLogic license is used only for ODI. If you need WebLogic for other purposes, purchase separate WebLogic licensing and deploy it on separate infrastructure.
5. Establish prospective license governance. Implement a change control process that requires licensing review before deploying new ODI features or adding new named users to your environment. Train your development and operations teams on ODI licensing boundaries to prevent future compliance issues.
Our Oracle licensing advisory specialists provide ODI compliance assessments and audit defence support. Visit the Oracle Knowledge Hub for related licensing guides.