Reduced disk space standby

• US 8,589,361 B2
• Filed: 08/30/2010
• Issued: 11/19/2013
• Est. Priority Date: 08/30/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Hu, Wei Ming, Loaiza, Juan R., Li, Yunrui, Srihari, Vinay H.
• Primary Examiner(s): Lee, Wilson
• Assistant Examiner(s): BUI, THUY T
• Application Number:
  US12/871,795
• Publication Number:
  US 20120054158A1
• Time in Patent Office: 1,177 Days
• Field of Search: 707/692, 707/769
• US Class Current: 707/692
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/1748 De-duplication implemented within the file system, e.g. based on file segments de-duplication techniques in storage systems for the management of data blocks G06F3/0641
• CPC Class Codes: G06F 16/1752 based on file chunks
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06F 2212/465 Structured object, e.g. database record

Abstract

A method and system for replicating database data is provided. One or more standby database replicas can be used for servicing read-only queries, and the amount of storage required is scalable in the size of the primary database storage. One technique is described for combining physical database replication to multiple physical databases residing within a common storage system that performs de-duplication. Having multiple physical databases allows for many read-only queries to be processed, and the de-duplicating storage system provides scalability in the size of the primary database storage. Another technique uses one or more diskless standby database systems that share a read-only copy of physical standby database files. Notification messages provide consistency between each diskless system'"'"'s in-memory cache and the state of the shared database files. Use of a transaction sequence number ensures that each database system only accesses versions of data blocks that are consistent with a transaction checkpoint.

Claims

1. A computer-implemented method, comprising:

a main standby database system applying changes to standby database files, wherein the changes were made to a primary database of a primary database system;

in response to applying changes, advancing an established logical time associated with a consistent state of the primary database system for computing queries to a particular logical time associated with a subsequent consistent state of the primary database system;

sending to one or more subsidiary standby database systems said particular logical time, wherein said one or more subsidiary standby database systems do not apply said changes to said standby database files; and

while said main standby database system is applying said changes to said standby database files;

receiving a query issued to a subsidiary standby database system of the one or more subsidiary database systems; and

said subsidiary standby database system computing results for said query that are consistent with said particular logical time based on data read from said standby database files;

wherein each of the above steps is performed by one or more computing devices.

2. The method of claim 1, further comprising said one or more subsidiary standby database systems receiving a set of invalidation records, wherein an invalidation record of the set of invalidation records identifies portions of an in-memory cache to mark as invalid;

wherein the portions of the in-memory cache to mark as invalid correspond to the changes applied to said standby database files; and

marking the portions of the in-memory cache as invalid.

3. The method of claim 1, further comprising sending one or more notification messages to one or more subsidiary standby database systems, wherein each of the one or more notification messages includes an SCN.

4. The method of claim 3, wherein each of the one or more notification messages includes a set of invalidation records.

5. The method of claim 3, wherein a notification message is received by a particular subsidiary standby database system;

and

in response to determining that a sequential query number in the notification message is not consecutive with a current sequential query number, determining to invalidate all data blocks cached in the subsidiary standby database system.

6. A non-transitory computer-readable medium storing one or more sequences of instructions which, when executed by one or more processors, cause performing of:

a main standby database system applying changes to standby database files, wherein the changes were made to a primary database of a primary database system;

in response to applying changes, advancing an established logical time

associated with a consistent state of the primary database system for computing queries to a particular logical time associated with a subsequent consistent state of the primary database system;

sending to one or more subsidiary standby database systems said particular logical time, wherein said one or more subsidiary standby database systems do not apply said changes to said standby database files; and

while said main standby database system is applying said changes to said standby database files;

receiving a query issued to a subsidiary standby database system of the one or more subsidiary database systems; and

said subsidiary standby database system computing results for said query that are consistent with said particular logical time based on data read from said standby database files.

7. The non-transitory computer-readable medium of claim 6, wherein the one or more sequences of instructions further cause performing of:

said one or more subsidiary standby database systems receiving a set of invalidation records, wherein an invalidation record of the set of invalidation records identifies portions of an in-memory cache to mark as invalid;

wherein the portions of the in-memory cache to mark as invalid correspond to the changes applied to said standby database files; and

marking the portions of the in-memory cache as invalid.

8. The non-transitory computer-readable medium of claim 6, wherein the one or more sequences of instructions further cause performing of:

sending one or more notification messages to one or more subsidiary standby database systems, wherein each of the one or more notification messages includes an SCN.

9. The non-transitory computer-readable medium of claim 8, wherein each of the one or more notification messages includes a set of invalidation records.

10. The non-transitory computer-readable medium of claim 8, wherein a notification message is received by a particular subsidiary standby database system, and wherein the one or more sequences of instructions further cause performing of:

in response to determining that a sequential query number in the notification message is not consecutive with a current sequential query number, determining to invalidate all data blocks cached in the subsidiary standby database system.