JP2000076107A - Data base management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten write/read time to a data base(DB) as much as possible and to read the latest write data with respect to a data base management system. SOLUTION: A DB system for receiving the write/read requests of data generated from plural request sources at all times and writing or reading them is provided with the two sets of the DBs 100 for respectively storing the same data, a DB management means 101 for managing the write/read state of the respective DBs, a write/read means 102 for referring to the DB management means when the write/read request to the DB is generated and executing write/ read to an optional free DB, an updating contents storage means 103 for tentatively storing updating contents in the case of updating the data stored in one DB and a stored data matching means 104 for executing the same updating processing to the stored data of the other DB as well, based on the already stored updating contents after updating to one DB is ended.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database management system, and more particularly, to a database management system in which data collected from a transmission system is written to a database and then searched and referred to as appropriate.

[0002]

2. Description of the Related Art FIG. 10 is a diagram illustrating a transmission device monitoring system to which the present invention is applied, FIG. 11 is a diagram illustrating a conventional log management device, and FIG. 12 is a database search function in FIG. FIG.

In FIG. 10, a transmission system 1 to be monitored by the transmission device monitoring system includes a plurality of transmission devices 2.
Is installed. Whenever a situation (hereinafter, collectively referred to as an event) occurs in each of the transmission devices 2 such as increase / decrease of the number of transmission paths or constituent devices to be accommodated, switching of operation / pause, occurrence / recovery of a failure, occurrence / recovery of congestion, Event data (I) describing the state of the generated event is transmitted to the transmission device 2 of the generation source.
Is generated and sent.

[0004] The log management device 3 collects event data (I) sent from each transmission device 2, transmits it to the monitoring device 4, and writes it as log data (L) in a built-in database (DB). .

Since the present invention manages a database (DB), a description of the function of transmitting the event data (I) sent from the transmission device 2 to the monitoring device 4 will be omitted. Further, the log data (L) is also referred to as event data (I), so that the description is simplified.

The monitoring device 4 analyzes the event data (I) transmitted from the log management device 3, grasps the operation state of each transmission device 2, and instructs necessary countermeasures. The monitoring device 4 reads out and analyzes the event data (I) written in the database (DB) in the log management device 3 to grasp the operation state of the transmission system 1 and to store the stored event. By inserting required data into the data (I), classification and search are facilitated.

As shown in FIG. 11, the conventional log management device 3 includes a notification receiving unit 31, a control receiving unit 32, a control notifying unit 33, and a database (DB) 34. When receiving the event data (I) sent from each transmission device 2, the notification receiving unit 31 transmits the event data (I) to the control notifying unit 33 and requests writing to the database (DB).

[0008] The control notification unit 33 writes the transmitted event data (I) to a database (DB) 34 based on a request from the notification reception unit 31. The control receiving unit 32
A request from the monitoring device 4 to read out data (D) stored in the database (DB) 34 or the database (DB)
Upon receiving a request to write the required data (D) to
The received read request or write request is transmitted to the control notification unit 33, and a request is made to read from the database (DB) 34 or write to the database (DB) 34.

The control notifying unit 33 reads out required data (D) and returns it to the control receiving unit 32 based on a request from the control receiving unit 32, and transmits required document data (D) to a database (DB) 34. Write to.

When requesting the log management device 3 to read the required data (D), the monitoring device 4 presents the required search conditions and requests the log management device 3 to read the data (D) satisfying the search conditions. There are many cases.

The control receiving unit 32, which has received the read request with the search condition, sends the read request with the search condition to the control notifying unit 3.
3, and the control notifying unit 33 transmits the read request with the search condition to the database (DB) 34.

As shown in FIG. 12, a database (DB) 34 includes a DB search unit 341 and a DB storage unit 342.
The DB storage unit 342 actually stores the data (D) requested to be written by the control notification unit 33, and the DB search unit 341 stores the data (D).
Is analyzed, and data (D) satisfying the search condition is read out from the DB storage unit 342.

In FIG. 12, the DB storage unit 342
Data (D) stored in each of the three types of attributes (M) [each attribute (M) is represented by (M ₁ ), (M ₂ ), (M
₃ )], the four event data (I ₁ ), (I ₂ ), (I ₃ ), and (I ₄ ). The search condition given to the read request transmitted to the database (DB) 34 is that the target attribute (M) is (M ₁ ).
And (M ₂ ), and attributes (M ₁ ) and (M ₂ )
Is satisfied (hereinafter referred to as a search key (K)), the attribute (M ₁ ) is “0” and the attribute (M ₂ ) is “0”. ₁ = “0”) ×
(M ₂ = "0")]. [However, "0"
Indicates a decimal number. The database (DB) 34 transmits the read request with search condition transmitted from the control notification unit 33 to the DB search unit 341.

The DB search unit 341 analyzes the received search conditions, finds that the target attributes (M) are (M ₁ ) and (M ₂ ), and the search key (K) is (M ₁ = "0") × (M ₂ =
When the event data is recognized as “0”), the written event data (I ₁ ) to (I ₄ ) are sequentially read from the DB storage unit 342, and the first term (M ₁ = “0”) of the search key (K) is first read. )), And when it is determined that the event data (I ₁ ) and (I ₂ ) correspond, the event data (I ₁ ) and (I ₂ ) are sequentially read out,
The event data (I) corresponding to the second term (M ₂ = “0”) of the search key (K) is searched, and the event data (I ₁ )
When it is determined that only the event data is applicable, the event data (I ₁ )
Is returned as the read data of the read request with search condition transmitted from the control notifying unit 33.

The control notifying unit 33 includes a database (DB)
The event data (I ₁ ) returned from 34 is returned as read data of the read request with search condition transmitted from the monitoring device 4.

[0016]

As apparent from the above description, in the conventional log management apparatus 3, a set of a control notification unit 33 and a database (DB) 34 are provided.
When a plurality of request for writing event data (I) from the transmission device 2 or a request for reading or writing required data (D) from the monitoring device 4 arrives in parallel, In addition, a write request or a read request is linked to a queue and processed in the order of one request. If a large number of write requests or read requests are rushed at the same time, the waiting time increases, and it cannot be processed quickly. There was a problem.

In the conventional log management device 3,
When a read request with a search condition is received from the monitoring device 4,
Based on the attribute (M) to be searched by the DB search unit 341 in the database (DB) 34, the DB storage unit 342
Since the data that has already been written is searched for, the required search time increases as the number of search target attributes (M) increases.

Further, in the conventional log management device 3,
When a read request for the written data is received in the database (DB) 34 and a write request for the event data (I) arrives during the required read processing, the event data (I)
Is started after the first-arrival reading process is completed, the immediately preceding read data does not include the second-arrival event data (I). There was a problem that the latest write data was not reflected.

An object of the present invention is to shorten the time for writing and reading data to and from a database as much as possible and to read the latest write data.

[0020]

FIG. 1 shows the principle of the present invention. FIG. 1 (a) shows the principle of the present invention (claims 1 to 3), and FIG. 1 (b) shows the present invention ( The principle of claims 4 and 5) will be described.

First, FIG. 1A shows a database system which accepts data write / read requests that occur as needed from a plurality of request sources and writes or reads the data in a database.

Reference numeral 100 denotes two databases provided in the database system according to the present invention (claims 1 to 3). Reference numeral 101 denotes a database management unit provided in the database system according to the present invention (claims 1 to 3).

