Oracle Database is a multi-model database management system commonly used for running online transaction processing, data warehousing and mixed database workloads. |
The process to export data to an Oracle DB is described in the following sections:
Define the Oracle Target Data Connection > Create a Pipeline to Add Oracle Node > Export the Data |
The following are the steps to configure a Postgres data connection:
| Field | Description |
|---|---|
| Type | The type of target data connection. Select Oracle. |
| Name | The name for the target data connection. The connection name must be unique across the specific domain. |
| Description | The description for the target data connection. |
| JDBC URL | The JDBC URL to connect to the Oracle database. The URL must be of the following format: jdbc:oracle:thin:@<hostname>:<port>:<sid> |
| User Name | The username of the Oracle target account. |
| Password | The password of the Oracle target account. |
| Additional Params | The optional JDBC parameters. For example, ssl=true & TCPKeepAlive=false. |
Following are the steps to add a new pipeline to the domain:
| Field | Description |
|---|---|
| Name | Unique name for the pipeline. |
| Description | Description for the pipeline. |
| Execution Engine | Select the Execution Engine as Spark. |
| Machine Learning Library | Select SparkML____. |
| Cluster Templates for Batch Mode | Select the default cluster template. |
Following are the steps to design a pipeline:

Following are the steps to apply Oracle Table Target node in pipeline:
| Field | Description |
|---|---|
| Build Mode | The options include overwrite, append, merge or insert-overwrite. Overwrite: Drops and recreates the Oracle target. Merge: Merges data to the existing table based on the natural key. Append: Appends data to the existing Oracle target. Insert-Overwrite: Overwrites all the rows based on combination of natural keys (OR condition) and inserts new rows. |
| Data Connection | The data connection created in the Define the Oracle Target Data Connection step for Oracle Target. |
| Schema Name | The name of the existing schema in the Oracle database. Infoworks does not create a schema, hence the schema should be pre-existing. |
| Table Name | The table name for the Oracle target. |
| Natural Keys | The combination of keys to uniquely identify the row. |
| Is Existing Table | When enabled, existing table behavior works as an external table to Infoworks. The table will not be created/dropped or managed by Infoworks. |
| Partition Type | The type of partition for the table. By default, the Partition Type is set to None. You can also select the following partition types: List: Table is partitioned according to the listed values. If the table’s relevant columns contain data for a particular list, then the List partitioning method is used in these tables. Range: Table is partitioned according to the specific date and number range. Each partition has an upper and lower bound, and the data is stored in this range on partitions. Note:Following datatypes can be used as an indexing column for range partitioning: String, Number of rows or Timestamp Hash: Hash partitioning divides partitions using a hashing algorithm that partitioning key is applied that you identify. |
| Partition Column | The column based on which the data will be partitioned. This field is displayed for the list, range, and hash partition types. |
| Is Default | The condition to use the default partitioning for the child partition. This field is displayed for the list partition type. |
| Partition Table | The name of the partition table. This field is displayed for the list and range partition type. You can add multiple partition tables. |
| Values | The values based on which the child partition will be created. This field is displayed for the list partition types. |
| Less Than Value | The less than value for the range partition. |
| Number of Partitions | The number of partitions to be created. This field is displayed for the hash partition type. |
| Tablespace Names | A comma-separated list of tablespace names for hashing. |
| Index Type | The indexing option. By default, the Index Type is set to None. You can also select the following Index types: BTree: A b-tree index works by creating a series of nodes in a hierarchy. In a b-tree, you walk the branches until you get to the node that has the data you want to use. In the classic b-tree structure, there are branches from the top that lead to leaf nodes that contain the data. Bitmap: : A bitmap index is a special kind of database index which uses bitmaps or bit array. In a bitmap index, Oracle stores a bitmap for each index key. Each index key stores pointers to multiple rows. Note:____Bitmap index can not be used with the partitioned table |
| Sync Table Schema | The option to synchronise pipeline export table schema with source table schema. |
Export the Data
Following are the steps to build a pipeline:

2. Select the Version and click Build Pipeline to build the pipeline version.
Below is the list of supported source datatypes and their mapping to oracle datatypes:
| Spark Datatype | Oracle Datatype |
|---|---|
| DecimalType | NUMBER |
| NUMBER | NUMBER |
| FloatType | FLOAT |
| DoubleType | FLOAT |
| StringType | VARCHAR2(4000) |
| DateType | DATE |
| TimestampType | TIMESTAMP |
| BooleanType | NUMBER |