STOP AFTER time
STOP AFTER time ON stopdate
STOP AFTER time ON + days
The STOP AFTER parameter provides an “effective time” for Snapshot to stop requesting updates. In other words, Snapshot requests updates until it encounters the QPT (quiet point) after the time you specify. By default, STOP AFTER does not appear in the parameter file. If you want to use it, you must type it in the Snapshot parameter file.
Note: This parameter only works with online clones. Since an offline clone prevents any updating, there can be no audit to read to bring the database to a particular time. If you configure the STOP AFTER parameter and specify an offline clone, Snapshot ignores the STOP AFTER parameter and reports the stop point as the following:
Stop Point = (ignored for offline clone)
Time in the STOP command refers to the time the update occurred on the primary system, not the current time of day.
The “+ days” is in relation to the Snapshot start date. For example, when Snapshot starts, it calculates an audit location STOP date based on the current date plus the “+ days” parameter. Snapshot stops when it reaches an audit location from the primary system with this calculated date.
If you enter the following:
STOP AFTER 11:30 PM
Snapshot will request updates until it sees the QPT after 11:30 PM, even if Snapshot starts at 10:05 PM and completes the extract at 10:45 PM. The data in the Snapshot data files will match the database as of 11:30 PM.