Troubleshooting IBM Match 360
Use these solutions to resolve problems that you might encounter with the IBM Match 360 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
- 403 - Forbidden: The service user does not have correct permissions
- After mapping a field in an asset to the
record_sourceattribute, the asset cannot load successfully - Bulk data load job failures and retry configuration
Profiling and automapping are not available
To use the data profiling and automapping features of IBM Match 360, 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 | none | 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.
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_sourceattribute. 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.
Bulk data load job failures and retry configuration
When you attempt to load a large amount of data into IBM Match 360 by using a bulk data load, you might encounter failures for a variety of reasons. The bulk data load process includes a built-in retry mechanism to enhance the robustness of data load operations. When a record fails to load, the retry mechanism automatically attempts the operation again until it either succeeds or the number of retries exceeds the defined limit.
Upon the failure of a bulk load operation, the IBM Match 360 initiates the retry process. The load operation is retried until either it completes successfully or the retry count surpasses the predefined limit.
Symptoms
If the number of records that fail to load exceeds the failure record threshold, the entire bulk load job is marked as failed.
The default settings for the retry mechanism are as follows:
- Retries: 3
- Failed record threshold: 20,000
If a record fails to be loaded after the maximum number of retries, the record ID gets logged in the executor pod following completion of the bulk load operation.
Parent topic: Troubleshooting