> ## Documentation Index > Fetch the complete documentation index at: https://docs.maia.ai/llms.txt > Use this file to discover all available pages before exploring further. # Oracle Unload from Snowflake export const maia = "Maia"; export const ComponentMetadata = ({warehouses, unsupportedWarehouses = [], componentType, connectionInputs, connectionOutputs}) => { const allWarehouses = [...warehouses.map(w => ({ name: w, supported: true })), ...unsupportedWarehouses.map(w => ({ name: w, supported: false }))]; return
Project Availability
{allWarehouses.map((w, i) => {w.name} {w.supported ? '✅' : '❌'} )}
Component Type {componentType}
Connection Inputs {connectionInputs}
Connection Outputs {connectionOutputs}
; }; The **Oracle Unload** orchestration component lets you write data in your Snowflake source to a target Oracle database. In a Snowflake {maia} project, the Snowflake account credentials are taken from the environment the current branch is connected to. This means you only need to configure parameters to identify the data being written and to set up the connection to the target Oracle database. *** ## Properties Reference material is provided below for the Configure and Destination properties. A human-readable name for the component. ### Configure * **Basic:** This mode will build a query for you using settings from the **Schema**, **Data Source**, **Data Selection**, **Data Source Filter**, **Combine Filters**, and **Limit** parameters. In most cases, this mode will be sufficient. * **Advanced:** This mode will require you to write an SQL-like query to call data from the service you're connecting to. The available fields and their descriptions are documented in the data model. There are some special pseudo columns that can form part of a query filter, but are not returned as data. This is fully described in the data model. While the query is exposed in an SQL-like language, the exact semantics can be surprising, for example, filtering on a column can return more data than not filtering on it. This is an impossible scenario with regular SQL. {/* */} The Snowflake *source* warehouse. The special value `[Environment Default]` uses the warehouse defined in the environment. Read [Snowflake's Virtual Warehouses documentation](https://docs.snowflake.com/en/user-guide/warehouses.html) to learn more. {/* */} The Snowflake *source* database. The special value `[Environment Default]` uses the database defined in the environment. Read [Databases, Tables and Views - Overview](https://docs.snowflake.com/en/guides-overview-db) to learn more. {/* */} The Snowflake *source* schema. The special value `[Environment Default]` uses the schema defined in the environment. Read [Database, Schema, and Share DDL](https://docs.snowflake.com/en/sql-reference/ddl-database.html) to learn more. {/* */} Select a single data source to be extracted from the source system and loaded into a table in the destination. The source system defines the data sources available. Use multiple components to load multiple data sources. {/* */} Choose one or more columns to return from the query. The columns available are dependent upon the data source selected. Move columns left-to-right to include in the query. To use [grid variables](/docs/guides/grid-variables), select the **Use Grid Variable** checkbox at the bottom of the **Data Selection** dialog. {/* */} Define one or more filter conditions that each row of data must meet to be included in the load. * **Input Column:** Select an input column. The available input columns vary depending upon the data source. * **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 data sources support all comparators. * **Value:** The value to be compared. Click the **Text Mode** toggle at the bottom of the **Connection Options** dialog to open a multi-line editor that lets you add items in a single block. For more information, read [Text mode](/docs/guides/components-overview#component-properties). {/* */} The data source filters you have defined can be combined using either **And** or **Or** logic. If **And**, then all filter conditions must be satisfied to load the data row. If **Or**, then only a single filter condition must be satisfied. The default is **And**. If you have only one filter, or no filters, this parameter is essentially ignored. {/* */} Set a numeric value to limit the number of rows that are loaded. The default is an empty field, which will load all rows. ### Destination Currently, only **Username & Password** credentials are supported. {/* */} Your Oracle login username. {/* */} Your Oracle password. This is stored as a secret definition. Read [Secrets and secret definitions](/docs/guides/secrets-and-secret-definitions) to learn how to store a password as a secret definition. {/* */} The Oracle database endpoint. Typically, this is your Oracle database IP. For example, `10.12.2.15`. {/* */} The port number that follows your Oracle database endpoint. The default value is `1521`. {/* */} Select a method of identifying the Oracle database to connect to. * **Service Name:** In Oracle, the SERVICE\_NAMES parameter specifies one or more names by which clients can connect to the Oracle instance. * **SID:** The Oracle Service Identifier prefix is the first 8 characters of the database name. This prefix can only contain the characters a-z, A-Z, and 0-9. {/* */} Specify the full name of your Oracle database. This is the name of the database as it is known to the Oracle instance. It can be up to 30 characters long and can contain alphanumeric, underscore `_` dollar `$`, and pound `#` characters, but must begin with an alphabetic character. No other special characters are permitted in a database name. Read [Selecting a Database Name](https://docs.oracle.com/en/database/oracle/oracle-database/19/rilin/selecting-a-database-name.html) to learn more about Oracle database names. {/* */} * **Parameter:** A JDBC parameter supported by the database driver. The parameters available to your database will usually be explained in the database's data model. * **Value:** A value for the given parameter. Click the **Text mode** toggle 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](/docs/guides/components-overview#text-mode). {/* */} The name of the Oracle schema to output the target table into. For information about using Oracle schemas, read [Schemas and Schema Objects](https://docs.oracle.com/en/database/oracle/oracle-database/23/dbiad/db_schemas.html). {/* */} A name for the output table that is to be created in the Oracle database. {/* */} 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. {/* */} Select one or more columns to be designated as the table's primary key. To use grid variables, select the **Use Grid Variable** checkbox at the bottom of the dialog. For more information, read [Grid variables](/docs/guides/grid-variables). {/* */} If **Load Strategy** 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. {/* */} Data read from the Snowflake source will be written directly to the Oracle target, without using an intermediate stage. Currently, therefore, the only option here is **Batch Load**. {/* */} The number of rows batched for passing to the Oracle database. Default is `1000`.