KR970011854B1 - Relation data processing method of distribution dbms system - Google Patents

Abstract

The relation-based data change checking method for a distributed database system is directed to checking a normal database change by designating a certain database information and providing a periodic checking function. The checking method includes a first step(20 and 21) for changing to a ready state for receiving an operator instruction, a second step(22, 23, and 30) for performing a corresponding instruction when a database relation information output is requested and changing to the ready state, and a third step(24, 25 and 30) for performing a corresponding instruction when a certain relation checking is requested, and a fifth step(28, 29 and 30) for performing a corresponding instruction when a check performing stop instruction is received.

Description

How to monitor data change by relation in distributed database system

1 is a system structural diagram to which the present invention is applied;

2 is a flowchart of main processing for monitoring relation data changes;

3 is a detailed processing flowchart for outputting relation information;

4 is a detailed processing flowchart for monitoring in relation units;

5 is a detailed processing flowchart for analyzing monitoring result information;

6 is a detailed processing flowchart for performing relation monitoring in each processor;

7 is a detailed processing flowchart for outputting monitoring information;

8 is a detailed processing flowchart for stopping monitoring execution.

* Explanation of symbols for main parts of the drawings

1: Analog Subscriber Service Subsystem

2: Digital Subscriber Service Subsystem

3: trunk line service subsystem

4: interconnect network subsystem

5: central control subsystem

According to the present invention, random database information is assigned to information that is changed during operation except for permanent information, which is not changed after initial mounting, to give periodic monitoring function. Distributed database system that can be checked by outputting data before and after the change at the closest point of time to monitor whether normal database changes are made, and to normally change the database information distributed and accommodated in the system It relates to a data change monitoring method for each relation in.

In the conventional data monitoring function, the data monitoring function detects the case where any attribute of a specific relation is changed to a value out of the range specified in advance by periodic monitoring while operating the system, and outputs the necessary error information. The function changes to the initial value information and ends.

Accordingly, the conventional method for monitoring data change by relation in a distributed database system according to the related art has a problem in that a program must be changed to perform a monitoring function for an attribute to be added when new information is added.

In order to solve the above problems, the present invention receives information for monitoring whether a relation of a database is changed by an operator's request, and transmits information for monitoring request to a processor in which the database is mounted. The monitoring function in each processor reads the data at the required monitoring interval for the requested database and checks whether the change has occurred, and if it is changed, transmits the information before and after the change to the control function and outputs it through the operator matching function. For this purpose, it is classified into a set form that gives an integer, a character, and a meaning of data according to the type of data. In the case of a character and a set form, all relations can be output to output meaningful character information indicated by the information. To manage configuration information. It provides information by using other, and it is possible to extend the range of the requested key value through one command for the convenience of monitoring function, and to output and stop the information during the monitoring function through the operator's command. The purpose of the present invention is to provide a method for monitoring data change by relations in a distributed database system.

The present invention devised to achieve the above object, the present invention, an access switching subsystem (ASS-S) including an access switching processor (ASP) and a digital subscriber service subsystem (ASS-I: Access) Interconnection Network Subsystem (INS) including Switching Subsystem-ISDN and Access Switching Subsystem-Trunk (ASS-T), Number Translation Processor (NTP) and Internal Network Processor (INP), Central Processor Subsystem (CCS), including the Operation and Maintenance Processor (OMP) and Input / Output Control Processor (MMP), and the Inter Processor Communication (IPC), which establishes the communication path between the processors mounted in each subsystem. In a data change monitoring method applied to a distributed database system provided, the input / output control processor (MMP) is configured by an operating system It is the first step to enter the standby state for receiving the operator instructions; A second step of performing a corresponding command when requesting to output database relation information after performing the first step, and switching to the standby state to receive a next command; A third step of performing a corresponding command and transitioning to the standby state when the monitoring of any relation is requested after performing the first step; A fourth step of performing a corresponding command and transitioning to the standby state if a request for outputting monitoring execution information is requested to confirm the monitoring execution state after performing the first step; And a fifth step of performing a corresponding command and switching to the standby state after receiving the monitoring execution stop command for stopping the monitoring execution after performing the first step.

