Transition properties summary
- Last Updated: January 29, 2026
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Replication transition properties are found after the [transition] directive
in the OpenEdge Replication properties (db-name.repl.properties) file. A
properties file can only have one [transition] section. The properties filemust be located in
the same directory as the db-name.db file.
database-role=reverse).The following table provides a summary of the transition properties. The table
lists each property in the repl.properties file, identifies
the property type, and provides a property description.
| Property name | Value | Description |
|---|---|---|
replication-set |
0 | 1 |
Specifies whether replication source and target
databases transition together. Possible values are:
For more information, see Transition of a Replication Set . |
database-role
|
reverse | normal |
Specifies the new replication role of the database
once it is transitioned. Possible values are:
|
responsibility
|
primary | secondary |
Specifies a user-defined responsibility to the
database. This property is currently informational. Note: Property value must be less than or equal to 14 characters long. Any value
exceeding 14 characters will cause the database log entries describing
repl.properties values to become corrupted. |
restart-after-transition
|
0 | 1 |
Specifies whether the database broker is started
following a transition. The database broker can be started after transition is performed, depending on whether you want to control database startup or have the transition process start the database. Possible values are: When
restart-after-transition=1, the
following *-startup-arguments properties must be
supplied:
Note: During online transition, database brokers stay
online throughout the duration of the transition. Online transition
changes the behavior of the
restart-after-transition property to behave as
follows:
restart-after-transition=1 and
performing online transition:
For more information, see Plan for transition and the
|
start-secondary-broker |
0 | 1 |
Specifies whether the transition process
automatically starts a secondary database broker after database has transitioned to
its new role. Possible values are:
Note: When
start-secondary-broker=1, it is required that
restart-after-transition=1. |
source-startup-arguments
|
character[256] | Specifies the database broker startup arguments to use when transition starts the database as a replication source database. During the transition, the database may be shutdown and restarted as a replication source database for achieving synchronization or to act as the coordinator in the coordination phase of the replication-set recovery transition.Additionally, when
The arguments will be appended to the
In most cases,
the only argument specified here should be -pf, followed by a
parameter file name. For example: -pf
db-name.source.pf.Note: This property must be set if restart-after-transition=1 and
transition is not an online transition..If
Although the property value is not validated in this case, not setting this property can lead to unspecified behavior causing transition failure such as failure to start the database broker or failure to establish network connection to another replication database involved in the transition. |
target-startup-arguments
|
character[256] |
Specifies the database broker startup arguments to use when the transition starts the database as a replication target database. During the transition, the database may be shutdown and restarted as a replication target database following the coordination phase of the replication-set recovery transition. Additionally, when The arguments will be appended to the PROSERVE command, which starts the database. In most cases, the only argument specified here should be
-pf,
followed by a parameter file name. For example: -pf
db-name.target.pf. Note: This property must be set if restart-after-transition=1 and
transition is not an online transition.. If
Although the property value is not validated in this case, not setting this property can lead to unspecified behavior causing transition failure, such as failure to start the database broker or failure to establish a network connection to another replication database involved in the transition. |
normal-startup-arguments
|
character[256] |
Specifies the database broker startup arguments to use when the transition process starts the database as a non-replication-enabled database. The transition process uses these arguments to start the database after it transitions to a normal database. The arguments will be appended to the PROSERVE command, which starts the database. In most cases, the only argument specified here should be -pf db-name.normal.pfNote: This property must be set
if
|
source-secondary-broker-startup-arguments |
character[256] | Specifies the database broker startup arguments to use when the transition
process starts a secondary database broker after the database has been transitioned to
a replication source database. If the database is transitioned to a source database
and The arguments will be appended to the PROSERVE command, which starts the secondary broker. In most cases, the only argument specified here should be
-pf, followed by a parameter file name. For example:
-pf
db-name.second-source.pf. Note: This property must be set if
start-secondary-broker=1. |
target-secondary-broker-startup-arguments |
character[256] | Specifies the database broker startup arguments to
use when the transition process starts a secondary database broker after the database
has been transitioned to a replication target database. If the database is
transitioned to a target database and The arguments will be appended to the PROSERVE comman, which starts the secondary broker. In most cases, the only argument specified
here should be -pf, followed by a parameter file name. For example:
-pf
db-name.second-target.pf.Note: This property must be set if
start-secondary-broker=1. |
normal-secondary-broker-startup-arguments |
character[256] | Specifies the database broker startup arguments to use when the transition
process starts a secondary database broker after the database has been transitioned to
a non-replication-enabled database. If the database is transitioned to a normal
database and The arguments will be appended to the PROSERVE command, which starts the secondary broker. In most cases, the only argument specified here should be -pf, followed by a
parameter file name. For example: -pf
db-name.second-normal.pf.Note: This property must be set if
start-secondary-broker=1 and
database-role=normal. |
auto-begin-ai
|
0 | 1 |
Specifies whether the transition process automatically enables the database for after-imaging. After imaging can be enabled for a database that has AI areas. Validation of this property occurs at the start of the transition process:
Possible values are:
|
transition-to-agents
|
agent_name[, agent_name] | Specifies an ordered list of replication agent names
for transition. At the time of transition, transition to the first agent in the list. If the first agent is not available, transition to the second agent in the list. If A valid value for this
property is any configured agent name; separate the names by a comma if you are
listing more than one. For example: Note: If both dr-transition-to-agents and transition-to-agents are defined, dr-transition-to-agents is used in recovery transition and transition-to-agents is used for failover
transition. If dr-transition-to-agents is not
defined, transition-to-agents is used for both
types of transition. |
dr-transition-to-agents
|
agent_name[, agent_name] | For Recovery Transition
only. Specifies an ordered list of replication agent names for recovery transition. Transition to the first agent in the list when a failure occurs. If the first agent is not available, transition to the second agent in the list. If A valid value for this property is any configured agent name; separate the names by a comma if you are listing more than one. For example:
Note: If both dr-transition-to-agents and transition-to-agents are defined, dr-transition-to-agents is used in recovery transition and transition-to-agents is used for failover
transition. If dr-transition-to-agents is not
defined, transition-to-agents is used for both
types of transition. |
auto-add-ai-areas
|
0 | 1 |
Specifies whether the transition process
automatically adds AI areas to the database during transition. Adding AI areas during transition is required when both of the following conditions are met:
This property is ignored if the database is already enabled for after-imaging. Possible values are:
Note: It is required that
auto-add-ai-areas=1 when auto-begin-ai=1 and the
database does not already have AI areas. In addition, when
auto-add-ai-areas=1, the ai-structure-file
property must be set to a valid ai structure filename. |
ai-structure-file
|
(.st)filename | Specifies the filename of the structure file that contains the list of AI areas to add during transition. This property is ignored ifauto-add-ai-areas=0.Note: When auto-add-ai-areas=1 and ai-structure-file is
specified, the existence of the structure file is verified. |
backup-method
|
mark | full-offline |
full-online |
Specifies the backup method performed after the
database has been transitioned to its new role. Possible values are:
Note:
During online transition, database brokers stay online throughout the duration of
the transition. Online transition changes the behavior of the
backup-method property to behave as follows:
|
backup-arguments
|
character[256] | Specifies the list of backup command line arguments
required for the full online and offline database backups that are performed by the
transition process. These parameters are required if the
At a minimum, the backup file or device must be specified in the arguments list. The arguments should begin with device-name. Do not use backup validation parameters (such as -vp and -vf). To avoid overwriting a
backup, do not use the same backup file or device in any of the
|
incremental-backup-arguments
|
character[256] | Specifies the list of backup command line arguments required for the incremental
backups that are performed after the database has been transitioned to its new role.
These parameters are required if the At a minimum, the backup file or device must be specified in the arguments list. The arguments should begin with device-name. Do not use backup validation parameters (such as -vp and -vf). To avoid overwriting a backup,
do not use the same backup file or device in any of the
|
recovery-backup-arguments
|
character[256] | Specifies the list of backup command line arguments
for the transition recovery backup that is performed at the start of the transition
process. Not setting this property will disable the transition recovery backup from being performed. At a minimum, the backup file or device must be specified in the arguments list. The arguments should begin with device-name. Do not use backup validation parameters (such as -vp and -vf). To avoid
overwriting a backup, do not use the same backup file or device in any of the
|
apply-streaming-data |
0 | 1 |
For auto-transition only.
Specifies whether the replication agent will discard or apply AI Blocks in the RSB
cache to the target database before moving forward with auto-transition. Possible values are:
Note: Replication AI Streaming is enabled by default. |
online-transition |
0 | 1 |
Specifies whether the replication source and replication target database brokers remain online during failover transition. Online transition reduces the duration of transition by allowing the database broker to remain online throughout the transition process. Any database synchronization or changes made to the database are carried out online through new transition operations. Possible values are:
|
online-manual-transition |
0 | 1 |
Specifies whether the replication target database brokers remain online during manual recovery transition. Online transition reduces the duration of transition by allowing the database broker to remain online throughout the transition process. Any database synchronization or changes made to the database are carried out online through new transition operations. Possible values are:
|
online-auto-transition |
0 | 1 |
Specifies whether the replication target database brokers remain
online during automatic recovery transition. Online transition reduces the duration of transition by allowing the database broker to remain online throughout the transition process. Any database synchronization or changes made to the database are carried out online through new transition operations. Possible values are:
|
transition-end-trigger |
0 | 1 |
Specifies whether transition will run a custom defined script at the
end transition. Possible values are:
For more information, see Transition End Trigger . |