JP2007293831A - Database synchronous update processing method, slab applying method and coil applying method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a database synchronous update processing method capable of synchronizing and updating all databases about distributed and arranged databases even when the databases are hierarchical databases. <P>SOLUTION: The database synchronous update processing method comprises the steps for: transmitting update processing information from a main site 2 to a secondary site 3; deciding whether or not update processing of a database 11 of the secondary site 3 is executable; registering the update of the secondary site 3 and transmitting such registered update information to the main site 2; registering the update of a database 6 of the main site 2; and determining the registered update of the database 6 of the main site 2 and the database 11 of the secondary site 3. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a database synchronous update processing method, a slab allocation method, and a coil allocation method that can update a database arranged in a distributed manner in synchronization.

Generally, in a steel company, slab orders are collectively managed by the order management department, and the order management department instructs each production department such as a steel mill to produce slabs according to the contents of each order. .
On the other hand, because slabs are manufactured in each lot in each manufacturing department, the slab weight required in each order does not match the slab weight manufactured in the minimum lot in the manufacturing department. Such surplus slabs are managed as slab inventory in each manufacturing department.

In each manufacturing department, the slab inventory information is classified based on components, dimensions, weights, etc. in order to prioritize and allocate the slab inventory to the slab order instructed by the order management department. Are managed by a hierarchical database.
Here, in recent years, in order to make it possible to immediately determine whether or not slab inventory is appropriated in each manufacturing department (subordinate site) for a new order in an order management department (primary site), a steel company has information on slab inventory in each manufacturing department. In addition, it is desired that the order management department builds a system that collectively manages a database.

  In a system that collectively manages the slab inventory information at the conventional slave site using the database at the main site, the site including the databases to be updated is provided with the same determination means for determining whether or not the database can be updated. Each site is configured to determine whether or not the database can be updated. For example, when slab inventory is allocated to an order instructing manufacture, program logic for determining whether or not slab inventory can be allocated to an order instructing manufacture to each of the manufacturing department and order management department (Determination means) is arranged. Here, the program logic is a check logic that compares manufacturing specifications such as components, dimensions, and weights related to orders with manufacturing results related to inventory, and check logic related to the progress of products manufactured in the manufacturing department and intermediate products. This refers to the check logic of the allocation relationship between orders and inventory.

  However, the conventional method has a problem that the program development load increases because the determination means having the same contents for determining whether or not each database can be updated is arranged for each site. In addition, this method requires maintenance at both the primary site and the secondary site when the program logic needs to be modified, which increases development costs and causes deterioration in the quality of the program logic. There is a problem.

In addition, the main site usually does not have all the information held by the slave site. Therefore, in the conventional method, there are cases where the database is updated at the primary site and the database is updated at the primary site, but the database is not updated at the secondary site and the database is not updated. There is a problem that matching may occur.
As a means of avoiding these problems, a job is linked between the master site and the slave site, and necessary information such as order information and inventory information is transmitted from the master site to the slave site and held in the slave site. Thus, a method has been adopted in which whether or not the database can be updated is determined, the database on the slave site is updated, the update result is transmitted to the main site, and the database on the main site is also updated.

However, in such a method of asynchronously updating between the primary and secondary sites, for example, the process start timing between the reflection process of the inventory information update result generated at the secondary site to the primary site and the linkage processing started from the primary site is If the database update timing is reversed or the update process at one site ends abnormally, the information stored in the database may be inconsistent between the primary and secondary sites. There was a problem.
Therefore, in recent years, a master-slave relationship synchronization method in a distributed database system shown in FIG. 7, for example, is known as an invention of a system that updates a database at a slave site and a database at a master site in synchronization (see Patent Document 1). .

  As shown in FIG. 7, the master-slave relationship synchronization method 140 in the distributed database system includes a main table (dummy) 143 in the relational database (slave) 142 of the slave server 141 and a main table (dummy) 143 and a slave table (copy). ) Define a master-slave relationship with 144. Then, the log monitoring unit 145 determines whether or not the update log file 149 is updated with update log information output when the main table (master) 148 in the relational database (master) 147 of the master server 146 is updated. Monitor regularly. Further, the update reflection processing unit 150, when the update of the update log file 149 is detected by the log monitoring unit 145, based on the latest update log information of the update log file 149, the relational database (slave) 142 of the slave server 141. The contents of the update are reflected in the main table (dummy) 143.

