Skip to main content

Algorithm: Data Cleansing (KBA1662)




KBA# 1662

At a Glance

Description: This algorithm is used to Cleanse Data (or standardize in Data Quality terms). Even if rare, it can be used to obfuscate the data. The algorithm uses lookup values to change a set of terms to another (standard) set of terms. This algorithm is lightweight and fast.

The KBA is for Data Cleanse v1.
New Version: The Data Cleanse algorithm has been updated and the latest release is available from Delphix Continuous Compliance Engine version
  Type RI1 1:12
Data Cleansing Lookup Yes  Yes

1 Referential Integrity - The cleaned value will be the same between job executions as well as tables.
2 1:1 Mapping - The cleaned value will be mapped uniquely to the input value.

Uses UTF-8 (some limitations if the code page is not supported - DLPX-43116).
Lookup Pool: For best performance - up to 500,000 values.
Notes: Notes:
  • Will only match a full string in a field (not a word or words within a string).
  • Sensitive to white space (data not trimmed). 
  • Case Sensitive (Value and VALUE are different).
  • A large pool size (number of rows in the lookup file) will take a long time to load. 
Create/Modify: Creation: Lookup values are loaded when the algorithm is created from a text file.

Modify: The description and the list of lookup values can be changed. 
More info: Data Cleanse v2 documentation:

More information about this can be found in the Masking Docs:


The Data Cleansing Algorithm is a simple algorithm that uses a lookup file with mappings of original/cleansed value pairs. These value pairs are imported when you create or modify the Data Cleansing algorithm.

This algorithm has been upgraded to the New Algorithm Framework as of Delphix Continuous Compliance Engine version

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases





Creating and Modifying  

The algorithms are accessed from the tab Settings and under the submenu Algorithm. Once created, the algorithm can be modified:

  • To create click Add Algorithm at the top of the page.
  • To modify click the Edit icon next to each algorithm.

User Interface 

When creating (and modifying) the algorithm, the following popup will display:

UI - Algorithm - Data Cleansing Algorithm Docs.png

  1. Algorithm Properties:
    • Algorithm Name.
    • Description.
  2. Lookup Details:
    • Lookup File Name.
    • Delimiter - the character used in the file to separate mappings of original/cleansed value pairs.


Editable parameters are:

  • Description
  • List of lookup values


To change any other parameter the algorithm needs to be deleted and then recreated. 


Pool Size and Performance 

The pool size (number of rows in the lookup file) affects both the algorithm creation time and the load time when the job starts up. An estimate is that the increase in load time is 10 to 3 - increase the number of values by 3 times and it will take 10 times longer to load. On an average system, it will take 4 min to load 500,000 values. Loading 1,500,00 will take 40 min. 

The graph below shows the load values in milliseconds (y) and in the number of values loaded on the horizontal axis (x). 


Memory Requirements 

The ingested values are loaded into RAM when the masking job starts. For large pool sizes, it might be required to increase the Min/Max Memory settings in the Job Configuration. 

White Space Workaround

The Data Cleansing Algorithm is sensitive to white spaces and case. This can be a problem if the data being masking is stored in a CHAR (or NCHAR) column as these values will be padded. 

To resolve white space issues on a database, use this workaround:

  1. Open and edit the Rule Set
  2. Add a Custom SQL statement with the following amendment to the column that needs to be trimmed:

To   : LTRIM(RTRIM((maskCol)) as maskCol



SELECT ID, LTRIM(RTRIM((maskCol)) as maskCol from myTable;

Case Sensitivity Workaround 

To resolve case sensitivity on a database, use this workaround:

  1. Open and edit the Rule Set
  2. Add a Custom SQL statement with the following amendment to the column with the case issue:

To   : UPPER((maskCol)) as maskCol



SELECT ID, UPPER(maskCol) as maskCol from myTable;

Non-Standard Code Page 

The data to be masked might be encoded and contain characters that are not converted correctly to UTF-8. The masked data is masked as????. This issue is resolved in version 5.1.


Below is an example of cleansed results using varchar. Note the case and white space sensitivity. 

Text file with search lookup values:


Masking (cleansed) result:

| ID  | Orig   | Cleansed |
| 1   | tst    | test     |
| 2   | Tst    | Test     |
| 3   | TST    | TEST     |
| 4   | tsT    | tsT      |  << Not cleansed >> no search value match
| 5   | TST    | TST      |  << Not cleansed >> trailing white space