Known issues and limitations for IBM Manta Data Lineage

Can't Get lineage with an Oracle and Qlik Sense connections in FIPS environments

Applies to: 5.4.0

If you try to import metadata for data assets with the Get lineage scenario with an Oracle or Qlik Sense connection in a FIPS environment, the metadata import fails.

Cancelling a job that is paused has no effect

Applies to: 5.4.0

A lineage metadata import job that is paused cannot be cancelled. You can select the Cancel action from the menu of the job, but the job is not cancelled. After some time, the status changes back to paused.

Workaround: To cancel a job that is in the paused state, first resume the job, and then cancel it.

Running a new import job is possible even for a paused job

Applies to: 5.4.0

When a lineage metadata import job is in the paused state, it is possible to start a new job for the same metadata import asset.

The lineage metadata import job might remain in the paused state after it is finished

Applies to: 5.4.0

A metadata import job might get stuck in the paused state. It might happen when you pause a metadata import job, and during this time the metadata import service is restarted. After you resume the job later, the job actually finishes but the status is not changed.

The lineage import of Data Virtualization schema fails

Applies to: 5.4.0

When you import lineage metadata from Data Virtualization and you define schema as a scope, the import job fails.

Workaround: To import lineage successfully, provide a Data Virtualization certificate manually when you create the connection to Data Virtualization.

Lineage for IBM DataStage for Cloud Pak for Data Amazon S3 is generated incorrectly under IBM DataStage for Cloud Pak for Data node

Applies to: 5.4.0

When you import lineage for IBM DataStage for Cloud Pak for Data, the Amazon S3 nodes are located under IBM DataStage for Cloud Pak for Data node in the repository tree, instead of the Amazon S3 node.

Private key can't be defined for the PostgreSQL connection

Applies to: 5.4.0

When you import metadata from the PostgreSQL data source, you can authenticate only by using a username and password. You can't use a private key. Even if you provide the value, it has no effect.

Hostname in SSL certificate has to match the name provided in the connection details for PostgreSQL and Amazon RDS for PostgreSQL

Applies to: 5.4.0

The hostname provided in the Hostname in SSL certificate field is ignored for PostgreSQL and Amazon RDS for PostgreSQL. The name provided in the connection details and the one signed by SSL certificate has to be identical, otherwise the connection fails.

Can't import linkedServerConnectionsConfiguration.prm assets during metadata import from Microsoft Azure SQL Database and Microsoft SQL Server

Applies to: 5.4.0

When you import metadata from Microsoft Azure SQL Database or Microsoft SQL Server and add external inputs, the assets of linkedServerConnectionsConfiguration.prm file are not imported.

Can't import connectionsConfiguration.prm assets during metadata import from Google BigQuery

Applies to: 5.4.0

When you import metadata from Google BigQuery and add external inputs, the assets of connectionsConfiguration.prm file are not imported.