This Snap allows you to fetch data from an Oracle database by providing a table name and configuring the connection. The Snap produces the records from the database on its output view which can then be processed by a downstream Snap.
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.
Snap type:
Read
Description:
JSON paths can be used in a query and will have values from an incoming document substituted into the query. However, documents missing values for a given JSON path will be written to the Snap's error view. After a query is executed, the query's results are merged into the incoming document overwriting any existing keys' values. The original document is output if there are no results from the query.
Queries produced by the Snap have an equivalent format:
SELECT * FROM [table] WHERE [where clause] ORDER BY [ordering] LIMIT [limit] OFFSET [offset]
If more powerful functionality is desired, then the Execute Snap should be used.
Expected upstream Snaps: A dynamic where a clause can be defined by providing values upstream, such as the Mapper Snap can provide constants, pipeline parameters mapped into variables, which then can be used in the where clause or even in the table/schema properties.
Expected downstream Snaps: The Snap will output one document for every record retrieved, hence any document processing Snap can be used downstream.
Expected input: Document that provides values for one or more properties of the Snap or simply for pass through purpose.
Expected output: Document for each record retrieved. Special types such as TIMESTAMP, TIMESTAMPTZ and TIMESTAMPLTZ are converted into SnapLogic internal date type representations which then can be consumed by downstream Snaps just like any other data type.
The where clause can only use variables, not constants or pipeline parameters.
A good example of a where clause is: SALARY =$SALARY (here we use the SALARY variable of the input document).
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 up to one input view. If the input view is defined, then the where clause can substitute incoming values for a given expression, such as a table name or as a variable as part of the where clause.
Output
A second view can be added to show the metadata for the table as a Document. The metadata document can then be fed into the second input view of Oracle - Insert or Bulk Load Snap so that the table is created in Oracle with a similar schema as the source table.
Error
This Snap has at most one error view and produces zero or more documents in the view.
Settings
Label*
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
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.
Default value: None Example: SYS
Table name*
Specify the table that the rows will be inserted into. This list is populated based on the tables associated with the selected schema.
Default value: None Example: people
Where clause
WHERE clause of SELECT statement. The value to be used in the WHERE clause will be used here. Document value substitutions (such as $person.firstname with the value found in the incoming document at the path) can also be used as needed. The "=" will not need to be checked when using document value substitutions unless using expression language.
"EMPNO=" + $EMPNO + " and ENAME='" + $EMPNAME+ "'"
Caution
Using expressions that join strings together to create SQL queries or conditions has a potential SQL injection risk and is hence unsafe. Ensure that you understand all implications and risks involved before using concatenation of strings with '=' Expression enabled.
The Where clause property does not support passing Pipeline parameters or passing upstream parameters.
Order by: Column names
Enter in the columns in the order in which you want to order by. The default database sort order will be used.
Default value: None Example:name, email
Limit offset
Specify the first row for the query.
Default value: None Example: 0
Limit rows
Specify the number of rows to return from the query.
Default value: None Example: 10
Output fields*
Enter or select output field names for SQL SELECT statement. To select all fields, leave it at default.
Default value: None Example: email, address, first, last
Fetch Output Fields In Schema
Select this check box to include only the selected fields or columns in the Output Schema (second output view). If you do not provide any Output fields, all the columns are visible in the output. If you provide output fields, we recommend you to select Fetch Output Fields In Schema check box.
Default value: Not selected
Pass through
Select this checkbox to pass the input document to the output view under the key 'original'.
Default value: Selected
Ignore empty result
Select this checkbox to ignore empty results, that is no document will be written to the output view when a SELECT operation does not produce any result. If you do not select this checkbox and select the Pass through checkbox, the input document will be passed through to the output view.
Default value: Not selected
Auto commit
Select one of the options for this property to override the state of the Auto commit property on the account. The Auto commit at the Snap-level has three values: True, False, and Use account setting. The expected functionality for these modes are:
True - The Snap will execute with auto-commit enabled regardless of the value set for Auto commit in the Account used by the Snap.
False - The Snap will execute with auto-commit disabled regardless of the value set for Auto commit in the Account used by the Snap.
Use account setting - The Snap will execute with Auto commit property value inherited by the Account used by the Snap.
Default value: False
Match data types
Conditional. If you select this checkbox, the Snap matches the output data types same as when the Output fields property is empty (SELECT * FROM ...). The output preview would be in the same format as the one when SELECT * FROM is implied and all the contents of the table are displayed.
This field applies only when the Output fields field is provided with any values.
Default value: Not selected
Number of retries
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
If the value is larger than 0, the Snap first downloads the target file into a temporary local file. If any error occurs during the download, the Snap waits for the time specified in the Retry interval and attempts to download the file again from the beginning. When the download is successful, the Snap streams the data from the temporary file to the downstream Pipeline. All temporary local files are deleted when they are no longer needed.
Ensure that the local drive has sufficient free disk space to store the temporary local file.
Default value: 0
Example:3
Retry interval (seconds)
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
Staging mode
Required when the value in the Number of retries field is greater than 0.
Specify the location from the following options to store input documents between retries:
In memory: The query results are stored in the Snaplex memory. If the query is too large to fit in the memory space, it may cause the Snap to fail, choose the On disk option.
On disk: The query results are stored on the disk in a temporary (tmp) directory that is managed by the SnapLogic platform. This directory is deleted automatically when the Snap terminates.
Default value: In memory
To disable staging, enter 0 in the Number of retries field.
Column-specific timestamp precision
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
Select one of the following three modes in which the Snap executes:
Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
Disabled: Disables the Snap and all Snaps that are downstream from it.
Default Value: Execute only
Example: Validate & Execute
For the 'Suggest' in the Order by columns and the Output fields properties, the value of the Table name property should be an actual table name instead of an expression. If it is an expression, it will display an error message "Could not evaluate accessor: ..." when the 'Suggest' button is clicked. This is because, at the time the "Suggest" button is clicked, the input document is not available for the Snap to evaluate the expression in the Table name property. The input document is available to the Snap only during the preview or execution time.
Examples
Using the Where clause with expressions enabled:
The values are passed upstream for the Oracle Select Snap to fetch the data from a table:
The Oracle Select Snap retrieves the records from the EMPTABLE. The values passed from the upstream for the Where clause in different ways is displayed below:
Without expressions enabled: The values are directly passed for the Select Snap to retrieve the specified records.
With expressions enabled:
The queries can be passed in either of the ways as below for the above upstream values (using the Mapper Snap):
"EMPNO=$EMPNO and ENAME=$EMPNAME"
"EMPNO=" + $EMPNO + " and ENAME='" + $EMPNAME+ "'"
Successful execution of the Snap displays the below output preview, with the field names as provided from the upstream:
Following are the two examples. The first one using a where clause for a conditional retrieval. The second one will showcase error handling.
1. Using a where clause for a conditional retrieval
The first Oracle Execute Snap will drop the existing table. We use an error view to handle the case where the table does not exist yet. Both the error and the output view then are funneled into a Union Snap which triggers the actual insertion data provided by a JSON Generator Snap.
Then we use a Mapper Snap to map back the original input data and use a Tail to use the last record (having the color black).
Next, we select on the table using the where clause: "color"=$color, which will retrieve the color black from the table and write it to the output view. Hint: The table COLOR1 was created on the fly, and the color column is created lowercase. We quote the color column in the merge condition since it is defined as a lower case column on the table. Hint: Multiple columns can be used in an expression such as "color"=$color and "value"=$value
2. Error view on the Oracle Select Snap
In the second example, we use an error view on the Oracle Select Snap.
Here we mis-typed the variable in the condition, which will trigger an error. The error will be written to the error view of the Snap, which then can be used for debugging purpose or further processing. An example of the error view is shown below.
Error is the message provided by SnapLogic.
Reason is defined as the underlying reason of the error, here the path $colo does not exist in the input view.
Original is defined as the data from the input view.
invalidValuePath: "$" error: "Unable to read path: $.colo" reason: "Field not found in JSON object: colo" invalidSubPath: "$.colo" original: color: "black" value: "#000" resolution: "Check the path syntax" stacktrace: "com.Snaplogic.jsonpath.FieldNotFoundException: Field not found in JSON object: colo\n ... invalidValue: color: "black" value: "#000"
Getting Data For Columns Using Fetch Output Fields In Schema
In this example Pipeline, we use an Oracle Select Snap to get data for only the fields that we provide in the Output fields list.
We configure the Oracle Select Snap to get data from TECTONIC.EMPLOYEE table, and fetch EMPLOYEE_ID and EMPLOYEE_NAME columns in the output.
On validation, we see that only the selected output fields (EMPLOYEE_ID and EMPLOYEE_NAME) appear in the preview and column schema.
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
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
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
Latest
Fixed an issue with the Oracle - Execute Snap that displayed an error when handling OffsetDateTimetype bindings.
May 2024
main26341
Stable
Updated the Delete Condition (Truncates a Table if empty) field in the Oracle - DeleteSnap 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
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
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
Stable
Updated and certified against the current SnapLogic Platform release.
November 2023
435patches24769
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
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.
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
Stable
Updated and certified against the current SnapLogic Platform release.
August 2023
434patches23000
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
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
Stable
The Oracle - ExecuteSnap now includes a newQuery typefield. WhenAutois selected, the Snap tries to determine the query type automatically.
May 2023
main21015
Stable
Upgraded with the latest SnapLogic Platform release.
February 2023
main19844
Stable
Upgraded with the latest SnapLogic Platform release.
November 2022
431patches19781
Latest
TheOracle-Stored ProcedureSnap works as expected and does not fail with the error Invalid value type when youpass BLOB data as a parameter to the stored procedure with BLOB datatype.
November 2022
431patches19275
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 returnvalkey.
November 2022
main18944
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
Latest
The Oracle Select Snap now work as expected when the table name is dependent on an upstream input.
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
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
Latest
Fixed an issue with Oracle Bulk Load Snap where the Snap encountered an error when trying to load data into Timestampwithtimezonedatatype 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
Stable
Upgraded with the latest SnapLogic Platform release.
4.28
main14627
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 DeleteSnap
Enhanced the Oracle Bulk Load Snap with Additional SQL Loader Parameters field set to define additional SQL Loader parameters if required.
4.26
main11181
Stable
Upgraded with the latest SnapLogic Platform release.
4.25
425patches11008
Latest
Improved the support for the CLOB data type in the Oracle - Insert Snap.
Improved the error messages for all the Snaps in the OracleSnap Pack where the Snaps fail with Null Pointer Exception when the account reference provided is invalid.
4.25
main9554
Stable
Upgraded with the latest SnapLogic Platform release.
4.24
main8556
Stable
Enhances the Oracle - SelectSnap 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 theIgnore Null Parameterscheck box. This applies to parameters with defined default values.
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
Fixes the issue whereSnowflake SCD2Snap generates two output documents despite no changes toCause-historizationfieldswithDATE, TIME and TIMESTAMPSnowflake data types, and withIgnore unchanged rowsfield selected.
4.21 Patch
421patches6144
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
Latest
Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
Enhances the Oracle Snap Pack to support connections to the Oracle ADG (Active Data Guard) URL.
4.20 Patch
db/oracle8803
Latest
Support for Oracle Database 19c.
4.20
snapsmrc535
Stable
Upgraded with the latest SnapLogic Platform release.
4.19 Patch
db/oracle8408
Latest
Fixes an issue with the Oracle - Update Snap wherein the Snap is unable to perform operations when:
An expression is used in theUpdate conditionproperty.
Input data contain the character '?'.
4.19
snaprsmrc528
Stable
Upgraded with the latest SnapLogic Platform release.
4.18 Patch
oracle7786
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
Stable
Upgraded with the latest SnapLogic Platform release.
4.17 Patch
db/oracle7459
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
Latest
Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17
snapsmrc515
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
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
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
Stable
Upgraded with the latest SnapLogic Platform release.
4.15 Patch
db/oracle6534
Latest
Improved performance in Pipelines that contain child Pipelines.
4.15 Patch
db/oracle6417
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
Latest
Replaced the existingMax idle timeandIdle connection testperiodproperties withMax life timeandIdle Timeoutproperties 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
Stable
Upgraded with the latest SnapLogic Platform release.
4.14
snapsmrc490
Stable
Upgraded with the latest SnapLogic Platform release.
4.13 Patch
db/oracle5192
Latest
Fixed the Oracle Bulk Load Snap that stores special characters incorrectly in the target table.
Fixed the Oracle Bulk Load Snap that throws aNullPointerException error when the input letter case does not match with that of the Oracle table.
4.13
snapsmrc486
Stable
Upgraded with the latest SnapLogic Platform release.
4.12 Patch
oracle4862
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
Latest
Added a property, "SSL/TCPS" for Oracle Account.
4.12 Patch
MULTIPLE4744
Latest
Enabled expression for Delete Condition in Oracle Delete Snap.
4.12
snapsmrc480
Stable
Upgraded with the latest SnapLogic Platform release.
4.11 Patch
db/oracle4369
Latest
Enhanced the Oracle Bulk Load Snap to accept date-type values in the format "yyyy-mm-dd".
4.11
snapsmrc465
Stable
Upgraded with the latest SnapLogic Platform release.
4.10 Patch
oracle3633
Latest
FixedBULKLOAD 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
Stable
AddedAuto commitproperty to the Select and Execute Snaps at the Snap level to support overriding of theAuto commitproperty at the Account level.
4.9.0 Patch
oracle3188
Latest
Fixed the issue that "NaN" check was done to unexpected data types like varchar.
4.9.0 Patch
oracle3096
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
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
Stable
Upgraded with the latest SnapLogic Platform release.
4.8.0 Patch
oracle2905
Latest
Fix for SQL*Loader interpreting white-space only data as null values.
4.8.0 Patch
oracle2756
Latest
Potential fix for JDBC deadlock issue.
4.8.0 Patch
oracle2711
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
Stable
Database accounts now invalidate connection pools if account properties are modified and login attempts fail.
4.7.0 Patch
oracle2190
Latest
Fixed an issue with the Oracle Select Snap regarding Limit rows not supporting an empty string from a pipeline parameter.
4.7
snapsmrc382
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.
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
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
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
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
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
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
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
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
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.