Run GETMETADATA and SCANCOLUMNS actions

Search Knowledge Base by Keyword

< Back

Although GETMETADATA and SCANCOLUMNS Masking Actions could be run separately, they are always run together in Masking. Note that when doing Subsetting, you may want to run them separately.

GETMETADATA action

The GETMETADATA action retrieves the MetaData needed to retain referential integrity when masking data. This includes information regarding the catalog tables for the database that is being masked. Tables, ForeignKeys and Identity Columns in the Control spreadsheet are updated with the results.

The GETMETADATA action I/O:

Input: all the mandatory parameters are contained in C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_1_Prep.cmd script . Copy and paste this into the arguments tab and edit any mandatory parameters required. See Parameters for a full list and explanation of mandatory and optional parameters to define at this point.

Output: Tables, ForeignKeys and IdentityColumns sheets updated in the Control spreadsheet

Associated Files: C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_1_Prep.cmd

Function: This step uses a command script to get the MetaData about the database being masked from the database catalog tables.

SCANCOLUMNS action

The SCANCOLUMNS action will scan columns, populating the MaskingRules sheet of the Control Spreadsheet with the following information:

• For each Table in the Database, this action will return a list of all the columns along with some information about the data they contain, for example maximum and minimum values, number of null values.

• If parUseScanRules is set to True then the regular expressions in DataScannerRules.csv are checked against values in the database and matches are reported in columns Category1 to Category5 in the MaskingRules sheet.

• The number of rows checked against regular expressions is limited by setting the parameter parSampleSize.

The MaskingRules sheet then allows you to then define what you would like to mask using the MaskingRules sheet to do so.

SCANCOLUMNS run I/O:

Input: all the mandatory parameters are contained in C:\VIPTDM\SubsetCloneAndMaskRun\Mask\Mask_1_Prep.cmd script . Copy and paste this into the arguments tab and edit any mandatory parameters required. See Appendix for a full list and explanation of mandatory and optional parameters to define at this point.

Output: MaskingRules sheet is updated in the Control spreadsheet

Associated Files: C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_1_Prep.cmd

Function: This step uses a command script to create and populate the MaskingRules sheet for the database being masked.

Running GETMETADATA and SCANCOLUMNS Actions

Once you have defined the Input for both GETMETADATA and SCANCOLUMNS actions, run both actions together using the VIP Server Controller.  See Run Flow tab article for more information.

If you receive an error message in your output dialogue or log when running these Actions, please refer to this troubleshooting article to troubleshoot common issues. You can also run your Actions in debug mode for a more detailed log. If you still cannot find the problem, please get in touch with Curiosity by writing to info@curiosity.software