tOracleInvalidRows
Checks Oracle database rows against specific Data Quality patterns (regular
expression) or Data Quality rules (business rule).
tOracleInvalidRows extracts database rows that do not match
a given data quality pattern or rule. You can then implement any required correction.
tOracleInvalidRows Standard properties
These properties are used to configure tOracleInvalidRows running in the Standard Job framework.
The Standard
tOracleInvalidRows component belongs to the Data Quality and the Databases families.
This component is available in Talend Data Management Platform, Talend Big Data Platform, Talend Real Time Big Data Platform, Talend Data Services Platform, Talend MDM Platform and Talend Data Fabric.
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.
Basic settings
| Database |
Select a type of database from the list and click |
|
Validation type |
Either Regex pattern validation |
| Â |
Regex pattern validation: |
| Â |
DQ rule validation: Validate data |
|
Property type |
Either Built-in or Repository. |
|
 |
Built-in: No property data stored |
|
 |
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component List click the relevant connection component to 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:
For an example about how to share a database connection |
|
Connection Type |
Drop-down list of available drivers. |
|
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. |
|
Oracle schema |
Name of the Oracle schema. |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
Schema and Edit |
A schema is a row description, it defines the number of fields to |
|
 |
Built-in: You create and store |
|
 |
Repository: You have already |
|
Table Name |
Enter the name of the table to be read. |
|
Where clause |
Enter a WHERE clause to define a row filter on the table. You can use the WHERE clause to filter the rows you want to |
Advanced settings
|
Additional JDBC Parameters |
Specify additional connection properties for the DB connection you Note:
You can press Ctrl+Space to |
|
Covert XML type to Java Type |
Select this check box and then use the table to convert the types of the defined columns to Java types. |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
|
Use cursor |
Select this check box to specify the number of rows you want to |
|
Trim all the String/Char columns |
Select this check box to remove leading and trailing whitespace from all the String/Char columns. |
|
Trim column |
Remove leading and trailing whitespace from the defined This check box is not visible if Trim all |
|
No null values |
Select this check box to improve the performance if there are no |
Global Variables
|
Global Variables |
NB_LINE: the number of rows read by an input component or
QUERY: the query statement being processed. This is a Flow
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
|
Usage rule |
This component can be used as a start or intermediary step. It |
|
Note:
Available only for Regex pattern |
Analyzed column |
|
Note:
Available only for Regex pattern |
Custom pattern |
|
Note:
Available only for Regex pattern |
Patterns list |
|
Note:
Available only for DQ rule |
DQ rule list |
|
Note:
Available only for DQ rule |
Query type |
| Â | Â |
| Â | Â |
|
Note:
Available only for DQ rule |
Guess Query |
|
Note:
Available only for DQ rule |
Guess schema |
|
Note:
Available only for DQ rule |
Query |
Related scenarios
For a related scenario, see Reading email addresses from a DB table and retrieving specific data.