Oracle Connection String¶
Builds a valid Oracle database connection URI from separate parameters. Supports both service name and SID styles, and can append a custom character encoding. Intended to simplify passing a single, correctly formatted connection string to downstream database nodes.
Usage¶
Use this node when you need to assemble an Oracle connection string from host, port, service/service_name (or SID), username, and password. Typically placed before nodes that accept a connection string for querying or executing commands against an Oracle database.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| host | True | STRING | Database hostname or IP address. | db.company.internal |
| port | True | INT | Oracle listener port. Must be between 1 and 65535. | 1521 |
| service_name | True | STRING | Oracle service name or SID to connect to. Used for both connection types; for SID connections it is appended as a sid query parameter. | XE |
| username | True | STRING | Database username. | system |
| password | True | PASSWORD | Database password for the specified user. | |
| connection_type | True | ["service_name", "sid"] | Choose how to form the connection: service_name uses the standard path segment; sid adds a sid query parameter. | service_name |
| encoding | True | STRING | Optional character encoding to append to the URI. If set to UTF-8 (default), it is omitted. | AL32UTF8 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | The constructed Oracle connection string. | oracle://system: |
| json | JSON | JSON output (unused when successful; contains error details if construction fails). | {"error": "Failed to construct connection string: |
| html | HTML | HTML output placeholder (empty for this node). | |
| xlsx | XLSX | XLSX output placeholder (empty for this node). | |
| PDF output placeholder (empty for this node). |
Important Notes¶
- Output format: Only the text output is meaningful on success; other outputs remain empty.
- Service name vs SID: When connection_type is "sid", the node appends "?sid=
" to the URI path; otherwise it uses the service name in the standard path segment. - Encoding parameter: The encoding query parameter is only added if it differs from "UTF-8".
- Security: Never hard-code real credentials in shared workflows. Use secure credential management where possible.
- Example URI structure: service_name: oracle://username:password@host:port/SERVICE; sid: oracle://username:password@host:port/SERVICE?sid=SERVICE
Troubleshooting¶
- Invalid or empty password produces connection failures downstream: Confirm the password input is correct and not blank.
- Wrong connection_type: If you see authentication or service errors, try switching between service_name and sid depending on your Oracle setup.
- Bad host/port: If clients cannot reach the database, verify hostname resolution and that the port (default 1521) is open and correct.
- Encoding issues: If you observe garbled characters, set encoding to the correct Oracle charset (e.g., AL32UTF8) instead of UTF-8.
- Error output: If construction fails, check the json output for an "error" message detailing the reason.