Planning the HA for TimesTen Installation and Configuration

This section contains the information you need to plan your HA for TimesTen installation and configuration.

Planning the Resource Group Topology for HA for TimesTen

TimesTen can be configured in the following ways, classified by the TimesTen replication configuration.

Table 1-2 TimesTen and Resource Group Topology

TimesTen and Solaris Containers

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.

HA for TimesTen and In-Memory Database Cache

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.

Configuration Restrictions

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.

Configuration Requirements

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.

  Resource Type Dependency ORCL.TimesTen_server SUNW.HAStoragePlus is required if the configuration uses a highly available local file system. SUNW.Logical_Hostname is required for a failover resource. SUNW.Shared_Address is required for a scalable subscriber. ORCL.TimesTen_cldaemon An ORCL.TimesTen_clag resource is required in an active-standby configuration. ORCL.TimesTen_dbmon An ORCL.TimesTen_cldaemon resource is required in an active-standby configuration. ORCL.TimesTen_active An ORCL.TimesTen_dbmon resource is required in an active-standby configuration. ORCL.TimesTen_standby An ORCL.TimesTen_dbmon resource is required in an active-standby configuration.

  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.