Then, according to the master-slave relationship synchronization method 140 in the distributed database system, the master server 146 only updates the master table (master) 148, while maintaining the master-slave relationship between the contents and the table in the distributed slave servers 141. Update processing can be performed, and as a result, it is possible to eliminate processing for updating data having the same content for each server.
Japanese Patent Laid-Open No. 13-34518

However, since the master-slave relationship synchronization method 140 in the distributed database system shown in FIG. 7 is based on the premise that the distributed database is a relational database, the distributed database is a hierarchical database. If this is the case, there is a problem that it cannot be applied.
The present invention has been made to solve the above-described problems of the prior art, and its purpose is to eliminate the need for a determination means at the main site, reduce the program development load, and correct the program logic. It is an object of the present invention to provide a database synchronous update processing method capable of reducing development cost and suppressing deterioration of program logic quality when it becomes necessary.

Another object of the present invention is to prevent rework or information inconsistency from occurring by updating all databases synchronously with respect to distributed databases. Is to provide a simple database synchronous update processing method.
Furthermore, another object of the present invention is to provide a database synchronous update processing method capable of synchronously updating all databases even when such databases are hierarchical databases. Is to provide.

In the database synchronous update processing method according to claim 1 of the present invention, in a distributed database environment comprising a master site having a database and a slave site having a database for storing information common to the database of the master site, A database synchronous update processing method for synchronously updating the database of the slave site and the database of the primary site based on the update process started from the primary site,
Transmitting update processing information from the primary site to the slave site;
Determining whether or not the update processing of the database at the slave site is possible from the received update processing information and the information stored in the database at the slave site;
A step of registering the update of the slave site when the update process of the database of the slave site is possible, and transmitting the registered update information to the master site;
Registering an update of the main site database based on the received update information;
And a step of confirming registered updates of the database of the main site and the database of the subordinate site based on the received update information and the update processing information.

In the slab allocation method according to claim 2 of the present invention, a slave site having a database storing at least one of slab inventory information and slab order information, and a database storing information common to the database of the slave site In a distributed database environment comprising a primary site having a primary site, the secondary site database and the primary site database are synchronized based on at least one of slab inventory information and slab order information input or derived at the primary site. Slab appropriation method to take and update,
Transmitting at least one of the slab inventory information and the slab order information input or derived at the main site to the slave site;
From at least one of the received slab inventory information and the slab order information, and at least one of the slab inventory information and the slab order information stored in the database at the slave site, the slab inventory is stored in the slab order. Determining whether appropriation is possible;
When the slab inventory can be allocated to the slab order, the update of the database of the slave site is registered, and the registered update information is transmitted to the main site;
Registering an update of the main site database based on the received update information;
Determining a registered update of the primary site database and the secondary site database based on the received update information and at least one of the input or derived slab inventory information and slab order information It is characterized by providing.

Furthermore, the coil allocation method according to claim 3 of the present invention stores a slave site having a database storing at least one of coil inventory information and coil order information, and information common to the database of the slave site. In a distributed database environment comprising a primary site having a database, the database of the slave site and the primary site are based on at least one of coil inventory information and coil order information input or derived at the primary site. A coil allocation method for synchronously updating a database,
The step of transmitting at least one of the coil inventory information and the coil order information input or derived at the main site to the slave site;
The received order information from at least one of the received coil inventory information and the coil order information and at least one of the coil inventory information and coil order information stored in the database of the slave site. Determining whether or not the coil stock can be allocated to the order;
When the coil stock is available for the order, the update of the database of the slave site is registered, and the registered update information is transmitted to the main site;
Registering an update of the main site database based on the received update information;
Based on the received update information and at least one of the coil inventory information and the coil order information input or derived, the registered update of the primary site database and the secondary site database is confirmed. And a process.

  According to the database synchronous update processing method according to claim 1 of the present application, it is not necessary to provide a determination means at the main site, and the development cost is reduced when the program development load is reduced and the program logic needs to be corrected. Can be reduced, and deterioration of the quality of the program logic can be suppressed. In addition, according to the database synchronous update processing method according to claim 1 of the present invention, by renewing all databases synchronously with respect to the databases arranged in a distributed manner, rework or information inconsistency occurs. This can be prevented. Furthermore, according to the database synchronous update processing method according to claim 1 of the present application, even when the database is a hierarchical database, it is possible to update all the databases in synchronization with each other even if the database is a hierarchical database. It becomes possible.

