Known issues and limitations for IBM Knowledge Catalog

Assets imported with the user admin instead of cpadmin

For Cloud Pak for Data clusters with Identity Management Service enabled, the default administrator is cpadmin. However, for import, the default administrative user admin is used. Therefore, the assets are imported with the admin user instead of cpadmin.

Applies to: 5.3.0 and later

Workaround:

Before running the import, apply the following workaround:

1. Edit the config map by executing oc edit cm catalog-api-exim-cm

2. Manually update the environment variable admin_username in import-job.spec.template.spec.env from:

   - name: admin_username
   value: ${admin_username}
   

   to:

   - name: admin_username
   value: cpadmin
   

Search bar returning incorrect results

• Searching for assets when using the search bar returns unexpected results if only one or two characters are used.

  Applies to: 5.3.0 and later
  

  Workaround: Type at least three characters in the search bar.

Assessment link in email notifications doesn't work

Applies to: 5.4.0

In email notifications for data quality SLA assessment, the link to the assessment does not work due to an extra dot in the URL.

Workaround: To access the assessment, copy the link to a new browser window, remove the extra dot between ibm and com, and press Enter.

Intermittent ingestion service pod startup failure

Applies to: 5.4.0

The wdp-kg-ingestion-service pod might fail intermittenly during the startup when messaging queues are initialized and eventually time out. As a result, you might observe the following issues:

• RabbitMQ health check failures
• wdp-kg-ingestion-service pod might be temporarily unavailable affecting relationship explorer and data lineage features.

Workaround: Restart RabbitMQ pods one by one by using the following command:

oc rollout restart statefulset rabbitmq-ha -n ${PROJECT_CPD_INST_OPERANDS}

Ensure that each pod status is Healthy before restarting the next one. This action restores the cluster stability and allows the ingestion service to start again.

IBM Knowledge Catalog portal-catalog pod out of sync after upgrade

Applies to: 5.4.0

When upgrading IBM Knowledge Catalog and changing editions, the portal-catalog pod might become out of sync, leading to missing functionality that should be enabled from the upgrade.

Workaround: To enable the missing functionality, restart the portal-catalog pod after upgrading IBM Knowledge Catalog.

After installing IBM Knowledge Catalog, some pods might go into the error state and related jobs will fail

Applies to: 5.4.0

After installing IBM Knowledge Catalog, during the post-install steps when the apply-cr commands are running, pods related to kg-resync-glossary and jobs related to these pods might fail.

Workaround: To fix this issue, run the following steps:

1. Check for pods that are in the failed status:

   oc get pod -n ${PROJECT_CPD_INST_OPERANDS} | grep kg-resync-glossary-
   

2. Check the corresponding job status for those pods:

   oc get job kg-resync-glossary -n ${PROJECT_CPD_INST_OPERANDS}
   

3. Delete the kg-resync-glossary job:

   oc delete job kg-resync-glossary -n ${PROJECT_CPD_INST_OPERANDS}
   

4. Reconcile the custom resource (CR) by restarting the wkc-operator pod:

   oc delete pod ibm-cpd-wkc-operator-xxxx-xxxx -n ${PROJECT_CPD_INST_OPERATORS}
   

5. Wait for the CR reconciliation to complete and check the pods. Then, the kg-resync-glossary-xxxx pod should be completed.

Upgrading IBM Knowledge Catalog to 5.4.x might fail if you customized resources

Applies to: 5.4.0

If you customized the resources for any services in IBM Knowledge Catalog, the upgrade to version 5.4.x can fail because the configuration doesn't include a requests: section. For example, you might have added the following entry in the wkc-cr:

wkc_term_assignment_resources:
  limits:
    cpu: "2"
    memory: 4Gi

This specification can cause an error similar to the following one:

wkc_term_assignment_resources.requests.cpu : 'dict object' has no attribute 'requests'

Starting in version 5.3.0, the requests: section is required.

Workaround: Edit the wkc-cr and update resources by adding requests: sections as required. For example:

wkc_term_assignment_resources:
  limits:
    cpu: "2"
    memory: 4Gi
  requests:
    cpu: "1"
    memory: 1Gi

You can use the oc patch command to update the configuration. See the following example:

oc patch wkc wkc-cr -n ${PROJECT_CPD_INSTANCE} --type=merge -p '{"spec":{"wkc_term_assignment_resources":"limits":{"cpu": "2", "memory": "4Gi"}, {"requests":{"cpu": "1", "memory": "1Gi"}}}'

Installing IBM Knowledge Catalog or upgrading a watsonx.data intelligence 5.3.1 patch release to IBM Software Hub 5.4.0 might fail with ImagePullBackOff error

Applies to: 5.4.0

For new installations of IBM Knowledge Catalog on IBM Software Hub 5.4.0 or upgrades of a watsonx.data intelligence 5.3.1 patch release to IBM Software Hub 5.4.0, deployments might fails because IBM Knowledge Catalog Postgres instance pods, for example ikc-dp-dps-bidata-mde-mdi-postgres, or the common-service-db pods might go into ImagePullBackOff state.

Workaround: Restart the pods in question.

Assets imported from local file in the previous releases not visible in relationship explorer after upgrading IBM Knowledge Catalog to 5.4

Applies to: 5.4.0

If you imported assets from local file in the previous releases, these local file assets will not be visible in relationship explorer after you complete upgrading IBM Knowledge Catalog to 5.4.

Workaround: Resynchronize the container to which the local file assets belong. For details, see Resync of lineage metadata.

Cannot run import operations on a container package exported from another Cloud Pak for Data cluster

Applies to: 5.4.0

When you're importing a container package exported from another Cloud Pak for Data cluster, permissions on the archive must be configured so that export operations are available on the target cluster and the files within the archive can be accessed.

Workaround: To extract the export archive and modify permissions, complete the following steps:

1. Create a temporary directory:

   mkdir temp_directory
   

2. Extract the archive:

   tar -xvf cpd-exports-<export_name>-<timestamp>-data.tar --directory temp_directory
   

3. Clients must run the following command on the target cluster:

   oc get ns $CLUSTER_CPD_NAMESPACE -o=jsonpath='{@.metadata.annotations.openshift\.io/sa\.scc\.supplemental-groups}'
   

   Example output: 1000700000/10000.

4. Apply the first part of the output of the previous step (ex. 1000700000) as the new ownership on all files within the archive. Example:

   cd temp_directory/
   chown -R 1000700000:1000700000 <export_name>
   

