JP2003280955A - Method and system for updating definition information in data extraction - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To alleviate complication of operation for a user and prevent occurrences of an information mismatch due to re-inputting by minimizing re-inputting of information when updating definition information. <P>SOLUTION: In a method for updating the definition information in an data extraction, an associated information table associating user re-definition information in an extraction origin database with the definition information in an extraction destination database is created to be stored into a memory. When updating the user re-definition information, a table part not needed to be changed is remained unchanged even when the information table is updated, a new table part is created as associated information needed by the updating, and an associated information table corresponding to the updated user re- definition information is created by adding the table part newly created to the remaining table part in the memory. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a definition information updating method and system in data extraction.

[0002]

2. Description of the Related Art Conventionally, when extracting data from a general-purpose database into a database of an open relational database management system (RDBMS) (for example, Oracle, MS SQL Server, etc.),
Another host computer or workstation terminal is interposed between the general-purpose machine and the RDBMS, and data extraction is automatically performed under the control of this host computer or workstation terminal. This host computer or workstation terminal is equipped with software that creates a data extraction program that runs on a general-purpose machine, and uses the user redefinition information in the database of the general-purpose machine to make settings for data extraction. It is supposed to be possible.

Generally, when the definition of the database is changed, the range of influence accompanying the change is widened. Therefore, in order not to change the definition of the normal database, the FI is previously recorded in the record.
The LLER clause (spare area) is reserved, and the user program redefines the FILLER clause part of the record as an actual item and uses it to ensure flexibility in data usage. Open these record definition information
Even when a program that extracts data by reflecting it on the RDBMS database is generated, data extraction that correctly reflects these redefinition information is performed. The data once extracted on the open RDBMS is used on the RDBMS according to the record definition at the time of extraction.

[0004]

In the conventional system,
When the user redefinition of a record is changed on the general-purpose machine side, the definition information of the changed record is changed to the RDBMS again.
In order to reflect in the record of, the relation between the general-purpose machine database (extraction source) and the open system RDBMS (extraction destination) had to be manually done for all items.

When the number of set items is large or the number of changes of user redefinition information is large, the change of the record definition information of the database requires a lot of work for associating the items with each other, resulting in a great work load at the time of data transfer. Therefore, manual work errors are likely to occur, and the return loss is large.

The same is true when the definition for the open RDBMS is changed, and re-entry is required. This takes time for the user to re-enter the information once input, and halves the function for facilitating redefinition. Moreover, in addition to this, when re-inputting, input mistakes and input omissions occur, which is also a cause of trouble. Therefore, updating the user redefinition information results in great effort and risk for the user.

An object of the present invention is to provide a definition information updating method and system in data extraction which can solve the above-mentioned conventional problems.

[0008]

According to one aspect of the present invention, in a definition information updating method in data extraction,
When the user redefinition information of the extraction source database and the definition information of the extraction destination database are associated with each other and stored in a memory, and the user redefinition information is updated, the association information Of the table, the table portion that does not need to be changed even by the update is left as it is, and a new table portion is created as the association information required by the update,
Definition information update, characterized in that an association information table corresponding to the updated user redefinition information is generated by adding the newly created table portion on the memory to the table portion left as it is. A method is provided.

According to one embodiment of the present invention, the memory is a repository included in a computer that generates a data extraction program for performing data extraction from the extraction source database to the extraction destination database.

According to another embodiment of the present invention, the updating of the user redefinition information is performed by a program operating an extraction source database, and the updated user redefinition information is stored in the repository. The original user redefinition information and the previous user redefinition information are used as the import source user redefinition information, and the pre-update user redefinition information associated with the record definition is used as the previous user redefinition information. Including comparing.

According to yet another embodiment of the present invention,
The updating of the user redefinition information is performed on the user redefinition information captured in the repository, and the updated user redefinition information is reflected on the side of the program that operates the extraction source database. , The updated user redefinition information is used as the original user redefinition information, and the user redefinition information before update that is associated with the record definition is used as the previous user redefinition information. It includes comparing information with the pre-user redefinition information.

