CN108572994A - A processing method and server for data migration - Google Patents

Abstract

Embodiments of the present invention provide a data migration processing method and server, the method comprising: extracting the data to be migrated from the first database; Two rules corresponding to database data types, wherein the node network is mapped with the corresponding relationship between the data type of the data to be migrated and the rules; according to the matched rules, the data to be migrated is migrated to the in the second database. The server executes the above method. The data migration processing method and server provided by the embodiments of the present invention can reduce the workload of data migration personnel and complete automatic data migration between different databases, thereby improving the efficiency of data migration.

Description

A processing method and server for data migration

technical field

The embodiments of the present invention relate to the technical field of data processing, and in particular to a data migration processing method and server.

Background technique

With the rapid development of information technology, the data volume of enterprises has shown explosive growth, and the rapid growth of database access and data volume has correspondingly increased the database processing capacity and computing intensity, making data migration between different database systems appears to be particularly important.

MYSQL database is one of the alternatives to the existing ORACLE database. In the existing technology, the data in the ORACLE data table is exported by using SQL Developer in ORACLE, and then the data types in the ORACLE data table are matched by experienced migration personnel. Create the data type corresponding to MYSQL, and then use the Work Bench of MYSQL to create a data table and import the matched data to complete the data migration from the ORACLE database to the MYSQL database. However, the technical definitions of heterogeneous data in different databases are different. It makes database cross-platform and cross-structure migration difficult and heavy, and depends on the experience and technical level of the migration personnel.

Therefore, how to reduce the workload of data migration personnel and complete the automatic migration of data between different databases, so as to improve the efficiency of data migration, has become an urgent problem to be solved.

Contents of the invention

Aiming at the problems existing in the prior art, embodiments of the present invention provide a data migration processing method and server.

On the one hand, an embodiment of the present invention provides a data migration processing method, including:

Extracting the data to be migrated in the first database;

According to the preset node network and the data type of the data to be migrated, match the rules corresponding to the data type of the second database, wherein the node network is mapped with the data type of the data to be migrated and the rule Correspondence between;

Migrate the data to be migrated to the second database according to the matched rules.

On the other hand, an embodiment of the present invention provides a processing server for data migration, including:

An extraction module, configured to extract the data to be migrated in the first database;

A matching module, configured to match a rule corresponding to the data type of the second database according to the preset node network and the data type of the data to be migrated, wherein the node network is mapped with the data type of the data to be migrated Correspondence with said rules;

The migration module is configured to migrate the data to be migrated to the second database according to the matched rules.

The data migration processing method and server provided by the embodiments of the present invention can reduce the workload of data migration personnel and complete automatic data migration between different databases, thereby improving the efficiency of data migration.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

1 is a schematic flow diagram of a processing method for data migration according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a node network according to an embodiment of the present invention;

3 is a schematic structural diagram of a processing server for data migration according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a server entity provided by an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Fig. 1 is a schematic flowchart of a processing method for data migration according to an embodiment of the present invention. As shown in Fig. 1 , a processing method for data migration provided by an embodiment of the present invention includes the following steps:

S1: Extract data to be migrated from the first database.

Specifically, the server extracts the data to be migrated from the first database. It should be noted that: the first database can be an ORACLE database, and the data to be migrated can be extracted from the metadata list in the ORACLE database. The metadata can include: user information, table name information, table field information, table partition information, and index information , comment information, field type information, field comment information, etc.

S2: Match the rules corresponding to the second database data type according to the preset node network and the data type of the data to be migrated, wherein the node network is mapped with the data type of the data to be migrated and the Correspondence between rules.

Specifically, the server matches the rules corresponding to the data type of the second database according to the preset node network and the data type of the data to be migrated, wherein the node network is mapped with the data type of the data to be migrated and Correspondence between the rules. It should be noted that: the data type of the data to be migrated can be the data type of the ORACLE database, and the data type can specifically include: VARCHAR, CHAR and other character types, and can also include numerical values, etc. The second database can be a MYSQL database. The data types of the ORACLE database and the MYSQL database have different corresponding rules, for example: VARCHAR, CHAR is the character data type in the ORACLE database, and TEXT is the text data type in the MYSQL database. They are essentially the same data type, and essentially the same data type corresponds to the same rule. However, the numerical data type in the ORACLE database is considered to be substantially different from the character data types such as VARCHAR and CHAR, and multiple data types with substantially different data types correspond to multiple rules. It can be considered that the matching rules are the data types of the ORACLE database and the MYSQL database. Correspondence between.

