Generic Database Account

In this article

Overview

You can use this account type to connect JDBC Snaps with data sources that use Generic Database account.

Prerequisites

None.

Limitations

None.

Known Issue

Generic JDBC Snaps connecting to Informix database through the Generic Database account can cause thread leaks due to JDBC driver implementations.

Workaround: To avoid these thread leaks, do the following:

  • Use the Informix JDBC driver version 4.50.4.1 or a higher version.
  • Configure the following URL properties in the account settings:
    • Url Property name: IFMXCONNECTION_CLEANER_THREADS
    • Url property value: 0

Behavior Change

From 4.27 release, the validation message after executing SQL query is different when Batch size is 1.

  • Till 4.26 release, for invalid test data, the database Snaps displayed the error message as follows:
    {error=Batch operation failed, reason=<Reason for Failure>}
    For example, {error=Batch operation failed, reason=Data truncation: Data too long for column 'id' at row 1, error code: 1406, SQL state: 22001}
  • In 4.27 release, when Batch size is 1, SQL statement is executed as individual statement and the error message displayed is as follows:
    {error=SQL operation failed, reason=<SQL Statement and Reason>}]
    For example, {error=SQL operation failed, reason=SQL [INSERT into enron.book (id, book) VALUES (?,?)]; Data truncation: Data too long for column 'id' at row 1}]

    If any of your existing Pipelines depend on error messages, then such pipelines might fail post SnapLogic upgrade to 4.27.


Account Settings

Field names marked with an asterisk ( * ) are mandatory.

Field Name

Field Type

Description

Label*

String

Specify a unique label for the account.

Default Value: N/A
Example: Generic Database Account

Account properties*The information required to create a connection to the database.

JDBC JARs

Use this field set to define JDBC Drivers. This field set consists of the JDBC Driver field.

JDBC Driver*String

Specify the JDBC driver to use. Click the Upload icon to upload the JDBC driver that you want. Click Add  to add a row for specifying a JDBC driver. Specify each driver in a separate row.

  • Type 3 and Type 4 JDBC drivers are only supported. Type 4 JDBC driver is recommended. For more information on JDBC driver versions and downloads, see https://www.ibm.com/support/pages/db2-jdbc-driver-versions-and-downloads
  • You can upload the JDBC drivers through Designer or Manager and it is stored on a per project basis. That is, only users with access to that project can view the uploaded JDBC drivers. To provide access to all users of your org, place the driver in the /shared project.
  • We recommend you to use the db2jcc.jar driver for DB2 with your JDBC account. The DB2 version 11.5 supports only JDBC 4.0 Driver (db2jcc4.jar) and 11.1 version supports JDBC 3.0 driver (db2jcc.jar) and JDBC 4.0 Driver (db2jcc4.jar).

Default Value: N/A
Examplevertica-jdk5-6.1.2-0.jar

JDBC Driver Class*

String

Specify the JDBC Driver class name to use.

Default Value: [None]
Examplecom.vertica.jdbc.Driver

JDBC URL

String

Specify the JDBC URL to use.

Default Value: [None]
Example: jdbc:vertica://Snaplogic.com/database

UsernameString

Specify the database username to use.

Default Value: N/A
ExampleSnapuser

PasswordString

Specify the database password to use.

Default Value: N/A
Example: k*#!@09

Database nameString

Choose a database to which the account must be connected. The available options are:

  • Auto detect
  • PostgreSQL
  • Redshift
  • MySQL
  • Oracle
  • SQL Server 2012
  • SQL Server 2008
  • SAPHana
  • Apache Hive
  • DB2
  • SQLMX
  • Apache Derby
  • Spark SQL

If you use PostgreSQL JDBC driver to connect to Redshift database, the Auto detect option automatically detects the PostgreSQL database instead of Redshift. The behavior of the JDBC Snaps is optimized for the selected database.

Default Value: Auto detect
Example: Oracle

Test QueryString

Activates on selecting on selecting Auto detect for Database name.

Specify a custom query to validate the database connection.

  • The Test Query must be effective as this executes multiple times during the lifecycle of a connection. The efficiency of a Test Query directly affects the efficiency of the Pipeline execution. All databases do not support all test queries. Hence, use a query that supports your database.
  • Select 1 test query is supported only in H2, MySQL, PostgreSQL, and SQLite databases.

Default Value: N/A
Example: Select 1

Advanced properties*
Min pool size*Integer

Specify a minimum number of idle connections a pool will maintain at a time.

Default Value: 0
Example: 0

If the size is set to non-zero, JCC restart is needed when the database account expires.

Max pool size*IntegerSpecify a maximum number of idle connections a pool will maintain at a time.

Default Value: 15
Example: 10
Max idle time*IntegerSpecify the number of seconds a connection will exist in the pool before being destroyed.

Default Value: 60 
Example: 300
Checkout timeout*IntegerSpecify the number of milliseconds to wait for a connection to be available in the pool. A timeout of zero makes the Snap wait infinitely.  After a certain time, an exception is thrown and the Pipeline fails.

