How priority auditing determines what objects to select - assure_mimix

How priority auditing determines what objects to select - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software

Version

10.0

Language

English

Product name

Assure MIMIX

Title

Assure MIMIX Operations Guide

2023

First publish date

1999

Last updated

2024-03-12

Published on

2024-03-12T11:06:36.794496

MIMIX determines the auditing priority of each replicated object based on its most recent change, most recent audit, and the frequency specified for auditing priority categories. At any time, every replicated object falls within one of several predetermined categories. Objects in each category are eligible for selection according to the frequency assigned to their category.

Every day, MIMIX automatically submits requests to run a prioritized audit periodically within the time range specified in its schedule. Each time a prioritized audit starts, it selects only the objects eligible in each category.

Table 1. Priority auditing categories
Category	Description	Eligibility Frequency
Objects not equal	Objects for which MIMIX detected differences since the start of the most recent audit are in this category. This includes: Objects that had any value other than EQ in their most recent audit, including those with differences that were automatically resolved. Objects for which target system differences were detected by target journal inspection or by virtual switch processing. Objects with problems detected by database replication that are being tracked for automatic recovery. When MIMIX is configured for DLY commit mode, objects for which commit rollback entries still exist in the journal when those objects were part of a commit cycle that MIMIX automatically processed (by a commit operation) to clear a deadlock condition.	Objects in this category have the highest priority and are always selected.
New objects	A new object is one that has not been audited since it was created.	Objects in these categories are eligible for selection according to the category frequency specified in the Priority audit policy.
Changed objects	A changed object is one that has been modified since the last time it was audited.
Unchanged objects	An unchanged object is one that has not been modified since the last time it was audited.
Audited with no differences	An object with no differences is one that has not been modified since the last time it was audited and has been successfully audited with no changes on at least three consecutive audit runs. Objects remain in this category until a change occurs.
The #FILDTA audit always selects all members of a file for which auditing is less than 100 percent complete. The occurs in all of the above object selection categories.

Initially, the objects selected by a prioritized audit may be nearly the same as those selected by a scheduled audit. However, over time the number of objects selected by a prioritized object stabilizes to a subset of those selected by a scheduled audit.

When both scheduled and priority audits are allowed for the same rule and data group, MIMIX may not start a prioritized audit if the scheduled audit will start in the near future.