S3: Migrate the data to be migrated to the second database according to the matched rule.

Specifically, the server migrates the data to be migrated to the second database according to the matched rule. It should be noted that: referring to the VARCHAR embodiment above, the rule that CHAR corresponds to TEXT can complete the migration of data corresponding to character data types, and similarly, according to other rules, the migration of data corresponding to all data types such as numeric data types can be completed.

The data migration processing method provided by the embodiment of the present invention can reduce the workload of data migration personnel, complete automatic data migration between different databases, and thereby improve the efficiency of data migration.

On the basis of the foregoing embodiments, the node network includes class nodes, rule nodes and intermediate nodes, wherein:

Each class node corresponds to each data type of the data to be migrated, each rule node corresponds to each rule corresponding to the second database data type, and the intermediate node is located between the class node and the rule node Between, the intermediate node is bound with the attribute information of the data type of the data to be migrated according to the same rule.

Each of the rule nodes is connected to each of the intermediate nodes one by one, and multiple class nodes with the same attribute information are respectively connected to the intermediate nodes corresponding to the same rule node.

Specifically, FIG. 2 is a schematic structural diagram of a node network according to an embodiment of the present invention. As shown in FIG. 2, the node network in the server may include multiple class nodes, multiple regular nodes, and multiple intermediate nodes, wherein:

Each class node corresponds to each data type of the data to be migrated, and each rule node corresponds to each rule corresponding to the second database data type. Due to the difference between the first database and the second database, the class node The number can be more than, less than, or equal to the number of regular nodes, the intermediate nodes are located between the class nodes and the regular nodes, the number of regular nodes can be equal to the number of intermediate nodes, and the intermediate nodes The node is bound with the attribute information of the data type that conforms to the same rule to be migrated. The attribute information can be understood as characters or numerical values with reference to the above-mentioned embodiments. The first three types of nodes shown in Figure 2 can be considered to have the same The attribute information of the data type, they are respectively connected to the intermediate node on the same rule, and then connected to the rule node of the same rule through the intermediate node.

Each of the rule nodes is connected to each of the intermediate nodes one by one, and multiple class nodes with the same attribute information are respectively connected to the intermediate nodes corresponding to the same rule node.

The data migration processing method provided by the embodiment of the present invention further optimizes the matching rules used for automatic data migration by setting class nodes, rule nodes and intermediate nodes in the node network, thereby improving the efficiency of data migration.

On the basis of the foregoing embodiments, the node network further includes:

Each class node is one-to-one connected to each rule node without passing through the intermediate node.

Specifically, the node network in the server further includes: each class node connected to each rule node one by one without going through the intermediate node. As shown in Fig. 2, the latter class node can be regarded as attribute information that does not have the same data type as other class nodes, so it can be directly connected to the rule node individually and one by one.

The data migration processing method provided by the embodiment of the present invention further optimizes the matching rules used for automatic data migration by setting up class nodes directly connected to regular nodes in the node network, thereby improving the efficiency of data migration.

On the basis of the above embodiments, the matching of the rules corresponding to the second database data type according to the preset node network and the data type of the data to be migrated includes:

If it is determined that the data type of the data to be migrated contains the attribute information bound by the intermediate node, then the intermediate node matches the rule corresponding to the second database data type.

Specifically, if the server determines that the data type of the data to be migrated contains attribute information bound to the intermediate node, the intermediate node matches the rule corresponding to the second database data type. An example is as follows: If the data type of the data to be migrated is VARCHAR and CHAR, and its attribute information is character type, and the server matches an intermediate node whose data type is VARCHAR and CHAR, and whose attribute information is character type, the intermediate node Matches to the TEXT data type in the MYSQL database. The corresponding relationship between them is the rule that the data type of the ORACLE database corresponds to the data type of the MYSQL database.

or,

