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.

• JSON Generator
• JSON Formatter
• XML Formatter

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.

• Mapper
• Copy
• File Writer

Label

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: Oracle Execute

Example: Oracle Execute

Required. 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 = '[email protected]' 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 into " + $tablename + " (city, temp_lo, temp_hi, date) values ('" + $city + "','" + $temp_lo + "', '" + $temp_hi + "', '" + $date + "')"
• "select * from " + $tablename

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 be 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: Has no single quotes | To pass this value: Schaum Series | Use: 'Schaum Series'
• If String: Contains single quotes | To pass this value: O'Reilly's Publication | Use: 'O''Reilly''s Publication'

Default value: N/A

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

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

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: Deselected

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

Specify the maximum number of retry attempts the Snap must make in case of network failure.

When you set the Number of retries to more than 0, the Snap generates duplicate records when the connection is not established. To prevent duplicate records, we recommend that you follow one of the following:

• Set the Number of retries to 0 (default value) to prevent duplicate records from being passed downstream while executing a pipeline.
• Use a Primary key to prevent records from being inserted into the database.
• Use an Upsert instead of an Insert statement.

Default value: 0

Example: 3

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

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

Default value: Execute only

Example: Validate & execute