Overview
This node allows executing SQL queries on an Oracle Database. It supports parameterized queries with flexible input parameters, including support for handling multiple values in IN statements. This makes it useful for scenarios where you need to read, insert, update, or delete data in an Oracle database directly from your workflow.
Typical use cases include:
- Fetching records based on dynamic criteria.
- Updating or inserting data using parameterized SQL.
- Running complex queries that require multiple parameters, including lists of values for
INclauses.
For example, you could run a query like:
SELECT id, name FROM product WHERE id < :param_name
with param_name provided dynamically as a parameter.
Properties
| Name | Meaning |
|---|---|
| SQL Statement | The SQL query to execute. Supports bind parameters prefixed with : (e.g., :param_name). |
| Parameters | A collection of named parameters to bind to the SQL query. Each parameter includes: - Name: The parameter name without the leading colon. - Value: The value to bind. - Data Type: Either "String" or "Number". - Parse for IN statement: If set to "Yes", the value is treated as a comma-separated list and expanded into multiple bind variables for use in an IN clause. |
Output
The node outputs an array of JSON objects representing the rows returned by the executed SQL query. Each object corresponds to a row, with keys matching the column names.
If the query modifies data (e.g., INSERT, UPDATE), the output will reflect any returned rows if applicable.
No binary data output is produced by this node.
Dependencies
- Requires an Oracle Database connection configured via credentials containing user, password, connection string, and optionally privilege and thin mode settings.
- Uses the official OracleDB Node.js driver (
oracledbpackage). - Requires proper network access and permissions to connect to the target Oracle database.
Troubleshooting
- Connection errors: Ensure credentials are correct and the Oracle database is reachable.
- SQL syntax errors: Verify the SQL statement syntax and parameter names match those used in the query.
- Parameter binding issues: Make sure parameter names do not start with a colon (
:) and that data types correspond correctly to the expected types in the database. - IN statement parsing: When using the "Parse for IN statement" option, ensure the value is a properly formatted comma-separated string without extra spaces unless intended.
- Resource cleanup: The node attempts to close the database connection after execution; failures here are logged but do not stop the workflow.
Common error messages come from the OracleDB driver and typically indicate issues with authentication, connectivity, or SQL execution. Review the error message details to adjust credentials, network settings, or query syntax accordingly.