Method 2: lsepoch and chepoch method

To recover a lost packet, you can use the lsepoch command to determine the receiving replica's epoch number matrix and then use a chepoch command to reset the sending replica's epoch table.

1. At the receiving replica, use the lsepoch command to display the replica’s epoch number matrix:

   
   multitool lsepoch sanfran_hub@/vobs/dev
   For VOB replica "/vobs/dev":
   Oplog IDs for row "sanfran_hub" (@ goldengate):
    oid:7ag3b0bc.defa11d0.ba57.00:01:72:73:3c:94=950     (bangalore)
    oid:87f6265f.72d911d4.a5cd.00:01:80:c0:4b:e7=1300    (boston_hub)
    oid:0eaa6fc3.737d11d4.adbe.00:01:80:c0:4b:e7=2000    (sanfran_hub)
   

   multiutil lsepoch –clan telecomm –site sanfran_hub –family PRODA –user sfadmin –p secret sanfran_hub

   Multiutil: Estimates of the epochs from each site replayed at site ’sanfran_hub’ (@goldengate):
   BANGALORE: 950
   LEX_HUB: 1300
   SANFRAN_HUB: 2000
   

2. Use this output in a chepoch command at the sending replica:

   multitool chepoch sanfran_hub bangalore=950 boston_hub=1300 sanfran_hub=2000
   Change oplog IDs in row "sanfran_hub" [no] yes
   Epoch row successfully set.
   

   multiutil chepoch -clan telecomm -site lex_hub -family PRODA -user lexadmin -password secret bangalore=950 lex_hub=1300 sanfran_hub=2000
   Change oplog ID in row "sanfran_hub", column "bangalore" to 950 [no]yes
   Change oplog ID in row "sanfran_hub", column "lex_hub" to 1300 [no]yes Change oplog ID in row "sanfran_hub", column "sanfran_hub" to 2000 [no]yes
   Epoch row successfully set