Default Value: 10000
Example:10000
Url propertiesUse this field set to define URL properties to use in the JDBC URL.

Url property nameString

Specify the name for the URL property.

Default Value: N/A
Example: maxAllowedPacket

Url property valueString

Specify a value for the property name.

Default Value: N/A
Example1000

Auto commitCheckbox

Select this checkbox to commit a batch immediately after the batch executes. So, only the current executing batch will be rolled back if the Snap fails.
If you deselect, then a transaction is started for the Snap run and committed upon run success. The transaction is rolled back if the Snap fails.

Default Value
: Selected

Fetch size*IntegerSpecify the number of records to retrieve from the DB at a time.

Default Value: 100
Example: 100
Batch size*

Integer

Specify the number of query statements to execute at a time. SELECT queries are not batched.

  • If the Batch Size is one, the query is executed as-is, that is the Snap skips the batch (non-batch execution).

  • If the Batch Size is greater than one, the Snap performs the regular batch execution.

Default Value50
Example10



Snap Pack History

 Click to view/expand
Release Snap Pack VersionDateType  Updates
4.27main12833 Stable
4.26 main11181 StableUpgraded with the latest SnapLogic Platform release.
4.25 Patch425patches11008 Latest
  • Fixed an issue with Generic JDBC - Select Snap where if there are URL properties in the account, the unPooledConnection does not use the properties when creating a connection. This causes the auto-detect functionality to use the wrong database name.
  • Fixed an issue with MySQL and MariaDB in Generic JDBC - Update Snap when a table is incorrectly reported as not being found.
4.25main9554
 
StableUpgraded with the latest SnapLogic Platform release.
4.24 Patch4.24patches8903 Latest

Fixes the Pipeline execution failure issue when using the JDBC Snaps with a Microsoft Access account by setting the correct quotation handler for the configured account.

4.24main8556
Stable

Enhances the Generic JDBC - Select Snap to return only the fields (provided in the Output Fields) in the output schema (second output view), through a new check box Fetch Output Fields In Schema. If the Output Fields property is empty all the columns are visible.

4.23 Patch423patches8027 Latest

Fixes the multiple connection issue in the JDBC Snap Pack that occurs when the Auto Detect field is enabled for each execution of the Snap by storing a copy of the database name.

4.23 Patch

423patches7800 Latest

Fixes an issue with JDBC account through a Test Query option that establishes a database connection upon using Auto detect option for the Database name.

4.23main7430
 
Stable
  • Fixes an issue with the JDBC account that displays a connection is closed error when connecting with the SQL server.

  • Fixes an issue with the JDBC Snaps that fail while displaying the javax.management.MalformedObjectNameException: Invalid character '=' in value part of property error repeatedly when there is “=“ or ”:” in the JDBC URL connection.

4.22 Patch 422patches7246 Latest

Fixes the file descriptor error in the Snap Pack by removing logging exception which was causing log file spam.

4.22 Patch422patches6772 Latest

Fixes the issue with Auto detect in Generic JDBC - Execute Snap by implementing the JDBC Auto detect feature to use the correct database name.

4.22main6403
 
StableUpgraded with the latest SnapLogic Platform release.
4.21 Patch421patches6272 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 Patch421patches6144 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 PatchMULTIPLE8841 Latest

Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.

4.21snapsmrc542

 

StableUpgraded with the latest SnapLogic Platform release.
4.20 Patchjdbc8783 Latest

Fixes the Generic JDBC Execute Snap that adds the value of the previous column's field to a NULL field when SELECT queries having duplicate column names are run on the PostgreSQL database.

4.20snapsmrc535
 
StableUpgraded with the latest SnapLogic Platform release.
4.19 Patch db/jdbc8405 Latest

Fixes an issue with the Generic JDBC - 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.19snaprsmrc528
 
StableUpgraded with the latest SnapLogic Platform release.
4.18snapsmrc523
 
Stable

Added support for JDBC account Active Directory authentication for SQL server for driver JAR version mssql-jdbc-6.2.2-jre8.jar.

4.17ALL7402
 
Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17snapsmrc515
 
Latest
  • Fixes an issue with the Generic JDBC 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 PatchMULTIPLE7123 Latest

Added two new properties, Number of retries and Retry interval, to Execute, Insert, Select, and Update Snaps that enables you to handle retry attempts during a connection failure.

4.16snapsmrc508
 
StableUpgraded with the latest SnapLogic Platform release.
4.15snapsmrc500
 
StableUpgraded with the latest SnapLogic Platform release.
4.14snapsmrc490
 
StableUpgraded with the latest SnapLogic Platform release.
4.13 Patchjdbc5231 Latest

Added binding information for DB2 database connection on the Generic JDBC Snap Pack to ensure that pipelines correctly validate and execute.   

4.13 Patchjdbc5229 Latest

