Oracle Table Info¶
Retrieves metadata for a specific Oracle table. It loads Oracle credentials, calls the table-info endpoint with the provided table and optional schema, and returns a human-readable summary plus a JSON payload of the table details.
Usage¶
Use this node when you need to inspect the structure of a table in an Oracle database (e.g., columns, data types, and related metadata). Typically placed early in a data workflow to validate schemas before building queries, transformations, or reports.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | Not specified | Path or handle to the stored Oracle credentials used for authentication. | |
| timeout | True | Not specified | Maximum time to wait for the operation to complete before failing. | 30 |
| table_name | True | STRING | The name of the Oracle table to analyze. | employees |
| schema_name | True | STRING | Schema name containing the table. Leave empty to use the current user schema. | HR |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | A readable summary describing the Oracle table information request and results. | Oracle Table Info: employees |
| json | JSON | Structured JSON containing table metadata returned by the service (e.g., columns, data types, nullable flags, indexes if provided). | {"table":"employees","columns":[{"name":"EMPLOYEE_ID","type":"NUMBER","nullable":false}]} |
Important Notes¶
- Schema handling: If schema_name is left empty, the current user schema is used by default.
- Credentials required: Valid Oracle credentials are required; the node uses an Oracle credential template.
- Timeout behavior: The operation will fail if the service does not respond within the specified timeout.
- Result format: The node returns both a human-readable text summary and a JSON payload of the metadata.
Troubleshooting¶
- Table not found: Verify table_name is correct and exists in the specified schema; ensure schema_name is correct or left empty to target the current user schema.
- Insufficient privileges: Confirm the Oracle user has privileges to access the specified schema and table.
- Invalid credentials: Recheck the credentials_path and that the stored credentials are valid and up-to-date.
- Network/timeout errors: Increase the timeout value or check connectivity to the Oracle service endpoint.
- Malformed inputs: Ensure table_name and schema_name are valid strings without unsupported characters.