Zero downtime upgrade of systems with database-side replication

Patent metadata

Field	Value
Publication number	US-11232126-B2
Application number	US-201816197888-A
Country	US
Kind code	B2
Filing date	Nov 21, 2018
Priority date	Nov 21, 2018
Publication date	Jan 25, 2022
Grant date	Jan 25, 2022

Abstract

Implementations include providing, by a deploy tool, clone data components in the first database system, each clone data component being a copy of a data component, defining, by the deploy tool, a source-side green access schema in the first database system, the green access schema providing views to the clone data components, providing, by a replication system and based on statements received from the deploy tool, consumer-side clone data components in the first database system, each consumer-side clone data component being a copy of a respective data component, defining, by a replication system and based on statements received from the deploy tool, a consumer-side green access schema in the first database system, the green access schema providing views to the source-side clone data components, and, during execution of the upgrade, replicating, by a handler of the replication system, data from at least one source-side data component to a consumer-side component.

First claim

What is claimed is:

1. A computer-implemented method for replication of data from a first database system to a second database system during upgrade of an application from a first version to a second version, the application interacting with the data in the first database system and a consumer consuming data from the second database system, the method being executed by one or more processors and comprising:
providing, by a deploy tool, one or more source-side clone data components in the first database system, each source-side clone data component being a copy of a respective data component;
defining, by the deploy tool, a source-side green access schema in the first database system, the source-side green access schema providing one or more views to the one or more source-side clone data components based on the second version of the application;
providing, by a replication system and based on one or more statements received from the deploy tool, one or more consumer-side clone data components in the second database system, each consumer-side clone data component being a copy of a respective data component;
defining, by a replication system and based on one or more statements received from the deploy tool, a consumer-side green access schema in the second database system, the consumer-side green access schema providing one or more views to the one or more consumer-side clone data components based on the second version of the application;
during execution of the upgrade:
replicating, by a first handler of the replication system, data from at least one source-side data component to a respective consumer-side component, the first handler corresponding to the first version of the application; and

after completion of the upgrade:
replicating, by a second handler of the replication system, data from at least one source-side data component to a respective consumer-side component, the second handler corresponding to the second version of the application.

2. The method of claim 1 , further comprising, after completion of the upgrade:
switching an upgraded version of the application to the source-side green access schema for interacting with the one or more source-side clone data components; and
removing a source-side blue access schema, through which a previous version of the application accessed data in the first database system.

3. The method of claim 1 , further comprising, after completion of the upgrade:
switching replication of data from the first database system to the consumer-side green access schema; and
removing a consumer-side blue access schema, through which data was replicated to in the second database system.

4. The method of claim 3 , wherein the replication system triggers switching of replication of data, and removing the consumer-side blue access schema based on post-upgrade statements received from the deploy tool.

5. The method of claim 1 , wherein the source-side green access schema comprises a replication trigger for replicating data to the second database system.

6. The method of claim 1 , wherein a data schema of the first database system comprises a trigger for copying data from an original clone data component to at least one source-side data component.

7. The method of claim 1 , wherein the one or more source-side data components comprise one or more of a clone column, and a clone table.

8. A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for replication of data from a first database system to a second database system during upgrade of an application from a first version to a second version, the application interacting with the data in the first database system and a consumer consuming data from the second database system, the operations comprising:
providing, by a deploy tool, one or more source-side clone data components in the first database system, each source-side clone data component being a copy of a respective data component;
defining, by the deploy tool, a source-side green access schema in the first database system, the source-side green access schema providing one or more views to the one or more source-side clone data components based on the second version of the application;
providing, by a replication system and based on one or more statements received from the deploy tool, one or more consumer-side clone data components in the second database system, each consumer-side clone data component being a copy of a respective data component;
defining, by a replication system and based on one or more statements received from the deploy tool, a consumer-side green access schema in the second database system, the consumer-side green access schema providing one or more views to the one or more consumer-side clone data components based on the second version of the application;
during execution of the upgrade:
replicating, by a first handler of the replication system, data from at least one source-side data component to a respective consumer-side component, the first handler corresponding to the first version of the application; and

after completion of the upgrade:
replicating, by a second handler of the replication system, data from at least one source-side data component to a respective consumer-side component, the second handler corresponding to the second version of the application.

9. The computer-readable storage medium of claim 8 , wherein operations further comprise, after completion of the upgrade:
switching an upgraded version of the application to the source-side green access schema for interacting with the one or more source-side clone data components; and
removing a source-side blue access schema, through which a previous version of the application accessed data in the first database system.

10. The computer-readable storage medium of claim 8 , wherein operations further comprise, after completion of the upgrade:
switching replication of data from the first database system to the consumer-side green access schema; and
removing a consumer-side blue access schema, through which data was replicated to in the second database system.

11. The computer-readable storage medium of claim 10 , wherein the replication system triggers switching of replication of data, and removing the consumer-side blue access schema based on post-upgrade statements received from the deploy tool.

12. The computer-readable storage medium of claim 8 , wherein the source-side green access schema comprises a replication trigger for replicating data to the second database system.

13. The computer-readable storage medium of claim 8 , wherein a data schema of the first database system comprises a trigger for copying data from an original clone data component to at least one source-side data component.

14. The computer-readable storage medium of claim 8 , wherein the one or more source-side data components comprise one or more of a clone column, and a clone table.

15. A system, comprising:
a computing device; and
a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for replication of data from a first database system to a second database system during upgrade of an application from a first version to a second version, the application interacting with the data in the first database system and a consumer consuming data from the second database system, the operations compri

Assignees

• Sap Se

Inventors

• Meissner Steffen
• Driesen Volker
• Karpstein Tobias
• Mayer Martin
• Saelinger Thomas
• Ullrich Thomas

Classifications

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F16/212

  with details for data modelling support · CPC title

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/214

  Database migration support · CPC title