System for database integrity with multiple logs assigned to client subsets

• US 5,499,367 A
• Filed: 10/27/1994
• Issued: 03/12/1996
• Est. Priority Date: 11/15/1991
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle Corporation
• Inventors: Kabcenell, Dirk A., Howard, Forrest W., Miner, Robert N., Bamford, Roger J.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): AMSBURY, WAYNE P
• Application Number:
  US08/330,100
• Time in Patent Office: 502 Days
• Field of Search: 395/650, 395/575, 395/600
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery

Abstract

The present invention provides a distributed log system where the logs are distributed on a per client basis. That is, the clients are partitioned into subsets. Each subset of clients is assigned a log, and the the redo records of those clients are maintained in that log. This reduces contention bottlenecks, because the number of clients writing to any one log is limited. Also, all of a client'"'"'s changes are stored in a single log. During a recovery process, the changes for a block of data may be stored in different logs. For proper recovery, the changes must be applied to the database in the order in which they were originally made. The present invention provides a system for ordering the log entries in the correct order by using a "sequence number". Each page of data in the database has an associated sequence number. When a change is made to that page, the sequence number is incremented. The new sequence number is written to the log along with the change information. To minimize overhead, the sequence number is structured as a two part value. The first part of the value is an "incarnation number" that is increased whenever the associated change assigns a new value to the entire data block that is independent of its prior value, such as the change that initiates a block.

Claims

1. A method of distributing log entries of transactions initiated by a plurality of clients commonly accessing at least one database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients, each of said plurality of clients commonly accessing said at least one database, each of said plurality of clients initiating transactions with said at least one database, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a different transaction log buffer associated with each one of said plurality of subsets of clients; and

for each transaction of one of said plurality of clients, storing a transaction log entry in said different transaction log buffer associated with the subset of clients that includes the client that initiated said transaction.

2. The method of claim 1 further including the steps of:

providing in a second memory means a transaction log for each transaction log buffer;

storing said transaction log entry in said transaction log.

3. The method of claim 2 further including the step of providing, in a third memory means, a cache buffer;

said cache buffer for storing a copy of a data block from said database upon which a transaction is executed.

4. The method of claim 1 wherein said first memory means comprises a random access memory (RAM).

5. The method of claim 2 wherein said second memory means comprises a disk drive.

6. The method of claim 1 wherein each said transaction is associated with a data block, said data block being a subdivision of said database.

7. The method of claim 6 further including the steps of:

providing a sequence number for each said data block;

incrementing the sequence number associated with said data for each transaction changing said data block.

8. The method of claim 7 further including the steps of:

providing an incarnation number for each said data block;

increasing said incarnation number associated with said data block for each transaction changing said data block, said changing being an initializing of said data block;

setting said sequence number for said data block to an initial value when said incarnation number is increased.

9. A database system comprising:

first storage means for storing data blocks, said data blocks being subdivisions of a database;

a plurality of clients, each client of said plurality of clients commonly accessing said database, each client of said plurality of clients initiating transactions with said database;

first and second subsets of said plurality of clients each of said subsets of clients having at least one client of said plurality of clients, clients of said first subset not being clients of said second subset;

cache buffer means coupled to said first storage means and to said first and second subset of clients, said cache buffer means for storing copies of said areas of data from said first storage means;

first and second transaction log buffer means coupled to said first and second subsets of clients respectively, said first and second transaction log buffer means for temporarily storing a log entry for each transaction initiated by a client of said first and second subset of clients respectively.

10. The database system of claim 9 further including:

first and second log storage means coupled to said first and second log buffer means respectively for permanently storing a log entry for each transaction of said first and second subset of clients respectively.

11. The database system of claim 9 wherein said first storage means comprises a disk drive.

12. The database system of claim 9 wherein said cache buffer means comprise random access memory (RAM).

13. The database system of claim 9 wherein said first and second transaction log buffer means comprise random access memory (RAM).

14. The database system of claim 9 wherein each of said data blocks includes a sequence number.

15. The database system of claim 14 further including sequence number incrementing means for incrementing a sequence number associated with said data block for each transaction changing said data block.

16. The database system of claim 15 wherein each of said data blocks further has an associated incarnation number.

