Two-way sync
Changes in DuckDB or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Oracle Fusion Cloud HCM in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Oracle Fusion Cloud HCM is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. DuckDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments, Jobs in Oracle Fusion Cloud HCM need to exist as queryable Attached databases, Database files, Schemas, Tables in DuckDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Attached databases, Database files, Schemas, Tables in DuckDB with Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments, Jobs in Oracle Fusion Cloud HCM field by field, in real time. You decide which system owns which fields — Oracle Fusion Cloud HCM typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments, Jobs replicate into DuckDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Oracle Fusion Cloud HCM stay consistent in DuckDB, so hierarchy-driven logic and permissions don't drift.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| DuckDB objects | Oracle Fusion Cloud HCM objects | How this pairing syncs | |
|---|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Workers (publicWorkers) Person master with personNumber, names, national IDs, and work relationships; synced two-way via the /workers resource, which replaced the desupported /emps resource. | Attached databases is specific to DuckDB and Workers (publicWorkers) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Assignments Child of a worker's work relationship carrying job, position, department, location, grade, and manager; effective-dated, so writes go through PATCH with an effective date. | Database files is specific to DuckDB and Assignments to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. | Schemas is specific to DuckDB and Jobs to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. | Tables is specific to DuckDB and Positions to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | Departments (Organizations) Org-structure records that define cost centers and reporting lines; typically mastered in HCM and read into other systems. | Views is specific to DuckDB and Departments (Organizations) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Locations Physical work locations referenced by assignments; synced so downstream provisioning and directory tools resolve the same location codes. | External files (Parquet/CSV/JSON) is specific to DuckDB and Locations to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is written to Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Oracle Fusion Cloud HCM are captured at the source via change data capture — no polling loop against its API. Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change).
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Oracle Fusion Cloud HCM connection.
Changes in DuckDB or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Oracle Fusion Cloud HCM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Oracle Fusion Cloud HCM record.
Track your DuckDB ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Oracle Fusion Cloud HCM.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate DuckDB and Oracle Fusion Cloud HCM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the DuckDB and Oracle Fusion Cloud HCM objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Oracle Fusion Cloud HCM: authenticate both systems, choose the objects to sync (such as DuckDB's Attached databases and Database files), map fields visually, and changes propagate both ways in milliseconds — no code required.
DuckDB: DuckDB runs in-process like SQLite; there is no server, so integrations embed the engine or operate on the single-file databases it produces. Oracle Fusion Cloud HCM: REST access is secured by Oracle Web Services Manager and requires OAuth 2.0, HTTP Basic, or SAML/JWT bearer over SSL; each caller's data is scoped by HCM security roles and data-security profiles. Stacksync's field mapping accounts for these differences between DuckDB and Oracle Fusion Cloud HCM without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DuckDB and Oracle Fusion Cloud HCM records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Oracle Fusion Cloud HCM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Oracle Fusion Cloud HCM integration in-house.
Yes — Stacksync ships production-grade connectors for both DuckDB and Oracle Fusion Cloud HCM. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Oracle Fusion Cloud HCM: Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change); REST q= filters on LastUpdateDate and HCM Extract in incremental mode cover broader deltas. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 447 integrations available for DuckDB and Oracle Fusion Cloud HCM.