JPH09146804A - Data matching device - Google Patents

Abstract

(57) [Summary] [Purpose] Data is exchanged between a plurality of RDBMS while maintaining the consistency of the record data of the DB table. [Structure] This data matching device has a plurality of RDBMS in advance.
The SQL statement conversion definition file 23 in which the attributes 11 and 21 and the conversion rules of the SQL statement for each are defined, and R
RD of the data of DBMS11 side by file transfer etc.
Transaction monitoring function unit 1 to send to the BMS 21 side
4 and the data from the RDBMS11 side are received, and based on the conversion rule of the SQL statement conversion definition file 23, the SQL statement of the received data is converted into the SQL statement corresponding to RDBMS21, and the SQL statement and the attribute are corresponded. And a SQL statement loading function unit 22 for returning a normal termination message to the transaction monitoring function unit 14 on the RDBMS 11 side when the loading of the SQL statement is completed normally. .

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data matching device for matching data between different relational database management systems (RDBMS).

[0002]

2. Description of the Related Art Conventionally, since different RDBMSs have different internal structures from each other, it is difficult to exchange data, and improvement is desired.

Conventionally, when a plurality of relational database management systems (RDBMS) exchange data between databases, one RDB
It is possible to record data of one database in the other if the table structure of each database is the same when the transaction from the MS is made to the other and only in this case, the contents of the table of the other RDBMS can be recorded. Will be updated.

Even if the RDBMSs have the same table structure, the RDBMSs may have different attributes.

In this case, the consistency of the record data in both tables cannot be maintained, and data cannot be exchanged.

[0006]

As described above, when data is exchanged between a plurality of conventional relational database management systems, if the respective table structures are the same but the respective attributes are different, the two There was a problem that the data could not be exchanged because the consistency of the record data of the table could not be maintained.

The present invention has been made to solve the above problems, and an object thereof is to provide a data matching device capable of exchanging data between heterogeneous relational database management systems.

[0008]

In order to achieve the above-mentioned object, a data matching device according to claim 1 is a data matching device which handles data communication between a plurality of relational database management systems. An attribute of the management system and a conversion rule defining unit that predefines a conversion rule of communication data according to the attribute, a transmitting unit that transmits communication data from one relational database management system side to the other, and a transmitting unit from the transmitting unit. Receiving means for receiving communication data, converting means for converting the communication data received by the receiving means into communication data corresponding to the attribute of the transmission source based on the conversion rule of the conversion rule defining means, and converting by the converting means A data storage unit that stores the communication data that has been transmitted and its attributes in association with each other; When the communication data storage means data was successfully saved, and a returning means for returning information indicating success to the transmitting means.

According to a second aspect of the present invention, there is provided a data matching device which handles data communication between a plurality of relational database management systems, wherein attributes of the plurality of relational database management systems and conversion rules of SQL statements for the respective relations are set. A predefined SQL statement conversion definition file, a transaction monitoring function unit that sends data from one relational database management system side to the other, and data from the transaction monitoring function unit, and converts the SQL statement conversion definition file Based on the rules, the SQL statement of the received data is converted into the SQL statement corresponding to the attribute of the sender, and the SQL statement and the attribute are matched and loaded into the own database.
An SQL statement loading function unit that returns a normal termination message to the transaction monitoring function unit when the SQL statement loading is completed normally.

Note that it is premised that the internal table structures of the plurality of relational database management systems that are trying to achieve consistency with each other are the same.

[0011]

According to the first aspect of the invention, when the receiving means receives the communication data from the transmitting means, the communication data is converted into communication data corresponding to the attribute of the transmission source based on the conversion rule of the conversion rule defining means. Then, the communication data and the attribute are associated with each other and stored in the data storage means. Then, when the communication data is normally stored, the information indicating the normal end is returned to the transmitting means.

Therefore, the consistency of the record data of both tables can be maintained between different relational database management systems, and data can be exchanged between different types of relational database management systems. Further, in the invention according to claim 2, when a transaction occurs from the transaction monitoring function unit of one relational database management system to the other and data is received by the other, SQ
The L statement loading function unit converts the SQL statement of the received data into the SQL statement corresponding to the attribute of the sender based on the conversion rules of the SQL statement conversion definition file, and associates the SQL statement with the attribute and This SQ
When loading of the L statement is completed normally, a normal termination message is returned to the transaction monitoring function part.

