This Snap has exactly one document input view.

Values to be updated in the target columns.

• Mapper
• Oracle - Execute

This Snap has at most one document output view.

Updated records.

• File Writer
• Mapper

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 - Update

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.

The values can be passed using the pipeline parameters but not the upstream parameter.

Default value: None

Example: SYS

Required. Specify the name of the table to execute the update operation on. This list is populated based on the tables associated with the selected schema.

The values can be passed using the pipeline parameters but not the upstream parameter.

Default value: None

Example: people

Required. Specify the SQL WHERE clause of the update statement. You can define specific values or columns to update (Set condition) in the upstream Snap, such as Mapper Snap, and then use the WHERE clause to apply these conditions on the columns sourced from the upstream Snap. For instance, here is a sample of an Update SQL query:

UPDATE table_name SET column1 = value1, column2 = value2, WHERE condition;

• If the Update Condition field is left blank, the condition is applied on all the records of the target table.
• Instead of building multiple Snaps with inter dependent DML queries, we recommend that you use the Oracle - Stored Procedure Snap. In a scenario where the downstream Snap depends on the data processed on an Upstream Database Bulk Load Snap, use the Script Snap to add delay for the data to be available.

In certain scenarios where you want to use specific data from the upstream Snaps, and do not want to change that data in the Update Snap, then you need to place the data in the original structure of the input document. Hence, we recommend that you use the format for Update condition and input data format as shown below:

{ "valueToUpdate" : "true", "original": { "col1" : "KEY" } }

Refer to the example to understand how the Update Condition works.

If Batch size in your account is greater than one, do not toggle on the expression button if a dynamic argument needs to be defined referencing several input documents.

Default value: None

Examples:

Without using expressions

• EmpId = 12
• email = '[email protected]'

Using expressions

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

Specifies 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.

This field does not support values from upstream Snaps when you enable the expression icon; it can accept values only from Pipeline parameters.

Default value: 0

Example: 3

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

This field does not support values from upstream Snaps when you enable the expression icon; it can accept values only from Pipeline parameters.

Default value: 1

Example: 10

Specify the name of the NLS parameter.

• This Snap supports the Enable, Disable, and Force commands in session parameters.
• This field supports only pipelines parameters, and not upstream values.

Default value: None

Example: NLS_TERRITORY

Specify the value for the NLS parameter. This field supports only pipelines parameters, and not upstream values.

Default value: None

Example: CZECH REPUBLIC

Snap execution

Default value: Execute only

Example: Validate & execute