Oracle Data Integrator licensing in 2026. The license follows the agents.

Oracle Data Integrator Enterprise Edition lists at $30,000 per processor or $900 per Named User Plus, counted on every host that runs an agent. Most of the cost sits around it, in restricted WebLogic, repository databases and GoldenGate.

How is Oracle Data Integrator licensed in 2026?

Oracle Data Integrator (ODI) is licensed under Oracle's middleware rules, on either the Processor metric or the Named User Plus metric. The metric applies to every machine where an ODI component executes, which covers the agents as well as the console. ODI is not a database option, and it is never included with the database it loads.

This guide is for data and integration leaders who own an ODI renewal, an audit response or a platform decision. Read it with our Fusion Middleware licensing guide, the complete middleware licensing guide and the wider Oracle Knowledge Hub.

What do the two ODI metrics cost?

The list prices sit on the Oracle Technology Global Price List under Data Integration Technology. Support is charged at 22 percent of net license fees every year. The gap between the two metrics is much narrower than on the database, and that changes how you choose between them.

Divide $30,000 by $900 and one processor license costs the same as about 33 named users. Below that density, Named User Plus is cheaper. Above that density, Processor is cheaper and you stop counting people.

That is a low bar. A four core x86 host is 2 processors after the 0.5 core factor, so the Named User Plus route there starts at the 20 user minimum, $18,000, against $60,000 on Processor. Once that host serves more than about 66 users, Processor becomes the cheaper metric.

Why do the agents, and not the data volume, set the count?

ODI executes its work through agents, and every machine that hosts one is in scope, whatever volume of data passes through it. There are three agent types, plus load balanced groups, and each leaves a different footprint. Map all of them before you count anything.

• Java EE agent. Runs inside a WebLogic domain. This is the type that collides with the restricted use WebLogic license described below.
• Standalone agent. A lightweight Java process on its own host. It is cheap to deploy, which is exactly why these agents multiply.
• Standalone colocated agent. Managed through a WebLogic domain but running outside the container. Its host is still a licensed machine.
• Load balanced agent groups. Every member of the group is licensed, including members that only take work during a peak.

Which ODI entitlement do you actually hold?

Most organizations should hold Oracle Data Integrator Enterprise Edition. Oracle's Fusion Middleware licensing manual defines it as ODI plus Oracle Warehouse Builder Enterprise ETL. Older contracts often carry component entitlements with narrower rights, so read the product names on the order document before you assume anything.

• ODI Enterprise Edition. The full use ETL platform, excluding the technologies sold separately in the Application Adapters for Data Integration.
• Oracle Data Integrator for Oracle Business Intelligence. A restricted entitlement that arrives with BI and analytics purchases. It cannot be used as a standalone ETL tool.
• Application Adapters for Data Integration. Separately licensed connectors for packaged applications such as E Business Suite, Siebel and PeopleSoft.
• Oracle Warehouse Builder Enterprise ETL. Included in ODI Enterprise Edition, but you may only use it with a licensed Oracle Database Enterprise Edition.

What have we seen in recent ODI license reviews?

ODI exposure almost always came from where the product was deployed and what had arrived bundled with it. We handled roughly 15 to 25 Oracle middleware reviews between 2024 and 2025, and the ODI list price was rarely the problem. Three findings came up repeatedly.

• Agent hosts were undercounted. Licensed counts sat 30 to 50 percent below the real number of agent hosts. Disaster recovery and staging servers were the usual omissions.
• The database was assumed to cover ODI. In about 1 review in 3, the team believed the database license on the same server covered ODI. It never does.
• A bundled edition was running as the main ETL platform. Where ODI had come with a BI purchase, no one had checked which edition it was. In two cases a restricted entitlement was carrying the company's entire enterprise ETL workload.

None of these gaps appears in a renewal quote. They surface when Oracle's audit team, or your own review, lays the ODI topology next to the order documents.

What does the restricted use WebLogic inside ODI actually let you do?

It covers running the ODI Web Console and nothing else. Oracle's manual says an ODI Enterprise Edition license includes a restricted use license to WebLogic Server Standard Edition, limited 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.

What does high availability add to the bill?

The same manual states that a highly available ODI deployment requires separate licenses to Oracle WebLogic Server Enterprise Edition and to Oracle Coherence Enterprise Edition. That puts two more products on the same core counts. At list, WebLogic Server Enterprise Edition is $25,000 per processor and Coherence Enterprise Edition is $11,500.

Say you cluster the Java EE agent across two 8 core x86 hosts. Each host is 4 processors at the 0.5 factor, so the cluster needs 8 processors of each product.

The two products bought only to make ODI highly available cost $292,000 at list, more than the ODI licenses they support. Our Coherence licensing guide covers its editions, and the WebLogic Suite and Standard Edition comparison shows where each WebLogic edition stops.

Who pays for the Master and Work repositories?

