0 / 0
Troubleshooting IBM Match 360 with Watson

Troubleshooting IBM Match 360 with Watson

Use these solutions to resolve problems that you might encounter with the IBM Match 360 with Watson service.

The following items include a description of the problem and instructions to resolve or work around the issue:

Profiling and automapping are not available

To use the data profiling and automapping features of IBM Match 360 with Watson, you must have the IBM Knowledge Catalog service and must associate a catalog with IBM Match 360. IBM Knowledge Catalog is not required for running other IBM Match 360 capabilities.

Symptoms

If IBM Knowledge Catalog is not available in your IBM Cloud Pak for Data instance or if you have not associated a catalog with your master data configuration asset, then the Profile and Automap buttons are disabled on the Mapping screen.

Resolving the problem

A IBM Knowledge Catalog administrator user must add IBM Knowledge Catalog to your IBM Cloud Pak for Data instance and associate it with your master data configuration asset.

403 - Forbidden: The service user does not have correct permissions

Service users who are not members of one of the appropriate user groups cannot access the IBM Match 360 service or the master data configuration asset. An administrator must assign the proper user groups to themselves and to other users who require access to the service.

The DataEngineer user group is required to set up a master data configuration asset.

To access IBM Match 360, a Cloud Pak for Data user must belong to one of the following user groups:

  • DataEngineer
  • DataSteward
  • PublisherUser
  • EntityViewer
User group Entity maintenance tasks Model tasks Matching tasks Jobs tasks Configuration tasks Pair analysis tasks
DataEngineer read, write, manage read, write, manage read, write, manage read, write, manage read, write, manage read, write, manage
DataSteward read, write read read, write read none read
PublisherUser read, write, manage read, write, manage none read, write none none
EntityViewer read read read read none read

Symptoms

Users who do not have an appropriate service instance role see a 403 - Forbidden error message on the master data home screen.

Resolving the problem

To resolve this issue, ensure that users belong to one of the correct user groups. For details, see Giving users access to IBM Match 360 with Watson.

After mapping a field in an asset to the record_source attribute, the asset cannot load successfully

If the record_source attribute is mapped to any field in the asset, then that field must be populated in all of the asset's records. If any record is missing a value for the field mapped to record_source, then the asset cannot successfully load.

Symptoms

After mapping an asset and attempting to load it into the system, the loading job fails with a message saying that no record source is defined.

Resolving the problem

There are two options to resolve this issue:

  • Remove the mapping for the record_source attribute. In this case, a default record source name will be automatically derived using the asset name.
  • Edit the asset to ensure that there are no blank values in the field that you want to define as the record source.

Learn more

Managing master data by using IBM Match 360 with Watson

Parent topic: Troubleshoot

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more