Therefore, the consistency of the record data of the tables of both relational database management systems can be maintained, and data can be exchanged between different types of relational database management systems.

[0014]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a diagram showing a configuration of a data matching apparatus according to an embodiment of the present invention, and FIG. 2 is a diagram showing a data structure transferred between computers.

In the figure, reference numerals 1 and 2 denote computers of different types, each having a shared memory (not shown). The computer 1 has a relational database management system (hereinafter referred to as RDBMS) 11, a DB update application group 12, a transaction log function unit 13, a transaction monitoring function unit 14, an external file 15 for synchronization processing, and the like. RDBMS11
Is provided with a user definition table 16 and a transaction management table 17.

As shown in FIG. 2, the transaction management table 17 is composed of columns such as registration time 30, SQLLOG 31, and transfer flag 32.

Here, the registration time 30 is a column for recording the time when a record is INSERTED in the transaction management table 1, and the system time at the time of INSERT is a decimal point of seconds so as to be a unique key in this table. Less than
Records up to 6 digits. SQLLOG31 is the SQL statement itself
This is a column for INSERT, and SQL statements of INSERT, UPDATE, and DELETE are recorded in the transaction that occurred in RDBMS. The transfer flag 32 is a flag column indicating whether or not the record is reflected in the other RDBMS,
The status of "transferred" or either is recorded.

That is, the transaction management table 17 is INSE in which the record in the table is updated in the transaction generated in the RDBMS 11.
This is a table for managing the SQL statements of RT, UPDATE, and DELETE processing as logs on the table.

The transaction log function unit 13 uses INSERT, UPDATE, and DELE among transactions for each user-defined table 16 in one RDBMS 11.
Regarding TE, the SQL statement itself is inserted into the transaction management table 17. At this time, the system time is recorded in the registration time column 30 and the "untransferred" data is set in the transfer flag column 32 as a default value. The transaction monitoring function unit 14 selects the column 31 of SQLLOG and records it in the external file 15 in the transaction management table 17 under the condition that the transfer flag is “not transferred” and the registration time is before the current time. . The other RDBMS21
UPDATE the transfer flag to "transferred" when the data has been set normally.

One of the computers 2 is the above RDBMS.
The RDBMS 21, the SQL statement loading function unit 22, the SQL statement conversion definition file 23, and the like, which are different in type from 11, are included. A user definition table 24 is provided in the RDBMS 21. SQL statement loading function unit 22
Is the contents of the external file 15 created by the transaction monitoring function unit 14 (SQ of INSERT, UPDATE, DELETE
The SQL statement is issued to the corresponding table 23 in the other RDBMS 21 based on the (L statement). Also this SQ
The L statement loading function unit 22 returns a normal termination message to the transaction monitoring function unit 14 of the issuer when the SQL statement is normally issued and the record is committed. In the SQL statement conversion definition file 23, the attributes of the plurality of RDBMSs 11, 21, ... And the conversion rules of the SQL statement for each are defined in advance.

Next, the operation of the data matching device will be described with reference to FIG.

In this data coordinating apparatus, first, when the data updating process from the DB updating application group 12 such as one computer 1 to the RDBMS 21 of the other computer 2 is performed (step 101 in FIG. 3), one R
In the DBMS 11, the transaction log function unit 13, which is a log device of, issues SQL statements such as INSERT, UPDATE, and DELETE of records to each internal table (user-defined table 16, transaction management table 17, etc.) ( Step 102).

In this case, the SQL statement is directly inserted into the transaction management table 17. At this time, the registration time and transfer flag data are also set.

Next, the transaction monitoring function unit 14
In the transaction management table 17,
The search is always performed under the condition that the registration time is before the current time and the flag data is “not transferred”, and the hit record is written to the external file 15 for data matching (step
103).

Then, the external file 15 is transferred to the SQL statement loading function unit 22.

Next, the SQL statement loading function unit 22
The external file 15 is received by a shared memory (not shown) by file transfer or the like, and the conversion rule is read from the SQL statement conversion definition file 23 (step 104).

From the shared memory, the external file 15
The SQL statement is read, the SQL statement is converted according to the conversion rule of the first RDBMS in which the attribute is defined, and a new SQL statement is created (step 105).

The SQL statement loading function unit 22
Is the created SQL statement and the SQL of the sender RDBMS11
When the sentences match, the attribute and the SQL sentence are associated with each other and loaded into the RDBMS 21.

When the SQL statement is loaded normally, the transaction monitoring function unit 1 of the computer 1
A normal termination message is returned to 4.

The transaction monitoring function unit 14 of the computer 1, which has received the normal termination message, updates the status of the transfer flag of the corresponding record in the transaction management table 17 to "transferred".

Subsequently, the above process is cyclically repeated by the FOR loop from step 106 until the defined number of processes are completed (steps 106 to 109).
). That is, the RD running on the computer 1
The data of the user definition table 16 of the BMS 11 is downloaded to the RDBMS 21 running on the computer 2 at regular intervals, whereby the mainframe database is switched from the centralized management type to the distributed management type, and the load balancing of the computer 1 is performed. We are trying to improve the response from the terminal.

