Low-downtime and zero-downtime upgrades of database-centric applications

• US 8,521,706 B2
• Filed: 10/19/2007
• Issued: 08/27/2013
• Est. Priority Date: 10/20/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Alpern, David M., Choi, Alan, Iyer, Chandrasekharan, Lee, Jaebock, Rajamani, Kumar, Shankar, Shrikanth, Viswanathan, Guhan, Waddington, William, Yam, Philip
• Primary Examiner(s): Leroux, Etienne
• Assistant Examiner(s): BIBBEE, JARED M
• Application Number:
  US11/875,478
• Publication Number:
  US 20080098046A1
• Time in Patent Office: 2,139 Days
• Field of Search: 707/200, 707/695, 707/736
• US Class Current: 707/695
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/24565 Triggers; Constraints

Abstract

A database may facilitate zero-downtime upgrades by concurrently maintaining multiple editions of database objects for use by both pre-upgrade and post-upgrade clients of a database application. Operations performed within the database are associated with an edition based on, for example, an initiating client or transaction. When an operation references an object or data, the database automatically performs the operation using the object or data associated with the edition with which the operation is itself associated. The database may determine the associated edition without explicit identification of the associated edition in a query or in code. Thus, no client or stored procedure code changes are necessary to reflect a new edition added during an update. Data changes in one edition may be automatically and immediately propagated to the other edition through the use of cross-edition triggers, thereby allowing both pre-upgrade and post-upgrade clients to remain fully functional throughout an upgrade.

Claims

1. A method comprising:

concurrently maintaining metadata defining an old edition of one or more objects within a database and metadata defining a new edition of the same one or more objects within the database;

concurrently maintaining as a view, referenced by a particular view label, an old view edition of the view, associated by said metadata with the old edition, and a new view edition of the view, associated by said metadata with the new edition;

wherein the old view edition defines a view column, referenced by a view column label, to be mapped to a first column in a table in the database;

wherein the new view edition defines the same view column, referenced by the same view column label, to be mapped to a second column that is different than the first column and that is in the table in the database; and

wherein the second column comprises data values that have been calculated based on corresponding data values in the first column;

executing a first query that references the view by the particular view label and that references the view column by the view column label, wherein executing the first query includes;

in response to determining that the first query is associated with the new edition;

accessing the view column through the new view edition, thereby

accessing data in the second column in the table; and

performing the first query by at least accessing the view column through the second column; and

concurrently to executing the first query, executing a second query that references the view by the particular view label and that references the view column by the view column label, wherein executing the second query includes;

in response to determining that the second query is associated with the old edition;

accessing the view column through the old view edition, thereby accessing data in the first column in the table; and

performing the second query by at least accessing the view column through the first column; and

wherein the method is performed by one or more computing devices.

2. The method of claim 1,

wherein accessing the first column causes a change in the first column, and the method further comprises the step of:

responsive to the change, automatically transforming the second column to reflect the change in the first column;

wherein accessing the second column causes a change in the second column, and the method further comprises the step of;

responsive to the change, transforming the first column to reflect the change in the second column.

3. The method of claim 2, wherein the step of transforming the second column is performed in response to a pre-defined trigger associated with the first column, wherein the pre-defined trigger defines a transformation of data values in the first column to data values in the second column.

4. The method of claim 1, wherein determining that the first query is associated with the new edition is based upon at least one of:

an identity of a client requesting performance of the first query, configuration parameters communicated by said client, or session data associated with said client.

5. The method of claim 1, wherein the first column and the second column are stored within a particular table, wherein the view is of the particular table.

6. The method of claim 1,

wherein accessing the first column causes a change in the first column, and the method further comprises the step of:

responsive to the change, executing at least a set of triggers associated with the first column, each trigger in the set of triggers modifying a different column, including the second column, to reflect the change in the first column;

wherein the different column is mapped to the view column in a different edition.

7. The method of claim 1,

wherein accessing the first column causes a change in the first column, and the method further comprises the step of:

responsive to the change, executing a plurality of triggers;

wherein executing the plurality of triggers comprises executing the plurality of triggers in an order indicated by ordering data defined for the plurality of triggers.

8. The method of claim 1, wherein the data values in the first column are of a different type than the data values in the second column.

9. The method of claim 1, wherein executing the first query includes initializing a value in the first column based on a function of a corresponding value in the second column.

