Lineage harvester messages

A message code is shown in the lineage harvester logs when something goes wrong during the lineage harvester process. The message code indicates which part of the harvesting process was skipped or failed and provides steps to resolve it.

General lineage harvester messages

Message code	Description
MSG-LIN-1001	The current asset does not have a technical lineage yet. Only assets that are processed and stitched by Collibra Data Lineage have a Technical lineage. Look for the asset name in the navigation tree of the Browse tab pane, to see if the asset was processed. If the asset name is not shown in the navigation tree, ensure that the data source of the asset is included in the configuration file. If the asset name is shown in the navigation tree, ensure that you correctly prepared the Data Catalog physical data layer for technical lineage before you run the harvester. Specifically, the full path of each asset in Data Catalog must match the full path of the corresponding data object from your data source on the Stitching tab page. Note that in Collibra, full paths are case-sensitive. Less likely factors, such as your lineage harvester version and parsing errors can also lead to this error. For complete troubleshooting information, see Technical lineage general troubleshooting.
MSG-LIN-2501	When the `full-sync` command was entered to create a technical lineage, synchronization processing failed because a duplicate BI tool data source was added with different source IDs in the lineage harvester configuration file. To resolve this issue, complete the following steps: Enter the `list-sources` command and review the listed data sources to identify the sources IDs for the same data source. Enter the `ignore-source` command with one of the source IDs of the duplicated data source specified. Remove the configuration of the data source with the source ID that you ignored in step 2 from the lineage harvester configuration file. Enter the `full-sync` command to synchronize the technical lineage again.
MSG-LIN-3000	This is an unknown or unclassified lineage harvester error. Create a support ticket to report the issue.
MSG-LIN-3001	The lineage harvester was able to successfully connect to the Collibra Data Lineage service instances, but received HTTP client error response. If the error message contains Technical lineage is not enabled for this Catalog instance, do the following: Make sure that the URL to your Collibra Data Intelligence Platform in the `catalog` section of the lineage harvester configuration file is correct. Make sure that the username and password you use to sign in to Collibra are correct. Make sure that Collibra Data Lineage is enabled for your Collibra environment. If the error message contains Enter a valid URL, do the following: This error is caused by an invalid URL. Make sure that the URL to your Collibra Data Intelligence Platform in the `catalog` section of the lineage harvester configuration file is correct. If the issue persists, please contact Collibra support or your customer success manager.
MSG-LIN-3002	The lineage harvester was able to successfully connect to an instance of the Collibra Data Lineage service, but received an HTTP server error response. Wait a few minutes and then run the lineage harvester again. If the issue persists, please contact Collibra support or your customer success manager.
MSG-LIN-3003	The lineage harvester failed to retrieve the API key of your Collibra Data Intelligence Platform environment with Data Catalog from the Collibra Data Lineage service instances due to network connectivity issues. To resolve this issue, do the following: Check your network connectivity. Make sure you have allowed the IP addresses of all Collibra Data Lineage service instances. Check your proxy settings. Tip You can test your connectivity using the `test-connectivity` command.
MSG-LIN-3004	Unable to determine the geographic location of your Collibra Data Intelligence Platform environment. When you run the lineage harvester, it firsts connects to any available Collibra Data Lineage service instance to determine your cloud provider and geographic location of your Collibra environment. Then, the lineage harvester sends the harvested metadata to the Collibra Data Lineage service instance with the same cloud provider and geographic location. In this case, the geographic location of your Collibra environment could not be determined. If the issue persists, please contact Collibra support or your customer success manager.
MSG-LIN-3005	Connection error due to Snowflake DB Client. The lineage harvester encountered an error through the Snowflake database connector SDK. This issue is specific to the Snowflake connector, not the lineage harvester. To resolve this issue, set the `JAVA_OPTS` environment variable when you run the lineage harvester. For example, to process data from all data sources including the Snowflake data sources, take the following steps: On Windows Enter one of the following commands: If you use OpenJDK 16: `set JAVA_OPTS="-Djdk.module.illegalAccess=permit"` If you use OpenJDK 17 or higher: `set JAVA_OPTS="--add-opens=java.base/java.nio=ALL-UNNAMED"` In the same command line, enter the following command: `.\bin\lineage-harvester.bat full-sync` Note The `set` command is specific to the Windows Command Shell. The command is different if you are using PowerShell. On Linux Enter the following command: If you use OpenJDK 16: `JAVA_OPTS="-Djdk.module.illegalAccess=permit" ./bin/lineage-harvester full-sync` If you use OpenJDK 17 or higher: `JAVA_OPTS="--add-opens=java.base/java.nio=ALL-UNNAMED" ./bin/lineage-harvester full-sync`
MSG-LIN-4000	The Collibra Data Lineage service instance is unable to connect to Data Catalog. To resolve this issue, try the following: Check your network connectivity. Make sure that the URL to your Collibra Data Intelligence Platform in the `catalog` section of the lineage harvester configuration file is correct. Make sure the host names of all databases in the lineage harvester configuration file are correct. If the issue persists, please contact Collibra support or your customer success manager.
MSG-LIN-19001	Connection not defined in config file. This means that a connection to the system or server could not be established. To resolve this issue, try to ensure that you have correctly prepared your Informatica Intelligent Cloud Services <source ID> configuration file.
MSG-LIN-19002	Taskflow failed to process because of missing connection definition. A taskflow could not be processed because one of the mappings in the taskflow refers to a connection that could not be extracted from the <source ID> configuration file. To resolve this issue, try to ensure that you have correctly prepared your Informatica Intelligent Cloud Services <source ID> configuration file.
MSG-LIN-19003	Both the auth and username properties exist in the lineage harvester configuration file. Lineage harvester processing ends. The username property is deprecated. Take the following steps: Update the lineage harvester configuration file by using the auth property only. Run the lineage harvester again.

SQL scanner messages

Message code	Steps to resolve the issue
MSG-LIN-5001	This is an unexpected error. Create a support ticket to report your issue.
MSG-LIN-5002	<Object> not found, please provide DDL or object definition. The scanner for SQL statements couldn't successfully complete its analysis, due to a missing object definition. The error message includes the name of the object. This happens, for example, in a scenario whereby a SQL statement such as "CREATE TABLE TMP AS SELECT * FROM ACCOUNTS" is uploaded, but the definition for the table ACCOUNTS was not uploaded. In this case, it's impossible to extract lineage information, as the structure of the table ACCOUNTS is unknown. Therefore "*" cannot be expanded to an actual list of columns, which results in the error. To resolve this issue, if you are uploading SQL statements as files, you need to ensure that you provide DDL for all objects. You can inspect the lineage harvester output to identify the queries that are using the object in the error.

Message code

Steps to resolve the issue

MSG-LIN-5001

This is an unexpected error. Create a support ticket to report your issue.

MSG-LIN-5002

<Object> not found, please provide DDL or object definition.

The scanner for SQL statements couldn't successfully complete its analysis, due to a missing object definition. The error message includes the name of the object.

This happens, for example, in a scenario whereby a SQL statement such as "CREATE TABLE TMP AS SELECT * FROM ACCOUNTS" is uploaded, but the definition for the table ACCOUNTS was not uploaded.

In this case, it's impossible to extract lineage information, as the structure of the table ACCOUNTS is unknown. Therefore "*" cannot be expanded to an actual list of columns, which results in the error.

To resolve this issue, if you are uploading SQL statements as files, you need to ensure that you provide DDL for all objects. You can inspect the lineage harvester output to identify the queries that are using the object in the error.