Hereinafter, with reference to the accompanying drawings will be described an embodiment according to the present invention;

FIG. 1 is a system architecture diagram to which the present invention is applied, and includes an Access Switching Subsystem-Subscriber (ASS-S) 1 and an Access Switching Subsystem-ISDN (ASS-I) ( 2) and the trunk switching service subsystem (ASS-T) (3), the Interconnection Network Subsystem (INS) (4), which controls number translation and switch connections, and a functional hierarchy. A central control subsystem (CCS) (5), which collects and analyzes failure and status information for each subsystem and finally manages overall operation management and maintenance functions such as command processing by an operator's request, is provided. Processors mounted in the subsystems exchange information using an Inter Processor Communication (IPC) 6 communication path. In addition, the operation and maintenance processor (OMP), the input / output control processor (MMP), the access exchange processor (ASP), the number translation processor (NTP), and the internal connection network processor (INP) distributed to each subsystem are distributed to the upper processor (MP). Main Processor is responsible for resource information management, operator message processing, database management and call processing control. The function proposed by the present invention receives information input from the operator matching function in the SSDH (hereinafter referred to as "SSDH") 7 mounted in the input / output control processor (MMP), and each higher processor in the distributed subsystem. Data monitoring is performed through a DBSH (Database Sypervision Hander) implemented in (MP) (hereinafter referred to as “DBSH”) block 8. In operation, management is performed by interworking between SSDH 7 and DBSH 8. The status information of the monitoring function is used to check or stop the information being performed.

2 is a flowchart of a main control process for monitoring relation data change, and illustrates a procedure of performing detailed functions configured in units of processors in response to an operator's request in a main control function mounted in an input / output control processor (MMP). The SSDH 7 is driven by the operating system at the completion time of restarting the input / output control processor MMP (20) and transitions to a standby state for receiving an operator command (21). Requesting the output of information about the database relation (22) creates a process for processing the instruction (23) and transitions to the wait state for receiving the next instruction (30). When a watch function is requested for an arbitrary relation (24), a process for processing a corresponding instruction is created (25) and the state transitions to a waiting state for receiving the next instruction (30). When the monitoring information output is requested to check the status of the function being monitored (26), a process for processing the corresponding command is generated (27), and the state is switched to the waiting state for receiving the next command (30). Upon receiving the monitoring execution stop command for stopping the monitoring execution function (28), a process for processing the command is generated (29) and the state is switched to the standby state for receiving the next command (30).

FIG. 3 is a detailed process flow chart for outputting relation information. In FIG. 2, a process flow process 23 for outputting relation information according to an operator's request is shown.

Driven by the main control function (31) and the process is classified according to the output type requested by the operator (32). When requested as a relation number, information about the requested relation is read from the information about the entire relation using the relation number (33) .If requested as a relation name, information about the requested relation is read using the relation name. (34). The result of the read relation is analyzed (35) to output the output message to a relation that does not exist and does not exist (36) and to terminate (37). (38) End (39). If the result of the read relation is normal, the database information is read to extract the number of attributes belonging to the relation (40), and the result of the read attribute is analyzed (41). (42) exit (43), if the result of the read attribute is normal (44), store the relation information (44) and use the serial number of the attribute belonging to the relation to read the name of the attribute and how to organize the data (45). If the processing status of an attribute is checked (46), and if the processing of all attributes is not completed, the serial number is updated to read the information of the next attribute (47), and the information reading of the attribute (45) is repeated. If the state is complete, the stored relation and configuration information for each attribute are output (48) and terminated (49). If you require the output of information about the entire relation, prepare to read the information about the first relation (50), read the relation information from the database (51), and then analyze the results of the read relation (52) to access the database. If it is an error, it outputs database error information (53) and exits (54). If the result of the read relation is normal (55), it stores the relation name and number (55) and checks whether it is the last relation (56) and processes the entire relation. If is not completed, the relation read process is repeated sequentially for the next relation (57). If the processing for the whole is completed, the stored result information output is requested (58) and ends (59).

