Connecting Oracle Cloud to Data Hub

Many enterprise teams run Oracle Cloud for ERP, HCM, or SCM — but struggle to get unified visibility across those systems. Data Hub solves this by pulling Oracle Cloud data into iDataWorkers, where Cognify, Visualization Studio, and your AI agents can work with it alongside data from every other source.

What You Will Learn

How to set up the Oracle Cloud connector in Data Sync
How to authenticate with Oracle Cloud APIs
How to select and map Oracle modules
How to verify Oracle data in Data Hub

Prerequisites

Oracle Cloud instance with API access enabled
Service account credentials (client ID and secret)
Network access to your Oracle Cloud REST endpoints

Step 1: Prepare Oracle Cloud Access

In your Oracle Cloud console, create a service account for iDataWorkers:

Navigate to Identity & Security > Users
Create a new service user (e.g., idataworkers-sync)
Assign read-only roles for the modules you want to sync
Generate API keys and download the credentials file

Security note: Always use read-only service accounts. iDataWorkers never writes back to your source systems.

Step 2: Add the Oracle Cloud Connector

In iDataWorkers, go to Data Sync > + New Connection > Oracle Cloud. Enter:

Instance URL:   https://your-org.oraclecloud.com
Client ID:      idataworkers-sync
Client Secret:  ••••••••••••
Region:         us-ashburn-1

Click Test Connection. A successful test shows the available Oracle modules.

Step 3: Select Modules and Entities

Oracle Cloud organizes data into modules. Select the ones relevant to your analysis:

Financials — GL journals, AP/AR, invoices, budgets
Procurement — purchase orders, suppliers, contracts
HCM — employees, departments, compensation, headcount
SCM — inventory, shipments, warehouse data

For each module, drill into the available entities and select what you need. You can always add more later.

Step 4: Configure Sync Settings

For enterprise Oracle data, consider these settings:

Sync frequency: Daily for financials (data changes slowly), hourly for procurement (time-sensitive)
Historical backfill: Import last 12 months on first sync
Incremental sync: After backfill, only pull new and changed records

Step 5: Verify in Data Hub

Once the initial sync completes, open Data Hub and find your Oracle Cloud source. Browse the data, spot-check a few records against Oracle Cloud directly, and confirm field mapping is correct.

Now you can:

Build finance dashboards in Visualization Studio
Ask Cognify: “What is our AP aging by supplier?”
Set up agents to monitor budget variances

Conclusion

Oracle Cloud is now part of your unified data layer. Combined with data from other sources, you get cross-system visibility that Oracle Cloud alone cannot provide. Explore the Integrations Marketplace to connect more sources.