On this Page

Overview

You can use this Snap to execute stored procedures in an Oracle database and write OUT parameter values to the output view. If an OUT parameter is:

Custom type OBJECT, then the output is displayed as a JSON object.
Custom type TABLE, then the output is displayed as a JSON array.

This Snap supports executing stored functions with OUT and INOUT parameters and writes these parameters in the output view along with the returnval key.

JDBC Driver Upgrade

The Oracle JDBC Driver is upgraded from OJDBC6 JAR (v11.2.0.4) to OJDBC10 JAR (v19.20.0.0) in the latest distribution in October 2023 and deployed to the stable distribution in the November 2023 release (after the Snaplex upgrade). The latest JDBC driver upgrade is backward-compatible. Learn more: Oracle JDBC Driver Upgrade from v11.2.0.4 to v19.20.0.0 and JOOQ Upgrade from v3.9.1 to 3.17.x.

You can consume this driver upgrade with the 434patches23000 Snap Pack version.

Behavior Change

This JDBC driver upgrade has resulted in specific behavior changes that include errors, status codes, and success and failure messages. Learn more about the behavior changes to ensure your migration to the upgraded driver is seamless.

Snap type:

Write

Examples:

Example 1: Stored procedure has output parameters firstName, lastName and both are of built-in type VARCHAR2.

The output document is:

{
    firstName: "John",
    lastName: "Smith"
}

Example 2: Stored procedure has three output parameters firstName, lastName, and hobbies where firstName and lastName are of built-in type VARCHAR2 and hobbies is of custom type TABLE.

The output document is:

{
    firstName: "John",
    lastName: "Smith",
    hobbies:[
                        "swimming",
                        "reading",
                        "joking"
                      ]
}

Example 3: Stored procedure has three output parameters firstName, lastName, and location where firstName and lastName are of built-in type VARCHAR2 and location is of custom type OBJECT.

The output document is:

{
    firstName: "John",
    lastName: "Smith",
    location: {
                        "ADDRESS":"1520 8th Ave N",
                        "CITY":"San Mateo",
                        "STATE":"CA"
                      }
}

Example 4: Stored function accepts a customerId (NUMBER) and returns the customer's name (VARCHAR2).
The output document is:

{

"returnval": "Acme Corporation"

}

The attribute names of OBJECT are not displayed with the default JDBC driver. With a custom JDBC driver, they are displayed as Field1, Field2, Field3, etc.

User-defined types are only supported with a specific version of the JDBC driver. Refer to the JDBC Driver setting in Oracle Account.

There is a limitation in Oracle JDBC driver that prevents the passing of a record type parameters to the stored procedure. Refer the link: http://docs.oracle.com/cd/E11882_01/java.112/e16548/apxref.htm#JJDBC28928

A workaround could be to write a wrapper stored procedure to avoid passing of record type parameter directly to the original stored procedure.

Known Issues

Support for Ultra pipelines

Works in Ultra Task Pipelines.

Account:

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Oracle Account for information on setting up this type of account.

Views:

Input	This Snap allows none or one input view. If an input view is defined, then values from an incoming document can be used as input parameters to the stored procedure. Note: The attribute names of custom type OBJECT are case-sensitive. For example, for custom type LOCATION with three fields ADDRESS, CITY and STATE, the input below is acceptable: location: { "ADDRESS":"1520 8th Ave N", "CITY":"San Mateo", "STATE":"CA" } But the input below won't be accepted: location: { "address":"1520 8th Ave N", "city":"San Mateo", "state":"CA" }
Output	This Snap has exactly two document output views, Output Parameters and Result Set.
Error	This Snap has at most one error view and produces zero or more documents in the view.

Settings

Label

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

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.

Default value: None
Example: SYS

Package name

The package name where the procedure resides. The property is suggestible and will return all packages of the DB. If a schema is defined, then it will only return the packages of that schema.
Example: PACKAGE2

To invoke stored functions in a package, you need to upgrade the Oracle JDBC driver to 12.1.0.2 or later.

User-defined types are supported only with a specific version of the JDBC driver. Refer to the JDBC Driver setting in Oracle Thin Account.

Stored Procedure Name

Required. Stored procedure to execute. The property is suggestible and will return all procedures of the DB. If a package is defined, then it will only return the procedures of that package. If a schema is defined and no package is defined, then it will return all procedures of that schema.

Example: addSeventeen
Default value: [None]

Procedure sequence

