Oracle Execute¶
Runs non-SELECT SQL statements (INSERT, UPDATE, DELETE, DDL) against an Oracle database. It uses provided credentials, sends the SQL to the Oracle service, and returns a human-readable summary plus the raw JSON result.
Usage¶
Use this node when you need to modify data or schema in an Oracle database as part of a workflow (e.g., inserting records, updating fields, deleting rows, creating/dropping tables). Typically placed after a credentials-loading step, it executes the given SQL text within the configured timeout and returns execution results for logging or branching.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path to the stored Oracle credentials configuration to authenticate the request. | /path/to/credentials/oracle.json |
| timeout | True | INT | Maximum time in seconds to wait for the operation before timing out. | 60 |
| sql_text | True | STRING | The SQL statement to execute. Intended for INSERT/UPDATE/DELETE or DDL statements. | UPDATE employees SET salary = salary * 1.05 WHERE department_id = 10 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Readable summary of the execution (e.g., operation type and outcome). | Oracle Execute Results: 25 rows affected. |
| json | JSON | Raw JSON payload returned by the Oracle service with details about the execution. | {"status":"success","rows_affected":25} |
Important Notes¶
- This node is designed for executing non-SELECT statements; for SELECT queries, use the Oracle Query node.
- Credentials must be valid and grant sufficient permissions for the SQL being executed.
- Bind variables are not supported as separate inputs; provide fully formed SQL with literal values or ensure the service can handle your SQL as provided.
- Execution behavior (e.g., transaction handling, autocommit) follows the backing Oracle service configuration.
- Large or long-running statements may require increasing the timeout to avoid premature failure.
Troubleshooting¶
- SQL errors (e.g., ORA-00900, ORA-00933): Verify your SQL syntax and ensure it matches Oracle SQL standards.
- Permission denied (e.g., ORA-01031): Ensure the credentialed user has the necessary privileges for the target tables or DDL.
- Connection/timeout issues: Check network access to the Oracle service and increase the timeout input if the operation is expected to run long.
- No rows affected when expected: Confirm WHERE clause conditions and that the target records exist.
- Service returned unexpected JSON: Inspect the json output for error fields and message details to guide remediation.