JPH11203185A - Duplex data base comparison method for transmitter monitoring device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a duplex data base comparison method for a transmitter supervisory arid controlling device capable of more accurately recognizing a non-matching factor when the non-matching of the contents of duplexed data bases is generated. SOLUTION: In duplexed first and second data bases, the date and time attributes 10 of a year, a month, a date and time, etc., are registered as additional attributes 11 in addition to attributes 3 including the name 1 and setting information 2 of a management object 5 and the operation 4 of changeover or the like. Also, the name of the management object for which an operation is performed is time sequentially stored in the operation object name table of a console. When the non-matching of the contents of the first data base and the second data base is generated, the date and time of the previous management objects are successively read from the name of the object name table and the latest date and time of the first and second data bases, both are compared and the normality of the first and second data bases is judged by the newness and oldness of the date and time.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention assigns the date and time to the attribute of a management object to be monitored by a monitoring and control device of a transmission device, and records the name of a managed object that has been operated in a file in a fixed time series. A transmission device monitoring device that reads out and compares the date and time of the corresponding management object contained in both types of DBs based on the operation object name table when a mismatch occurs between two duplexed databases (hereinafter, appropriately referred to as DBs). The present invention relates to a method for comparing duplicated databases in Japan.

[0002]

2. Description of the Related Art In a monitoring and control system for a transmission device,
The DB for storing the management information of the management target is duplicated, and when the operations such as registration and change are performed by the operation unit of the operation console, writing is performed in the first DB and the second DB of the processing unit. As an application example of the DB duplication, for example, Japanese Patent Laid-Open Publication No. H06-348628 discloses that a duplicate service management system on the act side provisionally updates its own master DB in response to a data update request of an access terminal, and then executes a service control point. , A real-time DB update request is transmitted, and when the response is normal, the own master DB is finally updated. Then, it is disclosed that an update request for the backup DB of the standby-side service management system is transmitted, and the update is terminated when the response is normal.

Japanese Patent Application Laid-Open No. 09-198288 discloses that while data is stored in a main DB, data stored in the main DB during a period from a previous copy cycle to a current copy cycle is stored in a copy DB. In a DB multiplexing method of performing regular copying, it is disclosed that when a failure occurs in a device holding a main DB, a duplicate DB is used as a new main DB.

However, in the case of these publications, it is difficult to determine which DB includes a factor causing the mismatch when the storage contents of the DBs of the two systems are mismatched. . In addition, when writing to one of the DBs fails due to a communication error or the like during the writing of the duplicated DB, the storage contents of the first DB and the second DB become inconsistent. Manages the success or failure of writing to the DB. For this reason, when a mismatch occurs, some operation is performed by the operation unit of the operation console, and when a DB mismatch state occurs in each system, it is not possible to determine which DB of which system is normal and how much. However, there is a problem that it is difficult to determine whether maintenance is to be performed in the event of an abnormality.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned conventional problems. When a DB mismatch occurs in one of the duplicated DBs, a certain period of time elapses and some operation is performed. It is an object of the present invention to provide a duplicated DB method in a transmission device monitoring and control system that can more accurately grasp the cause of a DB mismatch even after the above and can determine which system DB is normal. I do.

[0006]

In order to achieve the above object, a duplicate database comparison method in a transmission apparatus monitoring apparatus according to the present invention comprises a predetermined attribute and a date and time attribute of a management object to be managed by a monitoring control apparatus of the transmission apparatus. And the operation are collectively defined as a management object, registered in the first database and the second database, and operated by the operation console when the management object is first registered in the duplicated first and second databases, and The date and time of the date and time attribute are set for each of the management object changes, the names of the management objects operated by the operation console are stored in a file in chronological order, and when the monitoring control device of the transmission device is operated, When the content of the first database and the content of the second database do not match, the file And performing a comparison of both reading the date and time of the sequential previous management object from the date and time of the relevant managed object of the latest of the first database and the second database according Deburu inner.

According to the present invention, the management object is registered in the first database and the second database, and the date and time attribute of the management object is first registered in the first database and the second database and each time the management object is changed. The date and time are set, and the names of the management objects are stored in a file in chronological order. If a mismatch occurs between the contents of the first database and the second database during the operation of the monitoring control device of the transmission device, the latest date and time of the management object registered in the first database and the second database according to the table in the file. From the table and compare them with the date and time of the table to grasp the cause of the mismatch between the first database and the second database.

[0008]

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an embodiment of a method for comparing duplicated databases in a transmission apparatus monitoring and control system according to the present invention. FIG. 1 is an explanatory diagram showing attributes of a managed object applied to the first embodiment of the present invention, and FIG. 2 is an operation console unit and a processing unit in the monitoring control device also applied to the first embodiment. FIG. 4 is an explanatory diagram of a duplicated DB comparison method.

