The entries represent the jobs initiated to catalog datasources and connection within the Data Integrity Suite. Each job is created for the database selected for cataloging, including jobs related to discovering available databases for cataloging purposes.
- Navigate to . This page will display a comprehensive list of catalog jobs initiated for datasources and connections.
- Optional: Use the Search box to filter jobs for easier navigation.
- In the Job column, click on a specific job name to view detailed information in the side panel.
- Click on a Connection name to access specific information about the cataloged connection.
| Column | Description |
|---|---|
| Job | Displays the name of the job. |
| Datasource | Shows the name of the datasource containing the associated connection. |
| Connection | Displays the name of the connection. |
| Status | Indicates whether a job is Completed, In progress, Stopped, Failed with number errors. |
| Started | Timestamp indicating when the job was initiated. |
| Ended | Timestamp indicating when the job concluded. |
Catalog schema vs. table jobs: Catalog job names are prefixed by either of the following:
-
Catalog schema: These jobs focus on cataloging the overall structure and metadata of databases. They discover database schema, tables, views, procedures, and functions and provide a higher-level view of the database, -
Catalog table: These jobs specifically target the cataloging of individual tables within a database. They provide granular details for selected tables.
Jobs status overview: The status of a job on the Jobs page indicates it current progress and outcome. Here are the key status types:
- Completed: Indicates that the job has been successfully completed.
- In Progress: Indicates that the job is currently running.
- Stopped: Indicates that the job has been halted before completion, either manually by the user or due to an unexpected issue.
- Failed with number errors: Indicates that the job has failed to run due to errors, requiring further investigation and resolution.
Catalog jobs may fail for various reasons. To view error details and log, click on the 'Failed with number errors' message for that job and then select Show details. Common errors include failure to authenticate to the database, inability to reach the host instance, and problems structuring the database schema. Reviewing the detailed error log assists in resolving issues to allow re-running the catalog job. It also helps administrators troubleshoot catalog access and configuration problems.