Moreover, according to the slab allocation method according to claim 2 of the present application, in addition to the effect of the database synchronous update processing method according to claim 1, it is possible to efficiently allocate slab inventory to the slab order.
Furthermore, according to the coil allocation method according to claim 3 of the present application, in addition to the effect of the database synchronous update processing method according to claim 1, it is possible to efficiently allocate the coil stock to the coil order.

Hereinafter, a database synchronous update processing method according to a first embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic configuration diagram of a database synchronous update processing system according to the first embodiment of the present invention. FIG. 2 is a diagram showing a flow of processing in the database synchronous update processing system shown in FIG.
As shown in FIG. 1, the database synchronous update processing system 1 connects a main site 2, a plurality of slave sites 3 that are arranged apart from the master site 2, and the master site 2 and the slave sites 3. And a communication line 4. The database synchronous update processing system 1 synchronizes and updates a database 11 (described later) of the slave site 3 and a database 6 (described later) of the primary site 2 based on an update process activated from the primary site 2. .
The main site 2 includes a database 6, an input terminal 7, a transaction control unit 9, and a database update unit 10.
The database 6 is composed of a relational database, and stores information common to information stored in the database 11 provided in each slave site 3.

  Update processing information is input to the input terminal 7. Further, the input terminal 7 includes calculation means (not shown), and derives (calculates) additional update processing information necessary for subsequent processing by the calculation means. Hereinafter, update process information input to the input terminal 7 or update process information derived (calculated) by the input terminal 7 is simply referred to as update process information. Here, the update processing information is information for specifying a processing target (for example, an order number for specifying an order, an actual product number for specifying a product or an actual product, etc.), and information for specifying a processing content (for example, steel) In slab appropriation, it refers to information that specifies the execution processing contents such as appropriation and appropriation change) and related information held only in the main site 2. The related information is information obtained from the information stored in the database 6 of the main site 2, information stored in the database 6 of the main site 2, etc. by logic, calculation formulas, search processing, etc. This is input information for determination processing (for example, manufacturing specifications as order items, manufacturing results as actual items, etc.). In addition, an update result for the update processing information is displayed on the input terminal 7.

  The transaction control means 9 receives the update process information from the input terminal 7 and confirms the contents related to the update process information. Then, the transaction control means 9 verifies the slave site 3 that performs the update processing based on the contents of the update processing information and the information stored in the database 6, and selects the slave site 3 that performs the transaction. Further, the transaction control means 9 transmits update processing information to the selected slave site 3. Further, the transaction control means 9 registers the update contents of the database 6 based on the update result information returned from the slave site 3 (for example, the allocation result of the slab inventory in the steel slab allocation process) and the update information, and the database 6 and Determine (commit) or discard (rollback) update contents registered in the database 11 of the slave site 3.

The database update unit 10 confirms the registered update of the database 6 when the transaction control unit 9 determines to commit the database 6.
Each slave site 3 includes a database 11, a transaction control unit 12, a determination unit 13, and a database update unit 14.
The database 11 is configured by a hierarchical database.

  The transaction control unit 12 inputs the update processing information received from the transaction control unit 9 of the main site 2 to the determination unit 13 and sends the update result information output from the determination unit 13 to the transaction control unit 9 of the main site 2. Send back. The transaction control unit 12 registers the update of the database 11 and updates the registered update information when the update result information output from the determination unit 13 determines that the update is possible. It returns to the transaction control means 9 of the site 2. Further, the transaction control unit 12 outputs a commit instruction for the update contents registered in the database 11 to the database update unit 14 based on the commit or rollback instruction transmitted from the transaction control unit 9 of the main site 2. Alternatively, the update contents registered in the database 11 are rolled back.

The determination unit 13 determines whether or not the update process can be performed based on the update process information input from the transaction control unit 12 and the information stored in the database 11. In this case, the determination unit 13 stores check logic, and it is determined whether or not the update process can be performed based on the check logic.
The database update unit 14 confirms the registered update of the database 11 when the transaction control unit 12 instructs to commit the database 11.

