Oracle Query¶
Executes a read-only SQL SELECT query against an Oracle database through the Salt data-connector service. It loads connection credentials from a database URI, calls the Oracle service endpoint, and returns both a human-readable summary and raw JSON results.
Usage¶
Use this node when you need to fetch data from an Oracle database with a SELECT statement. Provide a valid Oracle connection URI and your SQL text. Typical workflow: set credentials_path, optionally adjust timeout, enter your SELECT query, then consume either the formatted text result for quick inspection or the JSON output for downstream processing. For write operations (INSERT/UPDATE/DELETE), use SaltOracleExecute instead.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Oracle database connection URI. Must use the oracle:// scheme. The path component determines SID or service name: if it contains a dot it is treated as a service_name; otherwise it is treated as a SID. | oracle://scott: |
| timeout | True | INT | Request timeout in seconds for the query execution against the data-connector service. | 60 |
| sql_text | True | STRING | SQL SELECT statement to execute against the Oracle database. | SELECT employee_id, first_name, last_name FROM employees WHERE ROWNUM <= 10 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| result | STRING | Human-readable summary of the query results, including row count and row-by-row key-value display. | Query Results (10 rows): employee_id: 100 \| first_name: Steven \| last_name: King employee_id: 101 \| first_name: Neena \| last_name: Kochhar |
| json_result | STRING | Raw JSON response string containing the data returned by the service, suitable for downstream parsing. | {"data":[{"EMPLOYEE_ID":100,"FIRST_NAME":"Steven","LAST_NAME":"King"}],"row_count":1} |
| html_table | STRING | HTML table representation of the results. For this node’s default output mode, this is returned as an empty string. | |
| xlsx_data | STRING | Base64-encoded XLSX content of the results. For this node’s default output mode, this is returned as an empty string. | |
| pdf_data | STRING | Base64-encoded PDF content of the results. For this node’s default output mode, this is returned as an empty string. |
Important Notes¶
- Read-only operation: This node is intended for SELECT queries. Use SaltOracleExecute for INSERT/UPDATE/DELETE.
- Credentials URI required: The credentials_path must be a valid Oracle URI (oracle://...). If the path after the host contains a dot, it is interpreted as service_name; otherwise as SID.
- Service dependency: The node communicates with the configured Oracle data-connector service endpoint. Ensure the oracle_data_connector endpoint is configured in your environment.
- Output formats: Only the formatted text and JSON outputs are populated by default. HTML, XLSX, and PDF outputs are empty strings in this node.
- Timeouts: Long-running queries may require increasing the timeout value.
- Security: Do not paste real passwords into shared workflows. Use secure secret management where possible.
Troubleshooting¶
- Invalid credentials URI: If you see an error like "Invalid credentials URI" or "Credentials URI is required", verify the URI format: oracle://
: @ : / . - Service URL not configured: Errors about missing service URL indicate the oracle_data_connector endpoint is not set in environment configuration. Configure it before running.
- Request failed or timed out: If requests fail or timeout, check network access to the data-connector service, increase the timeout, and confirm the Oracle instance is reachable.
- Unsupported SQL: If the query returns errors, ensure you are using a valid SELECT statement supported by Oracle and that referenced schemas/tables are accessible to the provided user.
- No data returned: If result shows "No data returned", verify your WHERE clause, user permissions, and that the target table contains matching rows.
- SID vs Service Name: If connection fails, confirm that the database path in the URI correctly represents SID or service_name; e.g., oracle://user:pass@host:1521/ORCL (SID) vs oracle://user:pass@host:1521/orcl.example.com (service name).