You set the Transition properties to specify the transition process values, which are used when the target database becomes a normal database after a failure.
Note: If you are not familiar with OpenEdge Replication and its configuration, see OpenEdge Replication: User Guidebefore setting the properties.
The transition properties are divided into the following categories:
General
Start Up
After Image
Back Up
To set the OpenEdge Replication Transition properties:
1. Click Resources in the management console menu. All resources managed by your console appear in the grid frame.
2. Filter or search for the database whose Replication Transition properties you want to set.
3. Click the Edit icon. The Database details page appears.
4. In the Command and control section of the page, click Configuration. The Database Configuration page appears.
5. In the OpenEdge Replication Group Links section, click Transition. The Database Replication Configuration page opens.
6. Set the following General properties:
Database role:
reverse — The role of the database is reversed: A source database becomes a target database, and a target database becomes a source database.
normal — The role of the database becomes that of a normal database; the database is no longer enabled for replication once the transition is performed. This is the default value.
Responsibility:
primary — This is the primary database.
secondary — This is the secondary database.
Transition to agents — Transitions 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.
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, agent1,agent2.
7. Set the following Start Up properties:
Restart after transition — The database can be automatically restarted after transition is performed. When you select this option, the *-startup-arguments properties must be supplied, or the database startup will fail:
If the database role is normal, you must specify the normal-startup-arguments.
If the database role is reversed, you must specify the source-startup-arguments and the target-startup-arguments.
Source startup arguments — If the database is transitioned to a source database, these arguments are used when the database is started. The arguments are appended to the PROSERVE command (used to start the database).
In most cases, the only argument specified here should be -pf followed by a parameter file name; for example, -pf db-name.source.pf.
Because the database is a source, you must also specify the -DBService replserv argument, as an indication to the broker to start the Replication server.
Target startup arguments — If the database is transitioned to a target database, these arguments are used when the database is started. The arguments will be appended to the PROSERVE command.
In most cases, the only argument specified here should be -pf followed by a parameter file name; for example, -pf db-name.target.pf.
Because the database is a target, you must also specify the -DBService replagent -S port-number or service-name arguments, as an indication to the broker to start the Replication agent and to listen on the TCP/IP port specified with -S port-number or service-name.
Normal startup arguments — If the database is transitioned to a normal database, these arguments are used when the database is started. The arguments will be appended to the PROSERVE command.
In most cases, the only argument specified here should be -pf followed by a parameter file name; for example, -pf db-name.normal.pf.
8. Set the following After image properties:
Begin after imaging after transition — Select the option to automatically begin AI after a target-to-source database transition. After-imaging can be started for a database that has AI areas.
Automatically add after imaging extents — This property instructs the transition process to automatically add AI areas to the database if:
It is transitioned to a source database.
There are currently no AI areas for the database.
If you do not select the option, AI areas are not added to the database. If you do select the option, AI areas are automatically added to the database by using the structure file specified in the ai-structure-file property.
Structure file containing after image area definitions — The name of the structure file that contains the list of AI areas to add.
9. Set the following Back Up properties:
Backup method — Specifies the backup method performed before AI is enabled. The following values are valid:
mark — Marks the database backed up by using the rfutil db-name -C mark backedup command. Marking the database as backed up does not allow future AI extents to be used when recovering from a disaster
full off-line — Backs up the database offline by using the OpenEdge PROBKUP utility. The backup is performed in two steps. The first backup is a full backup, which is performed before AI is enabled for the database. The second backup is an incremental backup, which is performed after AI is enabled, and after the role of the database is changed.
full on-line — This backup is performed after the database is restarted, which occurs after the database has been transitioned.
Full on-line and off-line backup arguments — The arguments required for the full online and offline backups that are performed for the database. At a minimum, the target file or device must be specified in these arguments for both online and offline backups.
To avoid overwriting a backup, do not use the same target file or device for both the backup and the incremental backup.
Do not use backup validation parameters (such as -vp and -vf).
The arguments should begin with device-name.
Incremental backup arguments — The arguments required for the offline incremental backup performed after AI is enabled and the database's role is reversed.
General