Fixes are available
Closed as program error.
Multi-threading Replication(MTR) transmits multiple add/deletes for the same operation. In order to duplicate this condition, we need to: 1. Create 4 instance and add sample data to all. 2. Configure a 4 way peer to peer topology between them. (Like PP replication 1-2, 2-3, 3-4, 4-1) 3. configure the topology to use MTR 4. configure the ibm-replicaconsumerconnections=5 With this configuration, we observe: A. On adds, although we have a single operation on the supplier, we see this results in multiple operations on the consumer(s) B. The same is true for deletes.
Disable Multi-threading Replication.
The APAR IO15073 enabled MTR to use "last Change Id" instead of the "last Sent Id". This caused MTR to push one change multiple number of times. MTR should use "last Sent Id". Solution: Code has been changed to use "last Sent Id" for MTR.
This problem was introduced by APAR IO15073 which is contained in the following maintenance packages: | MDVREGR 188.8.131.52-ISS-ITDS-IF0026 | | MDVREGR 184.108.40.206-ISS-ITDS-IF0025 | | MDVREGR 220.127.116.11-ISS-ITDS-FP0024 | | MDVREGR 18.104.22.168-ISS-ITDS-IF0024 | | MDVREGR 22.214.171.124-ISS-ITDS-IF0023 | | MDVREGR 126.96.36.199-ISS-ITDS-IF0022 | | MDVREGR 188.8.131.52-TIV-ITDS-IF0021 | | MDVREGR 184.108.40.206-TIV-ITDS-IF0020 | The fix for this APAR will be contained in the following maintenance packages: | interim fix | 220.127.116.11-ISS-ITDS-IF0027 |
Reported component name
IBM TIV DIR SER
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
IBM TIV DIR SER
Fixed component ID
Applicable component levels