Upgrade to OpenEdge
10.2B02, 11.0.0 or later, where updating VST's against the source database can be carried out offline without having to first disable Replication.
- Updating VST's remains an offline operation.
- The Target database must also be offline before updating VST's on the source database, unless "agent-shutdown-action=recovery" is configured and the target database is in PRE-TRANSITION when the source database is shutdown.
To update VST's on a source replication enabled database: 1. Stop the source database
$ proshut source -by
2. Stop the Target database unless "agent-shutdown-action=recovery" has triggered the RPLA to PRE-TRANSITION
Do not force the target shutdown with -F
$ proshut target -by
2. Update the VST's on source
$ proutil source -C updatevst
3. Start the source database (and target database if needed)
Once the RPLS and RPLA re-establish connection and synchronised, VST updates recorded in AI notes will be propagated to the Target database.
Prior to OpenEdge 10.2B02, 11.0.0, replication must be disabled before
updatevst can be run offline against the source database. The target database needs to be re-baselined once VST's have been updated on the source database.
The relevant section in the Progress Fathom Replication User’s Guide is the Utilities and Fathom Replication section, where it states:
"Many of the Progress database utilities are used to change a database. Table 4–12 lists the Progress utilities and indicates whether they are allowed to operate on a source or target database."
Table 4-12 lists
proutil -C updatevst amongst those utilities that cannot be used with replication enabled source or target databases in these versions.
