The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Aug. 27, 2013
Filed:
Oct. 19, 2007
David M. Alpern, San Jose, CA (US);
Alan Choi, Redwood City, CA (US);
Chandrasekharan Iyer, Foster City, CA (US);
Jaebock Lee, Sunnyvale, CA (US);
Kumar Rajamani, San Ramon, CA (US);
Shrikanth Shankar, Los Altos, CA (US);
Guhan Viswanathan, Kirkland, WA (US);
William Waddington, Foster City, CA (US);
Philip Yam, Foster City, CA (US);
David M. Alpern, San Jose, CA (US);
Alan Choi, Redwood City, CA (US);
Chandrasekharan Iyer, Foster City, CA (US);
Jaebock Lee, Sunnyvale, CA (US);
Kumar Rajamani, San Ramon, CA (US);
Shrikanth Shankar, Los Altos, CA (US);
Guhan Viswanathan, Kirkland, WA (US);
William Waddington, Foster City, CA (US);
Philip Yam, Foster City, CA (US);
Oracle International Corporation, Redwood Shores, CA (US);
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.