Method and apparatus for accessing data as it existed at a previous point in time

The present application claims priority to Provisional Patent Application Ser. No. 60/378,016, filed May 10, 2002, the disclosure of which is hereby incorporated by reference herein in its entirety.

The systems and methods described herein relate to data access systems and, more particularly, to systems and methods that access data from a database.

A database management system (DBMS) is a layer of software between a physical database (i.e., the files storing the data in the database) and the user. The DBMS manages requests for database action (such as queries or updates) from a user. Additionally, the DBMS permits centralized control of security and data integrity requirements.

In some situations, it is desirable to retrieve data in the state in which the data existed at a specific previous point in time. FIG. 1 is a flow diagram illustrating an existing procedure 100 for accessing “past data” from a database or other data storage mechanism. Initially, the procedure identifies a previous time that the data values should reflect (block 102 ). A flashback command is executed that changes the system time to the previous time (block 104 ). The procedure then executes one or more commands to retrieve data values associated with the previous time (block 106 ). Finally, the procedure executes a flashback disable command that changes the system time back to the current time (block 108 ).

The above procedure is effective at retrieving data values associated with a previous time. However, if the procedure is in the flashback mode (i.e., a flashback command has changed the system time to the previous time), then the procedure must exit (or disable) the flashback mode before retrieving data values associated with the current time or associated with a different previous time. This switching into and out of the flashback mode is time-consuming and may result in the repeated compilation of similar database queries.

Various database languages, such as SQL (Structured Query Language), support special-purpose constructs referred to herein as “cursors”. Prior to retrieving the results of a specific query statement, the DBMS may perform a significant amount of preliminary work for the statement, such as parsing, semantic analysis, and query plan generation. A cursor stores the results of much of this preliminary work. Consequently, when a query statement arrives, the DBMS first attempts to match the statement to statements for which cursors have already been created. If a match is found, the cursor is shared by the query statements, and the overhead work is avoided.

A “flashback cursor” is a particular type of cursor that is used to access past data. A flashback cursor is created in response to receipt of a “flashback query”. Unlike conventional queries, flashback queries specify a flashback time, and return data as it existed at the specified flashback time. One technique for handling flashback queries is described in patent application Ser. No. 09/676,305, filed Sep. 29, 2000, entitled SYSTEM AND METHOD FOR PROVIDING FINE-GRAINED TEMPORAL DATABASE ACCESS, by JONATHAN D. KLEIN, et al, the contents of which are incorporated herein by this reference.

Because flashback queries return data as of a particular flashback time, the flashback time must be taken into account during the preliminary work performed on the flashback query. For example, the execution plan of a flashback query should not attempt to use access structures, such as indexes, that did not exist at the flashback time of the query for which they are being made. Because the preliminary work is based on the specific flashback time, flashback cursors generally cannot be used by flashback queries other than the one for which they are created. The inability to share flashback cursors can result in significant inefficiencies.

The systems and methods described herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. Similar reference numbers are used throughout the drawings to reference similar elements and features.

FIG. 1 is a flow diagram illustrating an existing procedure for accessing past data from a database or other data storage mechanism.

FIG. 2 is a block diagram illustrating a data storage and data access system.

FIG. 3 is a flow diagram illustrating a procedure for the time-based sharing of flashback cursors to access data associated with different points in time.

FIG. 4 is a block diagram that illustrates a computer system upon which the procedures discussed herein may be implemented.

The systems and methods described herein are related to sharing data structures used to access data associated with a specific point in time. For purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various systems and methods. It will be apparent, however, that the systems and methods described herein may be implemented without these specific details. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Exemplary Data Storage System

FIG. 2 is a block diagram illustrating a data storage and data access system 200 . System 200 includes a server 202 coupled to a database 204 . The server 202 contains a database engine 206 that performs various data save operations and data retrieval operations. The database engine 206 includes a query engine 208 and a flashback cursor module 210 . Query engine 208 provides the basic functionality for interrogating the database 204 and retrieving data items from data tables 212 stored therein. In a particular embodiment, query engine 208 interprets statements written in SQL, although other query languages may also be used.

