Oracle® TimesTen In-Memory Database Reference Release 11.2.1 Part Number E13069-03 |
|
|
View PDF |
The attributes defined in this chapter are used to set up TimesTen active standby pairs that are managed by Oracle Clusterware. These clusterware attributes are set in the cluster.oracle.ini
file. The ttCWAdmin utility creates and administers active standby pairs based on the information in the cluster.oracle.ini
file.For more information about creating a high availability replication scheme, see Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. Also see "ttCWAdmin".
This section lists the clusterware attributes in these tables:
Name | Description | Default |
---|---|---|
Lists host names that may contain master data stores in an active standby pair scheme. |
None |
|
Specifies the path to be used to store action scripts for Clusterware resources |
None |
Table 5-2 Conditionally required attributes
Name | Description | Default |
---|---|---|
Command line for checking the status of an application that is managed by Clusterware |
None |
|
The name of an application that is managed by Clusterware |
None |
|
Command line for starting an application that is managed by Clusterware |
None |
|
Command line for stopping an application that is managed by Clusterware |
None |
|
The data store to which the application should link. |
None |
|
Specifies whether the active standby pair replicates cache groups. |
N |
|
A list of two virtual IP addresses that can be associated with the master data stores. |
None |
|
A list of subscriber hosts that are not part of the cluster. |
None |
|
The directory to which the active master data store is backed up. |
None |
|
List of host names that can contain subscriber data stores. |
None |
|
The list of virtual IP addresses that can be associated with subscriber data stores. |
None |
|
The name of the public network adapter that will be used for virtual IP addresses on each host. |
None |
|
The netmask of the virtual IP addresses. |
None |
Name | Description | Default |
---|---|---|
The number of seconds that the Clusterware resource that monitors the application will wait after a failure is detected before performing a failover. |
0 |
|
The number of concurrent Clusterware resource failures to tolerate before considering the active standby pair failed and recovering the backup. This attribute is ignored if the configuration does not use virtual IP addresses or if RepBackupPeriod is 0. |
2 |
|
The number of seconds the TimesTen application container waits for the action scripts to complete for a specific application. |
60 |
|
Specifies whether an active master should be automatically recovered from a backup if both master data stores fail. |
No |
|
The type of cluster. |
Active |
|
The number of seconds that Oracle Clusterware waits before migrating a data store to a new host after a failure. |
60 |
|
The number of failures of resources that Clusterware can tolerate before giving up. |
2 |
|
A list of all desired replication scheme STORE attributes on master data stores. |
None |
|
An integer representing the number of seconds for the monitoring interval of processes that monitor an active standby pair. |
5 |
|
The number of seconds between each backup of the active master data store. |
0 (disabled) |
|
A SQL construct of the active standby pair scheme. |
None |
|
The number times an incremental backup occurs between full backups. |
5 |
|
The return service attribute of the active standby pair scheme. |
None |
|
The list of all desired replication scheme STORE attributes for the subscriber data store. |
None |
|
The number of seconds that Clusterware waits for the monitor process to start before assuming a failure. |
21600 (seconds, or 6 hours) |