Method, system and program for recording changes made to a database

• US 20060020634A1
• Filed: 07/20/2004
• Published: 01/26/2006
• Est. Priority Date: 07/20/2004
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Huras, Matthew Albert, Posner, Sarah, Zheng, Roger Luo Quan, Fleet, James William Van
• Application Number:
  US10/896,272
• Publication Number:
  US 20060020634A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

A method, computer program product and database management system for recording a change to a database in a log including a plurality of log records. The database management system is capable of concurrently processing and logging multiple database changes. A tracking descriptor is used in conjunction with first and second identifiers for each log record to reduce the amount of logic executed using latching for each log record.

Claims

1. For a database management system, the database management system being capable of concurrently processing and logging multiple database changes, a method for recording a change to a database in a log, the log including a plurality of log records, the method comprising the steps of:

generating a first identifier for mapping to an address in a log buffer for storing a log record describing the change;

generating a second identifier for allocating a tracking descriptor for storing information concerning the log record;

allocating a tracking descriptor for the log record from available tracking descriptors using said second identifier; and

storing the log record at the address in the log buffer.

2. The method as claimed in claim 1, further comprising the steps of:

updating the information stored in the tracking descriptor after the occurrence of each of a plurality of predetermined events; and

copying one or more log records from the log buffer to permanent storage after the information stored in the tracking descriptor has been updated to indicate the one or more log records have been stored in the log buffer.

3. The method as claimed in claim 2, wherein the plurality of predetermined events comprises the group of:

allocating the tracking descriptor for the log record, storing the log record at the address in the log buffer, copying the log record from the log buffer to permanent storage, and determining that the log record requires a timestamp.

4. The method as claimed in claim 3, wherein the step of copying one or more log records from the log buffer to permanent storage comprises the steps of:

reading the status information stored in the tracking descriptors to identify one or more log records which have been copied to the log buffer; and

copying the one or more log records from the log buffer to permanent storage; and

releasing the tracking descriptor for the log record so that the tracking descriptor is available for allocation to a new log record.

5. The method as claimed in claim 3, further comprising, after the step of updating the information stored in the tracking descriptor, prior to the step of copying one or more log records from the log buffer to permanent storage, the steps of:

reading the status information stored in the tracking descriptor to determine if the log record requires a timestamp; and

if the log record requires a timestamp,

generating a timestamp for the log record, and

storing the timestamp in the log record.

6. The method as claimed in claim 2, wherein the information stored in the tracking descriptor includes:

said first identifier, a size of the log record, and status information concerning the occurrence of a predetermined event affecting the log record.

7. The method as claimed in claim 2, after the step of copying one or more log records from the log buffer to permanent storage, the step of:

increasing a read limit address by an amount proportional to the amount of log data comprised by the one or more log records copied from the log buffer to permanent storage, log records below said read limit address being protected from overwriting during reading.

8. The method as claimed in claim 1, wherein said first identifier has a value derived from a counter which is incremented by the size of the log record, and said second identifier has a value derived from a counter which is incremented for each said second identifier generated.

9. The method as claimed in claim 1, wherein said first identifier is associated with the address in the log buffer for storing the log record.

10. The method as claimed in claim 1, wherein the steps of generating a first identifier and generating a second identifier, comprise the steps of:

implementing a logic latch;

while the logic latch is implemented,

generating said first identifier;

generating said second identifier; and

releasing the logic latch.

11. The method as claimed in claim 1, wherein the steps of generating a first identifier and generating a second identifier, comprise the steps of:

obtaining a value for said first identifier to be generated; and

generating said second identifier;

when the value for said first identifier has not been affected by a second log record describing another database change, generating said first identifier;

when the value for said first identifier has been affected by a second log record describing another database change,

allocating a second tracking descriptor for the log record from available tracking descriptors using said second identifier, and

updating the information stored in the second tracking descriptor to indicate the second tracking descriptor has been allocated; and

repeating the steps of obtaining a value for said first identifier, generating said second identifier, and the conditional steps defined above until the value for said first identifier has not been affected by a log record.

12. The method as claimed in claim 1, wherein the step of storing the log record at the address in the log buffer comprises the steps of:

determining when any log record previously stored at the address in the log buffer to be copied to permanent storage; and

when any log record previously stored at the address in the log buffer has been copied to permanent storage, storing the log record at the address in the log buffer.

13. The method as claimed in claim 1, further comprising the steps of:

receiving a user request to read a log record;

preventing changes to a read limit address in the log buffer, log records below said read limit address being protected from overwriting during reading;

while the read limit address is prevented from changing,

when the address of the log record to be read is below said read limit address,

reading the log record from the log buffer, and

when the address of the log record to be read is above said read limit address,

reading the log record from permanent storage; and

releasing said read limit address to allow it to change.

14. A computer program product having a computer readable medium tangibly embodying code for directing a database management system to record a change to a database in a log, the log including a plurality of log records, the database management system being capable of concurrently processing and logging multiple database changes, the computer program product comprising:

code for generating a first identifier for mapping to an address in a log buffer for storing a log record describing the change;

code for generating a second identifier for allocating a tracking descriptor for storing information concerning the log record;

code for allocating a tracking descriptor for the log record from available tracking descriptors using said second identifier; and

code for storing the log record at the address in the log buffer.

15. The computer program product as claimed in claim 14, further comprising:

code for updating the information stored in the tracking descriptor after the occurrence of each of a plurality of predetermined events; and

code for copying one or more log records from the log buffer to permanent storage after the information stored in the tracking descriptor has been updated to indicate the one or more log records have been stored in the log buffer.

16. The computer program product as claimed in claim 15, wherein the plurality of predetermined events comprises the group of:

allocating the tracking descriptor for the log record, storing the log record at the address in the log buffer, copying the log record from the log buffer to permanent storage, and determining that the log record requires a timestamp.

17. The computer program product as claimed in claim 14, wherein the code for generating a first identifier for mapping to an address in a log buffer for storing a log record describing the change and the code for generating a second identifier for allocating a tracking descriptor for storing information concerning the log record is executed in sequence so that said first identifier and said second identifier are generated in order for each log record.

18. The computer program product as claimed in claim 14, further comprising:

code for reading the status information stored in the tracking descriptor to determine if the log record requires a timestamp; and

code responsive to log records requiring a timestamp for,

generating a timestamp for the log record, and

storing the timestamp in the log record.

19. A database management system for recording a change to a database in a log, the log including a plurality of log records, the database management system being capable of concurrently processing and logging multiple database changes, the database management system comprising:

a log buffer;

a logger module responsive to a change to the database, the logger module including,

a module for generating a first identifier for mapping to an address in a log buffer for storing a log record describing the change;

a module for generating a second identifier for allocating a tracking descriptor for storing information concerning the log record;

a module for allocating a tracking descriptor for the log record from available tracking descriptors using said second identifier; and

a module for storing the log record at the address in the log buffer.

20. The database management system as claimed in claim 19, further comprising:

a module for updating the information stored in the tracking descriptor after the occurrence of each of a plurality of predetermined events; and

a module for copying one or more log records from the log buffer to permanent storage after the information stored in the tracking descriptor has been updated to indicate the one or more log records have been stored in the log buffer.