Skip to content

Oracle Database Info

Retrieves instance-level information from an Oracle database using the provided credentials. Returns a human-readable summary along with the raw JSON payload. This node does not require any additional Oracle-specific parameters.
Preview

Usage

Use this node to quickly verify and inspect Oracle database instance metadata (such as version, host, and status) after setting up credentials. It’s typically placed early in a workflow to validate connectivity and environment details before running queries or schema introspection.

Inputs

FieldRequiredTypeDescriptionExample
credentials_pathTrueSTRINGPath or reference to the saved Oracle credentials that include connection details (host, port, service/SID, username, password)./configs/credentials/oracle.json
timeoutFalseINTMaximum time in seconds to wait for the request to complete before timing out.60

Outputs

FieldTypeDescriptionExample
textSTRINGReadable summary of the Oracle database information.Oracle Database Info: Version 19c, Status OPEN, Service XE
jsonJSONRaw JSON payload of the database info response for programmatic use.{"version":"19c","status":"OPEN","service_name":"XE","host":"db-host","port":1521}
htmlHTMLHTML output (unused for this node’s default formatting; typically empty).
xlsxXLSXXLSX binary output (unused for this node’s default formatting; typically empty).
pdfPDFPDF binary output (unused for this node’s default formatting; typically empty).

Important Notes

  • Credentials required: Valid Oracle connection details must be provided via credentials_path.
  • Read-only operation: This node only retrieves metadata and does not modify any data.
  • Timeout behavior: If the Oracle server is slow or unreachable, increase the timeout value.
  • Output formats: By default, only text and JSON are populated; HTML/XLSX/PDF are left empty.

Troubleshooting

  • Connection failed or timed out: Verify host, port, and network access; increase the timeout value if needed.
  • Authentication error: Check username/password and that the account has permission to access instance metadata.
  • Service/SID mismatch: Ensure the credentials correctly specify service name vs. SID according to your Oracle setup.
  • Empty or minimal info: Confirm the Oracle instance is running and accessible, and that the user has adequate privileges.