Oracle Table Info¶
Retrieves structural information about a specific Oracle table. It loads Oracle credentials, optionally targets a schema, calls the Oracle service to fetch metadata, and returns both a human-readable summary and the raw JSON payload.
Usage¶
Use this node when you need to inspect a table’s structure before writing queries or building data workflows. Typical use: provide your Oracle credentials, the table name (and optionally the schema), then connect the outputs to logging, visualization, or downstream nodes that need table metadata (e.g., column names, data types).
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | CREDENTIALS | Path or reference to stored Oracle credentials that match the 'oracle' credential template. | |
| timeout | False | INT | Maximum time (in seconds) to wait for the Oracle service request before failing. | 60 |
| table_name | True | STRING | Name of the Oracle table to retrieve information for. | employees |
| schema_name | True | STRING | Oracle schema name that contains the table. Leave empty to use the current user’s default schema. |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Human-readable summary describing the table info request and result status. | Oracle Table Info: employees |
| json | JSON | Raw JSON metadata returned by the Oracle service (e.g., columns, data types, keys, constraints, indexes if available). | {'table': 'employees', 'schema': 'HR', 'columns': [{'name': 'EMPLOYEE_ID', 'type': 'NUMBER', 'nullable': False}, {'name': 'FIRST_NAME', 'type': 'VARCHAR2', 'nullable': True}], 'primary_key': ['EMPLOYEE_ID']} |
Important Notes¶
- This node requires Oracle credentials configured under the 'oracle' credential template.
- If schema_name is left empty, the node queries the current user’s default schema.
- Timeout controls the maximum wait for the remote Oracle service; adjust for large schemas or slower networks.
- Returned JSON structure depends on the Oracle service and database metadata; available fields may include columns, data types, nullability, primary keys, and indexes.
Troubleshooting¶
- Table not found: Verify table_name and schema_name are correct and exist in the target database.
- Insufficient privileges: Ensure the provided Oracle user has privileges to read table metadata.
- Connection or timeout errors: Increase the timeout value and confirm network access and service availability.
- Empty or partial metadata: Confirm the table exists and that the user can access system metadata views (e.g., ALL_TAB_COLUMNS).