JPH0543140B2 - - Google Patents

Description

[Detailed description of the invention]

[Industrial Field of Application] The present invention relates to a method for comparing hierarchical databases, and more particularly to a method for comparing hierarchical databases that can compare the access order of records at the same time as comparing the contents of data. [Prior Art] In recent years, with the rapid increase in online transactions and the increase in large-scale and large-capacity databases, it has become necessary to migrate (convert) from conventional database systems to large-scale database systems. Along with this system migration,
A database is migrated, but in order to verify the validity of the database after migration, it is necessary to compare the database before and after migration. To compare databases, you must compare the data contents (physical comparison) and at the same time compare the access order of the records, that is,
It is necessary to compare the logical relationships of records. As a conventional technology of this kind, for example,
Publication No. 57-31040 "Data comparison method", 56-
Publication No. 97144 "File comparison method" can be mentioned. [Problems to be solved by the invention] However, although conventionally known compare programs have the function of comparing data contents, they do not consider comparing the access order of records, and the database It was insufficient to perform a comparison. The present invention has been made in view of the above circumstances, and its purpose is to solve the above-mentioned problems in the conventional database comparison method, and to compare not only the data contents but also the access order of records. The purpose of this invention is to provide a method for comparing hierarchical databases. [Means for Solving the Problems] The above object of the present invention is to provide level information for each record indicating the hierarchy in which the record type to which the record belongs exists in a hierarchical database hierarchically configured with a plurality of records. When comparing two hierarchical databases by associating them with access information indicating the access order of record types, the level information and access information corresponding to the records constituting one hierarchical database and the hierarchical type of the other This is achieved by a hierarchical database comparison method that compares level information and access information corresponding to records constituting the database. [Operation] In the present invention, the determination of record correspondence is performed by comparing the level numbers and record codes of records in the reference database and records in the comparison database, and determining the comparison result. Records with different access orders cannot be matched, making it possible to compare the access orders of the records. [Example] Hereinafter, an example of the present invention will be described in detail based on the drawings. FIG. 3 is a diagram showing an example of the structure of a database to be compared. This database has record types A10, B20, C30, D40, E5
It consists of 5 record types: 0. In order to physically compare two records in a database, that is, to compare the data contents, it is assumed that the logical relationship between the two records to be compared, that is, the access order of the records match.
In the present invention, mapping of the logical relationship between two records (hereinafter referred to as "record mapping")
This is done using two parameters: record code and level number. Next, record codes and level numbers will be explained. First, level numbers are numbers assigned from the upper level to the lower level of the hierarchical database, such as 1, 2, 3, and so on. In the example in Figure 3, record type A10 has level number 1, record type B20,
Record type D40 and record type E50 have level number 2, and record type C30 has level number 3. Furthermore, a record code is a number attached to a record type in the order of record access, and the access order in a hierarchical database follows the following rules. Search from the upper level to the lower level. If the level is the same, search from the left record to the right record. If there are duplicate records at the lowest level, search all the records sequentially. 3rd In the database shown in the figure, the record code is 1 for record type A10, 2 for record type B20, and 2 for record type B20.
C30 is 3, D40 is 4, and E50 is 5. Using the level numbers and record codes described above, records are associated with each other in the database. The above level number and record code are obtained from the record type information table 100 shown in FIG. Using the acquired value as a parameter, the record correspondence is determined from the record correspondence table 200 shown in FIG. The record type information table 100 is a table composed of information for each record type created from the definition information of the database, and is created at the time of program execution, and exists on the memory 600 at the time of execution. In addition, the record correspondence table 20
0 is a table showing the correspondence of records with changes in level numbers and record codes,
It exists on the memory 600 during execution. FIG. 1 shows an overview of the processing flow of this embodiment.
The operation of this embodiment will be described below based on this flowchart. Now, consider a case where two databases as shown in FIGS. 5 and 6 are compared. 5 and 6 are databases existing on disk. The database 300 in FIG. 5 is a reference database, and the database 400 in FIG. 6 is a comparison database. The comparison of the databases is performed by comparing the sequential data set 310 on the reference side and the sequential data set 410 on the comparison side shown in FIG. Here, the forward data set 310 on the reference side is
This is a sequential data set in which the reference database 300 is unloaded onto tape in the order in which the records are accessed.The sequential data set 410 on the comparison side is a sequential data set in which the database 400 on the comparison side is unloaded onto the tape in the order in which the records are accessed. . First, from the sequential data set 310 on the reference side, a record of record type A10 is buffered (1) 32.
Read to 0. Similarly, the sequential database 4 on the comparison side
10, records of record type A10 are read into buffer (2) 420 (steps 510, 52
0). The record type of the read two records A160 is A10, and the level number,
Both record codes are required to be "1" (step 530). At this time, from the record correspondence table 200 mentioned above, 2 records A1
60 is found to be logically consistent (step 540). Two logically matched records are
Next, a physical comparison (data content comparison) is performed using the record correspondence table 200 described above (step 550). When the comparison result is a match,
2 records count as a match. After the comparison is completed, read the next record (step 58).
0). Thereafter, the same process is repeated until the end. FIG. 7 shows the correspondence of records when the two databases shown in FIGS. 5 and 6 are compared. In FIG. 7, records A160 and B16 of the reference database 300 are shown.
1, B263, C264, C365, D166, E16
7 are records of the comparison database 400, A160, B161, B263, and C16, respectively.
2, corresponds to C264, D166, and E167. Next, details of the compare process will be explained. (1) Record C16 of the reference database 300
2 Records on the reference side in step 550 above
After the comparison of the data contents of record B161 and comparison side record B161 is completed, in step 580, the reference side record C162 and comparison side record B263 are read into buffer (1) 320 and buffer (2) 420, respectively. . The level number and record code of the two records read are in the record type information table 100.
, record C162 is [3,3], record B2
63 is calculated as [2,2] (step 53
0). Furthermore, in step 540, the comparison result of the level number and record code [record C16
2 level number: 3>2: level number of record B263 and record code of record C162: 3>2: record code of record B263] and the record correspondence table 200,
The record corresponding to record C162 in the reference database 300 is in the comparison database 40.
It can be seen that it does not exist at 0. At this time, since the two records are logically inconsistent, an error message indicating that the access order of record C162 is different is output (step 581). In this case, the data content comparison process is skipped, the next record B263 is read from the reference side order database 310 (step 570), and the process is continued. (2) Record C26 of the reference database 300
4 Reference side record in step 550 above
After the data contents of B263 and comparison record B263 are compared, in step 580, reference record C264 and comparison record C162 are read into buffer (1) 320 and buffer (2) 420, respectively. . The level number and record code of the two records read are in the record type information table 100.
, record C264 is [3,3], record C1
62 is calculated as [3,3] (step 53
0). Here, in step 540, the comparison result between the level number and the record code is 3 for both records, and it is required from the record correspondence table 200 that the record C264 and the record C162 logically match. For the two logically matched records, a physical comparison is next performed (step 550). If the comparison result is a match, the two records are counted as a match,
If there is a mismatch, record C264 and record C16
2 outputs an error message indicating that the data contents do not match (step 582). In this case, after the comparison is completed, the next record C365 is transferred from the reference side sequential data set 310, and the next record C264 is transferred from the comparison side sequential data set 410.
is read (step 580) and processing continues. (3) Record C36 of comparison database 400
5 Record on the reference side in step 550 above
After the comparison of the data contents of C365 and comparison record C264 is completed, in step 580, the reference record D165 and comparison record C365 are read into buffer (1) 320 and buffer (2) 420, respectively. . The level number and record code of the two records read are in the record type information table 100.
From, record D166 is [2,4], record C3
65 is calculated as [3,3] (step 53
0). Furthermore, in step 540, the comparison result of the level number and record code [record D16
From the level number of 6: 2<3: level number of record C365 and the record code of record D166: 4>3: record code of record C365] and the record correspondence table 200,
The record corresponding to record C365 in the comparison database 400 is in the reference database 30.
It can be seen that it does not exist at 0. At this time, since the two records are logically inconsistent, the record C365 on the comparison side outputs an error message indicating that the access order of the records is different (step 5).
83). In this case, the data content comparison process is skipped, the next record D166 is read from the comparison data set 410 (step 560), and the process is continued. (4) Record D26 of comparison database 400
8 In this case, the record is created using the same process as (1) and (2).
D268 correspondence can be determined. Reference side record in step 550 above
After the data contents of D166 and comparison record D166 are compared, in step 580, reference record E167 and comparison record D268 are read into buffer (1) 320 and buffer (2) 420, respectively. . The level number and record code of the two records read are in the record type information table 100.
, record E167 is [2,5], record D2
68 is calculated as [2,4] (step 53
0). Furthermore, in step 540, the level number and record code comparison result [record E16
7 level number: 2=2: level number of record D268 and record code of record E167: 5>4: record code of record D268] and the record correspondence table 200,
The record corresponding to record D268 in the comparison database 400 is in the reference database 30.
It can be seen that it does not exist at 0. At this time, since the two records are logically inconsistent, the record D268 on the comparison side outputs an error message indicating that the access order of the records is different (step 5).
83). In this case, as in (3), the data content comparison process is skipped and the next record E167 is read from the sequential data set 410 on the comparison side (step 56).
0), processing continues. As described above, according to the present embodiment, in comparing databases, it is possible to compare not only the match/mismatch of data contents but also the logical relationships (order of access of records) in the databases. In addition, when comparing databases, the level number and record code are used as parameters, and the record type information table 100 is
By using the record correspondence table 200, it is possible to simplify the correspondence of records, which has a complicated processing structure. Furthermore, according to the method of this embodiment, since the database is unloaded onto tape and compared, database comparison can be performed independently from the database system, and the database system in operation is not affected at all. do not have. This has a tremendous effect on system operation. Note that the various tables and the like used in this embodiment are shown as an example, and it goes without saying that the present invention should not be limited to these systems. [Effects of the Invention] As described above, according to the present invention, in a database comparison method for comparing hierarchical databases, a comparison result of level information and record type information of each data in the hierarchical database is used. As a result, it is possible to compare not only the data contents but also the data access order, thereby realizing a database comparison method that is extremely effective when comparing hierarchical databases.

