Oracle Connector

This node creates a connection to an Oracle server via an Oracle JDBC driver. Due to license restrictions the Oracle JDBC driver is not part of the KNIME Analytics Platform and needs to be downloaded and registered separately. For more details on where to download and how to register the Oracle driver see the database documentation.
You need to provide the server's hostname (or IP address), the port, and a database name. Login credentials can either be provided directly in the configuration or via credential variables.

This node uses the selected driver's JDBC URL template to create the concrete database URL. Field validation in the dialog depends on whether the (included) tokens referencing them are mandatory or optional in the template.

Options

Connection settings

Database Dialect: Choose the registered database dialect here.
Driver Name: Choose the registered database driver here. Additional drivers can be registered via KNIME's preference page "KNIME -> Databases". For more details on how to register the Oracle driver see the database documentation.
Hostname: The hostname (or IP address) of a Oracle server. The corresponding driver URL template variable is host.
Port: The port on which the Oracle server is listening. The default port is 1,521. The corresponding driver URL template variable is port.
Database name: The name of the database you want to connect to. The corresponding driver URL template variable is database.
None: Sending no credentials is required for some Oracle specific logins such as Oracle Wallet. Please refer to the Oracle documentation for any further setup steps that might be required.
Credentials: If checked, the credentials (user and password) are used as defined on the workflow. The credential name links to the specified user and password.
Username & password: Your log-in user name and password for the database. Note that the password is encrypted before storage and decrypted afterwards for being used internally.
Kerberos: Uses an existing Kerberos ticket for authentication.
For more details on how to configure and use Kerberos in KNIME Analytics Platform see the Kerberos User Guide.

JDBC Parameters

This tab allows you to define JDBC driver connection parameter. The value of a parameter can be a constant, variable, credential user, credential password or KNIME URL. For more information about the supported driver properties see the Oracle documentation.

Advanced

This tab allows you to define KNIME framework properties such as connection handling, advanced SQL dialect settings or logging options.

Input Type Mapping

This tab allows you to define rules to map from database types to KNIME types.

Mapping by Name: Columns that match the given name (or regular expression) and database type will be mapped to the specified KNIME type.
Mapping by Type: Columns that match the given database type will be mapped to the specified KNIME type.

Output Type Mapping

This tab allows you to define rules to map from KNIME types to database types.

Mapping by Name: Columns that match the given name (or regular expression) and KNIME type will be mapped to the specified database type.
Mapping by Type: Columns that match the given KNIME type will be mapped to the specified database type.

Input Ports

This node has no input ports

Output Ports

: Oracle DB Connection.

Popular Predecessors

Popular Successors

Views

This node has no views

Workflows

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME Database from the below update site following our NodePit Product and Node Installation Guide:

v5.3

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland

Plugin version: 5.3.0.v202406061602

On NodePit since: 2024-07-09

Last update: 2024-11-15

KNIME versions: Since v3.7

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!