Oracle Connection String¶
Builds a valid Oracle database connection URI from individual parameters. Supports service name or SID style connections and optionally appends character encoding. Returns the constructed URI as the primary output; other outputs are unused placeholders.
Usage¶
Use this node when you need to generate a single Oracle connection string to feed into other Oracle database nodes as the credentials_path. Typical workflow: configure host, port, service/service SID, username and password (and optionally encoding), run this node, then connect its 'result' output to subsequent Oracle query or management nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| host | True | STRING | Database hostname or IP address. | db.company.com |
| port | True | INT | Database port number. | 1521 |
| service_name | True | STRING | Oracle service name or SID (value is used for both; behavior depends on connection_type). | XE |
| username | True | STRING | Database username. | system |
| password | True | PASSWORD | Database password corresponding to the username. | |
| connection_type | True | CHOICE | Select whether to connect using a service name or a SID. | service_name |
| encoding | True | STRING | Character encoding to append to the URI. If left as UTF-8 (default), no parameter is added. | UTF-8 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| result | STRING | The constructed Oracle connection URI. This is the value you pass as credentials_path to other nodes. | oracle://system: |
| json_result | STRING | JSON output used only when an error occurs; otherwise empty. | |
| html_table | STRING | Not used by this node; returned as an empty string. | |
| xlsx_data | STRING | Not used by this node; returned as an empty string. | |
| pdf_data | STRING | Not used by this node; returned as an empty string. |
Important Notes¶
- If connection_type is 'sid', the URI includes '?sid=
'; otherwise it uses the service name path segment without the sid parameter. - The encoding parameter is only appended when it is not 'UTF-8'.
- Special characters in usernames or passwords may require URL-safe encoding before use to avoid malformed URIs.
- This node does not test connectivity; it only constructs the string. Use an Oracle test/connection node to validate.
- The password is embedded in the URI. Handle and store this output securely.
Troubleshooting¶
- Connection failures in downstream nodes: Verify host, port, and whether your database expects a service name vs a SID. Switch the connection_type accordingly.
- Authentication errors: Confirm username/password are correct and URL-safe (encode characters like @, :, /, or spaces).
- Invalid service or SID: Ensure the 'service_name' matches your Oracle configuration (e.g., service alias in tnsnames.ora).
- Character encoding issues: If you see garbled characters, try setting a specific encoding (e.g., 'AL32UTF8') and regenerate the URI.
- Downstream node shows empty credentials: Make sure you wired this node's 'result' output to the 'credentials_path' input of the target node.