Configuring the components - 7.1
- Talend Big Data
- Talend Big Data Platform
- Talend Data Fabric
- Talend Data Integration
- Talend Data Management Platform
- Talend Data Services Platform
- Talend ESB
- Talend MDM Platform
- Talend Open Studio for Big Data
- Talend Open Studio for Data Integration
- Talend Open Studio for ESB
- Talend Open Studio for MDM
- Talend Real-Time Big Data Platform
- Talend Studio
- Data Governance > Third-party systems > Database components > Oracle components
- Data Quality and Preparation > Third-party systems > Database components > Oracle components
- Design and Development > Third-party systems > Database components > Oracle components
Double-click the tOracleInput to open its
Basic settings view.
Define the Oracle connection details. It is recommended to store the
database connection details in the Metadata
folder of the Repository tree view in order
to retrieve them easily at any time in any Job.
Define the schema, if it is not stored in the Repository. In this example, the schema contains four
columns as follows: ID_Contract,
ID_Client, Contract_type and
Define the tFileOutputDelimited component
parameters, including output File Name,
Row separator and Fields delimiter.
Double-click on the tOracleBulkExec to
define the database populating properties.
In the Property Type list, select
Repository if you stored the database
connection details under the Metadata node
of the Repository or select Built-in to define them manually. In this
scenario, use the Built-in mode.
Set the connection parameters in the following fields: Host, Port,
Database, Schema, Username, and
Fill in the name of the Table to be
populated and the Action on data to be
carried out. In this use case, select insert.
In the Schema list, select Built-in, and click the [...] button next to the Edit
schema field to define the structure of the data to be passed
to the next component.
Click the Advanced settings view to
configure the advanced settings of the component.
Select the Use an existing control file
check box if you want to use a control file (.ctl) storing the status of the
physical structure of the database. Or, fill in the following fields
manually: Record format, Specify .ctl file's INTO TABLE clause manually,
Field terminated by, Use field enclosure, Use
schema's Date Pattern to load Date field, Specify field condition, Preserve blanks, Trailing null
columns, Load options,
NLS Language and Set Parameter NLS_TERRITORY according to your
In the Encoding list, select the
encoding, or enter the encoding between double quotes if it does not exist
in the list.
In the Output list, select to console to output the standard output of the
database in the console.