BGS-Oracledb-connector icon

BGS-Oracledb-connector

Execute queries on Oracle Database
Join our community

Actions5

Overview

This node connects to an Oracle Database and performs various database operations such as executing SQL queries, inserting rows, updating rows, deleting rows, and executing stored procedures. It is useful for automating database interactions within workflows, such as updating records based on input data, running custom queries, or managing data in Oracle tables.

Use Case Examples

  1. Updating user information in a database table based on a unique key.
  2. Executing a stored procedure to perform complex database logic.
  3. Deleting records from a table based on specified criteria.

Properties

Name Meaning
Table The name of the database table to operate on, required for insert, update, and delete operations.
Update Key The column name used to match rows for updating records in the table.
Options Additional options for the database operation, including auto-commit behavior, fetch size, and maximum rows to return.

Output

JSON

  • json
    • success - Indicates if the operation was successful (true/false).
    • rowsAffected - Number of rows affected by the operation (insert, update, delete).
    • outBinds - Output bindings returned from executing a stored procedure.
    • error - Error message if the operation failed.
  • json (query result rows) - Rows returned from executing a SQL query, each row as a JSON object.

Dependencies

  • Oracle Database client library (oracledb)

Troubleshooting

  • Ensure Oracle client libraries are installed and properly configured, as the node attempts to initialize the Oracle client and may skip if not found.
  • Verify database connection credentials and connection string parameters are correct to avoid connection failures.
  • Check that SQL queries and parameters are valid and properly formatted JSON when required.
  • If an error occurs during execution, the node can continue on fail if configured, otherwise it throws an error with the message.
  • Errors closing the database connection are logged but do not stop the workflow.

Links

Discussion