According to another aspect of the present invention, in the definition information updating method in data extraction, an association information table for associating the user redefinition information of the extraction source database with the definition information of the extraction destination database is created. When the definition information of the extraction destination database is stored in the memory and updated, the table portion of the association information table that does not need to be changed by the update is left as it is, and the association information required by the update is maintained. A new table portion is created as, and the newly created table portion is added to the left table portion on the memory, thereby creating an association information table corresponding to the updated definition information of the extraction destination database. Providing a definition information updating method characterized by generating It is.

According to one embodiment of the present invention, the memory is a repository included in a computer that generates a data extraction program for performing data extraction from the extraction source database to the extraction destination database.

According to another embodiment of the present invention, the table definition information of the extraction destination database is updated by the database management system managing the extraction destination database, and the updated table of the extraction destination database is updated. Including definition information in the repository.

According to yet another embodiment of the present invention,
Update of the table definition information of the extraction destination database,
It is included in the table definition information of the extraction destination database stored in the repository and reflects the updated table definition information on the side of the database management system that manages the extraction destination database.

According to still another aspect of the present invention, in the definition information updating system for data extraction, an association information table for associating the user redefinition information of the extraction source database with the definition information of the extraction destination database is stored. In the case of updating the first storage location for updating and the user redefinition information or the definition information of the extraction destination database, the table portion of the association information table that does not need to be changed by the update is stored as it is. Second storage location, new table portion creation means for creating a new table portion as association information required by the update, and new table portion creation in the table portion stored in the second storage location. Said updated by adding the table part created by the means Definition information update system comprising: a an association information table generating means for generating association information table corresponding to the use's redefined information or definition information of the extracted destination database is provided.

According to one embodiment of the present invention, the first storage location and the second storage location are data extraction programs for performing data extraction from the extraction source database to the extraction destination database. The new table part creating means and the association information table creating means are provided in a repository included in the computer that generates the data, and the new table part creating means and the association information table creating means are provided by a program for operating the data stored in the repository and implemented in the computer. .

According to yet another embodiment of the present invention,
There is provided a computer-readable recording medium in which a program for causing a computer to function as the above definition information updating system is recorded.

According to still another aspect of the present invention, there is provided a program for causing a computer to function as the above definition information updating system.

[0020]

BEST MODE FOR CARRYING OUT THE INVENTION Next, the present invention will be described in more detail with reference to the accompanying drawings with regard to the embodiments and examples of the present invention.

FIG. 1 shows an embodiment in which the present invention is applied to a host computer or workstation terminal for extracting data from a general-purpose machine database which is an extraction source database to an open RDBMS database which is an extraction destination database. It is a figure which shows the outline of a structure and function.

As shown in FIG. 1, a host computer or workstation terminal 30 is interposed between the general-purpose machine 10 and the RDBMS on the open system computer 20,
The host computer or workstation terminal 30 performs control for data extraction from the database 11 of the general-purpose machine 10 to the RDBMS database 21 on the open system computer 20. The host computer or workstation terminal 30 is equipped with software for generating a data extraction program for implementing the definition information updating method according to the present invention. Also, this host computer or workstation terminal 30
Contains a repository 31 which is an internal database.

The basic concept of the definition information updating method according to the present invention will be described with reference to the schematic explanatory view shown in the lower part of FIG.

It is assumed that the extraction source database definition information in the general-purpose device 10 which is the extraction source database management system is as shown at the left end of the lower part of FIG. 1, and the database 11 in the general-purpose device 10 which is the extraction source.
The user redefinition information of RD is as shown as X1, and the RD on the open system computer 20 that is the extraction destination
It is assumed that the corresponding definition information in the database 21 of the BMS is as shown as Y1 and that the definition information uses data. At this time, the repository 31 of the host computer or workstation terminal 30 stores an association information table x as association information that associates the user redefinition information X1 and the extraction destination database definition information Y1.