The flashback cursor module 210 allows database engine 206 to access data values stored in database 204 in the state in which such values existed at a previous point in time. As used herein, a “point in time” may refer to a particular moment in time (e.g., 5:15 p.m.). A previous point in time may be identified, for example, by a standardized time (e.g., 5:20 p.m.), a time relative to the standardized time (e.g., 15 minutes ago), or by a system change number, discussed below.

Sharing Flashback Cursors

A statement may share an existing cursor if the text of the SQL query statement matches the statement for which the cursor was built and some other conditions are satisfied. The cursor is shared if and only if the compiled result of the query would be exactly the same as the one already present in memory. Cursor sharing results in highly efficient query processing due to the time and resources saved in statement parsing, semantic analysis, and query plan generation. As mentioned above, flashback cursors are special cursors for accessing past data. These cursors are built with dictionary data as of the system time when the query was issued. The query plan is generated by taking into account the creation time of the access structures like indices and the specified point in time in the past for the flashback query.

According to one embodiment, the sharing of flashback cursors is facilitated by adding a time domain property to flashback cursors. This time domain property defines the range of flashback times for which the flashback cursor is valid. According to one embodiment, this “validity range” is closed at the lower bound and open at the upper bound. A flashback query can share an existing flashback cursor if the flashback time of the query falls within the validity range of the existing flashback cursor.

According to one embodiment, the flashback cursor time domain is defined as (low — time, hi — time). Any subsequent flashback query with a specified point in time (t) in the past can share an existing flashback cursor if t≧low — time and t≦hi — time. These times are initialized at the beginning of the parse phase of the flashback query. The following example code illustrates one possible implementation of a flashback cursor.

hi — time=current system time

low — time=t — flashback (specified point in time for the flashback query)

The hi — time is adjusted, if necessary, at the query optimization time as follows:

for(every — index — used — for — this — query) { if(index — specification — time ≧ t — flashback) { ignore — this — index; /* hi — time adjustment */ if(first — index — being — ignored) { copy — the — index — specification — time — into — the — hi — time; } else if (hi — time > index — specification — time) { copy — the — index — specification — time — into — the — hi — time; } } }

After the adjustments, the resulting time domain of the flashback cursor defines an interval for which cursor sharing does not lose any efficiency in terms of access methods. Using appropriate access structures is very important for a query. For example, the access structures chosen to process a query can drastically change the time needed to process the query. Choosing the appropriate access structures is even more important when processing a flashback query, since every data block encountered during use of the access structures is reconstructed as of the flashback query time.

In a particular embodiment, flashback queries contain a time parameter (also referred to as a “time identifier”). The time parameter associated with a command specifies the point in time with which the command is to operate. For example, the command

SELECT Foo from Bar ASOF time — identifier

selects data (Foo) from a data source (Bar) at a particular point in time (time — identifier). The time identifier can be a timestamp, a system change number (SCN), or other parameter that identifies a particular point in time.

The DBMS receives the command and determines the point in time associated with command. The DBMS then determines whether any existing flashback cursor is associated with (1) a query that matches the received command, and (2) a time range that includes the time value of the received command. According to one embodiment, if an existing flashback cursor satisfies these two conditions, then the flashback cursor is “shared” by the received command. Otherwise, a new flashback cursor is created for the received command.

Processing Data

FIG. 3 is a flow diagram illustrating a technique for the time-based sharing of flashback cursors to access data, where the flashback queries that are sharing the flashback cursor may be associated with different points in time. The technique illustrated in FIG. 3 may be executed, for example, by database engine 206 discussed above with respect to FIG. 2 .

Referring to FIG. 3 , at step 302 a flashback query is received by a database server. At step 304 , the database server determines whether the flashback query semantically matches a previously-received flashback query for which a flashback cursor has been created. If the flashback query semantically matches a previously-received flashback query for which a flashback cursor has been created, then control proceeds to step 306 . Otherwise, control proceeds to step 308 . At step 306 , the database server determines whether the point in time associated with the flashback query falls within the validity range of the flashback cursor. If the point in time associated with the flashback query falls within the validity range of the flashback cursor, then control proceeds to step 310 where the existing flashback cursor is used to process the flashback query. Otherwise, control proceeds to step 308 .

