Partially replicated distributed database with multiple levels of remote clients

• US 6,266,669 B1
• Filed: 08/12/1999
• Issued: 07/24/2001
• Est. Priority Date: 02/28/1997
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Lim, Peter S., Brodersen, Robert A., Chatterjee, Prashant
• Primary Examiner(s): Choules, Jack
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US09/373,128
• Time in Patent Office: 712 Days
• Field of Search: 707/10, 707/1, 707/4, 707/100, 707/202, 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A method of and system for collecting, storing, and retrieving data in a data base management system. The database management system includes a master database server (4), at least one workgroup server (315), and a plurality of workgroup user clients (310). The workgroup server (315) is interposed between the master database server (4) and said workgroup user clients (310). The method creating a transaction in a local database resident on one of the workgroup user clients (310), entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding to the transaction in an outbox of said workgroup user client (310). Next, the transaction file is copied to an inbox identified to the workgroup user client (310) and updating the transaction file into a workgroup database (305) resident on the workgroup server (315). The workgroup database (305) includes a transaction log.

Claims

1. A method of collecting, storing, and retrieving data in a multi-tier database management system having a master database server (4), an application server (303), at least one workgroup server (315), and a plurality of workgroup user clients (310), said application server (303) and said workgroup server (315) interposed between said master database server (4) and said workgroup user clients (310), said method comprising:

(a) creating a transaction in a local database resident on one of said workgroup user clients (310),

(b) entering the transaction into a transaction log resident on said workgroup user client (310),

(c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310),

(e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log;

(f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4),

(g) creating data files corresponding to the entries therein,

(h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and

(i) updating the transactions into a master database (3) on the master database server (4).

2. The method of claim 1 comprising carrying out in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310).

3. The method of claim 1 comprising carrying out in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log.

4. The method of claim 1 comprising carrying out in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).

5. The method of claim 1 comprising:

(1) carrying out in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(2) carrying out in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log; and

(3) carrying out in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).

6. An article of manufacture comprising a computer usable medium having computer readable program code means embodied therein for collecting, storing, and retrieving data in a multi-tier data base management system having a master database server (4), an application server (303), at least one workgroup server (315), and a plurality of workgroup user clients (310), said application server (303) and said workgroup server (315) interposed between said master database server (4) and said workgroup user clients (310), the computer readable program in said article of manufacture comprising computer readable program code for causing a computer to effect:

(a) creating a transaction in a local database resident on one of said workgroup user clients (310),

(b) entering the transaction into a transaction log resident on said workgroup user client (310),

(c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(d) copying said transaction file to an inbox resident on said workgroup server (315) and identified to the workgroup user client (310),

(e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log;

(f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4),

(g) creating data files corresponding to the entries therein,

(h) copying data files corresponding to an transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and

(i) updating the transactions into a master database (3) on the master database server (4).

7. The article of manufacture of claim 6 wherein said computer readable program code causes a computer to effect in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310).

8. The article of manufacture of claim 6 wherein said computer readable program code causes a computer to effect in the in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log.

9. The article of manufacture of claim 6 wherein said computer readable program code causes a computer to effect in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).

10. The article of manufacture of claim 6 wherein the computer readable program code causes the computer to effect:

(1) carrying out in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(2) carrying out in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log; and

(3) carrying out in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).

11. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for collecting, storing, and retrieving data in a multi-tier data base management system having a master database server (4), an application server (303), at least one workgroup server (315), and a plurality of workgroup user clients (310), said application server (303) and said workgroup server (315) interposed between said master database server (4) and said workgroup user clients (310), said method steps comprising:

(i) creating a transaction in a local database resident on the one of said workgroup user clients (310),

(ii) entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding thereto in an outbox of the workgroup user client (310);

(iii) copying said transaction file to an inbox resident on the workgroup server (315) and identified to the workgroup user client (310),

(iv) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log;

(v) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4),

(vi) creating data files corresponding to the entries therein,

(vii) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and

(viii) updating the transactions into a master database (3) on the master database server (4).

12. The program storage device of claim 11 further comprising:

(a) on one of said work group user clients;

(i) creating a transaction in a local database resident on the one of said workgroup user clients (310), (ii) entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding thereto in an outbox of the workgroup user client (310);

(b) on said workgroup server;

(i) copying said transaction file to an inbox resident on the workgroup server (315) and identified to the workgroup user client (310), and (ii) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log; and

(c) on said master database server;

(i) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (ii) creating data files corresponding to the entries therein, (iii) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (iv) updating the transactions into a master database (3) on the master database server (4).

13. The program storage device of claim 11 further comprising:

(a) on one of said work group user clients;

(i) creating a transaction in a local database resident on the one of said workgroup user clients (310), (ii) entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding thereto in an outbox of the workgroup user client (310).

14. The program storage device of claim 11 further comprising:

(a) on said workgroup server;

(i) copying said transaction file to an inbox resident on the workgroup server (315) and identified to the workgroup user client (310), and (ii) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log.

15. The program storage device of claim 11 further comprising:

(a) on said master database server;

(i) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (ii) creating data files corresponding to the entries therein, (iii) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (iv) updating the transactions into a master database (3) on the master database server (4).

16. A system for managing a database residing in a multitier data base management system having a master database server (4), an application server (303), at least one workgroup server (315), and a plurality of workgroup user clients (310), said application server (303) and said workgroup server (315) interposed between said master database server (4) and said workgroup user clients (310), the system being configured to effect:

(a) creating a transaction in a local database resident on one of said workgroup user clients (310),

(b) entering the transaction into a transaction log resident on said workgroup user client (310),

(c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(d) copying said transaction file to an inbox resident on said workgroup server (315) and identified to the workgroup user client (310),

(e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log;

(f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4),

(g) creating data files corresponding to the entries therein,

(h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and

(i) updating the transactions into a master database (3) on the master database server (4).

17. The system of claim 16 wherein said system is configured to effect a computer to carry out in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310).

18. The system of claim 16 wherein said system is configured to effect a computer to carry out in the in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log.

19. The system of claim 16 wherein said system is configured to effect a computer to carry out in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).

20. The system of claim 16 wherein the system is configured to effect the computer to carry out:

(1) in the workgroup user client one or more of (a) creating a transaction in a local database resident on one of said workgroup user clients (310), (b) entering the transaction into a transaction log resident on said workgroup user client (310), or (c) creating a transaction file corresponding thereto in an outbox of said workgroup user client (310);

(2) in the workgroup server one or more of (d) copying said transaction file to an inbox on said workgroup server (315) identified to the workgroup user client (310), and (e) updating said transaction file into a workgroup database (305) resident on said workgroup server (315), said workgroup database (305) including a transaction log; and

(3) in the master database server one or more of (f) reading said workgroup database (305) transaction log while skipping those transactions which originate at the master database server (4), (g) creating data files corresponding to the entries therein, (h) copying data files corresponding to transactions originating at the workgroup user client (310) to an inbox on the master database server (4) corresponding to the workgroup server (315), and (i) updating the transactions into a master database (3) on the master database server (4).