Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle TimesTen In-Memory Database Guide |
Installing and Configuring HA for TimesTen
Overview of Installing and Configuring HA for TimesTen
Planning the HA for TimesTen Installation and Configuration
Planning the Resource Group Topology for HA for TimesTen
TimesTen and Solaris Containers
Installing and Configuring TimesTen
How to Enable a TimesTen Database to Run in a Global Zone Configuration
How to Enable TimesTen to Run in a Non-Global Zone Configuration
How to Install and Configure TimesTen
Verifying the Installation and Configuration of TimesTen
How to Verify Installation and Configuration of TimesTen
Installing the HA for TimesTen Packages
How to Install the HA for TimesTen Packages
Registering and Configuring HA for TimesTen
Specifying Extension Properties for the TimesTen Resource
Creating and Enabling Resources for TimesTen
How to Create and Enable Resources for TimesTen in a Failover Configuration
How to Create and Enable Resources for TimesTen in a Multiple-Master Configuration
How to Create and Enable Resources for TimesTen in a Scalable Configuration
How to Create and Enable Resources for TimesTen in an Active-Standby Configuration
Verifying the HA for TimesTen Installation and Configuration
How to Verify the HA for TimesTen Installation for Failover Configurations
How to Verify the HA for TimesTen Installation for Scalable or Multiple-Master Configurations
Define the TimesTen Replication
Tuning the HA for TimesTen Fault Monitor
Operation of the Fault Monitor for ORCL.TimesTen_server Resource Type
Operation of the Fault Monitor for the Other HA for TimesTen Resource Types
How to Activate Debugging for HA for TimesTen
A. HA for TimesTen Extension Properties
B. Deployment Example: Installing HA for TimesTen in a Failover Configuration
C. Deployment Example: Installing HA for TimesTen in an Active-Active Configuration
D. Deployment Example: Installing HA for TimesTen in a Scalable Subscriber Configuration
This section contains the information you need to plan your HA for TimesTen installation and configuration.
TimesTen can be configured in the following ways, classified by the TimesTen replication configuration.
Table 2 TimesTen and Resource Group Topology
|
HA for TimesTen is supported in Solaris Containers, also called Solaris non-global zones. Oracle Solaris Cluster offers the following concepts for Solaris Containers:
A simple non-global zone can be configured in a resource group. The zone uses the node name nodename:zonenameas a valid target in the resource group's node list.
A zone cluster is a Solaris container of brand cluster that is created by using the clzonecluster command. A zone cluster forms a complete and separate cluster across the global-cluster nodes.
An HA container is a non-global zone that is managed by the HA-Solaris Containers agent, and is represented by a resource of a resource group.
HA for TimesTen is configurable in all types of Solaris containers except an HA container.
TimesTen offers the option to configure data stores as in-memory database caches. This is a data store property and it is transparent to the HA for TimesTen agent. The underlying Oracle database can be made highly available in the same cluster as the in-memory database caches or in a different cluster.
The following configuration restrictions apply to HA for TimesTen.
Caution - Your data service configuration might not be supported if you do not observe these restrictions. |
Combining data stores - The TimesTen database can manage multiple data stores with a single instance. However, you can only mix the data-store topology if the data stores match your resource-group topology. For example, if one data store requires a failover resource and the other requires a multiple-master resource, you cannot mix the data stores in one single TimesTen server resource.
Automatic startup - The TimesTen software installation provides an option to start the TimesTen server on system reboot. In an HA for TimesTen configuration, do not configure this option. HA for TimesTen controls the TimesTen server startup.
Recovery actions - The TimesTen server resource type does not perform TimesTen internal error recovery actions, such as the reduplication of data stores. Only an active-standby configuration uses this type of recovery. For all other configurations, these type of actions are manual procedures.
Node lists in an active-standby configuration - All resource groups that are part of an active-standby configuration must share the same node list.
The following are configuration requirements for HA for TimesTen.
Caution - If your data service configuration does not conform to these requirements, the data service configuration might not be supported. |
Dependencies between resource types – The dependencies between the HA for TimesTen resource types are described in the following table.
|
You set these dependencies when you register and configure HA for TimesTen. For more information, see Registering and Configuring HA for TimesTen.
If more elaborate dependencies are required, see the r_properties(5) and rg_properties(5) man pages for further dependencies and affinities settings.
Replication policies and cache policies – Except for active-standby configurations, in all configurations that use replication and in-memory database cache, the startup policy for the replication and the cache must be set to always.