Reference numeral 102 denotes a writing / reading means provided in the database system according to the present invention (claims 1 to 3). Reference numeral 103 denotes an update content storage unit provided in the database system according to the present invention (claims 1 to 3).

Reference numeral 104 denotes storage data matching means provided in the database system according to the present invention (claims 1 to 3). Each database 100 stores the same data.

The database management means 101 manages the writing / reading state of each database 100. When a write / read request to the database 100 occurs, the writing / reading unit 102 refers to the database managing unit 101 and executes writing / reading to an arbitrary empty database 100.

When the data stored in one of the databases 100 is updated, the update content storage means 103 temporarily stores the update content. Storage data matching means 104
Is executed on the data stored in the other database 100 on the data stored in the other database 100 based on the update content stored in the update content storage unit 103 after the update on the one database 100 is completed. Execute the same update processing as [The above is related to the present invention (claim 1). The writing / reading means 102 is connected to one of the databases 10
After reading the data from 0, the update content stored in the update content storage means 103 is read, and one database 100 is read.
It is considered that the data read out of the update content and the update content read out from the update content storage unit 103 are compared to synthesize read data including the latest update content. [Related to the present invention (claim 2). Further, by dividing and managing each database 100 by data type and providing a plurality of threads in the writing / reading means 102, it is possible to execute the above-described writing / reading by type in parallel. Be considered. [Related to the present invention (claim 3). Next, FIG. 1B shows a database system that receives a data search request generated from a request source and reads out the corresponding data from a database.

Reference numeral 200 denotes a database provided in the database system according to the present invention (claims 4 and 5). Reference numeral 201 denotes a search condition registration unit provided in the database system according to the present invention (claims 4 and 5).

Reference numeral 202 denotes search means provided in the database system according to the present invention (claims 4 and 5). The database 200 stores data having a plurality of attributes.

The search condition registration means 201 pre-registers search conditions for searching for data in which each attribute satisfies a required condition from data stored in the database 200.

When writing data to the database 200, the search means 202 adds information for identifying a search condition that satisfies the data from the search conditions registered in the search condition registration means 201. Search condition registration means 201
When a search request with a search condition registered in the database 200 occurs, the search condition added to each data stored in the database 200 is referred to satisfy the search condition added to the search request. Data to be detected.
[The above is related to the present invention (claim 4). When a search request with an unregistered search condition is generated, the search condition registration unit 201 holds the unregistered search condition, and stores the search condition registered in the search condition registration unit 201. The frequency of use and the frequency of use of each unregistered search condition being held are counted for each search condition, and the frequency of use of each registered search condition and each unregistered search condition are compared later. Only the search condition is newly registered and changed.

The search means 202 considers updating the search condition identification information added to each data stored in the database 200 based on the search conditions registered and changed in the search condition registration means 201. [The above is related to the present invention (claim 5). Therefore, according to the present invention (claims 1 to 3), data can be written / read in parallel to two sets of databases each storing the same storage data, and the read data can be read / written. Can always incorporate the latest updated contents, furthermore, it is possible to execute write / read requests for a plurality of types of data in parallel to a set of databases, and the present invention (claims 4 and 5) According to this, data that satisfies the search requirements can be quickly detected,
The convenience of the database system is greatly improved.

[0032]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 2 is a diagram showing a log management device according to an embodiment of the present invention, FIG. 3 is a diagram showing a signal sequence according to an embodiment of the present invention (claim 1), and FIG.
FIG. 5 is a diagram illustrating a setting status of various flags in FIG. 5, FIG. 5 is a diagram illustrating a signal sequence according to the embodiment of the present invention (claim 2), and FIG. 6 is a diagram illustrating a setting status of various flags in FIG. FIG. 7 shows the present invention (claim 3).
FIG. 8 is a diagram showing a data write / read status according to the embodiment of the present invention, FIG. 8 is a diagram (No. 1) showing a data search status according to the embodiment of the present invention (claims 4 and 5), and FIG. It is FIG. (2) which shows the data search situation by embodiment of (claim 4 and 5). The same reference numerals indicate the same objects throughout the drawings. The target transmission device monitoring system is as shown in FIG.

The log management apparatus 3 shown in FIG. 2, the notification receiving unit 31, the control receiving unit 32, two sets of control notification unit 33 [refer to individual control notification unit 33 _1, 33 _2, hereinafter the same], It comprises two sets of databases (DB) 34, a DB access management unit 35, a difference buffer 36, and a search key file 37.

The notification reception unit 31 receives the event data (I) sent from the transmission device 2 in the transmission system 1, to control the notification unit 33 _2, or control notification unit 33 _first database (DB) 34 ₁ or requests writing to 34 _2.

The control receiving unit 32, the read request for the database to be transmitted from the monitoring device 4 (DB) 34 ₁ or 34 ₂ to the write completion of the data (D) [i.e. event data (I)] (Q _R), Or, a write request (Q _W ) of required data (D) [information other than event data (I)] is received,
To control notification unit 33 ₁ or the control notification unit 33 ₂ to request the reading and writing to the database (DB) 34 ₁ or 34 _2.

Each of the control notifying units 33 requests the writing of the event data (I) from the notification receiving unit 31 or the control receiving unit 3.
2 receives a request to write / read data (D) from
After confirming the usage of both database (DB) 34 to the B access management unit 35, writing of the data base (DB) 34 ₁ or 34 _2, requested the writing of event data (I) or data, (D) Execute read / write.

When the event data (I) or data (D) is written, the same event data (I)
Alternatively, the data (D) is also written to the difference buffer 36.
In addition, each control notification unit 33 includes both databases (DB) 34
Is in an unused state, the database (DB) 3
41 ₁ shall be used preferentially.

The DB access management unit 35 manages the write state and reading state of the two databases (DB) 34, also written in only one database (DB) 34 ₁ or 34 _2, write the delta buffer 36 the are written-flop with data (D), the other not written yet written database (DB) by writing 34 ₂ or 34 written to _1, the event data being written to both databases (DB) 34 (I) Alternatively, the data (D) is the same.

Further, the search key file 37 is stored in the monitoring device 4
Holds the search condition (hereinafter referred to as the search key (K)) for reading the event data (I) or data (D) already written in the database (DB) 34 from the storage key (K). Event data (I) or data (D)
Read time is reduced.

In the notification receiving section 31, a use state flag check section (BF) incorporating a use state flag (f ₃₃₂ ) is provided.
C) 311, a function selection inquiry section (FSA) 312 and a write request section (IWR) 313 are provided, and a use state flag check section (a use state flag (f ₃₃₂ ) built in the control reception section 32) BFC) 321, function selection inquiry section (FSA) 322, read / write request section (RWR) 323
And a read result notifying unit (RDS) 324 are provided. Each control notifying unit 33 includes a DB access flag checking unit (DFC) 331 and a buffer writing / reading unit (BW).
R) 332, a DB writing / reading unit (DWR) 333, and a data synthesizing unit (DCM) 334, and a DB writing flag (f _W1 ) in the DB access management unit 35;
(F _W2 ), DB read flag (f _R1 ), (f _R2 ), buffer read unit (DDR) 351, DB difference write unit (DDW)
352, a use status flag release unit (BFR) 353, and a search key file management unit (KFM) 354 are provided.

The use status flag (f ₃₃₂ ) included in the use status flag check unit (BFC) 311 is stored in the control notification unit 33.
_{When 1} is in the unused state, it is set to logic “0”, but when it is in use, it is set to logic “1”.

The use status flag check unit (BFC) 32
1 built-in usage flags (f _{33 1)} is control notification unit 33 ₂ is set to a logic "0" when it is in an unused state, a logic "1" if is in use Is set.

The D built in the DB access management unit 35
B write flag (f_W1) Is a database (DB) 34₁
Is set to logic "0" when is in the unwritten state
Is set to logic "1" when in the write state,
DB write flag (f_W2) Is the database (DB) 3
4_TwoIs set to logical "0" when
However, when it is in the write state, it is set to logic "1",
In addition, the DB read flag (f _R1) Is a database (DB)
34₁Is set to logical "0" when
However, when it is in the read state, it is set to logic "1".
And the DB read flag (f_R2) Is the database (D
B) 34_TwoIs set to logic "0" when
Set to logic "1" when in read state
Is done.

First, an embodiment of the present invention (claims 1 and 2) will be described with reference to FIG. 2 to FIG. 6 and FIG.
The database (DB) 34 includes a database 100 in FIG. 1A and a database 2 in FIG.
00, and a use status check unit (BFC) 311 and a function selection inquiry unit (FSA) 312 in the notification reception unit 31, a use status check unit (BFC) 321 and a function selection in the control reception unit 32 Inquiry section (FS
A) 322, DB access flag checker (DFC) 331 and DB access manager 35 in each control notifier 33
DB write flags (f _W1 ), (f _W2 ), DB read flags (f _R1 ), (f _R2 ), and use status flag release section (B)
1 (a), a write request unit (IWR) 313 in the notification receiving unit 31, and a read / write request unit (RWR) 323 in the control receiving unit 32. , DB writing / reading unit (DWR) 333 and data synthesizing unit (DCM) in each control notifying unit 33
334 plays the role of the writing / reading means 102 in FIG. 1A, and the buffer writing / reading section (BWR) 332 of each control notifying section 33 and the difference buffer 36 serve as the update content storage means in FIG. Plays the role of 103 and D
Buffer reading unit (DDR) 3 in B access management unit 35
Reference numeral 51 plays a role of the update content storage means 103 in FIG. 1A, and a buffer reading unit (DDR) 351 and a DB difference writing unit (DDW) in the DB access management unit 35.
352 is the write data matching means 104 in FIG.
Plays a role.

First, the process of collecting event data (I) according to the embodiment of the present invention (claim 1) will be described with reference to FIGS. 2 to 4 and FIG. In FIGS. 2 to 4 and 10, when no event data (I) is transmitted from the transmission device 2 and a required read or write request is not generated from the monitoring device 4, log management is performed. The two control notification units 33 in the device 3 are both in the unused state, and the usage flag (f) built in the usage flag checking unit (BFC) 311 in the notification receiving unit 31
₃₃₂ ) and the usage flag (f ₃₃₁ ) incorporated in the usage flag checking unit (BFC) 321 in the control reception unit 32 are both set to logic “0”, and two sets of databases (DB) Reference numeral 34 denotes a DB write flag (f) corresponding to a database (DB) 34 ₁ incorporated in the DB access management unit 35, which is not in a write or read state.
_W1) and DB read flag (f _R1), and a database (DB) 34 ₂ the corresponding DB write flag (f _W2) and DB read flag (f _R2) is also set to all logic "0".

