Implementing Oracle to Snowflake Synchronization Using Cloud Mass Ingestion Databases

Back Next

Step 1: Defining basic task information

To begin defining a

database ingestion

task, you must first enter some basic information about the task, such as a task name, project or project folder location, and load operation type.

Mass Ingestion

, click

New

Database Ingestion Task

The

Definition

page of the

Mass Ingestion Databases

Task wizard appears.

Configure the following properties:

Property	Description
Name	A name for the database ingestion task. Task names can contain Latin alphanumeric characters, spaces, periods (.), commas (,), underscores (_), plus signs (+), and hyphens (-). Task names cannot include other special characters. Task names are not case sensitive. Maximum length is 50 characters. If you include spaces in the database ingestion task name, after you deploy the task, the spaces do not appear in the corresponding job name.
Location	The project or project\folder that will contain the task definition. The default is the currently selected project or project subfolder in Explore. If a project or project subfolder is not selected, the default is the Default project.
Runtime Environment	The runtime environment in which you want to run the task. The runtime environment must be a Secure Agent group that consists of one or more Secure Agents. A Secure Agent is a lightweight program that runs tasks and enables secure communication. You cannot use the Hosted Agent or a serverless runtime environment. Click the Refresh icon to refresh the list of runtime environments.
Description	An optional description for the task. Maximum length is 4,000 characters.
Load Type	The type of load operation that the database ingestion task performs. For this scenario, select Initial and Incremental Loads to perform an initial load of point-in-time data to the target and then automatically switch to propagating incremental data changes made to the same source tables on a continuous basis. If a change record is captured during the initial unload load phase, it's withheld from apply processing until after the unload phase completes. Any insert rows captured during the unload phase are converted into a pair of delete and insert operations so that only one insert row is applied to the target in the case where the insert occurs in both the unloaded data and the captured change data.