At step 308 , a new flashback cursor is created for the flashback query. During the creation process, a validity range is assigned to the flashback cursor. The validity range assigned to the flashback cursor may then be used to determine whether subsequent flashback queries can share the new flashback cursor.

In the technique illustrated in FIG. 3 , an existing flashback cursor is shared by an incoming flashback query if the flashback query satisfies two conditions: (1) the flashback query semantically matches the query associated with the flashback cursor, and (2) the point in time associated with the flashback query falls within the validity range associated with the flashback cursor. However, in alternative embodiments, these conditions may be merely two of a set of many conditions that are actually taken into account when determining whether a flashback query can or should share an existing flashback cursor. Consequently, the present invention is not limited to any particular set of conditions.

The technique illustrated in FIG. 3 does not require a “flashback mode” to be activated and deactivated for each previous time at which data values are desired. Instead, commands to retrieve data from different previous times can be intermixed with one another. This ability is supported through the use of data retrieval commands that specify a desired time (or point in time) at which data values are to be retrieved.

Hardware Overview

FIG. 4 is a block diagram that illustrates a computer system 400 upon which an embodiment of the invention may be implemented. Computer system 400 includes a bus 402 or other communication mechanism for communicating information, and a processor 404 coupled with bus 402 for processing information. Computer system 400 also includes a main memory 406 , such as a random access memory (RAM) or other dynamic storage device, coupled to bus 402 for storing information and instructions to be executed by processor 404 . Main memory 406 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 404 . Computer system 400 further includes a read only memory (ROM) 408 or other static storage device coupled to bus 402 for storing static information and instructions for processor 404 . A storage device 410 , such as a magnetic disk or optical disk, is provided and coupled to bus 402 for storing information and instructions.

Computer system 400 may be coupled via bus 402 to a display 412 , such as a cathode ray tube (CRT), for displaying information to a computer user. An input device 414 , including alphanumeric and other keys, is coupled to bus 402 for communicating information and command selections to processor 404 . Another type of user input device is cursor control 416 , such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 404 and for controlling cursor movement on display 412 . This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

The invention is related to the use of computer system 400 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 400 in response to processor 404 executing one or more sequences of one or more instructions contained in main memory 406 . Such instructions may be read into main memory 406 from another computer-readable medium, such as storage device 410 . Execution of the sequences of instructions contained in main memory 406 causes processor 404 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to processor 404 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 410 . Volatile media includes dynamic memory, such as main memory 406 . Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 402 . Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 404 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 400 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 402 . Bus 402 carries the data to main memory 406 , from which processor 404 retrieves and executes the instructions. The instructions received by main memory 406 may optionally be stored on storage device 410 either before or after execution by processor 404 .

Computer system 400 also includes a communication interface 418 coupled to bus 402 . Communication interface 418 provides a two-way data communication coupling to a network link 420 that is connected to a local network 422 . For example, communication interface 418 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 418 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 418 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 420 typically provides data communication through one or more networks to other data devices. For example, network link 420 may provide a connection through local network 422 to a host computer 424 or to data equipment operated by an Internet Service Provider (ISP) 426 . ISP 426 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 428 . Local network 422 and Internet 428 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 420 and through communication interface 418 , which carry the digital data to and from computer system 400 , are exemplary forms of carrier waves transporting the information.

Computer system 400 can send messages and receive data, including program code, through the network(s), network link 420 and communication interface 418 . In the Internet example, a server 430 might transmit a requested code for an application program through Internet 428 , ISP 426 , local network 422 and communication interface 418 .

The received code may be executed by processor 404 as it is received, and/or stored in storage device 410 , or other non-volatile storage for later execution. In this manner, computer system 400 may obtain application code in the form of a carrier wave.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.