Next, the flow of update processing in the database synchronous update processing system 1 will be described.
First, as shown in FIG. 2, update processing information is input or derived (calculated) at the input terminal 7 of the main site 2 (step S101). Then, the update processing information input or derived (calculated) at the input terminal 7 is input to the transaction control means 9 of the main site 2.
The transaction control means 9 of the master site 2 that has received the update processing information selects the slave site 3 that performs the transaction (step S102), and establishes a communication path with the slave site 3 (step S103).

After establishing the communication path between the primary site 2 and the slave site 3, the transaction control means 9 of the primary site 2 transmits update processing information to the transaction control means 12 of the slave site 3 to start a transaction. (Step S104). Here, the transaction control means 9 of the main site 2 stores the update processing information transmitted to the transaction control means 12 of the slave site 3 in a file.
Then, the transaction control means 12 of the slave site 2 that has received the update process information from the main site 2 inputs the update process information to the determination means 13.

The determination unit 13 to which the update process information is input determines whether or not the update process can be performed based on the update process information and the information stored in the database 11 of the slave site 3 (step S105). The update result information is output to the transaction control means 12 of the slave site 3.
The transaction control unit 12 of the slave site 3 to which the update result information is input from the determination unit 13 registers the update contents of the database 11 of the slave site 3 when it is determined that the update result information can be updated. Is performed (step S106). Then, the transaction control means 12 of the slave site 3 returns the registered information as update information to the transaction control means 9 of the main site 2 together with the update result information (step S107).

On the other hand, if it is determined that the update is not possible in the update result information input from the determination unit 13, the transaction control unit 12 of the slave site 3 uses only the update result information as the transaction control unit of the main site 2. 9 is returned (step S108). The update result information is displayed on the input terminal 7.
When it is determined in the update result information that the update is possible, the transaction control means 9 of the main site 2 that has received the update information and the update result information from the transaction control means 12 of the slave site 3 updates the update information. Based on this, the update contents of the database 6 of the main site 2 are registered (step S109).

  The transaction control means 9 of the main site 2 that has registered the update contents of the database 6 of the main site 2 determines whether or not both pieces of information are consistent based on the update information and the update processing information stored in the file. Is determined (step S110), the commit is determined if they are consistent (step S111), and the rollback is determined if they are not consistent (step S112).

Then, the transaction control means 9 of the main site 2 that has decided to commit transmits a commit instruction to the database update means 10 of the main site 2 and the transaction control means 12 of the subordinate site 3, and the database 6 and the subordinate of the main site 2. The registered update contents of the database 11 of the site 3 are confirmed (step S113).
On the other hand, the transaction control means 9 of the primary site 2 that has decided to roll back discards the registered update contents of the database 6 of the primary site 2 and issues a rollback instruction to the transaction control means 12 of the slave site 3. Then, the update contents registered in the database 11 of the slave site 3 are discarded (step S114).

When the registered update contents of the database 6 of the main site 2 and the database 11 of the slave site 3 are confirmed, the update information and the update result information are displayed on the input terminal 7 and the update process is completed. .
On the other hand, when the registered update contents of the database 6 of the main site 2 and the database 11 of the slave site 3 are discarded, a message to that effect is displayed on the input terminal 7.

  As described above, according to the database synchronous update processing system 1, it is not necessary to provide the determination means 13 in the main site 2, and the program development load is reduced and the development is performed when the program logic needs to be corrected. Costs can be reduced and deterioration of program logic quality can be suppressed. Moreover, according to the database synchronous update processing system 1, it is possible to prevent rework or information inconsistency from occurring by updating all the databases synchronously with respect to the databases arranged in a distributed manner. Is possible. Furthermore, according to the database synchronous update processing system 1, it is possible to update all databases synchronously even when the databases arranged in a distributed manner are hierarchical databases.

Next, a database synchronous update processing method according to the second embodiment of the present invention will be described with reference to the drawings.
In the present embodiment, a case where the database synchronous update processing method according to the present invention is applied to a slab allocation system will be described as an example.
FIG. 3 is a schematic configuration diagram of a slab allocation system according to the second embodiment of the present invention. FIG. 4 is a diagram showing a flow of processing in the slab allocation system shown in FIG.
As shown in FIG. 3, the slab allocation system 21 includes a main site 22 arranged in the order management department, a plurality of subsites 23 arranged in each steelworks separated from the order management department, and the main site 22. And a LAN line 24 for connecting the slave site 23 to the slave site 23. The slab allocation system 21 synchronizes and updates the server database 31 (described later) of the slave site 23 and the client database 26 (described later) of the primary site 22 based on update processing activated from the primary site 22. .