FIG. 4 is a detailed process flowchart for monitoring in relation units, and in FIG. 2, a detailed flowchart of a process generating process 25 for performing a monitoring function for a specific relation according to an operator's request.

It is driven by the main control function (61), and reads information about the relation from the database using the number of the input relation (62). It analyzes the result of reading (63) and outputs error information about undefined relations when there is no information (66) and exits (67), and outputs database error information if it is an error on database access (64). It ends (65). If the processing is successful, read the number of attributes of the attribute (68), set the serial number to read the first attribute (69), read the information about the attribute, and store the necessary information in the buffer (70). After checking the processing status of the entire attribute (71), if it is not complete, update the serial number for the next attribute (72) and repeat the attribute reading process. The process transfers to the monitoring execution function which is commonly installed in the processor (73), registers the time for waiting for the response (73), and switches to the response waiting state (75). If there is no response from the monitoring function performed in the corresponding processor within the response waiting time, a result message by the timeout processing 76 is output (77) and terminated (78). When a response is received (79), an analysis of the result of the reception is requested (80), the completion of all processing is checked (81), and when completed, the entire execution completion information is output (82) and the termination (83), If it is not completed, it registers a response waiting timer for receiving the next result (84) and transitions to the response waiting state (85). In response to the monitoring execution start response information 112 being received during the execution of the monitoring function described in FIG. 6 (86), the information is stored in the corresponding execution status buffer (87) and the state transitions to the response waiting state (88). . The stored information is used in the process of outputting the execution status information described in FIG. 7 and in the process of stopping the monitoring function being performed described in FIG.

FIG. 5 is a detailed process flow chart for analyzing the monitoring result information. FIG. 4 is a detailed flowchart of a process 80 of receiving information about a change from the monitoring function and performing analysis on information in which the change has occurred in an attribute unit. .

The received result is stored in the corresponding buffer (91), the data type is analyzed in attribute units belonging to the relation (92), and if it is an integer, the value before the change is written to the output buffer (93) and the value after the change is written to the output buffer. After recording (94), compare the values before and after the change (95). If the comparison value is different, mark the attribute as the change occurred (96), and if it is a character, write the value before the change to the output buffer (97). Write the value after the change to the output buffer (98) and compare the string information before and after the change (99) .If the string information is different, it is marked as the attribute where the change occurred (100) and is defined as a SET variable. In this case, the database is read to find the variable name for the value before the change (101), the pre-change value is written to the output buffer (102), and the database is read (103) to find the variable name for the value after the change. Variable name After the information is written into the output buffer (104), the value before and after the change is compared (105). If the comparison value is different, the change is indicated as an attribute (106). After checking the processing status for the entire attribute (107), if it is not complete, update the serial number for the next attribute, repeating the attribute analysis process (108), and if so, request the output of the information stored in the output buffer. (109) End (110).

FIG. 6 is a detailed process flow diagram for performing relation monitoring in each processor. In FIG. 4, in operation relation monitoring of FIG. 4, information of a process 73 for transmitting information about a relation and an attribute is received 111 and monitoring is performed. After responding to the start information reception result (112), the timer information for the monitoring execution period is registered (113), and the state is switched to the execution standby state (114). When the monitoring execution stop information is received in the standby state (115), the execution stop completion information is responded to (116) and ends (117). When the timer for the watchdog cycles out, it reads the database (119) and checks whether it is the number of first attempts (120). In the first case, it reads the read value into a buffer that stores the value before the change (121). If the number of times of monitoring is checked (122), if it is once, the read information is transmitted as it is (123) and the process ends (124). If the number of monitoring is one or more times, the total number of execution request monitoring is checked (129), and if completed, all processing completion information is transmitted (130) and terminated (131). If the entire monitoring function is not completed, the next monitoring is performed. A timer for execution is registered (132) and the state transitions to a waiting state (133). If it is not performed for the first monitoring period, the current read value is stored (125) and the value before and after the change is checked (126). Otherwise, the information before and after the change is transferred to the monitoring execution control function. In operation 127, the current read value is transferred to the changed buffer (128), and then the entire process completion determination process 129 is performed.