17. The database system of claim 16 further including incarnation number increasing means for increasing an incarnation number associated with a block of data for each transaction initializing said data block.

18. The database system of claim 17 wherein said sequence number incrementing means sets a sequence number of a data block to a first value when the incarnation number of said data block is increased.

19. A method of providing a log of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients all accessing a single data abase, each of said subsets including at least one of said plurality of clients, each of said subsets having an associated log;

initiating a transaction on an original data block of said database by a client of one of said subsets of clients;

providing a copy of said data block to a cache buffer;

executing said transaction on said copy of said block data;

storing a transaction log entry of said transaction in a temporary memory means.

20. The method of claim 19 further including the step of storing said transaction log entry of said transaction in a permanent memory means.

21. The method of claim 20 wherein said permanent memory means comprises a disk drive.

22. The method of claim 19 wherein said temporary memory means comprises a random access memory (RAM).

23. The method of claim 19 further including the step of writing said copy of said data block over said original data block in said database.

24. The method of claim 19 further including the steps of:

providing a sequence number of said data block;

incrementing the sequence number associated with said data block for each transaction changing said data block.

25. The method of claim 24 further including the steps of:

providing an incarnation number for said data block;

increasing said incarnation number associated with said data block for each transaction initializing said data block;

setting said sequence number for said data blocks to an initial value when said incarnation number is increased.

26. A database system comprising:

first storage means for storing data blocks, each of said data blocks having a sequence number

first and second subsets of clients accessing a single database, each of said subsets of clients having at least one client;

cache buffer means coupled to said first storage means and to said first and second subset of clients respectively, said first and second cache buffer means for storing copies of said data blocks from said first storage means;

first and second transaction log buffer means coupled to said first and second subsets of clients respectively, said first and second transaction log buffer means for temporarily storing a log entry for each transaction of said first and second subset of clients respectively;

first and second log storage means coupled to said first and second log buffer means respectively for permanently storing a log entry for each transaction of said first and second subset of clients respectively;

sequence number incrementing means coupled to said first storage means for incrementing a sequence number associated with a data block for each transaction changing said data block.

27. The database system of claim 26 wherein said first storage means comprises a disk drive.

28. The database system of claim 26 wherein said first and second cache buffer means comprise random access memory (RAM).

29. The database system of claim 26 wherein said first and second transaction log buffer means comprise random access memory (RAM).

30. The database system of claim 26 wherein each of said data blocks has an associated incarnation number.

31. The database system of claim 30 further including incarnation number increasing means coupled to said first storage means for increasing an incarnation number associated with said data block for each transaction initializing said data block.

32. The database system of claim 31 wherein said sequence number incrementing means sets a sequence number of said data block to a first value when the incarnation number of said data block is increased.

33. A method of distributing log entries of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a transaction log buffer for each subset of clients;

for each transaction of a client, storing a transaction log entry in a transaction log buffer associated with the subset of clients that includes the client;

providing in a second memory means a transaction log for each transaction log buffer;

storing said transaction log entry in said transaction log.

34. A method of distributing log entries of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients all accessing a single database, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a transaction log buffer for each subset of clients;

for each transaction of a client, storing a transaction log entry in a transaction log buffer associated with the subset of clients that includes the client;

providing in a second memory means a transaction log for each transaction log buffer;

storing said transaction log entry in said transaction log;

providing, in a third memory means, a cache buffer;

said cache buffer for storing a copy of a data block from said database upon which a transaction is executed.

35. A method of distributing log entries of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients all accessing a single database, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a transaction log buffer for each subset of clients, said first memory means comprising a random access memory (RAM);

for each transaction of a client, storing a transaction log entry in a transaction log buffer associated with the subset of clients that includes the client;

providing in a second memory means a transaction log for each transaction log buffer;

storing said transaction log entry in said transaction log;

providing, in a third memory means, a cache buffer;

said cache buffer for storing a copy of a data block from said database upon which a transaction is executed.

36. A method of distributing log entries of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients all accessing a single database, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a transaction log buffer for each subset of clients, said first memory means comprising a random access memory (RAM);

