Skip to end of banner
Go to start of banner

WIP: Oracle - Parallel Load

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

In this article

Overview

You can use this Snap to insert data in parallel across multi-threaded tasks to execute a high-performance data load compared to the Oracle - Bulk Load Snap.

snap-oracle-parallel-load.png

Snap Type

The Oracle - Parallel Load Snap is a Write-type Snap that writes the specified data in the target table.

Prerequisites

Support for Ultra Pipelines  

Limitations

None.

Known Issues

Although the Schema name and Table name settings both accept schema from upstream snaps and offer suggestions for expressions, we recommend that you do not use those suggestions as they cause incorrect behavior.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

  • Min: 1

  • Max: 2

  • Mapper

  • Copy

Requires the EDI data and internal ID as a JSON document.

Output

Document

  • Min: 0

  • Max: 1

  • Mapper

Snap outputs the number of documents successfully inserted into the target table in the output view document.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

  • Asterisk ( * ): Indicates a mandatory field.

  • Add icon ( (blue star) ): Indicates that you can add fields in the field set.

  • Remove icon ( (blue star)): Indicates that you can remove fields from the field set.

  • Expression icon ((blue star)): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Upload icon ((blue star)): Indicates that you can upload files. Learn more about managing Files.

Field Name

Field Type

Description

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.

You can pass the values as expressions using the Pipeline parameters but cannot use values from the upstream Snap.

Table name*

Default Value: N/A
Example: people

String/Expression

Specify the table on which to execute the load operation.

You can pass the values as expressions using the Pipeline parameters but cannot use values from the upstream Snap.

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).

The newly created table is not visible to subsequent database Snaps during runtime validation because of implementation details. If you want to immediately use the newly updated data, you must use a child pipeline invoked through the Pipeline Execute Snap.

Maximum thread count*


Default Value: N/A
Example: people

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: N/A
Example: people

Integer/Expression

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

Maximum error count*


Default Value50 
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 as long as the number of failed records is less than 10.

A value of -1 means no limit. At least one more error document than the specified maximum value is expected, but task concurrency may result in additional error documents. This applies only when the error behavior is set to Route Error Data to Error View.

Truncate table before load


Default Value: Deselected

Checkbox

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.

Troubleshooting

Error

Reason

Resolution

Interrupted while waiting for dataWriter

dataWriter is still null

"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";

Connection used to retrieve table metadata threw exception while closing";

Examples

Excluding Fields from the Input Data Stream

e can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:

<screenshot of Pipeline/Snap and description>

Download this Pipeline. 

Downloads

  1. Download and import the pipeline into the SnapLogic application.

  2. Configure Snap accounts, as applicable.

  3. Provide pipeline parameters, as applicable.

  File Modified
No files shared here yet.

Snap Pack History

 Click here to expand...
Error rendering macro 'excerpt-include' : No link could be created for 'XYZ Snap Pack'.

Related Content

  • No labels