Oracle Test Connection¶
Validates connectivity to an Oracle database using the provided credentials. It performs a lightweight test and returns both a human-readable status summary and a structured JSON response with details.
Usage¶
Use this node early in your workflow to verify that your Oracle credentials, host, port, and database settings are correct before running queries or metadata operations. Typical usage is immediately after loading or selecting Oracle credentials to ensure the environment is reachable and authentication works.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path to the saved Oracle credentials file that follows the Oracle credential template. | /workspace/credentials/oracle.json |
| timeout | True | INT | Maximum time in seconds to wait for the connection test to complete. | 60 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| string | STRING | A concise, human-readable summary of the connection test result. | Oracle Connection Test: Success |
| json_string | STRING | A JSON-formatted string with structured details of the test outcome, which may include status, messages, and diagnostic information. | {"status":"success","details":"Connected to Oracle database","latency_ms":128} |
Important Notes¶
- Credential Template: This node uses the Oracle credential template. Ensure your credentials file matches the required schema for Oracle (e.g., host, port, database/service, username, password, and any SSL settings as applicable).
- No extra parameters: The node does not require additional inputs beyond credentials and timeout for the connection test.
- Network access: The environment running this node must have network access to the Oracle host/port. Firewalls, VPNs, or security groups may block connectivity.
- Timeout behavior: If the database is slow to respond or the network is constrained, increase the timeout value accordingly.
Troubleshooting¶
- Authentication failed: Verify username/password in the credentials file and ensure the account is not locked or expired.
- Host unreachable or timeout: Check network connectivity, DNS resolution, firewall rules, and that the Oracle listener is running on the specified host/port.
- Service name/SID mismatch: Confirm that the credentials reference the correct Oracle service (SERVICE_NAME) or SID expected by the server.
- SSL or wallet issues: If using SSL/TLS or an Oracle wallet, confirm all required files and settings are correctly referenced in the credentials and accessible to the runtime.