The main site 22 includes a client database 26, an input terminal 27, client transaction control means 29, and a database update means 30.
The client database 26 is composed of a relational database, and stores information common to the slab inventory information stored in the server database 31 provided in each slave site 23.
The input terminal 27 receives the slab order information received by the order management department and displays the allocation result of the slab inventory for the slab order information.

  The client transaction control means 29 receives the slab order information from the input terminal 27 and confirms the slab information such as the slab component and dimensions related to the slab order information. Then, the client transaction control means 29 verifies the slave site 23 having a slab inventory that can be allocated to the slab order information based on the slab information and the slab inventory information stored in the client database 26, and performs the transaction. 23 is selected. Further, the client transaction control unit 29 transmits slab order information to the selected slave site 23. Further, the client transaction control means 29 registers the update contents of the client database 26 and stores the update contents in the client database 26 and the server database 31 based on the slab allocation result information and the slab inventory update information (update information) returned from the slave site 23. Determine commit or rollback of registered updates.

The database update unit 30 confirms the registered update of the client database 26 when the client transaction control unit 29 determines to commit the client database 26.
Each slave site 23 includes a server database (database of the slave site 23) 31, server transaction control means 32, determination means 33, and database update means 34.
The server database 31 is composed of a hierarchical database and stores slab inventory information possessed by each steelworks. In this case, the slab inventory information stored in the server database 31 is stored in a grouped state based on slab information such as components and dimensions of each slab.

  The server transaction control unit 32 inputs the slab order information received from the client transaction control unit 29 to the determination unit 33 and returns the slab allocation result information output from the determination unit 33 to the client transaction control unit 29. In addition, the server transaction control unit 32 determines whether the slab inventory can be allocated to the slab order in the slab allocation result information output from the determination unit 33. 31 is registered, and the registered slab inventory update information is returned to the client transaction control means 29. Further, the server transaction control unit 32 outputs a commit instruction for the registered update contents of the server database 31 to the database update unit 34 based on the commit or rollback instruction transmitted from the client transaction control unit 29, or The registered update contents of the server database 31 are rolled back.

Based on the slab order information input from the server transaction control unit 32 and the slab inventory information stored in the server database 31, the determination unit 33 determines whether or not slab inventory can be allocated to the slab order. In this case, the determination unit 33 stores slab information check logic such as slab components and dimensions related to the slab order information, and determines whether or not slab inventory can be allocated to the slab order based on the check logic. Is called.
The database update unit 34 confirms the registered update of the server database 31 when the server transaction control unit 32 instructs to commit the server database 31.

Next, the flow of the slab allocation process in the slab allocation system 21 will be described.
First, as shown in FIG. 4, slab order information is input to the input terminal 27 of the main site 22 (step S201). The slab order information input to the input terminal 27 is input to the client transaction control means 29.
Upon receiving the slab order information, the client transaction control means 29 selects the slave site 23 that performs the transaction (step S202), and establishes a communication path with the slave site 23 (step S203).

  After establishing the communication path between the main site 22 and the slave site 23, the client transaction control means 29 transmits slab order information to the server transaction control means 32 of the slave site 23 to start a transaction (step S204). ). Here, the client transaction control means 29 stores the slab order information transmitted to the server transaction control means 32 in a file.

The server transaction control unit 32 that has received the slab order information from the main site 22 inputs the slab order information to the determination unit 33.
Based on the slab order information and the slab inventory information stored in the server database 31, the determination means 33 to which the slab order information has been input determines whether or not slab inventory can be allocated to the slab order (step S205). The slab allocation result information is output to the server transaction control means 32.

  The server transaction control unit 32 that has input the slab allocation result information from the determination unit 33 determines that the slab inventory can be allocated to the slab order in the slab allocation result information. The update contents of the server database 31 are registered for (step S206). Then, the registered information is returned as slab inventory update information to the client transaction control means 29 together with the slab allocation result information (step S207).

