|
Property name
|
Type and length
|
Description
|
|
replication-set
|
integer
|
Defines if source and target replicas transition together. Possible values are as follows:
 0 — The source and and targets do not transition together (the default).
1 — The source and and targets transition together.
See A Replication Set for details.
|
|
database-role
|
character[15]
|
The new role of the database once it is transitioned. The possible values for this property are as follows:
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
|
character[15]
|
This property must contain one of the following values:
primary — This database is the primary database.
secondary — This database is the secondary database.
This property is currently informational.
|
|
restart-after-transition
|
integer
|
The database can be automatically restarted after transition is performed.
Valid values for the property are 0 and 1. When the property is set to 1, the following *-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 andthe target-startup-arguments.
|
|
start-secondary-broker
|
integer
|
Set to 1 to automatically start a secondary broker after transition.
|
|
source-startup-arguments
|
character[256]
|
If the database is transitioned to a source database, these arguments are used when the database is started. The arguments will be 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.pfBecause the database is a source, you must also specify the following argument, which is case-sensitive, as an indication to the broker to start the replication server:-DBService replserv
|
|
target-startup-arguments
|
character[256]
|
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 following arguments (note that -DBService is case-sensitive), 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:
-DBService replagent -S port-numberservice-name
|
|
normal-startup-arguments
|
character[256]
|
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
|
|
source-secondary-broker- startup-arguments
|
character[256]
|
For secondary broker. See the description of source-startup-arguments for details.
|
|
target-secondary-broker- startup-arguments
|
character[256]
|
For secondary broker. See the description of target-startup-arguments for details.
|
|
normal-secondary-broker- startup-arguments
|
character[256]
|
For secondary broker. See the description of normal-startup-arguments for details.
|
|
auto-begin-ai
|
integer
|
Specify 1 to automatically begin AI after a target-to-source database transition. After-imaging can be started for a database that has AI areas.
|
|
transition-to-agents
|
character[256]
|
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 replication-set=1, the first agent in the transition-to-agents list is selected to become the new source.
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
|
|
auto-add-ai-areas
|
integer
|
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 the value specified for the property is 0, AI areas are not added to the database. If the value specified is 1, AI areas are automatically added to the database by using the structure file specified in the ai-structure-file property.
|
|
ai-structure-file
|
character[256]
|
Name of the structure file that contains the list of AI areas to add.
|
|
backup-method
|
character[15]
|
Specifies the backup method performed before AI is enabled. The following values are valid:
mark — Mark the database backed up by using the following command:
rfutil db-name -C mark backedup
Marking the database as backed up does not allow future AI extents to be used when recovering from a disaster.
full-offline — The database will be backed up offline by using the 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-online — An online backup is performed after the database is restarted, which occurs after the database has been transitioned.
|
|
backup-arguments
|
character[256]
|
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
|
character[256]
|
The arguments required for the offline incremental backup performed after AI is enabled and the database's role is reversed.
The arguments should begin with device-name.
|
|
recovery-backup- arguments
|
character[256]
|
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.
|