In this article
Overview
You can use this Snap to insert data parallelly across multi-threaded tasks. Compared to the Oracle Bulk Load Snap, this Snap executes a high-performance data load.
The Oracle - Parallel Load Snap always auto-commits its database operations. The Auto commit setting either in the Oracle Thin Account or the Oracle Thin Dynamic Account configured for the Snap does not affect the Snap’s behavior.
This Snap supports Kerberos authentication for Oracle.
Snap Type
The Oracle - Parallel Load Snap is a Write-type Snap that writes the specified data in the target table.
Prerequisites
A valid Oracle Thin Account or Oracle Thin Dynamic Account.
Support for Ultra Pipelines
Does not work in Ultra Pipelines.
Limitations
None.
Known Issues
Both the Schema name and the Table name settings accept schema from upstream Snap and offer suggestions for expressions. However, we recommend that you do not use those suggestions because they cause incorrect behavior.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
|
| Requires both the Schema name and the Table name to process a specific number of input documents into a prepared insert query and execute all of the prepared input document values on that query as a batch. |
Output | Document |
|
| The Snap outputs the number of documents successfully inserted into the target table in the output. |
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:
Learn more about the behavior of the Oracle - Parallel Load Snap with open error views. | |||
Snap Settings
Asterisk ( * ): Indicates a mandatory field.
Add icon (
): Indicates that you can add fields in the field set.Remove icon (
): Indicates that you can remove fields from the field set.Expression icon (
): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.Suggestion icon (
): Indicates a list that is dynamically populated based on the configuration.Upload icon (
): Indicates that you can upload files. Learn more about managing Files.
Field Name | Field Type | Description |
|---|---|---|
Label* Default Value: 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 Snaps in your pipeline. |
Schema name Default Value: N/A | String/Expression | Specify the database schema name. The suggestions in the Schema field are populated only when at least a single table exists in the schema. If no tables exist to use that schema, only SYS, SYSTEM, and XDB are populated. 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 | 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.
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*
| 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. There is no upper limit for the Maximum thread count, therefore you should exercise caution when setting this value to avoid unexpected behavior or performance degrade. |
Batch capacity*
| Integer/Expression | Specify the maximum number of records allowed in a single batch for an insertion task. There is no upper limit for Batch capacity, therefore you should exercise caution when setting this value to avoid unexpected behavior or performance degrade. |
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: | ||
Maximum error count*
| 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. 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
| Checkbox/Expression | Select this checkbox to truncate the target table before loading data. |
Snap Execution Default Value: | Dropdown list | Select one of the following three modes in which the Snap executes:
|
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
| Either the target table might not exist or a database access error might have occurred when trying to execute the TRUNCATE statement. | Verify your database credentials and ensure the target table exists, then retry. |
| The connection used to retrieve table metadata displayed an exception before closing. | Verify the target table column names and retry. |
Behavior of Parallel Load Execution with Open Error Views
The following table describes the expected behavior for the general outcomes of Parallel Load execution when the Snap has an open error view (that is, when you select Route Error Data to Error View for When error occurs).
Committed Database Insertions | Error View | Output Preview | Snap Outcome | Final Snap State |
|---|---|---|---|---|
All insertions committed. | N/A | One document containing the | All input records are successfully inserted into the target database. | Success |
One error document for each record that failed to insert. | One document containing the | Some input records individually fail to insert into the target database, but do not exceed maximum error count. | Success | |
Insertions made successfully | Multiple error documents, one for each record that failed to insert. | One document containing the | Enough input records individually fail to insert to exceed the Maximum error count and cause the Snap to end execution early. | Success |
Insertions made | One error document for | One document containing | An error occurs beyond the scope of any individual record. | Failure |
Individual record insertion failures occur when the database encounters an error during the insertion of a record. These failures are recoverable and specific to one input document. For example, an error might occur if the value of a document field is incompatible with the data type of the target column. | ||||
Examples
Load 1000 Document Insertions
The following example pipeline demonstrates the use of Parallel Load to insert 1000 documents. This example showcases Parallel Load's efficiency and capability in managing large-scale data insertion tasks.
Configure the Mapper Snap with subscriber details (Subscriber ID, Last Login, and Subscriber’s full name) to pass them to the Oracle - Parallel Load Snap.
Configure the Oracle - Parallel Load Snap with the following settings:
Maximum thread count: 4
Batch capacity: 100
On validation, the pipeline inserts a maximum of 400 records simultaneously, across 4 threads handling 100 records each. The image below displays only 50 records because the Preview document count is set to 50.
Handle Database Insertion Failures with Open Error View
This example demonstrates a Mapper Snap configuration designed to intentionally cause a small number of records to fail during database insertion. For every failed insertion, an error document is generated. Specifically, out of 1000 records, 7 are expected to fail, resulting in 7 error documents, and the remaining 993 records are successfully inserted. The count of successful insertions is also recorded in the output document. This pipeline demonstrates how to efficiently manage and log insertion errors.
Configure the Mapper Snap with settings so that a small number of records fail during database insertion, and route the error documents to the error view.
Configure the Oracle - Parallel Load Snap as follows to insert a total of 1000 documents.
On validation, 993 records are successfully inserted and written to the output document, and 7 error documents are written on the error view. The image below displays only 47 records because the Preview document count is set to 50.
Inserted records | Insertion failed records |
|---|---|
 |  |
