Skip to main content Skip to complementary content

tOracleOutputBulk Standard properties

These properties are used to configure tOracleOutputBulk running in the Standard Job framework.

The Standard tOracleOutputBulk component belongs to the Databases family.

The component in this framework is available in all Talend products.

Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see DB Generic components.

Basic settings

Database

Select the desired database type from the list and click Apply.

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.

File Name

Name of the file to be generated.

Information noteWarning:

This file is generated on the local machine or a shared folder on the LAN.

Append

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

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.

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

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

    If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

 

Built-In: You create and store the schema locally for this component only.

 

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

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 information, see Retrieving table schemas.

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.

Field separator

Character, string or regular expression to separate fields.

Row separator

String (ex: "\n"on Unix) to separate rows.

Encoding

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

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.

Global Variables

Global Variables 

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

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 more information about variables, see Using contexts and variables.

Usage

Usage rule

This component is to be used along with tOracleBulkExec component. Used together they offer gains in performance while feeding a Oracle database.

Component family

Databases/Oracle

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!