# tOracleInput MapReduce properties (deprecated)

Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated)

This content is deprecated.

These properties are used to configure tOracleInput running in the MapReduce Job framework.

The MapReduce tOracleInput component belongs to the Databases family.

The component in this framework is available in all Talend products with Big Data and Talend Data Fabric.

Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated)

This content is deprecated.

The MapReduce framework is deprecated from Talend 7.3 onwards. Use Talend Jobs for Apache Spark to accomplish your integration tasks.

## Basic settings

| Property type | Either Built-In or Repository.<br><br><br>Built-In: No property data stored centrally.<br><br><br>Repository: Select the repository file where the<br>properties are stored. |
| --- | --- |
| ![](https://help.qlik.com/talend/en-US/components/7.3/Resources/images/Save_Icon.png) | Click this icon to open a database connection wizard and store the<br>database connection parameters you set in the component Basic settings view.<br><br>For more information about setting up and storing database<br>connection parameters, see *Talend Studio User Guide*. |
| Connection type | Drop-down list of available drivers:<br><br><br>Oracle OCI: Select this connection<br>type to use Oracle Call Interface with a set of C-language software<br>APIs that provide an interface to the Oracle database.<br><br><br>Oracle Custom: Select this<br>connection type to access a clustered database.<br><br><br>Oracle Service Name: Select this<br>connection type to use the TNS alias that you give when you connect<br>to the remote database.<br><br><br>WALLET: Select this connection type<br>to store credentials in an Oracle wallet.<br><br><br>Oracle SID: Select this connection<br>type to uniquely identify a particular database on a system. |
| DB Version | Select the Oracle version in use. |
| Host | Database server IP address. |
| Port | Listening port number of DB server. |
| Database | Name of the database. |
| Oracle schema | Oracle schema name. |
| Username and<br>Password | DB user authentication data.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Schema and Edit<br>Schema | A schema is a row description, it defines the number of fields to<br>be processed and passed on to the next component. The schema is<br>either Built-in or stored remotely<br>in the Repository.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                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 <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
|  | Built-In: You create and store the schema locally for this component<br>only. |
|  | Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs. |
| Table name | Database table name. |
| Query type and<br>Query | Enter your DB query paying particularly attention to properly<br>sequence the fields in order to match the schema definition. |
| Die on error | Select the check box to stop the execution of the Job when an error<br>occurs.<br><br>Clear the check box to skip any rows on error and complete the process for<br>error-free rows. When errors are skipped, you can collect the rows on error using a Row &gt; Reject link. |

## Usage

| **Usage rule** | In a<br>Talend<br>Map/Reduce Job, it is used as a start component and requires<br>a transformation component as output link. The other components used along with it must be<br>Map/Reduce components, too. They generate native Map/Reduce code that can be executed<br>directly in Hadoop.<br><br>You need to use the Hadoop Configuration tab in the<br>Run view to define the connection to a given Hadoop<br>distribution for the whole Job.<br><br>Note that in this documentation, unless otherwise<br>explicitly stated, a scenario presents only Standard Jobs,<br>that is to say traditional<br>Talend<br>data integration Jobs, and non Map/Reduce Jobs. |
| --- | --- |
| Hadoop Connection | You need to use the Hadoop Configuration tab in the<br>Run view to define the connection to a given Hadoop<br>distribution for the whole Job.<br><br>This connection is effective on a per-Job basis. |