Canonical: https://molo17.com/solutions/replicate-to-oracle/ Markdown mirror: https://molo17.com/solutions/replicate-to-oracle/index.md Title: Replicate to Oracle in real time with Gluesync | MOLO17 Description: Real-time replication to Oracle Database from SQL Server, IBM i, MySQL, PostgreSQL, and MongoDB, with JDBC batches and array-bound bulk cycles. Start a trial. [Solutions](/solutions/) Replicate to Oracle SOLUTION · REPLICATE TO ORACLE # Real-time data replication to Oracle Database from your operational systems **Committed changes from your systems of record land in Oracle Database continuously, through JDBC batches and array-bound bulk cycles, instead of waiting for the next batch run.** Gluesync by MOLO17 captures changes from SQL Server, IBM i, MySQL, PostgreSQL, MongoDB, and other [heterogeneous sources](/integrations/?target=Oracle+Database#integration-finder) with a dedicated agent per database, then writes them to Oracle Database through a target agent built on the Oracle JDBC driver bundled with Gluesync. Snapshots seed each table first, CDC follows, and bulk cycles bind rows as arrays. Core Hub, the Gluesync control plane, runs every pipeline from one web UI and REST API. [Start a Gluesync trial](/get-gluesync/) [Talk to us](/contacts/) VENDOR COMPATIBILITY ## Battle-tested on every Oracle Database you deliver to The same Gluesync Oracle Database agent is tested against each vendor offering below, self-managed or fully managed, so delivery behaves the same wherever Oracle Database runs. - **Oracle Database** Source Target Tested - **Amazon RDS for Oracle** Source Target Tested - **Oracle Autonomous Data Warehouse** Source Target Tested - **Oracle Autonomous Database** Source Target Tested WHO THIS IS FOR ## Teams that need Oracle to reflect operations now, not after the nightly extract - Analytics and application engineers who need Oracle tables that match the source, with primary keys carried over, a reviewed `CREATE TABLE` generated from the source definition, and inserts, updates, and deletes applied in commit order - Data platform leads feeding Oracle from SQL Server, IBM i, MySQL, PostgreSQL, or MongoDB who want one Core Hub for every source instead of one connector per source, backed by [best-in-class enterprise support, rated 4.9/5 by customers](/support/#customer-ratings) - Architects and DBAs who decide which tables use native bulk load and which use optimized batches, which accounts and schemas the agent writes to, and how the agent connects to a single instance or a RAC cluster - Engineers replacing Kafka Connect JDBC sinks, scheduled export and import jobs, or hand-written PL/SQL load scripts with [one product for every source](/integrations/?target=Oracle+Database#integration-finder), with snapshots and monitoring built in THE PROBLEM ## Oracle data that arrives in batches is already behind Most Oracle targets are fed by scheduled jobs: an export and import run, an ETL tool, or a script extracts rows from the source, loads them, and merges them on a timer. Applications and reports then read the state at the last run, every extract adds load to a production database, and each source ends up with its own schedule and failure mode. Teams weighing a fix usually compare Oracle GoldenGate, Qlik Replicate, Fivetran HVR, Striim, a Debezium and Kafka stack with a JDBC sink, AWS Database Migration Service, or scripts they maintain themselves. Gluesync addresses that with **per-agent CDC into Oracle Database**. A source agent reads each database's native change mechanism, Core Hub routes the changes, and the Oracle target agent applies them with JDBC batches or staged bulk cycles. The pipeline model, the snapshot, and the operations stay the same whether the data comes from SQL Server, IBM i, or MongoDB. HOW IT WORKS ## How Gluesync writes to Oracle Database ### The write path: optimized batches and array-bound bulk load The Oracle target agents connect through the Oracle JDBC driver bundled with Gluesync, with TLS. Each agent is a target: it applies the change stream from any Gluesync source agent to your tables in real time, after a snapshot seeds each table. Gluesync never writes one row at a time; each entity uses one of two paths. - **Optimized batches, never row by row:** by default, changes are grouped into highly optimized SQL batches, which cuts round-trips to the listener and keeps load on the instance predictable. The chunk size is configurable on the target agent. - **Native bulk load:** switch it on per entity for the initial snapshot, for ongoing CDC, or both, and rows reach Oracle through array binding, as described below. See the [Oracle LogMiner agent overview ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-logminer-intro.html). ### Native bulk load for snapshots and CDC Bulk load is switched on per entity with two independent settings, one for the initial load and one for the ongoing change stream. Turn on one, the other, or both, on an existing entity without recreating it. In each mirroring cycle Core Hub collects the change events and collapses those on the same primary key: an insert followed by a delete is skipped, and consecutive updates become one update. The batch is bound as arrays into a global temporary staging table created `ON COMMIT PRESERVE ROWS`, which keeps network round-trips to a minimum; OracleBulkCopy is also available. Columns the source log omitted can be backfilled from the live table, then deletes and inserts are applied to the target table in one pass and the staging table is cleared. Each changed key lands as one current row. ### Snapshot first, then continuous CDC - **Seed, then stream:** each entity loads its full table into Oracle Database, then follows the source agent's change stream, applied in commit order per entity. - **INSERT or UPSERT:** INSERT with `TRUNCATE before snapshot` is the fast path for empty or reset tables. UPSERT merges the snapshot with rows that already exist in Oracle. - **On duplicate key:** Upsert, Skip, or Fail, set per entity. Oracle reports a duplicate as `ORA-00001`. Upsert overwrites the row, Skip keeps the row already in Oracle and raises a notification, and Fail stops the entity. - **Pre and post SQL:** commands can run before or after the snapshot and before or after CDC, for example to set session parameters or to clean up staging objects. ### Schema, types, and keys in Oracle - **Table creation:** when a target table does not exist, Core Hub generates a `CREATE TABLE` from the source columns, data types, and primary key, converted to Oracle syntax. You review and edit the statement before it runs. - **Type mapping:** each source value is normalized into a Gluesync data family and written in the closest representation the Oracle connector supports. Fixed-point values such as Oracle `NUMBER` keep their precision, and the Fields Editor shows the inferred target type for each column before you deploy. - **Data types:** user-defined data types are supported, and the Triggers agent handles all Oracle native data types. ### What your Oracle administrator sets up The agent needs a database user with write access to the target tables. Full connection fields and the custom host credentials are in the [Oracle target setup guide ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-logminer-target.html). 1. Create a user with `INSERT`, `UPDATE`, and `DELETE` on the target tables, plus `CREATE TABLE` where Gluesync creates tables. Bulk staging also needs DDL rights on the schema it uses. 2. In Core Hub, enter the host or SCAN name, the port (1521 by default), the database name, and the credentials, with TLS and the certificate path set when the listener uses TLS. 3. Set the custom host connection type to `SID` or `SERVICE_NAME`. Use the instance name for a named RAC instance, and use the wallet option with a wallet path when the team authenticates with an Oracle wallet. Then save the connection. ### Architecture around Core Hub Lightweight agents sit close to each source. Core Hub orchestrates them through its web UI and REST APIs and routes changes to the Oracle agent. A pipeline groups the source agents, the Oracle agent, and the entities they replicate. Core Hub and the agents deploy with Docker and Podman, Docker Compose, or Kubernetes. See [CDC streaming](/solutions/cdc-streaming/). [Explore the general CDC streaming architecture →](/solutions/cdc-streaming/) WRITE OPTIONS ## The Oracle target agents: one JDBC write path, three agents Oracle has three Gluesync agents that write to Oracle Database: LogMiner, XStream, and Triggers. All three use the Oracle JDBC driver, optimized SQL batches by default, and native array-bound bulk load for snapshots and CDC, switched on per entity. | Agent | Write technique | Versions | Best for | | --- | --- | --- | --- | | [Oracle LogMiner Agent ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-logminer-intro.html) | Oracle JDBC driver with TLS; optimized SQL batches by default; native bulk load with array binding into a staging table for snapshots and CDC | Oracle Database 11.2.0.4 and later, all editions, RAC supported | Oracle targets of any edition, including RAC clusters, fed from any Gluesync source. Optimized batches by default, and native array-bound bulk load for snapshots and CDC, switched on per entity. | | [Oracle XStream Agent ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-xstream-intro.html) | Oracle JDBC driver with TLS; optimized SQL batches by default; native bulk load with array binding into a staging table for snapshots and CDC | Oracle Database 11.2.0.4 and later, Enterprise Edition, RAC supported | Enterprise Edition Oracle targets, including RAC clusters, with the same write path and per-entity bulk settings as the other Oracle agents. | | [Oracle Triggers Agent ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-triggers-intro.html) | Oracle JDBC driver with TLS; optimized SQL batches by default; native bulk load with array binding into a staging table for snapshots and CDC | Oracle Database 11.2g and later, all editions, RAC supported | Oracle targets of any edition, with the same write path and per-entity bulk settings as the other Oracle agents. | SOURCES AND TOPOLOGIES ## Feed Oracle Database from the systems of record you already run Any Gluesync source agent can feed Oracle Database, each with its own native capture technique. Open the [integrations finder with Oracle pre-selected](/integrations/?target=Oracle+Database#integration-finder) to see every source you can pair with it. One Core Hub runs SQL Server to Oracle, IBM i to Oracle, and MySQL to Oracle side by side, with the same snapshot, monitoring, and write settings for each. Gluesync keeps pace with your change volume at any scale, and [MOLO17 Professional Services](/solutions/professional-services/) can help design the pipeline with your DBAs. - SQL Server to Oracle from the transaction log or Change Tracking, for Microsoft estates moving onto Oracle: see [SQL Server CDC](/solutions/sql-server-cdc/) - IBM i (AS/400) to Oracle through the native journal APIs, for operational Db2 data that feeds Oracle reporting: see [IBM i CDC](/solutions/ibm-i-cdc/) - MySQL to Oracle from the binary log, for consolidation of MySQL-family databases onto Oracle: see [MySQL CDC](/solutions/mysql-cdc/) - PostgreSQL to Oracle from the write-ahead log, for cross-engine moves: see [PostgreSQL CDC](/solutions/postgresql-cdc/) FAIR, HIGH-LEVEL COMPARISON ## Where Gluesync fits among Oracle ingestion approaches | Approach | What buyers usually get | Where Gluesync fits | | --- | --- | --- | | Oracle GoldenGate | Oracle's own log-based replication, a common choice for Oracle-to-Oracle replication | Oracle targets fed from any source under one Core Hub, with the same pipeline model for IBM i, SQL Server, MongoDB, and others. See [cloud migration](/solutions/cloud-migration/) | | Qlik Replicate, Fivetran HVR, and Striim | Commercial log-based replication with broad source and target catalogs; licensing and deployment differ by product | Native capture per engine, optimized batches and array-bound bulk load, and enterprise support from MOLO17 behind every pipeline | | Debezium, Kafka, and a JDBC sink connector | Open-source capture into Kafka topics, then a sink connector that writes to Oracle; you run Kafka, Connect, and the schemas, and usually add a step that turns change events into current-state tables | Changes applied to current-state Oracle tables with no Kafka cluster in the path, and Kafka still available as another target. Compare the [Debezium alternative](/solutions/debezium-alternative/) | | AWS Database Migration Service | Managed migration and replication that runs on a replication instance in AWS, typically used for database moves into AWS | Agents sit next to each source and write straight to Oracle, with the same product for every source under one Core Hub. See [migrating to Gluesync](/migrate-to-gluesync/) | | Managed ELT services | Managed connector catalogs with scheduled syncs; incremental and CDC modes vary by connector, and the sync schedule sets how fresh the data is | Changes applied as they arrive instead of on a sync schedule, with MOLO17 enterprise support behind every pipeline | | DIY scheduled jobs and PL/SQL scripts | Full control; your team owns the extract queries, the merge logic, retries, and the load each run puts on production | Log-based capture, staged bulk apply, and Core Hub monitoring without pipeline code to maintain; read [batch ETL vs real-time data replication](/blog/batch-etl-vs-real-time-data-replication/) | RELATED CONTENT ## Oracle replication background and implementation detail - [Oracle CDC: LogMiner, XStream, and triggers](/solutions/oracle-cdc/) - [Oracle LogMiner agent for Gluesync: real-time CDC for Oracle databases](/blog/oracle-logminer-agent-for-gluesync/) - [Oracle CDC: technical strategies and build vs buy](/blog/oracle-cdc-technical-strategies-build-vs-buy/) - [Batch ETL vs real-time data replication: how to choose](/blog/batch-etl-vs-real-time-data-replication/) - [Database offload: move read traffic off the system of record](/solutions/database-offload/) - [Cloud migration: migrate to cloud without a long cutover](/solutions/cloud-migration/) - [Oracle target setup guide ↗](https://docs.molo17.com/gluesync/latest/agents/oracle-logminer-target.html) - [Bulk load: staging and apply phases ↗](https://docs.molo17.com/gluesync/latest/core-hub/bulk-load.html) FAQ ## Oracle Database replication questions What does replicating to Oracle Database with Gluesync involve? A source agent captures committed changes from your database through its native change mechanism, Core Hub routes them, and the Oracle target agent applies them to your tables continuously after a snapshot seeds each table. Does Gluesync bulk load into Oracle Database? Yes, for the initial snapshot and for ongoing CDC, with a separate switch for each on every entity. Changes are collapsed per primary key, bound as arrays into a global temporary staging table, and applied to the target table in one pass. Without bulk load, the agent writes through the bundled Oracle JDBC driver in optimized SQL batches. Which sources can replicate to Oracle Database? Any Gluesync source agent, including SQL Server, IBM Db2 for i, MySQL, PostgreSQL, and MongoDB. The integrations finder on our website shows every source that pairs with Oracle. How are duplicate keys handled when replicating to Oracle? A duplicate key raises ORA-00001. The On duplicate key setting is applied per entity: Upsert overwrites the existing row and is the default, Skip keeps the row already in Oracle and raises a notification, and Fail stops the entity. What does the Oracle administrator need to set up? A user with INSERT, UPDATE, and DELETE on the target tables, plus CREATE TABLE where Gluesync creates tables. The connection type is set to SID or SERVICE\_NAME in Core Hub, and the default port is 1521. Can Gluesync create the tables in Oracle Database? Yes. When a target table is missing, Core Hub generates a CREATE TABLE from the source definition, converted to Oracle syntax, and you review it before it runs. Which Oracle versions and editions can Gluesync write to? Oracle Database 11.2g and later. The LogMiner and Triggers agents run on all editions, the XStream agent runs on Enterprise Edition, and all three support RAC clusters. How does an Oracle connection work in Core Hub? Enter the host or SCAN name, the port, the database name, and the credentials. Custom host credentials choose SID or SERVICE\_NAME, and the wallet and instance name options apply when the team uses an Oracle wallet or a named RAC instance. REPLICATE TO A TARGET ## Other targets Gluesync delivers to - [Replicate to Aerospike](/solutions/replicate-to-aerospike/) - [Replicate to DynamoDB](/solutions/replicate-to-dynamodb/) - [Replicate to Redshift](/solutions/replicate-to-redshift/) - [Replicate to Amazon S3 & S3-compatible](/solutions/replicate-to-amazon-s3/) - [Replicate to Cassandra](/solutions/replicate-to-cassandra/) - [Replicate to Kafka](/solutions/replicate-to-kafka/) - [Replicate to Cosmos DB](/solutions/replicate-to-cosmos-db/) - [Replicate to Azure Data Lake](/solutions/replicate-to-azure-data-lake/) - [Replicate to ClickHouse](/solutions/replicate-to-clickhouse/) - [Replicate to CockroachDB](/solutions/replicate-to-cockroachdb/) - [Replicate to Couchbase](/solutions/replicate-to-couchbase/) - [Replicate to file stores](/solutions/replicate-to-file-stores/) - [Replicate to BigQuery](/solutions/replicate-to-bigquery/) - [Replicate to Google Cloud Storage](/solutions/replicate-to-google-cloud-storage/) - [Replicate to Google Pub/Sub](/solutions/replicate-to-google-pubsub/) - [Replicate to GridGain](/solutions/replicate-to-gridgain/) - [Replicate to Db2](/solutions/replicate-to-db2/) - [Replicate to Informix](/solutions/replicate-to-informix/) - [Replicate to MariaDB](/solutions/replicate-to-mariadb/) - [Replicate to SQL Server](/solutions/replicate-to-sql-server/) - [Replicate to MongoDB](/solutions/replicate-to-mongodb/) - [Replicate to MySQL](/solutions/replicate-to-mysql/) - [Replicate to PostgreSQL](/solutions/replicate-to-postgresql/) - [Replicate to RavenDB](/solutions/replicate-to-ravendb/) - [Replicate to Redis](/solutions/replicate-to-redis/) - [Replicate to SAP ASE](/solutions/replicate-to-sap-ase/) - [Replicate to SAP HANA](/solutions/replicate-to-sap-hana/) - [Replicate to ScyllaDB](/solutions/replicate-to-scylladb/) - [Replicate to SingleStore](/solutions/replicate-to-singlestore/) - [Replicate to Snowflake](/solutions/replicate-to-snowflake/) - [Replicate to Solace PubSub+](/solutions/replicate-to-solace/) - [Replicate to Vertica](/solutions/replicate-to-vertica/) - [Replicate to YugabyteDB](/solutions/replicate-to-yugabytedb/) ## Evaluate Gluesync with your Oracle Database Start a trial on your own infrastructure, or talk to MOLO17 about your sources, the write path for each table, and how Oracle fits your replication plan. [Start a Gluesync trial](/get-gluesync/) [Talk to MOLO17](/contacts/)