The
schema-Lock-Action property was first introduced in
OpenEdge 10.1A.
The replication enabled source database does not need to be shutdown to change the
schema-Lock-Action parameter, the replication server (RPLS) process does.
Shutting down the Replication Server process will automatically terminate any replication agents connected to it.
- Prior to OpenEdge 11.6, the replication target database will need to be restarted before any schema changes can be applied to the source database, because the replication server and agent processes need to be running and synchronized. Since OpenEdge 11.6, agents can be restarted like replication servers with: DSRUTIL target -C restart agent.
- Unless the "agent-shutdown-action=recovery" property is in use, in which case the replication agent waits in a PRE-TRANSITION state for the replication server to re-establish connection. Once the RPLA and RPLS processes are running and synchronized, the schema update can be applied
Steps: To change the
schema-Lock-Action behaviour when applying Schema Updates to a source database
1. Shutdown the replication server process on the source:
$ dsrutil <dbname> -C terminate server
2. Update the
<dbname>.repl.properties file for the source database and add the following line to the
[server] section:
schema-Lock-Action=[force|wait]
3. Unless the "
agent-shutdown-action=recovery" property was already configured, in which case the RPLA will be in PRE-TRANSITION, restart the replication agent (RPLA) process.
Pre-OpenEdge 11.6: shutdown and restart the target database
OpenEdge 11.6+: DSRUTIL target -C restart agent
4. Restart the replication server (RPLS) process on the source:
$ dsrutil <dbname> -C restart server
Once the RPLA and RPLS processes are running and synchronized, the schema update can be applied