10. The method of claim 1, wherein executing the first query further includes locking a value in the second column while changing a corresponding value in the first column, said locking continuing at least until the value in the second column has been modified to reflect said changing of the corresponding value.

21. The method of claim 1, wherein maintaining metadata defining the old edition of one or more objects within the database and metadata defining the new edition of the same one or more objects within the database comprises maintaining additional metadata that defines at least one additional new edition, and associates the new view edition with the at least one additional new edition and the new edition.

11. One or more non-transitory computer-readable storage media storing instructions that, when executed by one or more computing devices, cause:

concurrently maintaining metadata defining an old edition of one or more objects within a database and metadata defining a new edition of the same one or more objects within the database;

concurrently maintaining as a view, referenced by a particular view label, an old view edition of the view, associated by said metadata with the old edition, and a new view edition of the view, associated by said metadata with the new edition;

wherein the old view edition defines a view column, referenced by a view column label, to be mapped to a first column in a table in the database;

wherein the new view edition defines the same view column, referenced by the same view column label, to be mapped to a second column that is different than the first column and that is in the table in the database; and

wherein the second column comprises data values that have been calculated based on corresponding data values in the first column;

executing a first query that references the view by the particular view label and that references the view column by the view column label, wherein executing the first query includes;

in response to determining that the first query is associated with the new edition;

accessing the view column through the new view edition, thereby

accessing data in the second column in the table; and

performing the first query by at least accessing the view column through the second column; and

concurrently to executing the first query, executing a second query that references the view by the particular view label and that references the view column by the view column label, wherein executing the second query includes;

in response to determining that the second query is associated with the old edition;

accessing the view column through the old view edition, thereby accessing data in the first column in the table; and

performing the second query by at least accessing the view column through the first column.

12. The one or more non-transitory computer-readable storage media of claim 11,

wherein accessing the first column causes a change in the first column, and wherein the instructions, when executed by the one or more computing devices, further cause:

responsive to the change, automatically transforming the second column to reflect the change in the first column;

wherein accessing the second column causes a change in the second column, and wherein the instructions, when executed by the one or more computing devices, further cause;

responsive to the change, transforming the first column to reflect the change in the second column.

13. The one or more non-transitory computer-readable storage media of claim 12, wherein the step of transforming the second column is performed in response to a pre-defined trigger associated with the first column, wherein the pre-defined trigger defines a transformation of data values in the first column to data values in the second column.

14. The one or more non-transitory computer-readable storage media of claim 11, wherein determining that the first query is associated with the new edition is based upon at least one of:

an identity of a client requesting performance of the first query, configuration parameters communicated by said client, or session data associated with said client.

15. The one or more non-transitory computer-readable storage media of claim 11, wherein the first column and the second column are stored within a particular table, wherein the view is of the particular table.

16. The one or more non-transitory computer-readable storage media of claim 11,

wherein accessing the first column causes a change in the first column, and the instructions, when executed by the one or more computing devices, further cause:

responsive to the change, executing at least a set of triggers associated with the first column, each trigger in the set of triggers modifying a different column, including the second column, to reflect the change in the first column;

wherein the different column is mapped to the view column in a different edition.

17. The one or more non-transitory computer-readable storage media of claim 11,

wherein accessing the first column causes a change in the first column, and the instructions, when executed by the one or more computing devices, further cause:

responsive to the change, executing a plurality of triggers;

wherein executing the plurality of triggers comprises executing the plurality of triggers in an order indicated by ordering data defined for the plurality of triggers.

18. The one or more non-transitory computer-readable storage media of claim 11, wherein the data values in the first column are of a different type than the data values in the second column.

19. The one or more non-transitory computer-readable storage media of claim 11, wherein executing the first query includes initializing a value in the first column based on a function of a corresponding value in the second column.

20. The one or more non-transitory computer-readable storage media of claim 11, wherein executing the first query further includes locking a value in the second column while changing a corresponding value in the first column, said locking continuing at least until the value in the second column has been modified to reflect said changing of the corresponding value.

22. The one or more non-transitory computer-readable storage media of claim 11, wherein maintaining metadata defining the old edition of one or more objects within the database and the new edition of the same one or more objects within the database comprises maintaining additional metadata that defines at least one additional new edition, and associates the new view edition with the at least one additional new edition and the new edition.