Set up a connection to Oracle DB (SQL)

Tom Santiago

Updated October 02, 2024 17:43

Important

This connector requires an on-premise agent and is only for SQL (not SODA).

You must create your connection using Oracle’s Easy Connect naming method, as we do not support TNS names or configuration files.

Oracle DB (SQL) links: API guide , Authentication

A. Set up an Oracle DB (SQL) connection

Start establishing a connection to Oracle DB (SQL) in either of the following ways:

From the Resources menu, select Connections. Then, click + Create connection at the top right.

– or –
While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination/lookup.

In the resulting Application list, select Oracle DB (SQL).

The Create connection pane opens with required and advanced settings.

B. Describe the Oracle DB connection

At this point, you’re presented with general settings about the Oracle DB connection:

Name (required): Provide a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.

Application (required, not-editable): A reminder of the app you’re editing.

Agent (required): To connect to an on-premise application integrator.io requires that an agent be installed on a computer that has network access to the on-premise application. Once the agent has been installed you can reference the agent with the drop-down menu here. A single agent can be used by multiple different connections.

C. Edit required Oracle DB (SQL) settings

At this point, you’re presented with a series of options for establishing Oracle DB (SQL) authentication.

Host (required): Enter the hostname or IP address of the server you are connecting to.

Username (required): Enter the username to authenticate with the server.

Password (required): Enter the password to authenticate with the server.

Instance name (optional): This field specifies the instance name to connect to. The SQL Server Browser service must be running on the database server, and UDP port 1521 or 1434 on the database server must be reachable. If you set this field you cannot also set the port field because "instanceName" and "port" are mutually exclusive connection options.

Port (optional): The server port to connect to. The default port is 1521.

D. Edit advanced Oracle DB settings

Before continuing, you have the opportunity to provide additional configuration information, if needed, for the Oracle DB connection.

Service Name: This field specifies the name or alias of a database service that integrator.io should connect to. Not every Oracle installation will use this feature. In this case, "ORCL" is the service name used by the external database.

Server Type: Choose one of the following server types from the drop-down menu:

sidebar. Optional concurrency and rate limit settings

Borrow concurrency from (optional): Select another connection from the list. By default, all data flowing through a connection record is submitted to the respective endpoint application at the concurrency level configured for that connection record. There are cases, however, where multiple integrator.io connections need to share the same concurrency level, and this field allows you to specify which connection you would like to borrow from. With borrowed concurrency, the data flowing through both connections will be submitted to the endpoint application together, via a shared concurrency model.
Auto-recover rate limit errors: This setting is enabled by default with a predefined value for Target concurrency level. You can disable the setting if required. To set or make changes in any of these settings, you must have admin or manage permissions.
- Target concurrency level: This field is shown only if Auto-recover rate limit errors is enabled. Change the predefined value as required to limit the number of concurrent API requests allowed by the connection resource. See also, Setting currency level on a connection.
- Concurrency level: When Auto-recover rate limit errors is checked, you can't modify the concurrency level because it matches the value set by the connected platform's runtime. When Auto-recover rate limit errors is not checked, you can enter a value to limit the number of concurrent API requests allowed by the connection resource. See also, Setting currency level on a connection.

E. Test and save the connection

Once you have configured the Oracle DB connection, you have a few options for continuing:

Save – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account
Save & close – click to test and save the connection and exit the Create connection pane
Cancel – click to exit without saving any new changes
Test connection – click this button to verify that your new connection is free of errors

When you test or save the connection, it is verified before continuing.

The new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.