Added test connection query for SQLMX database in the JDBC Accounts to check if the database connection is valid.

4.13

snapsmrc486

 
StableUpgraded with the latest SnapLogic Platform release.
4.12 PatchMULTIPLE4744 Latest

Added support to execute multiple queries in a single batch for Snowflake, this patch affects Generic JDBC Execute. 

4.12

snapsmrc480

 
StableUpgraded with the latest SnapLogic Platform release.
4.11snapsmrc465
 
StableUpgraded with the latest SnapLogic Platform release.
4.10

snapsmrc414

 
Stable

Adds 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 Patchjdbc3242 Latest

Addresses an issue in JDBC Execute Snap with functions not working (fixes by executing commit() at the end of the processing query).

4.9.0 Patchjdbc3205 Latest

Fixes auto-commit issue for PostgreSQL SELECT query.

4.9.0 Patch jdbc3133 Latest

Fixed error handling of the limit clause by adding Apache Derby support.

4.9.0 Patchjdbc3069 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.9snapsmrc405
 
StableUpgraded with the latest SnapLogic Platform release.
4.8.0 Patchjdbc2801 Latest

Addressed an issue with Generic JDBC - Execute Snap holding the resultset in memory, exhausting memory and causing a core dump.

4.8.0 Patchjdbc2753 Latest

Potential fix for JDBC deadlock issue.

4.8

snapsmrc398

 
Stable
  • Updated the default value for the property Min pool size to 0. 

  • Info tab added to accounts.

  • Database accounts now invalidate connection pools if account properties are modified and login attempts fail.
4.7 Patchjdbc2195 Latest

Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.

4.7

snapsmrc382

 
StableUpgraded with the latest SnapLogic Platform release.
4.6snapsmrc362
 
Stable
  • Enhanced Generic JDBC Execute Snap to fully support SQL statements with/without expressions & SQL bind variables.

  • Resolved an issue in Generic JDBC Insert Snap that caused unexpectedly failures on Snowflake and connecting to DB2.

  • Resolved an issue in Generic JDBC Select Snap that caused errors with Teradata database instance.

  • Resolved an issue in Generic JDBC Select Snap with Snowflake account that caused an error when auto-commit was not selected.

  • Resolved an issue in Generic JDBC Select Snap with Snowflake account that caused an error when a merge statement was used in the Snap.

Known Issue:

  • JDBC Insert: "The Maximum Possible Row Length in the Table is too Large" error message: You will see this message if trying to insert data into Teradata that is larger than Teradata can handle (rows are limited to approximately 64,000 bytes). Workaround: Use smaller default column size, e.g., 32000 bytes.

4.5.1

snapsmrc344

 
Stable

Resolved an issue with JDBC Select failing with a syntax error when special characters were used.

4.5

snapsmrc344

 Stable
  • Verified Generic JDBC Snaps connections to Hive. See JDBC Account for configuration information. SELECT and INSERT are supported. SnapLogic does not support UPDATE, DELETE, or MERGE due to limitations in the drivers. 

  • Resolved an issue in Generic JDBC Insert Snap that occurred when inserting records in batches. 

  • Resolved an issue in Generic JDBC Insert Snap that occurred because of an SQL execution (internal) error.

  • Resolved an issue in Generic JDBC Select Snap that occurred because of an SQL query execution. 

4.4.1N/A Stable
  • Added expression support to the Where clause property for Select Snaps.

  • Resolved an issue with the JDBC Select Snap failing with Teradata because of a Limit Offset.

  • Resolved an issue with JDBC Execute failing to execute a create or replace table statement with Snowflake.

  • Resolved issues with JDBC Insert Snap:

    • Failing to create a table when Create table if not present is selected.

    • An exception occurred when attempting to insert record containing date columns into Teradata.

4.4N/A StableUpgraded with the latest SnapLogic Platform release.
4.3.2N/A Stable

Resolved an issue with Generic JDBC Update updating null into database when an invalid string value is provided as input for time datatype.

4.3.1N/AN/AStable
  • New! Generic JDBC SELECT Snap

  • New! Generic JDBC UPDATE Snap

  • Feature: JDBC Snaps - add a new property 'Database name' to JDBC Account

  • Defect: JDBC Execute Snap fails in preview for Oracle timestamp data type

  • Defect: JDBC Insert to Snowflake throws an error

  • Defect: Generic JDBC Execute with JDBC4OLAP drivers to connect to Essbase resulted in com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Unable to parse content type: null

4.2.2N/AN/AStable
  • Ignore empty result added to Execute Snap. The option will not write any document to the output view for select statements producing no results.

  • Addressed an issue with idle timeouts.

  • Resolved an issue in JDBC Execute throwing an exception, unable to get driver.

4.2.1N/AN/AStable
  • Resolved Generic JDBC Execute not working with value substitution.

  • Resolved JDBC Execute unable to read CLOB columns via jTDS/JDBC.

See Also