Oracle Connection String¶
Builds an Oracle database connection URI from individual parameters. Supports both service name and SID connection types, and optionally appends a custom character encoding. Returns the constructed connection string in the node’s primary text output slot.
Usage¶
Use this node when you need a correctly formatted Oracle connection URI to pass into downstream database nodes or any component that accepts a connection string. Typical workflow: provide host, port, service name or SID, and credentials; choose the connection type; optionally set a non-default encoding; then connect the resulting string to nodes that initiate database operations.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| host | True | STRING | Database hostname or IP address where the Oracle instance is reachable. | db.example.com |
| port | True | INT | TCP port for the Oracle listener. Valid range is 1–65535. | 1521 |
| service_name | True | STRING | Oracle service name or SID, depending on the selected connection type. | ORCLPDB1 |
| username | True | STRING | Database user for authentication. | system |
| password | True | PASSWORD | Password for the specified database user. | |
| connection_type | True | ["service_name", "sid"] | Choose whether the value provided is a service name or a SID. Determines how the URI is formed. | service_name |
| encoding | True | STRING | Optional character encoding appended as a query parameter when not UTF-8. | AL32UTF8 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Primary output containing the constructed Oracle connection string (URI). | oracle://system: |
| json | STRING | Auxiliary JSON output. Not used by this node (empty). | |
| html | STRING | Auxiliary HTML output. Not used by this node (empty). | |
| xlsx | BYTES | Auxiliary Excel output. Not used by this node (empty). | |
| BYTES | Auxiliary PDF output. Not used by this node (empty). |
Important Notes¶
- If connection_type is "sid", the node appends a sid parameter and still uses the same service_name value in the path component.
- The encoding parameter is only added to the URI when it differs from UTF-8.
- Ensure usernames and passwords with special characters are URL-safe; if needed, URL-encode credentials before use.
- This node does not test connectivity; it only formats the connection string.
Troubleshooting¶
- Constructed string fails to connect: Verify host, port, and that connection_type matches your database configuration (service name vs SID).
- Authentication errors: Confirm username/password and check if special characters require URL-encoding.
- Invalid service name/SID: Confirm the exact service name or SID from your Oracle listener configuration.
- Unexpected character encoding behavior: Leave encoding as UTF-8 (default) unless your environment requires a different value.