When data is used under such user redefinition information X1, the user redefinition information X1 is updated (revised) to the user redefinition information X2.
The procedure according to the invention for doing so is as follows. Of the association information table x of X1 and Y1 in the repository 31, the association information of unchanged portions A1, A2, and B is copied as it is to generate another association information table y1, and then manually. Added items C1 and C
By adding the definition information y2 of the association for the item 2 to y1, as the correspondence information on the table in the repository 31, the updated user redefinition information X2 referred to by the reference information
It is possible to generate association information y between the database definition information Y2 in the RDBMS of the extraction destination and take over the association information.

As an embodiment of the system of the present invention for carrying out such a method, a repository included in the computer 30 for generating a data extraction program for performing data extraction from the extraction source database to the extraction destination database. A first storage location for storing the association information table x that correlates the user redefinition information of the extraction source database and the definition information of the extraction destination database in 31 and the user redefinition information or the extraction destination database In the case of updating the definition information of, the table portion y1 of the association information table x stored in the first storage location that does not need to be changed by the update is provided with a second storage location for storing as it is. deep. Then, a new table part creating means for creating a new table part y2 as the association information required by the update is realized, and the new table part y2 created by the new table part creating means is stored in the second storage. An association information table creating means for generating an association information table y corresponding to the updated user redefinition information or the definition information of the extraction destination database by adding to the table portion y1 that does not need to be changed by updating at the place. A program capable of realizing the above is installed in the computer 30, and the repository 3 is installed in accordance with this program.
The data stored in 1 can be operated as described above.

In the case of the conventional method, when the contents of the user redefinition were updated, the association information had to be created anew, whereas according to the present invention, the user redefinition information as described above. Since it suffices to add and edit the association information corresponding to the updated portion of, the burden on the user is reduced.

Next, the details of the processing operation by the software that generates the data extraction program to which the definition information updating method based on the basic concept of the present invention as described above is applied will be described item by item.

1. Basic Operation FIG. 2 is for explaining a procedure of creating association information between user redefinition information and extraction destination database definition information used for controlling data extraction from the extraction source database 11 to the extraction destination database 21. FIG. 3 and FIG.
Is a flow chart of the procedure. The configuration shown in FIG. 2 and FIG.
In order to make it easy to understand the relationship with each procedure in the flowchart of FIG. 3, step numbers S1 to S6 showing each procedure in FIG.
Are shown in association with the corresponding arrows in FIG.

In order to create the association information between the user redefinition information and the extraction destination database definition information, first, as shown as step S1 in FIGS. 2 and 3, the extraction source database definition information (record Definition) to the repository 31. Further, as shown as step S2, the user redefinition information (user redefinition) is copied from the extraction source database 11 to the repository 31. Furthermore, as shown as step S3, the extraction destination database definition information (table definition) is copied from the extraction destination database 21 to the repository 31.

Next, as shown as step S4, the record definition in the extraction source database definition information and the user redefinition information related thereto are associated with each other. Then, as shown as step S5, a record to be extracted is selected from the extraction source database definition information. Then, as shown as step S6, the items in the extraction source record selected in the process of step S5 are associated with the columns in the extraction destination database (table). At this time, if necessary, processing such as processing a value using an arithmetic expression, setting a condition according to the value in the item, and dividing the value to be assigned to the column is performed. Explaining a specific example, in step S5, a record to be migrated in the database of the general-purpose machine is selected, and for example, from April 2001 to 12
Select and extract the month record. Also, step S
In step 6, for example, the value recorded in # 2 of the extraction destination database and the value recorded in # 3 are added to the table of # 4 of the extraction destination database, and association is also performed.

FIG. 4 shows database definition information on the extraction source database 11 and user redefinition information for redefining the record definition on the database 11 from the extraction source database 11 among the basic operations described above. Alternatively, a block diagram collectively shows a procedure of storing the information in the repository 31 of the workstation terminal 30 and a procedure of extracting the database definition information on the extraction destination database 21 and storing it in the repository 31. Here, the database definition information is a collection of information that includes, in addition to the record definition, a definition related to the relationship between the records and a definition related to the physical arrangement of the records.

FIG. 5 is a block diagram showing a procedure for creating user redefinition map information for associating the record definition in the extraction source database definition information and the user redefinition information related to it among the basic operations described above. It is shown collectively.

