How to prevent or reduce chances of queue corruption? (4300927)

Shareplex is designed to recover from many types of failures but the power failure or system panic can likely result in queue corruption. This may stall the replication till the corrupted portion of queues is removed or the queues are entirely removed. This will result in loss of data and consequent out of sync on target. The reason for corruption is that Shareplex queues are partly cached in memory for performance reasons. In the event of power failure, some messages may not be fully written to disk, resulting in queue corruption. The parameter SP_QUE_SYNC controls whether the queue data is written to disk at all times or is partly cached in memory. In case of former there will be no data loss but would result in overhead and slow posting. The following description applies to Shareplex 5.1 or higher. In earlier versions, the parameter can be set to 1 (on) or 0 (off).