You do, through a database license. ODI stores its Master and Work repositories in a relational database that sits outside the ODI license. Teams often drop the schemas into an existing Enterprise Edition instance without checking for 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. If the database is licensed on Named User Plus, every ODI developer and operator who connects to the repositories also counts toward that database's user total.

What if your ODI came with a BI or analytics purchase?

Then check the entitlement name before you build anything on it, because "it came with the product" is the assumption behind the costliest ODI findings we see. Oracle's Analytics Server licensing manual says Oracle Data Integrator for Oracle Business Intelligence may not be used on a standalone basis or as a standalone extract, transform and load tool.

• Permitted targets are narrow. A database used by Oracle Business Intelligence Applications, a database used exclusively by Oracle Analytics Server, Oracle Analytics Cloud or BI Foundation, or a staging database for those.
• Any other target is a breach. Loading a finance data mart, a customer data platform or a lakehouse with that entitlement is unlicensed use.
• The fix is a purchase. A configuration change does not cure it. You need full use ODI Enterprise Edition on the agent hosts, priced on the same cores you already run.
• The evidence is in the topology. The ODI repository lists every data server and schema it writes to, and an auditor can pull that with one query.

The analytics side of that boundary is covered in our Oracle Analytics Server licensing guide and the Oracle Analytics Cloud guide. If ODI feeds either product, read both before you scope the ETL license.

How many ODI licenses does a typical deployment need?

More than the production count suggests, because the license follows the agents into every environment. 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.

What does an undercount look like in practice?

Take a hypothetical company that licensed ODI for its single 16 core production agent host. That host is 8 processors, or $240,000 at list. The table shows what an honest inventory of the same deployment finds.

The shortfall is 10 processors, $300,000 at list, plus $66,000 a year in support on those licenses. An audit settlement usually also asks for back support on the gap, which is why finding it yourself first is cheaper.

Why negotiating the ODI processor count is the wrong place to start

The usual advice is to focus the ODI negotiation on the processor count, because that is where the list price lands. We disagree. In our middleware reviews across 2024 and 2025, the ODI license itself was rarely the largest line, and at $30,000 a processor it is one of the cheaper products Oracle sells.

The money sat around 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 no one had reviewed. Price that perimeter first. Then negotiate the ODI line, knowing what it is attached to.

Where do ODI and GoldenGate overlap, and where do you pay twice?

They overlap at change data capture, which is exactly where companies 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.

Which tool should own which job?

• GoldenGate for continuous replication. Low latency change capture and delivery, especially between heterogeneous databases.
• ODI for transformation and orchestration. Set based loads, dimensional builds and scheduled batch.
• Both together only with intent. If ODI calls GoldenGate for capture, you are licensing two products across two host populations.
• Never assume symmetry. GoldenGate counts source and target machines separately, so a feed that runs in one direction can still mean two sets of licensed hosts.

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.

How is Oracle Data Integrator licensed when it runs in the cloud?

The same way as on premises, 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. Moving an agent to a virtual machine does not stop that machine being licensed.

How are ODI agents counted in AWS and Azure?

Under Oracle's cloud licensing policy for authorized cloud environments, two vCPUs count as one processor when multithreading 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. The same four physical cores on premises would be 2 processors, or $60,000.

• Autoscaling groups. License the maximum configured capacity, not the average number of running instances.
• Ephemeral agents. A container that starts, runs a load and exits still ran on a machine. Count the host it ran on.
• Marketplace images. An ODI image on a cloud marketplace is usually Bring Your Own License, so it consumes entitlements you already hold.
• Cloud data integration services. OCI GoldenGate and the OCI Data Integration service are separately metered services. They are not ODI and do not draw on ODI entitlements.

Treat a lift and shift as a recount. The companies 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. Our note on authorized cloud core counting works through more instance sizes.

How do you check your own ODI license position?

Start in the ODI repository, because it records most of what an auditor will ask about. Then confirm the hardware behind each host and match both against the order documents. The sequence below takes a few days for a typical deployment.

1. List the physical agents. In ODI Studio, open Topology and expand Physical Architecture, then Agents. Each entry shows the host and port. Then confirm on each server which agents actually run, because entries go stale and cloned hosts keep copies of agent installs.
2. Read the session history. The Operator view in ODI Studio, or the SNP_SESSION table in the work repository, shows which agent ran each session and when. This is the fastest way to prove whether a standby agent has ever processed work.
3. List every data server. Under Physical Architecture, each technology shows its data servers and physical schemas. If you hold ODI for Oracle Business Intelligence, compare that list with the permitted targets above.
4. Review the knowledge modules. In Designer, check the journalizing knowledge modules in each project and among the global ones. Names containing OGG, such as JKM Oracle to Oracle Consistent (OGG Online), mean GoldenGate is in the picture.
5. Open the WebLogic domain. Read the domain's config.xml or the administration console. A cluster definition, or any deployment other than the ODI Web Console, falls outside the restricted use right.
6. Count the cores. On Linux, lscpu gives sockets and cores per socket. For virtual machines, record the physical hosts in the cluster as well as the VM size.