In FIG. 6, of the basic operations described above, the record to be extracted is selected from the extraction source database definition information, and if necessary, the selection condition at the time of record extraction is set, and the repository 31 is used as the schema link information. A block diagram collectively shows the procedure to be stored in.

FIG. 7 associates the items in the extraction source record selected in the previous step with the columns in the extraction destination database (table) among the basic operations described above, and, if necessary, the arithmetic expression. The block diagram shows the procedure for processing values using, and setting conditions based on the values in the items and dividing the values to be assigned to the columns, and storing them in the repository 31 as table map information. There is. In this way, by performing the previous steps, the subordinate information is created and linked to the copy of the user redefinition information.

2. Regarding Related Information In order to make it easier to understand what kind of information the “related information” created in the above-described procedure is, it will be collectively described below. The related information is divided into the following three types of information: user redefinition map information, schema link information, and table map information.

First, the user redefinition map information will be described. This user redefinition map information relates the definition information of the extraction source database with the user redefinition information redefined when the user uses it. This is information for. This is to associate the definition information of the extraction source database managed by the database management system as a general-purpose machine with the user redefinition information redefined when the user uses it. FIG. 8 is a diagram for explaining an example of user redefinition map information which is such related information, and includes definition information of an extraction source database and
An example of the user redefinition information corresponding thereto is shown side by side. In FIG. 8, for example, A in the definition information of the database is date data. The data is 20 in the database of general-purpose machines as a number indicating the date.
It is assumed that the 8-digit number 020227 is used.
In this case, the data of A is 20020227. However, in practice, if it is easier to use 4 digits and 4 digits, A is divided into A1 and A2 in the user redefinition, and the data of A1 is the year of the date. 2002, and the data of A2 is 0227 indicating the date of the date. Then, which part of the A data corresponds to the A data, and which part of the A2 data corresponds to the A data are linked.
This connection information becomes the user redefinition map information which is one related information. Such user redefinition map information is represented by using the address of the storage location of the database. For example, the data of A1 corresponds to what address of A is stored and which address of A2. The data may be an address map that associates which address of A corresponds to what is stored.

Next, the schema link information will be described. The schema link information indicates a condition for extracting a record from the extraction source database.
Although what is shown in FIG. 8 is one record unit, the extraction condition necessary for the extraction is the schema link information which is one of the related information.

Next, the table map information will be described. The table map information includes the user redefinition information of the database of the general-purpose machine which is the extraction source database and the definition information of the database of the open RDBMS which is the extraction destination database. Is to be associated with. This is because the database of the general-purpose machine and the data of the open RDBMS are different, so that the association is required.
Since there is a column for putting the result of some operation in this information, such an arithmetic expression is also a part of the information. FIG. 9 is a diagram for explaining an example of the table map information that is such related information, and shows an example of the user redefinition information of the extraction source database and the definition information of the extraction destination database side by side. ing. In the example shown in FIG. 9, the table map information is [A1: a
1, A2: a2, B: b, C1: c1, C2: c2, C
3: c3]. In this case, if the relationship between A1 and A2 and B is such that the data of A1 and the data of A2 are added to the data of B, this relationship is included in the table map information. Information such as [B = A1 + A2] is also added as the information to be shown.

3. Flow of Update Process of User Redefinition Information A detailed example of the procedure for updating the user redefinition information will be described with reference to FIGS. 10 and 11.

FIG. 10 shows a table 1 showing an example of the current user redefinition information and a table 2 showing the updated current user redefinition information side by side. FIG. 11 is a flow chart showing a processing procedure for updating the user redefinition information in this way. The current user redefinition information shown in Table 1 of FIG. 10 is already taken in the repository 31 and stored in association with the record definition.
This is called pre-user redefinition information. To update this to the user redefinition information as shown in Table 2 of FIG. 10, step S1 in the flow of FIG.
As shown by, the extraction source database management system 10 updates the user redefinition information. This updated user redefinition information is taken into the repository 31 and stored therein in step S2 in the flow of FIG.
The acquired information will be referred to as former user redefinition information.

