Oracle List Schemas¶
Lists all available schemas in the connected Oracle database. It uses provided Oracle credentials to connect and returns a human-readable summary along with structured JSON data.
Usage¶
Use this node early in a database exploration workflow to discover which schemas exist before listing tables or querying specific objects. Provide a valid Oracle credential set and an appropriate timeout. The output includes both text and JSON so you can branch it to visualization or downstream logic.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to the saved Oracle credentials to use for the connection. | |
| timeout | True | INT | Maximum time in seconds to wait for the operation before timing out. | 30 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | A formatted, human-readable summary of the Oracle schemas. | Oracle Schemas: HR, SYSTEM, SYS, APP_DATA |
| json | JSON | Structured data containing the list of schemas and any additional metadata. | {"schemas": ["HR", "SYSTEM", "SYS", "APP_DATA"]} |
| html | HTML | HTML representation (empty for default output of this node). | |
| xlsx | XLSX | Excel file content (empty for default output of this node). | |
| PDF content (empty for default output of this node). |
Important Notes¶
- Credentials: Requires a valid Oracle credential configuration. Ensure the credential template matches the Oracle service.
- Permissions: The connected user must have privileges to view schemas; results may be limited by database permissions.
- Timeouts: Large environments or slow connections may require increasing the timeout value.
- Outputs: By default, this node returns text and JSON. HTML/XLSX/PDF outputs are not populated for this operation.
Troubleshooting¶
- Authentication failed: Verify the credentials file path and contents, and ensure host/port/service name are correct.
- Timeout or network errors: Increase the timeout value and confirm network access to the Oracle server.
- Empty or partial schema list: Check user permissions in Oracle; lack of privileges can hide schemas.
- Unexpected output format: Ensure downstream nodes handle text/JSON; this node does not generate HTML/XLSX/PDF by default.