In this state, when the event data (I) is transmitted from the transmission device 2, the event data (I) is transmitted to the log management device 3 via the transmission path in the transmission system 1. In the log management device 3, when the notification receiving unit 31 receives the event data (I) transmitted from the transmission device 2, the usage flag checking unit (BFC) 311 checks the built-in usage flag (f ₃₃₂ ). Referring to FIG. 4A, when it is determined that the logic is set to "0" (see FIG. 4A), the control notification unit 33 ₂
Is confirmed to be in the unused state, the use status flag (f ₃₃₂ ) is set to logic “1”, and the control notification unit 33 is set.
Change the setting of ₂ to the use state (see FIG. 4 (b)).

[0047] Then the writing request unit (IWR) 313 is to transmit the event data (I) that has received the control notification unit 33 _2, and requests the writing to the database. Control notification unit 33
₂ receives the request to write the event data (I) from the notification accepting unit 31, and receives the DB access flag checking unit (DF
C) 331 ₂ refers to the DB write flags (f _W1 ) and (f _W2 ) and the DB read flags (f _R1 ) and (f _R2 ) in the DB access management unit 35, and
_W1 ) and the DB read flag (f _R1 ) are both set to logic "0", so that the database (DB) 34 ₁
Is confirmed to be unused (see FIG. 4C), the event data (I) is stored in the database (DB) 3.
4 ₁ , the DB write flag (f _W1 ) is changed to a logical “1”, and the database (DB) 34 _{1 is written.}
Is changed to the write state (see FIG. 4D).

Next, a buffer write / read unit (BWR) 332
₂ writes the event data (I) into the difference buffer 36. Next, the DB write / read unit (DWR) 333 ₂ writes the event data (I) into the database (DB) 34 ₁ .

The event data (I) database (D
B) When the writing to 34 ₁ is completed, the DB access flag checking unit (DFC) 331 ₂ causes the DB access management unit 35
The DB write flag of the internal (f _W1), and configuration changes to a logic "0" from logic "1", sets change the database (DB) 34 ₁ to unwritten state [FIG. 4 (e)].

The DB access control unit 35, by monitoring the setting change status of the DB write flag (f _W1), upon identifying a write completion for one database (DB) 34 _1, a buffer read unit (DDR) 351 reads the event data (I) already written in the difference buffer 36.

Next, the DB difference writing unit (DDW) 352
Buffer read portion (DDR) 351 of the read event data (I), for writing to the other database (DB) 34 _2, DB write flag (f _W2) and DB read flag (f _R2) are both logical After confirming that it is set to “0” (see FIG. 4E), the DB write flag (f _W2 ) is changed from logic “0” to logic “1”, and the database (DB) 34 is changed. After changing the setting to ₂ in the writing state [Fig. 4 (f)
Reference], and the event data (I) is stored in a database (DB).
34 ₂ After writing in, and setting change DB write flag (f _W2) from the logic "1" to a logic "0", the database (D
B) 34 ₂ Setting changes to non-written state [see FIG. 4 (g)].

[0052] DB access management unit 35, by monitoring the setting change status of the DB write flag (f _W2), upon identifying a write completion of the other database (DB) the same event data for the 34 ₂ (I) The use flag release unit (BFR) 353 sets the use flag (f ₃₃₂ ) included in the use flag inspection unit (BFC) 311 in the notification reception unit 31 from logic “1” to logic “0”. change, changing the setting control notification unit 33 ₂ in the unused state [see FIG. 4 (h)]. Further, the DB access management unit 35 deletes the write data (D _W ) stored in the difference buffer 36.

