Continuously available database server having multiple groups of nodes, each group maintaining a database copy with fragments stored on multiple nodes
This is a continuation of application Ser. No. 07/852,669 filed Mar. 17, 1992, now abandoned. 
    
    
     The present invention relates generally to database server computer systems using multiple interconnected computers to provide continuous, reliable transactional services. 
     BACKGROUND OF THE INVENTION 
     In a variety of commercial contexts it is very important for a database transactional server to be continuously available, twenty-four hours per day, without interruption. For instance, the database server used to accumulate toll charges and other billing information for a telephone system must have a level of reliability similar to that of the telephone system itself. While most fault-tolerant computer systems are only single-fault tolerant, in order to have the level of reliability required for a telephone charge database or an airline reservation system, the database server should also have fast, automatic self-repair to re-establish the original fault tolerance level. In the context of the present invention, self-repair means that all of the data storage and transaction handling responsibilities of the failed node are transferred to other nodes in the database server system. Completion of the self-repair process must re-establish single fault tolerance. Thus, not only must no single hardware failure be able to cause the entire system to fail, even a second hardware failure should not be able to cause the entire system to fail. 
     Due to the requirement of continuous availability, the self-repair process should be non-blocking, meaning that database server remains continuously available (i.e., able to continue servicing transactions) while the self-repair is being performed. 
     In addition to continuous availability, another desirable feature for high reliability database servers is graceful degradation with respect to data availability when multiple failures occur. In other words, even if multiple failures should cause some data records to be unavailable, the database server should still continue to service transactions that do not need to access the unavailable data. 
     One common method of providing reliable computer operation is to use &#34;fault tolerant&#34; computer systems, which typically have redundant components. However, most fault tolerant computer systems can only handle one hardware component failure in a short period of time, and also, most such systems are vulnerable to failures of peripheral equipment such as power failures and communication network failures. It is the object of the present invention to overcome these shortcomings, and to provide a highly reliable database server that is single fault tolerant, has automatic non-blocking, self-repair that quickly re-establishes single fault-tolerance after a first node failure, and provides graceful degradation with respect to data availability when multiple failures occur. 
     SUMMARY OF THE INVENTION 
     In summary, the present invention is a database server computer system having multiple data processors, also called nodes. Using a &#34;shared nothing&#34; system architecture, each data processor has its own central processing unit, primary and secondary memory for storing database tables and other data structures, and communication channels for communication with other ones of the data processors. Some or all of the data processors include a communications processor for receiving transaction requests and for transmitting responses thereto. To prevent any one hardware failure from causing the entire system to fail, the data processors are divided into at least first and second node groups, wherein each node group shares no resources, including power supply and cooling system components, with the other groups. 
     Each database table in the system is divided into N fragments, where N is the number of data processors in the system. The records of the database table are allocated as evenly as possible among the table fragments, for example, by hashing a primary key value for each record with a predefined hash function and using the resulting value to select one of the database table fragments. A &#34;primary replica&#34; of each fragment is stored on a corresponding one of the data processors. For each primary fragment replica, the system also generates at least one standby replica, which is essentially a copy of the fragment&#39;s primary replica. Database transactions are performed using the primary fragment replicas, and the standby replicas are updated using transaction log records. To ensure continued data availability even after a single node failure, the primary and standby replicas for each database table fragment are stored in data processors in different ones of the first and second node groups. 
     Every node of the system includes a data dictionary that stores information indicating where each primary and standby fragment replica is stored among the system&#39;s data processors. A transaction manager on each system node responds to database queries by determining which fragment of a database is being accessed by the database query and then forwarding the database query to the data processor on which the primary replica of that fragment is stored. 
     Upon failure of any one of the data processors in the system, each node changes the information in its data dictionary (A) to indicate that the primary and standby fragment replicas stored on the failed data processor are not available, and (B) to indicate that for each primary fragment replica stored on the failed data processor, the corresponding standby replica is to be used in its place. In addition, the fragment replicas made unavailable by the node failure are regenerated from the other replicas thereof in the system and stored in subfragments on the remaining available nodes of the database server. Thus the data replicas made unavailable by a node failure are redistributed over the remaining available nodes. The replica regeneration process is non-blocking, allowing the database server to continuously service transactions even during self-repair of the database server. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     Additional objects and features of the invention will be more readily apparent from the following detailed description and appended claims when taken in conjunction with the drawings, in which: 
     FIG. 1 is a block diagram of a multiprocessor computer system having nodes that are interconnected by a multi-path hypercubic communication network. 
     FIG. 2 is another block diagram of the multiprocessor computer system of FIG. 1. 
     FIG. 3 is a block diagram of one processor in the multiprocessor computer system of the present invention. 
     FIG. 4 is a block diagram showing fragmentation of a single database table in accordance with the present invention. 
     FIG. 5 is a block diagram showing a redistribution of database table fragments after a single node failure. 
     FIG. 6 depicts relationships between software modules and data structures used in a preferred embodiment of the present invention. 
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT 
     Referring to FIG. 1, there is shown a multiprocessor database server 100 having eight data processors 102, often called nodes, interconnected by a multi-path hypercubic communication network 104. The number of data processors shown in this example is eight or 2 3 , corresponding to a three dimensional hypercube. The communication network 104 includes all the communication paths between nodes 102 shown in FIG. 1. In an N dimensional hypercube, each node has direct connections to N neighboring nodes. 
     Multiple ones of the data processors 102 have a communications co-processor 106 for external communications so that the failure of any single one of these communications co-processors does not cause the database server 100 to become unavailable. The database server 100 responds to queries received from requestor systems 110 via communication connections 112 that couple those requestor systems to communication co-processors 106. In the preferred embodiment, at least one data processor 102 in every group of four data processors is coupled by a communication co-processor and communication connection 112 to an external host computer. 
     The number of processors used can be scaled up or down to fit the data processing needs of any particular application. It is preferred, but not necessary, to use hypercubic architectures having 2 J  data processors interconnected in a hypercubic communication network, with J being an integer greater than or equal to three. More generally, the database server 100 should have a symmetric set of nodes on each side of the system&#39;s &#34;mirror dimension&#34;. 
     Many aspects of the invention can be implemented using as few as 2 2  (i.e. four) processors. However, a system with just four nodes will not be able to achieve the preferred level of fault tolerance following a single node failure. 
     Referring to FIG. 2, a system with sixteen data processors 102 is divided into two groups of eight processors, half on each side of the computer system&#39;s &#34;mirror dimension&#34; as shown. To ensure fault tolerence, the database server system uses multiple, homogenous powerful nodes with a high degree of node isolation. In particular, a &#34;shared nothing&#34; hardware architecture is used, meaning that neither primary memory nor disks are shared between nodes. Neither primary nor secondary memory can be shared in a database server with fault masking capabilities because memory is a critical component used by servers at all nodes. 
     In the preferred embodiment of FIG. 2, the sixteen data processors 102 are divided along two dimensions into four groups. Each group shares a pair of power supply units 120 and a pair of cooling fans 122, each pair of power supply units and cooling fans providing single fault tolerence. As will be described in more detail below, in order to provide multi-fault tolerance and fault masking, it is important that the processors on each side of the mirror dimension be divided into at least two distinct groups that share no resources whatsoever. It is for this reason that the data processors 102 are divided into sub-groups on each side of the mirror dimension in FIG. 2. 
     Referring to FIG. 3, each data processor 102 in the preferred embodiment has a central processing unit (CPU) 132 such as the i486 microprocessor made by Intel, a system bus 134 that connects the CPU 132 to secondary memory 136 (e.g., magnetic disk storage devices), and primary memory 138 (i.e., high speed, random access memory). Every data processor 102 also has a multiplicity of parallel communication channels 140 for communication with at least two other data processors 102 in the system. At least one data processor in each node group (see FIG. 2) includes a communications co-processor 106 for receiving transaction requests from requestor systems via a communications bus 112 and for transmitting responses thereto. 
     The secondary memory 136 will typically contain a number of disk storage devices 144-146 that are used to store data and programs (e.g., a set of precompiled transactions). In database servers with very high transaction handling rates, multiple disk storage devices are required because of the limited data handling capabilities of any single one device, and because of the large amounts of data to be stored. In the present invention, secondary memory 106 is used to store portions (herein called fragments) of data tables 148, as well as corresponding table indices 150. 
     Stored in primary memory 138 are currently executing programs, including the node&#39;s operating system software 152, database management system (DBMS) software 154, and communication control software 156. In the preferred embodiment, the DBMS software 154 includes a data dictionary 158, database fragmentation control software 160, and a transaction manager 162. A copy of the data dictionary is also maintained on disk (secondary memory 136). As will be described in more detail below, the data dictionary 158 is used to determine the location of various fragments (portions) of any specified database table, and the database fragmentation control software 160 controls the process of fragmenting database tables, masking node failures, making extra replicas of database fragments, and reconstructing database fragments on nodes after a failure recovery. 
     Database Fragments and Replicas 
     Referring to FIG. 4, for the purposes of explaining database table fragmentation, we will use as an example a system having eight nodes. Every database table is fragmented over the system nodes, and the number of fragments of each table corresponds to the number of nodes in the system. FIG. 4 shows the fragments for one database table, labelled as Primary Replica fragments 0 to 7 and Hot Standby Replica fragments 0 to 7. Each table fragment, such as primary replica fragment 200, represents a portion of the records in a table. The records in a database table are allocated to the various fragments as evenly as possible so as to spread the data storage and transaction handling load as evenly as possible among the system&#39;s nodes. 
     The term &#34;record&#34; as used in this document is defined to be synonymous with the term &#34;tuple&#34; often found in database computer science literature. A record or tuple is defined as a unit of data uniquely identified by a key value. 
     In the preferred embodiment, records of a table are allocated among the fragments using a hash function such as: 
     
         v=k modulo n 
    
     where k is the key value associated with the record, n is the number of fragments, and v is the result from the hashing that is used to select the record&#39;s fragment. v will always have a value between 0 and n-1. For example, if the key value for a record is 15 and n=8, then the record belongs in fragment 7. 
     As new records for a table are created, they are stored in the node that stores the corresponding table fragment. 
     In the present invention, each table fragment has between two and four replicas. The example in FIG. 4 shows just two replicas 200 and 202 for each table fragment. One of the replicas is called the primary replica, a second one is called the hot standby replica, and any additional replicas are called &#34;additional read only replicas&#34;. Increasing the number of table replicas increases the level of fault tolerance provided. 
     An important part of the replica allocation strategy of the present invention is that two replicas of a data record must never be dependent on the same software or hardware servers. The fragment replicas are therefore stored at nodes within different node groups. In particular, the primary and first hot standby replicas of a fragment am always stored in nodes on opposite sides of the system&#39;s mirror dimension, thereby ensuring that both replicas are not dependent on the same power supply or cooling fan units. If a third replica is provided, the third replica is always stored in a node group different from the node groups in which the primary and hot standby replicas are stored. 
     During &#34;normal&#34; operation, when all nodes of the database server system are operational, database operations are performed using the primary fragment replicas. The records in the hot standby replica fragments are kept up to date by sending all log records produced by transactions from the node with the primary replica to the node with the corresponding hot standby replica. The serialized log records are read and the corresponding table records updated at the node of the hot standby replica as an ongoing activity. More particularly, operations represented by the log records are repeated at the node of the hot standby replica after checking the data table to make sure that those operations have not already been performed, which can be the case when a table has been refragmented or rebuilt. 
     Referring to FIG. 5, when a node such as Node 2 of the system fails, the system performs an automatic non-blocking, corrective on-line repair that masks the occurrence of single node failures. For each table fragment replica that becomes inaccessible due to a node or disk failure, a new replica is produced on each side of the mirror dimension. While this repair activity takes place, the system is vulnerable to a second node or disk failure. After the repair is done the system is again single fault-tolerant. 
     When one fragment replica of a table becomes unavailable, the unavailable fragment is refragmented into a collection of subfragments. More specifically, when a primary fragment replica such as fragment 204 in FIG. 5 becomes unavailable, the corresponding hot standby replica fragment 206 is promoted to primary replica status. Then, using the still available replica 206 of the fragment, the data records in the fragment are copied into new subfragments 2&#39;A, 2&#39;B and 2&#39;C that are stored on the remaining available nodes on the same side of the mirror dimension as the failed node. Simultaneously, replicas 2&#34;A, 2&#34;B and 2&#34;C of those subfragments are generated and stored on the corresponding nodes on the other side of the mirror dimension. When a hot standby fragment replica such as fragment 208 in FIG. 5 becomes unavailable, the corresponding primary replica fragment is used to generate new subfragments 6&#39;A, 6&#39;B and 6&#39;C that are stored on the remaining available nodes on the same side of the mirror dimension as the failed node, as well as replicas 6&#34;A, 6&#34;B and 6&#34;C of those subfragments on the other side of the mirror dimension. 
     One subfragment is allocated to each available node in order to distribute the reallocated data and the added transaction workload over as many nodes as possible. Once all the subfragments for a particular table fragment have been built, the remaining higher level fragment (i.e., in Node 6) is no longer used as the primary fragment replica for handling transactions. Instead, the new subfragments on the same side of the mirror dimension as the primary fragment replica are now given the status of &#34;primary&#34;. In the example shown in FIG. 5, the table fragments 206 and 210 are no longer used after the subfragments have been built, and instead subfragments 2&#39;A, 2&#39;B and 2&#39;C are used as the primary (sub)fragments in place of primary fragment 2, and subfragments 6&#34;A, 6&#34;B and 6&#34;C are used as the primary (sub)fragments for transaction processing in place of primary fragment 6. As a result, once all the affected table fragments have been subfragmented, node 6 is essentially dormant until the failed node is restarted. 
     If further node failures occur after the above described repair has taken place, a subfragment may be further refragmented. The same policies with respect to fragmentation, allocation and primary replica determination are used as for a first level subfragment. Data for each subfragment is kept in separate files to reduce the read and written data volumes when a replica is built and erased. 
     One exception to the above described method of handling multiple node failures is that if the second node failure is on the same side of the mirror dimension as &#34;dormant&#34; node 6, then table fragments in the second failed node can be rebuilt on node 6, and node 6 can then be used in place of the second failed node. For instance, if node 5 were to fail after completion of the self-repair caused by the failure of node 2, then the fragmentation control software would copy all the table fragments from node 1 onto node 6, and then use node 6 in the place of node 5. 
     In one preferred embodiment, the following hash function is used to determine the fragment to which each database record is allocated: 
     
         hash (k,n)=&lt;v, r&gt;=&lt;k modulo n,  k÷n &gt; 
    
     where k is the key value associated with the record, n is the number of fragments, v is the result (with a value between 0 and n-1) from the hash function, and r is an independent value for recursive use of the hash function. In the above expression, the division operator &#34;÷&#34; is surrounded by operators &#34; &#34; and &#34; &#34; to indicate that the result of the divide operation is rounded down to closest integer. A given database record can be found by applying the hash function to the record&#39;s key value k and the number of fragments n. The value of v determines which level 1 fragment the record belongs to. If the level 1 fragment has been subfragmented, the value r is used as the new key value that is hashed to determine the correct level 2 subfragment. This process is continued recursively until a fragment with replicas is found, and then the record is accessed from the primary replica. 
     During successive iterations of the above hash function to locate a record in a database table, the value of n in the above hash function is equal to the number of subfragments into which a fragment of the table has been divided. Typically, the value of n during successive iterations is assigned a sequence of values such as 
     n0=total number of nodes in system 
     n1=(n0/2)-1 
     n2=n1-1 
     n3=n2-1 
       . . . 
     An alternate, &#34;linear&#34; hash function that could be used for locating records within table fragments and subfragments is: 
     
         hash.sub.L (k,n)=&lt;v,r&gt;=&lt; n(k-L)÷(U-L+1) , N(k-L))modulo(U-L+1)+L&gt; 
    
     where the value of n is equal to the number of fragments or subfragments over which a table or table fragment is being distributed, and k is a key in the range [L, U]. This function divides the range of key values into equal sized intervals, and assumes that the key values k are homogeneously distributed over the value range L to U. &#34;v&#34; is the result (with a value between 0 and n-1) from the hash function, and r is an independent value for recursive use of the hash function. 
     For example, if key value k for a particular record is equal to 1377, all key values for the table fall in the range [1000, 1999], and n=5 on the first level and n=4 on the second level of hashing, then hash L  (k,n) is evaluated as follows: 
     
         hash.sub.L (1377,5)=&lt; 5·377÷1000 , 5·377 modulo 1000+1000&gt;=&lt;1, 1885&gt; 
    
     
         hash.sub.L (1885,4)=&lt; 3540÷1000 , 3540 modulo 1000+1000&gt;=&lt;3, 1540&gt; 
    
     Thus, the record with key value 1377 is allocated to node 1 at the first fragment level, and to the third node at the second fragmentation level. 
     A &#34;fragment crash&#34; occurs when both the primary and the hot standby replicas of a fragment or subfragment become unavailable, typically due to a node or disk failure. The crashed fragment becomes unavailable, but other fragments of the table remain available. Therefore, a fragment crash results in &#34;omission failures&#34; for only those transactions trying to access data records belonging to the failed fragment. 
     A gradual reduction of data availability is provided for subfragments as well as for fragments. If all replicas of a subfragment, or the fragment replicas containing the subfragment become unavailable, the subfragment is said to be crashed. For instance, referring to FIG. 5, if nodes 1 and 6 failed after the failure of Node 2 and after the resulting refragmentations were completed, then subfragments 2&#39;B and 6&#39;B would become unavailable, but the remainder of the database table would still be available. 
     When a previously failed node is restarted, data is again redistributed to obtain an approximately even distribution of data among the available nodes. The redistribution is performed on a per table basis to preserve the serializability of the redistribution operation, and also to restrict the workload induced by the redistribution activity so as to limit its impact on the timely servicing of database transactions. When data in the restarted node is available (i.e., the disk and file in which the table was stored were not lost), the restarted replica, which is assigned the role of a hot standby replica during the table rebuilding process, is produced using the state of the restarted replica at the point that the replica&#39;s node failed, plus the log records accumulated by the primary replica during the time that the failed node was unavailable. 
     When data in the restarted node is not available, or is so old that it does not meet timeliness criteria (e.g., restarting the node within 24 hours of a node failure), the restarted replica is rebuilt from scratch by copying the primary replica, and then using log records accumulated by the primary replica during the coping progress to ensure that the records in the restarted replica are consistent. In other words, because the copying process takes time, all data updates during the time occupied by the copying progress are repeated to ensure that the restarted replica is in a consistent state. 
     In the preferred embodiment, the nodes have sufficient computational power and inter-node communications bandwidth, above that needed for normal transaction processing loads, that all the table subfragmenting initiated by a node failure can be accomplished in approximately fifteen minutes, assuming that each node stores on the order of one to five gigabytes of data. It is important that the self-repair process be completed quickly, preferably in less than an hour, in order to reduce the likelihood that a second node might fail before a prior node failure is repaired. The &#34;excess&#34; computational and communications capabilities provided in order to make fast self-repair possible can be used during normal operations for activities such as computing and comparing the transactional and data storage loads on the system&#39;s nodes, and redistributing data among the nodes (by selecting a new hash function and then fragmenting the data tables and distributing the data among the nodes using that new hash function) when transactional or data storage loads are imbalanced. 
     Making the self-repair process non-blocking is accomplished by locking down only the pages of a data table that are currently being repliced while they are being read. Each page is therefore locked by the self-repair process only for a very brief time. Thus, the progress of transactions is not blocked by the self-repair process. A consistent version of each fragment replica is generated by sending to the new fragment replica, along with the copied pages of the data table, a copy of (A) all log records created for that fragment, beginning at the time that the copying process began, and (B) all &#34;undo&#34; log records that may be needed to reverse data table changes made by aborted transactions. Undo records are needed only for long running transactions in progress at the time the process of generating the new fragment replica begins. 
     Data Dictionary 
     Referring to FIG. 6, a copy of the data dictionary 158 is stored on every node of the system. The purpose of the data dictionary is to store all the information necessary to determine the current configuration of nodes in the system and to find any identified record in any identified data table. In particular, the data dictionary 158 comprises a set of &#34;system&#34; tables, the purpose and structure of which are explained next. The SysMachine Table 220 has just one record, which provides the name of the database server system, the number of nodes (i.e., data processors) in the system, and the number of data processor groups, also herein called node groups, in the system. As explained above, node groups are totally independent of each other insofar as hardware failures are concerned. The SysGroup Table 222 has one record 224 for each group of data processors. That record 224 indicates the group&#39;s Group ID, its status (e.g., running or unavailable), and a count of the number of nodes in the group. 
     The SysNodes Table 226 has one record 228 for each node in the system. Each record 228 indicates the node&#39;s node number, its status (e.g., running, restarting, isolated, or dead), the Group ID of its group, and a list of &#34;pair nodes&#34; in other groups that are preferred for table replication. 
     The SysTable Table 230 has one record 232 for each data table in the system. The record 232 for any particular table lists its Table ID, table name, a &#34;replica count&#34; that indicates the numbers of replicas of the table that exist in the system, the top level &#34;Fragment ID&#34; that corresponds to an entry in the SysFragment Table 236, the &#34;distribution method&#34; for locating the fragment associated with a specified record, the table&#39;s level 0 Fragment ID, and a timestamp indicating when the table was created. The &#34;distribution method&#34; is typically (1) one of two or more predefined hash functions, (2) &#34;linear,&#34; indicating that the fragment containing a particular record is located by hashing the key value for the record with a linear hash function, or (3) &#34;RoundRobin&#34;, indicating that the records in this table are assigned to fragments in a &#34;round robin&#34; fashion. The 
     &#34;RoundRobin&#34; distribution method is used only for low usage tables because a transaction using records in such tables must be sent to all the nodes in order to find the one in which the queried record is located. 
     Note that the Replica Count field for each table is a value assigned to each data table either by the table&#39;s creator or by an operating system policy, such as a policy that assigns every data table two replicas unless that assignment is explicitly overridden by a system operator. 
     Another table in data dictionary, called the Data Table Schemas table 234, stores the column definitions for each data table, often called table schemas. 
     The SysFragment Table 236 has a separate record 238 for every fragment and subfragment of every data table in the system. The record 238 for each table fragment contains the fragment&#39;s Fragment ID, an ordered list of the fragment&#39;s Replica IDs, a count of the number of subfragments at the next level of subfragmentation of the table, an ordered list of the Fragment IDs for those subfragments. Since table &#34;fragments&#34; are identified in the preferred embodiment as a value between 0 and n-1, where n is the number of fragments in any particular set, &#34;an ordered list&#34; in this context means that the Fragment IDs in the subfragment list are ordered so that the first Fragment ID in the list is for Fragment 0, the second Fragment ID in the list if for Fragment 1, and so on. 
     Similarly, if a particular data table has M replicas (as specified in the Replica Count field of the SysTable Table 230), then the Replica ID list will contain M Replica IDs for Fragment 0, followed by M Replica IDs for Fragment 1, and so on. Furthermore, in the preferred embodiment, the first Replica ID in the Replica ID list for a particular fragment is the Replica ID for the primary replica, the next Replica ID in the list is for the hot standby replica, and any additional Replica IDs in the list are for additional read only replicas. 
     The purpose of the SysReplica Table 240 is to store data representing the location and status of each data table fragment replica. For each fragment replica there is a separate record 242 in table 240 that indicates (A) the fragment replica&#39;s Replica ID and Fragment ID, (B) the node on which the fragment replica is stored and the file ID for the file in which it is stored, (C) the role of the fragment replica, such as &#34;primary,&#34; &#34;hot standby,&#34; or &#34;additional read only copy,&#34; and (D) the status of the fragment replica, such as &#34;available,&#34; &#34;void,&#34; or &#34;refragmenting&#34;. 
     The data dictionary 158 may also include other tables not relevant herein, such as tables for storing security or data access control information, tables for indicating the &#34;views&#34; and indices used in conjunction with each data table, and so on. 
     Whenever a database query is received by a node in the database server system, a transaction manager 162 in the database management system (DBMS) software 154 searches the SysTable Table 230 to find the Fragment ID for the applicable Database and the record Distribution Method for that table. The key value for the record being accessed by the query is hashed or otherwise reduced to a fragment number in accordance with the Distribution Method, and then the transaction manager 162 searches the SysFragment and SysReplica Tables 236 and 240 to find the primary fragment replica corresponding to the record being accessed and the Node number on which the primary fragment replica is located. Finally, if the node on which the primary fragment replica is located is not the node that received the query, the transaction manager 162 forwards the query to the appropriate node via the hypercubic communication network. 
     The DBMS software 252 at the node that receives the forwarded query (or at the original node if the query did not need to be forwarded) executes the query, creates log records indicating data table records changed by executing the query, and forwards a copy of each log record to the data processor(s) on which is stored the standby (or other additional) replica of the effected database table fragment. The DBMS software 252 at the node that receives the log record copy updates the standby replica of the effected database table fragment in accordance with the information in the received log record copy. 
     In practice, the initial entries in the data dictionary 158 are made at the time the system is first put into service. Typically, very few new data tables are created after the system is first put into service, and the number of nodes in the system is changed infrequently. As a result, the only tables in the data dictionary that undergo changes on a regular ongoing basis are the SysFragment and SysReplica Tables 236 and 240. If the data dictionary 158 includes tables with data access control information and tables with information regarding the various procedures used to access data, those data dictionary tables may also undergo frequent changes, but those tables and their operation are not relevant here. 
     When all the nodes of the database server system are operating normally, and there have been no node failures in the recent past, each data table has just two levels of entries in the SysFragment Table 236: a top level fragment entry for the entire table, and one entry for each fragment of the table. The top level (called level 0) entry lists all the subfragment IDs for the table fragments, and each of the next level entries indicates that it has zero subfragments and lists only the replica IDs for the corresponding level 1 table fragment. 
     In reality, a heavily used system with sixteen or more data processors that are in use 24 hours per day will typically suffer node faults in random fashion. For instance, a particular system might average one node failure per week, but only once every thirty years or so will two or more nodes fail within a few (e.g., fifteen) minutes of each other, and occasionally there may be a power supply failure that causes four nodes to fail simultaneously. 
     Node failures are detected by neighboring nodes using a signalling protocol (Node Status Monitoring Software 250 in FIG. 6) that requires that each node to send its neighbors predefined signals, sometimes called &#34;I&#39;m alive&#34; signals, on a periodic basis (e.g., once per millisecond). Each node is connected to several neighboring nodes, for example in accordance with the hypercubic interconnection scheme of the preferred embodiment. When a node fails to receive the expected periodic signals from one of its neighbors, a predefined status verification procedure is executed that attempts to communicate with the neighboring node and then declares the neighboring node to be unavailable if its attempts are unsuccessful. Such procedures are well known to those skilled in the art. One added feature of the node status monitoring procedure 250 that is useful in the present invention is that the status checking procedure checks the status of all nodes in a group, for the purpose of detecting group failures, any time that two or more nodes from the same node group are detected to have failed. 
     When a node determines that one its neighboring nodes is not available, it sends a node-failure message to all its neighbors, which in turn retransmit the node-failure message to their neighbors until the &#34;wavefront&#34; of messages reaches all the nodes in the system. The functional nodes in the system which receive the node-failure message send acknowledgement messages back to node which originated the node-failure message. After collecting all such acknowledgements, the originating node then sends out a &#34;new configuration&#34; message to all the nodes in the system indicating the set of functional nodes in the system. 
     Each node that is still operational responds to the new configuration message by invoking the fragmentation control software 160 (present on every node), which then causes the following sequence of steps to be performed. First, the node inspects its own data dictionary to determine which data tables are affected by the node failure(s) and which new table subfragments will have to be created and stored at that node. At each operational node, fragment replicas status values are updated in the data dictionary. For example, for each primary fragment replica that resided on the failed node, the fragment status is changed to &#34;refragmenting&#34;, and the corresponding hot standby fragment replica is given the role of &#34;primary&#34;. Each node then creates the files necessary for storing the new subfragments assigned to that node (in accordance with the system&#39;s predefined refragmentation procedures in the fragmentation control software 160), sends messages with that information to the other nodes so that all the nodes can update their data dictionaries accordingly, and then goes through the process of creating each new subfragment replica that is to be stored at that node. As the process of generating each new subfragment replica is completed, its status is changed to &#34;available&#34; and a message to that effect is sent to all the other nodes. This process continues until all the new subfragment replicas have been built. In general, each node modifies its own data dictionary entries in accordance with the status messages received from other nodes. Because every node has the same fragmentation control software 160 for data table refragmentation and for data table rebuilding (after a failed node comes back on line), there is no need to coordinate activities between nodes other than the transmission of status messages. 
     After the system has responded to a node failure, the process of accessing data records is impacted by the changed fragment and replica records in the data dictionary. In particular, more levels of the SysFragment and SysReplica Tables may have to be searched to find the node to which a transaction should be sent. In addition, additional levels of these system tables may need to be searched when determining the nodes to which copies of the log records for a transaction should be sent (for the purpose of keeping hot standby and other replicas up to date). 
     When a failed node is repaired, the above described fragmentation process is reversed. In particular, the repaired node goes through a process of rebuilding its data table fragment replicas, and sends status messages to all the other nodes as each recovered table fragment replica is ready to resume its normal role. The other nodes update their data dictionary entries accordingly, and also delete subfragment replica files no longer needed. 
     When an entire group of nodes fails simultaneously, such as when a power supply failure occurs, the subfragmentation procedure is essentially unchanged, except that the number of target nodes for the new subfragments is reduced. In the preferred embodiment, to ensure that no single group failure can cause data to be unavailable, each half of the system has at least two separate groups of nodes that share no resources with the other node groups. As a result, when a group of nodes fails, at least one copy of every table fragment can be found elsewhere in the system, enabling a new replica thereof to be generated. 
     While the present invention has been described with reference to a few specific embodiments, the description is illustrative of the invention and is not to be construed as limiting the invention. Various modifications may occur to those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims.