Search

Release Notes

Release Notes

10.4.1
- 10.4.0

Back Next

Data Privacy Management Known Limitations (10.4.1)

Data Privacy Management Known Limitations (10.4.1)

The following table describes known limitations that were found in 10.4.1:

Bug	Description
SATS-29940	A scan job that uses a remote agent fails if the agent become unavailable instead of reassigning files to another available agent.
SATS-29938	A subject registry scan on an Azure WASB data store goes into an infinite loop.
SATS-29920	If you resume a remote agent scan job that failed because of a Data Privacy Management restart, the resumed job fails with a Duplicate pageId found error. Workaround: Restart the remote agent and then resume the job.
SATS-24409	A scan job fails if the domain and Data Privacy Management run on a backup node and the Catalog Service runs on the primary node. Workaround: Refresh the Data Privacy Management Service each time the Catalog Service is switched to a different node.
SATS-23135	Resetting the classification results of a data store deletes the connection string and schema options of the data store.
SATS-23129	If you integrate Axon Data Governance created with HTTPS with Data Privacy Management, sync jobs fail with a certificate error.
SATS-23127	A security policy violation details page displays the wrong data stores and an incorrect data store count for data stores configured for Agent scans.
SATS-23120	A Scan for Missing Domains job does not fetch results as expected. Workaround: Run an Import Catalog Resource job for the data store to import the correct results from Enterprise Data Catalog.
SATS-23117	UBA Manager fails a few minutes after it starts on a SUSE Linux Enterprise Server 12 SP3 installed on a multinode external Cloudera cluster.
SATS-23110	Repeat subject registry scans to link subjects on an unstructured data store return varied results.
SATS-23096	If you resume a scan job that fails, the resumed scan also fails. Workaround: Terminate the job and then run the job again.
SATS-21211	A scan job that uses the remote agent fails if the scan includes a custom classification policy that has unsupported OOTB domains. Workaround: For unsupported domains, create and use custom domains with the required data patterns.
SATS-20790	A scan that uses an agent calculates the confidence level based on all domains in the policy instead of only the domains included in the custom criteria.

10.4.1 Known Limitations

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.