with TimesTen In-Memory Database and Clusterware
An Active Standby Pair configuration includes an active database, a standby database, and optional read only subscriber databases. The standby database uses Oracle TimesTen Replication to receive the changes from the active database and forwards the changes to optional read-only subscriber databases.
Oracle Clusterware is a general purpose cluster manager that manages and monitors the availability of software components that participate in a cluster. TimesTen In-Memory Database is integrated with Oracle Clusterware via the ttCWAdmin utility. When a customer chooses to use Oracle Clusterware with the TimesTen in-memory database, the failover and restart of Active Standby Pair databases are handled automatically. In addition, Oracle Clusterware may be used to manage the actual applications that use TimesTen.
Installing Oracle Clusterware and TimesTen
| 1. | Install Clusterware | Oracle Clusterware 11.2.0.2 is required. |
| 2. | Install TimesTen | Oracle TimesTen In-Memory Database 11.2.2 is required. |
Follow the example below to install Oracle Clusterware and TimesTen as described in the tasks above:
Installing Oracle Clusterware and TimesTen example
Configuring the Active Standby Pair for Clusterware and TimesTen In-Memory Database
| 1. | Register instance information | TimesTen instance information is stored in the Oracle Cluster Registry. Register the TimesTen instance information by executing the ttCWAdmin -ocrConfig command on any one of the hosts. |
| 2. | Start cluster agents | Start the TimesTen cluster agents by executing the ttCWAdmin -init command on any one of the hosts. These cluster agents manage the TimesTen main daemon, which in turn manages the TimesTen replication agent on all hosts in the cluster. |
| 3. | Create a Database | In order to set up an active standby pair configuration, you need to start with a running database.
This database should include one or more tables owned by an application user. All tables must also have a primary key index. If you have an existing database, this step can be skipped. |
| 4. | Create a user to administer the active standby pair | This database must include a user with ADMIN privilege. This user is the replication administrator responsible for managing the active standby configuration. |
| 5. | Create cluster.oracle.ini file | The cluster.oracle.ini configuration file uses attributes to declaratively define the configuration of an active standby pair that will be managed by Oracle Clusterware. The entry name for the Active Standby Pair in the cluster.oracle.ini file must correspond to the system DSN created in step 2 above. |
| 6. | Create Active Standby Pair | Create an Active Standby Pair by executing the ttCWAdmin -create command on any host. |
| 7. | Start Active Standby Pair | Start the Active Standby Pair by executing the ttCWAdmin -start command on any host. |
Follow the example below to configure an active standby pair with TimesTen and Oracle Clusterware using the configuration steps described above:
Configuring an Active Standby Pair with TimesTen
In-Memory Database and Clusterware example
Managing an Active Standby Pair using Clusterware and TimesTen In-Memory Database
| 1. | Check the cluster agents' status | Find the status of the Active Standby Pair cluster via the ttCWAdmin -status command on any host in the cluster. |
| 2. | Stop the Active Standby Pair | Stop the Active Standby Pair via the ttCWAdmin -stop command on any host in the cluster. |
| 3. | Drop the Active Standby Pair | Drop the Active Standby Pair via the ttCWAdmin -drop command on any host in the cluster. |
| 4. | Shutdown the cluster agents | Shutdown the TimesTen cluster agents via the ttCWAdmin -shutdown command on any host in the cluster. |
Follow the example below to manage an active standby pair with TimesTen and Oracle Clusterware using the configuration steps described
above:
Managing an Active Standby Pair
with TimesTen In-Memory Database and Clusterware example
The following documentation link
covers more admin tasks.
Automatic failover and restart for Active Standby Pairs and user applications
The following links describe how Oracle Clusterware is used to failover and restart Active Standby Pairs and user applications.
The following viewlet shows failover and failback of a user application and its corresponding Active Standby Pair with Oracle Clusterware.