Overview
This node executes SQL statements on an Oracle database. It is designed to run queries or commands by connecting to an Oracle DB using provided credentials and returning the results as JSON data. This node is useful for integrating Oracle database operations into automated workflows, such as fetching records, updating data, or running complex queries dynamically.
Practical examples include:
- Retrieving product information based on dynamic parameters.
- Inserting or updating rows in Oracle tables.
- Running batch queries with parameterized inputs to avoid SQL injection risks.
Properties
| Name | Meaning |
|---|---|
| SQL Statement | The SQL query or command to execute on the Oracle database. Supports bind parameters prefixed with : (e.g., :param_name). |
| Parameters | A collection of named parameters to bind to the SQL statement. Each parameter includes: - Name: The placeholder name without the colon prefix. - Value: The value to bind. - Data Type: Either "String" or "Number". - Parse for IN Statement: If set to "Yes", treats the value as a comma-separated list and expands it into multiple bind variables for use in SQL IN clauses. |
Output
The output is a JSON array representing the rows returned by the executed SQL statement. Each element corresponds to one row, with key-value pairs matching column names and their values.
If the SQL statement does not return rows (e.g., an UPDATE), the output will reflect the result accordingly (usually empty or metadata).
No binary data output is produced by this node.
Dependencies
- Requires an Oracle database accessible via network.
- Needs valid Oracle database credentials including user, password, and connection string.
- Uses the official OracleDB Node.js driver (
oracledbpackage). - Requires n8n credentials configured with appropriate Oracle connection details.
- No additional environment variables are explicitly required beyond standard Oracle client setup.
Troubleshooting
- Connection errors: Ensure the Oracle database is reachable from the n8n instance and credentials are correct.
- SQL syntax errors: Verify the SQL statement syntax and parameter placeholders match the defined parameters.
- Parameter binding issues:
- Parameter names must not start with a colon (
:). - When using "Parse for IN Statement," ensure the value is a comma-separated string without spaces unless intended.
- Parameter names must not start with a colon (
- Resource cleanup warnings: If the node logs failure to close connections, check network stability and Oracle client configuration.
- Unsupported features: Complex PL/SQL blocks or multi-statement executions may require adjustments or separate handling.