Skip to main content
Available starting with FlowX.AI 5.7.0Oracle Database integration supports Oracle 19c, 21c, and 23ai. The integration uses the ojdbc11 driver, the same driver used by other FlowX services.

​
Overview

Oracle Database is a relational data source type that lets you connect FlowX workflows to Oracle databases that your organization manages independently. You configure a connection, save named SQL queries against the schema, and call those queries from workflows.

Connect to your Oracle instance

Connect via Service Name or SID, with an optional SSL toggle

Schema-aware SQL editor

Monaco editor with SQL syntax highlighting, schema-aware autocomplete, and a side panel that lists tables, columns, primary keys, and foreign keys

Test before you ship

Run any saved query with sample parameters and inspect the response: table view for SELECT, affected-row count for INSERT / UPDATE / DELETE

Reusable in workflows

Reference Oracle queries from the Database Operation node alongside other data sources

​
Prerequisites

  • An Oracle Database 19c, 21c, or 23ai instance accessible from your FlowX deployment
  • A database user with the privileges your queries require (typically SELECT, INSERT, UPDATE, DELETE on the target schema, plus SELECT on data dictionary views for schema discovery)
  • Network connectivity between the nosql-db-runner service and the Oracle instance
  • For SSL connections: appropriate certificates configured on the Oracle instance and trusted by the FlowX deployment

​
Creating an Oracle Database data source

Oracle Database data source settings
1

Open Data Sources

Navigate to Integration Designer → Data Sources in your project.
2

Add a new data source

Click the + button to open the Add Data Source dialog. In the Databases category, select Oracle Database.
3

Configure the connection

Fill in the connection fields:
FieldDescription
HostOracle server hostname or IP
PortOracle listener port (default 1521)
Database Name / SIDThe service name or SID, depending on the connection type
Schema NameOptional. The schema to use for queries and discovery
SSL EnabledToggle SSL on or off for the connection
Connection TypeService Name or SID
UsernameDatabase username
PasswordDatabase password
Each field accepts configuration parameters for environment-specific values.
4

Test the connection

Click Test Connection and Rescan to verify connectivity and refresh the schema cache.
The data source is created even if the connection test fails, so you can save partial configuration and resolve connectivity later. Return to the Settings tab and click Test Connection and Rescan once the issue is fixed.
5

Save

Click Save to create the data source.

​
Queries

Each Oracle Database data source holds a list of named SQL queries. A query is a single parameterized SQL statement that you can call from a workflow.

​
SQL editor

Open the Queries tab on the data source, then click New query to open the editor:
  • Query area: Monaco editor with SQL syntax highlighting and schema-aware autocomplete. Use Oracle-native bind variables (:paramName); they’re auto-detected from the query text and surfaced in the parameters panel.
  • Parameters panel (left): declare each bind parameter with a type. Supported types are STRING, NUMBER, BOOLEAN, DATE, and CURRENCY.
  • Schema browser (right): pick a table from the dropdown to inspect its columns. Primary-key and foreign-key badges appear next to column names. Hover a foreign-key badge to see the referenced table and column.

​
Testing a query

Click Test query to open the test modal:
  • Parameters: supply values for declared bind parameters.
  • Query and tables: view the SQL and the resolved schema context.
  • Response: for SELECT, results render as both a table and JSON, with totalCount and executionTimeMs. For INSERT / UPDATE / DELETE, the response is affectedRows. Errors include the Oracle sqlState and message (for example, ORA-00942: table or view does not exist).
The modal warns before discarding unsaved changes.

​
Using in workflows

Oracle queries are called from the existing Database Operation node in workflows.
1

Add a Database Operation node

On the workflow canvas, drag a Database Operation node onto the workspace.
2

Select the data source and query

In the node configuration panel, pick the Oracle data source. The query picker then lists only the queries saved on that data source.
3

Map parameters

Map workflow inputs to the query’s bind parameters. Map the response (rows or affectedRows) to a workflow variable.
Scoping the picker to the selected data source keeps Oracle queries and MongoDB operations separate, even when both data source types exist in the same project.

​
Deployment

No new microservices are required. Oracle Database queries run inside the existing nosql-db-runner service, which bundles the Oracle JDBC driver. Each Oracle data source uses its own HikariCP connection pool.

​
Configuration defaults

The following defaults apply to all Oracle data sources and can be tuned via environment variables on the nosql-db-runner service:
Environment VariableDescriptionDefault
FLOWX_JDBC_CONNECTIONS_CACHE_MAX_ENTRIESMaximum cached JDBC connection pools100
FLOWX_JDBC_CONNECTIONS_CACHE_TTLTime-to-live for cached connection pools1d
FLOWX_SQL_DEFAULTS_MAX_POOL_SIZEMaximum HikariCP pool size per data source5
FLOWX_SQL_DEFAULTS_CONNECTION_TIMEOUT_SECONDSJDBC connection timeout10
FLOWX_SQL_DEFAULTS_ROW_LIMITDefault row cap on SELECT responses1000
FLOWX_SQL_DEFAULTS_QUERY_TIMEOUT_SECONDSQuery execution timeout30
Ensure the nosql-db-runner service has network access to your Oracle instance. If Oracle is behind a firewall, configure the appropriate network rules.

FlowX Database

Managed MongoDB data storage within FlowX

Unmanaged MongoDB

Connect to externally managed MongoDB instances

Integration Designer

Overview of all data source types and workflow building

NoSQL DB Runner setup

Deployment configuration for the database runner service
Last modified on April 28, 2026