Oracle

Oracle database is a multi-model database management system by Oracle Corporation. It can be hosted on-premise or in a private cloud.

Supported editions

All releases of Oracle database are supported.

How to connect to Oracle on Workato

The Oracle connector uses basic authentication to authenticate with Oracle. Configured Oracle connection

Field Description
Connection name Give this Oracle connection a unique name that identifies which Oracle instance it is connected to.
On-prem secure agent Choose an on-premise agent if your database is running in a network that does not allow direct connection. Before attempting to connect, make sure you have an active on-premise agent. Refer to the On-premise agent guide for more information.
Username Username to connect to Oracle.
Password Password to connect to Oracle.
Host URL of your hosted server.
Port Port number that your server is running on, typically 1521.
SID/Service name SID or Service name of your Oracle database instance you wish to connect to.

Working with the Oracle connector

Table, view and stored procedure

The Oracle connector works with all tables, views and stored procedures. These are available in pick lists in each trigger/action or you can provide the exact name.

Table selection from pick list Select a table/view from pick list

Exact table name provided Provide exact table/view name in a text field

Single row vs batch of rows

Oracle connector can read or write to your database either as a single row or in batches. When using batch triggers/actions, you have to provide a batch size you wish to work with. The batch size can be any number between 1 and 100, with 100 being the maximum size limit.

Batch trigger inputs Batch trigger inputs

Besides the difference in input fields, there is also a difference between the outputs of these 2 types of operations. A trigger that processes rows one at a time will have an output datatree that allows you to map data from that single row.

Single row output Single row output

However, a trigger that processes rows in batches will output them as an array of rows. The Rows datapill indicates that the output is a list containing data for each row in that batch.

Batch trigger output Batch trigger output

As a result, the output of batch triggers/actions needs to be handled differently. This recipe uses a batch trigger for new rows in the users table. The output of the trigger is used in a Salesforce bulk upsert action that requires mapping the Rows datapill into the source list.

Using batch trigger output Using batch trigger output

WHERE condition

This input field is used to filter and identify rows to perform an action on. It is used in multiple triggers and actions in the following ways:

  • filter rows to be picked up in triggers
  • filter rows in Select rows action
  • filter rows to be deleted in Delete rows action

This clause will be used as a WHERE statement in each request. This should follow basic SQL syntax. Refer to this Oracle documentation for a full list of rules for writing Oracle statements.

WHERE operators

Operator Description Example
= Equal WHERE ID = 445
!=
<>
Not equal WHERE ID <> 445
>
>=
Greater than
Greater than or equal to
WHERE PRICE > 10000
<
<=
Less than
Less than or equal to
WHERE PRICE > 10000
IN(...) List of values WHERE ID IN(445, 600, 783)
LIKE Pattern matching with wildcard characters (% and _) WHERE ID BETWEEN 445 AND 783
IS NULL
IS NOT NULL
NULL values check
Non-NULL values check
WHERE NAME IS NOT NULL

Simple statements

String values must be enclosed in single quotes ('') and column identifiers used must exist in the table.

A simple WHERE condition to filter rows based on values in a single column looks like this.

CURRENCY = 'USD'

If used in a Select rows action, this WHERE condition will return all rows that have the value 'USD' in the currency column. Just remember to wrap datapills with single quotes in your inputs.

Using datapills in WHERE condition Using datapills in WHERE condition

Column names that do not conform to standard rules (includes spaces, lower-case letters or special characters) must be enclosed in double quotes (""). For example, PUBLISHER NAME must be enclosed in backquotes to be used as a valid identifier.

"PUBLISHER NAME" = 'USD'

WHERE condition with enclosed identifier WHERE condition with enclosed identifier

Complex statements

Your WHERE condition can also contain subqueries. The following query can be used on the users table.

ID IN (SELECT "USER ID" FROM TICKETS WHERE PRIORITY >= 2)

When used in a Delete rows action, this will delete all rows in the users table where at least one associated row in the tickets table has a value of 2 in the priority column.

Using datapills in WHERE condition with subquery Using datapills in WHERE condition with subquery

results matching ""

    No results matching ""