For example, the above operation will be described with reference to the block diagram of FIG. 1. When the DB update application group 12 on the computer 1 updates the RDBMS 11 to the user-defined table 16, the SQL statement is used as the transaction management table. Inserted in 17 ().

Then, the transaction management table 1
The updated SQL is searched from 7 and the result is recorded in the external file 15 for the synchronization processing (,).

This external file 15 is stored in the computer 1
From the computer to the computer 2.

On the computer 2 side, the external file 15
Received in shared memory (), its external file 1
5 is an RDBMS on the server side, that is, the computer 2 side
After being converted to 21 SQL statement format, RDBM
It is loaded into S21 (,).

As described above, according to the data matching apparatus of the present embodiment, since the SQL statement conversion definition file 23 defining the conversion rules of the SQL statement for a plurality of RDBMS attributes is provided, even between different RDBMSs 11 and 21. Data can be exchanged while maintaining the consistency of records in the internal table.

R on a different computer (machine)
Even when the DBMS 11 and 21 exist, the synchronous processing can be performed by transferring the external file 15 between the machines by using the shared memory.

[0039]

As described above, according to the invention described in claim 1, when the communication data transmitted from the transmitting means is normally stored in the other party, the information indicating the normal end is returned to the transmitting means. Therefore, the consistency of the record data of both tables can be maintained between different relational database management systems.

According to the second aspect of the present invention, when data is transmitted by the transaction monitoring function unit, a normal termination message is always issued when the data is normally loaded into the other party's database. The record data in both tables will be kept consistent.

As a result of the above, data can be exchanged between different types of relational database management systems while maintaining the consistency of record data.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a data matching device according to an embodiment of the present invention.

FIG. 2 is a diagram showing a data structure transferred between different RDBMSs.

FIG. 3 is a flowchart showing the operation of this data matching device.

[Explanation of symbols]

1, 2 ... Computer, 11, 21 ... Relational database management system (RDBMS), 12 ... DB update application group, 13 ... Transaction log function unit, 14 ... Transaction monitoring function unit, 15 ... External file, 16, 24 ... User definition Table, 17 ... Transaction management table, 22 ... SQL statement loading function section, 23 ... SQL statement conversion definition file.

Claims (2)

[Claims] 1. A data matching device that handles data communication between a plurality of relational database management systems, wherein a conversion rule definition that defines in advance an attribute of the plurality of relational database management systems and a conversion rule of communication data according to the attribute. Means, a transmitting means for transmitting communication data from one relational database management system side to the other, a receiving means for receiving the communication data from the transmitting means, and a conversion rule defining means for the communication data received by the receiving means. A conversion unit that converts the communication data corresponding to the attribute of the transmission source based on the conversion rule of 1., a data storage unit that stores the communication data converted by the conversion unit and the attribute in association with each other, and the data storage unit. When the communication data is normally stored in the A data matching apparatus comprising: a reply unit that returns information indicating the end. 2. A data matching device that handles data communication between a plurality of relational database management systems, comprising: an attribute of the plurality of relational database management systems; and an SQL statement conversion definition file that defines in advance the SQL statement conversion rules for each. , A transaction monitoring function unit that transmits data from one relational database management system side to the other, and receives data from the transaction monitoring function unit, and based on the conversion rules of the SQL statement conversion definition file, The SQL statement is converted into the SQL statement corresponding to the attribute of the sender, the SQL statement is associated with the attribute and loaded into its own database, and when the loading of this SQL statement is completed normally, the transaction monitoring function Reply message of normal end to department Data matching apparatus being characterized in that comprising a SQL statement loading function unit that.