7 is a detailed processing flow chart for outputting monitoring information, which is a detailed flowchart of a process generating process 27 for outputting information performing monitoring function according to an operator's request in FIG.

It is driven by the main control function (141), sets the first execution status buffer information (142), reads the information of the execution status buffer (143), checks whether it is running (144), and if so, the contents in the result buffer. After saving the data (145), if the status is not running, check the processing completion status (146). If the status is not completed, update the information to read the information about the next buffer (147) to read the information of the execution status buffer. The process is repeated, and if it is completed, the result information is output (148) and ends (149).

FIG. 8 is a detailed process flow chart for stopping monitoring execution. FIG. 8 is a detailed flowchart of a process generation process 29 for stopping monitoring performance according to an operator's request in FIG.

It is driven by the main control function (151), reads the buffer information for the requested execution number (152) and checks whether it is being executed (153), and outputs the result information indicating that it is not being executed. In step 154, the controller transmits a monitoring stop request to the monitoring execution function (156), registers a timer for waiting for response (157), and then transitions to the waiting state (158). If the timer is out without a response (159) and outputs a result of no response (160) and terminates (161), and receives a response to stop monitoring function execution (162), the corresponding information is deleted from the monitoring execution status buffer. After outputting the result of the monitoring execution stop (163) and ending (164).

[Table 1] shows the configuration of the command input by the operator and the output form of the processing result message in the detailed processing flowchart for outputting the relation information described in FIG. In this case, the input information may be given by the relation number 1-1 or the relation name 1-2, or when omitted, the information is processed as information output for the entire relation. The output message is classified into a request for a specific relation and a request for the whole, and in the case of a request for a relation, the serial number (1-3), name (1-4) and data of the relation Relation type information (1-5) indicating memory or disk resident, position information (1-6) indicating how data information of a relation is mounted on each processor, and information (1-7) indicating a processor on which a corresponding relation is mounted Information about the processor (1-8) that can be read by other processors, the serial number (1-9) of the attribute belonging to the relation, the name of the attribute (1-10), how to find the key (1-11), and Data configuration forms 1-12. When the output request for the entire relation is made, only the information about the relation name (1-13) and the number (1-14) is outputted.

TABLE 1

[Table 2] shows the configuration of the operator command and the result message for requesting the execution of the relation unit monitoring function described in FIG. As the input contents, the relation number (2-1), the target processor (2-2) where the monitoring function is performed, the monitoring execution period (2-3), the number of monitoring executions (2-4), and the key value to be read according to the relation Since the number can be configured differently, one (2-5) to two (2-6), up to three (2-7) key values can be given, and up to 10 based on the given key value And a range value (2-8) to request to perform the monitoring function. The configuration of the output message includes the name (2-9) of the relation and the information (2-10) informing the reception of the execution as the result information, in addition to the output of the input information, the information indicating the beginning of the execution of the monitoring function. In the event that data changes occur during the monitoring process, the serial number of the attribute (2-11), the name of the attribute (2-12), the value of the attribute before the change (2-13), and the current An attribute value (2-14) and a portion (2-15) indicating whether a change has occurred, wherein the type of data to be output is numeric information (2-16) if it is an integer and a string form (if it is a character). 2-17) In the case of a set, the name of the set variable (2-18) and the bit information are output as a hexadecimal integer (2-19).

TABLE 2

[Table 3] is a configuration of a command configuration and an output message for outputting the monitoring information described in FIG. 7 as follows. The number (3-1) of the function being performed may be specified or the output of information about the whole may be requested. When requested by the execution number, only the information being executed for the number is output, and the output includes the information input when the execution request is made in [Table 2] (3-2). 3-3) is output together, and when requesting the whole, information about all the functions being executed is output in the order of registration (3-4).

TABLE 3

[Table 4] shows the configuration of command and output message to stop the monitoring function described in FIG. [Table 4] should be entered using the execution number identified through the output function described in [Table 3] (4-1). The outputted message is outputted as it is until now (4-2) to confirm and terminate.

TABLE 4