Required for overloaded procedures. Sequence number that indicates the procedure to be used for overloaded procedures. The property is optional and only to be used when the selected procedure is overloaded. The starting index is always 1. The property is suggestible and will return the available indexes of the overloaded procedure, if any. The procedure sequence instructions apply similarly to stored functions.

Example:

A procedure sp1 exists in a package pkg1 as sp1 (arg1, arg2) and sp1 (arg1, arg2, arg3), then the sequence number defines which procedure is used. Sequence number 1 uses sp1 (arg1, arg2) and sequence number 2 uses sp1 (arg1, arg2, arg3).
A function f1 exists in a package pkg1 as f1 (arg1, arg2) and f1 (arg1, arg2, arg3), then the sequence number defines which function is used. Sequence number 1 uses f1 (arg1, arg2) and sequence number 2 uses f1 (arg1, arg2, arg3).

Ignore Null Parameters

Select this check box to enable the Snap to ignore the parameters evaluated as null. This applies to parameters with defined default values.

Default value: Not selected

Parameter Values

Select the input parameter values for the stored procedure. If you define parameter values, you must do so in the same order as they appear in the stored procedure definition.

Example: There is a stored procedure named createGreeting. It has two input parameters: p1 and p2 of type VARCHAR2. Then you need to provide two string values. The first value goes to p1 and the second value goes to p2.

Default value: [None]

Quotation marks should not be used when setting input parameters unless they are part of the input value itself, since they are treated as escaped plain characters. For example, if the desired input value is TEST_VALUE1, the input parameter should be set as TEST_VALUE1, if you set it as "TEST_VALUE1", it will be recognized as \"TEST_VALUE1\".

If you do not provide any parameters in the Snap, you can still view the required input parameters in the Target Schema of the upstream Mapper Snap. The parameters are dynamically populated based on the column keys of the stored procedure; you can map the parameters and pass them as an input to the Stored Procedure Snap.

Pass through

If selected, the input document will be passed through to the output views under the key 'original'. The document will be passed to the Parameter output view, and it will also be passed to the Result Set output view if there is output sent from this view.

This property applies only to the Execute Snaps with SELECT statement or the Select Snaps.

Default value: Not selected

Custom type parameters mapping

optional

Supports mappings for all parameters.

Parameter index

The index is of the custom type parameter. It is suggestible based on stored procedure name.

The first parameter's index is 1 for stored procedures.
The first parameter's index is 2 for stored functions.
The return value has index 1 for stored functions.

Parameter type

The custom type name the parameter is of. Its suggestible based on database account.

Snap execution

Select one of the three modes in which the Snap executes. Available options are:

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.

Examples

We will provide two examples, the first one calls a simple stored procedure, the second one calls a procedure with user-defined type parameters.

1. Calling a simple Stored Procedure

In this example we want to call stored procedure TEST_PROC.

Here is the definition of stored procedure TEST_PROC:

CREATE OR REPLACE PROCEDURE TEST_PROC 
(
    in_sbset_id         IN  NUMBER
    ,test_date          IN  DATE
    ,test_timestamp     IN  TIMESTAMP
    ,test_timestamptz   IN  TIMESTAMP WITH TIME ZONE
    ,test_timestampltz  IN  TIMESTAMP WITH LOCAL TIME ZONE
    ,out_result         OUT VARCHAR2
)

AS
    l_sql_statement VARCHAR(4000);

BEGIN
    DBMS_OUTPUT.PUT_LINE('Started');
    DBMS_OUTPUT.PUT_LINE('test_date : ' || test_date);
    DBMS_OUTPUT.PUT_LINE('test_timestamp : ' || test_timestamp);
    DBMS_OUTPUT.PUT_LINE('test_timestamptz : ' || test_timestamptz);
    DBMS_OUTPUT.PUT_LINE('test_timestampltz : ' || test_timestampltz);
    l_sql_statement := 'INSERT INTO TEST_TABLE VALUES (
                           '||in_sbset_id||',
                           TO_DATE('''||test_date||''',''DD-MON-YYYY'') ,
                           TO_TIMESTAMP('''||test_timestamp||''') ,
                           TO_TIMESTAMP_TZ('''||test_timestamptz||''') ,
                           CAST('''||test_timestampltz||''' AS TIMESTAMP WITH LOCAL TIME ZONE))';
    COMMIT;
        
    DBMS_OUTPUT.PUT_LINE('l_sql_statement ::  '||l_sql_statement);
    EXECUTE IMMEDIATE l_sql_statement;
    COMMIT;

    DBMS_OUTPUT.PUT_LINE('Completed');
    out_result := 'SUCCESSFUL';
