Oracle Data Integrator Enterprise Edition lists at $30,000 per processor or $900 per Named User Plus, and it is licensed on the machines its agents run on. The expensive parts are the restricted use WebLogic inside it and the products around it.
Oracle Data Integrator Enterprise Edition lists at $30,000 per processor or $900 per Named User Plus, and it is licensed on the machines its agents run on, not on the data it moves. The expensive parts are the restricted use WebLogic inside it, the repositories underneath it, and the GoldenGate that often sits beside it.
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 is licensed under Oracle middleware rules on either Processor or Named User Plus, and the metric applies to every machine where an ODI component executes. That includes agents, not just the console. It is not a database option and it is never included with the database it loads.
The list prices sit on the Oracle Technology Global Price List under Data Integration Technology. The ratio between them is much tighter than on the database, which changes the metric decision materially.
Oracle Data Integrator Enterprise Edition, list prices
List and before discount. Support is charged at 22 percent of net license fees each year.
| Metric | License at list | Annual support | Minimum |
|---|---|---|---|
| Processor | $30,000 | $6,600 | 1 processor |
| Named User Plus | $900 | $198 | 10 users per processor |
| GoldenGate, for comparison | $17,500 per processor | $3,850 | 10 users per processor |
Breakeven: $30,000 divided by $900 is about 33 named users per processor. Above that density, Processor is cheaper.
Thirty three users is a low bar. A four core x86 host is 2 processors after the 0.5 core factor, so the Named User Plus alternative is 20 users at $18,000 against $60,000 on Processor. Add a second team and Processor wins.
ODI executes work through agents, and every machine hosting one is in scope. There are three shapes and they carry different footprints. Map all three before you count anything.
Most estates should be on Oracle Data Integrator Enterprise Edition, which Oracle's Fusion Middleware licensing manual defines as ODI plus Oracle Warehouse Builder Enterprise ETL. Older estates carry component entitlements that do not grant the same rights.
White Paper · Oracle Middleware
Oracle Fusion Middleware Licensing
WebLogic, SOA and Coherence, priced. Read it free.
It lets you run the ODI Web Console and nothing else. Oracle's licensing manual states that a license to ODI Enterprise Edition includes a restricted use license to WebLogic Server Standard Edition, restricted to running the ODI Web Console, and that any other use requires a full use license. Architects read the words "includes WebLogic" and stop there.
The same manual is explicit that separate licenses to Oracle WebLogic Server Enterprise Edition and Oracle Coherence Enterprise Edition are required for a highly available ODI deployment. That is two more products on the same core counts. At list, WebLogic Server Enterprise Edition is $25,000 per processor before you price Coherence.
What the ODI bundle covers, and what it does not
| What you are doing | Covered by ODI Enterprise Edition? | What you need instead |
|---|---|---|
| Running the ODI Web Console on the bundled WebLogic | Yes | Nothing further |
| Clustering the Java EE agent for high availability | No | WebLogic Server Enterprise Edition and Coherence Enterprise Edition, full use |
| Deploying any other application into that WebLogic domain | No | Full use WebLogic on those cores |
| Master and Work repositories in an Oracle database | No, never bundled | A licensed Oracle Database on that host |
| Using Oracle Warehouse Builder Enterprise ETL | The software is included | A licensed Oracle Database Enterprise Edition as prerequisite |
| Change data capture through GoldenGate knowledge modules | No | A full GoldenGate license on every source and target |
ODI stores its Master and Work repositories in a relational database, and that database is not part of the ODI license. Teams drop the schemas into an existing Enterprise Edition instance without checking spare licensed capacity. If the schemas justify a new host, a new core, or a new option, that is a database line on the order.
The sentence is "it came with the product." If your ODI arrived with an analytics or BI purchase, check the entitlement name before you build anything on it. Oracle's Analytics Server licensing manual states that Oracle Data Integrator for Oracle Business Intelligence may not be used on a standalone basis or as a standalone extract, transform and load tool.
The analytics side of that boundary is set out in our Oracle Analytics Server licensing guide and the Oracle Analytics Cloud guide. If ODI feeds either of them, read both before you scope the ETL license.
They are deployment driven. ODI rarely costs more than expected because of its price. It costs more because it runs in more places than the license count assumed, and because of what has to be bought around it.
ODI deployment scenarios and licensing scope
| Scenario | Hosts in scope | Likely metric | Watch out for |
|---|---|---|---|
| Single standalone agent, one host | 1 | Named User Plus | The 10 user per processor floor |
| Agents on staging and production | 2 or more | Processor | Staging is the most forgotten host |
| Production plus disaster recovery | 2 or more | Processor | Only a cold, unstarted standby escapes |
| ODI installed on a database server | That host | Either | Never free with the database |
| Java EE agents in a WebLogic cluster | Every node | Processor | Full use WebLogic and Coherence on top |
| Agents on a shared VMware cluster | Potentially every host | Processor | The partitioning policy decides the boundary |
They overlap at change data capture, and that is exactly where estates pay twice without meaning to. ODI ships journalizing knowledge modules that use Oracle GoldenGate to capture changes at source. Using them requires a GoldenGate license in its own right, on every machine where data is captured or delivered.
We cover the replication side in the Oracle GoldenGate licensing guide and the heterogeneous cases in GoldenGate for non Oracle databases. Read those before you decide which product owns capture, because the decision is commercial as much as technical.
The same way, with a different counting rule. ODI in a public cloud is still your license on someone else's hardware, so the entitlement travels but the arithmetic changes. Nothing about moving an agent to a virtual machine makes it stop being a licensed machine.
Under Oracle's cloud licensing policy for authorized cloud environments, two vCPUs count as one processor when multi threading is enabled, and the processor core factor table does not apply. An eight vCPU agent host is four processors, or $120,000 at list, with no 0.5 reduction available.
Treat a lift and shift as a recount, not a migration. Estates that moved ODI agents to cloud instances without redoing the arithmetic are the ones we most often find short, because the vCPU rule removes the core factor discount that made the on premises number acceptable.
Consolidate agents, choose the metric that matches the population, and treat ODI as a separate product from everything it touches. Each of those moves reduces either the host count or the metric cost, and none of them requires a negotiation.
Usually yes, and it is the single highest yield action available. Fewer agent hosts means fewer licensed processors, and most estates run agents on hosts chosen for convenience rather than capacity. Consolidating six lightly used standalone agents onto two properly sized hosts is a two thirds reduction.
Count the humans, then count the machines that trigger jobs. Named User Plus counts non human operated devices as users, so a scheduler, an API caller or an upstream application can each become a countable user. That definition kills the Named User Plus case in most automated estates.
It depends on whether the standby runs and how often. Oracle's failover allowance is narrow and time limited, and it does not cover a warm standby that has agents started. Document the configuration, the failover test schedule, and the days per year the standby is active.
The common advice is to focus the ODI negotiation on the processor count, because that is where the list price lands. We disagree. In the middleware reviews Fredrik Filipsson ran across 2024 and 2025, the ODI license itself was rarely the largest line: at $30,000 a processor it is one of the cheaper things Oracle sells. The money was in what surrounded it, a full use WebLogic and Coherence pair bought to make the agents highly available, a database bought to hold repositories, and a GoldenGate license triggered by a knowledge module nobody had reviewed. Negotiate the ODI estate, not the ODI SKU, and price the perimeter before you argue about the middle.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
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.
ODI is licensed under Oracle middleware rules on either Processor or Named User Plus, and the metric applies to every machine where an ODI component runs, agents included. ODI Enterprise Edition lists at $30,000 per processor and $900 per Named User Plus.
No. ODI is a separate product on the Technology Price List, and installing it on a licensed database server grants nothing. The reverse is also true: the database holding the ODI repositories needs its own license.
No. The bundled WebLogic Server Standard Edition is restricted to running the ODI Web Console, and any other use requires a full use license. Oracle's manual also states that a highly available ODI deployment requires separate WebLogic Server Enterprise Edition and Coherence Enterprise Edition licenses.
Yes. Every host running an agent falls into scope, whatever the agent type. Standalone agents are the usual source of undercounting because they are trivial to deploy and nobody records them.
Only when the total population, including non human operated devices, stays below roughly 33 per licensed processor and above the 10 per processor floor. Because schedulers and calling applications count as users, most automated integration estates fail this test and belong on Processor.
It is a restricted entitlement that arrives with BI and analytics purchases, and it may not be used on a standalone basis or as a standalone ETL tool. Permitted targets are limited to databases used by Oracle BI Applications or exclusively by Oracle Analytics, plus their staging databases. Using it as a general ETL platform is unlicensed use.
Only if you use change data capture through the GoldenGate knowledge modules, or need continuous low latency replication. That use requires a full GoldenGate license on every machine where data is captured or delivered, which is a separate estate from the ODI agent hosts.
Usually yes. Oracle's failover allowance is narrow and time limited, and a standby with agents started is a running deployment. Document the configuration, the failover test days per year, and whether the standby node ever processes work.
The standard Oracle core factor table applies, so processor licenses equal physical cores times the factor for that chip, rounded up. On current x86 the factor is 0.5, so a 16 core host is 8 processors, or $240,000 at list.
Consolidate agent hosts onto fewer, properly sized machines, and confirm the metric matches the real population. Then price the perimeter, WebLogic, Coherence, the repository database and any GoldenGate use, because that is usually where the money actually is.
The middleware layer is licensed like the database, per processor with the core factor, but the bundles pull you up to the $120,000 Suite. The edition ladder and how to license to need.
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.
