Skip to main content

Supported Versions

  • Oracle Database 11g Release 2 and above
  • Oracle 12c, 18c, 19c, 21c

Variants

Required Privileges

Required Configurations

Connection Keepalive

Integrate.io keeps idle Oracle connections alive with TCP keepalive probes. The connect descriptor built from your host, port, and database includes EXPIRE_TIME=2, which sends a probe after 2 minutes of socket idleness:
This prevents connection resets (NJS-500 / NJS-501 ... read ECONNRESET) when a NAT gateway, firewall, or tunnel on the network path drops idle connections. The source connection can sit idle for several minutes during initial sync of a pipeline with many tables, so keepalive matters most there. The expireTime connection parameter controls the interval in whole minutes. Integrate.io rounds fractional values. Setting expireTime to 0 disables keepalive and connects with the plain host:port/database form instead. Keepalive applies only to the connect descriptor that Integrate.io builds. If you configure an explicit connectString, Integrate.io uses it unchanged. The auto-built descriptor is TCP-only, so TCPS (TLS) connections require an explicit connectString. Add EXPIRE_TIME to that string yourself if you want keepalive.

Data value handling

Oracle LogMiner renders every value in a redo log statement as a quoted literal. The redo log alone does not distinguish a numeric column from a string column that holds digits. Integrate.io ELT & CDC resolves each value against the column type in your source schema:
  • NULL column values in UPDATE and DELETE operations replicate as NULL in the destination. You do not need to take any action.
  • VARCHAR2 and CHAR values that contain only digits, such as '86296' or '007', replicate as strings. Integrate.io ELT & CDC preserves leading zeros and trailing spaces.
  • NUMBER, BINARY_DOUBLE, and BINARY_FLOAT values replicate to numeric destination columns. This includes values that LogMiner renders in non-canonical form, such as .5 or 1.0E+020.
  • A value that cannot be represented in the destination column type causes the sync to report an error instead of writing an altered value.
For example, this Oracle row replicates with ALT_RES_ID as the string 86296 in the destination when the column is declared as VARCHAR2:

History Mode (SCD Type 2)

Oracle sources support History Mode. When enabled for a table, Integrate.io retains every version of each record in the destination with _iio_active, _iio_start, and _iio_end tracking columns. The _iio_start timestamp comes from the LogMiner change timestamp in the redo log, so it reflects when the change happened in Oracle. History Mode requires ALL-column supplemental logging on each tracked table. Without it, an UPDATE captures only the changed columns and the historical version is stored with the remaining columns empty. Those partial versions are retained permanently and a resync does not repair them. Enable ALL-column supplemental logging at the database level or per table:
Connection validation reports this as a separate step, Checking ALL-column supplemental logging (History Mode / SCD2). Pipelines that do not use History Mode are not blocked by it. MINIMAL or PRIMARY KEY supplemental logging alone is not sufficient for History Mode. For a table covered only by the database-level setting, DBA_LOG_GROUPS is empty. Verify the database-level setting with:
Notes:
  • LogMiner reads redo logs to capture INSERT, UPDATE, DELETE operations
  • Continuous sync replicates committed transactions only. Changes from rolled-back transactions never reach the destination.
  • Integrate.io delivers changes in commit order. A long-running transaction arrives after it commits, so it can increase replication lag until then.
  • SELECT ON V_$TRANSACTION is optional. Without it, continuous sync still works, but Integrate.io can miss changes from a transaction that stays open across multiple sync polls.
  • CLOB/BLOB columns are automatically converted to strings/buffers
Last modified on October 27, 2026