On the other hand, if it is determined in the slab allocation result information input from the determination unit 33 that the slab inventory cannot be allocated to the slab order, the server transaction control unit 32 uses only the slab allocation result information as the client. It returns to the transaction control means 29 (step S208). The slab allocation result information is displayed on the input terminal 27.
Then, when it is determined in the slab allocation result information that the slab inventory can be allocated to the slab order, the client transaction control unit 29 that has received the slab inventory update information and the allocation result information from the server transaction control unit 32 Based on the slab inventory update information, the update contents of the client database 26 are registered (step S209).

  The client transaction control means 29 that has registered the update contents of the client database 26 determines whether or not both pieces of information are consistent based on the inventory update information and the slab order information stored in the file (step S210), commit is determined if they are consistent (step S211), and rollback is determined if they are not consistent (step S212).

  Then, the client transaction control unit 29 that has determined the commit transmits a commit instruction to the database update unit 30 and the server transaction control unit 32, and confirms the update contents registered in the client database 26 and the server database 31 ( Step S213). On the other hand, the client transaction control unit 29 that has decided to roll back discards the update contents registered in the client database 26 and transmits a rollback instruction to the server transaction control unit 32 so that the server database 31 is registered. The updated contents are discarded (step S214).

When the registered update contents of the client database 26 and the server database 31 are confirmed, the slab inventory update information and the allocation result information are displayed on the input terminal 27, and the allocation of the slab inventory to the slab order is completed. .
On the other hand, when the registered update contents of the client database 26 and the server database 31 are discarded, a message to that effect is displayed on the input terminal 27.

  Thus, according to the slab allocation system 21, it is not necessary to provide the determination means 33 in the main site 22, reducing the program development load and reducing the development cost when the program logic needs to be corrected. It is possible to reduce and suppress deterioration of the quality of the program logic. Moreover, according to the slab allocation system 21, it is possible to prevent rework or information inconsistency from occurring by updating all databases in synchronization with each other in a distributed database. It becomes. In addition, according to the slab allocation system 21, all databases can be updated in synchronization with each other even if the database is a hierarchical database. Furthermore, according to the slab allocation system 21, it is possible to efficiently allocate the slab inventory to the slab order.

Next, a database synchronous update processing method according to the third embodiment of the present invention will be described with reference to the drawings.
In this embodiment as well, as in the second embodiment, a case where the database synchronous update processing method according to the present invention is applied to a slab allocation system will be described as an example. Here, in the second embodiment, the case where the slab inventory information can be extracted from the order information at the slave site has been described as an example, but in this embodiment, the slab inventory information is extracted from the order information at the slave site. The case where it cannot be performed will be described as an example.

  FIG. 5 is a schematic configuration diagram of a slab application system according to the third embodiment of the present invention. The basic configuration of the slab allocation system 41 shown in FIG. 5 is the same as that of the slab allocation system 21 shown in FIG. However, the slab allocation system 41 is different from the slab allocation system 21 in that information transmitted and received between the main site and the sub site is slab inventory information and order information. Therefore, description is abbreviate | omitted about the structure same as the slab allocation system 21, and only a different structure is demonstrated below.

Each of the client database 46 and the server database 51 stores order information in addition to slab inventory information. The slab inventory information and order information are stored in a grouped state based on the slab information such as the components and dimensions of each slab.
The input terminal 47 receives slab inventory information and order information. Further, the input terminal 47 includes calculation means (not shown), and derives (calculates) slab inventory information and order information by such calculation means. In the following, the slab inventory information and order information input to the input terminal 47 or the slab inventory information and order information derived (calculated) by the input terminal 47 are simply referred to as slab inventory information and order information. The input terminal 47 displays the allocation result of the slab inventory for the order information.

  The client transaction control means 49 receives the slab inventory information and the order information from the input terminal 47, and confirms the slab information such as the slab components and dimensions related to the order information. Based on the slab information and the slab inventory information and order information stored in the client database 46, the client transaction control means 49 verifies the slave site 43 having a slab inventory that can be allocated to the order information, and executes the transaction. The slave site 43 to be selected is selected. Further, the client transaction control means 49 transmits slab inventory information and order information to the selected slave site 43. Further, the client transaction control means 49 registers the update contents of the client database 46 based on the slab allocation result information returned from the slave site 43, the slab inventory update information (update information) and the order update information (update information), and The commit or rollback of the update contents registered in the client database 46 and the server database 51 is determined.

  The server transaction control unit 52 inputs the slab inventory information and order information received from the client transaction control unit 49 to the determination unit 53 and returns the slab allocation result information output from the determination unit 53 to the client transaction control unit 49. To do. In addition, the server transaction control unit 52, when it is determined that the slab inventory can be allocated to the order in the slab allocation result information output from the determination unit 53, the server database about the allocation of the slab inventory 51 is registered, and the registered slab inventory update information and order update information are returned to the client transaction control means 49.

  Based on the slab inventory information and order information input from the server transaction control unit 52 and the slab inventory information and order information stored in the server database 51, the determination unit 53 determines whether or not the slab inventory can be allocated to the order. Judgment is made. In this case, the determination means 53 stores slab inventory information and slab information check logic such as dimensions and slab information related to the order information, and whether or not slab inventory can be allocated to the order based on the check logic. Is determined.

