This section provides troubleshooting guidance for technical lineage issues.
General troubleshooting resources
For complete troubleshooting information, go to the Collibra Support Portal.
For a list of technical lineage known issues, go to Technical lineage Known Issues in the Collibra Support Portal.
Technical lineage for Fivetran FAQ
This FAQ addresses common issues you may encounter when creating technical lineage for Fivetran.
Why is lineage not visible after a synchronization?
The source or destination metadata is missing from the Data Catalog.
Complete the following steps to solve the issue:
- Integrate the data sources for both source and destination systems, and verify that assets are in the Data Catalog.
- Synchronize the technical lineage for Fivetran again.
Why is only partial lineage visible?
The Destinations field on the synchronization page acts as a filter. When the field is specified, Collibra Data Lineage collects metadata only from the specified schemas or databases. Data that flows outside these boundaries is excluded from lineage.
Complete the following steps to solve the issue:
- Update the Destinations field to include the required destinations, or clear the field to extract lineage for all destinations.
- Synchronize the technical lineage for Fivetran again.
Why is the technical lineage graph incomplete or disconnected?
This issue can occur for one or more of the following reasons:
- Metadata extraction was not completed for the source or destination system.
- Source or destination assets are missing from the source configuration JSON file uploaded to the Source Configuration field in the technical lineage for Fivetran capability. The configuration defines how source and destination system assets are mapped for lineage generation.
- The Destinations field on the synchronization page is specified, and the required destination is excluded.
Complete the following steps to solve the issue:
- Integrate data sources for all required sources and destinations. Data source integration must be completed before synchronizing technical lineage.
- Validate the JSON file uploaded to the Source Configuration field.
- If the Destinations field is specified, include the required destination, or clear the field to extract lineage for all destinations.
- Synchronize the technical lineage for Fivetran again.
Why is lineage not stitched to existing assets? Nodes in the technical lineage graph are gray instead of yellow.
Technical lineage is not stitched when asset names do not match between the Fivetran configuration and the Data Catalog. Collibra Data Lineage uses the full asset name (System > Database > Schema > Table > Column) to create connections. If any part of the name differs, including case sensitivity, the lineage nodes remain disconnected.
To solve this issue:
- Compare the full asset names in the Data Catalog with the values in the source configuration JSON file, and ensure exact matches.
- Synchronize the technical lineage for Fivetran again.
For more information, go to Automatic stitching for technical lineage.