The syncreplica –export command assumes successful delivery of the update packet it generates. For example, when replica boston_hub sends an update to replica sanfran_hub, the syncreplica command assumes that the operations originating at boston_hub are imported to the sanfran_hub replica. For simplicity, this example does not reflect the fact that the update packet can also contain operations that originated at other replicas in the family.
If the packet is lost, boston_hub must reset its estimate of the state of replica sanfran_hub. After this correction is made, the next update packet sent from boston_hub to sanfran_hub contains the operations sanfran_hub needs.
To reset the epoch row:
multiutil lsepoch -clan telecomm -site sanfran_hub -family PRODA -user jcole -p secret sanfran_hub Multiutil: Estimates of the epochs from each site replayed at site ’sanfran_hub’ (@goldengate): BANGALORE: 950 BOSTON_HUB: 1300 SANFRAN_HUB: 2000
multiutil chepoch -clan telecomm -site boston_hub -family PRODA -user bostonadmin -password secret sanfran_hub bangalore=950 boston_hub=1300 sanfran_hub=2000 Multiutil: Change the estimate for the epochs of site ‘bangalore’ replayed at site ‘sanfran_hub’ to 950 [yes|NO|quit]yes Multiutil: Change the estimate for the epochs of site ‘boston_hub’ replayed at site ‘sanfran_hub’ to 1300 [yes|NO|quit]yes Multiutil: Change the estimate for the epochs of site ‘sanfran_hub’ replayed at site ‘sanfran_hub’ to 2000 [yes|NO|quit]yes Multiutil: 3 epoch estimate(s) for site ‘sanfran_hub’ successfully changed; 0 failures. Multiutil: Estimates of the epochs from each site replayed at site ‘sanfran_hub’ (@goldengate): BANGALORE: 950 BOSTON_HUB: 1300 SANFRAN_HUB: 2000