Property type

Either Built-in
or Repository.

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.

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 Custom: Select this
connection type to access a clustered database.

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

WALLET: Select this connection
type to store credentials in an Oracle wallet.

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

DB Version

Select the Oracle version in use.

Use tns file

Select this check box to use the metadata of a context
included in a tns file.

TNS File: Enter the path to the
tns file manually or browse to the file by clicking the three-dot button
next to the filed.

Select a DB Connection in Tns
File: Click the three-dot button to display all the
contexts held in the tns file and select the desired one.

Host

Database server IP address.

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.

Additional JDBC parameters

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

Use or register a shared DB Connection

Select this check box to share your
database connection or fetch a database connection shared by a parent or child Job,
and in the Shared DB Connection Name field displayed, enter the
name for the shared database connection. This allows you to share one single database
connection (except the database schema setting) among several database connection
components from different Job levels that can be either parent or child.

This option is
incompatible with the Use dynamic job and Use an
independent process to run subjob options of the
tRunJob component. Using a shared connection together with a
tRunJob component with either of these two options enabled
will cause your Job to fail.

This check box is not available when the Specify a data source
alias check box is selected.

Select this check box and specify the alias of a data source created on the
Talend Runtime
side to use the shared connection pool defined in the
data source configuration. This option works only when you deploy and run your Job in

Talend Runtime
. For a related use case, see Scenario: Deploying your Job on Talend Runtime to retrieve data from a MySQL database.

Auto Commit

Select this check box to commit any changes to the database automatically upon
the transaction.

With this check box selected, you cannot use the corresponding commit component
to commit changes to the database; likewise, when using the corresponding commit
component, this check box has to be cleared. By default, the auto commit function is
disabled and changes must be committed explicitly using the corresponding commit
component.

Note that the auto commit function commits each SQL statement as a single
transaction immediately after the statement is executed while the commit component does
not commit only until all of the statements are executed. For this reason, if you need
more room to manage your transactions in a Job, it is recommended to use the commit
component.

tStatCatcher Statistics

Select this check box to gather the job processing metadata at a
Job level as well as at each component level.

Usage rule

This component is more commonly used with other tOracle*
components, especially with the tOracleCommit and tOracleRollback components.