Hi Smukhi,
I think we're making progress :-)
I believe SP9 would have synchronization issues when adding new peers DSAs via DXmanager. I think the best way forward would be a manual re-synch of your newly added DSAs.
If you can plan an outage and PSdata-State-10389-OKCSTAGEDS02 is your preferred master DSA. The following procedure will synchronize your data in (host: command) notation. I can provide steps to be performed without an outage (using our online dump capability) but this is simpler:
(Change paths if on Windows)
Stop newly added DSAs
* UKLDC1-PRODDS01: dxserver stop PSdata-State-10389-UKLDC1-PRODDS01
* UKLDC1-PRODDS02: dxserver stop PSdata-State-10389-UKLDC1-PRODDS02
Checkpoint all hosts (prevent updates being resent)
* Every host: dxdisp PSdata-State-10389-UKLDC1-PRODDS01
* Every host: dxdisp PSdata-State-10389-UKLDC1-PRODDS02
Copy data from master to each newly added DSA
* OKCSTAGEDS02: dxserver stop PSdata-State-10389-OKCSTAGEDS02
* OKCSTAGEDS02: copy $DXHOME/data/PSdata-State-10389-OKCSTAGEDS02.db to UKLDC1-PRODDS01: $DXHOME/data/PSdata-State-10389-UKLDC1-PRODDS01.db
* OKCSTAGEDS02: copy $DXHOME/data/PSdata-State-10389-OKCSTAGEDS02.db to UKLDC1-PRODDS02: $DXHOME/data/PSdata-State-10389-UKLDC2-PRODDS01.db
* OKCSTAGEDS02: dxserver start PSdata-State-10389-OKCSTAGEDS02
Now start new peers
* UKLDC1-PRODDS01: remove transaction log $DXHOME/data/PSdata-State-10389-UKLDC1-PRODDS01.tx (prevent old transactions be applied)
* UKLDC1-PRODDS01: dxserver start PSdata-State-10389-UKLDC1-PRODDS01
* UKLDC1-PRODDS02: remove transaction log $DXHOME/data/PSdata-State-10389-UKLDC1-PRODDS02.tx (prevent old transactions be applied)
* UKLDC1-PRODDS02: dxserver start PSdata-State-10389-UKLDC1-PRODDS02
Verify
* Verified that replication is working
If replication is still no working, please log a support ticket.
Good luck!!
Justin