Method and apparatus to migrate a database

• US 20040064487A1
• Filed: 10/01/2002
• Published: 04/01/2004
• Est. Priority Date: 10/01/2002
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Vachuska, Thomas, Nguyen, Liem M.
• Application Number:
  US10/260,500
• Publication Number:
  US 20040064487A1
• Time in Patent Office: Days
• US Class Current: 707/204
• CPC Class Codes: G06F 16/214 Database migration support

Abstract

A method and apparatus is described to migrate database. Data transformations are specified in a configuration file. The configuration file contains both control information and data transformation information. The migration is performed automatically using the configuration file using an object-oriented migration application. A new database is created using the control information in the configuration file. The new database is populated with the appropriate data based on the data transformation information in the configuration file, resulting in a properly updated database.

Claims

1. A method for migrating a current database to an updated database, comprising:

starting a current database for migrating to an updated database;

reading a configuration file having both data transformation information and control information defining modifications to be made to the current database to effect a migration to the updated database;

exporting data from the current database;

creating the updated database based on control information in a configuration file;

moving the updated database to a target location; and

loading the updated database with new data files based on data transformation information in the configuration file.

2. The method as recited in claim 1, further comprising:

determining a version of the current database, and if the version is a same version as the updated database, then exiting before exporting data from the current database.

3. The method as recited in claim 1, wherein exporting data from the current data base further comprises stopping the current database.

4. The method as recited in claim 1, wherein loading the updated current data base further comprises starting the updated database.

5. The method as recited in claim 1, further comprising:

determining whether adequate storage space exists to migrate the current database, and if not, then exiting before exporting data from the current database.

6. The method as recited in claim 1, wherein the exporting generates comma separated files.

7. The method as recited in claim 1, further comprising:

moving the exported database files to a backup directory.

8. The method as recited in claim 1, further comprising:

automatically validating tables in the updated database based on database validation procedures.

9. The method as recited in claim 1, wherein the configuration file further comprises a plurality of actions corresponding to table and column information.

10. The method as recited in claim 9, wherein the plurality of actions are selected from a group consisting of add, remove, delete and update.

11. The method as recited in claim 1, further comprising:

automatically generating a skeleton configuration file having control information; and

editing the skeleton configuration file with data transformation information, resulting in the configuration file having both data transformation information and control information.

12. The method as recited in claim 11, wherein the configuration file is generated using a JAVA™

utility, and wherein the JAVA™

utility examines a schema for the current database and a schema and the updated database to determine differences in control information.

13. The method as recited in claim 12, wherein the control information comprises data types, table names, and column names.

14. A database migrator for transforming a current database into an updated database, comprising:

a module comprising a user interface running on a computing device capable of executing object-oriented computer programs;

a first section of object oriented computer code defining a migration model used by the user interface, the migration model using a configuration file having control information and data transformation information, wherein the configuration file defines changes required to transform a current database into an updated database;

a second section of object-oriented computer code defining a database transformer class; and

a third section of object-oriented computer code defining a database parser class.

15. The migrator as recited in claim 14, further comprising a fourth section of object-oriented computer code defining a database validator class.

16. The migrator as recited in claim 14, wherein the user interface is selected from a group of a graphic user interface (GUI) and a command line interface (CLUI).

17. The migrator as recited in claim 14, further comprising a further section of object-oriented computer code defining a database validator loader, wherein the validator loader reads a properties file and loads a plurality of validator instances, each validator instance corresponding to a database table.

18. The migrator as recited in claim 14, wherein the user interface allows a user to specify:

a database directory to migrate from;

a directory containing a new schema;

a temporary directory for migration;

a backup directory; and

a directory in which to place a migrated database.

19. The migrator as recited in claim 14, wherein a transformer method of the database transformer class is used to read the configuration file and perform database transformation.

20. The migrator as recited in claim 19, wherein for each table, columns to be transformed are stored into a sorted data structure, wherein each element in the sorted data structure represents a column to be transformed and has a corresponding action, and wherein for each column, control transformation is performed by modifying a control export file according to the data structure element that represents that column, and wherein for each column, the data transformation is performed by modifying the data export file according to the data structure element that represents that column.

21. The migrator as recited in claim 20, wherein data transformation utilizes a XtendedMessageFormat class to allow flexible concatenation of different fields of a record.

22. The migrator as recited in claim 14, further comprising automated means for generating a skeleton configuration file comprising data control information.

23. The migrator as recited in claim 22, wherein automated means for generating is a JAVA™

utility, the JAVA™

utility comparing a first schema corresponding to the current database and a second schema corresponding to the updated database.

24. A computer readable medium containing code sections for transforming a current database into an updated database, said medium comprising:

a first code section for implementing a user interface running on a computing device capable of executing object-oriented computer programs;

a second section of object oriented computer code defining a migration model used by the user interface, the migration model using a configuration file having control information and data transformation information, wherein the configuration file defines changes required to transform a current database into an updated database;

a third section of object-oriented computer code defining a database transformer class; and

a fourth section of object-oriented computer code defining a database parser class.

25. The computer readable medium as recited in claim 24, further comprising a fifth section of object-oriented computer code defining a database validator class.

26. The computer readable medium as recited in claim 24, wherein the user interface is selected from a group of a graphic user interface (GUI) and a command line interface (CLUI).

27. The computer readable medium as recited in claim 24, further comprising a further section of object-oriented computer code defining a database validator loader, wherein the validator loader reads a properties file and loads a plurality of validator instances, each validator instance corresponding to a database table.

28. The computer readable medium as recited in claim 24, wherein the user interface allows a user to specify;

a database directory to migrate from;

a directory containing a new schema;

a temporary directory for migration;

a backup directory; and

a directory in which to place a migrated database.

29. The computer readable medium as recited in claim 24, wherein a transformer method of the database transformer class is used to read the configuration file and perform database transformation.

30. The computer readable medium as recited in claim 29, wherein for each table, columns to be transformed are stored into a sorted data structure, wherein each element in the sorted data structure represents a column to be transformed and has a corresponding action, and wherein for each column, control transformation is performed by modifying a control export file according to the data structure element that represents that column, and wherein for each column, the data transformation is performed by modifying the data export file according to the data structure element that represents that column.