If it is determined that the data type of the data to be migrated does not contain the attribute information bound to the intermediate node, the class node corresponding to the data type of the data to be migrated is directly matched with the rule corresponding to the second database data type.

Specifically, if the server determines that the data type of the data to be migrated does not contain the attribute information bound to the intermediate node, it will directly match the class node corresponding to the data type of the data to be migrated with the data type of the second database. corresponding rules. An example is as follows: If the data type of the data to be migrated is X, and its attribute information is A, all intermediate nodes in the node network are not bound with A attribute information, and the data type corresponding to the data type X in the MYSQL database is Y, Then the class node corresponding to X directly matches the rule corresponding to the MYSQL database data type Y.

The data migration processing method provided by the embodiment of the present invention can further reduce the workload of data migration personnel and complete data migration between different databases by indirect matching of intermediate nodes or direct matching of rules corresponding to the second database data type by class nodes. Automatic migration, thereby improving the efficiency of data migration.

On the basis of the foregoing embodiments, the method further includes:

The node network is updated according to the change of the data type of the data to be migrated in the first database.

Specifically, the server updates the node network according to the change of the data type of the data to be migrated in the first database. It should be noted that: usually, the change of the data type of the data to be migrated in the first database is caused by the version upgrade of the first database, so the node network should also be correspondingly updated synchronously.

The data migration processing method provided by the embodiment of the present invention optimizes the matching rules used for automatic data migration by continuously updating the node network, thereby improving the efficiency of data migration.

On the basis of the above embodiments, updating the node network according to the change of the data type of the data to be migrated in the first database includes:

Traversing all the changed data to be migrated in the first database, for the newly added data type, if the attribute information of the newly added data type is associated with the attribute information bound to the intermediate node, then add For the class node of the newly added data type, connect the newly added class node with the associated intermediate nodes one by one.

Specifically, the server traverses all the changed data to be migrated in the first database. For the newly added data type, if it is determined that the attribute information of the newly added data type is bound to the attribute information of the intermediate node Associating, adding a class node for the added data type, and connecting the added class node with associated intermediate nodes one by one. It should be noted that: the server traverses all the data to be migrated after the Oracle database version upgrade, and for the newly added data type in the data to be migrated, it determines whether the attribute information of the newly added data type is associated with the attribute information bound by the intermediate node , continue to refer to the example of the above embodiment: one of the data types before the ORACLE database version upgrade is VARCHAR, and after the upgrade, it is changed to VARCHAR3, and the attribute information of the bound data information VARCHAR in the intermediate node is character type, and VARCHAR3 is also character type, it can be considered that VARCHAR is associated with VARCHAR3, that is, attribute information is all character type. The class node corresponding to the VARCHAR3 is added, and the newly added class node is connected to an intermediate node already bound with a data type of VARCHAR and attribute information of character type.

Test whether the newly added class node, the intermediate node, and the corresponding rule node are successfully connected.

Specifically, the server tests whether the newly added class node, the intermediate node, and the corresponding rule node are successfully connected. It should be noted that the test method may be to insert simulation data into newly added class nodes, intermediate nodes, and corresponding rule nodes, and then test whether the connection is successful.

If the connection is successful, activate the newly added class node, the intermediate node, and the corresponding rule node.

Specifically, if the server determines that the connection is successful, it activates the newly added class node, the intermediate node, and the corresponding rule node. It should be noted that the activated new class nodes, intermediate nodes, and corresponding updated node networks of the corresponding rule nodes can be used for data migration after the ORACLE database version is upgraded.

or,

If the attribute information of the newly added data type is not associated with the attribute information bound to the intermediate node, then add a class node for the newly added data type, and reset the A new rule whose type is matched and corresponding to the data type of the second database is connected, and the newly added class node is connected with the newly added rule node corresponding to the new rule one by one.

