TimesTen In-Memory Database
for Extreme Performance

  • May 15, 2017

How to create a simple TimesTen HA config on Oracle Bare Metal Cloud

Doug Hood
Evangelist for Oracle TimesTen, Oracle In-Memory and Oracle NoSQL

My blog How do I install TimesTen in the Oracle Bare Metal Cloud, resulted in the TimesTen In-Memory Database software being installed on a set of machines in the Cloud.

This blog uses those TimesTen installations and covers how to create the simplest TimesTen high availability configuration, a TimesTen Active Standby Pair via the mkasp script:

A TimesTen Active Standby Pair

The mkasp script will create a database, populate it with data, create the active standby pair and replicate some data.

Using the Oracle Bare Metal Cloud Service console, I created some Bare Metal High IO instances [BM.HighIO1.36] in three availability domains:

Oralce Bare Metal High IO instances

You need to click on the instance names (eg doughigh1 and doughigh2) to determine the public and private IP addresses for those machines.

IP addresses for doughigh1

IP addresses for doughigh2

The resulting IP addresses were:

Bare Metal Compute Public and Private IP Addresses

From your on premises machine [ie a bash shell in Linux, MacOS or Cygwin] do the following:

  • Change to the directory where the ott-bmc-byol scripts are
  • Run the mkasp script with the private IP addresses for the machines that will host the active and standby databases
    • -a means the Active host's IP address
    • -s means the Standby host's IP address
    • --admpwd is the password for the TimesTen Database user who will have the admin privilege
    • --apppwd is the password for the TimesTen Database user who owns the schema objects

Run the mkasp script

For my on premise environment, the commands are:

cd ott-bmc-byol/scripts/timesten

./mkasp -a -s --admpwd admin --apppwd appuser

This script will run several other scripts which will create the active standby pair and replicate a row of data:

Start of mkasp output

The end of the script output should look like this:

end of mkasp script output

The script output showed 'Active DB OK' and that the row for order_number 68531180 was replicated to the standby database.

Disclaimer: these are my personal thoughts and do not represent Oracle's official viewpoint in any way, shape, or form.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.