Two-way sync
Changes in InterSystems IRIS or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and OCI Database (Oracle Cloud) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between InterSystems IRIS and OCI Database (Oracle Cloud) continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both InterSystems IRIS and OCI Database (Oracle Cloud), so each workload runs on the engine that suits it.
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.
| InterSystems IRIS objects | OCI Database (Oracle Cloud) objects | |
|---|---|---|
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Views Read-only projections used to expose curated subsets to downstream systems | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Materialized views Precomputed result sets sometimes used as stable read sources for replication | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Schemas Namespace boundaries that scope which objects a sync connection can access | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Sequences Key generators that matter when writing new rows from external systems | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | |
| Views SQL views expose curated slices of data for outbound replication. | JSON collections Document-style storage in the converged engine, synced alongside relational tables |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–OCI Database (Oracle Cloud) connection.
Changes in InterSystems IRIS or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or OCI Database (Oracle Cloud) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or OCI Database (Oracle Cloud) record.
Track your InterSystems IRIS ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and OCI Database (Oracle Cloud).
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 InterSystems IRIS and OCI Database (Oracle Cloud) 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 InterSystems IRIS and OCI Database (Oracle Cloud) 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 InterSystems IRIS and OCI Database (Oracle Cloud): authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Persistent Classes and Globals), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the InterSystems IRIS side: Globals, Namespaces, Stored Procedures, Tables, plus custom fields where InterSystems IRIS exposes them. On the OCI Database (Oracle Cloud) side: PL/SQL procedures and packages, JSON collections, Partitions, Tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for InterSystems IRIS and OCI Database (Oracle Cloud): Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. Stacksync manages authentication, retries, and rate limits on both sides.
InterSystems IRIS: IRIS is multi-model: the same stored data can be accessed as relational tables via SQL, as persistent objects, and as multidimensional globals, so integrations usually standardize on the SQL projection. OCI Database (Oracle Cloud): OCI database services run the same Oracle Database engine as on-premises installs, so PL/SQL, sequences, and redo-log CDC behave identically to self-managed Oracle. Stacksync's field mapping accounts for these differences between InterSystems IRIS and OCI Database (Oracle Cloud) without custom code.
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 386 integrations available for InterSystems IRIS and OCI Database (Oracle Cloud).