Label*

Default Value: Oracle - Parallel Load
Example: Oracle - Parallel Load

String

Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Schema name

Default Value: N/A
Example: Sys

String/Expression

Specify the database schema name.

Table name*

Default Value: N/A
Example: people

String/Expression

Specify the table on which to execute the load operation.

Create table if not present

Default Value: Deselected

Checkbox

Select this checkbox to automatically create the target table if it does not exist.

• If a second input view is configured for the Snap and it contains a document with schema (metadata) from the source table, the Snap creates the new (target) table using the same schema (metadata). However, if the schema comes from a different database, the Snap might fail with the Unable to create table: "<table_name>" error due to data type incompatibility.

• In the absence of a second input view, the Snap creates a table based on the data types of the columns generated from the first row of the input document (first input view).

Maximum thread count*

Default Value: 0
Example: 20

Integer/Expression

Specify the maximum number of threads allowed to perform data insertions simultaneously. If the value is 0, the snap automatically sets the number of threads equal to the number of available processors on the system.

Batch capacity*

Default Value: 1000
Example: 500

Integer/Expression

Specify the maximum number of records allowed in a single batch for an insertion task.

Snap memory usage: To gracefully handle failed record insertions, the Snap must retain some input document data in memory during the Snap execution. To calculate the memory usage follow this formula:
Max thread count * Batch capacity * 2 * typical record size
For example, with a Maximum thread count of 4, a Batch capacity of 10,000, and an average record size of 50 bytes, the input document data in Snap memory may peak at 4 million bytes.

Maximum error count*

Default Value: 50 
Example:10

Integer/Expression

Specify the maximum number of record insertion errors allowed before execution stops on the next error. For example, if you specify a value of 10, the pipeline execution continues until the number of failed records exceeds 10.

Truncate table before load

Default Value: Deselected

Checkbox/Expression

Select this checkbox to truncate the target table before loading data.

Snap Execution

Default Value: 
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

• Validate & Execute: Performs limited execution of the Snap and generates a data preview during pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during pipeline runtime.

• Execute only: Performs full execution of the Snap during pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.

Pre-load truncation of the target table failed

The target table may not exist or a database access error may have occurred when trying to execute the TRUNCATE statement.

Verify your database credentials and ensure the target table exists, then try again.

Unable to determine target table column names

The connection used to retrieve table metadata displayed an exception while closing.

Verify the target table column names and try again.

All insertions committed.

N/A

One document containing
<insert_count> field with an integer value indicating the number of inserted records successfully.

All input records are successfully inserted to the target database.

Success

One error document for each record that failed to insert.

One document containing
<insert_count> field with an integer value indicating the number of inserted records successfully.

Some input records individually fail to insert into the target database, but do not exceed maximum error count.

Success

Insertions made successfully
prior to the Maximum
error count being
exceeded may be
committed.

Multiple error documents, one for each record that failed to insert.
The total number of error documents should be
equal to at least the Maximum
error count plus one, but might be more due to concurrency of attempted insertions.

One document containing
<insert_count> field with an integer value indicating the number of inserted records successfully
prior to exceeding maximum
error count.

Enough input records individually fail to insert to exceed the Maximum error count and cause the Snap to end execution early.

Success

Insertions made
successfully prior to the
Snap-failing error may be
committed.

One error document for
each record that individually
failed insertion (if any).

One document containing
<insert_count> field with an integer value indicating the number of inserted records successfully prior to the (Snap-failing) error.

An error occurs beyond the scope of any individual record.

Failure