Stopping Audit Tracking

To disable audit tracking

A Stop Tracking audit record is then written to the current journal. When this record is replayed on an RPS node or on an SDS secondary, tracking halts at that point in the audit trail.

This action neither forces a quietpoint nor closes the current journal.

The main purpose for this in an RPS context is to establish a journal trigger that coincides with a point-in-time on the primary database, to enable establishing a snapshot of the target database frozen at that time.