In this article

Overview

You can use this Snap to execute an Oracle statement or query. This is a Write Snap type. This Snap works only with single queries.

This Snap:

is for simple DML (SELECT, INSERT, UPDATE, DELETE) type statements. For the comprehensive scripting functionality offered by various databases, use stored procedure functionality offered by their chosen database using the Stored Procedure Snap.
might drop your database, hence be cautious.

If you execute a SELECT query, the query's results are merged into the incoming document and the values of any existing keys will be overwritten. On the other hand, if there are no results from the query, the original document is written.
Any valid JSON paths that you define in the WHERE clause for queries/statements are substituted with values from an incoming document. Documents will be written to the error view if the document is missing a value to be substituted into the query/statement.

Upcoming

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.

Prerequisites

None.

Support for Ultra Pipelines

Works in Ultra Pipelines.

Limitations

Due to the limitation in Oracle JDBC driver, the SQL statement cannot have semicolons at the end except that it is a BEGIN-END block.
This Snap cannot invoke procedures, hence we recommend that you use Oracle Stored Procedure Snap for invoking procedures.

Known Issues

When the SQL statement property is an expression, the Pipeline parameters are shown in the Suggest, but not the input schema.

Behavior Change

In 4.26, when the stored procedures were called using the Database Execute Snaps, the queries were treated as write queries instead of read queries. So the output displayed message and status keys after executing the stored procedure.
In 4.27, all the Database Execute Snaps run stored procedures correctly, that is, the queries are treated as read queries. The output now displays message key, and OUT params of the procedure (if any). The status key is not displayed.
If the stored procedure has no OUT parameters then only the message key is displayed with value success.

If you have any existing Pipelines that are mapped with status key or previous description then those Pipelines will fail. So, you might need to revisit your Pipeline design.

As part of main23721 (because of the JOOQ upgrade) previously, when you used a stored procedure in the Oracle-Execute Snap, the Snap displayed a Message:Success in the output. Now, the Snap displays $UPDATE_COUNT=-1.
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.

Snap Input and Output

Input/Output	Type of view	Number of views	Examples of Upstream/Downstream Snap	Description
Input	Document	Min:0 Max:1	JSON Generator JSON Formatter XML Formatter	This Snap has at most one document input view. If the input view is defined, then the where clause can substitute incoming values for a given expression.
Output	Document	Min:1 Max:1	Mapper Copy JSON Formatter and File Writer	This Snap has at most one document output view. If an output view is available and an update/insert/merge/delete statement was executed, then the original document that was used to create the statement will be output with the status of the statement executed. 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 Field Type Description

Label*

String

Enter a unique 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.

Default Value: Oracle Execute
Example: Oracle Execute

SQL statement*

String

Specify the SQL statement to execute on the server.

Executing SQL statements in SnapLogic

You must understand the following scenarios to successfully execute your SQL statements:

Scenario 1: Executing SQL statements without expressions
If you do not enable the expression toggle of the SQL statement field:

The SQL statement must not be within quotes.
The $<variable_name> parts of the SQL statement are expressions. In the below example, $id and $book.

Examples:

email = 'you@example.com' or email = $email
emp=$emp

Additionally, the JSON path is allowed only in the WHERE clause. If the SQL statement starts with SELECT (case-insensitive), the Snap regards it as a select-type query and executes once per input document. If not, it regards it as write-type query and executes in batch mode.

If your Oracle table has columns whose names contain a '$' (or any other special character) in it, enclose the column name within quotes, such as: select "USER$ID" from testtable1

Scenario 2: Executing SQL queries using expressions
If you enable the expression toggle of the SQL statement field:

The SQL statement must be within quotes.
The + $<variable_name> + parts of the SQL statement are expressions, and must not be within quotes. In the below example, $tablename.
The $<variable_name> parts of the SQL statement are bind parameter, and must be within quotes. In the below example, $id and $book.

Table name and column names must not be provided as bind parameters. Only values can be provided as bind parameters.

Examples:

"EMPNO=$EMPNO and ENAME=$EMPNAME"
"emp='" + $emp + "'"
"EMPNO=" + $EMPNO + " and ENAME='" + $EMPNAME+ "'"

Select * from "Snap10gic$#_1".emp order by ID asc
select firstname from test.cyclist_name
INSERT statement "insert into " + $tablename + " (city, temp_lo, temp_hi, date) values ('" + $city + "','" + $temp_lo + "', '" + $temp_hi + "', '" + $date + "')"
"select * from " + $tablename