Specifically, if the server determines that the attribute information of the newly added data type is not associated with the attribute information bound to the intermediate node, it adds a class node for the newly added data type, and resets the The newly added data type matches the new rule corresponding to the second database data type, and connects the added class node to the added rule node corresponding to the new rule one by one. It should be noted that: the server traverses all the data to be migrated after the version upgrade of the ORACLE database. For the newly added data types in the data to be migrated, it is determined that the attribute information of the newly added data type is not associated with the attribute information bound by the intermediate node. Then it can be considered that after the upgrade of the ORACLE database version, a new data type that is not available in the original node network is added, and it is not only necessary to add a corresponding class node for the new data type, but also to reset the newly added data type to match the The new rules corresponding to the data type of the second database, and the reset of the new rules can be written by relevant personnel and stored in the node network, and the newly added class nodes are connected to the newly added rule nodes corresponding to the new rules one by one.

Test whether the newly added class node and the corresponding newly added rule node are successfully connected.

Specifically, the server tests whether the newly added class node and the corresponding newly added rule node are connected successfully. Reference may be made to the foregoing embodiments, and details are not repeated here.

If the connection is successful, the newly added class node and the corresponding newly added rule node are activated.

Specifically, if the server determines that the connection is successful, it activates the newly added class node and the corresponding newly added rule node. Reference may be made to the foregoing embodiments, and details are not repeated here.

The data migration processing method provided by the embodiment of the present invention specifically optimizes the matching rules used for automatic data migration for newly added data types, thereby improving the efficiency of data migration.

On the basis of the above embodiments, the updating of the node network according to the change of the data type of the data to be migrated in the first database includes:

Traversing all the changed data to be migrated in the first database, for the deleted data type, if the attribute information of the deleted data type belongs to the original attribute information bound by the intermediate node, freeze The class node corresponding to the deleted data type.

Specifically, the server traverses all the changed data to be migrated in the first database. For the deleted data type, if it is determined that the attribute information of the deleted data type belongs to the original intermediate node binding attribute information, freeze the class node corresponding to the deleted data type. What needs to be explained is: the server traverses all the data to be migrated after the upgrade of the ORACLE database version. The corresponding data type can be considered to have been deleted. If the attribute information of the deleted data type belongs to the attribute information bound by the original intermediate node, that is: the deleted data type was originally connected to the intermediate node, it will be frozen The class node corresponding to the deleted data type, but keep the intermediate node.

or,

If the attribute information of the deleted data type does not belong to the original attribute information bound to the intermediate node, freezing the class node corresponding to the deleted data type and the corresponding rule node.

Specifically, if the server determines that the attribute information of the deleted data type does not belong to the original attribute information bound to the intermediate node, it freezes the class node corresponding to the deleted data type and the corresponding rule node. What needs to be explained is: if the attribute information of the deleted data type does not belong to the attribute information bound by the original intermediate node, that is: the deleted data type was not originally connected to an intermediate node, but directly connected with corresponding rules node, thus freezing that type of node and the corresponding rule node.

The data migration processing method provided by the embodiment of the present invention specifically optimizes the matching rules used for automatic data migration for deleted data types, thereby improving the efficiency of data migration.

On the basis of the above embodiments, before the step of extracting the data to be migrated in the first database, the method further includes:

The address information, the identifier, and the protocol used for the exported data of the metadata module in the first database are acquired.

Specifically, the server acquires the address information, the identifier, and the protocol used for exporting the metadata module in the first database. It should be noted that the address information can include the IP address of the device where the ORACLE database is located and the port number occupied, the identifier can be SID (Security Identifiers, hereinafter referred to as "SID"), and the protocol used for exporting data can be : OCI (ORACLE call interface Oracle Call Interface) or ORACLE thin.

A link between the first database and the second database is established based on the address information, the identifier, and the protocol used to derive the data.

Specifically, the server establishes a link between the first database and the second database according to the address information, the identifier, and the protocol used for exporting data. It should be noted that: through the description of the above embodiments, a link between the ORACLE database and the MYSQL database is established.

The data migration processing method provided by the embodiment of the present invention ensures normal progress of automatic data migration by first establishing a link between the first database and the second database.

Fig. 3 is a schematic structural diagram of a processing server for data migration according to an embodiment of the present invention. As shown in Fig. 3 , an embodiment of the present invention provides a processing server for data migration, including an extraction module 1, a matching module 2 and a migration module 3, wherein :

The extraction module 1 is used to extract the data to be migrated in the first database, and the matching module 2 is used to match the rules corresponding to the data type of the second database according to the preset node network and the data type of the data to be migrated, wherein , the node network is mapped with the corresponding relationship between the data type of the data to be migrated and the rules, and the migration module 3 is used to migrate the data to be migrated to the second database according to the matched rules .

