Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Selecting a schema, filters the Table name list to show only those tables within the selected schema. 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

.

SOAP Execute

Field Name

Field Type

Description

Label*

Default valueOracle - Insert
Example:Insert Emp data

String

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
ExampleSYS

String/Expression/Suggestion

The Specify the database schema name. In case it is not defined, then the suggestion for the Table Name will retrieve all tables names of all schemas. The property is suggestible and will retrieve available database schemas during suggest values.

Note

Table name


Default value:  N/A
Examplepeople

String/Expression/Suggestion

Specify the table that the rows will be inserted into.

Note

Create table if not present

Default stateDeselected

Checkbox

Multiexcerpt include macro
nameME_Create_Table_Automatically_2_Inputs
pageRedshift - Bulk Load

Learn more about table creation.

Preserve case sensitivity

Checkbox

Select this checkbox to preserve the case sensitivity of the column names while performing the insert operation.

  • If you deselect the Preserve case sensitivity checkbox, the input documents are loaded to the target table if the key names in the input documents match the target table column names ignoring the case.

  • If you include a second input view, selecting this checkbox has no impact on the column names of the target table, because the Snap uses the metadata from the second input view.

Number of retries

Default value: 0
Example3

Integer/Expression

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.

Retry interval (seconds)

Default value: 1
Example: 10

Integer/Expression

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

Session parameters

Use this field set to define the session parameters. This property lets you use the National Language Support (NLS) parameters. See the Oracle doc for detailed information about Setting NLS Parameters.

The NLS parameters enable overriding the default value (e.g., a comma) that is set for the session in the initialization parameter file or set by the client with environment variables (e.g., a decimal point).

You can add multiple parameters by using the plus (+) sign next to Session parameters.

Session parameter name

Default value: N/A
Example: NLS_TERRITORY

String/Expression

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.

Session parameter value

Default value: N/A
Example: "CZECH REPUBLIC"

String/Expression

Value of the NLS parameter. This field supports only pipelines parameters, and not upstream values.

Multiexcerpt include macro
nameSnap Execution
pageSOAP Execute

Dropdown list

Multiexcerpt include macro
nameExecution_Detail_Write
page

Specify the database schema name. Selecting a schema, filters the Table name list to show only those tables within the selected schema. 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.

Auto commit

In a scenario where the Auto commit on the account is set to true, and the downstream Snap does 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.

For example, when performing a create, insert and a delete function sequentially on a pipeline, using a Script Snap helps in creating a delay between the insert and delete function or otherwise it may turn out that the delete function is triggered even before inserting the records on the table.

...