How do you reduce Oracle Data Integrator licensing cost?

Consolidate agents, choose the metric that matches the real population, and treat ODI as a separate product from everything it touches. Each step reduces either the host count or the metric cost, and none of them requires a negotiation with Oracle.

Can you consolidate agents to cut cost?

Usually yes, and it is the highest yield action available. Fewer agent hosts means fewer licensed processors, and most companies run agents on hosts chosen for convenience rather than capacity. Consolidating six lightly used standalone agents onto two properly sized hosts cuts the licensed host count by two thirds.

How do you pick the right metric?

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 ends the Named User Plus case in most automated integration environments, as our note on non human devices explains.

1. Inventory every host running an ODI agent across development, test, staging, production and disaster recovery.
2. Count physical cores and apply the factor from Oracle's processor core factor table to each host.
3. Compare that Processor total against a Named User Plus count that includes devices and the 10 per processor floor.
4. Price the surrounding products, WebLogic, Coherence and the repository database, before you call the number final.

How does disaster recovery affect ODI licensing?

It depends on whether the standby runs, and how often. Oracle's data recovery policy is narrow and time limited, and a warm standby with agents started is a running deployment. The rules that matter for ODI hosts are these.

• Failover. An unlicensed spare computer may run the programs for up to ten separate 24 hour periods in a calendar year, and only where the machines share one logical disk array in a single data center.
• Standby and remote mirroring. Every Oracle program installed or running at the second site must be licensed like production.
• Testing. The allowance to test on an unlicensed computer up to four times a year, for no more than two days each time, is written for the Oracle Database. Do not assume it covers ODI agents, and remember that installing ODI on a remote standby to test it already makes that host licensable.

Document the configuration, the failover test schedule and the days per year the standby is active. Our guide to disaster recovery licensing covers standby designs in the cloud.

Does dropping surplus licenses cut the support bill?

Less than the list price suggests. Oracle's technical support policies allow it to reprice support on the licenses you keep when you terminate part of a license set. Model the repriced support before you promise savings from consolidation, and read our guide to reducing Oracle support costs first.

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.

What will Oracle's account team say about ODI, and how should you reply?

Expect the conversation to widen from ODI to the middleware around it. These are the lines we hear most often in ODI discussions, with the reply that keeps the scope where it belongs.

• "High availability means you need WebLogic Suite." Reply that the ODI manual names two products, the Enterprise Editions of WebLogic Server and Coherence. At list the pair cost $36,500 per processor against $45,000 for WebLogic Suite, so price the named pair unless you need Suite features elsewhere.
• "Your ODI for Oracle Business Intelligence is running general ETL, so every agent host needs Enterprise Edition." Ask Oracle to show which data servers fall outside the permitted targets. Then separate those loads onto their own agent hosts and license those hosts only.
• "Your agents run in a VMware cluster, so every host in the cluster counts." Ask for the contract term that says so, and bring evidence of where the agent VMs actually ran. The VMware licensing guide sets out the arguments.
• "Fold this into a larger middleware agreement and the compliance question goes away." Settle the ODI finding on its own facts first. A bundle ties new spend to a gap that may be smaller than the first estimate.

What contract wording should you ask for?

• The exact product name. The order should say Oracle Data Integrator Enterprise Edition, so no one can later argue the rights are the BI edition's.
• Written WebLogic scope. Ask Oracle to confirm how it treats a Java EE agent deployed in the bundled domain, since the manual's wording covers the Web Console only.
• A price hold on growth. Fix the discount for additional ODI processors, and for WebLogic Server Enterprise Edition and Coherence, for a set period after signing.
• The agreed disaster recovery design. Record the standby configuration and its licensed status in the order, so a later auditor cannot reinterpret it.
• Support repricing protection. Ask that terminating surplus ODI processors after consolidation will not reprice the support on the licenses you keep.
• The cloud counting rule. Ask that the vCPU rule in force at signature applies for the term, because Oracle's policy documents can change.

What to do next

1. Name the entitlement. Read the order document and confirm whether you hold ODI Enterprise Edition or ODI for Oracle Business Intelligence. Everything else depends on the answer.
2. Inventory every agent. Cover development, test, staging, production and disaster recovery, with physical core counts per host.
3. Query the repository for targets. List every data server the topology writes to and compare it against what your entitlement permits.
4. Open the WebLogic domain. If the Java EE agent is clustered, price WebLogic Server Enterprise Edition and Coherence on those cores this quarter.
5. Check the knowledge modules and repositories. Any journalizing module that calls GoldenGate creates a GoldenGate obligation on source and target, and the database holding the repositories needs licensed capacity to spare.
6. Run both metric models. Compare Processor against Named User Plus, with devices counted and the 10 per processor floor applied.
7. Consolidate before you buy. Reducing agent hosts is cheaper than negotiating a discount on hosts you did not need.
8. Get an independent review before any middleware true up. Scope the conversation before Oracle scopes it for you.

Frequently asked questions