This section describes some options for reconfiguring the save intervals for a logical replicate database. A save interval for a connection specifies how long messages will be retained in a stable queue before they can be deleted. If you set up a warm standby application through the usual procedure, the default settings will work correctly.
You can use the configure logical connection command to configure the DSI queue save interval and the materialization queue save interval for the logical connection.
Refer to Chapter 3, “Replication Server Commands,” in the Replication Server Reference Manual for the syntax of configure logical connection command.
WARNING! The DSI queue save interval and the materialization queue save interval settings for a logical connection should be reset only under serious conditions stemming from a lack of stable queue space. Resetting these save intervals (from strict to a given number of minutes) may lead to message loss at the standby database. Replication Server cannot detect this type of loss; you have to verify the integrity of the standby database yourself.
By default, the DSI queue save interval for the logical connection is set to 'strict' when you create a standby database. This causes Replication Server to retain DSI queue messages until they are delivered to the standby database. If you must change the DSI queue save interval for the logical connection, use the configure logical connection command.
For example, to force a replicate Replication Server to save messages destined for its logical replicate data server LDS for one hour (sixty minutes), enter the following command:
configure logical connection to LDS.logical_pubs2 set save_interval to '60'
To reset this save interval back to 'strict', enter:
configure logical connection to LDS.logical_pubs2 set save_interval to 'strict'
The materialization queue save interval for the logical connection is set to 'strict' by default when you create a subscription. This causes Replication Server to retain materialization queue messages until they are delivered to the standby database. If you must change the materialization queue save interval for the logical connection, use the configure logical connection command.
For example, to force a replicate Replication Server to save messages in the materialization queue for its logical replicate data server LDS for one hour (sixty minutes), enter the following command:
configure logical connection to LDS.logical_pubs2 set materialization_save_interval to '60'
To reset this save interval back to 'strict', enter:
configure logical connection to LDS.logical_pubs2 set materialization_save_interval to 'strict'