5. Archive the fixed files with the directory. Use the same export name and timestamp as the original exported tar:

   tar -cvf cpd-exports-<export_name>-<timestamp>-data.tar <export_name>/
   

6. Upload the archive.

Data protection rules don't apply to column names that contain spaces

Applies to: 5.4.0

If a column name contains trailing or leading spaces during import, the column cannot be masked using data protection rules.

Workaround: When you're importing columns, ensure that column names don't contain trailing or leading spaces.

Preview of data from file-based connections other than IBM Cloud Object Storage is not fully supported

Applies to: 5.4.0

Connected assets from file-based connections other than IBM Cloud Object Storage do not preview correctly. Data might appear in a table with missing and/or incorrect data. There is no workaround at this time.

Scroll bar is not visible when adding assets to a project on MacOS

When adding assets to a project, the scroll bar might not be available in the Selected assets table, showing a maximum of 5 assets.

Applies to: 5.4.0

Workaround: Change the MacOS settings:

1. Click the Apple symbol in the top-left corner of your Mac's menu bar, then click System Settings.
2. Scroll down and select Appearance.
3. Under the Show scroll bars option, click the radio button next to Always.

Unexpected assets filtering results in catalogs

Applies to: 5.4.0

In catalogs, when you are searching for an asset by using Find assets field, the search might return assets whose names don't match the name string that you typed in the search field and assets that contain a keyword in a property or a related item associated with the typed name string.

Can't use Git projects with identical data assets

Applies to: 5.3.0 and later

Identical data assets don't work with Git projects.

Workaround: To publish assets from catalog to a Git project, check out a branch in the Git project first.

Mismatched column metadata information

Applies to: 5.3.0 and later

If you add columns to an existing asset, you can see the new columns in the Assets tab, but not in the Overview or Profile tabs.

Workaround: Reprofile the asset to view the changes by running a metadata import with the Discover option.

Attempt to download protected data assets is allowed

Applies to: 5.4.0

After you apply a data protection rule to an asset, for example partial redacting of columns, and attempt to download it by clicking the download icon, you get a Prepare asset for download message, which confirms the download will be available through notifications. No notification ever appears, as the asset is protected and not available for download.

Workaround:

1. Generate the viewer user token:

   res=curl -k -X GET $url/v1/preauth/validateAuth -H Cache-Control: no-cache -H Content-Type: application/json -H password:$password -H username:$user
   export token=echo $res | jq -r .accessToken
   

2. Get the evaluation decision from the asset:

   export asset_id = xxx
   export catalog_id = xxx
   export iam_id=xxx
   export account=999
   curl -k -X POST --header "Content-Type: application/json"
   --header "Accept: application/json"
   --header "Authorization: Bearer ${token}"
   -d "{
   "bss_account_id": "${account}",
   "user": "${iam_id}",
   "catalog_id": "${catalog_id}",
   "roles": ["VIEWER"],
   "operation": "read"
   }" "${url}/v3/enforcement/governed_items/${asset_id}/evaluate/Access" | jq '{ transforms: .transform_specs }' > temp_transforms.json
   

3. Transform the data:

   curl -k --request PUT
   --url "${url}/v4/enforcement-transform/${catalog_id}/${asset_id}?transform_type=full"
   --header "Authorization: Bearer $token"
   --header "Content-Type: application/json"
   -d "@temp_transforms.json"
   

   Example output:

   {
   "catalog_id": "019e2157-f501-75c6-bb1d-486a470ed8c8",
   "source_asset_id": "019e2bae-e93d-7771-b645-a5dfc35afa6d",
   "target_asset_id": "019e3d53-3719-773b-bc31-7daf64588b88",
   "target_run_status": "finished",
   "target_flow_status": "finished",
   "transformed_date": "Mon May 18 23:08:31 GMT 2026"
   }
   

   Wait several minutes. Loop step 3. until you see target_run_status: finished and get the UI notification.

The Allow duplicates option isn't available when publishing assets from projects to catalog

Applies to: 5.3.1

When you're publishing assets from a project to catalog, the Allow duplicates option isn't listed as a possible duplicate action for the selected assets.

Workaround: If you want to add assets to a catalog and allow the creation of duplicates for these assets, you must add the asset directly from the catalog as a connected asset.

Connected data asset name updates aren't reflected in the Hierarchies view

Applies to: 5.4.0

If you change the name for connected data assets, the name changes aren't reflected when you're browsing asset hierarchies and in the related asset hierarchies panels.

Assets disappear in the Hierarchies panel and crash

Applies to: 5.4.0

For database connections with more than 10,000 assets, multiple network calls are performed to retrieve asset details. The initial requests successfully fetch and display up to 10,000 assets. When a subsequent fetch is triggered to load additional assets, they're not fetched and the assets already displayed in the Hierarchies panel disappear. The following error message is displayed:

No contents
Items will appear here after they are added.

Inaccurate number of assets shown in the Hierarchies tree view

Applies to: 5.4.0

The number of assets displayed in the Hierarchies tree view is inaccurate as compared to the panel view due to the following reasons:

• Unlike other assets, assets from database connections aren't categorized by schema name and tables when they're fetched to be displayed in the Hierarchies panel view. As a result, up to 1000 assets might be fetched in one call, but only 1 schema might be fetched if the retrieved assets include assets from a database connection.
• If there's more than 1,000 assets available, they can't be fetched and displayed in the Hierarchies view.

Local assets published from project to catalog are unavailable in Hierarchies view

Applies to: 5.4.0

If a local asset is added to a project and then published from the project to a catalog, the local asset isn't available in the Hierarchies view.

Workaround: Directly add a local file asset to the catalog. The local file asset appears under the 'Local files' technology type.

Data class imported by using CSV file doesn't trigger column masking on protected assets

Applies to: 5.4.0

When you add a data class in asset column by using CSV import file to a catalog and the asset has a data protection rule applied with a data class name on the asset, the column doesn't get masked even though the data class is updated successfully after CSV import completes.

Users withouth the Access data preview permissions can profile data, edit profile, or delete profile

You can profile data, edit, or delte profile without the Access data preview permission. The Profile data, and Edit profile and Delete profile buttons on the Profile page are available for users without the necessary permission.

Applies to: 5.4.0

Error Couldn't fetch reference data values shows up on screen after publishing reference data

Applies to: 5.3.0 and later

When new values are added to a reference data set, and the reference data set is published, the following error is displayed when you try to click on the values:

Couldn't fetch reference data values. WKCBG3064E: The reference_data_value for the reference_data which has parentVersionId: <ID> and code: <code> does not exist in the glossary. WKCBG0001I: Need more help?

When the reference data set is published, the currently displayed view changes to Draft-history as marked by the green label on the top. The Draft-history view does not allow to view the reference data values.

Workaround: To view the values, click Reload artifact so that you can view the published version.

Publishing large reference data sets fails with Db2 transaction log full

Applies to: 5.3.0 and later

Publishing large reference data sets might fail with a Db2 error such as:

The transaction log for the database is full. SQLSTATE=57011

Workaround: Publish the set in smaller chunks, or increase Db2 transaction log size as described in the following steps.

1. Modify the transaction log settings with the following commands:

   db2 update db cfg for bgdb using LOGPRIMARY 5 --> default value, should not be changed
   db2 update db cfg for bgdb using LOGSECOND 251
   db2 update db cfg for bgdb using LOGFILSIZ 20480
   

2. Restart Db2.

You can calculate the required transaction log size as follows:

(LOGPRIMARY + LOGSECOND) * LOGFILSIZ

For publishing large sets, the following Db2 transaction log sizes are recommended:

• 5GB for 1M reference data values and 300K relationships
• 20GB for 1M reference data values and 1M relationships
• 80GB for 1M reference data values and 4M relationships

where the relationship count is the sum of the parent, term and value mapping relationships for reference data values in the set.

Imported data assets with assigned out-of-the-box data classes or terms have incorrect identifiers resulting in no enforcement of data protection rules

When you migrate data assets across Cloud Pak for Data instances and these assets have out-of-the-box data classes or terms assigned, the imported data assets indicate correct data class or term assignments but the assigned artifact ID is incorrect. As a result, any operations that reference the data class or term, such as data protection rules, can't be applied to the imported data assets.

Relationships between catalog assets and out-of-the-box governance artifacts cannot be migrated correctly.

Applies to: All versions of Cloud Pak for Data beginning with 4.0 and later.

Workaround: none

Can't cascade delete a Knowledge Accelerator category

Applies to: 5.3.0 and later

If you run cascade delete of a Knowledge Accelerator category, the operation might fail due to deadlocks.

Workaround: In case of deadlocks, retry cascade delete of the same root category until it's deleted.

wkc-glossary-service pod restarting when updating or creating multiple business terms

When updating or creating large numbers of business terms, the wkc-glossary-service pod is restarting due to reaching the CPU limit.

Applies to: 5.3.0 and later

Workaround: Increase the CPU limit for wkc-glossary-service as described in Manually scaling resources for services.

Column data is not redacted in accordance with the rule precedence

Applies to: 5.4.0

Some advanced partial masking options get ignored by the rule precedence mechanism when the rules resolution is executed, which results in incorrect data redaction.

Workaround: If there are multiple rules with partial masking specified, ensure that all of the partial masking columns are the same in all of these rules for the same data class.

Bulk edit does not enforce mandatory properties

Applies to: 5.3.1

• Bulk edit ignores validation of the missing mandatory values for custom properties, when these properties are restricted to a specific category. Validation recognizes and filters out only the global mandatory custom properties.As a result of the bulk edit, updates are applied to artifacts with missing values. Such edits would be blocked when editing a single artifact.

• Bulk edit validation does not recognize and filter out attributes with missing mandatory custom relationships.

Workaround: None

ZIP import with specified or empty merge method issues for mandatory custom properties and relationships

Applies to: 5.3.1

Validation of mandatory custom properties and relationships doesn't work in ZIP import, if the merge method is set to specified or empty. Artifacts with missing values for mandatory custom properties or relationships are imported without any warning.

Also, applying default values in ZIP import with those merge methods doesn't work.

Workaround: Set ZIP import merge option to all.

Applying default values for the Predefined values mandatory property type doesn't work correctly in ZIP import

Applies to: 5.3.1

Applying default values in ZIP import with all merge method doesn't work for the Predefined values mandatory custom property type. The following error is returned:

Custom property {name} contains invalid value.

As a result, the affected artifact is not imported due to the mandatory value missing.

Workaround: None

Changing artifact's primary category to a category for which mandatory custom properties apply is blocked

Applies to: 5.3.1

Moving artifact to a category for which a mandatory custom property is defined is blocked due to missing mandatory values.

Workaround: The administrator can temporarily remove the mandatory checkbox from the custom property definition. After the artifact is moved to the category, the mandatory checkbox can be re-enabled.

Providing missing mandatory custom relationship in a category, which already has other mandatory custom relationships specified, fails

Applies to: 5.3.1

When a new mandatory custom relationship definition for the Category artifact type is created, then the user is asked to fill in the missing mandatory custom relationship value before editing the category in any way. If that category already has another mandatory custom relationships assigned, providing a value for the missing one fails.

Once there is at least one mandatory custom relationship value assigned to a category, creating another mandatory custom relationship definition applicable to this category renders the category uneditable.

Workaround: All the mandatory custom relationships need to be assigned to the categories in one edit action. Alternatively, the administrator can remove the mandatory checkbox from the custom relationship definition.

Editing the Make this source a required field setting in a custom relationship definition takes a long time or times out

Applies to: 5.3.1

If a custom relationship definition is restricted by a category, editing the Make this source a required field setting might take a few minutes or time out.

Workaround: None

Workflow types not available

When custom request workflow are used and a user group is added to the list of start users (in Workflow Type > Overview > Access), it is not possible to retrieve the workflow types anymore. This leads to missing workflow types in workflow management UI and task inbox. The Start new request button is not available either.

Applies to: 5.4.0

Workaround: To solve this issue manually you can access the workflow type that contains the user group using the following URL:

https://<HOST>/gov/workflow/types/<WORKFLOW_TYPE_ID>

Go to Overview > Access and remove the user group from the list of users that can start a request.

If you don't know the workflow type ID, follow these steps to get all IDs:

1. Open a terminal and run the following command to get an authorization bearer token:

   curl -k -X POST https://<HOST>/icp4d-api/v1/authorize     -H 'cache-control: no-cache'     -H 'content-type: application/json'     -d '{"username":"<USERNAME>","password":"<PASSWORD>"}'
   

2. Run the following command to retrieve all workflow types:

   curl -X GET "https://<HOST>/v3/workflow_types" --insecure -H "accept: application/json" -H "Authorization: Bearer <TOKEN>"
   