As can be seen by comparing Table 1 and Table 2 in FIG. 10, the update of the user redefinition information in this example is 2
Number FILLER clause is changed to two items NEW-ITEM1 and NEW-ITEM2, and FILLER.

The change from the definition in Table 1 to the definition in Table 2 is:
This is done as follows. (1) NEW-ITEM-1 and N of NEW-REC1 in the FILLER clause of Table 1
Set two items of EW-ITEM-2. (2) The portion left over in (1) above is the FILLER clause. (3) Since NEW-ITEM-1 and NEW-ITEM-2 are added above the FILLER clause, the sequence numbers after the original FILLER clause will be shifted. (4) The group item name (NEW-REC-1) is entered in # 2. (5) Each item name (NEW-ITEM-1 and NEW-ITEM-2) is entered in # 3 and # 4. (6) Shift the FILLER clause and the following items by 3, and renumber the sequence numbers.

Next, when the original user redefinition information fetched in step S2 and the record definition are associated with each other,
As shown in step S3 of the flow of FIG. 11, the original user redefinition information and the previous user redefinition information are compared. The procedure for this comparison is to compare items before and after the FILLER clause,
Check if any items other than FILLER items have been changed. (1) Obtain one item of pre-user redefinition information in numerical order. (2) If it is a FILLER item, check the following items.

(A) It is checked whether or not the information of the item name immediately before this exists in the "former user redefinition information".
In the case of Table 1 in FIG. 10, since the item name before the FILLER item is KEY, it is confirmed whether the item name KEY exists. If there is no item before FILLER, this process is not executed.

(B) In the redefinition of the previous user, the item name and number next to the FILLER item are acquired. Check if the item name exists in the "former user redefinition information".

In the flow of FIG. 11, if the items do not match in step S3, an error is displayed in step S4, and if they match, the original user redefinition information changes to the previous user redefinition information. Overwrite. Next, in step S6, the update process of the table map information as the related information, which is the lower information, is performed. Some of the sequence numbers have been changed, so in the lower information,
Since there is a part where this number is entered, that part is updated.

FIG. 12 schematically shows the contents stored in the repository 31 when the user redefinition information is updated. As shown in FIG. 12, the pre-update user redefinition information shown in Table 1 stored in the repository 31 becomes the post-update user redefinition information shown in Table 2. At this time, according to the present invention. For example, the related information and subordinate information within the circle indicated by the dotted line are inherited and stored for each item. In the conventional method, the related information is not carried over to the post-update user redefinition information in Table 2.

4. Update processing of the extraction destination database definition information
Also updating the management of the flow extracted the database definition information, according to the present invention may be carried out by a similar to the case of updating the user re-definition information extraction source database described above techniques. FIG. 13 is a diagram similar to FIG. 1 for explaining an example of the procedure for updating the extraction destination database definition information.
FIG. 6 is a flow diagram illustrating the procedure.

As shown in the schematic explanatory view shown in the lower part of FIG. 13, the extraction source database definition information in the general-purpose machine 10 which is the database management system of the extraction source is the left end of the lower part of FIG. 13 in this case as well. And the user redefinition information of the database 11 in the general-purpose machine 10 as the extraction source is as X1 and the RDBMS of the open-type computer 20 as the extraction destination. It is assumed that the corresponding definition information in the database 21 is as shown as Y1 and the definition information uses data. At this time, the repository 31 of the host computer or workstation terminal 30 stores an association information table x as association information that associates the user redefinition information X1 and the extraction destination database definition information Y1.

Such extraction destination database definition information Y
When the data is used under 1, the procedure according to the present invention when updating (revising) the extraction destination database definition information Y1 to the table definition information Y2 is as follows. Of the association information table x of X1 and Y1 in the repository 31, the unchanged portions A1, A2,
By copying the associating information of B as it is, another associating information table y1 is generated, and thereafter, the definition information y2 of the associating the newly manually added items c1 and c2 is added to y1. As the correspondence information on the table in the repository 31, the association information y between the updated updated user redefinition information X2 to be referenced and the database definition information Y2 in the extraction destination RDBMS is generated, and the association information is inherited. It can be performed. Here, the table definition information is the same as the database definition information, and is a collection of information including a table definition on the RDBMS, a definition on the relation between the tables, and a definition on the physical arrangement between the tables.

