Oracle Test Connection¶
Validates connectivity to an Oracle database using provided credentials. It sends a lightweight test request to confirm that the host, port, service/SID, and authentication are correct, returning a human-readable status and a structured JSON result.
Usage¶
Use this node early in a workflow to confirm that your Oracle database credentials and network access are correctly configured before running queries or schema operations. Point it to an Oracle credential file or connection configuration and set a suitable timeout to catch network or authentication issues quickly.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | CREDENTIALS | Path or reference to the stored Oracle credentials. Must include host, port, service/SID, username, and password (and any required options). | |
| timeout | True | INT | Maximum time, in seconds, to wait for the test connection to complete before failing. | 30 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | A concise, human-readable summary of the connection test outcome. | Oracle Connection Test: Success |
| json | JSON | Structured details about the connection test, including status and any diagnostic messages. | {"status":"success","message":"Connection established","latency_ms":124} |
| html | STRING | HTML-formatted output (may be empty for this operation). | |
| xlsx | BYTES | Binary Excel content for exports (not typically used for connection tests). | |
| BYTES | Binary PDF content for exports (not typically used for connection tests). |
Important Notes¶
- Ensure the credentials reference uses the Oracle template and contains valid host, port, service name or SID, username, and password.
- The timeout applies to the remote connectivity check; slow networks or database servers may require a higher value.
- This node does not execute SQL; it only validates that a connection can be established.
- Network/firewall rules, SSL/wallet requirements, or VPN constraints can cause failures even with correct credentials.
Troubleshooting¶
- Connection failed: Verify host, port, and service/SID in the credentials, and confirm the database is reachable from your network.
- Authentication error: Check username/password in the credentials and any account lock or permission issues on the database.
- Timeouts: Increase the timeout input and re-run; also verify latency, firewall rules, and that the Oracle listener is running.
- SSL/TLS or wallet issues: If your Oracle environment requires wallets or certificates, confirm those settings are correctly configured in the credentials.
- Unexpected errors: Recreate the credentials using the Oracle Connection String node or re-upload a clean credentials file, then test again.