tDB2BulkExec – Docs for ESB 5.x

Component family

Databases/DB2

Function

tDB2BulkExec executes the Insert
action on the data provided.

Purpose

As a dedicated component, tDB2BulkExec allows gains in performance during
Insert operations to a DB2 database.

Basic settings

Property type

Either Built-in or
Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Built-in: No property data stored
centrally.

Repository: Select the repository
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.

Use an existing connection

Select this check box and in the Component List click the
relevant connection component to reuse the connection details you already defined.

Host

Database server IP address

Port

Listening port number of DB server.

Database

Name of the database

Table Schema

Name of the DB schema.

Username and
Password

DB user authentication data.

To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.

Table

Name of the table to be written. Note that only one table can be
written at a time

Action on table

On the table defined, you can perform one of the following
operations:

None: No operation is carried
out.

Drop and create table: The table is
removed and created again.

Create table: The table does not
exist and gets created.

Create table if not exists: The
table is created if it does not exist.

Drop table if exists and create:
The table is removed if it already exists and created again.

Clear table: The table content is
deleted.

Schema and Edit
Schema

A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Built-in: You create the schema
and store it locally for this component only. Related topic: see
Talend Studio User
Guide.

Repository: You have already
created the schema and stored it in the Repository, hence can reuse
it. Related topic: see Talend Studio User Guide.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:

Data file

Name of the file to be loaded.

Action on data

On the data of the table defined, you can perform:

Insert: Add new entries to the
table. If duplicates are found, Job stops.

Update: Make changes to existing
entries

Insert or update: Insert a new record. If the record with
the given reference already exists, an update would be made.

Update or insert: Update the record with the given
reference. If the record does not exist, a new record would be inserted.

Delete: Remove entries
corresponding to the input flow.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the DB connection you
are creating.

Field terminated by

Character, string or regular expression to separate fields.

Date Format

Use this field to define the way months and days are
ordered.

Time Format

Use this field to define the way hours, minutes and seconds are
ordered.

Timestamp Format

Use this field to define the way date and time are ordered.

Remove load pending

When the box is ticked, tables blocked in “pending” status
following a bulk load are de-blocked.

Load options

Click + to add data loading
options:

Parameter: select a loading
parameter from the list.

Value: enter a value for the
parameter selected.

tStat
Catcher Statistics

Select this check box to collect log data at the component
level.

Dynamic settings

Click the [+] button to add a row in the table and fill
the Code field with a context variable to choose your
database connection dynamically from multiple connections planned in your Job. This feature
is useful when you need to access database tables having the same data structure but in
different databases, especially when you are working in an environment where you cannot
change your Job settings, for example, when your Job has to be deployed and executed
independent of Talend Studio.

The Dynamic settings table is available only when the
Use an existing connection check box is selected in the
Basic settings view. Once a dynamic parameter is
defined, the Component List box in the Basic settings view becomes unusable.

For more information on Dynamic settings and context
variables, see Talend Studio User Guide.

Global Variables 

NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.

NB_LINE_UPDATED: the number of rows updated. This is an
After variable and it returns an integer.

NB_LINE_INSERTED: the number of rows inserted. This is an
After variable and it returns an integer.

NB_LINE_DELETED: the number of rows deleted. This is an
After variable and it returns an integer.

QUERY: the SQL query statement processed. This is an After
variable and it returns a string.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.

Usage

This dedicated component offers performance and flexibility of DB2
query handling.

Log4j

The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User
Guide.

For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.

This component requires installation of its related jar files. For more information about the
installation of these missing jar files, see the section describing how to configure the
Studio of the Talend Installation and Upgrade Guide.