Specifically, the extraction module 1 is used to extract the data to be migrated in the first database, the extraction module 1 sends the data to be migrated to the matching module 2, and the matching module 2 is used to data type, matching a rule corresponding to the second database data type, wherein, the node network is mapped with the corresponding relationship between the data type of the data to be migrated and the rule, and the matching module 2 sends the matched rule For the migration module 3, the migration module 3 is configured to migrate the data to be migrated to the second database according to the matched rules.

The data migration processing server provided by the embodiment of the present invention can reduce the workload of data migration personnel and complete automatic data migration between different databases, thereby improving the efficiency of data migration.

On the basis of the foregoing embodiments, the matching module 2 is specifically used for:

If it is determined that the data type of the data to be migrated contains the attribute information bound by the intermediate node, then the intermediate node matches the rule corresponding to the data type of the second database; or, if it is determined that the data to be migrated is known. If the data type does not contain the attribute information bound to the intermediate node, then the class node corresponding to the data type of the data to be migrated directly matches the rule corresponding to the second database data type.

Specifically, the matching module 2 is specifically configured to: if it is determined that the data type of the data to be migrated contains the attribute information bound by the intermediate node, then the intermediate node matches the data type corresponding to the second database data type. or, if it is judged that the data type of the data to be migrated does not contain the attribute information bound to the intermediate node, then the class node corresponding to the data type of the data to be migrated is directly matched with the second database data type corresponding rules.

The data migration processing server provided by the embodiment of the present invention can further reduce the workload of data migration personnel and complete the data transfer between different databases through indirect matching by intermediate nodes or direct matching by class nodes to the rules corresponding to the data types of the second database. Automatic migration, thereby improving the efficiency of data migration.

The data migration processing server provided by the embodiments of the present invention can be specifically used to execute the processing procedures of the foregoing method embodiments, and its functions will not be described in detail here, and reference can be made to the detailed description of the foregoing method embodiments.

FIG. 4 is a schematic structural diagram of a server entity provided by an embodiment of the present invention. As shown in FIG. 4 , the server includes: a processor (processor) 401, a memory (memory) 402, and a bus 403;

Wherein, the processor 401 and the memory 402 complete mutual communication through the bus 403;

The processor 401 is used to call the program instructions in the memory 402 to execute the methods provided by the above method embodiments, for example, including: extracting the data to be migrated in the first database; according to the preset node network, and The data type of the data to be migrated is matched with a rule corresponding to the data type of the second database, wherein the node network is mapped with a corresponding relationship between the data type of the data to be migrated and the rule; According to the rule, the data to be migrated is migrated to the second database.

This embodiment discloses a computer program product, the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program includes program instructions, and when the program instructions are executed by the computer, the computer The methods provided by the above method embodiments can be executed, for example, including: extracting the data to be migrated in the first database; according to the preset node network and the data type of the data to be migrated, matching A corresponding rule, wherein the node network is mapped with a corresponding relationship between the data type of the data to be migrated and the rule; according to the matched rule, the data to be migrated is migrated to the second database .

This embodiment provides a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions cause the computer to execute the methods provided in the above method embodiments, for example, including : extract the data to be migrated in the first database; match the rules corresponding to the data type of the second database according to the preset node network and the data type of the data to be migrated, wherein the node network is mapped with the The corresponding relationship between the data type of the data to be migrated and the rule; according to the matched rule, the data to be migrated is migrated to the second database.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

The server and other embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, Located in one place, or can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative efforts.

Through the above description of the implementations, those skilled in the art can clearly understand that each implementation can be implemented by means of software plus a necessary general hardware platform, and of course also by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic discs, optical discs, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, not to limit them; although the embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art The skilled person should understand that: it is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the present invention The scope of the technical solution of each embodiment of the embodiment.

Claims (10)

1. a kind of processing method of Data Migration, which is characterized in that including：

Extract the data to be migrated in first database；

According to pre-set meshed network and the data type of the data to be migrated, matching and the second database data The corresponding rule of type, wherein the meshed network is mapped with the data type of the data to be migrated and the rule Between correspondence；