Next, the flow of the slab allocation process in the slab allocation system 51 will be described with reference to FIG.
First, as shown in FIG. 6, slab inventory information and order information are input or derived (calculated) at the main site 42 (step S301). The slab inventory information and order information input or calculated in the input terminal 47 are input to the client transaction control means 49.
The client transaction control means 49 that has received the slab inventory information and the order information selects the slave site 43 that performs the transaction (step S302), and establishes a communication path with the slave site 43 (step S303).

  After establishing the communication path between the master site 42 and the slave site 43, the client transaction control means 49 sends the slab inventory information and the order information to the server transaction control means 52 of the slave site 43 to start the transaction. (Step S304). Here, the client transaction control means 49 stores the slab inventory information and order information transmitted to the server transaction control means 52 in a file.

The server transaction control means 52 that has received the slab inventory information and order information from the main site 42 inputs the slab inventory information and order information to the determination means 53.
Based on the slab inventory information and order information and the slab inventory information and order information stored in the server database 51, the determination means 53 to which the slab inventory information and order information are input can allocate the slab inventory to the order. Is determined (step S305), and slab allocation result information is output to the server transaction control means 52.

  The server transaction control unit 52 that has input the slab allocation result information from the determination unit 53 determines that the slab inventory can be allocated to the order in the slab allocation result information. The update contents of the server database 51 are registered for (Step S306). Then, the registered information is returned as slab inventory update information and order update information to the client transaction control means 49 together with the slab allocation result information (step S307).

  On the other hand, if it is determined in the slab allocation result information input from the determination unit 53 that the slab inventory cannot be allocated to the order, the server transaction control unit 52 transmits only the slab allocation result information to the client. It returns to the transaction control means 49 (step S308). The slab allocation result information is displayed on the input terminal 47.

  When it is determined in the slab allocation result information that the slab inventory can be allocated to the order, the client transaction that has received the slab inventory update information, the order update information, and the allocation result information from the server transaction control unit 52 The control means 49 registers the update contents of the client database 46 based on the slab inventory update information and the order update information (step S309).

  The client transaction control means 49 that registered the update contents of the client database 46 matches both information based on the slab inventory update information and order update information and the slab inventory information and order information stored in the file. It is determined whether or not there is a match (step S310), and if it is consistent, commit is determined (step S311), and if it is not consistent, rollback is determined (step S312).

Then, the client transaction control unit 49 that has determined the commit transmits a commit instruction to the database update unit 50 and the server transaction control unit 52, and confirms the update contents registered in the client database 46 and the server database 51 ( Step S313).
On the other hand, the client transaction control means 49 that has decided to roll back discards the update contents registered in the client database 46 and sends a rollback instruction to the server transaction control means 52 so that the server database 51 is registered. The updated contents are discarded (step S314).

When the registered update contents of the client database 46 and the server database 51 are confirmed, the slab inventory update information, the order update information, and the allocation result information are displayed on the input terminal 47, and the slab inventory of the order is displayed. Allocation is completed.
On the other hand, when the registered update contents of the client database 46 and the server database 51 are discarded, a message to that effect is displayed on the input terminal 47.

As described above, according to the slab allocation system 41, when the slab inventory information related to the order information is transmitted from the main site 42 to the sub site 43, the sub site 43 cannot extract the slab inventory information from only the order information. However, the same effect as the slab 21 shown in FIG. 3 can be obtained.
In the present embodiment, the slab inventory information and the order information are described. However, the information regarding the slab (actual product) and the information regarding the order may be both or one of them.