The unit of the device to be monitored, the PKG, the section as the physical transmission path, the path as the logical transmission path, and the like are managed based on object orientation by the monitoring control device of the transmission apparatus. In the first embodiment, FIG. 1 shows attributes of a management object for each monitoring target.
As described above, the attribute 3 including the management object name 1 of the device to be monitored, the setting information 2 such as switching time, and the operation 4 such as switching are collectively determined as the management object 5. As shown in FIG. 2, the data is registered in the duplicated first DB 7 and second DB 8 of the processing unit 6.

[0010] The name 1 and the setting information 2 of the attribute 3 of the management object 5 are the attributes (hereinafter, referred to as the attributes) conventionally used.
Here, in the first embodiment, in addition to the conventional attribute 9, a date and time attribute 10 relating to the date, time, and the like is newly defined and added.
This newly added attribute will be referred to as an additional attribute 11 for simplicity of description. This additional attribute 11 is also registered in the first DB 7 and the second DB 8 together with the conventional attribute 9. Such a management object 5 is referred to as the first
In the case of first registration (generation) in the DB 7 and the second DB 8 and in the case where the operator (not shown) operates the operation unit 13 of the operation console 12 shown in FIG. The date and time are set in the date and time attribute 10.

The name 1 of the management object 5 operated by the operator on the operation unit 13 of the operation console 12 is stored in the operation object name table 14 of the file in chronological order.
That is, the information is sequentially recorded in the order of the operation time. Further, when the contents of the management objects 5 registered in the first DB 7 and the second DB 8 of both systems are inconsistent during the operation of the first DB 7 and the second DB 8, the contents of the first DB 7 and the second DB 8 are confirmed. Object 5 operated by the operator to perform
According to the contents of the operation object name table 14 in the file in which the name 1 of the management object 5 is recorded, the first DB 7 and the second DB 8
The date and time attribute 10 belonging to the corresponding management object 5 is read by the operation of the operation unit 13 by the operator.

The date and time attribute 10 belonging to the management object 5 read from the first DB 7 and the second DB 8 and the contents of the operation object name table 14 are stored in the operation console 1.
The second DB 15 compares the first DB with the new and old date
7. The normality of the second DB 8 is determined. As a result of the comparison by the comparing unit 15, the first DB7, the second DB
When it is determined that there is a mismatch in any one of No. 8, the contents of this mismatch DB are displayed together with the date and time information by a display means (not shown).

Next, the operation of the first embodiment will be described. In the operation console 12, when the operator operates the operation unit 13, the management object 5 to be managed by the monitoring control device is converted into the first D by the processing unit 6.
B7, when registered in the second DB8, the management object 5
Of the management object 5 is recorded in the operation object name table 14 which is a file of the operation console 12 at the same time as setting the date and time at which the writing was performed for the date and time attribute 10. In addition, the first DB7, the second DB
First DB such as change, deletion, etc. of attribute 3 of recorded management object 5, date continuity 10, operation 4, etc.
7. When a change is made on the second DB 8, the date and time attribute 10 is changed for each managed object 5 that has been changed or deleted, and the name is recorded in the operation object name table 14 in the operation console 12. .

Thus, the first DB 7 and the second DB 8
In response to execution of registration of the content of the management object 5,
Attribute 3 of recorded management object 5, date continuity 1
As shown in FIG. 2, each time a change, deletion, or the like of 0, operation 4, or the like is performed, the information is sequentially recorded in the first DB 7 and the second DB 8 and the name is also recorded in the operation object name table 14. An example of registration of the management object 5 in the first DB 7 and the second DB 8 in the processing unit 6 in FIG. 2 is shown. As is clear from FIG.
As the registration of the managed object 5 up to the first time, the contents of the managed object 5 shown in FIG.
As shown in FIG. 2, the first to fourth registration contents are marked with “○” in the figure, and the registration contents of the first DB 7 and the second DB 8 are indicated as shown in FIG. Is constant.

However, in such a recording process, for example, when the management object 5 is registered for the fifth time, the second DB of the content “object5” of the management object 5 is registered.
In the case where the writing to 8 has failed, in FIG.
As indicated by the “x” mark, only the date and time attribute 10 of the content of the management object 5 written in the first DB 7 is switched, and “9” representing 15:03 on September 13, 1997
7.9.13: 15: 03 ”, whereas the date and time attribute of“ object5 ”representing the content of the management object 5 registered in the second DB 8 is 10:13 on September 10, 1997. "97.9.12: 10: 1"
3 ". The date / time attribute 10 registered in the second DB 8 is the same as the date / time attribute 10 of “object4” registered in the second DB 8 at the time of the last fourth registration, “97.12: 10: 10: 10” (minutes). Only the unit is different, there is a difference of 10 minutes and 13 minutes).

