Known issues and limitations for Data Privacy (Masking flow)
The following known issues and limitations apply to Masking flow.
Known issues
Limitations
Known issues
Cannot use masked assets in Data Refinery
Applies to: 4.8.4 and later
For more information, see Cannot use masked assets in Data Refinery in the Known issues and limitations for IBM Knowledge Catalog topic.
Timeout during uninstallation of the Data Privacy service
Applies to: Uninstalling from 4.8.1, 4.8.2, or 4.8.3
Fixed in: 4.8.4
You might experience timeout errors during uninstallation of the Data Privacy service when you run the cpd-cli delete-cr
command.
A workaround to avoid the timeout errors before you run an uninstallation is to run the following commands:
oc patch dp dp-cr -n wkc -p '{"metadata":{"finalizers":[]}}' --type=merge
oc delete dp dp-cr
For more information, see Uninstalling Data Privacy.
Creating a job with an existing name fails without error messages
Applies to: 4.8.0, 4.8.1, and 4.8.2
Fixed in: 4.8.3
You cannot create a new job under an existing job name. For example, if you select the Mask option for a data asset from the overflow menu in the Asset page of an asset in a project, an error message fails to display that the job exists. Instead, a load icon and Create and run job button remains active.
Create a new job with a different job name that does not exist.
Cannot save changes to the Masking character
Applies to: 4.8.0, 4.8.1, and 4.8.2
Fixed in: 4.8.3
When you create a new or edit an existing data protection rule to redact columns with a data class, you might experience trouble to save the changes from the default masking character of X
to any other character.
If you click Create (or Update) to save your rule before the new character is shown under the After column in the Example data section, your change to the Masking character does not save.
A workaround to save the rule with the new masking character:
Wait about 3 seconds until the data under the After column in the Example data section is redact with the new masking character, then you can
click Create (or Update) to save the rule with the new character.
Limitations
Cannot truncate CHAR data type for Teradata in masking flow
Applies to: 4.8.0 and later
Masking flow job fail as CHAR data type cannot truncate for Teradata relational database. For example, the masking flow job fails with the following error message:
Character data truncation detected for the field <COLUMN_NAME>. The length of the value is 44 and the length of the target column is 26. (error code: INVALID_DATA)
The masked data output contains extra space padding even after the library truncates the data.
This issue is not applicable to VARCHAR data type for Teradata or CHAR data types for Db2 relational databases.
Importing data protection rules can be done only on systems with less than 10 thousand glossary artifacts
Applies to: 4.8.0, 4.8.1, 4.8.2, and 4.8.3
Fixed in: 4.8.4
Migrating data protection rules is limited to systems with less than 10,000 glossary artifacts, such as classifications, terms, and data classes. Attempting to import into a system over this limit can result in the following errors:
WDPPS9043E: Import rules failed
WDPPS9040E: Import rules failed to match export component ids
Parent topic: Masking data with Data Privacy