Although the embodiments of the present invention have been described above, various modifications can be made in the embodiments of the present invention.
For example, in the second embodiment and the third embodiment of the present invention, a case where the database synchronous update processing method according to the present invention is applied to a slab allocation system is described as an example. However, the database synchronous update processing method according to the present invention may be applied to the coil allocation system.

It is a schematic block diagram of the database synchronous update processing system which concerns on 1st embodiment of this invention. It is a figure which shows the flow of a process in the database synchronous update processing system shown in FIG. It is a schematic block diagram of the slab allocation system which concerns on 2nd embodiment of this invention. It is a figure which shows the flow of a process in the slab allocation system shown in FIG. It is a schematic block diagram of the slab allocation system which concerns on 3rd embodiment of this invention. It is a figure which shows the flow of a process in the slab allocation system shown in FIG. It is a schematic block diagram of the master-slave relationship synchronization system in the distributed database system which concerns on patent document 1. FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Database synchronous update processing system 2 Main site 3 Subordinate site 4 Communication line 6 Client database 7 Input terminal 9 Client transaction control means 10 Database update means 11 Client database 12 Client transaction control means 13 Judgment means 14 Database update means 21 Slab allocation system 22 Main site 23 Subordinate site 24 LAN line 26 Client database 27 Input terminal 29 Client transaction control means 30 Database update means 31 Server database 32 Server transaction control means 33 Judgment means 34 Database update means 41 Slab allocation system 42 Main site 43 Subordinate site 44 LAN Line 46 Client database 47 Input terminal 49 Client transaction control means 50 Database update means 51 Server database 52 Server transaction control means 53 Determination means 54 Database update means

Claims (3)

In a distributed database environment including a master site having a database and a slave site having a database for storing information common to the database of the master site, the slave site is based on update processing started from the master site. A database synchronous update processing method for synchronizing and updating the database of the main site and the database of the main site,
Transmitting update processing information from the primary site to the slave site;
Determining whether or not the update processing of the database at the slave site is possible from the received update processing information and the information stored in the database at the slave site;
A step of registering the update of the slave site when the update process of the database of the slave site is possible, and transmitting the registered update information to the master site;
Registering an update of the main site database based on the received update information;
A database synchronous update processing method comprising: a step of confirming a registered update of the database of the main site and the database of the subordinate site based on the received update information and the update processing information. In a distributed database environment comprising: a slave site having a database for storing at least one of slab inventory information and slab order information; and a master site having a database for storing information common to the slave site database. A slab allocation method for synchronizing and updating the database of the slave site and the database of the primary site based on at least one of the slab inventory information and the slab order information input or derived in
Transmitting at least one of the slab inventory information and the slab order information input or derived at the main site to the slave site;
From at least one of the received slab inventory information and the slab order information, and at least one of the slab inventory information and the slab order information stored in the database at the slave site, the slab inventory is stored in the slab order. Determining whether appropriation is possible;
When the slab inventory can be allocated to the slab order, the update of the database of the slave site is registered, and the registered update information is transmitted to the main site;
Registering an update of the main site database based on the received update information;
Determining a registered update of the primary site database and the secondary site database based on the received update information and at least one of the input or derived slab inventory information and slab order information A slab appropriation method comprising: In a distributed database environment comprising: a slave site having a database for storing at least one of coil inventory information and coil order information; and a master site having a database for storing information common to the slave site database. A coil allocation method for synchronizing and updating the database of the slave site and the database of the main site based on at least one of the coil inventory information and the coil order information input or derived at
The step of transmitting at least one of the coil inventory information and the coil order information input or derived at the main site to the slave site;
The received order information from at least one of the received coil inventory information and the coil order information and at least one of the coil inventory information and coil order information stored in the database of the slave site. Determining whether or not the coil stock can be allocated to the order;
When the coil stock is available for the order, the update of the database of the slave site is registered, and the registered update information is transmitted to the main site;
Registering an update of the main site database based on the received update information;
Based on the received update information and at least one of the coil inventory information and the coil order information input or derived, the registered update of the primary site database and the secondary site database is confirmed. A coil application method comprising the steps of:

Images