[Table 5] is requested to perform the monitoring function described in FIG. 4, and stores and manages the performance information in conjunction with the monitoring function described in FIG. 6, and outputs the information output of the monitoring function being performed in FIG. 7 and FIG. Shown are the components for managing information for handling pauses. The management element of the information about the processor that is commonly installed in each processor and performs the monitoring function is the number of the processor (5-1) in accordance with FIG. 6, and the execution of the operation according to the monitoring request of the operator. The processor number corresponding to the number 5-2, the flag indicating that it is being executed (5-3), the counter indicating the number of monitoring performed so far (5-4), the monitoring period (5-5), the number of monitoring (5) -6), the function number (5-7), relation number (5-8), start key value (5-9), key value range (5-10) and relation name (5-11) received from the operator matching function. It is configured to enable simultaneous execution of up to 100 (5-12) systems as a whole for the above information. In the above description, the range of key values (5-10) is the object of monitoring the relation if the range of the added values from the start key value (5-9) is omitted. You lose.

TABLE 5

The present invention is a method for outputting the value before and after the change including the entire contents when there is an attribute that is changed in relation units, or in another embodiment, when the operator requests and changes in each attribute unit by subdividing relations. This can be applied by printing the content immediately after the change to the attribute.

Therefore, the present invention as described above can be applied to a relation consisting of all databases mounted on each distributed processor as a target, so whether or not the normal processing of the database update information generated in the functional processing in the initial system development process It can be verified to ensure the reliability of the system, and it is possible to register and monitor the database information updated at the start and end of a function for a specific function unit at the same processor and another processor at the same time. There is an effect that can be easily identified.

Claims (12)

