Handling table deltas during zero downtime upgrade

Patent metadata

Field	Value
Publication number	US-10248408-B2
Application number	US-201414490529-A
Country	US
Kind code	B2
Filing date	Sep 18, 2014
Priority date	Sep 18, 2014
Publication date	Apr 2, 2019
Grant date	Apr 2, 2019

Abstract

A zero downtime upgrade of a source system to a target system is initiated. The source system and the target system operate in a first database layer and a second database layer. Thereafter, differences in structure and/or database type are computed between a source table in the source system and a target table in the target system in each of the two different database layers. The data is then migrated, using the computing differences and in the second database layer, from the source table to the target table. The upgrade procedure is later terminated after completion of the migration of the data. Related apparatus, systems, techniques and articles are also described.

First claim

What is claimed is:

1. A method comprising:
initiating a zero downtime upgrade of a source system to a target system, the upgrade procedure preparing software for the target system in parallel to operation of the source system by selectively (i) cloning, for the target system, tables and associated database triggers used by the source system according to a source database schema, (ii) generating new target tables comprising updated software content for use by a bridge database schema, and (iii) selectively sharing tables between the source database schema and the bridge database schema, the source system and the target system operating in a language layer and a database layer, the language layer including a source language layer and a target language layer, and the database layer including a source database layer and a target database layer, the source language layer including a first mapping of data types between the source database layer and the source language layer, and the target language layer including a second mapping of data types between the target language layer and the target database layer;
computing a first difference in structure and/or database type between a first data element in a source table in the source system and a second data element in a target table in the target system, in the database layer;
computing a second difference in structure and/or database type between a third data element in the source table and a fourth data element in the target table, in the language layer,
wherein the third data element is generated from the first data element in the source table by the first mapping of data types between the source database layer and the source language layer;
migrating, using the first and second computed differences, the first data element and third data element from the source table to the target table in the database layer, the first and second computed differences used to add, delete, and/or change field type of the migrated data; and
terminating the upgrade procedure after completion of the migration of the data; wherein at least one of the initiating, the computing, the migrating, and the terminating are implemented by at least one data processor forming part of at least one computing system.

2. The method of claim 1 , wherein the language layer is an Advanced Business Application Processing (ABAP) language layer.

3. The method of claim 2 , wherein the computing the first and second differences comprises accessing an ABAP data dictionary (DDIC) to identify a structure of the source table in the language layer.

4. The method of claim 1 , wherein the database layer uses Structured Query Language (SQL) for managing data.

5. The method of claim 1 , wherein the migrating implicitly converts the data of the source table on the database layer.

6. The method of claim 1 , wherein the migrating uses a conversion function to convert the data of the source table on the database layer.

7. A system comprising:
a source system comprising at least one data processor and memory;
a target system comprising at least one data processor and memory;
wherein the source system and the target system implement operations comprising:
initiating a zero downtime upgrade of the source system to the target system, the upgrade procedure preparing software for the target system in parallel to operation of the source system by selectively (i) cloning, for the target system, tables and associated database triggers used by the source system according to a source database schema, (ii) generating new target tables comprising updated software content for use by a bridge database schema, and (iii) selectively sharing tables between the source database schema and the bridge database schema, the source system and the target system operating in a language layer and a database layer, the language layer including a source language layer and a target language layer, and the database layer including a source database layer and a target database layer, the source language layer including a first mapping of data types between the source database layer and the source language layer, and the target language layer including a second mapping of data types between the target language layer and the target database layer;
computing a first difference in structure and/or database type between a first data element in a source table in the source system and a second data element in a target table in the target system, in the database layer;

computing a second difference in structure and/or database type between a third data element in the source table and a fourth data element in the target table, in the language layer,
wherein the third data element is generated from the first data element in the source table by the first mapping of data types between the source database layer and the source language layer;
migrating, using the first and second computed differences, the first data element and third data element from the source table to the target table in the database layer, the first and second computed differences used to add, delete, and/or change field type of the migrated data; and
terminating the upgrade procedure after completion of the migration of the data.

8. The system of claim 7 , wherein the language layer is an Advanced Business Application Processing (ABAP) language layer.

9. The system of claim 8 , wherein the computing the first and second differences comprises accessing an ABAP data dictionary (DDIC) to identify a structure of the source table in the language layer.

10. The system of claim 7 , wherein the database layer uses Structured Query Language (SQL) for managing data.

11. The system of claim 7 , wherein the migrating implicitly converts the data of the source table on the database layer.

12. The system of claim 7 , wherein the migrating uses a conversion function to convert the data of the source table on the database layer.

13. A method for implementation by one or more data processors forming part of at least one computing system, the method comprising:
initiating a zero downtime upgrade of a source system to a target system, the upgrade procedure preparing software for the target system in parallel to operation of the source system by selectively (i) cloning, for the target system, tables and associated database triggers used by the source system according to a source database schema, (ii) generating new target tables comprising updated software content for use by a bridge database schema, and (iii) selectively sharing tables between the source database schema and the bridge database schema, the source system and the target system operating in a language layer and a database layer, the language layer includes a source language layer and a target language layer, and the database layer including a source database layer and a target database layer, the source language layer including a first mapping of data types between the source database layer and the source language layer, and the target language layer including a second mapping of data types between the target language layer and the target database layer;
computing a first difference in structure and/or database type between a first data element in a source table in the source system and a second data element in a target table in the target system, in the database layer;
computing a second difference in structure and/or database type between a third data element in the source table and a fourth data element in the target table, in the language layer,
wherein the third data element is generated from the first data element in the source table by the first mapping of data types between the source

Assignees

• Meissner Steffen
• Specht Juergen
• Sap Se

Inventors

• Meissner Steffen
• Specht Juergen

Classifications

• G06F16/1873

  Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files · CPC title

• G06F16/27

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

• G06F16/211

  Schema design and management · CPC title

• G06F8/656 Primary

  while running · CPC title

• G06F16/214

  Database migration support · CPC title