Querying past versions of data in a distributed database

• US 7,552,149 B2
• Filed: 06/10/2004
• Issued: 06/23/2009
• Est. Priority Date: 09/06/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sinha, Bipul, Ganesh, Amit
• Primary Examiner(s): Vital; Pierre M
• Assistant Examiner(s): Raab; Christopher J
• Application Number:
  US10/866,333
• Publication Number:
  US 20050055385A1
• Time in Patent Office: 1,839 Days
• Field of Search: 707/1, 707/2, 707/3, 707/101, 707/102, 707200-203, 711/162
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2474 Sequence data queries, e.g. querying versioned data
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Past versions of data in a distributed database system comprising multiple databases and associated database servers are queried using temporal database access mechanisms, where a request for data in a past state from a “remote” database can be received at a “local” database server and relevant portions of the request are passed to the remote server for processing. The processing performed by the remote server includes returning the requested data in the specified past state to the local server, or at least with enough information to reconstruct the data into the past state.

Claims

1. A method for querying past versions of data in a distributed database comprising at least a first database and a second database logically connected via database links and appearing to client applications as a single database, the method comprising the computer-implemented steps of:

receiving, at a first database server that manages data in a first database, a request for a past version of data stored in a second database that is managed by a second database server;

wherein the request indicates one or more conditions and a time specifying parameter;

wherein said time-specifying parameter corresponds to one or more prior logical states of the second database;

wherein the request for the past version of data stored in the second database is a request for data that, as the data existed in said one or more prior logical states of the second database, satisfied said one or more conditions, without regard to whether the data, as the data exists in a current state of the second database, satisfies the one or more conditions;

in response to said request, said first database server requesting said past version of said data from said second database server; and

receiving at said first database server a representation of said past version of said data, as said data existed in said second database at a prior point in time that corresponds to the time specifying parameter, from said second database server;

wherein the step of requesting said past version comprises passing to said second database server one of;

(a) a particular time that can be compared to a timestamp that is associated with said data to identify said past version of said data by said second database server;

or

(b) a particular system change number that is associated with said data and is used to identify said past version of said data by said second database server, wherein a system change number is a logical time value indicating the sequence in which events occur within the second database server.

2. The method of claim 1, wherein the step of passing comprises passing to said second database server a particular time that can be compared to a timestamp that is associated with said data to identify said past version of said data by said second database server.

3. The method of claim 1, wherein the step of passing comprises passing to the second database server a particular system change number that is associated with said data and is used to identify said past version of said data by said second database server, wherein a system change number is a logical time value indicating the sequence in which events occur within the second database server.

4. The method of claim 1, wherein said data is stored only in said second database and not in said first database.

5. The method of claim 1, wherein the step of receiving a request comprises receiving a request that specifies a time interval that can be associated with said data in said second database.

6. The method of claim 5, wherein the step of receiving said past version of said data comprises receiving multiple versions of said data, each of which is associated with a time that falls within said time interval.

7. The method of claim 6, wherein the step of receiving said multiple past versions of said data comprises receiving transaction metadata associated with each past version.

8. The method of claim 1, wherein the step of receiving a request comprises receiving a request that specifies a database operation on said past version of said data that is stored in said second database, the method further comprising the computer-implemented step of:

performing said operation on said past version of said data.

9. The method of claim 1, wherein the step of receiving a request comprises receiving a request that specifies a database operation on said past version of said data that is stored in said second database and a current version of data, the method further comprising the computer-implemented step of:

performing said operation on said past version of said data and said current version of data.

10. The method of claim 9, wherein said past version and said current version are different versions of the same data from said second database.

11. The method of claim 9, wherein said current version of data is from said first database.

12. The method of claim 1, wherein the step of receiving a request comprises receiving a request that specifies a database operation on said past version of said data stored in said second database and a past version of data that is stored in said first database, the method further comprising the computer-implemented step of:

performing said operation on said past version of said data stored in said second database and said past version of said data that is stored in said first database.

13. The method of claim 12, wherein said past version of said data stored in said second database is associated with a first time and said past version of said data that is stored in said first database is associated with a second time, and wherein said first time is different than said second time.

14. The method of claim 1, further comprising the computer-implemented steps of:

wherein the step of receiving a request comprises receiving a request for a past version of first data, wherein said first data is stored in a first remote database that is associated with said first database via a database link, and a past version of second data, wherein said second data is stored in a second remote database that is associated with said first database via a database link; and

wherein the step of receiving data comprises receiving at said first database server said past version of said first data and said past version of said second data.

15. The method of claim 14, wherein said past version of said first data is associated with a first time and said past version of said second data is associated with a second time, and wherein said first time is different than said second time.

16. The method of claim 1, further comprising the computer-implemented step of:

retrieving said past version of said data from said second database without changing said data in persistent storage.

17. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 1.

18. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 2.

19. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 3.

20. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 4.

21. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 5.

22. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 6.

23. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 7.

24. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 8.

25. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 9.

26. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 10.

27. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 11.

28. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 12.

29. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 13.

30. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 14.

31. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 15.

32. A computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 16.

33. A system comprising:

means for receiving, at a first database server that manages data in a first database, a request for a past version of data stored in a second database that is managed by a second database server, wherein said first database and said second database are components of a distributed database and are logically connected via database links and appear to client applications as a single database;

wherein the request indicates one or more conditions and a time-specifying parameter;

wherein said time-specifying parameter corresponds to one or more prior logical states of the second database;

wherein the request for the past version of data stored in the second database is a request for data that, as the data existed in said one or more prior logical states of the second database, satisfied said one or more conditions, without regard to whether the data, as the data exists in a current state of the second database, satisfies the one or more conditions;

means for said first database server requesting said past version of said data from said second database server in response to said request; and

means for receiving at said first database server a representation of said past version of said data, as said data existed in said second database at a prior point in time that corresponds to the time specifying parameter, from said second database server;

wherein the step of requesting said past version comprises passing to said second database server one of;

(a) a particular time that can be compared to a timestamp that is associated with said data to identify said past version of said data by said second database server;

or

(b) a particular system change number that is associated with said data and is used to identify said past version of said data by said second database server, wherein a system change number is a logical time value indicating the sequence in which events occur within the second database server.