END TEST_PROC;

First, we use an Oracle Execute Snap, to get some input data from table TEST_TABLE.

Then, we use a Mapper Snap to map the data from the Oracle - Execute Snap to the Target paths, which the Oracle Stored Procedure Snap uses later.

In the Oracle Stored Procedure Snap, we define the stored procedure and parameters.

Upon validation, we see the output preview of the Oracle Stored Procedure Snap as shown below:

2. Oracle Stored Procedure with user-defined parameters

In this example we will call a Oracle Stored Procedure PROC_WITH_CUSTOM_IN_PARAM which has parameters of user-defined types.

Here is the definition of the stored procedure PROC_WITH_CUSTOM_IN_PARAM:

CREATE OR REPLACE PROCEDURE PROC_WITH_CUSTOM_IN_PARAM
(
    pPairsCount     IN  NUMBER
    ,pPrefix        IN  VARCHAR2
    ,pINMUIDS       IN  STRARRAY32
    ,pMUIDs         OUT STRARRAY32
    ,pAuthKeys      OUT STRARRAY49
    ,pDemoPeriod    OUT NUMBER
    ,pTransID       OUT NUMBER
    ,pErrorCd       OUT NUMBER
    ,pErrorMsg      OUT VARCHAR2
)

AS BEGIN
    select COUNT('s') Into pTransID from ACTRESS a;
    pMUIDs := STRARRAY32();
    pMUIDs.EXTEND(1);
    pAuthKeys := STRARRAY49();
    pAuthKeys.EXTEND(1);
    pMUIDs(1) := inMUIDS(1);
    pAuthKeys(1) := 'ABCD-r2mi-7vax-xn3m-hahj-2bqa-ev6f-dn3r-225x-ABCD';
    pErrorCd := 0;

    EXCEPTION 
    WHEN OTHERS THEN
        pErrorCd := 1;
        pErrorMsg := 'Some Error Happened.';

END PROC_WITH_CUSTOM_IN_PARAM;

First we use a JSON Generator Snap to pass parameter values as shown below to the Stored Procedure Snap:

Then we use the Stored Procedure Snap procedure name and define parameter values. As there are several parameters that are user-defined types, we add custom type mapping for them. Each mapping row consists of parameter index and type. Parameter index is the index when it is defined, and the parameter type is the name of the user-defined type. You can also use the Suggest button to get the list of available indices or types and select the needed one.

Upon validation, we see the output preview of the Oracle - Stored Procedure Snap as shown below:

3. Calling a simple stored function with custom type mapping

This Pipeline demonstrates invoking a stored function using the Oracle Stored Procedure Snap by defining a custom type mapping and documenting the indexing behavior. The return value has index 1 and the first parameter has index 2.

The code in the following section defines the stored function - payroll_pkg.employee_info.

We use the Oracle Execute Snap to query people table.

Then, we use the Mapper Snap to map Employee ID and Full name.

We use the Oracle - Stored Procedure Snap and select the stored procedure.

The Oracle Stored Procedure Snap invokes a stored function to lookup employee information, such as the employee's salary and hire date. The function accepts an Employee ID and returns a table of custom types (employee).

Downloads

Important steps to successfully reuse Pipelines

Download and import the pipeline into the SnapLogic application.
Configure Snap accounts as applicable.
Provide pipeline parameters as applicable.

	File	Modified