An access switching subsystem (ASS-S) including an access exchange processor (ASP) (1) and a digital subscriber service subsystem (ASS-I) (2); Access Switching Subsystem-Trunk (ASS-T) (3), Interconnection Network Subsystem (INS) including Number Translation and Switch (NTP) and Internal Network Processor (INP) Central Control Subsystem (CCS) (5), which includes an Operational and Maintenance Processor (OMP) and an Input / Output Control Processor (MMP), and an IPC (Interface) that establishes the communication path between the processors mounted in each subsystem. A data change monitoring method applied to a distributed database system having a processor communication (6), wherein the input / output control processor (MMP) is driven by an operating system to receive operator instructions. The first step (20,21) to switch to a standby state; A second step (22, 23, 30) of performing a corresponding command when requesting to output database relation information after performing the first step (20, 21) and switching to the standby state to receive the next command; A third step (24, 25, 30) of performing a corresponding command and transitioning to the standby state when the monitoring of any relation is requested after the first step is performed; A fourth step (26, 27, 30) of performing a corresponding command and transitioning to the standby state when requesting the output of the monitoring performance information in order to confirm the monitoring execution status after performing the first steps (20, 21); And a fifth step (28, 29, 30) of performing a corresponding command and transitioning to the standby state when receiving a monitoring execution stop command for stopping monitoring execution after performing the first step (20, 21). A method for monitoring data change by relations in a distributed database system. 2. The method of claim 1, wherein the relation information output process of the second steps (22, 23, 30) comprises: determining (31, 32) an output form requested by an operator after being driven by a main control function; After the above steps 31 and 32, if the output request type is a relation name, the relation information is read from the database using the relation name and the result is analyzed. The attribute information constituting the relation is read from the database and the result is analyzed. (34, 35, 40, 41, 44 to 59), then storing relation information and sequentially reading detailed information about all attributes from the database to construct and output the output information; After performing the steps 31 and 32, if the output request type is a relation number, the relation information is read from the database using the relation number, and the result is analyzed. The attribute information constituting the relation is read from the database and the result is analyzed. (33, 35, 40, 41, 44 to 49) storing the relation information and sequentially reading detailed information about all attributes from the database to construct and output the output information; And (50, 51, 52, 55 to 59), if the output request form is the entire relation and then reads information about each relation in order to configure and output the output information and ends. A method for monitoring data change by relations in a distributed database system comprising: a. The method of claim 2, wherein the relation information output command input by the operator includes a relation number (1-1) or a relation name (1-2) as a component, and the output message is requested as a component in relation units. Contains the serial number of the relation (1-3), the name of the relation (1-4), the relation type information (1-5), the relation position information (1-6), and information indicating the processor on which the relation is implemented (1-7). ), The processor's information (1-8) that can be read by other processors, the serial number of the attribute in the relation (1-9), the name of the attribute in the relation (1-10), and how to find the key (1-11). And a data configuration form (1-12) of the attribute, and a distributed database system including a relation name (1-13) and a relation number (1-14) when requesting output for the entire relation. Data change monitoring room in relation . The relation monitoring process of the third step (24, 25, 30), when driven by the main control function, the relation information is read and analyzed using the relation number to determine the number of attributes belonging to the relation. Acquiring the entire attribute information, and then transmitting relation and attribute information for performing the monitoring function to the corresponding processor, registering a timer, and transitioning to a response waiting state (61, 62, 63, 68 to 75); After performing the process of transmitting relation and attribute information for performing the monitoring function of the steps 61, 62, 63, 68 to 75 to the corresponding processor, each processor receiving the relation and attribute for performing the monitoring function is monitored. Performing a function of transmitting and monitoring start response information (111 to 133); After performing the steps 61, 62, 63, 68 to 75, if there is no response from the monitoring function performed in the processor within the response time in the response waiting state, outputting the result message by the time-out process and ending (76 to 78); After performing the steps 61, 62, 63, 68 to 75, if a normal response is received from the monitoring function performed on the processor within the response time in the response waiting state, the result of the reception is analyzed and the completion of all processing is checked. Outputting and terminating the complete execution completion information if completed, and if not completed, registering a response waiting timer for receiving the next result and transitioning to the response waiting state (79 to 85); And when the monitoring execution start response information is received in the response waiting state after performing the steps (61, 62, 63, 68 to 75), the execution state is stored in a buffer and the state transitions to the response waiting state (86). To a relational data change monitoring method in a distributed database system. 5. The method of claim 4, wherein the steps 111 to 133 each processor receiving the relation and attribute information for performing the monitoring function of the steps 61, 62, 63, 68 and 75 respond to the monitoring execution start information. And registering with the watch cycle timer and transitioning to the execution standby state (111 to 114); Stopping (115, 116, 117) terminating the monitoring execution and receiving the monitoring execution stop signal in the execution standby state after performing the steps (111 to 114); After performing the steps 111 to 114, if the watch cycle timer is out, determining (188, 119, 120) whether the number of first attempts is read by a corresponding relation; After performing the steps 118, 119, and 120, if the number of first attempts is stored, the value before the change is determined, and the requested number of monitoring is determined. If the number of monitoring is one time, the read information is transmitted and terminated. If the state is completed after checking the state, all processing completion information is transmitted and terminated, and if the state of the entire monitoring function is not completed, registering the monitoring cycle timer for performing the next monitoring and transitioning to the execution standby state (121 to 124). 129 to 133); And after the steps 118, 119, and 120, store the currently read value unless the number of first attempts is compared, and compare the before and after values to transfer the information before and after the change to the monitoring execution control function and buffer before the change. After storing the current value in, check the total number of execution request monitoring times and if it is completed, deliver all processing completion information and terminate. If the entire monitoring function is not completed, register the monitoring cycle timer to perform the next monitoring. In case of transition to the standby state and change of the value before and after occurs, the current value is saved in the buffer before the change and the total execution request monitoring count is checked and if it is completed, all processing completion information is transmitted and terminated. If it is not completed, the watchdog timer is registered and executed for the next watchdog. And a step (125 to 130) of transitioning to a standby state. 5. The method of claim 4, wherein the reception result analyzing process of steps 79 to 85 comprises: classifying the attribute data according to the type after storing the result received from the monitoring function in a corresponding buffer (91,92); After the above steps 91 and 92, the information consisting of the integers is stored in the output buffer before and after the change, and then it is checked whether the change has occurred, and then displayed as a changed attribute only when the change has occurred. Checking the processing status of the entire attribute in, repeating the attribute analysis process by updating the serial number for the next attribute if it is not completed, and requesting and ending the output of the information stored in the output buffer if it is completed. 93 to 96, 107 to 110; After performing the above steps 91 and 92, the information consisting of the characters is stored in the output buffer before and after the change, and the change is checked to indicate that the change has occurred only when the change has occurred. After that, it checks the processing status of the entire attribute and if it is not done, it updates the serial number for the next attribute and repeats the shape analysis process of the attribute, and if it is completed, it requests and outputs the information stored in the output buffer. Steps 97-100, 107-110; After performing the steps 91 and 92, if the type of the attribute data is defined as a SET variable, the database is read to find the variable name for the value before the change, and the value before the change is stored in the output buffer. Read the database to find the variable name for the value after the change, write the information about the variable name to the output buffer, check if the change occurred, mark the attribute as a change only if the change occurred, and then mark the entire attribute. Checking the processing status for and if it is not complete, update the serial number for the next attribute to repeat the shape analysis process of the attribute, and if it is completed, requesting and terminating the output of the information stored in the output buffer (101 to 110). Relation-specific data in a distributed database system comprising: Other change monitoring method. The relation monitoring execution command input by the operator is a component as a relation number (2-1), the target processor (2-2) on which the monitoring function is performed, the monitoring execution period (2-3), monitoring The output message of the information including the number of executions (2-4), the key values (2-5, 2-6, 2-7) and the range value (2-8) of the key, and the start of the monitoring function is displayed. Including the name (2-9) and information (2-10) indicating the receipt of the execution as a result information, and if a change of data occurs in the course of performing the monitoring function, the output message is the serial number of the attribute (2-11). ), The name of the attribute (2-12), the value of the attribute before the change (2-13), the value of the current attribute (2-14), and an indication of the status of the change occurring (2-15) Is a variance deciding including numeric information (2-16), string form (2-17), name of set variable (2-18) and hex integer (2-19). How to change by data from other relational database system monitoring. According to claim 1, wherein the monitoring execution information output process of the steps (26, 27, 30) is driven by the main control function, by checking whether the monitoring is performed by reading the information of the execution status buffer from the first execution status buffer information Repeating the process of storing the contents in the result buffer only when the process is performed until the process is completed (141 to 146); And (146, 148, 149) outputting and terminating the result information if the processing is completed after performing the steps (141 to 146). 9. The monitoring performance information output command input by the operator according to claim 8, wherein the monitoring execution information output command includes the number 3-1 of the function being monitored by the component, and the output message sends the monitoring frequency information 3-3 to the component. A method for monitoring data change by relations in a distributed database system comprising: a. The method of claim 1, wherein the monitoring execution stop step of the steps 28, 29, and 30 is driven by a main control function, and is performed by checking whether the monitoring is being performed after reading the buffer information for the requested execution number. Forwarding a request to stop monitoring execution and transitioning to the response waiting state after registering a timer for waiting for a response (151, 152, 153, 156, 157, 158); Outputting a result of no response (159, 160, 161) when the timer is out without a response within a response waiting time after performing the steps (151, 152, 153, 156, 157, 158); And after performing the steps 151, 152, 153, 156, 157 and 158, if a response is received to stop the execution of the monitoring function, deleting the corresponding information from the monitoring execution status buffer and outputting and ending the result information on the monitoring execution stop (162 to 165). A data change monitoring method for each relation in a distributed database system. 12. The method of claim 10, wherein the stop monitoring execution command input by the operator includes a number (4-1) of a function being monitored as a component. The method of claim 1, wherein the number of the processor (5-1) being executed as a component for managing the monitoring performance information, the number of the processor (5-2) controlling the performance according to the operator's monitoring request, indicating that the execution is being performed. Flag (5-3), counter (5-4) indicating the number of monitoring performed so far, monitoring cycle (5-5), monitoring number (5-6), function number (5-7) received from operator matching function A relation number (5-8), a start key value (5-9), a key value range (5-10), a relation name (5-11), and a system-wide concurrent execution range (5-12). How to monitor data change by relation in distributed database system.