On this Page
Overview
You can use this Snap to execute an SQL Insert statement. Document keys are used as the columns to insert into, and their values are inserted into the column. Any missing column will insert a null value into it.
Snap Type
The Oracle - Insert Snap is a Write-type Snap that inserts the specified data in the target table.
Prerequisites
A valid Oracle Thin Account or Oracle Thin Dynamic Account.
Support for Ultra Pipelines
Works in Ultra Task Pipelines if batching is disabled.
Known Issues
The Oracle - Insert Snap inserts incorrect time zone data for timestamp with time zone data type. For example, when an input value is 2021-08-10 17:30:43-07:00, the value written to the target table is 2021-08-10 17:30:43+07:00.
Workaround:
Use an expression Date.parse(2021-08-10 17:30:43-07:00) in Mapper Snap. The Mapper Snap converts it to a UTC timestamp string, that is, 2021-08-11 00:30:43 00:00. The Snap will now insert the value successfully.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document
|
|
| Requires the Schema name and Table name to process a certain number of input documents into a prepared insert query. The second input view can be added for metadata for the table as a document so that the table is created in Oracle with a similar schema as the source table. If the table already exists, then the metadata is not used. |
Output | Document
|
|
| 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:
Database Write Snaps output all records of a batch (as configured in your account settings) to the error view if the write fails during batch processing. | |||
Snap Settings
Field Name | Field Type | Description | |
|---|---|---|---|
Label* Default value: Oracle - Insert | 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
| String/Expression/Suggestion | The database schema name. In case it is not defined, then the suggestion for the Table Name will retrieve all tables names of all schemas. The property is suggestible and will retrieve available database schemas during suggest values. The values can be passed using the pipeline parameters but not the upstream parameter. | |
Table name
| String/Expression/Suggestion | Specify the table that the rows will be inserted into. The values can be passed using the pipeline parameters but not the upstream parameter. | |
Create table if not present Default state: Deselected | Checkbox | Select this checkbox to automatically create the target table if it does not exist. 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). Due to implementation details, a newly created table is not visible to subsequent database Snaps during runtime validation. If you want to immediately use the newly updated data you must use a child Pipeline that is invoked through a Pipeline Execute Snap. | |
Preserve case sensitivity | Checkbox | Select this checkbox to preserve the case sensitivity of the column names while performing the insert operation.
| |
Number of retries Default value: 0 | Integer/Expression | Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. | |
Retry interval (seconds) Default value: 1 | Integer/Expression | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. | |
Session parameters | Use this field set to define the session parameters. This property lets you use the National Language Support (NLS) parameters. See the Oracle doc for detailed information about Setting NLS Parameters. The NLS parameters enable overriding the default value (e.g., a comma) that is set for the session in the initialization parameter file or set by the client with environment variables (e.g., a decimal point). You can add multiple parameters by using the plus (+) sign next to Session parameters. | ||
Session parameter name Default value: N/A | String/Expression | Name of the NLS parameter.
| |
Session parameter value Default value: N/A | String/Expression | Value of the NLS parameter. This field supports only pipelines parameters, and not upstream values. | |
Snap execution | Dropdown list | Select one of the three modes in which the Snap executes. Available options are: Disabled: Disables the Snap and all Snaps that are downstream from it. | |
Additional information
Auto commit
In a scenario where the Auto commit on the account is set to true, and the downstream Snap does depends on the data processed on an Upstream Database Bulk Load Snap, use the Script Snap to add delay for the data to be available. For example, when performing a create, insert and a delete function sequentially on a pipeline, using a Script Snap helps in creating a delay between the insert and delete function or otherwise it may turn out that the delete function is triggered even before inserting the records on the table.
Oracle reports failures for the entire batch even if some rows successfully inserted/updated. Because the Snap must report what is reported by the database, the Snap sends all records to the error view and no record to the output view. If you want to see accurate results for each row you must set the batch size to 1 and execute the pipeline.
Table Creation
If the table does not exist when the Snap tries to do the insert, and the Create table if not present property is selected, the table will be created with the columns and data types required to hold the values in the first input document. If you would like the table to be created with the same schema as a source table, you can connect the second output view of a Select Snap to the second input view of this Snap. The extra view in the Select and Bulk Load Snaps are used to pass metadata about the table, effectively allowing you to replicate a table from one database to another.
The table metadata document that is read in by the second input view contains a dump of the JDBC DatabaseMetaData class. The document can be manipulated to affect the CREATE TABLE statement that is generated by this Snap. For example, to rename the name column to full_name, you can use a Mapper Snap that sets the path $.columns.name.COLUMN_NAME to full_name. The document contains the following fields:
columns - Contains the result of the getColumns() method with each column as a separate field in the object. Changing the COLUMN_NAME value will change the name of the column in the created table. Note that if you change a column name, you do not need to change the name of the field in the row input documents. The Snap will automatically translate from the original name to the new name. For example, when changing from name to full_name, the name field in the input document will be put into the "full_name" column. You can also drop a column by setting the COLUMN_NAME value to null or the empty string. The other fields of interest in the column definition are:
TYPE_NAME - The type to use for the column. If this type is not known to the database, the DATA_TYPE field will be used as a fallback. If you want to explicitly set a type for a column, set the DATA_TYPE field.
_SL_PRECISION - Contains the result of the getPrecision() method. This field is used along with the _SL_SCALE field for setting the precision and scale of a DECIMAL or NUMERIC field.
_SL_SCALE - Contains the result of the getScale() method. This field is used along with the _SL_PRECISION field for setting the precision and scale of a DECIMAL or NUMERIC field.
primaryKeyColumns - Contains the result of the getPrimaryKeys() method with each column as a separate field in the object.
declaration - Contains the result of the getTables() method for this table. The values in this object are just informational at the moment. The target table name is taken from the Snap property.
importedKeys - Contains the foreign key information from the getImportedKeys() method. The generatedCREATE TABLE statement will include FOREIGN KEY constraints based on the contents of this object. Note that you will need to change the PKTABLE_NAME value if you changed the name of the referenced table when replicating it.
indexInfo - Contains the result of the getIndexInfo() method for this table with each index as a separated field in the object. Any UNIQUE indexes in here will be included in the CREATE TABLE statement generated by this Snap.
Examples
Insert input data into a table
The following example pipeline demonstrates how to insert a row of data into TEST_EMPLOYEE table.
Table dataset:
CREATE TABLE "TECTONIC"."TEST_EMPLOYEE"
(
"Title" VARCHAR2(4000 BYTE),
"Employee_Name" VARCHAR2(4000 BYTE),
"Employee_ID" VARCHAR2(4000 BYTE)
);
Step 1: Configure the JSON Generator Snap with the data you want to insert into the target table.
Step 2: Configure the Oracle - Insert Snap as shown below to insert this data into the TEST_EMPLOYEE table. On validation, Snap inserts the employee details into the target TEST_EMPLOYEE table and displays the “success” message in the output.
| 
|
|---|
Error Handling of the Snap
This example pipeline demonstrates error handling.
Use the same pipeline as the one used in Example 1. Insert a row with a non-existing column name "Titlee". In the Oracle - Insert Snap, choose Route Error Data to Error View under the Views tab.
On validation, the error message is routed to Snap's error view:
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