From this state, the management object 5 continues.
If the sixth writing of “object6” representing the content of “object6” to the DB7 failed, this date and time attribute 10
"97.9.12: 1" representing 15:12 on September 15, 2008
5:12 ", and the 5th previous" object
"97.13: 15: 03" which is the date and time attribute of "5"
And the date and time are the same and only the minute is the difference between 03 minutes and 12 minutes. On the other hand, the date and time attribute registered in the second DB 8 is normally registered differently from the previous time, and
“97.9.14: 10: 1” representing 10:15 on the 4th
5 "is registered.

As described above, when writing to the first DB 7 or the second DB 8 fails, the first DB 7
And the registered contents of the second DB 8 are in a mismatched state. However, in the conventional management of the mismatch of the DB, the registered contents of the first DB 7 and the second DB 8 are In a different case, after a certain amount of time has passed, it is not known which DB is normal and to what extent it is normal. On the other hand, in the case of the first embodiment, the following operation is performed. Go first DB7
Then, the contents of registration with the second DB 8 are confirmed. That is,
When the operator operates the operation unit 13 of the operation console 12, the name of the management target recorded in the operation object table 14 of the file of the operation console 13 is read and transmitted to the comparison unit 15.

At the same time, the contents of the first DB 7 and the second DB 8 are updated by sequentially operating the contents of the first DB 7 or the second DB 8 which are updated at the latest point in time by operating the operation unit 13. The date and time attribute 10 of the management object 5 in the first DB 7 or the second DB 8 at the time of the mismatch is read out and sent to the comparison unit 15. Thus, the comparing unit 15 compares the name of the management object to be managed read from the operation object table 14 with the content of the date and time attribute 10 of the management object 5 read from the first DB 7 or the second DB 8. If the two do not match as a result of this comparison, the name of the mismatched management object and the date and time attribute 10 are displayed on a display means (not shown). From the contents displayed by the display means, the operator can more accurately grasp which DB has the cause of mismatch due to the operation date and time of the management object.

[0019]

As described above, according to the present invention, the first
The date and time attribute is added to the management object to be managed in the DB and the second DB in addition to the attribute of the name and the setting information and registered, and the operation object name table of the file on the operation console is displayed every time an operation such as a change of the management object is performed. The names of the objects are stored in chronological order, and when the registered contents of the first DB and the second DB do not match,
Since the registered contents of the first DB and the second DB and the name of the operation object name table are sequentially compared from the latest information to the previous information and compared, the normality of the first DB and the second DB is determined according to the new and old date and time. The cause of the discrepancy between the registered contents of the 1DB and the 2nd DB can be grasped more accurately, it is possible to reliably determine which system DB is more normal, and it is effective as a judgment material for maintenance in the event of a DB abnormality. Become.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a duplex D in a transmission device monitoring device according to the present invention.
FIG. 9 is an explanatory diagram of a management object applied in the first embodiment of the B comparison method.

FIG. 2 is a diagram illustrating a duplex D in the transmission apparatus monitoring apparatus according to the present invention;
FIG. 11 is an explanatory diagram of a registration state of a management object in a first DB and a second DB and a storage state of an object name in an operation object name table applied in the first embodiment of the B comparison method.

[Explanation of symbols]

1 ... name 2 ... setting information 3 ... attribute 4 ... operation 5 ... managed object 6 ... processing unit 7 ... 1st DB, 8 ... 2nd DB 9 ... conventional attribute , 10 date and time attribute, 11 additional attribute, 12 operation console,
13 ... operation unit, 14 ... operation object name table, 15 ... comparison unit.

Claims (6)

[Claims] 1. A predetermined attribute, a date and time attribute, and an operation of a management object to be managed by a monitoring control device of a transmission device are collectively defined as a management object and registered in a first database and a second database. Setting the date and time of the date and time attribute each time the management object is first registered in the duplicated first database and the second database by operating with and each time the management object is changed, and the operation is performed on the operation console. The name of the management object is stored in a file in time series, and when the monitoring and control device of the transmission device operates, when the content of the first database and the content of the second database do not match, the latest first database is stored in accordance with the table in the file. And the date and time of the corresponding managed object in the second database A method of comparing duplicated databases in a transmission device monitoring device, wherein the date and time of a previous managed object are sequentially read from the device and the two are compared. 2. The method according to claim 1, wherein the result of the comparison displays date and time information of the mismatch between the first database and the second database on a display unit. 3. The method according to claim 1, wherein the operation is a switching operation. 4. The method according to claim 1, wherein the date and time attribute includes a date and a time. 5. The method according to claim 1, wherein the predetermined attribute includes a name of the management object and setting information. 6. The method according to claim 1, wherein the setting information is a switching time.