It is possible to have a situation where the operating system attempts to retransmit journal receivers that already exist on the target system. When this situation occurs, the remote journal function ends with an error and transmission of entries to the target system stops. This can occur in the following scenarios:
-
When performing a clear pending start of the data group while also specifying a sequence number that is earlier in the journal stream than the last processed sequence number
-
When starting a data group while specifying a database journal receiver that is earlier in the receiver chain than the last processed receiver.
For example, refer to Figure 13. Replication ended while processing journal entries in target receiver 2. Target journal receiver 1 is deleted through the configured delete management options. If the data group is started (STRDG) with a starting journal sequence number for an entry that is in journal receiver 1, the remote journal function attempts to retransmit source journal receivers 1 through 4, beginning with receiver 1. However, receiver 2 already exists on the target system. When the operating system encounters receiver 2, an error occurs and the transmission to the target system ends.
You can prevent this situation before starting that data group if you delete any target journal receivers following the receiver that will be used as the starting point. If you encounter the problem, recovery is simply to remove the target journal receivers and let remote journaling resend them. In this example, deleting target receiver 2 would prevent or resolve the problem.
Figure 13.Example of processing from an earlier journal receiver.
