Methods and apparatus for managing a database in a distributed operating environment

• US 5,940,827 A
• Filed: 11/10/1997
• Issued: 08/17/1999
• Est. Priority Date: 03/31/1995
• Status: Expired due to Term

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Cattell, Roderic G., Hapner, Mark W.
• Primary Examiner(s): Lintz, Paul R.
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US08/968,516
• Time in Patent Office: 645 Days
• Field of Search: 395/185.1, 395/68.3, 707/103, 707/201, 707/10, 707/204, 707/8
• US Class Current: 707/703
• CPC Class Codes: G06F 12/0837 with software control, e.g. non-cacheable data
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/966 Distributed
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A variety of methods and apparatus for managing a database in a object oriented environment are disclosed. According to the present invention, a database is provided which includes a database cache and a persistent database portion. Clients of the database are able to write quickly and asynchronously to the database cache, which may be located in transient memory such as random access memory. In order to maintain consistency between the state of the client and the state in the database, the data in the database cache must be written to the persistent database portion. In preferred embodiments a time commit thread executing in a computer process will, in single operations performed at predetermined intervals and when predetermined conditions are met, commit the data in the database cache into the persistent database portion. Thus through the strategies of the present invention, a single client database can have multiple clients. Clients of the database may be a variety of computer entities which require a mechanism for maintaining persistent state. In particular, objects are contemplated. In an apparatus embodiment of the present invention, a computer system having a central processing unit, a transient memory, a persistent memory, and a database is disclosed.

Claims

1. A computer implemented method for managing a database resident in a computer system, the computer system being intended for use in a distributed object operating environment, the database including a database cache and a persistent database portion, the database operable to maintain data persistently for a plurality of clients, said database cache capable of maintaining concurrently data received from multiple clients, which clients intended said data to be maintained persistently by said database, said persistent database portion structured as a single client database, the method including the computer controlled steps of:

detecting that a cache dirty variable has been set to a first state that indicates that said database cache includes certain data received from at least one of said plurality of clients, said client intending said certain data to be maintained persistently by said database,

performing a data commit operation which commits to said persistent database portion said certain data intended to be maintained persistently by said database; and

after the performance of the data commit operation, setting said cache dirty variable to a second state that indicates that said database cache does not include data which must be committed to said persistent database portion.

2. A computer implemented method as recited in claim 1 wherein the computer system further includes a cache free condition variable having a cache commit request variable and a transaction counter, the method further comprising the step of performing a data write operation that writes the certain data into the database cache, the data write operation including the computer controlled steps of:

incrementing said transaction counter by a predetermined value, said transaction counter being indicative of the number of active data write operations;

writing the certain data intended for said persistent database portion into said database cache; and

decrementing said transaction counter by said predetermined value after said writing step is complete.

3. A computer implemented method as recited in claim 2 wherein the computer system further includes an associated cache free mutex, the data write operation further comprising the computer controlled steps of:

locking said cache free mutex prior to the transaction counter incrementing step thereby protecting said cache free condition variable from other operations;

unlocking said cache free mutex after the transaction counter incrementing step has been performed;

locking said cache free mutex prior to the transaction counter decrementing step; and

unlocking said cache free mutex after the transaction counter decrementing step has been performed.

4. A computer implemented method as recited in claim 2 wherein the data write operation further includes the step of prior to said step of incrementing the transaction counter, determining whether the cache commit request variable indicates that the data commit operation is active, wherein when it is determined that the data commit operation is active, the transaction counter incrementing, data writing and transaction counter decrementing steps are delayed until the cache commit request variable transitions to indicate that the data commit operation is not active.

5. A computer implemented method as recited in claim 4 wherein when it is determined that the data commit operation is not active, the transaction counter incrementing, data writing and transaction counter decrementing steps are performed substantially immediately.

6. A computer implemented method as recited in claim 4 wherein said step of performing said data commit operation includes the computer controlled step of setting the cache commit request variable to indicate that said data commit operation is active.

