Oracle OCI Data Catalog and Oracle Cloud Infrastructure Data Integration are managed data services that Oracle positions as cloud-native replacements for on-premise Oracle Data Integrator (ODI) and Oracle Enterprise Metadata Management. Understanding how their OCPU-based billing differs from ODI's Processor license model — and how they interact with your Oracle Database BYOL deployments on OCI — determines whether these services reduce your Oracle data integration costs or quietly increase them.
Oracle OCI Data Catalog is a managed cloud service that provides metadata harvesting, data discovery, business glossary management, and data lineage tracking for data assets across OCI and connected data sources. It is Oracle's answer to the enterprise data governance and metadata management use case — analogous to products like Collibra, Alation, or Microsoft Purview in function.
OCI Data Catalog pricing uses a dual-component model: metadata object storage charges and harvesting OCPU charges. The metadata object storage component is Oracle's most commonly cited "attractive" pricing point — metadata objects stored in the Data Catalog are priced at a low monthly rate per object (typically fractions of a cent per object per month), making the storage cost of even large enterprise data catalogs manageable. The harvesting component is where the cost adds up: when Data Catalog runs harvesting jobs to scan and catalog data sources — Oracle Autonomous Database, OCI Object Storage, Oracle Database on-premise via private endpoint, or external databases — it provisions OCPU compute for the harvesting process.
Harvesting OCPU charges depend on the frequency and scope of your harvesting schedules. An enterprise running daily incremental harvesting across 20 data sources (Oracle databases, OCI Object Storage buckets, and connected non-Oracle databases) might consume 2–4 OCPU-hours per day for harvesting — translating to $18–$36 per month at typical OCI compute rates. Full harvesting of large data sources (Oracle Database schemas with 10,000+ objects) can consume significantly more OCPU per harvest, particularly for the initial baseline harvest.
Harvesting Cost Model: Model your OCI Data Catalog harvesting cost based on (number of data sources) × (average objects per source) × (harvest frequency) × (OCPU-hours per harvest job). Oracle's Data Catalog pricing page presents the per-object storage cost prominently while the harvesting compute cost — which dominates the total for enterprises with frequent harvesting schedules — is a secondary disclosure. Build a full annual cost model before committing to OCI Data Catalog for enterprise-scale metadata management.
Oracle Cloud Infrastructure Data Integration (OCI DI) is Oracle's managed ETL/ELT service on OCI — a cloud-native data pipeline platform that allows enterprises to design, deploy, and run data transformation workflows without managing the underlying compute infrastructure. OCI DI is designed to replace or complement Oracle Data Integrator (ODI) deployments for organizations migrating data workloads to OCI.
OCI Data Integration billing has two primary components: workspace charges and task execution charges. An OCI DI workspace is the logical container for your data integration projects — holding your data assets, pipelines, and deployment configurations. Oracle charges a monthly fee per workspace — typically $35–$50 per workspace per month — regardless of usage. For enterprises with multiple development, test, and production workspace environments, workspace charges accumulate before a single pipeline has run.
Task execution is billed by the number of Integrated Pipeline Executions (IPEs) — each time an OCI DI data flow task executes, Oracle charges an IPE-based fee. The IPE pricing model charges per task execution rather than per OCPU-hour, which simplifies cost modelling for pipelines with predictable execution frequencies. However, for high-frequency pipelines (near real-time data loading every 5 minutes rather than batch-nightly), the IPE count multiplies rapidly. A single pipeline running every 15 minutes generates 96 executions per day — 2,880 per month. At Oracle's standard IPE pricing, the monthly execution cost for a single high-frequency pipeline can rival the monthly cost of an equivalent on-premise ODI license.
For data flows that require significant compute — large-volume transformations, complex SQL-intensive pipelines, or high-parallelism data loading operations — OCI DI also charges OCPU-hours for the compute consumed by the data flow execution engine. OCPU billing is additive to IPE billing for computationally intensive pipelines. Oracle's OCI DI documentation provides guidance on when data flows require OCPU billing versus using the standard IPE pricing model, but the boundary is not always obvious from the pipeline design interface — enterprises sometimes discover unexpected OCPU charges after a computationally intensive pipeline first executes in production.
The commercial decision between OCI DI and Oracle Data Integrator (ODI) on-premise is the central data integration licensing decision for Oracle customers. Oracle's sales teams consistently recommend OCI DI for cloud-first architectures while positioning ODI as legacy — but the total cost comparison is more nuanced than Oracle's cloud migration calculators suggest.
| Factor | OCI Data Integration | Oracle Data Integrator (ODI) |
|---|---|---|
| License model | Subscription (workspace + IPE/OCPU) | Perpetual (Processor metric, annual support) |
| Infrastructure cost | Included in OCI consumption | On-premise server + OS + database |
| Scaling cost | IPE/OCPU scales with pipeline volume | Fixed at Processor license count |
| High-frequency pipelines | IPE cost multiplies with frequency | Fixed regardless of execution frequency |
| BYOL compatibility | No ODI BYOL for OCI DI service | Can BYOL ODI to OCI compute instances |
| Development tools | Web-based visual designer | ODI Studio desktop application |
| On-premise source connectivity | Via OCI Data Connectivity Service | Native |
The break-even analysis between ODI perpetual license cost and OCI DI subscription cost depends heavily on pipeline execution frequency. For organizations with primarily batch-nightly data integration workloads — typical of Oracle Database to data warehouse patterns — OCI DI IPE pricing can deliver lower total cost than maintaining ODI perpetual licenses with 22% annual support. For organizations with high-frequency near real-time integration requirements, ODI's fixed Processor license cost often delivers lower total cost than OCI DI's per-execution pricing model.
Our Oracle Cloud & OCI Advisory team builds complete total cost of ownership models for ODI-to-OCI DI migration decisions — including the often-overlooked costs of Oracle Data Connectivity Service (the OCI managed agent required for OCI DI to reach on-premise Oracle Database sources), workspace charges, and high-frequency pipeline IPE costs.
OCI Data Catalog and OCI Data Integration interact with Oracle Database BYOL deployments on OCI in ways that affect Oracle license compliance — particularly for organizations that have migrated Oracle Database to OCI under BYOL and are using OCI data services to read from and write to those databases.
When OCI Data Catalog harvests metadata from an Oracle Database BYOL instance on OCI — scanning its schema objects, column definitions, and data types to populate the catalog — the harvesting process connects to Oracle Database using a JDBC connection. This connection is a Named User Plus metric connection in Oracle's license model: the Data Catalog service account connecting to Oracle Database counts as a Named User for NUP compliance purposes.
For Oracle Database instances licensed on the Processor metric (which has no per-user limit), this is not a concern. For Oracle Database instances licensed on Named User Plus metric — typically SE2 deployments or smaller EE deployments optimized for NUP cost — the Data Catalog service account must be included in your NUP count. Oracle's NUP minimum is 25 users per Processor (where applicable), so small NUP deployments often have headroom for additional service accounts. However, in large-scale OCI data platform deployments with multiple OCI data services accessing the same Oracle Database NUP instances, the service account counts can push NUP requirements above contracted quantities.
OCI Data Integration pipelines that query Oracle Database BYOL instances using SQL transformations, aggregations, or analytics queries may inadvertently trigger Oracle Database options compliance requirements. If an OCI DI pipeline submits a SQL query that Oracle's USMM captures as using Diagnostics Pack SQL monitoring features (Oracle AWR tracking SQL execution plans for OCI DI pipeline queries), this creates the same Diagnostics Pack license obligation as any other Oracle Database client tool generating SQL activity.
ODI/OCI DI to Oracle DB Options: Review your OCI DI pipeline SQL carefully before production deployment. Pipelines that use Oracle Database Parallel Query (a feature of EE not available in SE2), Oracle Partitioning for optimized access patterns, or Oracle In-Memory for transformation intermediate result storage require the corresponding Oracle Database options licenses on the target Oracle Database instance. Our Oracle Compliance Review service includes OCI DI pipeline SQL analysis as part of BYOL compliance assessments.
Our Oracle Cloud & OCI Advisory team builds accurate OCI DI and Data Catalog cost models — including workspace charges, IPE costs, OCPU billing, BYOL interactions, and ODI migration comparison.
A persistent source of Oracle data services licensing confusion is the distinction between OCI Data Integration and Oracle Integration Cloud (OIC). These are different products with different use cases and different pricing models — but Oracle's naming conventions and marketing presentations frequently blur the distinction for enterprise buyers.
OCI Data Integration is purpose-built for bulk data movement and transformation — ETL/ELT pipelines moving data between databases, data warehouses, OCI Object Storage, and data lake platforms. It is optimized for high-volume, asynchronous, batch-oriented data flows where transformation complexity and data volume are the primary design considerations. OCI DI has no API connectivity features and is not designed for real-time integration or application-to-application messaging.
Oracle Integration Cloud (OIC) is an iPaaS platform designed for application integration, API management, and process automation — the Oracle equivalent of MuleSoft, Dell Boomi, or Azure Logic Apps. OIC handles real-time integration between applications (Oracle ERP to Salesforce, for example), REST/SOAP API connectivity, and business process orchestration. OIC is priced on a message-based model (number of messages processed per hour) and per-integration design environment.
For Oracle Database-centric data platform work — moving data from Oracle Database ERP systems into Oracle Autonomous Data Warehouse for analytics — OCI Data Integration is the appropriate service. For connecting Oracle ERP to external SaaS applications, automating HR workflows between Oracle HCM and third-party payroll, or building API facades over Oracle Database data — OIC is the appropriate service. Using OIC for bulk ETL workloads is expensive relative to OCI DI due to OIC's per-message pricing; using OCI DI for real-time API integration is architecturally inappropriate and technically constrained. The cost impact of choosing the wrong service can be 3–5x the cost of the appropriate service at enterprise scale.
Both OCI Data Catalog and OCI Data Integration have meaningful cost optimization opportunities that most Oracle cloud deployments leave unexploited. The following strategies reduce OCI data service costs without compromising functionality.
Daily full harvesting of all data sources is Oracle's default recommendation but rarely necessary for most enterprise data catalog use cases. Review each data source's change frequency and harvest only at a frequency that matches the business need for catalog freshness. Static or infrequently-changed Oracle Database schemas (legacy on-premise ERP systems) can be harvested weekly or even monthly without degrading catalog value. Reducing harvesting frequency from daily to weekly for stable data sources can reduce OCI Data Catalog harvesting OCPU costs by 60–80% with negligible impact on catalog quality.
Consolidate near-real-time OCI DI pipeline requirements before using OCI Streaming (Kafka) or Oracle GoldenGate as change data capture intermediaries rather than running OCI DI pipelines at high frequency. An OCI DI pipeline that reads from an OCI Streaming topic (which captures Oracle Database changes via GoldenGate CDC) and executes every 15 minutes will accumulate 2,880 IPEs per month per pipeline. An alternative architecture using Oracle GoldenGate to stream CDC directly to the target (Autonomous Data Warehouse, OCI Object Storage) without OCI DI intermediate processing can deliver equivalent near-real-time analytics at lower OCI DI IPE cost — and sometimes at lower total OCI service cost depending on the GoldenGate pipeline pricing model.
OCI Data Catalog and OCI Data Integration costs are consumed from your OCI Universal Credit balance if you hold OCI Universal Credits. This means that OCI data service costs are discounted at whatever discount rate applies to your OCI Universal Credit commitment — typically 20–40% for enterprise commitments. Ensure your OCI budget model accounts for Universal Credit discount rates when comparing OCI data service costs to alternative on-premise or third-party ETL tool costs. The effective cost of OCI DI at a 30% Universal Credit discount is significantly lower than the list-price OCPU rate suggests. Our OCI Universal Credits guide explains how to optimize Universal Credit allocation across OCI services.
Oracle Data Catalog and OCI Data Integration create a small set of Oracle license compliance considerations that ITAM teams should document in their Oracle compliance position.
OCI Data Catalog's harvesting connections to Oracle Database instances on OCI BYOL must be counted as Named User Plus connections for NUP-metric Oracle Database licenses — as described in the BYOL interaction section above. For Processor-metric Oracle Database BYOL instances, no additional NUP counting is required.
OCI DI's ability to connect to on-premise Oracle Database sources via Oracle Data Connectivity Service (the managed agent Oracle deploys in your network for OCI DI on-premise connectivity) creates an interesting license scenario: the on-premise Oracle Database from which OCI DI extracts data is subject to its standard Processor or NUP license. The OCI DI service agent account connecting to that on-premise database counts as a Named User Plus user if your on-premise Oracle Database is NUP-licensed. For large-scale on-premise to OCI data migration projects using OCI DI, verify that your on-premise Oracle Database license allows for the service-account NUP requirement before deploying OCI Data Connectivity Service agents at scale.
Finally, OCI DI pipelines that use Oracle Autonomous Database as a target — loading transformed data into Autonomous Data Warehouse — are fully covered by the OCI Autonomous Data Warehouse subscription cost. There is no separate Oracle Database license requirement for loading data into OCI-provisioned Autonomous Data Warehouse instances. This is a genuine licensing advantage of the OCI-native data platform architecture versus hybrid architectures that mix on-premise Oracle Database with OCI data services. The Oracle Autonomous Database licensing guide on this site provides a complete overview of how Autonomous Database simplifies Oracle licensing for OCI data platform deployments.
OCI Data Catalog and OCI Data Integration costs are negotiated as part of your broader OCI Universal Credit or Oracle Cloud commitment deal rather than as standalone service contracts. This creates both a limitation (you cannot easily negotiate OCI DI workspace or IPE rates independently) and an opportunity (leveraging OCI DI requirements within a larger Oracle Cloud deal can improve your Universal Credit discount rate).
When building your OCI commitment deal, include OCI Data Catalog and OCI Data Integration cost projections in your Universal Credit consumption model. Oracle's account team will typically increase Universal Credit discount proposals when you present a credible, data-backed consumption model that demonstrates significant planned usage across multiple OCI services. A buyer who can show projected Universal Credit consumption of $500K per year across compute, database, storage, and data services is a better deal partner than a buyer presenting only compute and database figures.
For enterprises making the ODI-to-OCI DI migration decision, use the perpetual ODI license value as negotiating leverage. Oracle is highly motivated to migrate ODI perpetual license holders to OCI DI subscriptions — perpetual licenses generate only annual support revenue, while OCI DI subscriptions generate ongoing consumption revenue that Oracle's cloud metrics count more favorably. Oracle will sometimes offer extended OCI DI trial periods, ODI-to-OCI DI migration credits, or enhanced Universal Credit discounts in exchange for a commitment to retire ODI perpetual licenses and migrate to OCI DI. Approach this conversation strategically through our Contract Negotiation advisory service rather than accepting Oracle's initial migration offer at face value.
The logistics database consolidation case study illustrates how independent OCI cost analysis delivered $3.1M in savings for a client who had initially accepted Oracle's cloud migration cost model without challenge — a pattern we see consistently across OCI data services deployments.
Complete guide to Oracle cloud migrations — OCI DI vs ODI decision framework, Data Catalog cost modelling, BYOL portability rules, and Universal Credit negotiation frameworks. Free download.
Download Free GuideWeekly updates on Oracle OCI data service pricing changes, data integration licensing developments, ODI migration incentives, and Oracle Cloud cost optimization intelligence.
We provide independent OCI Data Catalog and Data Integration cost analysis — ODI vs OCI DI TCO modelling, BYOL interaction assessment, Universal Credit optimization, and OCI data services contract negotiation support.
Schedule a Confidential ConsultationRelated Resources