Migrating data using an intermediate self-describing format

• US 7,290,003 B1
• Filed: 08/19/2004
• Issued: 10/30/2007
• Est. Priority Date: 08/19/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Tong, Ka-Leung
• Primary Examiner(s): Truong; Cam Y
• Assistant Examiner(s): Ly; Anh
• Application Number:
  US10/922,558
• Time in Patent Office: 1,167 Days
• Field of Search: 707100-102, 707/104.1
• US Class Current: 1/1
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

In accordance with one embodiment of the present invention, there is provided a technique for migrating data using a self-describing format. According to an embodiment of the technique, a first source data set, which is in a source-specific format and which conforms to a source schema, is read from a source database. Based on the structure of the first source data set, a second source data set, which conforms to the source schema but which is in a self-describing format, is generated. The second source data set is automatically converted to a first target data set, which is in the self-describing format but which conforms to a target schema. Based on the structure of the first target data set, a second target data set, which conforms to the target schema but which is in a target-specific format, is generated. The second target data set is written to a target database.

Claims

1. A machine-implemented method, comprising:

reading a set of source data, wherein the set of source data conforms to a source schema;

determining, based on a first mapping, that a first conversion mechanism is capable of converting the set of source data into a first set of intermediate data that conforms to a first intermediate schema that differs from the source schema;

determining, based on a second mapping, that a second conversion mechanism is capable of converting the first set of intermediate data into a second set of intermediate data that conforms to a second intermediate schema that differs from both the source schema and the first intermediate schema;

determining, based on one or more third mappings, that one or more third conversion mechanisms are capable of converting the second set of intermediate data into a set of target data that conforms to a target schema that differs from the source schema, the first intermediate schema, and the second intermediate schema;

in response to determining that the first conversion mechanism is capable of converting the set of source data into the first set of intermediate data, automatically converting the set of source data into the first set of intermediate data via the first conversion mechanism;

in response to determining that the second conversion mechanism is capable of converting the first set of intermediate data into the second set of intermediate data, automatically converting the first set of intermediate data into the second set of intermediate data via the second conversion mechanism;

in response to determining that the one or more third conversion mechanisms are capable of converting the second set of intermediate data into the set of target data, automatically converting the second set of intermediate data into the set of target data via the one or more third conversion mechanisms; and

writing the set of target data.

2. The machine-implemented method of claim 1, wherein reading comprises reading the set of source data from a source database, wherein writing comprises writing the set of target data to a target database, and wherein the source database is an earlier version of the target database.

3. The machine-implemented method of claim 1, wherein reading comprises reading the set of source data from a source database, wherein writing comprises writing the set of target data to a target database, wherein the source database is created by a first vendor, and the target database is created by a second vendor that differs from the first vendor.

4. The machine-implemented method of claim 1, further comprising:

converting the set of source data from a source-specific format into a self-describing format that differs from the source-specific format; and

converting the set of target data from the self-describing format into a target-specific forma that differs from the self-describing format;

wherein the source-specific format differs from the target-specific format.

5. The machine-implemented method of claim 4, wherein the self-describing format is a markup language.

6. The machine-implemented method of claim 5, wherein the markup language is Extensible Markup Language (XML).

7. The machine-implemented method of claim 5, wherein the source-specific format is Standard Generalized Markup Language (SGML).

8. The machine-implemented method of claim 4, wherein the source-specific format is a relational table format and wherein the target-specific format is a relational table format.

9. The machine-implemented method of claim 1, wherein the steps of converting are performed by three or more dynamically selected, separate conversion mechanisms, and wherein at least one of the three or more conversion mechanisms receives, as input, output from at least another of the three or more conversion mechanisms.

10. The machine-implemented method of claim 1, further comprising:

determining that the set of source data comprises embedded data that conforms to a first schema that differs from the source schema;

in response to determining that the set of source data comprises embedded data, determining one or more additional conversion mechanisms that are capable of converting the embedded data into converted data that conforms to a second schema that differs from the first schema;

automatically converting the embedded data into the converted data via the one or more additional conversion mechanisms; and

embedding the converted data into one of the first intermediate set of data and the second intermediate set of data prior to the second set of intermediate data being converted into the set of target data;

wherein the one or more additional conversion mechanisms are separate from the first conversion mechanism, the second conversion mechanism, and the one or more third conversion mechanisms.

11. The machine-implemented method of claim 10, further comprising:

identifying an “

<

embed>

”

tag in the set of source data as a beginning of the embedded data within the set of source data; and

identifying an “

<

/embed>

”

tag in the set of source data as an ending of the embedded data within the set of source data;

wherein the step of converting the embedded data into the converted data comprises inputting, into at least one of the one or more additional conversion mechanisms, data that begins within the “

<

embed>

”

tag and ends with the “

<

/embed>

”

tag in the set of source data.

12. The machine-implemented method of claim 10, wherein the embedded data corresponds to data that is of “

XML type”

in a relational database table.

13. A computer-readable storage medium carrying one or more sequences of instructions, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

reading a set of source data, wherein the set of source data conforms to a source schema;

