tOracleCDC Standard properties - 6.5

Change Data Capture

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
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 Real-Time Big Data Platform
task
Data Governance > Third-party systems > Database components > Change Data Capture
Data Quality and Preparation > Third-party systems > Database components > Change Data Capture
Design and Development > Third-party systems > Database components > Change Data Capture
EnrichPlatform
Talend Studio

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

The Standard tOracleCDC component belongs to the Databases family.

The component in this framework is available in all Talend subscription-based products.

Basic settings

Property of the CDC connection

Either Built-in or Repository.

 

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.

Use an existing connection

Select this check box and in the Component List click the relevant connection component to reuse the connection details you already defined.

Note: When a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to:
  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.

  2. In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels, see Talend Studio User Guide.

Connection Type

Select a connection type from the drop-down list:

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

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

  • 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.

DB Version

Select the version of the Oracle database being used.

Host

Specify the host name or IP address of the Oracle database.

This field appears only when Oracle SID or Oracle Service Name is selected from the Connection Type drop-down list.

Port

Specify the listening port number of the Oracle database.

This field appears only when Oracle SID or Oracle Service Name is selected from the Connection Type drop-down list.

Database

Specify the Oracle database name.

This field appears only when Oracle SID or Oracle Service Name is selected from the Connection Type drop-down list.

Local Service Name

Specify the local service name of the Oracle database.

This field appears only when Oracle OCI is selected from the Connection Type drop-down list.

URL

Specify the URL of the remote Oracle database.

This field appears only when Oracle CUSTOM is selected from the Connection Type drop-down list.

Oracle schema

Specify the name of the Oracle schema.

Username and Password

Specify the user authentication data of the Oracle database.

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.

Schema using CDC 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.

The schema is set by default according to the CDC mode being used.

 

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.

CDC mode

Select a CDC mode to be used:

  • Trigger: the CDC trigger mode.

  • Log: the CDC Redo/Archive log mode. This mode requires Oracle database Enterprise Editions and is available only when the DB Version is Oracle 11-6 or a previous version.

  • XStream: the CDC XStream mode. This mode is available only when the Connection Type is Oracle OCI and the DB Version is Oracle 12-7.

For more information about CDC modes, see Talend Studio User Guide.

Generate LCR type

Select a type for the LCR to be generated, either LCR Object or LCR XML Document.

This list appears only when the CDC mode is XStream.

Table using CDC

Specify the source table from which changes made to data are to be captured.

Set data table schema

Select this check box if you want to specify the schema of the CDC table.

This check box appears only when the CDC mode is Trigger or Log.

Subscriber

Specify the name of the application that will use the change table if you use the Trigger mode to capture changes done on data.

This field appears only when the CDC mode is Trigger.

Events to catch

Insert: Select this check box to catch the data inserted in the change table since the last extraction.

Update: Select this check box to catch the data updated in the change table since the last extraction.

Delete: Select this check box to catch the data deleted in the change table since the last extraction.

These check boxes appear only when the CDC mode is Trigger or Log.

Limit

Specify the maximum number of consumed rows a subscriber can recover from the change table, per execution.

This field appears only when the CDC mode is Trigger.

Outbound server name

Specify the XStream outbound server name.

This field appears only when the CDC mode is XStream.

Keep listening

Select this check box to keep monitoring the outbound server for data changes. The Job will not stop until you manually stop it when you need to.

This check box appears only when the CDC mode is XStream.

Advanced settings

Keep data in CDC Table

Select this check box to keep the changes made available to one or more target systems, even after they have been consulted.

This field appears only when the CDC mode is Trigger or Log.

Use cursor

Select this check box to specify the number of rows you want to work with at any given time. This option optimises performance.

This field appears only when the CDC mode is Trigger or Log.

Trim all the String/Char columns

Select this check box to delete any spaces found at the beginning or end of fields, in all of the columns containing character strings.

This field appears only when the CDC mode is Trigger or Log.

Trim column

Remove leading and trailing whitespace from defined columns.

Note:

Clear Trim all the String/Char columns to enable Trim columns in the table.

This table appears only when the CDC mode is Trigger or Log.

Acknowledge interval(seconds)

Specify the value for the OCI_ATTR_XSTREAM_ACK_INTERVAL attribute for the outbound server. The default value is 30 seconds.

For more infomrmation about this attribute, see http://docs.oracle.com/cd/E18283_01/server.112/e16545/xstrm_oci_intro.htm#CEGDICBB.

This field appears only when the CDC mode is XStream.

Idle timeout(seconds)

Specify the value for the OCI_ATTR_XSTREAM_IDLE_TIMEOUT attribute for the outbound server. The default value is 1 second.

For more information about this attribute, see http://docs.oracle.com/cd/E18283_01/server.112/e16545/xstrm_oci_intro.htm#CEGDICBB.

This field appears only when the CDC mode is XStream.

tStatCatcher Statistics

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

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:
  • Enter the number of parallel executions desired.

  • Press Ctrl + Space and select the appropriate context variable from the list. For further information, see Talend Studio User Guide.

Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob.

  • The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table.

  • When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob.

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 further information about variables, see Talend Studio User Guide.

Usage

Usage rule

This component is used as a start component. It requires an output component and row Main link.