Explanation of Microsoft SSIS Connector Log Errors
Problem
We have found some errors in log files when analyzing Microsoft SSIS packages and projects with IBM Automatic Data Lineage. Could you provide detailed information as to what these errors mean?
Solution
The table below describes the error messages you can find in Automatic Data Lineage connector log files (e.g.,
ssisDataflowMasterScenario_SSIS_REPO.properties.log, etc.).
| Log message | Probable cause | Consequences |
|---|---|---|
| There is no mapping for the connection ... |
There is an SQL override in a transformation with a connection to a database whose database dictionary has not been extracted, or the connection settings are not sufficient. Verify the connection details and have Automatic Data Lineage scan this database or map the existing database to this connection via
|
The SQL override is ignored |
|
No connection string set for connection manager ...
|
The connection definition is likely defined dynamically by reading the connection definition via the property expression or variable and is typically used for file system connections. Use variable override to specify the value used for lineage purposes. See SSIS Resource Configuration for more details. |
Missing connection to source/target |
|
Could not find connection manager ... referenced in ... |
The connection manager is not available in the package or project definition. Verify that all the property files for the package are available and that the connection manager is defined within the project. | Missing connection to source/target |