Data quality remediation workflows are not available after installation

Applies to: 5.4.0

The data quality remediation workflow type is not available after installing IBM Knowledge Catalog 5.4.0.

Workaround: To make this workfow type available, create at least one data quality SLA.

Assets are not imported from the IBM Cognos Analytics source when the content language is set to Japanese

Applies to: 5.4.0

If you want to import metadata from the Cognos Analytics connection, where the user's content language is set to Japanese, no assets are imported. The issue occurs when you create a metadata import with the Get BI report lineage goal.

Workaround: In Cognos Analytics, change the user's content language from Japanese to English. Find the user for which you want to change the language, and change this setting in the Personal tab. Run the metadata import again.

Dummy assets get created for any file assets that come from Amazon S3 to show the complete business data lineage if Get ETL job lineage is performed

Applies to: 5.4.0

If you perform Get ETL job lineage import involving Amazon S3 connection, dummy assets get created for any file assets that come from Amazon S3 connection to show the complete business data lineage. If you perform metadata import for the same Amazon S3 connection, a duplicate asset will get created for the dummy asset created from Get ETL job lineage import and a valid asset discovered during the metadata import.

SocketTimeoutException during metadata import

Applies to: 5.4.0

During metadata import, when records from a CSV file that contains more than 30,000 rows are read, SocketTimeoutException is returned. This indicates a network issue where the connection between the client and server was unexpectedly closed.

Workaround:

1. Log in to the OpenShift console.

2. Go to Workloads > Pods > metadata-discovery-pod.

3. Go to the Environment section.

4. Search for the manta_wf_export_download environment variable and set it to true.

   Example:

   manta_wf_export_download=true
   

   By setting the variable, you're bypassing the socket timeout issue and downloading the CSV file to the local system. As a result, the CSV file can be read locally rather than over the network. After the CSV file is read, the locally downloaded file is deleted from the local system.

Business lineage shows Name not available when you're using Get BI report lineage option to import Tableau data assets

Applies to: 5.4.0

When you're using Get BI report lineage option to import Tableau data assets, business lineage for some of these assets shows Name not available instead of the actual data asset names due to extra object types that are generated by MANTA Automated Data Lineage service.

Workaround: Use technical data lineage to show the names of all data assets.

Reference assets are not marked as Removed from scope or Removed from source

Applies to: 5.4.0

If you remove an asset that was initially imported into the catalog with the associated primary and foreign keys from the metadata import scope or remove the asset from the data source, the asset itself is marked accordingly as Removed from scope or Removed from source in the catalog on reimport, but the associated PK and FK constraint assets aren't. However, when you delete the data asset from the catalog, the associated constraint assets are also deleted.

Issues with the Microsoft Excel add-in

Applies to: 5.4.0

The following issues are known for the Review metadata add-in for Microsoft Excel:

• When you open the drop-down list to assign a business term or a data class, the entry Distinctive name is displayed as the first entry. If you select this entry, it shows up in the column but does not have any effect.

• Updating or overwriting existing data in a spreadsheet is currently not supported. You must use an empty template file whenever you retrieve data.

• If another user works on the metadata enrichment results while you are editing the spreadsheet, the other user's changes can get lost when you upload the changes that you made in the spreadsheet.

• Only assigned data classes and business terms are copied from the spreadsheet columns Assigned / suggested data classes and Assigned / suggested business terms to the corresponding entry columns. If multiple business terms are assigned, each one is copied to a separate column.

Masked data might be profiled when the data source is IBM watsonx.data

Applies to: 5.4.0

If a user who is not the owner of a protected data asset in IBM watsonx.data adds such asset to a project and runs metadata enrichment on it, the masked data is sent for profiling. As a result, even the asset owner will see the profile with masked data.

Workaround: None.

In small system configurations, large metadata enrichment jobs can fail

Applies to: 5.4.0

In a system that is configured for smaller workloads, metadata enrichments that contain a lot of assets can fail with out-of-memory errors.

Workaround: To resolve the issue, you have these options:

• Increase the CPU and memory values of the profiling pod.
• Add one more replica.

Update these parameters in the wkc-cr custom resource:

• For the number of replicas: the wdp_profiling_min_replicas and wdp_profiling_max_replicas values
• For the CPU and memory values: the requests and limits entries for the wdp_profiling_resources parameter

Use the oc patch command to update the values. See the following example:

oc patch wkc wkc-cr -n ${PROJECT_CPD_INSTANCE} --type=merge -p '{"spec":{"wdp_profiling_min_replicas":"4","wdp_profiling_max_replicas":"4","wdp_profiling_resources":{"requests":{"cpu": "300m", "memory": "600Mi"}, "limits":{"cpu": "4000m", "memory": "8192Mi"}}}}'

Login form for accessing a connection in metadata enrichment might disappear

Applies to: 5.4.0

When you configure a data scope or an output table for data quality analysis in metadata enrichment with a connection that is set up with personal credentials, the form for providing the credentials disappears when you enter an incorrect password.

Workaround: To provide the correct credentials, select the same connection once more.

Rules bound to columns of the data type NUMERIC in data assets from Oracle data sources might not work

Applies to: 5.4.0

Testing or running a data quality rule that is bound to a NUMERIC column in a data asset from an Oracle data source fails if the data source is connected through a Generic JDBC connection.

Workaround: Use the native connector.

Runs of migrated data quality rules complete with warnings

Applies to: 5.4.0

When you run a data quality rule that was migrated from from InfoSphere Information Server, you might see a message like the following one:

7/2/2025 11:22:30 WARNING IIS-DSEE-TFIP-00072 <Modify_1> When checking operator: When binding output schema variable "outRec": When binding output interface field "col1" to field "col1": Implicit conversion from source type "int32" to result type "string[variable_max=10]": Converting number to string.

Such warnings are displayed when you run the DataStage job for a data quality rule that was created in InfoSphere Information Server as a Rule Stage with an output link of the type Violation details and then migrated to Cloud Pak for Data.

Workaround: You can ignore such warnings or set up a DataStage message handler to suppress such messages or to redurce their severity.

Data quality rules with duplicated variable names from multiple data quality definitions might not work

Applies to: 5.4.0

When you create a data quality rule from multiple data quality definition that reference the same variable name, the variables are internally renamed for differentiation by adding a suffix. If the renaming results in a name collision with other variables from the definitions, the data quality rule will not work.

Can't drill-down into data quality output on DataStax Enterprise