It, will be in the Data Migration to be migrated to second database according to the rule after matching.

2. according to the method described in claim 1, it is characterized in that, the meshed network include class node, regular node and in Intermediate node, wherein：

Each class node is corresponding with each data type of the data to be migrated, and each regular node is corresponding with each with second The corresponding rule of database datatype, the intermediate node are described between the class node and the regular node Intermediate node binds the attribute information for having the data type for meeting same rule data to be migrated；

Each regular node is connected one by one with each intermediate node, and the identical class node of multiple attribute informations distinguishes phase It is connected in intermediate node corresponding with the same regular node.

3. according to the method described in claim 2, it is characterized in that, the meshed network further includes：

Not via the intermediate node, each class node being connected one by one with each regular node.

4. method according to claim 1 or 2 or 3, which is characterized in that it is described according to pre-set meshed network, with And the data type of the data to be migrated, rule corresponding with the second database datatype is matched, including：

If judging to know the attribute information that the data type of the data to be migrated contains the intermediate node binding, by described Intermediate node matches rule corresponding with the second database datatype；

Or,

If judging to know the attribute information that the data type of the data to be migrated does not contain intermediate node binding, directly By the corresponding class node matching of the data type of the data to be migrated rule corresponding with the second database datatype.

5. according to the method described in claim 1, it is characterized in that, the method further includes：

According to the variation of the data type of data to be migrated in the first database, the meshed network is updated.

6. according to the method described in claim 5, it is characterized in that, described according to data to be migrated in the first database The variation of data type updates the meshed network, including：

The data to be migrated in the first database after all changes are traversed, for newly-increased data type, if described new The attribute information of the data type of increasing is associated with the attribute information that the intermediate node is bound, then increases newly for described newly-increased The class node of data type, and newly-increased class node is connected one by one with associated intermediate node；

Test the newly-increased class node, the intermediate node and corresponding regular node whether successful connection；

If successful connection, the newly-increased class node, the intermediate node and corresponding regular node are activated；

Or,

If the attribute information of the newly-increased data type is unrelated to the attribute information that the intermediate node is bound, increase newly For the class node of the newly-increased data type, and reset it is matching with the newly-increased data type, with second The corresponding new rule of database datatype, and by newly-increased class node and new regular corresponding newly-increased regular node phase one by one Even；

Test the newly-increased class node and accordingly newly-increased regular node whether successful connection；

If successful connection, activates the newly-increased class node and increase regular node newly accordingly.

7. method according to claim 5 or 6, which is characterized in that described according to number to be migrated in the first database According to data type variation, update the meshed network, including：

The data to be migrated in the first database after all changes are traversed, for the data type being deleted, if institute The attribute information for stating the data type being deleted belongs to the attribute information of the former intermediate node binding, then freeze it is described by The corresponding class node of data type of deletion；

Or,

If the attribute information of the data type being deleted is not belonging to the attribute information of the former intermediate node binding, freeze The corresponding class node of data type and the corresponding regular node being deleted described in knot.

8. according to the method described in claim 1, it is characterized in that, extraction first database in data to be migrated the step of with Before, the method further includes：

It obtains the address information of meta data block in first database, identifier and exports agreement used in data；

According to described address information, identifier and export data used in agreement, establish the first database with it is described Link between second database.

9. a kind of processing server of Data Migration, which is characterized in that including：

Extraction module, for extracting the data to be migrated in first database；

Matching module, for according to the data type of pre-set meshed network and the data to be migrated, matching and the The corresponding rule of two database datatypes, wherein the meshed network is mapped with the data type of the data to be migrated With the correspondence between the rule；

Transferring module is used for according to the rule after matching, will be in the Data Migration to be migrated to second database.

10. server according to claim 9, which is characterized in that the matching module is specifically used for：

If judging to know the attribute information that the data type of the data to be migrated contains the intermediate node binding, by described Intermediate node matches rule corresponding with the second database datatype；

Or,

If judging to know the attribute information that the data type of the data to be migrated does not contain intermediate node binding, directly By the corresponding class node matching of the data type of the data to be migrated rule corresponding with the second database datatype.