Data replication between software versions

• US 8,930,499 B2
• Filed: 07/09/2010
• Issued: 01/06/2015
• Est. Priority Date: 07/09/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Berry, Lee, Khuu, Trung Nghia, Chan, Philip Seik Poon
• Primary Examiner(s): Algibhah, Hamza
• Assistant Examiner(s): EDWARDS, JAMES A
• Application Number:
  US12/833,398
• Publication Number:
  US 20120011495A1
• Time in Patent Office: 1,642 Days
• Field of Search: 709/219
• US Class Current: 709/219
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method, computer program product, and system for data replication between software versions is described. A method may comprise determining if a first item created in a first software version includes data native to a second item in a second software version. The method may further comprise, if the first item created in the first software version includes data native to the second item in the second software version, storing the data native to the second item in the second software version as native data. The method may also comprise, if the first item created in the first software version is missing required data based upon, at least in part, the second item in the second software version, storing a default value for the missing required data as native data.

Claims

1. A method of replicating a first item from a first software version to a second software version, on a computing system running the second software version, comprising:

for each of a plurality of fields of the first item;

determining whether the field is native to a second item in the second software version;

upon determining that the field is native to the second item in the second software version, storing the field as native data to be loaded into memory of the computing system, wherein the field is determined to be native when the second software version is configured to access and use the field; and

upon determining that the field is non-native to the second item in the second software version, storing the field as auxiliary data to be stored on persistent storage in an original format, wherein the auxiliary data is not loaded into memory of the computing system, and wherein the field is determined to be non-native when the second software version is not configured to recognize the field; and

upon determining that the first item is missing one or more required fields for the second software version, based at least in part on the second item in the second software version, storing a default value for each of the one or more required fields as native data.

2. The method of claim 1, further comprising at least one of:

receiving the first item from a first computing environment running the first software version, at a second computing environment running the second software version; and

loading the first item after the first software version is upgraded to the second software version in the same computing environment.

3. The method of claim 1, further comprising:

sending the native data and the auxiliary data to a downstream computing environment when the second item in the second software version is sent to the downstream computing environment.

4. The method of claim 1, wherein the at least one field was added to a schema in the second software version.

5. The method of claim 1, wherein the first software version and the second software version correspond to different versions of a database, and wherein the plurality of fields include at least one of a database field and a database table.

6. The method of claim 1, wherein the second item represents an object in the second software version that is equivalent to the first item in the first software version, and wherein determining whether the field is native to a second item in the second software version comprises:

determining that the field of the first item is native to the second item, upon determining that the second item includes a second field that corresponds to the field of the first item; and

determining that the field of the first item is non-native to the second item, upon determining that the second item does not include the second field that corresponds to the field of the first item.

7. The method of claim 1, wherein determining that the first item is missing one or more required fields for the second software version further comprises:

determining that the second item contains a second field that does not correspond to any of the plurality of fields of the first item.

8. The method of claim 1, wherein the field is determined to be non-native upon determining that the field was added to a schema in a software version subsequent to the second software version.

9. The method of claim 1, wherein the field is determined to be non-native upon determining that the field was removed from a schema in the second software version.

10. A computer program product residing on a computer readable storage memory having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform an operation for replicating a first item from a first software version to a second software version, on a computing system running the second software version, the operation comprising:

for each of a plurality of fields of the first item;

determining, whether the field is native to a second item in the second software version;

upon determining that the field is native to the second item in the second software version, storing the field as native data to be loaded into memory of the computing system, wherein the field is determined to be native when the second software version is configured to access and use the field;

upon determining that the field is non-native to the second item in the second software version, storing the field as auxiliary data to be stored on persistent storage in an original format, wherein the auxiliary data is not loaded into memory of the computing system, and wherein the field is determined to be non-native when the second software version is not configured to recognize the field; and

upon determining that the first item is missing one or more required fields for the second software version, based at least in part on the second item in the second software version, storing a default value for each of the one or more required fields as native data.

11. The computer program product of claim 10, the operation further comprising at least one of:

receiving the first item from a first computing environment running the first software version, at a second computing environment running the second software version; and

loading the first item after the first software version is upgraded to the second software version in the same computing environment.

12. The computer program product of claim 10, the operation further comprising:

sending the native data and the auxiliary data to a downstream computing environment when the second item in the second software version is sent to the downstream computing environment.

13. The computer program product of claim 10, wherein the at least one field was added to a schema in the second software version.

14. A computing system comprising:

a processor; and

a memory containing a second software version and a program that, when executed by the processor, performs an operation for replicating a first item from a first software version to the second software version, the operation comprising;

for each of a plurality of fields of the first item;

determining whether the field is native to a second item in the second software version;

upon determining that the field is native to the second item in the second software version, storing the field as native data to be loaded into the memory of the computing system, wherein the field is determined to be native when the second software version is configured to access and use the field; and

upon determining that the field is non-native to the second item in the second software version, storing the field as auxiliary data to be stored on persistent storage in an original format, wherein the auxiliary data is not loaded into the memory of the computing system, and wherein the field is determined to be non-native when the second software version is not configured to recognize the field; and

upon determining that the first item is missing one or more required fields for the second software version, based at least in part on the second item in the second software version, storing a default value for each of the one or more required fields as native data.

15. The computing system of claim 14, the operation further comprising at least one of:

receiving the first item from a first computing environment running the first software version, at a second computing environment running the second software version; and

loading the first item after the first software version is upgraded to the second software version in the same computing environment.

16. The computing system of claim 14, the operation further comprising:

sending the native data and the auxiliary data to a downstream computing environment when the second item in the second software version is sent to the downstream computing environment.

17. The computing system of claim 14, wherein at least one of the plurality of fields was added to a schema in the second software version.