No files shared here yet.

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
November 2024	439patches29008	14 Nov 2024	Latest	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 `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. Breaking change: With the `439patches29008` Snap Pack version if any of your existing Oracle pipelines use the encoded `ROWID`(by manually handling the Base64 encoded data), your pipelines might break. To avoid potential pipeline failures, it is recommended to downgrade your Snap Pack to the previous version until the issue is resolved. Behavior change: Earlier, the `ROWID` columns were displayed in binary (Base64 encoded data) form in the output. With the `439patches29008`, the Oracle Execute and Select Snaps display the `ROWID` columns in string form in the output (which can be used for other operations downstream).
November 2024	main29029	13 Nov 2024	Stable	Updated and certified against the current SnapLogic Platform release.
August 2024	438patches27870	30 Aug 2024	Latest	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.
August 2024	main27765	21 Aug 2024	Stable	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.
May 2024	437patches26651	12 Jun 2024	Latest	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.
May 2024	437patches26346	14 May 2024	Latest	Fixed an issue with the Oracle - Execute Snap that displayed an error when handling `OffsetDateTime` type bindings.
May 2024	main26341	08 May 2024	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	26 Apr 2024	Latest	Fixed an issue with Oracle - Bulk Load Snap that intermittently displayed a `null pointer exception`. The exception is now replaced with `ConfigurationException`.
February 2024	436patches25696	02 Apr 2024	Latest	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 `hh:mm` format and had single digits (for example, 1:9) in the timestamp. The Oracle - Execute Snap displays both the status and the message in the output when you call stored procedures. Behavior Change: As part of `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 output
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	435patches24769	30 Jan 2024	Latest	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.
November 2023	435patches24445	19 Jan 2024	Latest	Enhanced the Oracle-Execute, Oracle-Select, and Oracle-Lookup Snaps with a Column-specific timestamp precision checkbox to represent column-specific timestamp precision for the string data type. The Oracle-Insert, Oracle-Update, and Oracle-Bulkload Snaps now support up to nanosecond precision for the string data type.
November 2023	435patches23823	20 Nov 2023	Latest	Fixed an issue with the Oracle-Stored Procedure Snap that displayed an error (`SnapDataException`) when custom JAR files were used in the Oracle Accounts. 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.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	434patches23000	13 Oct 2023	Latest	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.
August 2023	434patches22787	08 Sep 2023	Latest	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	16 Aug 2023	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	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	431patches19781	09 Feb 2023	Latest	The Oracle-Stored Procedure Snap works as expected and does not fail with the error `Invalid value type` when you pass BLOB data as a parameter to the stored procedure with BLOB datatype.
November 2022	431patches19275	14 Dec 2022	Latest	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 `returnval` key.
November 2022	main18944	10 Nov 2022	Stable	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.
September 2022	430patches17894	15 Sep 2022	Latest	The Oracle Select Snap now work as expected when the table name is dependent on an upstream input.
August 2022	430patches17658	07 Sep 2022	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	11 Aug 2022	Stable	Enhanced the Oracle - Merge and Oracle - Update Snaps with the Session parameters fieldset that provides National Language Support (NLS). Enhanced the Oracle - Stored Procedure Snap with a process that caches the fetched procedure metadata. Hence, the Snap processes the metadata calls only for the first few documents and does not process for subsequent documents, thereby improving the Snap's performance.
4.29 Patch	429patches16603	29 Jun 2022	Latest	Fixed an issue with Oracle Bulk Load Snap where the Snap encountered an error when trying to load data into `Timestampwithtimezone` datatype field. 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	14 May 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.28	main14627	12 Feb 2022	Stable	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. Updated the label for Delete Condition to Delete Condition (Truncates Table if empty) in the Snap Oracle Delete Snap
4.27	main12833	13 Nov 2021	Stable	Enhanced the Oracle - Execute Snap to invoke stored procedures. Enhanced the Oracle Bulk Load Snap with Additional SQL Loader Parameters field set to define additional SQL Loader parameters if required.
4.26	main11181	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25	425patches11008	04 Aug 2021	Latest	Improved the support for the CLOB data type in the Oracle - Insert Snap. Improved the error messages for all the Snaps in the Oracle Snap Pack where the Snaps fail with Null Pointer Exception when the account reference provided is invalid.
4.25	main9554	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main8556	13 Feb 2021	Stable	Enhances the Oracle - Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible. Enhances the Oracle - Stored Procedure Snap to ignore the parameters evaluated as null by using the Ignore Null Parameters check box. This applies to parameters with defined default values.
4.23	main7430	14 Nov 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.22	main6403	12 Sep 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.21 Patch	421patches6272	27 Jul 2020	Latest	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.
4.21 Patch	421patches6144	20 Jul 2020	Latest	Fixes the following issues with DB Snaps: The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive. Connection leaks occur during Pipeline execution.
4.21 Patch	MULTIPLE8841	19 May 2020	Latest	Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
4.21	snapsmrc542	09 May 2020	Stable	Updated the Oracle Thin Account and Oracle Thin Dynamic Account, enabling them to connect via Oracle Active Data Guard (ADG).
4.20 Patch	db/oracle8812	21 Apr 2020	Latest	Enhances the Oracle Snap Pack to support connections to the Oracle ADG (Active Data Guard) URL.
4.20 Patch	db/oracle8803	16 Apr 2020	Latest	Support for Oracle Database 19c.
4.20	snapsmrc535	08 Feb 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.19 Patch	db/oracle8408	13 Dec 2019	Latest	Fixes an issue with the Oracle - Update Snap wherein the Snap is unable to perform operations when: An expression is used in the Update condition property. Input data contain the character '?'.
4.19	snaprsmrc528	14 Nov 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.18 Patch	oracle7786	30 Aug 2019	Latest	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 .
4.18	snapsmrc523	10 Aug 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.17 Patch	db/oracle7459	26 Jun 2019	Latest	Fixed an issue with the Oracle Stored Procedure Snap wherein the Pipeline execution fails with an error when the input data type is CLOB.
4.17	ALL7402	11 Jun 2019	Latest	Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17	snapsmrc515	11 Jun 2019	Latest	Fixed an issue with the Oracle Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field. Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.
4.16 Patch	db/oracle6919	08 Mar 2019	Latest	Added a new property, Session parameters, in the Oracle Insert Snap to enable the use of National Language Support (NLS) parameters.
4.16 Patch	db/oracle6824	22 Feb 2019	Latest	Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end.
4.16	snapsmrc508	16 Feb 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.15 Patch	db/oracle6534	08 Jan 2019	Latest	Improved performance in Pipelines that contain child Pipelines.
4.15 Patch	db/oracle6417	29 Dec 2018	Latest	Fixed an issue with data types conversion. All fields with byte, short, int, or long data types will be converted to BigInteger after fetching.
4.15 Patch	db/oracle6284	05 Dec 2018	Latest	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.15	snapsmrc500	15 Dec 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.14	snapsmrc490	11 Aug 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.13 Patch	db/oracle5192	16 May 2018	Latest	Fixed the Oracle Bulk Load Snap that stores special characters incorrectly in the target table. Fixed the Oracle Bulk Load Snap that throws a `NullPointerException` error when the input letter case does not match with that of the Oracle table.
4.13	snapsmrc486	12 May 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.12 Patch	oracle4862	16 Mar 2018	Latest	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.
4.12 Patch	db/oracle4721	22 Feb 2018	Latest	Added a property, "SSL/TCPS" for Oracle Account.
4.12 Patch	MULTIPLE4744	22 Feb 2018	Latest	Enabled expression for Delete Condition in Oracle Delete Snap.
4.12	snapsmrc480	17 Feb 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.11 Patch	db/oracle4369	21 Dec 2017	Latest	Enhanced the Oracle Bulk Load Snap to accept date-type values in the format "yyyy-mm-dd".
4.11	snapsmrc465	11 Nov 2017	Stable	Upgraded with the latest SnapLogic Platform release.
4.10 Patch	oracle3633	17 Aug 2017	Latest	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.
4.10	snapsmrc414	12 Aug 2017	Stable	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	oracle3188	29 Jun 2017	Latest	Fixed the issue that "NaN" check was done to unexpected data types like varchar.
4.9.0 Patch	oracle3096	23 Jun 2017	Latest	Fixed a class casting issue for custom data types(BLOB, CLOB, NCLOB, etc) when custom Oracle JDBC driver is used.
4.9.0 Patch	oracle3071	01 Jun 2017	Latest	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.9	snapsmrc405	13 May 2017	Stable	Upgraded with the latest SnapLogic Platform release.
4.8.0 Patch	oracle2905	19 Apr 2017	Latest	Fix for SQL*Loader interpreting white-space only data as null values.
4.8.0 Patch	oracle2756	27 Mar 2017	Latest	Potential fix for JDBC deadlock issue.
4.8.0 Patch	oracle2711	01 Mar 2017	Latest	Fixed Oracle Snap Pack rendering dates that are one hour off from the date returned by database query for non-UTC Snaplexes.
4.8	snapsmrc398	11 Feb 2017	Stable	Database accounts now invalidate connection pools if account properties are modified and login attempts fail.
4.7.0 Patch	oracle2190	28 Nov 2016	Latest	Fixed an issue with the Oracle Select Snap regarding Limit rows not supporting an empty string from a pipeline parameter.
4.7	snapsmrc382	23 Nov 2016	Stable	Updated the Oracle - Stored Procedure Snap with the Pass through field. Resolved an issue in Oracle - Stored Procedure Snap that caused invalid column type failures. Oracle - Bulk Load updated to handle dates the same way as Oracle - Insert. Acceptable format for timestamp strings: 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) "yyyymmddThhmmss.SSS", (ex: 20161107T105512) 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" "yyyymmddThhmmss.SSSZ" "yyyy-mm-ddThh:mm:ss.SSS UTC" "yyyymmddThhmmss.SSS UTC" ex: 2016-11-07T10:55:12Z ex: 20161107T105512Z ex: 2016-11-07T10:55:12 UTC ex: 20161107T105512 UTC The ISO8601 format is used by many web services, Oracle Bulk Loader, and others.
4.6	snapsmrc362	13 Aug 2016	Stable	Resolved an issue in Oracle Select Snap that caused failures in the second output view when retrieving outputs from a table with a dot (.) character. Enhanced the Oracle Select Snap to fully support SQL statements with/without expressions & SQL bind variables. Extended support for Oracle Thin Dynamic accounts.
4.5.1	oracle1583	18 May 2016	Stable	Updated the Bulk Load Snap with a new field, Use direct path load, to enhance bulk loading performance. Resolved an issue with Oracle Select Snap failing if the table name included a dot (.) character.
4.4.1	NA	18 Mar 2016	Stable	Oracle Select: Resolved an issue with database access error occurring while iterating over table name result set when using an uploaded driver with a different version than the bundled driver. Resolved an issue with Oracle Stored Procedure Snap not accepting CLOB data. Made improvements to JDBC auto-commit consistency.
4.4	NA	13 Feb 2016	Stable	Table List Snap: A new option, Compute table graph, now lets you determine whether or not to generate dependents data into the output. Oracle Bulk Load Resolved an issue with a pipeline never completing. Resolved an issue with pipeline statistics, bulk load summary statistics not matching and bulk load summary was confusing. Maximum error count field added to set the maximum number of rows which can fail before the bulk load operation is stopped. Mixed-case matching option removed. Added error messaging to handle BLOB type data trying to be loaded to an Oracle table when not supported. Resolved an issue with the record separator of the input file not being processed correctly. Improved error messages for when data types do not match. Oracle Stored Procedure: All accessible objects are now visible during design.
4.3.2	NA	15 Jan 2016	Stable	Resolved an issue with Oracle Select not reading table names: Database access error occurred while iterating over table name result set. Resolved an issue with Oracle Bulk load failure: String index out of range: -1.
NA	NA	06 Jun 2015	Stable	Oracle Lookup failed in preview if DATE column was used for Lookup conditions Dynamic DB queries now supported in the Execute Snap. The SQL statement property now can be set as an expression property. When it is an expression, it will be evaluated with each input document and one SQL statement per each input document will be executed. Known issue: When the SQL statement property is an expression, the pipeline parameters are shown in the suggest, but not the input schema. With the SQL statement property set as an expression, the Snap can be exposed to SQL injection. Please use this feature with caution. Oracle Insert: When a string value is entered into a date col, its successfully inserting into db with null Oracle Stored Procedure: parameter type list was not populating even if a procedure had custom types defined.
NA	NA	15 May 2015	Stable	Oracle Execute error - no more documents will be written to SLFS Oracle Execute Snap failing with maximum number of documents reached Oracle Select Snap - Early dates are corrupted when reading data Oracle select- with date data type does not return Time(hh:mm:ss) Oracle Stored Procedure fails with error- Reason: invalid name pattern: TECTONIC.null Oracle Stored Procedure - fails with - "invalid name pattern: TECTONIC.strarray32 " when type name given in lower case
NA	NA	18 Oct 2014	Stable	The version number of the default Oracle JDBC driver (shared/ojdbc-6.1.jar) is now 11.2.0.4. Fixed the following defects: Oracle Stored Procedure: suggest method for parameter index throws -Suggestion value cannot be empty for property: customTypeParameterIndex 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: customTypeParameterType Oracle Stored Procedure: When custom type created in different schema, its not populating through Snap Oracle Select- Order by property as parameter fails Oracle Stored Procedure: Parameter type list- Can we make it in an order Oracle Snaps- When in account given a username which dont have privileges to access other schema, upon suggest all schema 's are populating Oracle Stored Procedure: NPE Oracle Stored Procedure: invalid name pattern: TECTONIC.STR_ARRAY_32_$ Oracle Stored Procedure: Procedure name mismatch error - suggest from parameter type when no package selected Oracle Stored Procedure: When in a schema if there are no types defined, showing null in type and index value Oracle Merge: error: "SQL operation failed" Oracle merge condition when expression is enabled, input schema in not getting populated Oracle Merge with expression more than 2 columns not working.getting Invalid identifier Oracle Merge: When expression enable- Fails with Failure: Could not evaluate expression: Oracle Stored Procedure: Failure: Failed to execute callable statement. Cause: invalid name pattern: TECTONIC.null.