In the case of the conventional method, when the contents of the extraction destination database definition information (table definition information) were updated, the association information had to be newly created, whereas according to the present invention, as described above. Add the association information corresponding to the updated part of the table definition information to
Since editing is sufficient, the burden on the user is reduced.

This will be explained with reference to the flow chart of FIG. 14. When it is desired to update the extraction destination database definition information Y1 shown in FIG. 13 to the table definition information Y2, FIG.
As shown in step S1 in the flow of 1., the extraction destination database management system 20 updates the table definition information Y1. This updated table definition information Y2 is stored in the repository 3 in step S2 in the flow of FIG.
It is captured in 1 and stored there. The acquired information will be called new table definition information. On the other hand, similarly to the above, the table definition information Y before update
1 is already stored in the repository 31, and this will be referred to as existing table definition information. Next, FIG.
As shown in step S3 of the flow of 4, the new table definition information and the existing table definition information are compared.
This comparison is performed for each item as in the case of the update process of the definition information for the user. In the flow of FIG. 14, if the items do not match in step S3, an error is displayed in step S4, and if they match, the new table definition information is overwritten on the existing table definition information. Next, in step S6, the update process of the table map information as the related information, which is the lower information, is performed. Since some sequence numbers have been changed, this number is included in some lower information, so that part is updated.

In the updating procedure of the table definition information described above, the table definition information is first updated on the extraction destination database management system side and reflected in the repository. However, the present invention is not limited to this. Instead, the table definition information stored in the repository may be updated and reflected in the database on the extraction destination database management system side. Furthermore, the same can be said in the process of updating the extraction source user redefinition information. First, the user redefinition information stored in the repository is updated and the extraction source database is updated. It may be reflected on the side of the program to be operated.

According to the present invention, as described above, the user redefinition information of the database on the general-purpose machine and the open RDB.
Import the database definition information of MS into the repository,
By associating each definition information with each other, generating a program for extracting data from the database on the general-purpose machine, and executing this generated program,
From a database on a general-purpose machine to an open RDBMS,
The selected data can be transferred.

[0056]

According to the present invention, in automatically creating a data extraction program for data extraction, the relation between the current extraction source user redefinition information and the extraction destination table definition information in the internal database (repository). By taking over and utilizing the information (correspondence information) and minimizing the user's input, it is possible to reduce the user's omission of input and input error.

The present invention is effective when there is no change in the contents of other items, such as "adding an item in the FILLER clause of user redefinition information" which is the most frequently occurring in the field.

Further, when the number of set items is large or the number of times the user redefinition information is changed is large, the work of associating the items increases, but according to the present invention, the user redefinition after updating is performed. Among the related information (correspondence information) between the current extraction source user redefinition information and the extraction destination table definition information, the definition information of the items that do not change for the user is left as it is, and new definition information is taken over. By diverting as, the user does not have to re-input the association information once input in the past, and the information only needs to be added about the update content accompanied by the change.

In short, according to the present invention, the re-input of information is minimized to reduce the complexity for the user and prevent the inconsistency of information due to the re-input. Useful for that.

[Brief description of drawings]

FIG. 1 is a diagram showing an outline of a configuration and a function of an embodiment to which the present invention is applied.

FIG. 2 is a diagram for explaining a procedure for creating association information between user redefinition information and extraction destination database definition information.

FIG. 3 is a flowchart of a procedure for creating association information.

FIG. 4 is a block diagram collectively showing a procedure for storing extraction source database definition information, user redefinition information, and extraction destination database definition information in a repository.

FIG. 5 is a block diagram collectively showing a procedure for creating user redefinition map information.

FIG. 6 is a block diagram collectively showing a procedure for storing schema link information in a repository.

FIG. 7 is a block diagram collectively showing a procedure for storing table map information in a repository.

FIG. 8 is a diagram illustrating an example of user redefinition map information.

FIG. 9 is a diagram for explaining an example of table map information.