As is apparent from the above description, according to the embodiment of the present invention (claim 1), when the event data (I) is transmitted from the transmission device 2, the control notification unit 33 in the log management device 3 ₂ is a DB built in the DB access management unit 35
Write flag _{(f W1), (f W2} ) and DB read flag _{(f R1), (f R2} ) by reference to the, after confirming the write-read state of the database (DB) 34 ₁ and 34 ₂ , One database in unused state (DB)
34 with writing event data (I) to _1, even temporarily stores event data (I) to the delta buffer 36, as soon as the writing process to the database (DB) 34 ₁ is completed, D
The B access management unit 35 stores the event data (I) stored in the difference buffer 36 into the other database (DB) 3
4 by writing also to _2, both databases (DB) 3
4, the same data (D) is always stored.

Next, a process of reading data (D) already written in the database according to the embodiment of the present invention (claim 2) will be described with reference to FIGS. 2, 5, 6 and 10.
2, 5, 6, and 10, in a state where no event data (I) is transmitted from the transmission device 2 and a required read request or write request is not generated from the monitoring device 4. As described above, the two sets of control notifying units 33 in the log management device 3 are both in the unused state, and the two sets of databases (DB) 34 are not in the writing or reading state. usage flag of the management apparatus _{3 (f 33 2), (} f 331), DB write flag (f _W1),
(F _W2 ) and the DB read flags (f _R1 ) and (f _R2 ) are all set to logic “0”.

