Masking job fails due to running out of Mapping values (KBA10282)

Issue

When a mapping algorithm is used, the masking job must have sufficient unique values. For example, if there are 1000 unique rows to be masked, there must be 1000 or more mapping values. Any less will generate an error message. The error message is different depending on the version of the masking engine in use.

A masking job might fail with one of the following errors when there are insufficient mapping values:

INFO  c.d.d.m.t.RunServiceImpl - [JOB_ID_1_10] 2022/05/17 12:33:11 - Delphix Algorithm.0 - TheMappingAlgorithm: Masked values: 20, Total initial mappings: 1, Total mappings created: 0
INFO  c.d.d.m.t.RunServiceImpl - [JOB_ID_1_10] 2022/05/17 12:33:11 - Delphix Algorithm.0 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : TheMappingAlgorithm: Failed to mask 80 values because the supply of unmapped values has been exhausted. Exactly 4 new mapping values are required to mask this data set.

[JOB_ID_1_10] WARNING-UNMASKED-DATA: TheMappingAlgorithm failed to mask data at table.name: null (1+ occurrences)

[JOB_ID_1_10] 2023/07/30 16:33:27 - Abort.0 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : ---------------Insufficient mapping values, please add more mapping values.[MAPPING_ID:10]

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies

Date	Release
Jul 24, 2023	13.0.0.0
Jun 21, 2023	12.0.0.0
May 25, 2023	11.0.0.0
Apr 13, 2023	10.0.0.0 | 10.0.0.1
Mar 13, 2023 | Mar 20, 2023	9.0.0.0 | 9.0.0.1
Feb 13, 2023	8.0.0.0
Jan 12, 2023	7.0.0.0
Releases Prior to 2023
Major Release	All Sub Releases
6.0	6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1, 6.0.11.0, 6.0.12.0, 6.0.12.1, 6.0.13.0, 6.0.13.1, 6.0.14.0, 6.0.15.0, 6.0.16.0, 6.0.17.0, 6.0.17.1, 6.0.17.2
5.3	5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0
5.2	5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1	5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0	5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Resolution

More mapping values will need to be added to the Mapping algorithm

In versions after 6.0.15.0, the error message will state the name of the algorithm. In the above example the algorithm is called 'TheMappingAlgorithm'.

If you need assistance in older versions, please open a support case, and a support engineer can assist.

Follow the steps here add more mappings: Importmappings.

Adding more mappings will append them to the mapping list rather than replacing the list

This action will add mappings to the mapping algorithm. Mappings can be provided in 2 different formats - PLAINTEXT or CSV.

Troubleshooting

Errors can be seen in the Info log. Search for the job ID and execution Id and look for ERROR. Example:

grep JOB_ID_1_10 info.log | grep ERROR

or 6.0.12.0 and 6.0.14.0

grep "null (1+ occurrences)"

In the user interface, you can view these errors on the Admin > Logs tab.

Alternatively, the error message can be seen in the support bundle logs.