tOracleSCD Standard properties

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 where properties are stored. The following fields are pre-filled in using fetched data.

Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

Note that connections that are of WALLET type are for the tCreateTable component, the tOracleInput component, and the tOracleOutput component only. Make sure that the connection selected is not of the WALLET type to prevent possible errors.

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 you are using.

Host

Database server IP address.

Port

Listening port number of DB server.

Database

Name of the database.

Schema

Name of the DB schema.

Username and Password

DB user authentication data.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, 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.

Action on table

Select to perform one of the following operations on the table defined:

- None: No action is carried out on the table.

- Create table: A new table is created.

- Create table if not exists: A table is created if it does not exist.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

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: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab.

SCD Editor

The SCD editor helps to build and configure the data flow for slowly changing dimension outputs.

For more information, see SCD management methodology.

Use memory saving Mode

Select this check box to maximize system performance.

Source keys include Null

Select this check box to allow the source key columns to have Null values.

Die on error

This check box is cleared by default, meaning to skip the row on error and to complete the process for error-free rows.

Additional JDBC parameters

Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

End date time details

Specify the time value of the SCD end date time setting in the format of HH:mm:ss. The default value for this field is 12:00:00.

This field appears only when SCD Type 2 is used and Fixed year value is selected for creating the SCD end date.

tStatCatcher Statistics

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

Debug mode

Select this check box to display each step during processing entries in a database.

Select this option to enable globalization support. See Overview of Globalization Support for related information.

This option is available when the Use an existing connection option is cleared and Oracle 18 and above is selected from the DB Version drop-down list in the Basic settings view.

Global Variables

NB_LINE_UPDATED: the number of rows updated. This is an After variable and it returns an integer.

NB_LINE_INSERTED: the number of rows inserted. This is an After variable and it returns an integer.

NB_LINE_REJECTED: the number of rows rejected. 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 rule

This component is used as Output component. It requires an Input component and Row main link as input.

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 examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.

Limitation

This component does not support using SCD type 0 together with other SCD types.