In this state, a write request (Q _W ) of a certain data (D) from the monitoring device 4 [hereinafter, the data (D) targeted for the write request is referred to as write data (D _W ), The write request (Q _W ) accompanied by the write data (D _W ) is sent to the write request [Q _W
(D _W )]. Is transmitted to the log management device 3.

In the log management device 3, the control receiving unit 3
2 is the write request [Q
_W (D _W )], the usage status check unit (B
FC) 321 refers to the use state flag (f ₃₃₁₎ that incorporates, when it detects that it is set to a logic "0" [refer to FIG. 6 (a)], the control notification unit 33 ₁ is unused state after confirming that the usage flag (f ₃₃₁₎ and configuration changes to a logic "1", changing the setting control notification unit 33 ₁ in use [refer to FIG. 6 (b)]. [Note At present, the control notification section 33 ₂ is also in an unused state, usage flag in notification reception unit 31 (f _{33 2)} are also set to logic "0". ] Then read write request unit (RWR) 323 is transmitted the received write request [Q _W a (D _W)] to control notification unit 33 _1,
Request writing to the database.

[0057] control notification unit 33 ₁ receives the write request [Q _W (D _W)] to control reception unit 32, the DB access flag checking unit (DFC) 331 ₁ is, DB in the DB access management unit 35 Write flags (f _W1 ) and (f _W2 ), D
Referring to B read flags (f _R1 ) and (f _R2 ), since both DB write flag (f _W1 ) and DB read flag (f _R1 ) are set to logic “0”, database (DB) 34 ₁ determines that the writing confirms that it is in the unused state [refer to FIG. 6 (c)], the write data (D _W) in the database (DB) 34 _1, DB write flag (f _W1 ) Is changed to logic “1” and the database (D
B) 34 ₁ changes the setting to the write state [see FIG. 6 (d)].

Next, a buffer write / read unit (BWR) 332
₁ writes the write data (D _W ) into the difference buffer 36. Next, the DB write / read unit (DWR) 333 ₁ writes the write data (D _W ) into the database (DB) 34 ₁ .

The write data (D _W ) is stored in the database (D
B) In parallel with the writing to the 34 ₁ , when the monitoring device 4 newly sends a read request (Q _R ) of the data (D) stored in the database (DB) 34, the log management device 3 is transmitted. [Data to be read thereafter (D)
Is referred to as read data (D _R ). In the log management device 3, when the control receiving unit 32 receives the read request (Q _R ) sent from the monitoring device 4,
Use state flag checking unit (BFC) 321 refers to the built-use state flag (f _331), when it detects that it is set to a logic "1", the control notification unit 33 ₁ is in the state during use (See FIG. 6 (b)).

[0060] When in use of the control notification section 33 ₁ is recognized, the function selection inquiry unit (FSA) 322 is the function selection inquiry unit (FSA) 312 within the notification reception unit 31, the usage flag checking unit (BFC ) 311 queries the setting state of the use state flags (f ₃₃₂₎ for built-in, recognizes and being set to a logic "0", control notification unit 33 ₂ confirms that it is in an unused state [FIG. 6 (e) ], the usage control notification section 33 ₂ by using the decided to perform a read request (Q _R), function selection inquiry unit (FSA) 312 through the use state flag checking unit (BFC) 311 Flag ( _f331 )
The requesting configuration changes to a logic "1", changing the setting control notification unit 33 ₂ in use [see FIG. 6 (f)].

[0061] Then the read write request unit of the control reception section 32 (RWR) 323 is transmitted the received read request (Q _R) in the control notification unit 33 _2, a request for reading from the database.

[0062] control notification unit 33 ₂ receives the read request (Q _R) from the control receiving unit 32, the DB access flag checking unit (DFC) 331 ₂ is, DB write flag in the DB access control unit 35 (f _{With reference to} ( _W1 ) and ( _fW2 ) and the DB read flags ( _fR1 ) and ( _fR2 ), since the DB write flag ( _fW1 ) is set to logic "1", the database (DB) 34 ₁ is in use, but since both the DB write flag (f _W2 ) and the DB read flag (f _R2 ) are set to logic “0”, the database (D
B) When 34 ₂ recognizes that the unused state [FIG. 6
see (d)], determined in the database (DB) 34 ₂ be read from, and setting change DB read flag (f _R2) to a logic "1", sets change the database (DB) 34 ₂ to the read state [See FIG. 6 (g)].

Next, a DB write / read unit (DWR) 333
_TwoIs a database (DB) 34_TwoRequired data from
(D₃₄₂) Is read. On the other hand, the control notification unit 33₁DB inside
Write / read unit (DWR) 333₁Is the write data (D_W)
Database (DB) 34₁After writing to the DB
Access flag checker (DFC) 331₁But DB access
DB write flag (f_W1), Logical
The setting is changed from “1” to logic “0” and the database (D
B) 34 ₁To the unwritten state (see Fig. 6 (h)
See).

[0064] On the other hand, DB write and read portions of the control notification section 33 in ₂ (DWR) 333 ₂ is a database (DB) 34 ₂
After reading the required data (D ₃₄₂ ) from the DB access flag checking unit (DFC) 331 ₂ , the DB read flag (f _R2 ) in the DB access management unit 35 changes the DB read flag (f _R2 ) from logic “1” to logic “0”. To the database (D
B) 34 ₂ changes the setting to the state leaving unread [see FIG. 6 (i)].

Next, a buffer write / read unit (BWR) 332
₂ refers to the difference buffer 36 and finds some data (D
₃₆ ) When recognizing that the write data (D _W ) by the write request [Q _W (D _W )] is currently being stored, the stored write data (D _W ) is read.

Next, the data synthesizing unit (DCM) 334 ₂
The DB write / read unit (DWR) 333 ₂ stores the database (D
B) from 34 ₂ and the read data (D _342), a buffer write and read unit (BWR) 332 ₂ is compared with the read out write data from the delta buffer 36 (D _W), write data (D _W) There whether the target of the read request (Q _R), and the target database (DB) 34 analyzes whether or not woven into the read data (D ₃₄₂₎ from _2, read request (Q _R) , And recognizes that it is not included in the read data (D ₃₄₂ ), by combining the read data (D ₃₄₂ ) with the write data (D _W ), the write request [Q _W (D _W )], And edits the read data (D _R ) corresponding to the read request (Q _R ), including the latest write data (D _W ), and returns it to the control accepting unit 32.

In the control receiving section 32, the control notifying section 3
3 ₂ read request from the read data to the (Q _R) (D _R)
When There is returned, control notification unit 33 ₂ read request (Q _R)
From the execution of the function selection inquiry section (FS
A) 322 requests the setting change of the usage status flag (f ₃₃₂ ) in the usage status checking unit (BFC) 311 from the logic “1” to the logic “0” via the function selection inquiry unit (FSA) 312. the control notification unit 33 ₂ sets changed to an unused state [see FIG. 6 (j)].

Next, the read result notifying unit (RDS) 324
Read data sent back from the control notification unit 33 ₂ (D _R)
Is returned to the monitoring device 4 that has issued the read request (Q _R ). On the other hand, the DB access management unit 35 monitors the setting change status of the DB write flag (f _W1 ), and identifies the completion of writing to the _one database (DB) 341. Reads the data (D ₃₆ ) currently stored in the difference buffer 36 (the write data (D _W ) based on the write request [Q _W (D _W )] at this time).

Next, the DB difference writing unit (DDW) 352
Buffer read portion (DDR) 351 of the read write data (D _W), for writing to the other database (DB) 34 _2, DB write flag (f _W2) and DB read flag (f _R2) is After confirming that both are set to logic "0" (see FIG. 6 (i)), the DB write flag (f _W2 ) is changed from logic "0" to logic "1", and the database (DB) is changed. ) 34 ₂ after setting change to the write state [FIG. 6 (k)
And write data (D _W ) to database (DB) 3
4 ₂ After writing in, and setting change DB write flag (f _W2) from the logic "1" to a logic "0", the database (D
B) 34 ₂ Setting changes to non-written state [see FIG. 6 (l)].

The DB access management unit 35 provides a DB write flag.
(F_W2) By monitoring the setting change status
Database (DB) 34_TwoSame write data for
(D _WWhen the writing completion is identified, the control notification unit 33₁To
Write request [Q_W(D_W)]
Then, the usage status flag release unit (BFR) 353 receives the control
The usage flag inspection unit (BFC) 321 in the attachment unit 32
Built-in usage flag (f₃₃₁) From the logic "1"
The setting is changed to logic “0”, and the control₁Unused status
Change the setting to the state (see FIG. 6 (m)).

As is clear from the above description, the present invention (contract
According to the embodiment of item 2), the monitoring device 4
(D_W) Write request (Q_W) Is sent out and the log management
Control notification unit 33 in the device 3₁Is unused.
Database (DB) 34₁Write data (D_WWrite)
In addition, the write data (D_W)
During the temporary storage, a new read data is read from the monitoring device 4.
Data (D_R) Read request (Q_R) Is sent, the log
The control notification unit 33 in the unused state in the management device 3_TwoBut,
The other database (DB) 34 in an unused state_TwoOr
Required data (D₃₄₂) And the difference buffer
Data (D₃₆) Also reads out the database
(DB) 34_TwoData (D₃₄₂) And diff
Data read from the buffer 36 (D₃₆Analysis)
The read request (Q _R)
Memory data (D_R) Can be returned.

Next, a database writing / reading method according to an embodiment of the present invention (claim 3) will be described with reference to FIGS. The event data (I) transmitted from each transmission device 2 is classified into a plurality of types.
A plurality of types of event data (I) may be transmitted from each transmission device 2.

In the log management device 3 shown in FIG. 7, each database (DB) 34 stores event data (I) divided for each type. Hereinafter, each divided part of the database (DB) 34 is referred to as a partial database (SDB) 343.

A plurality of threads are provided in a DB write / read unit (DWR) 333 provided in each control notification unit 33. 2, 7, and 10,
When a read request (Q _R ) for a plurality of types of event data (I) is sent from the monitoring device 4, the log management device 3
In the same manner as described above, the control reception unit 32 receives the read request (Q _R ) sent out, and the control notification unit 33
_{When 1} is selected and the received read request (Q _R ) is transmitted,
Control notification unit 33 _1, as well as selecting the readable one database (DB) 34 _1, analyzes the transmitted read request (Q _R), recognizes the read request of a plurality of types of event data (I) , The read request (Q _R ) is divided for each type of event data (I), and the DB write / read unit (DW
Each thread is provided in the R) 333 _1, and transmits each of the divided read request was the (Q _R).

Each thread is provided in a selected database (DB) 34 ₁ and stores a partial database (I) for storing the type of event data (I) targeted by the transmitted read request (Q _R ). The required event data (I) is read from the SDB) 343.

[0076] Note that each thread, because it has received different types of events read request for data (I) and (Q _R), in the same database (DB) 34 _1, from different parts database (SDB) 343 respectively The event data (I) is read out, and each thread executes the reading process in charge in parallel.

Next, a read request (Q _R ) for a certain type of event data (I) is sent from a certain monitoring device 4, and the control reception unit 32 in the log management device 3 sends the read request (Q _R ). receives a control notification unit 33 ₁ elect to execute the read request (Q _R), also DB write and read unit (DWR) 333 ₁
Certain threads of the inner is chosen in order to execute the read request (Q _R), elected database (DB) 34 ₁ of the read request subject to the type of event data (I) the storage of the (Q _R) It is assumed that the process of reading required event data (I) from the partial database (SDB) 343 to be performed is being executed.

In this state, when a read request (Q _R ) of a certain type of event data (I) is sent from another monitoring device 4, the control receiving unit 32 receives the read request (Q _R ),
Attempt to select the control notification unit 33 that executes the read request (Q _R ).

[0079] At this time, control notification unit 33 ₁ is in use, the control notification section 33 ₂ is unused, the embodiment of the present invention embodiments and the present invention (Claim 1) (claim 2) In the log management device 3 in the control notification unit 33 ₂
Although the can but be elected, control reception unit 32 in the embodiment of the present invention (Claim 3), the type of target event data (I) of the read request running control notification unit 33 ₁ (Q _R) Can be recognized by, for example, a built-in event data type flag or the like.
The type of the target event data (I) of the read request (Q _R ) being executed in step ₁ is compared with the type of the target event data (I) of the newly received read request (Q _R ), and both types are different. It found when uses other threads in control notification unit 33 ₁ for a new read request (Q _R), the same database (DB) 34 _1, target event of the read request (Q _R) and Judging from other parts database (SDB) 343 corresponding to the type of data (I) and can read a desired type of the event data (I), to transmit the new read request (Q _R) in the control notification section 33 ₁ .

[0080] control notification unit 33 _1, the newly transmitted the read request (Q _R), DB write and read unit (DWR) 333 ₁
Of unused threads in the database (DB) 34
₁ , a partial database (SDB) 343 for storing event data (I) of the type corresponding to the read request (Q _R )
To read out desired event data (I).

The control accepting unit 32 sends a new and old read request.
(Q_R) Is the type of event data (I)
As a result of comparison, if both are found to be of the same type,
Notification unit 33 ₁(DB) 34 being read by
₁New read request (Q_R) Target partial data
The base (SDB) 343 has already been₁Inside
While reading from the thread, a new read request (Q_R) Run
It is determined that it cannot be performed, and the other control notification unit 33_TwoA new read
Request (Q_R) To execute the read request (Q_R)
To communicate.

As is apparent from the above description, according to the embodiment of the present invention (claim 3), the DB in the control notifying section 33
A plurality of threads are provided in the write / read unit (DWR) 333,
In addition, the database (DB) 34 stores the event data (I)
By dividing into a partial database (SDB) 343 for each type, a plurality of write / read requests of different types of event data (I) can be performed in parallel by one control notification unit 33 and database (DB) 34. It can be executed.

Next, a database writing / reading method according to an embodiment of the present invention (claims 4 and 5) will be described with reference to FIGS. 2, 8 to 10. 2, a database (DB) 34 plays the role of the database 200 in FIG. 1B, and a search key file 37
1B plays a role of the search condition registration unit 201, and a search key file management unit (KFM) 354 provided in the DB access management unit 35 functions as the search unit 202 in FIG. 1B. Fulfill.

The event data (I) stored in the database (DB) 34 includes a plurality of (three in FIG. 8) attributes (M) [each attribute is referred to as (M ₁ ), (M ₂ ), etc. And each attribute (M) has a value of “0” or more.

In the search key file 37, a predetermined type (eight types in FIG. 8) of search keys (K) for searching the event data (I) in the database (DB) 34 is registered. Search key (K) [Each search key is referred to as (K ₁ ), (K ₂ ), or the like. ] Can be accumulated.

Further, search bits (B) [individual search bits] corresponding to predetermined types (four types in FIG. 8) of search keys (K ₁ ) to (K ₄ ) registered in the search key file 37, respectively. Are referred to as (B ₁ ) to (B ₄ )].

In FIG. 2, FIG. 8 to FIG.
Prior to the operation of the monitoring system, the search key of the log management device 3
The file 37 contains two types of search keys (K₁)and
(K _Two) Is registered, and the remaining six search keys (K
_Three) Through (K₈) Is unregistered.

The search key (K ₁ ) has an attribute (M ₁ ) of “0” and an attribute (M ₂ ) of “0” [(M ₁ = "0")
× (M ₂ = "0")] and the search key (K ₂ )
Indicates that the attribute (M ₁ ) is “0” and the attribute (M ₃ ) is “0”
[(M ₁ = "0") × (M ₃ = "0")].

Before operation, each search key (K)
Are set to “0” in FIG.
8 (a), first stage, see]. Such a transmission device monitoring system
Operation of the system is started, and event data is transmitted from the transmission device 2.
(I₁) And (I)_Two) Is sent, the log management device
3 is the event data by the same process as described above.
(I₁) And (I)_Two) Received by the notification receiving unit 31
If any of the control notification units (for example, 33₁) And DB
Database (DB) 34 by the access management unit 35₁
And 34_TwoIs executed, the present invention (claim
In the fourth and fifth embodiments, the DB access management unit 3
5, a search key file management unit (KF
M) 354 is the event data to be written (I ₁)and
(I_Two) After analyzing the attribute (M), search key file
37, each event for the registered search key (K)
Data (I₁) And (I)_TwoJudge satisfaction)
Then, a search bit (B) indicating the determination result is added.

Search key file management unit (KFM) 354
Is the event data (I₁) Analysis of the attributes
(M₁= "0"), (M_Two= "0"), (M_Three=
"0") and registered in the search key file 37
Search key [K₁= (M₁= "0") x (M_Two=
"0")] and the search key [K_Two= (M₁= “0”) ×
(M_Three= “0”)], the search key
ー (K₁) Corresponding to the search bit (B ₁) And search key
(K_Two) Corresponding to the search bit (B_Two) And
Satisfaction status (eg, logic "1") is set, and other searches are performed
Key (K_Three) And (K_Four) Is unregistered and satisfied
Since it cannot be determined, the corresponding search bit (B_Three) And (B)
_Four) Is set to an unsatisfied state (eg, logic “0”)
And the event data (I ₁).

Subsequently, a search key file management unit (KFM)
Reference numeral 354 denotes a result of analysis of the event data (I ₂ ), the attributes (M ₁ = "0"), (M ₂ = "1"), (M ₃ =
“0”), and the search key [K ₁ = (M ₁ = "0") × (M ₂ =
“0”)] is not satisfied, but the search key [K ₂ = (M ₁ =
If it is determined that “0”) × (M ₃ = "0")] is satisfied, the search bit (B ₁ ) corresponding to the search key (K ₁ ) is set to an unsatisfied state (ie, logic “0”), and the search is performed. Key (K
Search bits corresponding to ₂₎ (B ₂₎ is set to satisfy conditions [i.e. logic "1"], other search key (K ₃₎ and (K ₄₎ is therefore not registered, the search key (K ₁₎ Similarly, the corresponding search bits (B ₃ ) and (B ₄ ) are respectively set to the unsatisfied state (ie, logic “0”) and added to the event data (I ₂ ).

[0092] control notification unit 33 ₁ and the DB access control unit 35 searches the bit (B ₁₎ to the (B ₄₎ an additional pre event data (I ₁₎ and (I _2), a database (DB) 34 ₁ and 34 ₂ writes in [FIG. 8 (a), the first stage, see FIGS.

On the other hand, from the monitoring device 4,
Event data stored in database (DB) 34
In response to (I), the search key registered in the search key file 37
ー (K ₁When a search request using
The device 3 controls and receives the search request in the same process as described above.
Received by the control unit 32, and any control notification unit (for example, 33
₁) And the DB access management unit 35
(DB) 34₁And 34_TwoExecute reading from
However, in the embodiment of the present invention (claims 4 and 5), D
Search key file management unit (K in the B access management unit 35
FM) 354 identifies the search condition of the search request to be executed this time.
And search key (K₁), The data
Event data (I) stored in the database (DB) 34
Search bit (B₁) Through (B)_Four)of
Within the search key (K₁) Corresponding to the search bit (B₁)But
Event data (I) set to logic "1" is the search key
(K₁), The control notifying unit 33₁Inside
DB writing and reading unit (DWR) 333₁Search bit (B
₁= “1”) to instruct retrieval of event data (I)
And the search key of the search key file 37
(K₁) Corresponding to the count value (C₁Add “1” to)
You.

[0094] DB write and read unit (DWR) 333 ₁ is by a process similar to that described above, the read subject data base (DB)
After selecting [for example, 34 ₁ ], based on an instruction from the search key file management unit (KFM) 354, a search of the event data (I) by the search bit (B ₁ = “1”) is executed, and the search bit ( Event data (I ₁ ) to which B ₁ = “1”) is added is detected.

[0095] control notification unit 33 _1, the detected event data (I _1), and returns through the control reception unit 32 to the search request source of the monitoring device 4. Subsequently, a search request using the search key (K ₂ ) registered in the search key file 37 is issued from the monitoring device 4 to the event data (I) stored in the database (DB) 34 in the log management device 3. When it occurs,
In the log management device 3, by the same process as described above,
When the search key file management unit (KFM) 354 in the DB access management unit 35 analyzes the search condition of the search request to be executed this time, and identifies that the search request is the search key (K ₂ ),
Of database (DB) 34 that are added to it are searched bits already stored in the event data (I) (B ₁₎ to (B _4), the search bit corresponding to the search key (K ₂₎ (B ₂₎ is a logical Event data (I) already set to "1"
There recognizes that satisfies the search key (K _2), DB write and read portions of the control notification section 33 in _one of (DWR) 333 ₁ to search bit event data by _{(B 2 = "1")} (I) At the same time as instructing the search, “1” is added to the count value (C ₂ ) of the search key file 37 corresponding to the search key (K ₂ ).

[0096] DB write and read unit (DWR) 333 ₁ is by a process similar to that described above, the read subject data base (DB)
After selecting [for example, 34 ₁ ], based on an instruction from the search key file management unit (KFM) 354, a search of the event data (I) by the search bit (B ₂ = “1”) is executed, and the search bit ( Event data (I ₁ ) and (I ₂ ) to which B ₂ = “1” is added are detected.

[0097] control notification unit 33 ₁ sends back the detected event data (I ₁₎ and (I _2), via a control reception unit 32 to the search request source of the monitoring device 4. Hereinafter Similarly, the count value of each time a search request is to occur using the search key from the monitor 4 (K ₁₎ or (K _2), the search of the search key file 37 keys (K ₁₎ or (K ₂₎ ( “1” is added to C ₁ ) or (C ₂ ).

The monitoring device 4 sends the search key file 3
7, when a search request using a search key (K) [eg, (M ₁ = "0")] other than the search key (K ₁ ) and (K ₂ ) is generated, the DB access management unit The search key file management unit (KFM) 354 in the server 35 analyzes the search conditions of the search request to be executed this time, and searches the search key file 3
When it is identified that the search key (K) is not registered in 7,
DB write and read portions of the control notification section 33 in ₁ (DWR) 333
₁ , the same search as that of the conventional log management apparatus 3 (see FIG. 12) is instructed, and the unregistered search key (K _N1 ) is stored in the unregistered search key file 371 of the search key file 37.
And adds “1” to the _count value (C _N1 = “0”) corresponding to the registered unregistered search key (K _N1 ).

[0099] DB write and read unit (DWR) 333 ₁ is by a process similar to that described above, the read subject data base (DB)
After selecting the [eg 34 _1], based on an instruction from the search key file management unit (KFM) 354, a database (DB) 34 unregistered search key for ₁ [K _N1 = (M ₁
= “0”)], and receives event data (I ₁ ) and (I ₂ ) satisfying the unregistered search key (K _N1 ).

[0100] control notification unit 33 ₁ sends back the detected event data (I ₁₎ and (I _2), via a control reception unit 32 to the search request source of the monitoring device 4. Similarly, an unregistered search key (K _N2 ) [= (M ₁ ≧ “2”)],
(K _N3 ) [= (M ₂ = "0"], (K _N4 ) [= (M ₂ ≧
“1”)], (K _N5 ) [= (M ₃ ≦ “3”)],
_Every time a new search request for event data (I) using (K _N6 ) [= (M ₃ = "0")] is newly generated from the monitoring device 4, an unregistered search key file in the search key file 37 371 are sequentially registered and the corresponding count value (C
_N2 = "0") to (C _N2 = "0") to "1" is added.

The same search key (K) as the unregistered search key (K _N ) registered in the unregistered search key file 371
Search request with is when arising from the monitoring device 4, the search key file management unit (KFM) 354, similar to the above, DB write and read portions of the control notification section 33 in ₁ (DW
R) 333 _1, and instructs the search similar to the log management device 3 in the conventional [see FIG. 12], the unregistered search key file 371, the corresponding count value corresponding to the registered search key (K _N) ( Add “1” to C _N ). [FIG. 8B, Second Stage] The search key file management unit (KFM) 354 calculates the count value (C ₁ ) of each of the search keys (K ₁ ) and (K ₂ ) registered in the search key file 37. And (C ₂ ), the number of unregistered search keys (K _N ) registered in the unregistered search key file 371, and the count value (C _N ) corresponding to each unregistered search key (K _N ) The total of the number of search keys (K) registered in the search key file 37 and the number of unregistered search keys (K _N ) registered in the unregistered search key file 371 is predetermined. Number (for example, “8”), or when each count value (C ₁ )
When it is detected that the maximum value of (C ₂ ) and (C _N1 ) to (C _N6 ) has reached a predetermined limit value [for example, “10”, the search registered in the search key file 37 is performed. The keys (K ₁ ) and (K ₂ ) and the unregistered search keys (K _N1 ) to (K _N6 ) registered in the unregistered search key file 371
Are arranged in descending order of the count value (C) or (C _N ), and the search keys (K) or unregistered search keys (K _N ) up to the “4” th from the beginning are replaced with new search keys (K ₁₎ ) To (K ₄ )
And registered in the search key file 37 as the “5” th to “8” th search keys (K) or unregistered search keys (K
Cancel the _N) from the search key file 37 and unregistered search key file 371, further count (C ₁₎ to each search key (K ₁₎ to (K ₄₎ a (C ₄₎ to all "0" Update.

Each search key (K) shown in FIG.₁),
(K_Two) And unregistered search key (K _N1) Through (K_N6)
Each corresponding count value (C₁), (C_Two) And (C
_N1) Through (C_N6), The search key (K₁) [Count value
(C₁= “10”)], an unregistered search key (K_N2) [Count
Value (C_N2= “6”)], an unregistered search key (K_N3) [Count
Value (C_N3= “5”)] and an unregistered search key (K_N6)
[Count value (C_N2= “3”)] is the new search key
(K₁) Through (K_Four) Registered as a search key
(K_Two) [Count value (C_Two= “2”)], unregistered search key
(K_N1) [Count value (C_N1= "1")], unregistered search key
(K_N4) [Count value (C_N4= "1")] and unregistered search
Key (K_N5) [Count value (C_N5= "1")] is deleted
It will be. [FIG. 9 (c), third stage] Subsequently, the search key file management unit (KFM) 354
Database (DB) 34₁And 34_TwoEach of the
Search bit added to vent data (I)
(B₁) Through (B)_Four) Is added to the search key file 37.
Search key (K₁) Through (K_Four)
Update.

[0103] for example a database (DB) 34, the event data (I ₁₎ and (I ₂₎ only to the already stored event data (I _1), the search key (K _1),
Since (K ₂ ) and (K ₃ ) are satisfied and the search key (K ₄ ) is not satisfied, the search bits (B ₁ = "1") added to the event data (I ₁ ), (B ₂ =
_{"1"), (B 3} = "0") and (B ₄ = "0")
With search bits (B ₁ = “1”), (B ₂ = “1”),
The settings are changed to (B ₃ = "1") and (B ₄ = "0"), and the event data (I ₂ ) is changed to the search key (K ₂ ).
And (K ₃ ) are satisfied, and the search keys (K ₁ ) and (K
₄ ), the search bits (B ₁ = "0") and (B ₂ = 0) added to the event data (I ₂ ) are not satisfied.
_{"1"), (B 3} = "0") and (B ₄ = "0")
With search bits (B ₁ = "0"), (B ₂ = "1"),
Change the setting to (B ₃ = “1”) and (B ₄ = “0”).

Thereafter, each search request generated from the monitoring device 4
In response, the search key file management unit (KFM) 354
The registered search key is referred to the server search key file 37.
(K ₁) Through (K_FourThe search request using
(B₁) Through (B)_Four) To the DB write / read unit (D
WR) 333 and the count value (C₁) Through
(C_Four) And search using an unregistered search key (K).
The search request instructs a search by the database (DB) 34
At the same time, the unregistered search key file
Search key (K_N) And count value (C_N)
to add.

Eventually, the total value of the search key (K) registered in the search key file 37 and the unregistered search key (K _N ) registered in the unregistered search key file 371 becomes a predetermined number [8 in the previous example. ”], Or the count value (C) of each search key (K), or an unregistered search key (K _N )
When the count value (C _N ) of the search key exceeds a predetermined value (“10” in the previous example), each search key (K) or unregistered search key (K
Compared _N) of the count value of the (C) or (C _N), registers the search key file 37 by the count value (C) or (C _N) with many search key (K) or unregistered search key (K _N) change.

As is clear from the above description, the present invention (contract
According to the embodiment of the claims 4 and 5),
Used for search request of event data (I) to be performed
Of the key (K), a predetermined number frequently used (in the previous example,
"4" key] is registered in the search key file 37, and the data
Each event data stored in the base (DB) 34
(I) shows whether the registered search key (K) is satisfied or not.
Search bit (B₁) Through (B) _Four) Is added and the registered inspection
When a search request specifying the search key (K) occurs,
Relevant search key added to each event data (I)
Searching by search bit (B) corresponding to (K)
Event data that can be satisfied by a single search
(I) can be detected, and the search time can be reduced.

FIGS. 2 to 9 are only one embodiment of the present invention, and for example, the event data (I), the possession attribute (M), and the search key (K) which are the objects of the present invention are exemplified. However, the present invention is not limited to this, and many other modifications are considered, but the effect of the present invention does not change in any case. The configuration of the log management device 3 to which the present invention is applied is not limited to the configuration shown in FIG. 2. For example, the log management device 3 according to the embodiment of the present invention (claims 4 and 5) Many other modifications are considered, such as including a control notification unit and a database (DB), but the effect of the present invention does not change in any case. Further, it goes without saying that the database system to which the present invention is applied is not limited to the transmission device monitoring system shown in FIG.

[0108]

As described above, according to the present invention (claims 1 to 3), data can be written / read in parallel to two sets of databases each storing the same storage data. The read data can always incorporate the latest update contents, and write / read requests for a plurality of types of data can be executed in parallel to a set of databases. According to (5) and (5), data that satisfies the search request condition can be quickly detected, and the convenience of the database system is greatly improved.

[Brief description of the drawings]

FIG. 1 is a principle diagram of the present invention.

FIG. 2 is a log management device according to an embodiment of the present invention.

FIG. 3 is a signal sequence according to an embodiment of the present invention (claim 1);

FIG. 4 shows the setting status of various flags in FIG.

FIG. 5 is a signal sequence according to an embodiment of the present invention (claim 2);

FIG. 6 shows the setting status of various flags in FIG.

FIG. 7 shows a data write / read situation according to an embodiment of the present invention (claim 3).

FIG. 8 shows a data retrieval situation (part 1) according to the embodiment of the present invention (claims 4 and 5).

FIG. 9 is a data retrieval status (part 2) according to the embodiment of the present invention (claims 4 and 5);

FIG. 10 is a transmission device monitoring system according to the present invention.

FIG. 11 shows a conventional log management device.

FIG. 12 is a database search function in FIG. 11;

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 transmission system 2 transmission device 3 log management device 4 monitoring device 31 notification reception unit 32 control reception unit 33 control notification unit 34, 100, 200 database (DB) 35 DB access management unit 36 difference buffer 37 search key file 101 database management unit 102 Writing / reading means 103 Update contents storage means 104 Storage data matching means 201 Search condition registration means 202 Search means 311, 321 Usage status check section (BFC) 312, 322 Function selection inquiry section (FSA) 313 Write request Section (IWR) 323 read / write request section (RWR) 324 read result notification section (RDS) 331 DB access flag check section (DFC) 332 buffer write / read section (BWR) 333 DB write / read section (DWR) 334 data Synthesizer (DCM) 341 DB Search unit 342 DB storage unit 343 Partial database (SDB) 351 Buffer reading unit (DDR) 352 DB difference writing unit (DDW) 353 Usage status flag release unit (BFR) 354 Search key file management unit (KFM) 371 Unregistered search Key file

Continuation of the front page (72) Inventor Tsuyoshi Naka 3-1-1 Hirooka, Kanazawa-shi, Ishikawa Prefecture Inside Fujitsu Hokuriku Communication System Co., Ltd. (72) Yuko Yokota 3-1-1 Hirooka, Kanazawa-shi, Ishikawa Fujitsu Hokuriku Communication In System Co., Ltd. (72) Inventor Masayuki Hasegawa 3-1-1 Hirooka, Kanazawa City, Ishikawa Prefecture F-term in Fujitsu Hokuriku Communication System Co., Ltd. 5B075 KK04 PP23 PR08 QR01 QS06 QT06 5B082 AA00 CA05 CA18 DC09 DE04 EA05 FA11 FA16 GA04 GA14 GB02 GB06 HA08

Claims (5)

[Claims] 1. A database system for receiving write / read requests for data generated as needed from a plurality of request sources and writing or reading the data to / from a database, comprising: two sets of databases each storing the same data; Database management means for managing the writing / reading state of each database; and when a writing / reading request for the database is generated, referring to the database management means to execute writing / reading on any free database. Writing / reading means; update data storage means for temporarily storing the update content when data stored in one database is updated; and updating content storage means after the update to the one database is completed. Based on the stored update content, the one data is stored in the other database. Database management system, characterized by providing the stored data match means that performs the same update processing as performed on the base of the stored data. 2. The read / write unit reads data from one of the databases and then reads update contents stored in the update content storage unit, and reads the data read from the one database and the update data. 2. The database management system according to claim 1, wherein read data including the latest update content is synthesized by comparing the update content read from the content storage means. 3. The database is divided and managed for each data type, and a plurality of threads are provided in the writing / reading means so that writing / reading for each type can be executed in parallel. 2. The database management system according to claim 1, wherein: 4. A database system for receiving a data search request generated from a request source and reading the corresponding data from a database, comprising: a database storing data having a plurality of attributes; Search condition registering means for preliminarily registering a search condition for searching for data in which each attribute satisfies a required condition, and when the data is written in the database, the search condition is registered in the search condition registering means. From among the search conditions, information for identifying a search condition that satisfies the data is added, and when a search request with a search condition registered in the search condition registration unit occurs, each search condition stored in the database is added. By referring to the search condition identification information added to the data, data satisfying the search condition added to the search request can be obtained. A database management system comprising: a search unit for detecting. 5. The search condition registering means, when a search request with an unregistered search condition occurs, stores the unregistered search condition, and stores each of the registered search conditions in the search condition registering means. The frequency of use of the search condition and the frequency of use of each unregistered search condition being held are counted for each of the search conditions, and the frequency of use of each of the registered search conditions and each of the unregistered search conditions is compared later. Only a predetermined number of search conditions are newly registered and changed in descending order of frequency, and the search means is added to each data stored in the database based on the search conditions registered and changed in the search condition registration means. 5. The database management system according to claim 4, wherein said search condition identification information is updated.