The non-expression form uses bind parameters, so it is much faster than executing N arbitrary SQL expressions.
Using expressions that join strings together to create SQL queries or conditions has a potential SQL injection risk and hence unsafe. Ensure that you understand all implications and risks involved before using concatenation of strings with '=' Expression enabled.
The '$' sign and identifier characters, such as double quotes (“), single quotes ('), or back quotes (`), are reserved characters and should not be used in comments or for purposes other than their originally intended purpose.

We recommend you to add a single query in the SQL Statement field.

We recommend you to use the Oracle Stored Procedure Snap for invoking procedures as the Oracle Execute Snap has the following limitation while invoking procedures:

Procedures have to invoked as a PL/SQL block (with older jdbc JARs). However, with this approach the output parameters cannot be sent to the output view. Besides, the latest oracle jdbc drivers do not support PL/SQL.

Oracle JDBC documentation recommends using CallableStatement for invoking procedures, which is what the Oracle Stored Procedure Snap does.

Single quotes in values must be escaped

Any relational database (RDBMS) treats single quotes (') as special symbols. So, single quotes in the data or values passed through a DML query may cause the Snap to fail when the query is executed. Ensure that you pass two consecutive single quotes in place of one within these values to escape the single quote through these queries.

For example:

If String	To pass this value	Use
Has no single quotes	Schaum Series	`'`Schaum Series`'`
Contains single quotes	`O'Reilly's Publication`	'`O''Reilly''s Publication`'

Default Value: [None]

Query type

Dropdown list/Expression

Select the type of query for your SQL statement (Read or Write).

When Auto is selected, the Snap tries to determine the query type automatically.
If the execution result of the query is not as expected, you can change the query type to Read or Write.

Default Value: Auto
Example: Read

Pass through

Checkbox

Select this checkbox to pass the input document to the output view under the key 'original'. This field applies only to the Execute Snaps with SELECT statement.

Default Value: Selected

Ignore empty result

Checkbox

Select this checkbox to not write any document to the output view when a SELECT operation does not produce any result.
If you deselect this checkbox and select Pass through, the input document will be passed through to the output view.

Default Value: Not selected

Auto commit

Dropdown list

Choose one of the options from the list to override the state of the Auto commit on the account. The available options are:

True - The Snap executes with auto-commit enabled regardless of the value set for Auto commit in the Account used by the Snap.
False - The Snap executes with auto-commit disabled regardless of the value set for Auto commit in the Account used by the Snap.
Use account setting - The Snap executes with Auto commit property value inherited by the Account used by the Snap.

Default Value: Use account setting

'Auto commit' may be enabled for certain use cases if PostgreSQL jdbc driver is used in either Redshift, PostgreSQL or generic JDBC Snap. But the JDBC driver may cause out of memory issues when Select statements are executed. In those cases, “Auto commit" in Snap property should be set to ‘False’ and the Fetch size in the “Account setting" can be increased for optimal performance.

Behavior of DML Queries in Database Execute Snap when auto-commit is false

DDL queries used in the Database Execute Snap will be committed by the Database itself, regardless of the Auto-commit setting.
When Auto commit is set to false for the DML queries, commit will be called only at the end of the pipeline lifecycle.
Instead of building multiple Snaps with inter dependent DML queries, we recommend you to use the Oracle - Stored Procedure Snap.
The Auto commit needs to be true in a scenario where the downstream Snap does depend on the data processed on an Upstream Database Execute Snap containing a DML query.
When the Auto commit is set to the Use account setting on the Snap, the account level commit needs to be enabled.

Number of retries

Integer

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.

Default Value: 0
Example: 3

Retry interval (seconds)

Integer

Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception.

Default Value: 1
Example:10

Column-specific timestamp precision

Checkbox

Select this checkbox to display the timestamp with millisecond/microsecond/nanosecond precision in string type.

By default, the checkbox is deselected, which maintains the backward compatibility (supports only millisecond of date time type).

Default Value: Deselected

Snap Execution

Dropdown list

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

Get the student's records from a table

In this example, we have a table named STUDENT that stores students' scores. It has 3 columns: ID, NAME and SCORE. We will get the record of a student named "Brace" with this pipeline:

The JSON Generator Snap passes the student's name to Oracle-Execute Snap:

The Oracle-Execute Snap executes a select SQL statement to get the student's information from table STUDENT. Note that the student's name passed from previous Snap can be accessed with "$name".

Here is the running result of the pipeline:

Error handling on the Snap

This example will show the error handling of the Snap.

We use the same pipeline as the one in example #1 and route error messages to error view:

The Oracle - Execute Snap tries to select AGE column that doesn't exist in table STUDENT. This should cause a SQL execution error and the error message will be routed to error view:

Here is the error message that is routed to the error view:

Downloads

Important steps to successfully reuse Pipelines

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

	File	Modified
Labels No labels Preview View	File Example_Oracle_execute.slp	Feb 23, 2022 by Subhajit Sengupta

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
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.