FIG. 10 is a diagram showing an example of the current user redefinition information and the updated user redefinition information side by side.

FIG. 11 is a flowchart showing a processing procedure for updating user redefinition information.

FIG. 12 is an image diagram showing stored contents in a repository when updating user redefinition information.

FIG. 13 is a diagram similar to FIG. 1 for explaining an example of a procedure for updating the extraction destination database definition information.

FIG. 14 is a flowchart illustrating a procedure for updating extraction destination database definition information.

[Explanation of symbols]

10 General Purpose Machine 11 General Purpose Machine Database 20 Open Computer 21 RDBMS Database on Open Computer 30 Host Computer or Workstation Terminal 31 Repository

Claims (12)

[Claims] 1. A method of updating definition information in data extraction, wherein an association information table that associates user redefinition information of an extraction source database with definition information of an extraction destination database is created and stored in a memory, and In the case of updating the user redefinition information, the table portion of the association information table that does not need to be changed by the update is left as it is, and a new table portion is created as the association information required by the update, Definition information update, characterized in that an association information table corresponding to the updated user redefinition information is generated by adding the newly created table portion on the memory to the table portion left as it is. Method. 2. The definition information updating method according to claim 1, wherein the memory is a repository included in a computer that generates a data extraction program for performing data extraction from the extraction source database to the extraction destination database. 3. The updating of the user redefinition information is performed by a program that operates an extraction source database, and the updated user redefinition information is imported into the repository as original user redefinition information, and a record The method includes comparing the original user redefinition information with the previous user redefinition information, using the user redefinition information before update associated with the definition as the previous user redefinition information. The definition information updating method described in 2. 4. The user redefinition information is updated with respect to the user redefinition information taken into the repository, and the updated user redefinition information is stored in a program that operates an extraction source database. The updated user redefinition information is used as the original user redefinition information, and the user redefinition information before update that is associated with the record definition is used as the previous user redefinition information. The definition information updating method according to claim 2, further comprising comparing the original user redefinition information and the preceding user redefinition information. 5. A method of updating definition information in data extraction, wherein an association information table that associates user redefinition information of an extraction source database with definition information of an extraction destination database is created and stored in a memory. When updating the definition information of the extraction destination database, the table portion of the association information table that does not need to be changed by the update is left as it is, and a new table portion is created as the association information required by the update. The definition is characterized in that the newly created table part is added to the left table part on the memory to generate an association information table corresponding to the updated definition information of the extraction destination database. Information update method. 6. The definition information updating method according to claim 5, wherein the memory is a repository included in a computer that generates a data extraction program for performing data extraction from the extraction source database to the extraction destination database. 7. The table definition information of the extraction destination database is updated by a database management system that manages the extraction destination database, and the updated table definition information of the extraction destination database is reflected in the repository. 7. The definition information updating method according to claim 6, which includes. 8. The table definition information of the extraction destination database is updated to the table definition information of the extraction destination database stored in the repository, and the updated table definition information is managed in the extraction destination database. The definition information updating method according to claim 6, further comprising reflecting the information on the database management system side. 9. A definition information updating system for data extraction, comprising: a first storage location for storing an association information table that associates user redefinition information of an extraction source database with definition information of an extraction destination database;
When updating the user redefinition information or the definition information of the extraction destination database, a second storage location for storing a table portion of the association information table that does not need to be changed even by the update, and New table part creating means for creating a new table part as association information required by updating, and the table part created by the new table part creating means is added to the table part stored in the second storage location. Accordingly, the definition information updating system is provided with an association information table creating unit that creates an association information table corresponding to the updated user redefinition information or the definition information of the extraction destination database. 10. The first storage location and the second storage location are provided in a repository included in a computer that generates a data extraction program for performing data extraction from the extraction source database to the extraction destination database. 10. The definition information updating system according to claim 9, wherein the new table part creating means and the association information table creating means are provided by a program for operating data stored in a repository which is mounted on the computer. . 11. A computer-readable recording medium in which a program for causing a computer to function as the definition information updating system according to claim 9 or 10 is recorded. 12. A program for causing a computer to function as the definition information updating system according to claim 9.