Manually Determining the Incremental Transaction ID

The Jade Logical Certifier saves the highest transaction ID of the instances that have been certified on completion of a certify with no errors.

On subsequent certifies, inverses are certified only if the update transaction ID is greater than the saved highest transaction ID. If the update transaction ID of an inverse is lower than the saved value, it must have been certified previously.

Processing only changed inverses incrementally can significantly reduce the time required to check the integrity of user data.

Given that the Jade Logical Certifier must be run in single user mode, a full certify of a very a large system may not be possible due to operational requirements; for example, how long the system can be offline. To take advantage of the reduced overhead of an incremental certify, the incremental transaction ID can be set manually.

The transaction ID must be determined carefully. Using an incorrect transaction ID can result in failure to detect and report invalid inverses.

If a full certify is not possible on the production system, you should:

  1. Perform a full certify on a copy of the system.

  2. Fix any errors in the original system.

  3. Take another copy of the production system and perform another certify for verification.

  4. Repeat this process until no errors are reported in the production system.

Set the incremental transaction ID in the production system from the value of the highest transaction ID that is reported in the _logcert.log file.

Incremental certify operations can now be performed regularly either directly on the production system or on a copy of the system.

2020.0.01 and higher