Data protection rules are not enforced in Data Virtualization
Last updated: Mar 17, 2025
Data protection rules are not enforced in Data Virtualization.
Symptoms
Data protection rules are not being enforced as expected in Data Virtualization.
Resolving the problem
-
Identify whether the object is a table or a view. If the object is a view, data masking and row filtering rules cannot be applied directly. The result sets of views are masked according to the data protection rules that apply to the objects that the view references. You can mask the identifying details from tables that are referenced in the view definition.
-
Make sure that your object is published to a governed catalog and that the published asset is subject to data protection rules. For more information, see Governing virtual data in Data Virtualization.
- If the object is a table and is published to a governed catalog, you can complete the following
steps to resolve this issue:
- Click .
- Select your catalog and click Browse Assets.
- Find the data asset or assets that represent the virtualized object. If you find multiple assets in all governed catalogs, delete the duplicates or make sure that the assigned metadata on the duplicates, such as tags, business terms, data classes, and classifications, is identical.
- Open the governed catalog data asset or assets and, from the Source field, open the linked connection.
- Edit the connection by pressing Click here to edit connection.
- Check the connection details to ensure that the Instance ID field is correctly specified and does not contain any blank spaces.
- Check that your virtual object is published to a governed catalog and that your rules apply to the corresponding virtual data asset in the catalog.
- If you find an error in the Instance ID field, re-create all data assets that you added by using the Data Virtualization connection.
Was the topic helpful?
0/1000