A buyer side guide to Oracle Data Integrator licensing in 2026. Why ODI follows middleware rules, how Processor and Named User Plus compare, and why agent sprawl is the real cost driver.
Oracle Data Integrator is licensed on the Processor metric or Named User Plus, and the catch is that it draws on the WebLogic and middleware licensing rules, not the database ones. The biggest cost surprises come from running ODI on the same servers as licensed databases and from agents spread across more hosts than anyone counted.
This guide is for data and integration leaders licensing Oracle Data Integrator in 2026. Read it with the Fusion Middleware licensing guide, the complete middleware licensing guide, and the Oracle Knowledge Hub.
ODI follows Oracle middleware licensing. You choose Processor or Named User Plus, and the metric applies to every host where ODI components run, including agents. It is not a database option.
Processor licensing counts cores times the core factor on each ODI host. Named User Plus counts individuals plus any non human operated devices, subject to a per Processor minimum. Pick the metric that fits your deployment shape.
ODI runs agents that execute integration jobs. Each host running an agent needs licensing. Agents spread across staging, production, and disaster recovery hosts are the most common source of undercounting.
ODI Enterprise Edition supports standalone and Java EE agents with different deployment footprints. The edition and the agent topology together decide how many hosts fall into scope.
The traps are deployment driven. ODI rarely costs more than expected because of the price. It costs more because it runs in more places than the license count assumed.
ODI deployment scenarios and licensing scope
| Scenario | Hosts in scope | Likely metric | Watch out for |
|---|---|---|---|
| Single agent, one host | 1 | Named User Plus | NUP minimum floor. |
| Agents on staging and prod | 2 plus | Processor | Staging often forgotten. |
| Prod plus disaster recovery | 2 plus | Processor | DR licensing rules. |
| ODI on a DB server | That host | Either | Not free with the DB. |
Consolidate agents, pick the metric that matches your user shape, and treat ODI as a separate product from the database it integrates. Each move reduces the host count or the metric cost.
Often yes. Fewer agent hosts means fewer licensed hosts under the Processor metric. Consolidate integration workloads onto a smaller, well sized footprint where the architecture allows.
Map your user population. A small, fixed set of integration developers favors Named User Plus if it clears the minimum. A broad or automated population favors Processor. The wrong metric overpays from day one.
Disaster recovery hosts can require licensing depending on how they are configured and how often they run. Apply the same failover and standby rules you would for the database tier. Document the configuration.
Oracle Data Integrator is priced like middleware and deployed like plumbing. The license follows the agents into every environment, and the bill is set by how many places you let them run.
Oracle Data Integrator is licensed under Oracle middleware rules on either the Processor metric or Named User Plus. The chosen metric applies to every host where ODI components, including agents, run.
No. ODI is a separate product. Running it on a server that already has a licensed database does not make ODI free. It requires its own licenses.
The same Oracle Core Factor Table applies. Core counts on each ODI host are multiplied by the processor factor, which is commonly 0.5 on x86, to derive Processor licenses.
Yes. Every host running an ODI agent falls into the licensing scope. Agents spread across staging, production, and disaster recovery are the most common cause of undercounting.
Choose Named User Plus when you have a small, well defined set of users and the count clears the per Processor minimum. For broad or automated populations, Processor is usually cheaper.
It can, depending on the configuration and how often the standby runs. Apply the same failover and standby rules used for the database tier and document the setup.
ODI Enterprise Edition supports standalone and Java EE agents with different deployment footprints. The agent topology, together with the edition, determines how many hosts are in scope.
Consolidate agent hosts, choose the metric that matches your user shape, and treat ODI as separate from the database. Fewer licensed hosts and the right metric are the main savings.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, middleware, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The standard advice is that ODI on a licensed database server costs nothing extra. We disagree. In the middleware reviews we have run, that assumption appeared in one of three estates and was wrong every time. The buyer side move is to license ODI as the separate product it is, and to count every agent host.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle licensing moves, audit posture, partitioning policy, and the buyer side levers we are running in client engagements. No noise.
