Replication Server provides support for delaying replication by a fixed period of time.
You can use the replicate database as a failback system by keeping the replicate database a certain amount of time behind the primary database to provide a window of time during which to recover any human error committed on the primary database, such as a table or records dropped by mistake.
Use the dsi_timer parameter with alter connection or alter logical connection to specify a delay between the time transactions commit at the primary database and the time transactions commit at the standby or replicate database. Replication Server processes transactions in the outbound queue in commit order after the period of delay is over.
For example, to delay by two hours the time transactions commit at the pubs2 replicate database in the SYDNEY_DS data server, enter:
alter connection to SYDNEY_DS.pubs2 set dsi_timer to ‘02:00’
You can specify a maximum delay of 24 hours. The default delay value is 00:00 which means there is no delay
After you execute dsi_timer with alter connection or alter logical connection, suspend and resume the connection.
Replication Server does not support time zone differences
between the RepAgent at the primary database and the Replication
Server with the DSI connection where you want to execute dsi_timer.
