You can use this Snap to insert data parallelly across multi-threaded tasks. Compared to the Oracle Bulk Load Snap, this Snap executes a high-performance data load.
The Parallel Load Snap currently always auto-commits its database operations. The Auto commit setting in the Oracle Thin Account or Oracle Thin Dynamic Account configured for the Parallel Load snap does not affect the Snap’s behavior.
Snap Type
The Oracle - Parallel Load Snap is a Write-type Snap that writes the specified data in the target table.
The Schema name and Table name settings both accept schema from upstream snaps and offer suggestions for expressions; however, we recommend that you do not use those suggestions as they cause incorrect behavior.
Snap Views
Type
Format
Number of Views
Examples of Upstream and Downstream Snaps
Description
Input
Document
Min: 1
Max: 2
Mapper
Copy
Requires the Schema name and Table name to process a certain number of input documents into a prepared insert query and execute all of the prepared input document values on that query as a batch.
Output
Document
Min: 0
Max: 1
Mapper
Snap outputs the number of documents successfully inserted into the target table in the output view document.
Error
Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution. Learn more about Error handling in Pipelines.
Add icon ( ): Indicates that you can add fields in the field set.
Remove icon ( ): Indicates that you can remove fields from the field set.
Expression icon (): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Upload icon (): Indicates that you can upload files. Learn more about managing Files.
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
Default Value: N/A Example: Sys
String/Expression
Specify the database schema name.
You can pass the values as expressions using the pipeline parameters but cannot use values from the upstream Snap.
Table name*
Default Value: N/A Example: people
String/Expression
Specify the table on which to execute the load operation.
You can pass the values as expressions using the pipeline parameters but cannot use values from the upstream Snap.
Create table if not present
Default Value: Deselected
Checkbox
Select this checkbox to automatically create the target table if it does not exist.
If a second input view is configured for the Snap and it contains a document with schema (metadata) from the source table, the Snap creates the new (target) table using the same schema (metadata). However, if the schema comes from a different database, the Snap might fail with the Unable to create table: "<table_name>" error due to data type incompatibility.
In the absence of a second input view, the Snap creates a table based on the data types of the columns generated from the first row of the input document (first input view).
The newly created table is not visible to subsequent database Snaps during runtime validation because of implementation details. If you want to immediately use the newly updated data, you must use a child pipeline invoked through the Pipeline Execute Snap.
Maximum thread count*
Default Value: 0 Example: 20
Integer/Expression
Specify the maximum number of threads allowed to perform data insertions simultaneously. If the value is 0, the snap automatically sets the number of threads equal to the number of available processors on the system.
There is no upper limit for the Maximum thread count, therefore you should exercise caution when setting this value to avoid unexpected behavior or performance degrade.
Batch capacity*
Default Value: 1000 Example: 500
Integer/Expression
Specify the maximum number of records allowed in a single batch for an insertion task.
There is no upper limit for Batch capacity, therefore you should exercise caution when setting this value to avoid unexpected behavior or performance degrade.
Snap memory usage: To gracefully handle failed record insertions, the Snap must retain some input document data in memory during the Snap execution. To calculate the memory usage follow this formula: Max thread count * Batch capacity * 2 * typical record size For example, with a Maximum thread count of 4, a Batch capacity of 10,000, and an average record size of 50 bytes, the input document data in Snap memory may peak at 4 million bytes.
Maximum error count*
Default Value: 50 Example:10
Integer/Expression
Specify the maximum number of record insertion errors allowed before execution stops on the next error. For example, if you specify a value of 10, the pipeline execution continues until the number of failed records exceeds 10.
A value of -1 means no limit. At least one more error document than the specified maximum value is expected, but task concurrency may result in additional error documents. This applies only when the error behavior is set to Route Error Data to Error View.
Truncate table before load
Default Value: Deselected
Checkbox/Expression
Select this checkbox to truncate the target table before loading data.
Snap Execution
Default Value: Example: Validate & Execute
Dropdown list
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.
Troubleshooting
Error
Reason
Resolution
Pre-load truncation of the target table failed
The target table may not exist or a database access error may have occurred when trying to execute the TRUNCATE statement.
Verify your database credentials and ensure the target table exists, then try again.
Unable to determine target table column names
The connection used to retrieve table metadata displayed an exception while closing.
Verify the target table column names and try again.
Behavior of Parallel Load Execution with Open Error Views
The following table describes the expected behavior for the general outcomes of Parallel Load execution when the Snap has an open error view (that is, when you select Route Error Data to Error View for When error occurs).
Committed database insertions
Error view
Output preview
Snap outcome
Final Snap state
All insertions committed.
N/A
One document containing <insert_count> field with an integer value indicating the number of inserted records successfully.
All input records are successfully inserted to the target database.
Success
One error document for each record that failed to insert.
One document containing <insert_count> field with an integer value indicating the number of inserted records successfully.
Some input records individually fail to insert into the target database, but do not exceed maximum error count.
Success
Insertions made successfully prior to the Maximum error count being exceeded may be committed.
Multiple error documents, one for each record that failed to insert. The total number of error documents should be equal to at least the Maximum error count plus one, but might be more due to concurrency of attempted insertions.
One document containing <insert_count> field with an integer value indicating the number of inserted records successfully prior to exceeding maximum error count.
Enough input records individually fail to insert to exceed the Maximum error count and cause the Snap to end execution early.
Success
Insertions made successfully prior to the Snap-failing error may be committed.
One error document for each record that individually failed insertion (if any).
One document containing <insert_count> field with an integer value indicating the number of inserted records successfully prior to the (Snap-failing) error.
An error occurs beyond the scope of any individual record.
Failure
Individual record insertion failures occur when the database encounters an error during the insertion of a record. These failures are recoverable and specific to one input document. For example, an error might occur if the value of a document field is incompatible with the data type of the target column.
Examples
Parallel Loading for Document Insertion
The following example pipeline demonstrates the use of Parallel Load to insert 1000 documents. It showcases Parallel Load's efficiency and capability in managing large-scale data insertion tasks.
Configure the Mapper Snap with subscriber details (Subscriber ID, Last Login, and Subscriber’s full name) to pass them to the Oracle - Parallel Load Snap.
Configure the Oracle - Parallel Load Snap with the following settings:
Maximum thread count: 4
Batch capacity: 100
On validation, the pipeline inserts a maximum of 400 records simultaneously, across 4 threads handling 100 records each. The image below displays only 50 records because the Preview document count is set to 50.
Handle Database Insertion Failures with Open Error View
This example demonstrates a Mapper Snap configuration designed to intentionally cause a small number of records to fail during database insertion. For every failed insertion, an error document is generated. Specifically, out of 1000 records, 7 are expected to fail, resulting in 7 error documents, while the remaining 993 records are successfully inserted. The count of successful insertions is also recorded in the output document. This pipeline demonstrates how to manage and log insertion errors efficiently.
Configure the Mapper Snap with settings so that a small number of records fail during database insertion, and route the error documents to the error view.
Configure the Oracle - Parallel Load Snap as follows to insert a total of 1000 documents.
On validation, 993 records are successfully inserted and written to the output document, while 7 error documents are written on the error view. The image below displays only 47 records because the Preview document count is set to 50.
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.
Snap Pack History
Click here to expand...
Click to view/expand
Release
Snap Pack Version
Date
Type
Updates
August 2024
438patches27870
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
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.