Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1998-03-20
2001-03-20
Amsbury, Wayne (Department: 2171)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000
Reexamination Certificate
active
06205449
ABSTRACT:
TECHNICAL FIELD OF THE INVENTION
The present invention is directed, in general, to computer systems and, more specifically, to a system and method for providing hot spare redundancy and recovery f or a very large database management system.
BACKGROUND OF THE INVENTION
A database is a collection of data organized usefully and fundamental to some software application (e.g., an information management system). The database is associated with a database manager (“DBM”), which itself is software-based and performs a range of tasks on the database, usually for the software application, the range of tasks varying largely upon the intended use of the database and the sophistication of the DBM.
Traditionally, databases have been stored in non-volatile (disk) memory, while DBMs and software applications have resided, at least in pertinent part, in volatile (main) memory. DBMs have been distinguished by the manner in which they process and manipulate the data with which they are charged. For example, some DBMs only manipulate one data file at a time (flat-file DBMs), others process multiple data files at one time, associating data from several different data files (relational DBMs).
Fundamental DBM operations include storing data, creating indexes that allow retrieval of data, linking data from different files (relational DBMs), etc. Two of the most important operations, and hence most sophisticated, performed by DBMs are data integrity and database recovery.
Data integrity, very simply, insures that one software application cannot modify a particular data file while another software application is relying upon the contents of the same. Database recovery, on the other hand, involves rebuilding the database after part or all of its data is corrupted—data corruption may be caused by a power outage, a program failure or the like that causes the DBM to suspect that at least part of the data stored therein has been lost or damaged.
Today, many software applications require high performance access to data with response time requirements on the order of a few to tens of milliseconds. Traditional non-volatile (disk) memory DBMs have been largely incapable of meeting the high performance needs of such applications (often due to the latency of accessing data that is non-volatile memory-resident).
In an effort to improve performance, the entire database is mapped directly into volatile (main) memory. The data may be accessed either directly by virtual memory pointers, or indirectly via location independent database offsets that quickly translate into memory addresses. Data access using a main memory database is much faster than disk-based storage managers—pages need not be written to disk during normal processing to make space for other pages.
A significant danger exists however if a portion or all of the main memory database becomes corrupted then, unlike non-volatile (disk) memory databases, the entire database may need to be recovered. One recovery approach uses undo log records that are used to track the progress of transactions that have modified the database in some manner. Traditional recovery schemes implement write-ahead logging (“WAL”), whereby all undo logs for updates on a page are “flushed” to disk before the page is flushed to disk. To guarantee trueness, the WAL property and, hence, the recovery method, a latch is held on the page (or possibly on some system log) while the page is copied to disk, and, thus, reintroducing disk memory processing costs as such latching tends to significantly increase access costs to non-volatile memory, increase programming complexity, and interfere with normal processing.
SUMMARY OF THE INVENTION
To address the above-discussed deficiencies of the prior art, the present invention provides, for use with a primary database residing on a primary computer, the primary computer being couplable to a secondary computer having a secondary database, a system for, and method of, allowing the secondary computer to operate as a hot spare for the primary computer and a database management system employing the system or the method. In one embodiment, the system includes a transaction logger, associated with the primary database, that maintains log records of transactions involving persistent data in the primary database. The system further includes a transaction processor, associated with the primary database, that transmits at least a portion of the log records to the secondary computer. Transmission of the portion of the log allows the secondary computer to commit at least a portion of the log records to the secondary database and thereby provide at least partial data redundancy. The system may still further include parameters, associated with the primary and secondary databases, that designate a state of the primary and secondary computers and indicate relative synchronization of the primary and secondary databases. These parameters, if present, can aid in substitution of databases and recovery in the event of system failure.
The present invention therefore introduces the broad concept of employing a database log to synchronize primary and secondary (hot spare) databases. The mechanisms in the log ensure that transmitted transactions contained in the log are applied to both the primary and secondary databases.
The foregoing has outlined, rather broadly, preferred and alternative features of the present invention so that those skilled in the art may better understand the detailed description of the invention that follows. Additional features of the invention will be described hereinafter that form the subject of the claims of the invention. Those skilled in the art should appreciate that they can readily use the disclosed conception and specific embodiment as a basis for designing or modifying other structures for carrying out the same purposes of the present invention. Those skilled in the art should also realize that such equivalent constructions do not depart from the spirit and scope of the invention in its broadest form.
REFERENCES:
patent: 5140685 (1992-08-01), Sipple et al.
patent: 5212789 (1993-05-01), Rago
patent: 5257367 (1993-10-01), Goodlander et al.
patent: 5388256 (1995-02-01), Herbert
patent: 5499337 (1996-03-01), Gordon
patent: 5504879 (1996-04-01), Eisenberg et al.
patent: 5555404 (1996-09-01), Torbjornsen et al.
patent: 5651133 (1997-07-01), Burkes et al.
patent: 5720027 (1998-02-01), Sarkozy et al.
patent: 5924094 (1999-07-01), Sutter
patent: 5933839 (1999-08-01), Hasegawa et al.
patent: 5963634 (1999-10-01), Kantola et al.
patent: 5991804 (1999-11-01), Bolosky et al.
Rastogi Rajeev
Silberschatz Abraham
Amsbury Wayne
Lucent Technologies - Inc.
LandOfFree
System and method for providing hot spare redundancy and... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with System and method for providing hot spare redundancy and..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and System and method for providing hot spare redundancy and... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2454426