Applies to: 5.4.0

When you try to access details of data quality issues that are stored in a table on DataStax Enterprise, an error similar to the following one is displayed:

 Loading failed values failed.
 There was a problem loading the values that
 failed profiling.
 Internal Server Error Failed to get Fight info: CDICO2005E: Table could not be found:
 SQL syntax error: [IBM][Cassandra JDBC Driver)[Cassandra syntax error or access rule
 violation: base table or view not found: dgexceptions. If the table exists, then the user
 may not be authorized to see it.

This error occurs because the name of the data quality output table is created in a way that makes it case-sensitive in the underlying Cassandra database so that an uppercase name is generated. However, the SELECT statement for the lookup is constructed in a way that Cassandra search looks for a lowercase table name.

Can't create rules or SQL assets with plain-text queries for data quality output tables created before 5.3.1

Applies to: 5.4.0

For data quality rule output tables that were created in version 5.3.0 or earlier, you cannot create a new SQL-based data quality rule by using plain text queries. Also, you cannot create SQL assets (assets of the type query) from these tables.

Socket timeout errors can occur for Text2SQL API calls

Applies to: 5.3.0 and later

Socket timeout errors can occur for Text2SQL API calls if the load balancer timeout setting for watsonx.ai is too low.

Workaround: Check the load balancer configuration and make sure that the timeout is set to 600s (10m). For more information, see Changing load balancer timeout settings.

Can't work with a remote watsonx.ai instance if the system is configured to run models on CPU

Applies to: 5.4.0

If you installed IBM Knowledge Catalog or watsonx.data intelligence with the option enableModelsOn:cpu, the models used for the generative AI capabilities run locally on CPU. You cannot work with foundation models on a remote watsonx.ai instance.

For more information about setting up a connection with a remote watsonx.ai instance, see Configuring the setup for enabled gen AI capabilities in the Cloud Pak for Data documentation or Configuring the setup for enabled gen AI capabilities in the watsonx.data intelligence documentation.

Workaround: To be able to work with remote models, change your system configuration:

1. Log in to Red Hat OpenShift Container Platform as a user with sufficient permissions to complete the task.

   oc login <your_openshift_cluster_url>
   

2. Set the context to the project where IBM Knowledge Catalog or watsonx.data intelligence is deployed:

   oc project ${PROJECT_CPD_INST_OPERANDS}
   

3. Patch the semanticautomation-cr custom resource to set the installation parameter enableModelsOn to remote.

    oc patch sal semanticautomation-cr --type=merge -p '{"spec":{"enableModelsOn": "remote"}}'
   

Metadata import jobs for getting lineage might take very long to complete

Applies to: 5.4.0

If multiple lineage scans are requested at the same time, the corresponding metadata import jobs for getting lineage might take very long to complete. This is due to the fact that MANTA Automated Data Lineage workflows can't run in parallel but are executed sequentially.

Chrome security warning for Cloud Pak for Data deployments where MANTA Automated Data Lineage for IBM Cloud Pak for Data is enabled

Applies to: 5.4.0

When you try to access a Cloud Pak for Data cluster that has MANTA Automated Data Lineage for IBM Cloud Pak for Data enabled from the Chrome web browser, the message Your connection is not private is displayed and you can't proceed. This is due to MANTA Automated Data Lineage for IBM Cloud Pak for Data requiring an SSL certificate to be applied and occurs only if a self-signed certificate is used.

Workaround: To bypass the warning for the remainder of the browser session, type thisisunsafe anywhere on the window. Note that this code changes every now and then. The mentioned code is valid as of the date of general availability of Cloud Pak for Data 4.6.0. You can search the web for the updated code if necessary.

Can't Get lineage with a DB2 connection in FIPS environments

Applies to: 5.4.0

If you try to import metadata for data assets with the Get lineage scenario with a DB2 connection in a FIPS environment, the metadata import fails and the following error message is displayed.

Error creating the metadata import Metadata import creation failed due to connection validation errors. Not all connections in the metadata import passed validation. Check the log for the complete validation results.

Data Virtualization connection fails when SSL is required

Applies to: 5.4.0

When you're creating a connection to Data Virtualization and SSL is required, the metadata import lineage job will fail with an exception despite the connection validation passed.

Workaround:

1. In the project where metadata lineage import job will be executed, create a new independent Data Virtualization connection.

2. Download Data Virtualization SSL certificate from CP4D Menu > Data > Data virtualization > Menu > Configure connection > Download SSL Certificate.

3. In the project where you run MDI Lineage job, create a new non-Platform Data Virtualization connection with exactly the same details as the Data Virtualization Platform connection in CP4D Menu > Data > Connections and enter the SSL certificate contents in the SSL certificate field.

4. Use that connection to run metadata lineage import job.

Data export is incomplete due to table deduction in Query Service

Applies to: 5.4.0

When you reference a table from another system in the Query Service using the synonym of that table, then the resulting object is deduced and exported data is incomplete.

Validation shows complete for Data Virtualization metadata import jobs

Applies to: 5.4.0

When you're creating metadata import for Data Virtualization, the created job shows as if validated, regardless of user's insufficient permissions, which might result in missing metadata and errors in Manta extraction log.

Business data lineage is incomplete for the metadata imports with Get ETL job lineage or Get BI report lineage goals

Applies to: 5.4.0

In some cases, when you display business lineage between databases and ETL jobs or BI reports, some assets are missing, for example, a starting database. The data was imported by using the Get ETL job lineage or Get BI report lineage import option. Technical data lineage correctly shows all assets.

Workaround: Sometimes MANTA Automated Data Lineage cannot map the connection information from an ETL job or a BI report to the existing connections in IBM Knowledge Catalog. Follow these steps to solve the issue:

1. Open the MANTA Automated Data Lineage Admin UI:

   https://<CPD-HOSTNAME>/manta-admin-gui/
   

2. Go to Log Viewer and from the Source filter select Workflow Execution.

3. From the Workflow Execution filter, select the name of the lineage workflow that is associated with the incomplete business lineage.

4. Look for the dictionary_manta_mapping_errors issue category and expand it.

5. In each entry, expand the error and click View Log Details.

6. In each error details, look for the value of connectionString. For example, in the following error message, the value of the connectionString parameter is DQ DB2 PX.

   2023/11/14 18:40:12.186 PM [CLI] WARN - <provider-name> [Context: [DS Job 2_PARAMETER_SET] flow in project [ede1ab09-4cc9-4a3f-87fa-8ba1ea2dc0d8_lineage]]
   DICTIONARY_MANTA_MAPPING_ERRORS - NO_MAPPING_FOR_CONNECTION
   User message: Connection in use could not be automatically mapped to one of the database connections configured in MANTA.
   Technical message: There is no mapping for the connection Connection [type=DB2, connectionString=DQ DB2 PX, serverName=dataquack.ddns.net, databaseName=cpd, schemaName=null, userName=db2inst1].
   Solution: Identify the particular database technology DB2 leading to "DQ DB2 PX" and configure it as a new connection or configure the manual mapping for that database technology in MANTA Admin UI.
   Lineage impact: SINGLE_INPUT
   

7. Depending on the connection that you used for the metadata import, go to Configuration > CLI > connection server > connection server Alias Mapping, for example DB2 > DB2 Alias Mapping.

8. Select the connection used in workflow and click Full override.

9. In the Connection ID field, add the value of the connectionString parameter that you found in the error details, for example DQ DB2 PX.

10. Rerun the metadata import job in IBM Knowledge Catalog.

Hops for components and columns of components work only inside the data integration flow area of an expanded job node

Applies to: 5.4.0

When working with the lineage graph, hops for components and columns of data integration components work only inside the data integration flow area of an expanded job node and don't connect columns of nodes outside of the flow area.

Viewing large business lineage graph results in a service error

Applies to: 5.4.0

When you click the Lineage tab for a large business lineage graph, after around two minutes the following error message is displayed:

Lineage service error. An error occurred in the lineage service. Try to reload the lineage graph, and if the error persists, contact your administrator.

When you click the Lineage tab again, the lineage generation process starts, but after a while the following error is displayed:

Error 404 – Not Found

Workaround: To fix the issue, modify some of the configuration settings:

1. Increase the timeout value in nginx pod:
   1. Open the configuration YAML file by running the command oc edit zenextension wkc-base-routes -n ${PROJECT_CPD_INSTANCE}.
   2. In the section location /data/catalogs, change the value of the proxy_read_timeout variable to 10m, and save the changes.
   3. Restart the nginx pod by running the command oc rollout restart deploy/ibm-nginx -n ${PROJECT_CPD_INST_OPERANDS}
2. Allocate more memory to the service wkc-data-lineage-service, 8 GB or more, and enable horizontal scaling for the service:
   1. Update the lineage deployment with the environment variable oc edit deploy –n ${PROJECT_CPD_INSTANCE} wkc-data-lineage-service.
   2. In the containers section, change the default graph memory threshold by adding the variable lineage_memory_threshold_limit:

      - name: lineage_memory_threshold_limit
      value: "0.5"
      

   3. In the resources/limits section, increase the default memory allocation to 8192Mi:

      resources:
      limits:
         cpu: "2"
         ephemeral-storage: 1Gi
         memory: 8192Mi
      requests:
         cpu: 250m
         ephemeral-storage: 50Mi
         memory: 512Mi
      

   4. Change these settings to horizontally scale the lineage service to 2–3 instances:

      spec:
      progressDeadlineSeconds: 600
      replicas: 3
      HistoryLimit: 10
      

After you modify the configuration, try to open the Lineage tab again. If the error still occurs, change the value of the lineage_memory_threshold_limit parameter to 0.4.

The View lineage link does not redirect to the business lineage for imported assets

Applies to: 5.4.0

When you import assets to a catalog and you try to open business lineage by clicking View lineage button in the metadata import asset details, an error occurs.

Workaround: Navigate manually to the buisness lineage view. Open the catalog where you imported data, open the asset and go to the Lineage tab.

404 Error occurs when opening relationship explorer

Applies to: 5.4.0

Clicking the Explore relationships button from a catalog or project asset results in a 404 error.

Workaround: Check if your Cloud Pak for Data experience includes the IBM Knowledge Catalog any edition service. The relationship explorer is an IBM Knowledge Catalog any edition feature and can’t be accessed without it.

Primary and foreign keys are not visible for Google BigQuery assets

Applies to: 5.4.0

When selecting a Google BigQuery asset on the relationship explorer canvas, the Item metadata panel is not showing primary and foreign keys.

Some relationships are not displayed in relationship explorer after the upgrade

Applies to: 5.4.0

After upgrading from 5.1.x or 5.2.x to 5.4.0, relationships created before the upgrade are not displayed in relationship explorer. Relationships created after the upgrade display correctly.

Workaround: After the upgrade, in the cluster where Knowledge Graph is deployed, delete the sync job. Then, run the reconciliation of the Knowledge Graph custom resource.

Missing Explore relationships button for assets imported from local file

Applies to: 5.4.0

Explore relationships button for assets imported from local file is missing from 5.4 user interface.

Workaround: Open relationship explorer by using a standard asset, which is connected to the local file asset or from a business term.

Can't list business terms with the list_business_terms_by_search_term tool

Aplies to: 5.4.0

The list_business_terms_by_search_term tool is broken and fails due to a missing ctx argument. When you're trying to prompt an AI agent to list business terms for an item, you get the following response:

list_business_terms_by_search_term is currently broken on the connected MCP server and fails with a missing ctx argument, so business terms for xxx could not be retrieved with that tool.

Can't import glossary because the glossary_csv_import tool is broken and fails

Aplies to: 5.4.0

The glossary_csv_import tool is broken and fails. When you're trying to prompt an AI agent to list import glossary, an error message appears.

Duplicate actions fail if dynamic IP address are used

Applies to: 5.4.0 and later

Duplicate actions work only for connections with static IP addresses. If the connection is using a hostname with a dynamic IP address, duplicate actions might fail during connection creation.

Long names of the asset owners get truncated when hovering over their avatars

Applies to: 5.4.0 and later

When you are hovering over the avatar to show the long name of the asset owner in the side panel, the name gets truncated if it is longer than 40 characters or contains a space or a special character. If the name is longer than 40 characters, it will display correctly as long as it contains a space or '-' within the first 40 characters.

Can't add individual group members as asset members

Applies to: 5.4.0 and later

You can't add individual group members as asset members. You can add individual group members as catalog collaborators and then as asset members.

Catalog asset search doesn't support special characters

Applies to: 5.4.0 and later

If search keywords contain any of the following special characters, the search filter doesn't return the most accurate results.

Search keywords:

. + - && || ! ( ) { } [ ] ^ " ~ * ? : \

Workaround: To obtain the most accurate results, search only for the keyword after the special character. For example, instead of AUTO_DV1.SF_CUSTOMER, search for SF_CUSTOMER.

Missing default catalog and predefined data classes

Applies to: 5.4.0 and later

The automatic creation of the default catalog after installation of the IBM Knowledge Catalog service can fail. If it does, the predefined data classes are not automatically loaded and published as governance artifacts.

Workaround: Ask someone with the Administrator role to follow the instructions for creating the default catalog manually.

Special or double-byte characters in the data asset name are truncated on download

Applies to: 5.4.0 and later

When you download a data asset with a name that contains special or double-byte characters from a catalog, these characters might be truncated from the name. For example, a data asset named special chars!&@$()テニス.csv will be downloaded as specialchars!().csv.

The following character sets are supported:

• Alphanumeric characters: 0-9, a-z, A-Z
• Special characters: ! - _ . * ' ( )

Catalog UI does not update when changes are made to the asset metadata

Applies to: 5.4.0 and later

If the Catalog UI is open in a browser while an update is made to the asset metadata, the Catalog UI page will not automatically update to reflect this change. Outdated information will continue to be displayed, causing external processes to produce incorrect information.

Workaround: After the asset metadata is updated, refresh the Catalog UI page at the browser level.

A blank page might be rendered when you search for terms while manually assigning terms to a catalog asset

Applies to: 5.4.0

When you search for a term to assign to a catalog asset and change that term while the search is running, it can happen that a blank page is shown instead of any search results.

Workaround: Rerun the search.

Project assets that are added while you create segmented data assets might not be available for selection

Applies to: 5.4.0

If assets are added to the project while you are viewing the list of data assets to pick the column for segmentation, these new assets are listed, but you cannot select them.

Workaround: Cancel the creation process and start anew.

An extra path to manage catalogs in the navigation menu

Applies to: 5.4.0 and later

If you have the Manage catalogs user permission, an extra Administration > Catalogs path to manage catalogs shows up in the navigation menu.

Migrated connections aren't listed during importing from the asset browser

Applies to: 5.4.0 and later

After you migrate connections and you try to import assets from any of the migrated connections, the asset browser is empty. No connections are listed even though the connection is available in the project.

Row filter data protection rules are not available for previews of SQL query asset type

Applies to: 5.4.0

Row filter data protection rules do not work for previews of SQL query asset type. If any of the row filter rule applies to the SQL query asset in a governed catalog, the asset viewer will see an error.

Workaround: Choose one of the following methods:

• As a Data Steward, disable the row filter rule, which is applied on the SQL query asset.
• Edit the SQL query with where predicates are required at the time of creation of the asset in the project and then publish it to the catalog.

Pagination selection dropdown no longer available on the Catalogs page

Applies to: 5.4.0

Pagination selection dropdown that let you navigate to a specfic page is no longer available on the Catalogs page. You must use the left (previous page) or right (next page) arrows to get to the required page.

Can't add empty or zero-byte files to catalogs

Applies to: 5.3.0

You can't add empty or zero-byte files when you're adding local files to a catalog (on the catalog asset page, when you click Add to catalog and select Local files).

Workaround: Use the API to add empty or zero-byte files to catalogs as described in the Data and AI Common Core API documentation.

Migrating data source definitions from the Platform assets catalog will fail

Applies to: 5.3.0 and later

Data source definitions can't be migrated and attempts to migrate data source definitions will cause the migration to fail.

Workaround: There is currently no workaround for this issue.
You can migrate all other content from the Platform assets catalog without issues.

Associated connection isn't added when you add a vector index from catalog to project

Applies to: 5.3.0 and later

When you add a vector index (In memory, Elasticsearch, watsonx.data Milvus) to a project from a catalog, the associated connection isn't automatically added with it.

You can't manage more than 20 assets at the same time

Applies to: 5.3.0 and later

You can edit, delete only up to 20 assets at the same time.

Issues with publishing data quality rules

Applies to: 5.4.0 and later

When a rule has a connection for input data asset and a connection with the same name already exists in the catalog, publishing the rule does not overwrite or update the connection in the catalog, regardless of the duplicate asset handling settings in the catalog.

Workaround: Publish the connection before you publish the data quality rule.

The Profile tab isn't available if IBM Knowledge Catalog isn't installed

Applies to: 5.4 and later

If you don't have IBM Knowledge Catalog installed in your environment, you don't have access to the Profile tab and profile-related features.

Cannot use CSV to move data class between Cloud Pak for Data instances

Applies to: 5.3.0 and later

If you try to export data classes with matching method Match to reference data to CSV, and then import it into another Cloud Pak for Data instance, the import fails.

Workaround: For moving governance artifact data from one instance to another, especially data classes of this matching method, use the ZIP format export and import. For more information about the import methods, see Import methods for governance artifacts in the Cloud Pak for Data documentation.

Metadata import jobs might be stuck due to issues related to RabbitMQ

Applies to: 5.4.0 and later

If the metadata-discovery pod starts before the rabbitmq pods are up after a cluster reboot, metadata import jobs can get stuck while attempting to get the job run logs.

Workaround: To fix the issue, complete the following steps:

1. Log in to the OpenShift console by using admin credentials.
2. Go to Workloads > Pods.
3. Search for rabbitmq.
4. Delete the rabbitmq-0, rabbitmq-1, and rabbitmq-2 pods. Wait for the pods to be back up and running.
5. Search for discovery.
6. Delete the metadata-discovery pod. Wait for the pod to be back up and running.
7. Rerun the metadata import job.

Data assets might not be imported when running an ETL job lineage import for DataStage flows

Applies to: 5.4.0

When you create and run a metadata import with the goal Get ETL job lineage where the scope is determined by the Select all DataStage flows and their dependencies in the project option, data assets from the connections associated with the DataStage flows are not imported.

Workaround: Explicitly select all DataStage flows and connections when you set the scope instead of using the Select all DataStage flows and their dependencies in the project option.

When a job for importing lineage metadata hangs, it cannot be stopped

Applies to: 5.4.0

When you run a lineage metadata import and the job stops responding, the job can't be stopped.

Only files with .sql extension can be provided as manual input for metadata import from the Oracle and PostgreSQL sources

Applies to: 5.4.0

When you import metadata from the Oracle and PostgreSQL sources, only .sql files can be used as manual input. Other formats like files with .pck extension can't be used. This limitation is applicable when you install IBM Manta Data Lineage.

Assets and lineage might not be imported if many connections use the same data source

Applies to: 5.4.0

If more than one connection points to the same data source, for example to the same Db2 database, importing lineage might not be successful. Assets and lineage metadata might not be imported in such case. When you create a connection to use with metadata import, make sure that only one connection points to a selected data source.

When you import a project from a .zip file, the metadata import asset is not imported

Applies to: 5.4.0

When you import a project from a file, metadata import assets might not be imported. The issue occurs when a metadata import asset was imported to a catalog, not to a project, in the source system from which the project was exported. This catalog does not exist on the target system and the metadata import asset can't be accessed.

Workaround: After you import the project from a file, duplicate metadata import assets and add them to a catalog that exists on the target system. For details, see Duplicating a metadata import asset.

Lineage metadata cannot be imported from the Informatica PowerCenter connection

Applies to: 5.4.0

When you import lineage metadata from the Informatica PowerCenter connection, the metadata job run fails with the following message:

400 [Failed to create discovery asset. path=/GLOBAL_DESEN/DM_PES_PESSOA/WKF_BCB_PES_PESSOA_JURIDICA_DIARIA_2020/s_M_PEJ_TOTAL_03_CARREGA_ST3_2020/SQ_FF_ACFJ671_CNAE_SECUND�RIA details=ASTSV3030E: The field 'name' should contain valid unicode characters.]",
"more_info" : null

Workaround: Ensure that the encoding value is the same in the workflow file in Informatica PowerCenter and in the connection that was created in Automatic Data Lineage. If the values are different, use the one from the Informatica PowerCenter workflow file.
To solve the issue, complete these steps:

1. Open Automatic Data Lineage:

   https://<CPD-HOSTNAME>/manta-admin-gui/
   

2. Go to Connections > Data Integration Tools > IFPC and select the connection for which the metadata import failed.

3. In the Inputs section, change the value of the Workflow encoding parameter to match the value from the Informatica PowerCenter workflow file.

4. Save the connection.

5. In IBM Knowledge Catalog, reimport assets for the metadata import that failed.

Profiling in catalogs, projects, and metadata enrichment might fail for Teradata connections

Applies to: 5.4.0

If a Generic JDBC connection for Teradata exists with a driver version before 17.20.00.15, profiling in catalogs and projects, and metadata enrichment of data assets from a Teradata connection fails with an error message similar to the following one:

2023-02-15T22:51:02.744Z - cfc74cfa-db47-48e1-89f5-e64865a88304 [P] ("CUSTOMERS") - com.ibm.connect.api.SCAPIException: CDICO0100E: Connection failed: SQL error: [Teradata JDBC Driver] [TeraJDBC 16.20.00.06] [Error 1536] [SQLState HY000] Invalid connection parameter name SSLMODE (error code: DATA_IO_ERROR)

Workaround: For this workaround, users must be enabled to upload or remove JDBC drivers. For more information, see Enable users to upload, delete, or view JDBC drivers.

Complete these steps:

1. Go to Data > Connectivity > JDBC drivers and delete the existing JAR file for Teradata (terajdbc4.jar).
2. Edit the Generic JDBC connection, remove the selected JAR files, and add SSLMODE=ALLOW to the JDBC URL.

For assets from SAP OData sources, the metadata enrichment results do not show the table type

Applies to: 5.4.0

In general, metadata enrichment results show for each enriched data asset whether the asset is a table or a view. This information cannot be retrieved for data assets from SAP OData data sources and is thus not shown in the enrichment results.

Running primary key or relations analysis doesn't update the enrichment and review statuses

Applies to: 5.4.0

The enrichment status is set or updated when you run a metadata enrichment with the configured enrichment options (Profile data, Analyze quality, Assign terms). However, the enrichment status is not updated when you run a primary key analysis or a relationship analysis. In addition, the review status does not change from Reviewed to Reanalyzed after review if new keys or relationships were identified.

Republishing doesn't update primary key information in catalog

Applies to: 5.4.0

If you remove primary key information from a data asset that initially was published with the primary key information to a catalog with the duplicate-asset handling method Overwrite original assets in the metadata enrichment results and then republish the asset to that catalog, the primary key information on the catalog asset remains intact.

Workaround: Delete the existing catalog asset before you republish the data asset from the metadata enrichment results.

Rules run on columns of type timestamp with timezone fail

Applies to: 5.4.0

The data type timestamp with timezone is not supported. You can't apply data quality rules to columns with that data type.

MANTA Automated Data Lineage for IBM Cloud Pak for Data

Not all stages are displayed in technical data lineage graph for the imported DataStage ETL flow

Applies to: 5.4.0

When you import a DataStage ETL flow and view it in the technical data lineage graph, only three stages are displayed, even when four stages were imported.

Workaround: By default, three connected elements are displayed in the graph. To display more elements, click the expand icon on the last or the first displayed element on the graph.

Lineage is not reimported after the connection is reimported in Manta Admin UI

Applies to: 5.4.0

After you delete and restore connections in Manta Admin UI, reimporting the lineage metadata for these connections in Cloud Pak for Data fails. The issue occurs when the following steps are taken:

1. You create projects, connections to data sources and catalogs in Cloud Pak for Data.
2. You run metadata imports with the goal Get lineage. The imports are successful and the connections are listed in Manta Admin UI.
3. You export all connections from Manta Admin UI by using the Export all connections option.
4. You remove all connections from Manta Admin UI.
5. You import the same connections in Manta Admin UI again by using the Import connection option.
6. You rerun the metadata imports with the goal Get lineage again for the same connections but the imports are not successful and errors are displayed.

Workaround: The issue is caused by the presence of the truststore properties in the exported .json connection files. For example, for the Db2 data source, the properties are db2.extractor.truststore.path and db2.extractor.truststore.password. You can apply one of the following workarounds:

• Before you import the connection back in Manta Admin UI, manually remove these properties from the connection .json file.
• Export connections one by one, not by using the Export all connections option. When you export the connections individually, the truststore properties are not saved in the .json file.

Columns are displayed as numbers for a DataStage job lineage in the catalog

Applies to: 5.4.0

The columns for a lineage that was imported from a DataStage job are not displayed correctly in the catalog. Instead of column names, column numbers are displayed. The issue occurs when the source or target of a lineage is a CSV file.

An unnecessary edge appears when expanding data integration assets

Applies to: 5.4.0

After expanding a data integration asset and clicking Show next or Show all, the transformer nodes will have an unnecessary edge that points to themselves.