tOracleTableList Standard properties


Data Quality and Preparation > Third-party systems > Database components > Oracle components
Design and Development > Third-party systems > Database components > Oracle components
Data Governance > Third-party systems > Database components > Oracle components
Talend Studio

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

The Standard tOracleTableList component belongs to the Databases family.

Basic settings

Component list

Select the tOracleConnection component in the list if more than one connection is planned for the current Job.

Where clause for table name selection

Enter the WHERE clause that will be used to identify the tables to iterate on.

Advanced settings

tStatCatcher Statistics

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

Global Variables

Global Variables

CURRENT_TABLE: the name of the table currently iterated upon. This is a Flow variable and it returns a string.

NB_TABLE: the number of tables iterated upon so far. This is a Flow 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 further information about variables, see Talend Studio User Guide.


Usage rule

This component is to be used along with other Oracle components, especially with tOracleConnection.

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 .

Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide.