Configuring an Active Standby Pair
with TimesTen In-Memory Database and Clusterware

This tutorial will make use of the pre-defined DSN repdb1_1122 shipped with TimesTen 11.2.2. The hostnames of the two machines in the examples are ttcwnode1 and ttcwnode2. The active database will be created in ttcwnode1 and the standby database in ttcwnode2.

The following tasks are required to configure an Active Standby pair with Oracle Clusterware and TimesTen In-Memory Database:

1. Register the TimesTen Instance Information

  1. TimesTen instance information is stored in the Oracle Cluster Registry. As the root user on UNIX or Linux platforms, or as the instance administrator on Windows, register the TimesTen instance information by executing the ttCWAdmin -ocrConfig command on any one of the hosts (ttcwnode1 or ttcwnode2).

    ttCWAdmin -ocrConfig

    ttCWAdmin -ocrConfig

2. Start the Cluster Agent

  1. Start the TimesTen cluster agent by executing the ttCWAdmin -init command on any one of the hosts. This command starts the TimesTen clusterware agents and TimesTen daemons on all nodes and starts monitoring them. For example on ttcwnode1:

    ttCWAdmin -init

    ttCWAdmin -init

3. Create a database

In order to set up an Active Standby Pair via ttCWAdmin, you need to define an "active" TimesTen database on one of the hosts.
This database must include a user with the ADMIN privilege and an application user with some objects to be used for replication.

  1. Define a system DSN on the active master host as the instance administrator.

    In this example we will use a pre-defined system DSN repdb1_1122 on host ttcwnode1. ttcwnode1 will function as the active database in the active standby pair managed by Clusterware. For Clusterware-managed replication, the database DSN must be the same as the database file name. Here is a screenshot of the relevant section in ttcwnode1's sys.odbc.ini file:

    repdb1_1122 System DSN

    Note: On the other host (ttcwnode2), an identical system DSN (i.e. [repdb1_1122]) and database file name (i.e. repdb1_1122) must also exist. This is used during the creation of the standby database on ttcwnode2.

  2. Connect to the repdb1_1122 database from the active node (ttcwnode1) using ttIsql as the instance administrator.

    ttIsql repdb1_1122

    ttIsql repdb1_1122

    Refer to the section Setting up Data Source Name for more information on how to define your own DSNs.

4. Create a user to administer the active standby pair

  1. Create a database user and assign that user privilege as the database and replication administrator by granting the user the admin privilege. This admin user is responsible for setting up and managing the active standby pair.

    create user adm identified by adm;
    grant admin to adm;

    create admin user

  2. Create an application user and tables in the database. In this example, we will create an application user called appuser and this user will own the customers and orders tables.

    create user appuser identified by appuser;
    grant create session, create table to appuser;

    create appuser

  3. Log in as the user appuser in ttIsql and execute the following statements or run the script create_appuser_obj.sql located in the <install_dir>/quickstart/sample_scripts/replication directory to create the two tables in the appuser schema.


    connect "dsn=repdb1_1122;uid=appuser";

    Run the create_appuser_obj.sql script:


    Or run the following code:


    insert into customers values (3700,'Peter','Burchard','882 Osborne Avenue, Boston, MA 02122');
    insert into customers values (1121,'Saul','Mendoza','721 Stardust Street, Mountain View, CA 94043');


    insert into ORDERS values (6853036,3700,'0028616731',to_date('2008-04-05','yyyy-mm-dd'));
    insert into ORDERS values (6853041,3700,'0198612510',to_date('2009-01-12','yyyy-mm-dd'));
    insert into ORDERS values (6853169,1121,'0003750299',to_date('2008-08-01','yyyy-mm-dd'));
    insert into ORDERS values (6853174,1121,'0789428741',to_date('2008-10-25','yyyy-mm-dd'));
    insert into ORDERS values (6853179,1121,'0198612583',to_date('2009-02-02','yyyy-mm-dd'));

5. Create the TimesTen configuration file

  1. Although there are many possible attributes in a file, for a basic Active Standby pair configuration,
    only the MasterHosts attribute is needed.

    repdb1_1122 Cluster entry

    The file is in the <install_dir>/info directory.

    The entry name (eg [repdb1_1122]) must correspond to the system DSN for the active and standby databases.

    Note: When you use the installer or ttmodinstall to add support for Oracle Clusterware, the mandatory MasterHosts attribute will be created in the file for you. For more complex configurations, you need to add the relevant attributes yourself in the file on every node in the cluster.

6. Create an Active Standby Pair

  1. Drop any existing [SQL] Active Standby pair for the repdb1_1122 database by running the following command:

    drop active standby pair;

    You cannot mix Active Standby Pairs managed by SQL and managed by ttCWAdmin.
    An Active Standby Pair for a database should be managed by either SQL or by ttCWAdmin, and not by both.

  2. Create an Active Standby pair replication scheme by executing the ttCWAdmin -create command on any host. For example on ttcwnode2:

    ttcwadmin -create -dsn repdb1_1122

    ttCWAdmin create

    Based on the repdb1_1122 entries in the system DSN and the, this command created the replication scheme for the repdb1_1122 database on the ttcwnode1 and ttcwnode2 hosts, with ttcwnode1 as the active node.

7. Start the Active Standby Pair

  1. Start the Active Standby pair replication scheme managed by ttCWAdmin by executing the ttCWAdmin -start command on any host. For example on ttcwnode1:

    ttcwadmin -start -dsn repdb1_1122

    ttcwadmin start


    • ttCWAdmin -start will automatically start the replication agent on the standby machine and duplicate the active database onto the standby host.
    • The time it takes to duplicate the active database will be proportional to the size of the active database and the performance of the hardware used.
    • Once the Active Standby Pair has be started by ttCWAdmin, committed writes to the active database will be written to its local transaction logs, but they will not get replicated to the standby database until the duplicate operation is complete.
    • To check the progress of the database duplication, use the ttCWAdmin -status -dsn <your_DSN> command.

For more information about Using Oracle Clusterware to Manage Active Standby Pairs refer to the documentation here