for each transaction of a client, storing a transaction log entry in a transaction log buffer associated with the subset of clients that includes the client;

providing in a second memory means a transaction log for each transaction log buffer, said second memory means comprising a disk drive;

storing said transaction log entry in said transaction log;

providing, in a third memory means, a cache buffer;

said cache buffer for storing a copy of a data block from said database upon which a transaction is executed.

37. A method of distributing log entries of transactions of a plurality of clients accessing a database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients all accessing a single database, each of said subsets including at least one of said plurality of clients;

providing in a first memory means a transaction log buffer for each subset of clients, said first memory means comprising a random access memory (RAM);

for each transaction of a client, storing a transaction log entry in a transaction log buffer associated with the subset of clients that includes the client;

providing in a second memory means a transaction log for each transaction log buffer, said second memory means comprising a disk drive;

storing said transaction log entry in said transaction log, each transaction associated with a data block;

providing, in a third memory means, a cache buffer;

said cache buffer for storing a copy of a data block from said database upon which a transaction is executed.

38. A database system comprising:

first storage means for storing data blocks, said data blocks being subdivisions of a database, each of said data blocks having a sequence number contained therein;

at least one client coupled to said first storage means, said client for initiating transactions with said data blocks;

cache buffer means coupled to said first storage means and to said client, said cache buffer means for storing copies of said data blocks from said first storage means;

sequence number increasing means coupled to said first storage means for increasing a sequence number of a data block for each transaction changing said data block.

39. The database system of claim 38 wherein said first storage means comprises a disk drive.

40. The database system of claim 38 wherein said cache buffer means comprises random access memory (RAM).

41. The database system of claim 38 wherein each of said data blocks has an associated incarnation number.

42. The database system of claim 41 further including incarnation number increasing means coupled to said first storage means for increasing an incarnation number associated with said data block for each transaction initializing said data block.

43. The database system of claim 42 wherein said sequence number incrementing means sets a sequence number of said data lock to a first value when the incarnation number of said data block is increased.

44. A method of restoring a database comprising the steps of:

(a) providing a plurality of transaction logs, each of said transaction logs comprising a plurality of transactions, each of said transactions having a sequence number, each of said transaction logs associated with one of a plurality of subsets of clients of said database, each of said subsets of clients comprising at least one client;

(b) selecting one of said plurality of transaction logs;

(c) selecting a current transaction in said selected transaction log;

(d) reading said sequence number of said current transaction;

(e) comparing said sequence number of said current transaction with a current sequence number;

(f) performing said current transaction when said sequence number of said current transaction is one more than said current sequence number and applying current transaction to said database;

(g) setting said current sequence number equal to said sequence number of said current transaction;

(h) returning to step (c) when said sequence number of said current transaction is less than or equal to said current sequence number and when said sequence number of said current transaction is greater than one more than said current sequence number.

45. The method of claim 44 further including the steps of:

(i) returning to step (b) when all transactions in a selected transaction log have been selected;

performing steps (b) through (i) until all transactions of all transaction logs have been selected.

46. The method of claim 44 further including the steps of:

(i) providing an incarnation number for each transaction of said plurality of transaction logs;

(j) reading said incarnation number of said current transaction;

(k) comparing said incarnation number of said current transaction to a current incarnation number;

(l) returning to step (c) when said incarnation number of said current transaction is less than said current incarnation number;

(m) returning to step (d) when said incarnation number of said current transaction is greater than said current incarnation number.

47. The method of claim 46 further including the step of:

performing steps (b) through (m) until all transactions of all transaction logs have been selected.

48. A method of distributing log entries of transactions initiated by a plurality of clients commonly accessing at least one database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients, each of said plurality of clients commonly accessing said at least one database, each of said plurality of clients initiating transactions with said at least one database, each of said subsets including at least one of said plurality of clients, each said transaction being associated with a data block, said data block being a subdivision of said at least one database;

providing in a first memory means a different transaction log buffer associated with each one of said plurality of subsets of clients;

for each transaction of one of said plurality of clients, storing a transaction log entry in said different transaction log buffer associated with the subset of clients that includes the client that initiated said transaction;

providing a sequence number for each said data block associated with each said transaction;

