Shareplex transaction delay in posting. (4296751)

How to delay the Shareplex replication by a few hours/minutes before posting it on the target.

There is a parameter that can be set on the target to delay post from posting the messages. The details can be obtained from the Shareplex Reference Guide as well. Please see the details below:

SP_OPO_POSTER_DELAY
This parameter controls the amount of time that the Post process delays before it posts records to the target instance. Normally, Post applies the changes immediately to minimize latency between the source and target systems, but you can delay posting for up to 5 days (7200 minutes).

Delaying posting helps protect the data against accidental loss caused by unwanted deletes or object drops on the source system. The delay gives you enough time to detect the mistake and retrieve the data from the target instance before the mistake is replicated. Running "what-if" analyses is another reason you could change the default of this parameter. Having the target database behind in time enables you to validate predictive modeling compared to the real thing. The delay caused by SP_OPO_POSTER_DELAY is measured from the time the message first appears in the redo logs. Things to consider when using this parameter include the following:

1. Make certain that there is enough disk space for the data to collect in the post queue for the designated time interval until it is applied to the database.

2. To determine when to start posting based on the parameter's setting, SharePlex compares the target system's current timestamp with the time that a record enters the redo log on the source system. Those machines could be in different locations, perhaps
thousands of miles from each other. Consider any difference between time zones, and add that to the delay time. For example, there is an 18-hour time difference between Los Angeles, California, U.S.A., and Sydney, Australia. To delay posting for five hours, you would need to set SP_OPO_POSTER_DELAY to 23 hours (1380 minutes) to account for the desired five-hour delay plus the 18-hour time difference. Also consider whether or not a location observes Daylight Savings Time, which could change the time difference between two locations. The way that Daylight Savings Time is observed varies among, and even within, nations that use it.

3. Do not use this parameter going back in time, for example when a source system is in Sydney and a target system is in Los Angeles. To SharePlex, this as a negative time difference when the time stamps on each system are compared. For example, 2:00 in the morning on April 2 in Sydney is 8:00 in the morning on April 1 in Los Angeles. The parameter does not accommodate settings of less than 0.
Default: 0 minutes
Range of valid values: 0 to 7200 minutes
Takes effect: immediately

sp_ctrl>set param SP_OPO_POSTER_DELAY 60
You can verify that it is set with this command:
sp_ctrl>list param all post