Known issues
Release 21.0.0.0
Key | Summary | Workaround |
DLPX-87283 | The Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large size data sets (i.e. more size than the configured system default size), users should manually create the dataset with the same name as the input dataset, with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset, before the job execution, to resolve the issue. |
DLPX-90170 | The job status icon displayed in the Job Monitor UI, if the execution event type of | None |
Release 20.0.0.0
Key | Summary | Workaround |
DLPX-81579 | Job monitor UI should display when a file name pattern does not have any match. | None |
DLPX-87283 | The Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large size data sets (i.e. more size than the configured system default size), users should manually create the dataset with the same name as the input dataset with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
Release 19.0.0.0
Key | Summary | Workaround |
DLPX-87283 | Unable to mask a large dataset on the mainframe storage. | In the case of in-place jobs with large size datasets, i.e. more size than the configured system default size, users should manually create the dataset with the same name as the input dataset with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
DLPX-87852 | In the Monitor job UI completed grid, sort on the 'status' field will not sort the 'success' rows with non-conforming data when the user setting, 'Nonconforming Data behavior', is set to 'Mark job as Succeeded'. | Set the Nonconforming Data behavior to Mark Job as Failed in the UI or the application setting |
Release 18.0.0.0
Key | Summary | Workaround |
DLPX-83946 | The Swagger UI does not work while a user is already logged into the Compliance Engine in another tab. | Use an incognito window for the API client. |
DLPX-87283 | The Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large sized datasets (i.e. more size than the configured system default size), users should manually create the dataset using the same name as the input dataset with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
DLPX-87852 | Sorting the | Setting the non-conforming data behavior to ‘Mark Job as Failed’ in the UI or using the application setting |
Release 17.0.0.0
Key | Summary | Workaround |
DLPX-87283 | The Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large size datasets (i.e. more size than the configured system default size), users should manually create the dataset with the same name as the input dataset with a .msk extension at the end. To resolve the issue, allocate the newly created dataset with more size than the input dataset before the job execution. |
DLPX-87707 | In very rare cases, the Compliance Engine’s storage can be filled with compliance job and inventory PDF reports. This issue might be encountered after generating hundreds of thousands of reports over multiple years. | None |
DLPX-87852 | Sorting the | Setting the Nonconforming Data behavior to Mark Job as Failed in the UI or the application setting- |
DLPX-88335 | Rapid scrolling through the inventory tables in the presence of a sluggish API response can lead to an infinite loop of API calls, resulting in the grid becoming unresponsive and stuck in a perpetual loading state. | The problem occurs exclusively during high-speed scrolling within the grid. Upon encountering this issue, triggering a manual refresh will restore the grid to the most recently successfully loaded page. However, in scenarios where users continue to scroll even after the page has become unresponsive, a grid refresh may not recover the previous state. In such instances, a complete page refresh is required. To mitigate these issues, users are encouraged to mitigate the problem by using filters to narrow down the grid data. |
DLPX-89056 | Data-level profiling with ASDD for Oracle database might not return any classification results for a column that has large number of null or empty values. | None |
DLPX-89149 | ASDD Profiling job for Db2 zOS/LUW databases might fail when profiling a table with a column that has large number of null or empty values. | Update the asdd application setting- |
Release 16.0.0.0
Key | Summary | Workaround |
DLPX-87283 | Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large size datasets (i.e. more size than the configured system default size), users should manually create the dataset with the same name as the input dataset with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
DLPX-87707 | In very rare cases, the Continuous Compliance Engine’s storage can be filled with masking job and inventory PDF reports. This issue might be encountered after generating hundreds of thousands of reports over multiple years. | None |
DLPX-87852 | Sorting the | Setting the Nonconforming Data behavior to Mark Job as Failed in the UI or the application setting- |
DLPX-88335 | Rapid scrolling through the inventory tables in the presence of a sluggish API response can lead to an infinite loop of API calls, resulting in the grid becoming unresponsive and stuck in a perpetual loading state. | The problem occurs exclusively during high-speed scrolling within the grid. Upon encountering this issue, triggering a manual refresh will restore the grid to the most recently successfully loaded page. However, in scenarios where users continue to scroll even after the page has become unresponsive, a grid refresh may not recover the previous state. In such instances, a complete page refresh is required. To mitigate these issues, users are encouraged to mitigate the problem by using filters to narrow down the grid data. |
DLPX-88658 | Masking job abruptly fails when using the 'Lat_Long Coordinates' algorithm and the data doesn’t conform to the regexes of this extended algorithm. | The error is due to an issue with the default fallback action which gets triggered when data doesn't match the regexes specified by this algorithm. So add/modify the regexes within the algorithm such that fallback action is not triggered or replace the fallback action with a custom algorithm. |
DLPX-89056 | Data-level profiling with ASDD for Oracle database might not return any classification results for a column that has large number of null or empty values. | None |
Release 15.0.0.0
Key | Summary | Workaround |
DLPX-87283 | Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of in-place jobs with large size datasets (i.e. more size than the configured system default size), users should manually create the dataset with the same name as the input dataset, with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
DLPX-87535 | Copy privileges for custom roles are not getting updated via the Continuous Compliance UI and API. | Users can duplicate this role, uncheck copy privileges, and save it via the UI. Or create a new role via the API/UI. Updating the role with API for copy privilege will also give the same issue. |
DLPX-87707 | In very rare cases, the Compliance Engine storage can be filled with masking job and inventory PDF reports. This issue might be encountered after generating hundreds of thousands of reports over multiple years. | None |
DLPX-87852 | Sorting the | The user can set to fail with non-conformant data, then sorting works fine for success and failure records. |
Release 14.0.0.0
Key | Summary | Workaround |
DLPX-87283 | Compliance Engine is unable to mask a large dataset present in Mainframe MVS storage. | In the case of In-place jobs with large size data sets i.e. more size than the configured system default size, Users should manually create the dataset with the same name as the input dataset with a .msk extension at the end. Allocate the newly created dataset with more size than the input dataset before the job execution to resolve the issue. |
Release 13.0.0.0
Key | Summary | Workaround |
DLPX-85469 | JSON file masking does not support the use of multi-column algorithms on (a) Fields in two or more different arrays (b) Fields at different levels in a single multi-dimensional array. | None |
Release 12.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-85469 | JSON file masking does not support the use of a multi-column algorithms on
| No workaround. |
Release 11.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-86196 | Segment Mapping algorithms exported using Engine Synchronization from releases 6.0.15.0 to 10.0.0.0 are not validated upon import to 11.0.0.0. | View the imported algorithm configuration in the UI and click save. |
DLPX-84875 | User with create/edit permissions is not able to create or edit the classifier | Assign domain view role to user. |
DLPX-85469 | JSON file masking does not support the use of a multi-column algorithms on
| No workaround. |
DLPX-85560 | Salesforce on the fly jobs fail with latest CDATA driver, with a license error. | No workaround. |
Release 10.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-85469 | JSON file masking does not support the use of a multi-column algorithms on
| No workaround. |
DLPX-85560 | Salesforce on the fly jobs fail with latest CDATA driver, with a license error. | No workaround. |
DLPX-84875 | Unable to create/edit the classifier/expression using the user with create/edit permission of profiler role | Assign domain view role to user. |
DLPX-85867 | Incorrect non-conforming data count across all the tables of a job, if at least one table has non-conforming data. | No workaround. |
Release 9.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-84875 | Unable to create or edit classifiers/expressions as a user with create/edit permission of the Profiler role. | Assign the domain view role to user. |
DLPX-85867 | Incorrect non-conforming data count across all the tables of a job, if at least one table has non-conforming data. | No workaround. |
Release 8.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-84141 | Masking Engine environment revisionHash changes on profile job execution even though there is no change in inventory | No workaround. |
DLPX-85867 | Incorrect non-conforming data count across all the tables of a job, if at least one table has non-conforming data. | No workaround. |
Release 7.0.0.0
Key | Summary | Workaround |
---|---|---|
DLPX-84141 | Continuous Compliance Engine environment revisionHash changes on every profile job execution even if there is no inventory change. | No workaround. |
DLPX-84525 | Inventory Page fails to load on Continuous Compliance Engines when there are more than 32,767 masked columns. | A possible workaround is to reduce the number of masked columns on the Engine to less than 32,765. |
DLPX-85867 | Incorrect non-conforming data count across all the tables of a job, if at least one table has non-conforming data. | No workaround. |
Release 6.0.17.0
No known issues in this release.
Release 6.0.16.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-82517 | Issues w/ DB2 iSeries Connector License Installation | No workaround. |
Release 6.0.15.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-81895 | Data Profiling results are not shown at Job -> Monitor page -> Results tab, in the case of delimited, fixed, and XML files. | No workaround. |
DLPX-82517 | Issues w/ DB2 iSeries Connector License Installation | No workaround. |
Release 6.0.14.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-82517 | Issues w/ DB2 iSeries Connector License Installation | No workaround. |
Release 6.0.13.0
No known issues in this release.
Release 6.0.12.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-78478 | Reidentification of CM numeric algorithm on decimal data is failing. | When the field is long enough, use the Tokenization algorithm instead of CM tokenization. |
DLPX-78659 | CM Numeric is not producing unique results for the floating-point numbers. | Use an algorithm other than CM Numeric algorithm for masking floating-point numbers stored in a numeric field. |
DLPX-79567 | Drop index fails if an index with the same name exists on the masked columns across multiple tables for MSSQL databases. | No workaround. |
DLPX-79803 | Masking with MSSQL database fails if table name contains '['. | No workaround. |
DLPX-79804 | Masking with MSSQL database fails if table name contains '\'. | No workaround. |
Release 6.0.11.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-78009 | The masking job fails when masking the primary key column if Drop Indexes are not enabled along with the Disable Constraints. | In addition to Drop Indexes, you must enable Disable Constraints when masking primary keys using built-in driver support functionality. Advanced users who are not satisfied by some limitations of the built-in Oracle support for masking primary keys may also create custom pre and post-scripts to perform both drop indexes and disable constraints operations. |
DLPX-79803 | Masking with MSSQL database fails if table name contains '['. | No workaround. |
DLPX-79804 | Masking with MSSQL database fails if table name contains '\'. | No workaround. |
Release 6.0.10.0
No known issues in this release.
Release 6.0.9.0
No known issues in this release.
Release 6.0.8.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-74882 | Masking's SFTP client no longer compatible with SolarWinds and Goanyware SFTP servers | No workaround. |
Release 6.0.7.0
No known issues in this release.
Release 6.0.6.0
No known issues in this release.
Release 6.0.5.0
No known issues in this release.
Release 6.0.4.0
No known issues in this release.
Release 6.0.3.0
No known issues in this release.
Release 6.0.2.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-69638 | Masking job created on engine 6.0.1.1 or prior is failing after the upgrade to version 6.0.2.0 or later | Masking jobs created in 6.0.1.x using a HANA JDBC driver will need to be updated to grant the following permission |
Release 6.0.1.0
No known issues in this release.
Release 6.0.0.0
Bug Number | Description | Workaround |
---|---|---|
DLPX-60397 | If a mapping algorithm is included in multiple jobs, only one job should be run at a time. If multiple jobs are run at the same time, then the mapping algorithm might contain multiple mappings to the same value or the jobs might deadlock. | Only run one job at a time. |
DLPX-61405 | Masking operation should wait for zfs delete queue to drain | Replication may send more data than expected if masking involves dropping large DBF files. |
DLPX-74882 | Masking's SFTP client no longer compatible with SolarWinds and Goanyware SFTP servers | No workaround. |
DLPX-64493 | V5 API /roles endpoint missing certain items | View and set these privileges through the GUI |
DLPX-66973 | Date format is changed after importing the environment | Either (a) use the GUI import feature and then review the imported date formats for correctness or (b) use EngineSync to export/import jobs, which will not alter the date format. |