About the Server Side Audit Table
Published 22 March 2018
The Data Masker software requires an audit table to be present in the target schema (or in the proxy schema if the optional proxy connection is used). The audit table is always named DMO_AUDITTAB and is used to record the rules as they execute. The audit table makes it possible to determine which masking rules have been executed in the schema and also makes it possible to restart the rules if an error occurs.
The audit table can be emptied at the start of each masking set run by choosing the Truncate audit table before each run option on the Misc. Setup Tab.
The structure of the Audit Table
The Audit table has the structure shown below. Note that two Types are also created along with the audit table - these are used in the SQL code for some types of masking rule and are not, strictly speaking, related in any way to the audit table.
-- copyright (c) 2008 - Net 2000 Ltd. All rights reserved
-- The Data Masker audit table records the successful completion
-- of the masking rules. This makes restarts and auditing
DROP table DMO_AUDITTAB;
CREATE table DMO_AUDITTAB
--two types are needed for some masking rules:
Drop type DMO_RIDTYPE_TAB;
Drop type DMO_RIDTYPE;
CREATE TYPE DMO_RIDTYPE AS OBJECT (rid VARCHAR2(100));
CREATE TYPE DMO_RIDTYPE_TAB IS TABLE OF DMO_RIDTYPE;
The Oracle timestamp indicating the date and time of the rule completion.
Multiple runs of same masking set (or different masking sets) can be recorded in the audit table. This field indicates the set name and the start time of the masking set and allows the records for individual runs to be selected.
The ruleblock of the rule recorded in that audit table row.
The ruleid of the rule recorded in that audit table row.
A summary of the rule type of the rule recorded in that audit table row.
The target table or object of the rule recorded in that audit table row.
The execution time in seconds of the rule recorded in that audit table row.
A checksum for the rule. This permits the audit table entries to be checked against a known list to see if previously tested and validated rules have been updated or modified. For rule types of New Run Marker, which indicate the start of a masking set run, the checksum value is the checksum of the collection of rules and also the Data Masker options configuration.
The status of the rule. Will always be a C if the rule successfully completed.
The audit table is usually created in the target schema when the masking set is created by the New Masking Set Wizard button on the Data Masker Main form. The audit table can also be created or dropped using the tools on the options tab of the Rule Controller form. If an audit table is not present in the target schema, the Missing Audit Table Form (as shown below) will be displayed.
The Missing Audit Table Form