determining, based on a first mapping, that a first conversion mechanism is capable of converting the set of source data into a first set of intermediate data that conforms to a first intermediate schema that differs from the source schema;

determining, based on a second mapping, that a second conversion mechanism is capable of converting the first set of intermediate data into a second set of intermediate data that conforms to a second intermediate schema that differs from both the source schema and the first intermediate schema;

determining, based on one or more third mappings, that one or more third conversion mechanisms are capable of converting the second set of intermediate data into a set of target data that conforms to a target schema that differs from the source schema, the first intermediate schema, and the second intermediate schema;

in response to determining that the first conversion mechanism is capable of converting the set of source data into the first set of intermediate data, automatically converting the set of source data into the first set of intermediate data via the first conversion mechanism;

in response to determining that the second conversion mechanism is capable of converting the first set of intermediate data into the second set of intermediate data, automatically converting the first set of intermediate data into the second set of intermediate data via the second conversion mechanism;

in response to determining that the one or more third conversion mechanisms are capable of converting the second set of intermediate data into the set of target data, automatically converting the second set of intermediate data into the set of target data via the one or more third conversion mechanisms; and

writing the set of target data.

14. The computer-readable storage medium of claim 13, wherein reading comprises reading the set of source data from a source database, wherein writing comprises writing the set of target data to a target database, and wherein the source database is an earlier version of the target database.

15. The computer-readable storage medium of claim 13, wherein reading comprises reading the set of source data from a source database, wherein writing comprises writing the set of target data to a target database, wherein the source database is created by a first vendor, and the target database is created by a second vendor that differs from the first vendor.

16. The computer-readable storage medium of claim 13, further comprising:

converting the set of source data from a source-specific format into a self-describing format that differs from the source-specific format; and

converting the set of target data from the self-describing format into a target-specific form a that differs from the self-describing format;

wherein the source-specific format differs from the target-specific format.

17. The computer-readable storage medium of claim 16, wherein the self-describing format is a markup language.

18. The computer-readable storage medium of claim 17, wherein the markup language is Extensible Markup Language (XML).

19. The computer-readable storage medium of claim 17, wherein the markup language is Standard Generalized Markup Language (SGML).

20. The computer-readable storage medium of claim 16, wherein the source-specific format is a relational table format and wherein the target-specific format is a relational table format.

21. The computer-readable storage medium of claim 13, wherein the steps of converting are performed by three or more dynamically selected, separate conversion mechanisms, and wherein at least one of the three or more conversion mechanisms receives, as input, output from at least another of the three or more conversion mechanisms.

22. The computer-readable storage medium of claim 13, wherein the steps further comprise:

determining that the set of source data comprises embedded data that conforms to a first schema that differs from the source schema;

in response to determining that the set of source data comprises embedded data, determining one or more additional conversion mechanisms that are capable of converting the embedded data into converted data that conforms to a second schema that differs from the first schema;

automatically converting the embedded data into the converted data via the one or more additional conversion mechanisms; and

embedding the converted data into one of the first intermediate set of data and the second intermediate set of data prior to the second set of intermediate data being converted into the set of target data;

wherein the one or more additional conversion mechanisms are separate from the first conversion mechanism, the second conversion mechanism, and the one or more third conversion mechanisms.

23. The computer-readable storage medium of claim 22, wherein the steps further comprise:

identifying an “

<

embed>

”

tag in the set of source data as a beginning of the embedded data within the set of source data; and

identifying an “

<

/embed>

”

tag in the set of source data as an ending of the embedded data within the set of source data;

wherein the step of converting the embedded data into the converted data comprises inputting, into at least one of the one or more additional conversion mechanisms, data that begins within the “

<

embed>

”

tag and ends with the “

<

/embed>

”

tag in the set of source data.

24. The computer-readable storage medium of claim 22, wherein the embedded data corresponds to data that is of “

XML type”

in a relational database table.

25. An apparatus of a computer system, comprising:

a mechanism for reading a set of source data, wherein the set of source data conforms to a source schema;

a mechanism for determining, based on a first mapping, that a first conversion mechanism is capable of converting the set of source data into a first set of intermediate data that conforms to a first intermediate schema that differs from the source schema;

a mechanism for determining, based on a second mapping, that a second conversion mechanism is capable of converting the first set of intermediate data into a second set of intermediate data that conforms to a second intermediate schema that differs from both the source schema and the first intermediate schema;

a mechanism for determining, based on one or more third mappings, that one or more third conversion mechanisms are capable of converting the second set of intermediate data into a set of target data that conforms to a target schema that differs from the source schema, the first intermediate schema, and the second intermediate schema;

the first conversion mechanism for automatically converting the set of source data into the first set of intermediate data in response to determining that the first conversion mechanism is capable of converting the set of source data into the first set of intermediate data;

the second conversion mechanism for automatically converting the first set of intermediate data into the second set of intermediate data in response to determining that the second conversion mechanism is capable of converting the first set of intermediate data into the second set of intermediate data;

the one or more third conversion mechanisms for automatically converting the second set of intermediate data into the set of target data in response to determining that the one or more third conversion mechanisms are capable of converting the second set of intermediate data into the set of target data; and

a mechanism for writing the set of target data.