Overview
Wirekite supports Oracle 11g and above as a target database for:- Schema Loading - Create target tables from Wirekite’s intermediate schema format
- Data Loading - Bulk load extracted data into Oracle tables
- Change Loading (CDC) - Apply ongoing changes using MERGE operations
Oracle loaders use OCI (Oracle Call Interface) for high-performance bulk loading. The Change Loader uses shadow/merge tables for atomic change application.
Prerequisites
Before configuring Oracle as a Wirekite target, ensure the following requirements are met:Database Configuration
- Version: Oracle 11g or above
- User Permissions: Create a dedicated Wirekite user with:
- CREATE TABLE privilege
- INSERT, UPDATE, DELETE on target tables
- Read/write access to Wirekite internal tables (
wirekite_progressandwirekite_action)
File System Access
- Ensure the user running Wirekite has write permissions to the work directory
- Verify sufficient disk space for intermediate files during change loading
Schema Loader
The Schema Loader reads Wirekite’s intermediate schema format (.skt file) and generates Oracle-appropriate DDL statements for creating target tables.
The Schema Loader generates both base tables and merge tables (with
$wkm suffix) for CDC operations.Required Parameters
Path to the Wirekite schema file (
.skt) generated by the Schema Extractor. Must be an absolute path.Output file for CREATE TABLE statements. Includes both base tables and merge tables for CDC operations.
Output file for constraint definitions (indexes, unique constraints, check constraints).
Output file for FOREIGN KEY constraints. Can be applied after initial data load for better performance.
Absolute path to the log file for Schema Loader operations.
Optional Parameters
Output file for DROP TABLE IF EXISTS statements. Set to “none” to skip generation.
Output file for recovery table creation SQL. Set to “none” to skip.
When
true, generates merge tables ($wkm suffix) for CDC operations. Set to false if only doing data loads without change capture.When
true, only creates merge tables, skipping base table creation. Useful for bounce-back scenarios.Data Loader
The Data Loader reads Wirekite’s intermediate data format (.dkt files) and loads records into Oracle target tables using high-performance OCI bulk operations.
Required Parameters
Path to a file containing the Oracle connection string.
Directory containing data files (
.dkt) to load. Files are processed in parallel based on maxThreads.Path to the Wirekite schema file used by Schema Loader. Required for table structure information.
Absolute path to the log file for Data Loader operations.
Optional Parameters
Maximum number of parallel threads for loading tables. Each thread loads one table at a time.
Set to
true if data was extracted using hex encoding instead of base64.When
true, uses the C OCI bulk loader for approximately 100x faster performance. When false, uses Go row-by-row insertion.File extension for data files to process.
Change Loader
The Change Loader applies ongoing data changes (INSERT, UPDATE, DELETE) to Oracle target tables using a merge approach with shadow tables.The Change Loader requires merge tables to be created by the Schema Loader. It uses Oracle’s MERGE statement for atomic change application.
Required Parameters
Path to a file containing the Oracle connection string.
Directory containing change files (
.ckt) from the Change Extractor.Working directory for temporary CSV files during merge operations. Must be writable.
Path to the Wirekite schema file for table structure information.
Absolute path to the log file for Change Loader operations.
Optional Parameters
When
true, loads changes locally. When false, uses remote loading methods.Maximum number of change files to process in a single batch before executing MERGE operations.
Orchestrator Configuration
When using the Wirekite Orchestrator, prefix target parameters withtarget.schema., target.data., or target.change. depending on the operation.
Example orchestrator configuration for Oracle target:
