Methods and apparatus for managing a database in a distributed object operating environment using persistent and transient cache

• US 5,727,203 A
• Filed: 03/31/1995
• Issued: 03/10/1998
• 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: Hapner, Mark W., Cattell, Roderic G.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US08/414,119
• Time in Patent Office: 1,075 Days
• Field of Search: 364/200, 395/425, 395/600, 395/700, 395/474, 395/250, 395/650, 395/608, 395/472, 395/614, 395/705
• US Class Current: 1/1
• 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 system for use in a distributed object operating environment, said computer system comprising:

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device; and

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache.

2. A computer system as described in claim 1 further including a computer process executing on the computer system, said transient database cache being resident within said computer process.

3. A computer system for use in a distributed object operating environment, said computer system comprising:

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device;

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache to said persistent database portion as if the data intended for the persistent database is coming from a single client.

a computer process executing on the computer system, said transient database cache controlled within said computer process; and

a cache dirty condition variable resident in said computer process, said cache dirty condition variable having a cache dirty variable and a cache dirty mutex.

4. A computer system as described in claim 3 further including:

a cache dirty lock mechanism for locking and unlocking said cache dirty mutex; and

a cache dirty setting mechanism for setting and resetting said cache dirty variable, wherein setting said cache dirty variable indicates that data which is intended for said persistent database portion is resident in said transient database cache.

5. A computer system for use in a distributed object operating environment, said computer system comprising:

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device;

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache to said persistent database portion;

a computer process executing on the computer system, said transient database cache controlled within said computer process; and

a cache free condition variable resident in said computer process, the cache free condition variable having a cache free mutex, a cache commit request variable, a force abort variable, and a transaction counter.

6. A computer system as described in claim 5 further including:

a cache free lock mechanism for locking and unlocking said cache free mutex;

a cache free setting mechanism for setting and resetting said cache commit request variable, wherein setting said cache commit request variable indicates that a data commit operation is in process; and

an arithmetic device for incrementing and decrementing said transaction counter by a predetermined number, wherein the value of said transaction counter is indicative of the number of active data write operations.

7. A computer system for use in a distributed object operating environment, said computer system comprising:

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device;

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache to said persistence database portion as if the data intended for the persistence database is coming from a single client.

a computer process executing on the computer system, said transient database cache controlled within said computer process; and

a kill time commit condition variable having a kill time commit mutex and a kill bit.

8. A computer system as described in claim 7 further including:

a kill lock mechanism for locking and unlocking said kill time commit condition mutex; and

a kill set mechanism for setting and resetting said kill bit, wherein setting the kill bit indicates that a time commit thread cleanup is requested.

9. A computer system for use in a distributed object operating environment, said computer system comprising:

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device; and

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache to said persistent database portion as if the data intended for the persistent database is coming from a single client.

a database client operable to write certain data to said transient database, said certain data intended to be maintained persistently in said database.

10. A computer system as described in claim 9 wherein said database client is resident in said computer process.

11. A computer system as described in claim 10 wherein said database client is an object.

12. A distributed object operating environment comprising:

a plurality of computer systems, each of said computer systems including;

a central processing unit;

transient memory including random access memory;

persistent memory including a mass storage device; and

a database including;

a transient database cache resident in said transient memory, said transient database cache being arranged to receive and store client data via data write operations performed by a plurality of database clients; and

a persistent database portion resident in said persistent memory, said persistent database portion being arranged to receive and store cache data via data commit operations, said data commit operation being operable to commit said client data from said transient database cache;

to said persistent database portion as if the data intended for the persistent database is coming from a single client; and

a computer network interconnecting said plurality of computer systems.

13. A computer implemented method for performing a data write operation to a transient database cache portion of a database being intended to reside in a computer system, the database further including a persistent database portion, the database operable to maintain data persistently for a plurality of database clients, the method including the computer controlled steps of:

setting a cache dirty variable to a state that indicates that the transient database cache contains data which is intended for the persistent database portion;

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

writing the data intended for the persistent database portion to the transient database cache after the transaction counter incrementing step, the data being written into the cache by a one of said plurality of database clients, said transient database cache operable to simultaneously store data received from multiple write operations; and

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

14. A computer implemented method as recited in claim 13 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.

15. A computer implemented method as recited in claim 13 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.

16. A computer implemented method as recited in claim 15 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.

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

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

19. 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 transient database cache and a persistent database portion, the database operable to maintain data persistently for a plurality of database clients, the method including the computer controlled steps of:

performing a data write operation that writes data into said transient database cache, said data written into the cache by a one of said plurality of database clients, said data being intended for storage in the persistent database portion, said transient database cache operable to simultaneously store data received from multiple data write operations;

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

performing a data commit operation which commits said data intended for said persistent database portion to said persistent database portion, the data commit operation being performed after the cache dirty variable has been set to the first state, the data commit operation operable to commit data in said transient data cache as if the data intended for the persistent database portion is coming from a single client; and

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

whereby said database may maintain data persistently for the plurality of database clients in said persistent database portion as if only a single client were using said persistent database portion.

20. A computer implemented method as recited in claim 19 wherein the computer system further includes a cache free condition variable having a cache commit request variable and a transaction counter and wherein said step of performing a data write operation includes 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 data intended for said persistent database portion into said transient database cache; and

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

21. A computer implemented method as recited in claim 20 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.

22. A computer implemented method as recited in claim 20 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.

23. A computer implemented method as recited in claim 22 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.

24. A computer implemented method as recited in claim 22 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.

25. A computer implemented method as recited in claim 24 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 transient 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.

26. A computer implemented method as recited in claim 25 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.

27. A computer implemented method as recited in claim 25 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.

28. A computer implemented method as recited in claim 27 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.

29. A computer implemented method as recited in claim 20 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 transient 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.

30. A computer implemented method as recited in claim 19 wherein the steps of performing a data write operation and setting a cache dirty variable to indicate that said transient 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.

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

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

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

when it is determined that there is data in the transient 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.

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

when it is determined that there is data in the transient 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.

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

36. A computer implemented method for committing data from a transient database cache to a persistent database portion, the transient database cache and the persistent database portion each being an element of a database being intended to reside in a computer system, the database operable to maintain data persistently for a plurality of database clients, the transient database cache operable to simultaneously store data received from multiple data write operations, the computer system being suitable for use in a distributed object operating environment, the method including the computer controlled steps of:

determining whether a cache dirty variable indicates that the transient database cache includes data intended for the persistent database portion;

setting a cache commit request variable to indicate that a commit data operation is in progress when it is determined that the transient database cache includes data intended for the persistent database portion;

after the cache commit request variable setting step, determining whether a transaction counter indicates that data write operations are active, the data write operations being operable to write data to the transient database cache;

committing data in the transient database cache to the persistent database portion when the transaction counter indicates that no data write operations are active; and

after the committing data step, setting the cache dirty variable to indicate that the transient database cache does not include data intended for the persistent database portion.

37. A computer implemented method as recited in claim 36 wherein the cache dirty variable is an element of a cache dirty condition variable 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 cache dirty variable determining step;

simultaneously entering a sleep state and unlocking the cache dirty mutex when the cache dirty variable indicates that the transient database cache does not include data intended for the persistent database portion; and

locking the cache dirty mutex in response to receiving a wakeup call indicating the cache dirty variable has changed its value.

38. A computer implemented method as recited in claim 36 wherein the cache commit request variable and the transaction counter are elements of a cache commit condition variable which further includes a corresponding cache commit mutex, the method further including the computer controlled step of locking the cache mutex prior to the step of setting the cache commit request variable.

39. A computer implemented method as recited in claim 38 further including the following computer controlled steps performed prior to the cache commit request variable setting step:

entering a timed sleep state when the transaction counter indicates that data write operations are in progress;

waking up when the timed sleep state terminates; and

determining if the transaction counter indicates that data write operations are still in progress.

40. A computer implemented method as recited in claim 36 wherein the cluster dirty variable is an element of a cluster dirty condition variable, the method further including the computer controlled steps of:

locking the cluster dirty mutex prior to the steps of setting the cluster dirty variable; and

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