Oracle List Schemas
Retrieves all available schemas from the connected Oracle database using the provided credentials. Returns a human-readable summary and structured JSON, with optional formatted exports.
Usage
Use this node to discover which schemas exist in your Oracle instance before listing tables or building queries. Place it early in a workflow to validate connectivity and explore the database structure.
| Field | Required | Type | Description | Example |
|---|
| credentials_path | True | STRING | Path to the saved Oracle credential profile containing connection details. | /projects/my-flow/credentials/oracle.json |
| timeout | False | INT | Maximum time (in seconds) to wait for the operation before it times out. | 30 |
Outputs
| Field | Type | Description | Example |
|---|
| text | STRING | Readable summary of the schemas found. | Oracle Schemas: HR, SALES, SYSTEM, USERS |
| json | JSON | Structured JSON payload containing the list of schemas and related metadata. | {"schemas": ["HR", "SALES", "SYSTEM", "USERS"], "count": 4} |
| html | STRING | HTML-formatted table of schemas for rendering in UI contexts. May be empty if not requested by downstream tools. | |
| xlsx | FILE | Excel file export of the schema list when applicable. May be empty if not generated. | |
| pdf | FILE | PDF export of the schema list when applicable. May be empty if not generated. | |
Important Notes
- Credentials required: The node requires a valid Oracle credential profile to connect.
- Permissions affect results: The schemas returned depend on the database permissions of the provided user.
- Timeout behavior: Long-running or slow connections may require increasing the timeout input.
- Output variability: Depending on configuration and downstream usage, only text and JSON may be populated; HTML/XLSX/PDF may be empty.
Troubleshooting
- Connection failed: Verify the credentials file path and contents, network access to the Oracle host, and that the database is reachable.
- No schemas returned: Ensure the user has permission to view schemas. Try connecting with a user that has the necessary privileges.
- Operation timed out: Increase the timeout input and confirm the database isn't under heavy load.
- Authentication errors: Confirm username, password, service name/SID, and connection parameters in the credentials profile.