Oracle Table Info¶
Retrieves metadata for a specified Oracle database table. It loads provided Oracle credentials, queries the database for the table’s structure, and returns a readable summary along with a JSON payload of the details.
Usage¶
Use this node when you need to inspect a table’s structure before writing queries or building pipelines. Typical workflows include schema discovery, validating column names and data types, and preparing join conditions for downstream nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to stored Oracle database credentials configured in Salt. | salt://credentials/oracle.json |
| timeout | False | INT | Maximum time in seconds to wait for the operation before it times out. | 60 |
| table_name | True | STRING | Name of the Oracle table to retrieve information about. | employees |
| schema_name | False | STRING | Schema that contains the target table. Leave empty to use the current user’s schema. | HR |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Human-readable summary of the table information. | Oracle Table Info: employees Columns: EMPLOYEE_ID (NUMBER), FIRST_NAME (VARCHAR2), LAST_NAME (VARCHAR2), ... |
| json | JSON | Structured metadata for the table, typically including columns, data types, nullability, and other attributes. | {"table":"EMPLOYEES","columns":[{"name":"EMPLOYEE_ID","data_type":"NUMBER","nullable":false},{"name":"FIRST_NAME","data_type":"VARCHAR2","nullable":true}]} |
| html | STRING | HTML-rendered content for the results, if available. May be empty when using default formatting. | |
| xlsx | BYTES | Binary Excel data for the results, if available. May be empty when using default formatting. | |
| BYTES | Binary PDF data for the results, if available. May be empty when using default formatting. |
Important Notes¶
- Credentials required: Ensure the credentials_path points to valid Oracle credentials with permissions to read metadata.
- Schema handling: If schema_name is empty, the node queries the current user’s default schema.
- Case sensitivity: Table and schema names may be case-sensitive depending on how they were created (quoted identifiers).
- Access control: Insufficient privileges can result in empty results or errors when inspecting table metadata.
- Timeouts: Long-running or overloaded databases may require increasing the timeout.
Troubleshooting¶
- No results returned: Verify table_name and schema_name are correct and that the user has privileges to access the table.
- Authentication errors: Confirm credentials_path is correct and the stored credentials are valid.
- Timeouts: Increase the timeout value if the database is slow or under heavy load.
- Invalid table name: Check spelling and case; try fully qualifying with schema_name if not using the default schema.
- Partial metadata: Ensure the user has necessary dictionary/view access (e.g., permissions to read column metadata).