7. A computer implemented method as recited in claim 6 wherein the step of performing said data commit operation further comprises the computer controlled step of:

(a) determining whether there are any active data write operations based on the value stored in the transaction counter, wherein when it is determined that no data write operations are active the data in the database cache is written into the persistent database portion and the cache commit request variable is set to indicate that said data commit operation is not active.

8. A computer implemented method as recited in claim 7 wherein when the cache commit request variable is set to indicate that the data commit operation is not active, a cache commit request variable wakeup call is broadcast.

9. A computer implemented method as recited in claim 7 wherein when it is determined that there is an active data write operation, the step of performing a data commit operation further includes the computer controlled steps of:

(b) waiting for the reception of a wakeup call indicating that said transaction counter has changed to be received; and

(c) repeating step (a) of claim 7.

10. A computer implemented method as recited in claim 9 wherein when the cache commit request variable is set to indicate that the data commit operation is not active, a cache commit request variable wakeup call is broadcast.

11. A computer implemented method as recited in claim 2 wherein the steps of performing a data write operation and setting a cache dirty variable to indicate that said database cache includes data intended for said persistent database portion are performed by an object resident in a computer process executing on said computer system.

12. A computer implemented method as recited in claim 2 wherein the steps of performing a data commit operation and setting a cache dirty variable to indicate that said database cache does not include data intended for said persistent database portion are performed by a time commit thread executing in said computer system.

13. A computer implemented method for performing an orderly shutdown of a time commit thread as described in claim 12, the method including the computer controlled steps of receiving a start shutdown command and determining whether there is any data in the database cache based upon the state of the cache dirty variable, wherein when it is determined that there is no data in the database cache, a signal is sent indicating that the shutdown is complete.

14. A computer implemented method for performing an orderly shutdown of a time commit thread as described in claim 12, the method including the computer controlled steps of receiving a start shutdown command and determining whether there is any data in the database cache based upon the state of the cache dirty variable, wherein:

when it is determined that there is data in the database cache, a determination is made as to whether there are any active data write operations based on the value of the transaction counter; and

when it is determined that there are no active data write operations, a data commit operation is performed and a signal is sent indicating that the shutdown is complete.

15. A computer implemented method for performing an orderly shutdown of a time commit thread as described in claim 12, the method including the computer controlled steps of receiving a start shutdown command and determining whether there is any data in the database cache based upon the state of the cache dirty variable, wherein:

when it is determined that there is data in the database cache, a determination is made as to whether there are any active data write operations based on the value of the transaction counter; and

when it is determined that there are active data write operations, a warning is transmitted indicating to all active data write operations that an abort is impending, all active data write operations are aborted, a signal is sent indicating that the shutdown is complete.

16. A computer implemented method as recited in claim 2 wherein said step of performing said data commit operation includes the computer controlled step of setting a cache commit request variable to indicate that said data commit operation is active.

17. A computer implemented method as recited in claim 2 wherein:

the computer system further includes an associated cache free mutex;

the data write operation further includes the computer controlled steps of prior to said step of incrementing the transaction counter, determining whether the cache commit request variable indicates that the data commit operation is active, wherein when it is determined that the data commit operation is active, the transaction counter incrementing, data writing and transaction counter decrementing steps are delayed until the cache commit request variable transitions to indicate that the data commit operation is not active, and wherein when it is determined that the data commit operation is not active, the transaction counter incrementing, data writing and transaction counter decrementing steps are performed substantially immediately;

the step of performing said data commit operation includes the computer controlled steps of,

setting the cache commit request variable to indicate that said data commit operation is active,

determining whether there are any active data write operations based on the value stored in the transaction counter, wherein when it is determined that no data write operations are active the data in the database cache is written into the persistent database portion, and the cache commit request variable is set to indicate that said data commit operation is not active; and

the cache free mutex is unlocked prior to and unlocked after each transaction counter incrementing step, each transaction counter decrementing step, and each cache commit request variable setting step.

18. A computer implemented method for performing a data write operation to a database cache portion of a database being intended to reside in a computer system, the database cache portion suitable for concurrently maintaining data written thereto by a plurality of database clients, the database further including a persistent database portion operable for single client use only, the database operable to maintain data persistently for said plurality of database clients, the method including the computer controlled steps of:

setting a cache dirty variable to a state that indicates that the database cache contains data which is intended to be maintained persistently by said database;

incrementing by a predetermined value a transaction counter, the transaction counter indicating the number of active data write operations;

writing the data to be maintained persistently by said database to the database cache after the transaction counter incrementing step; and

decrementing the transaction counter by the predetermined value in conjunction with the data writing step.

19. A computer implemented method as recited in claim 18 wherein the cache dirty variable is one element of a condition variable cache dirty which further includes a corresponding cache dirty mutex, the method further including the computer controlled steps of:

locking the cache dirty mutex prior to the step of setting the cache dirty variable; and

unlocking the cache dirty mutex after the step of setting the cache dirty variable.

20. A computer implemented method as recited in claim 18 wherein the transaction counter is an element of a condition variable cache free which further includes a cache commit request variable and a corresponding cache free mutex, the method further including the computer controlled steps of:

locking the cache free mutex prior to the transaction counter incrementing step;

determining a state of the cache commit request variable after the step of locking the cache free mutex;

prior to the transaction counter incrementing step, waiting in a sleep state when the state of the cache commit request variable indicates that a cache commit operation is active, wherein the waiting step terminates upon the transition of the state of the cache commit request variable;

unlocking the cache free mutex in conjunction with the transaction counter incrementing step.

21. A computer implemented method as recited in claim 20 further including the computer controlled steps of:

locking the cache free mutex prior to the transaction counter decrementing step; and

unlocking the cache free mutex in conjunction with the transaction counter decrementing step.

22. A computer implemented method as recited in claim 18 wherein the method is performed by a client of the database.

23. A computer implemented method as recited in claim 22 wherein the client is an object resident in the computer system.

24. A persistent computer database arranged for persistently maintaining data for a plurality of clients, the persistent computer database comprising:

a cache database portion arranged to receive and store client data via data write operations performed by a plurality of database clients;

a persistent database portion being arranged to receive data from and store data for a single client, and

wherein a data commit operation is operable to commit said client data stored in said transient cache database portion into said persistent database portion such that from the perspective of said persistent database portion it appears that said persistent database portion only has a single client which is said transient cache database portion.

25. A persistent computer database as recited in claim 24 wherein said cache database portion and said persistent database portion are resident on a first computer system.

26. A persistent computer database as recited in claim 24 wherein said cache database portion is resident on a first computer system and said persistent database portion is resident on a second computer system, said first and second computer systems coupled together via a computer network.

27. A persistent computer database as recited in claim 24 wherein said cache database portion and said persistent database portion are resident on a first computer system, and at least one of said plurality of clients is resident on a second computer system that is coupled to said first computer system by a computer network.

28. A computer implemented method for managing a database resident in a computer system, the computer system being intended for use in a distributed object operating environment, the database including a database cache and a persistent database portion, the database operable to maintain data persistently for a plurality of clients, said database cache capable of maintaining concurrently data received from multiple clients, which clients intended said data to be maintained persistently by said database, said persistent database portion structured as a single client database, the method including the computer controlled steps of:

performing a data write operation that writes data into said database cache, said data written into the cache being intended for storage in the persistent database portion;

setting a cache dirty variable to a first state that indicates that the database cache includes data intended for storage in the persistent database portion;

detecting that a cache dirty variable has been set to a first state that indicates that said database cache includes certain data received from at least one of said plurality of clients, said client intending said certain data to be maintained persistently by said database,

performing a data commit operation which commits to said persistent database portion said certain data intended to be maintained persistently by said database; and

after the performance of the data commit operation, setting said cache dirty variable to a second state that indicates that said database cache does not include data which must be committed to said persistent database portion.