[Brief explanation of drawings]

FIG. 1 is a flowchart showing an overview of the processing flow of an embodiment of the present invention, FIG. 2 is a diagram showing an overview of the embodiment, FIG. 3 is a diagram showing an example of the structure of a database, and FIG. 4 is a simplified diagram of the record type information table, Figures 5 and 6 are structural diagrams of the database used in the example, Figure 7 is a diagram showing the comparison result of the record access order of the database of the example, and Figure 8 is the record type information table. It is a simplified diagram of a correspondence table. 100: Record type information table. 20
0: Record correspondence table, 300: Reference side database, 310: Reference side sequential data set, 40
0: Comparison side database, 410: Comparison side sequential data set, 510 to 590: Processing steps.

Claims (1)

[Claims] 1. In a hierarchical database hierarchically configured with a plurality of records, each record includes level information indicating the hierarchy in which the record type to which the record belongs exists, and access information indicating the access order of the record types. When comparing two hierarchical databases, the level information and access information corresponding to the records forming one hierarchical database, and the level information corresponding to the records forming the other hierarchical database. A comparison method for hierarchical databases that compares and access information. 2. The hierarchical database comparison method according to claim 1, wherein data contents are compared for two records whose comparison results match. 3 If the results of the comparison do not match, if the level information is not equal, select a record that is next in access order to the record for which the comparison was performed from the hierarchical database that has records associated with level information indicating a lower level. The level information and access information corresponding to the record are compared with the compared record of the hierarchical database having records associated with level information indicating a higher level, and the level information is If they are equal, a record next to the record in which the access order was compared is obtained from a hierarchical database having records associated with access information earlier in the access order, and the level information and access information corresponding to the record are obtained. In the hierarchical database according to claim 1, the information is compared with the record in which the comparison was performed in a hierarchical database having records associated with later access information in the order of access. Compare method.