tOracleOutputBulkExec – Docs for ESB 5.x

Component family

Databases/Oracle

Function

Executes the Insert action on the data provided.

Purpose

As a dedicated component, it allows gains in performance during
Insert operations to an Oracle 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.

Connection type

Drop-down list of available drivers:

Oracle OCI: Select this connection
type to use Oracle Call Interface with a set of C-language software
APIs that provide an interface to the Oracle database.

Oracle Service Name: Select this
connection type to use the TNS alias that you give when you connect
to the remote database.

Oracle SID: Select this connection
type to uniquely identify a particular database on a system.

Oracle Custom: Select this
connection type to access a clustered database.

DB Version

Select the Oracle version in use

Host

Database server IP address.

Currently, only localhost,
127.0.0.1 or the exact IP
address of the local machine is allowed for proper functioning. In
other words, the database server must be installed on the same
machine where the Studio is installed or where the Job using
tOracleOutputBulkExec is
deployed.

Port

Listening port number of DB server.

Database

Name of the database

Schema

Name of the 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 and that the table must exist for the insert
operation to succeed.

Action on table

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

None: No operations 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 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.

Truncate table: The table content
is deleted. You do not have the possibility to rollback the
operation.

File Name

Name of the file to be generated and loaded.

Create directory if not exists

This check box is selected by default. It creates a directory to
hold the output table if required.

Append

Select this check box to add the new rows at the end of the
file.

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.

Truncate: Remove all entries from
table.

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.

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

Built-In: You create and store the schema 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. You can reuse it in various projects and Job designs. Related
topic: see Talend Studio User Guide.

When the schema to be reused has default values that are integers or functions, ensure that
these default values are not enclosed within quotation marks. If they are, you must remove
the quotation marks manually.

For more details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema.

Field separator

Character, string or regular expression to separate fields.

Advanced settings

Advanced separator (for number)

Select this check box to change data separators for
numbers:

Thousands separator: define
separators you want to use for thousands.

Decimal separator: define
separators you want to use for decimals.

Use existing control file

Select this check box and browse to the .ctl control file you want
to use.

Field separator

Character, string or regular expression to separate fields.

Row separator

String (ex: ”
“on Unix) to separate rows.

Specify .ctl file’s INTO TABLE clause manually

Select this check box to enter manually the INTO TABLE clause of
the control file directly into the code.

Use schema’s Date Pattern to load Date field

Select this check box to use the date model indicated in the
schema for dates.

Specify field condition

Select this check box to define a condition for loading data.

Preserve blanks

Select this check box to preserve blank spaces.

Trailing null columns

Select this check box to load data with all empty columns.

Load options

Click + to add data loading
options:

Parameter: select a loading
parameter from the list.

Value: enter a value for the
parameter selected.

NLS Language

From the drop-down list, select the language for your data if the
data is not in Unicode.

Set Parameter NLS_TERRITORY

Select this check box to modify the conventions used for date and
time formats. The default value is that of the operating system.

Encoding

Select the encoding from the list or select Custom and define it manually. This field is
compulsory for DB data handling.

Oracle encoding type

Select the Oracle-specific encoding type for the data to be
processed. This encoding type allows tOracleOutputBulkExec to properly generate the
Sybase Bulk command.

Output

Select the type of output for the standard output of the Oracle
database:

to console,

to global variable.

Convert columns and table names to uppercase

Select this check box to put columns and table names in upper
case.

Bulk file parameters

Set the parameters Buffer Size
and StringBuilder Size for a
performance gain according to the memory size.

tStatCatcher Statistics

Select this check box to gather the job processing metadata at a
job level as well as at each 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.

Usage

This component is mainly used when no particular transformation is
required on the data to be loaded onto the database.

Limitation

The database server/client must be installed on the same machine
where the Studio is installed or where the Job using tOracleOutputBulkExec is deployed, so
that the component functions properly.