Skip to content

Oracle Query

Runs a read-only SQL SELECT statement against an Oracle database using the configured Oracle credentials. It sends the query to the Oracle service endpoint and returns formatted results as plain text plus a JSON payload, with optional export-friendly formats left empty by default.
Preview

Usage

Use this node when you need to fetch data from Oracle (SELECT queries). Provide a valid credentials file path and a SELECT statement. Chain its outputs to downstream nodes that parse JSON results or display text summaries. For write operations (INSERT/UPDATE/DELETE), use the Oracle Execute node instead.

Inputs

FieldRequiredTypeDescriptionExample
credentials_pathTrueSTRINGPath to the saved Oracle credentials file matching the 'oracle' credential template./workspace/credentials/oracle.json
timeoutTrueINTMaximum time in seconds to wait for the Oracle service to complete the request.60
sql_textTrueSTRINGSQL SELECT statement to execute against Oracle. Use Oracle-specific syntax for limits and joins.SELECT * FROM employees WHERE ROWNUM <= 10

Outputs

FieldTypeDescriptionExample
textSTRINGHuman-readable summary of the query result (first rows, row count, etc.).Oracle Query Results: 10 rows returned
jsonSTRINGRaw JSON response containing the query result data and metadata.{"data": [{"EMPLOYEE_ID": 101, "FIRST_NAME": "Neena"}], "row_count": 1}
htmlSTRINGHTML representation of the result (empty by default with the standard formatter).
xlsxBYTESExcel-formatted binary payload of results (empty by default with the standard formatter).
pdfBYTESPDF-formatted binary payload of results (empty by default with the standard formatter).

Important Notes

  • This node is intended for SELECT (read-only) queries. For INSERT/UPDATE/DELETE, use the 'Oracle Execute' node.
  • Credentials must match the 'oracle' credential template and be valid for the target database/schema.
  • Oracle uses ROWNUM or FETCH FIRST for limiting rows. Ensure your SQL uses Oracle-compatible syntax.
  • Large result sets may be subject to service timeouts or size limits; consider filtering or limiting rows.
  • The node returns text and JSON by default; HTML/XLSX/PDF outputs are left empty unless a different formatter/export path is used downstream.
  • SQL parameters are not automatically bound in this node; provide complete SQL text as executed.

Troubleshooting

  • Query fails with authentication error: Verify credentials_path points to a valid Oracle credential and that the user has necessary permissions.
  • Timeouts occur: Increase the timeout input or narrow your query (add filters/limits).
  • Syntax errors: Ensure the SQL uses Oracle-specific syntax (e.g., ROWNUM or FETCH FIRST n ROWS ONLY).
  • Empty results: Confirm the target schema/table and WHERE conditions; check user permissions on the tables.
  • Service connection issues: Ensure the Oracle service is reachable and healthy; retry after verifying network and service status.