Oracle Complex Query
Executes complex Oracle SQL statements, including multi-table JOINs and advanced clauses. It sends your SQL and a declared query type to the Oracle data service and returns results formatted for text and JSON, with optional rich outputs depending on the downstream formatting utilities.
Usage
Use this node when you need to run non-trivial Oracle queries (e.g., JOINs, GROUP BY, HAVING) against a configured Oracle database. Provide a valid credentials file path, set a suitable timeout, enter your SQL, and specify the query type (typically SELECT). This node fits into workflows where you need to retrieve or process relational data from Oracle and pass the results to subsequent steps.
| Field | Required | Type | Description | Example |
|---|
| credentials_path | True | STRING | Path to the saved Oracle credentials file to authenticate the request. | /workspace/credentials/oracle.json |
| timeout | True | INT | Maximum time (in seconds) to wait for the Oracle service to execute the query. | 60 |
| sql_text | True | STRING | The complex SQL statement to execute. Supports typical Oracle syntax including JOINs and advanced clauses. | SELECT e.employee_id, e.first_name, e.last_name, d.department_name FROM employees e JOIN departments d ON e.department_id = d.department_id WHERE e.salary > 50000 |
| query_type | True | STRING | Type of SQL query you are executing. Typically 'SELECT'; used by the service to route execution. | SELECT |
Outputs
| Field | Type | Description | Example |
|---|
| text | STRING | Human-readable summary or table-like text of the query results. | Oracle Complex Query (SELECT) Rows: 10 Columns: employee_id, first_name, last_name, department_name |
| json | STRING | Full JSON payload with the raw results from the Oracle service. | {"rows": [{"employee_id": 101, "first_name": "Neena", "last_name": "Kochhar", "department_name": "Executive"}], "row_count": 10} |
| html | HTML | HTML representation of the result table (if generated by downstream formatting). | | employee_id | first_name | last_name | department_name |
|---|
...
|
| xlsx | BYTES | Binary data for an Excel export of the results (if generated). | ... |
| pdf | BYTES | Binary data for a PDF export of the results (if generated). | ... |
Important Notes
- The node requires a valid Oracle credentials file; ensure it matches the 'oracle' credential template configured in your environment.
- query_type should reflect the SQL being run (commonly 'SELECT'). Mismatched query_type and SQL may lead to service errors.
- If your SQL uses bind variables (e.g., :min_salary), ensure they are supported or inlined as literals; otherwise the service may return parameter binding errors.
- Large or long-running queries may require increasing the timeout input.
- Outputs typically include text and JSON. HTML/XLSX/PDF outputs are produced when formatting/export utilities are triggered downstream.
Troubleshooting
- Connection or authentication errors: Verify credentials_path points to a valid Oracle credential file and that the database is reachable.
- SQL syntax errors: Validate the sql_text in an Oracle client and correct any syntax issues.
- Timeouts: Increase the timeout value or optimize the query (indexes, filters).
- Bind variable errors (e.g., missing value for :param): Replace bind variables with literals or configure supported parameter passing in your SQL.
- Empty or unexpected results: Confirm table names, schema context, JOIN conditions, and WHERE filters are correct for your data.
