Oracle Execute¶
Executes non-SELECT SQL statements (INSERT, UPDATE, DELETE, DDL) against an Oracle database. It uses saved Oracle credentials and a configurable timeout, and returns both a readable summary and the raw JSON response from the service.
Usage¶
Use this node when you need to modify data or schema in an Oracle database (e.g., insert new rows, update existing records, delete rows, or run DDL). Provide the SQL statement in the sql_text input. For data retrieval (SELECT), use SaltOracleQuery instead. Typical workflow: load credentials, set timeout if needed, author your DML/DDL SQL in sql_text, then connect the outputs to logging/validation or follow-up nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to stored Oracle credentials that match the 'oracle' credential template. | /workspace/credentials/oracle.json |
| timeout | False | INT | Maximum time (in seconds) to wait for the operation before timing out. | 60 |
| sql_text | True | STRING | An Oracle SQL statement to execute (INSERT/UPDATE/DELETE/DDL). The statement should be self-contained; parameter maps are not accepted by this node. | INSERT INTO employees (employee_id, first_name, last_name) VALUES (1001, 'Ada', 'Lovelace') |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | A human-readable summary of the execution result. | Oracle Execute Results: 1 row affected |
| json | JSON | Raw JSON payload returned by the service for programmatic use. | {"rows_affected": 1, "status": "success"} |
Important Notes¶
- Non-SELECT only: This node is intended for INSERT/UPDATE/DELETE or DDL. Use SaltOracleQuery for SELECT queries.
- Credentials: Requires a valid Oracle credential set that matches the 'oracle' template.
- Parameters: The node does not take a separate parameters map; provide a fully inlined SQL statement.
- Transactions/Auto-commit: Execution behavior (commit/rollback) is handled by the backing service; ensure your SQL aligns with your transaction expectations.
- Timeouts: Long-running statements may need a higher timeout value to avoid premature failure.
- Permissions: Ensure the database user has privileges to perform the requested operation.
Troubleshooting¶
- SQL errors (e.g., ORA-xxxxx): Verify your SQL syntax and object names. Ensure the target table/schema exists and the user has required privileges.
- No rows affected: Confirm WHERE clauses and data values. If inserting, check for constraint violations and unique keys.
- Timeouts: Increase the timeout input for large operations or heavy load. Validate network connectivity to the database service.
- Authentication/Authorization failures: Check credentials_path points to valid Oracle credentials matching the expected template and that the account is active.
- Bind variable issues: Since parameter maps are not supported, replace placeholders with literal values in sql_text or use a node that supports parameter binding.