Skip to main content
The Oracle Unload orchestration component lets you write data from your data warehouse to a target Oracle database. If the component requires access to a cloud provider (AWS, Azure, or Google Cloud), it will use credentials as follows:
  • If using Matillion Full SaaS: The component will use the cloud credentials associated with your environment to access resources.
  • If using Hybrid SaaS: By default the component will inherit the agent’s execution role (service account role). However, if there are cloud credentials associated with your environment, these will overwrite the role.
In Snowflake projects, you may have used the Oracle Output component to unload data from Snowflake to an Oracle database. This component was previously called Oracle Unload, but has been renamed so that we can use a consistent naming strategy for our Unload connectors.

​
Properties

Reference material is provided below for the Source and Destination properties.
​
string
required
A human-readable name for the component.

​
Source

​
drop-down
required
The Snowflake database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
drop-down
required
The Snowflake schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
drop-down
required
Select the table to unload to the target Oracle database. The tables available for selection depend on the chosen schema.
​
object selector
Select columns to return from the table.Leave this blank to unload all columns.
​
object selector
Select one or more columns to use as the table’s primary key. The component uses the primary key to identify matching rows in the target table when determining the update strategy.If you select multiple columns, the component creates a composite primary key using the combination of the selected columns.Leave this blank to load all rows without duplicate checking.
​
integer
Set a numeric value to limit the number of rows that are unloaded. The default is an empty field, which unloads all rows.
​
column editor
Define one or more filter conditions that each row of data must meet to be unloaded.
  • Input Column: Select an input column. The available input columns vary depending upon the selected table.
  • Qualifier:
    • Is: Compares the column to the value using the comparator.
    • Not: Reverses the effect of the comparison, so “Equals” becomes “Not equals”, “Less than” becomes “Greater than or equal to”, etc.
  • Comparator: Choose a method of comparing the column to the value. Possible comparators include: “Equal to”, “Greater than”, “Less than”, “Greater than or equal to”, “Less than or equal to”, “Like”, “Null”. Not all column types support all comparators.
  • Value: The value to be compared.
Click the Text Mode toggle at the bottom of the Filter Conditions dialog to open a multi-line editor that lets you add items in a single block. For more information, read Text mode.
​
drop-down
The filter conditions you have defined can be combined using either And or Or logic. If And, then all filter conditions must be satisfied to unload the data row. If Or, then only a single filter condition must be satisfied. The default is And.If you have only one filter condition, or no filter conditions, this parameter is essentially ignored.

​
Destination

​
drop-down
required
Select a Connection. This connection defines all credentials needed to connect to the service.If the required connection doesn’t yet exist, you can create it here by selecting Add Connection in the drop-down. Read Add a connection for further details, following that process from step 4 onwards. A connection created here is visible in the Connections tab and available for other connectors to use.
​
string
required
The name of the Oracle schema to unload the target table into. For information about using Oracle schemas, read Schemas and Schema Objects.
​
string
required
A name for the target table that is to be created in the Oracle database.
​
drop-down
required
Define what happens if the table name already exists in the specified database and schema.
  • Replace: If the specified table name already exists, that table will be destroyed and replaced by the table created during this pipeline run. If the table name doesn’t already exist, a new table will be created.
  • Truncate and Insert: If the specified table name already exists, all rows within that table will be removed and new rows will be inserted per the next run of this pipeline.
  • Append: If the specified table name already exists, new rows will be appended to that existing table.
In each case, if the specified table name doesn’t already exist then a new table will be created.
​
drop-down
required
If Write Mode is Append and Primary Keys have been specified, this property determines the behavior if there are existing rows with the same primary keys as an appended row.
  • Ignore: Existing rows with the same primary key values will be ignored. This is the default behavior.
  • Replace: Existing rows with the same primary key values will be replaced.
​
integer
The number of rows batched for passing to the Oracle database. Default is 1000.
​
column editor
  • Parameter: A JDBC parameter supported by the database driver. The available parameters are explained in the data model. Manual setup is not usually required, since sensible defaults are assumed.
  • Value: A value for the given parameter.
Toggle Text mode on at the bottom of the dialog to open a multi-line editor that lets you add items in a single block. For more information, read Text mode.