incrementing the sequence number associated with said data block for each transaction changing said data block;

providing an incarnation number for each said data block;

increasing said incarnation number associated with said data block for each transaction initializing said data block;

setting said sequence number for said data block to an initial value when said incarnation number is increased;

wherein said method maintains and distributes log entries of transactions initiated by said plurality of clients prior to a recovery process of said at least one database.

49. The method of claim 48 wherein a storage means comprising a disk drive stores said data block.

50. The method of claim 48 wherein said first memory means is a random access memory (RAM).

51. The database system of claim 50 further comprising:

first and second log storage means coupled to said first and second log buffer means respectively for permanently storing a log entry for each transaction of said first and second subset of clients respectively.

52. The database system of claim 50 wherein said first storage means comprises a disk drive.

53. The database system of claim 50 wherein said cache buffer means comprise random access memory (RAM).

54. The database system of claim 50 wherein said first and second transaction log buffer means comprise random access memory (RAM).

55. A database system for distributing log entries of transactions initiated by a plurality of clients accessing a single database, said database system comprising:

first storage means for storing data blocks, said data blocks being subdivisions of a database, each of said data blocks including a sequence number and an incarnation number;

a plurality of clients, each client of said plurality of clients commonly accessing said database, each client of said plurality of clients initiating transactions with said database;

first and second subsets of said plurality of clients accessing said at least one database, each of said subsets of clients having at least one client belonging to said plurality of clients, clients of said first subset not being clients of said second subset;

cache buffer means coupled to said first storage means and to said first and second subset of clients, said cache buffer means for storing copies of said data blocks from said first storage means;

first and second transaction log buffer means coupled to said first and second subsets of clients respectively, said first and second transaction log buffer means for temporarily storing a log entry for each transaction initiated by a client of said first and second subset of clients respectively;

sequence number incrementing means for incrementing, for each transaction changing one of said data blocks, said sequence number included in each of said data blocks;

incarnation number increasing means for increasing, for each transaction initializing said data block, said incarnation number included in each of said data blocks;

said sequence number incrementing means setting said sequence number of a respective one of said data blocks to a first value when said incarnation number of said respective one of said data blocks is increased;

wherein said database system maintains and distributes log entries of transactions initiated by said plurality of clients prior to a recovery process of said at least one database.

56. A method of distributing log entries of transactions initiated by a plurality of clients commonly accessing at least one database, said method comprising the steps of:

dividing said plurality of clients into a plurality of subsets of clients, each of said plurality of clients commonly accessing said at least one database, each of said plurality of clients initiating transactions with said at least one database, each of said subsets including at least one of the said plurality of clients;

providing in a first memory means a different transaction log buffer associated with each one of said plurality of subsets of clients;

for each transaction of one of said plurality of clients, storing a transaction log entry in said different transaction log buffer associated with the subset of clients that includes the client that initiated the transaction, each transaction being associated with a data block, said data block being a subdivision of said at least one database;

for each said transaction log entry, providing a length of log entry field, an operation code field, a page address field, and incarnation number field, a sequence number field, and a variable length change data field.

57. The method of claim 56 further comprises the steps of:

providing a sequence number for each said data block;

incrementing said sequence number associated with said data block for each transaction changing said data block.

58. The method of claim 57 further including the steps of:

providing an incarnation number for each said data block;

increasing said incarnation number associated with said data block for each transaction initializing said data block.

59. The method of claim 58 further including the step of:

setting said sequence number for said data block to an initial value when said incarnation number is increased.

60. The method of claim 59 wherein said variable length change data field contains data describing changes corresponding to a respective transaction log entry.

61. The method of claim 60 wherein said length of log entry field indicates the length of data contained in said variable length change data field.

62. The method of claim 61 wherein said operation code field indicates a type of a respective transaction log entry.

63. The method of claim 62 wherein said type of said respective transaction log entry is selected from the group consisting of delete type, change type, and write type.

64. The method of claim 63 wherein said page address field indicates the address of a data page corresponding to a respective transaction log entry.

65. The method of claim 64 wherein said incarnation number filed indicates a respective incarnation number of said data page.

66. The method of claim 65 wherein said sequence number field indicates a respective sequence number of said data page.