Browse Prior Art Database

High-availability Offline Transaction System (HOTS) Disclosure Number: IPCOM000028541D
Original Publication Date: 2004-May-19
Included in the Prior Art Database: 2004-May-19
Document File: 1 page(s) / 53K

Publishing Venue



This disclosure describes a technique to implement high-availability for database-based applications. The technique is simple, cost effective and low maintenance.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 1

High-availability Offline Transaction System (HOTS)


High availability is very important for business critical applications. However, availability is rarely an inherent feature in most applications. The system administrators, who are responsible for deploying and supporting the applications resort to technologies like replication, mirroring, redundancy, standby backup and clustering to implement high-availability. Such solutions are expensive as well as difficult to manage. It is not easy to justify the cost of implementing these solutions for all business applications. HOTS solution provides a mechanism to implement application-based high-availability. The solution can be implemented for any database-based transaction-oriented application by the database administrators. However, for COTS (commercial off the shelf) applications this would imply that each organization using the software design their own solution. The problem can be overcome, if the COTS vendors incorporate this solution into their applications.


The solution involves the use of a standby database server machine which is a scaled down version of the production database server. The standby server should house a copy of the "day zero" production database. In other words, the database shouldn't contain any transaction data; it should only contain the master data necessary to create the transactions. For example, a call center application's database should contain the customer information, product information, status codes, category codes etc. but it shouldn't contain any call records. In addition, all kinds o...