Downloads
Download and import the pipeline into the SnapLogic application.
Configure the Snap accounts, as applicable.
Provide the pipeline parameters, as applicable.
Snap Pack History
Fixed an issue with Oracle Execute, Select, and Stored Procedure Snaps where the data was displayed in an unexpected structure and without the actual row address value when querying table columns of Fixed an issue with the Oracle - Merge Snap that caused a date format error when the merge condition was used with the TO_DATE() function. Added Oracle - Parallel Load Snap that executes a high-performance data load by inserting data in parallel across multi-threaded tasks. Enhanced the Oracle Insert, Merge, Update, and Delete Snaps to support the Enable, Disable, and Force commands in the Session parameters that enable you to dynamically manage specific session settings. Enhanced the Oracle Thin and Oracle Thin Dynamic Accounts to support Kerberos authentication for Oracle databases on Windows and Linux systems. Enhanced the Oracle - Delete Snap with the Session parameters field set that provides National Language Support (NLS). Learn more about Setting NLS Parameters. Fixed an issue with the Oracle - Execute Snap that displayed an error when handling Fixed an issue with Oracle - Bulk Load Snap that intermittently displayed a Fixed an issue with the Oracle - Bulk Load Snap to handle the type definition of nvarchar and nchar data types by defining them in the control file of the SQL loader. Fixed an issue with the Oracle - Bulk Load Snap that incorrectly incremented the year part of the DATE datatype for specific datasets. Fixed an issue with the Oracle - Merge Snap that did not handle the timestamp conversion correctly when the time was not in the The Oracle - Execute Snap displays both the status and the message in the output when you call stored procedures. Behavior Change: As part of main25112 Fixed an issue with the Oracle Snap Pack that required the i18n extensions to be present when the Oracle database instance was in a specific language. The Oracle-Insert, Oracle-Update, and Oracle-Bulkload Snaps now support up to nanosecond precision for the string data type. Fixed an issue with the Oracle-Stored Procedure Snap that displayed an error ( Fixed an issue with the Oracle-Stored Procedure Snap that displayed an error when custom JAR files were used for BLOB and CLOB datatypes in the Oracle Accounts. The JDBC driver for the Oracle Snap Pack is upgraded from OJDBC6 JAR (v11.2.0.4) to OJDBC10 JAR (v19.20.0.0) in the latest distribution in October 2023 and will be deployed to the stable distribution in the November 2023 release (after the Snaplex upgrade). This upgrade changes specific error codes and status messages. The latest JDBC driver upgrade is backward-compatible. Learn more: Upgrading from Oracle JDBC 11.2.0.4 Driver to 19.20.0.0 Driver. Fixed an issue with the Oracle-Bulk Load Snap that was not resilient to the errors previously when trying to auto-discover the existing SQLLDR utility paths in the node. The Snap is now robust to those errors. August 2023 main22460 Stable The Oracle - Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically. May 2023 Stable Upgraded with the latest SnapLogic Platform release. November 2022 The Oracle-Stored Procedure Snap works as expected and does not fail with the error November 2022 The Oracle - Stored Procedure Snap now supports stored functions with OUT and INOUT parameters and displays these parameter values in the output along with the The Oracle Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met: The Create table if not present checkbox is selected. The target table does not exist. The table metadata is provided in the second input view. The Oracle Select Snap now work as expected when the table name is dependent on an upstream input. Fixed an issue with Oracle Bulk Load Snap where the Snap encountered an error when trying to load data into Fixed an issue with Oracle Execute Snap where the Snap did not display a valid error message when the delete condition was invalid. Fixed an issue with Oracle - Merge Snap where the Snap displayed an error when the Retry Interval and Number of Retries fields were expression enabled and the values were passed using the Pipeline parameters. Fixed an issue with the Oracle Stored Procedure Snap where the Snap errored out due to an upgrade made to HikariCP that caused a conditional failure and prevented the downstream Snaps to supply the parameters to the stored procedure. Enhanced the Oracle - Merge and Oracle - Update Snaps with the Session Parameters fieldset that provides National Language Support (NLS). 4.29 main15993 Stable Upgraded with the latest SnapLogic Platform release. Enhanced the Oracle - Update Snap to accept values in the Number of Retries and Retry Interval (seconds) fields from Pipeline parameters only. Enhanced the Oracle Bulk Load Snap with the Column Length Overrides field set to support CLOB (Character Large Object) and NCLOB (National Character Large Object) data types that may require a large buffer size, allowing users to load large amounts of data into a single column store of data type CLOB or NCLOB. Fixes the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected. Fixes the following issues with DB Snaps: Updated the Oracle Thin Account and Oracle Thin Dynamic Account, enabling them to connect via Oracle Active Data Guard (ADG). 4.20 Patch Enhances the Oracle Snap Pack to support connections to the Oracle ADG (Active Data Guard) URL. 4.20 Patch Support for Oracle Database 19c. Fixes an issue with the Oracle - Update Snap wherein the Snap is unable to perform operations when: Fixes an issue using the NVARCHAR2 datatype in Oracle databases when the character set is not AL32UTF8. However, a known issue is that special characters display as Fixed an issue with the Oracle Stored Procedure Snap wherein the Pipeline execution fails with an error when the input data type is CLOB. Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers. 4.16 Patch Added a new property, Session parameters, in the Oracle Insert Snap to enable the use of National Language Support (NLS) parameters. 4.16 Patch Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end. Improved performance in Pipelines that contain child Pipelines. Fixed an issue with data types conversion. All fields with byte, short, int, or long data types will be converted to BigInteger after fetching. Replaced the existing Max idle time and Idle connection test period properties with Max life time and Idle Timeout properties respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings. 4.13 Patch snapsmrc486 Fixed an issue in the Oracle Bulk Load Snap that fails to execute the SQLLDR (SQL Loader) command, while also enhancing the support for the TCPS protocol. Added a property, "SSL/TCPS" for Oracle Account. Enabled expression for Delete Condition in Oracle Delete Snap. snapsmrc480 4.11 Patch Enhanced the Oracle Bulk Load Snap to accept date-type values in the format "yyyy-mm-dd". Fixed BULK LOAD so it adds the thread name to the name of the temporary directory. This allows multiple BULK LOAD Snaps within a single pipeline. snapsmrc414 Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level. 4.9.0 Patch Fixed the issue that "NaN" check was done to unexpected data types like varchar. 4.9.0 Patch Fixed a class casting issue for custom data types(BLOB, CLOB, NCLOB, etc) when custom Oracle JDBC driver is used. 4.9.0 Patch Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap. 4.8.0 Patch Fix for SQL*Loader interpreting white-space only data as null values. 4.8.0 Patch oracle2756 Potential fix for JDBC deadlock issue. 4.8.0 Patch Fixed Oracle Snap Pack rendering dates that are one hour off from the date returned by database query for non-UTC Snaplexes. snapsmrc398 Database accounts now invalidate connection pools if account properties are modified and login attempts fail. 4.7.0 Patch Fixed an issue with the Oracle Select Snap regarding Limit rows not supporting an empty string from a pipeline parameter. snapsmrc382 Prior to 4.7, the only acceptable timestamp format was "yyyy-mm-dd hh:mm:ss.SSS", such as 2016-11-07 10:55:12 It now also supports: ISO8601 formats (plus fractional seconds) without timezone. "yyyy-mm-ddThh:mm:ss.SSS", (ex: 2016-11-07T10:55:12) ISO8601 formats with time zone. ONLY 'zulu' and 'UTC' at this time. Note that there is no space before the 'Z' but is a space before the 'UTC'. "yyyy-mm-ddThh:mm:ss.SSSZ" "yyyy-mm-ddThh:mm:ss.SSS UTC" ex: 2016-11-07T10:55:12Z ex: 2016-11-07T10:55:12 UTC The ISO8601 format is used by many web services, Oracle Bulk Loader, and others. oracle1583 Oracle Stored Procedure: Parameter index suggest throws "invalid path" when no schema nor procedure is selected Oracle Stored Procedure: If there is no type defined in Schema, suggest throwing Suggestion value cannot be empty for property: customTypeParameterTypeRelease Snap Pack Version Date Type Updates November 2024 439patches29008 Latest ROWID type. Now, the Snaps handle the ROWID type columns correctly to prevent the display of the nested output when ROWID is combined in the query with other selected columns.November 2024 main29029 Stable Updated and certified against the current SnapLogic Platform release. August 2024 438patches27870 Latest August 2024 main27765 Stable May 2024 437patches26651 Latest May 2024 437patches26346 Latest OffsetDateTime type bindings.May 2024 main26341 Stable Updated the Delete Condition (Truncates a Table if empty) field in the Oracle - Delete Snap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed. February 2024 436patches26208 Latest null pointer exception. The exception is now replaced with ConfigurationException.February 2024 436patches25696 Latest hh:mm format and had single digits (for example, 1:9) in the timestamp.436patches25696, when you use a stored procedure in the Oracle - Execute Snap, the Snap displays Message: Success and $UPDATE_COUNT=-1, 0, or 1 (based on the Snap Pack behavior) in the outputFebruary 2024 Stable Updated and certified against the current SnapLogic Platform release. November 2023 435patches24769 Latest November 2023 435patches24445 Latest November 2023 435patches23823 Latest SnapDataException) when custom JAR files were used in the Oracle Accounts.November 2023 main23721 Stable Updated and certified against the current SnapLogic Platform release. August 2023 434patches23000 Latest August 2023 434patches22787 Latest main21015 February 2023 main19844 Stable Upgraded with the latest SnapLogic Platform release. 431patches19781 Latest Invalid value type when you pass BLOB data as a parameter to the stored procedure with BLOB datatype.431patches19275 Latest returnval key.November 2022 main18944 Stable September 2022 430patches17894 Latest August 2022 430patches17658 Latest The Oracle - Stored Procedure Snap now takes lesser time to execute when calling a stored procedure, because the Snap queries the metadata as required, thereby optimizing the Snap's performance. August 2022 main17386 Stable 4.29 Patch 429patches16603 Latest Timestampwithtimezone datatype field.4.28 main14627 Stable 4.27 main12833 Stable 4.26 main11181 Stable Upgraded with the latest SnapLogic Platform release. 4.25 425patches11008 Latest 4.25 main9554 Stable Upgraded with the latest SnapLogic Platform release. 4.24 main8556 Stable 4.23 main7430 Stable Upgraded with the latest SnapLogic Platform release. 4.22 main6403 Stable Upgraded with the latest SnapLogic Platform release. 4.21 Patch 421patches6272 Latest 4.21 Patch 421patches6144 Latest 4.21 Patch MULTIPLE8841 Latest Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. 4.21 snapsmrc542 Stable db/oracle8812 Latest db/oracle8803 Latest 4.20 snapsmrc535 Stable Upgraded with the latest SnapLogic Platform release. 4.19 Patch db/oracle8408 Latest 4.19 snaprsmrc528 Stable Upgraded with the latest SnapLogic Platform release. 4.18 Patch oracle7786 Latest 
.4.18 snapsmrc523 Stable Upgraded with the latest SnapLogic Platform release. 4.17 Patch db/oracle7459 Latest 4.17 ALL7402 Latest 4.17 snapsmrc515 Latest db/oracle6919 Latest db/oracle6824 Latest 4.16 snapsmrc508 Stable Upgraded with the latest SnapLogic Platform release. 4.15 Patch db/oracle6534 Latest 4.15 Patch db/oracle6417 Latest 4.15 Patch db/oracle6284 Latest 4.15 snapsmrc500 Stable Upgraded with the latest SnapLogic Platform release. 4.14 snapsmrc490 Stable Upgraded with the latest SnapLogic Platform release. db/oracle5192 Latest NullPointerException error when the input letter case does not match with that of the Oracle table.4.13 Stable Upgraded with the latest SnapLogic Platform release. 4.12 Patch oracle4862 Latest 4.12 Patch db/oracle4721 Latest 4.12 Patch MULTIPLE4744 Latest 4.12 Stable Upgraded with the latest SnapLogic Platform release. db/oracle4369 Latest 4.11 snapsmrc465 Stable Upgraded with the latest SnapLogic Platform release. 4.10 Patch oracle3633 Latest 4.10 Stable oracle3188 Latest oracle3096 Latest oracle3071 Latest 4.9 snapsmrc405 Stable Upgraded with the latest SnapLogic Platform release. oracle2905 Latest Latest oracle2711 Latest 4.8 Stable oracle2190 Latest 4.7 Stable
"yyyymmddThhmmss.SSS", (ex: 20161107T105512)
"yyyymmddThhmmss.SSSZ"
"yyyymmddThhmmss.SSS UTC"
ex: 20161107T105512Z
ex: 20161107T105512 UTC4.6 snapsmrc362 Stable 4.5.1 Stable 4.4.1 NA Stable 4.4 NA Stable 4.3.2 NA Stable NA NA Stable NA NA Stable NA NA Stable