KR100331470B1 - Apparatus and Method for Guaranteeing Integrity of Database in the Switching System - Google Patents

Abstract

The present invention relates to an apparatus and method for guaranteeing the integrity of an exchange database for performing an integrity check for a database change request of an exchange application. The present invention defines a data integrity rule for checking the integrity of a database, and defines the data. It loads and calls the data integrity rule in the form of a common library, and calls the common library in the DBMS and performs an integrity check at the request of the application to control the change that directly causes the database error. Ensure the integrity of the database.

Description

Apparatus and Method for Guaranteeing Integrity of Database in the Switching System}

The present invention relates to an apparatus and method for ensuring database integrity of a switch, and more particularly, to an apparatus and method for guaranteeing database integrity for performing an integrity check on a database change request of an exchange application.

In the existing exchange, there was no integrity check for the change of the database, and the basic check was performed on the data change statement located in the source of the application at the time of application development.

In other words, the exchange application uses CHILL (CCITT High Level Language) as the programming language, and therefore through the Embedded Database Manipulation Language (EDML), a CHILL embedded data manipulation language that allows the database to be accessed by applications written in that CHILL. When compiling an application program, basic checks on data change statements are made. Database changes can be performed through the DBMS. Here, the application program refers to a program excluding the OS (Operating System) and DBMS among the programs operating in the exchange.

Then, the conventional configuration for performing the basic inspection, as shown in Figure 1, consists of a workstation 10, the exchanger 20.

Here, the workstation 10 includes a program development part 11 for developing an application, that is, a development operation up to a performance performing step before compilation, and a corresponding exchanger 20 by performing a compilation operation during a development process of the application. It includes an executable program portion 12 for changing to an executable program of the form.

The switch 20 includes an executable program portion 21, a DBMS 22, and a database 23, which executes an application program from the workstation 10. Receives a request for a database change to the DBMS 22 and receives a database change result from the DBMS 22, the DBMS 22 receives the database change request from the executable program portion 21 receives the database 23 ) And notify the execution program part 21 of the result.

Briefly looking at the operation of the configuration as described above, if the application developer writes a program using EDML, a data access language for data change, after the program is completed, the program is an executable program of the workstation 10 Part 12 undergoes a compilation step.

At this time, the data change statement is checked at the compilation stage. In this case, the data change statement is checked for minimal errors such as whether an error is included in the data change statement and whether it is a proper request within an attribute range to be changed. it means.

Thereafter, the compiled application is loaded into the switch 20, and the database request of the running application is transferred to the DBMS 22, and the database 23 in the DBMS 22 according to the transferred request. Will change.

However, the database is changed by the DBMS that receives the request of the application, and the DBMS accepts the received database change request as it is and changes the database. It is reflected in the DBMS, which causes the inconsistency of the database and affects other applications that access the database, which may cause the exchanger to malfunction and to become out of service.

In addition, it takes a lot of time and manpower to recover the malfunction or service outage of the application due to the inconsistency of the database, resulting in complaints of service users.

In order to solve the problems described above, the present invention can control the change that directly causes the database error by performing data integrity definition, exchange and loading form and integrity check, thereby ensuring the integrity of the database. The purpose is. That is, an object of the present invention is to make it appropriate to ensure the integrity of all changes made to the exchange database through the integrity check on the change request before the data change with respect to the data change request of the exchange application program.

1 is a block diagram showing a configuration for performing a basic inspection when developing a conventional application.

2 is a block diagram illustrating a configuration for performing an exchange database integrity check according to an embodiment of the present invention.

3 is a flowchart illustrating a method of guaranteeing an exchange database integrity according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

30: Workstation

31: relation definition part

32: shared library conversion unit

33: common library 34: loading

40: exchange 41: database

42: application 43: DBMS (Database Management System)

44: common library area

In accordance with an aspect of the present invention, an apparatus for guaranteeing an exchange database integrity according to an embodiment of the present invention includes a database storing data, an application program requesting a change of the database and being notified of the result, and a database of the application program. A relation definition unit for generating and generating relation schemas and data integrity rules according to the relation definition of the exchange application program developer in the exchange including a DBMS for executing a corresponding database change and reporting the result according to the change request; A common library converting unit which compiles the integrity rule generated by the relation definition unit and forms a common library by integrating all the integrity rules of the relation into a common library form; A loading unit which combines the relation schema part generated by the relation definition unit with data and loads the data into the database, and loads the common library formed by the common library converting unit when the exchange program is loaded; And a checker which loads a common library by the loading unit and performs integrity check of the database according to a database change request of the application program through the DBMS and notifies the DBMS of the result.

In addition, according to an embodiment of the present invention for achieving the object as described above, the method for guaranteeing the integrity of the exchange database according to the relation definition of the exchange application program developer in the relation definition unit for the data integrity rules and relation schema for the integrity check of the database; Defining process; Loading the relation schema with data in a loading unit, loading the relation schema into a database, compiling the data integrity rules, and then loading the relation schema into one common library integrating the integrity rules of all relations; Calling the common library area in the DBMS according to the request of the application, and performing the integrity check on the data stored in the database in the corresponding common library area. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

As shown in FIG. 2, an apparatus for guaranteeing database integrity according to an embodiment of the present invention includes a workstation 30 and an exchange 40.

Here, the workstation 30 includes a relation defining unit 31, a shared library converting unit 32, a shared library 33, and a loading unit 34. ) Defines data integrity rules for checking the integrity of the database as well as the relation schema (Schema) used in the own application according to the relation definition of the exchange application developer, and the corresponding common library conversion unit 32 defines the relation After compiling the form of the integrity rule created by the definition unit 31 and forming the common library 33 by integrating the integrity rules of all relations to form the corresponding common library 33, the loading unit 34 defines the relation The relation schema part defined in the section 31 is combined with data to form a database, and the data of the exchange 40 The library 41 is loaded on the base 41 and loaded in the shared library area 44 of the exchanger 40 together with other packages.

The switch 40 includes a database 41, an application program 42, a DBMS 43, and a common library area 44. The database 41 includes the workstation 30. The application 42 requests the DBMS 43 for database changes and is informed of the result from the DBMS 43, and the DBMS 43 receives the application 42. In response to a request for a database change authorized from the call, the corresponding public library area 44 is called and the test result is notified from the corresponding public library area 44 to determine whether the database 41 has been changed and execute the change. The library area 44 is a checker that executes a common library, and loads a common library authorized from the workstation 30, and loads the corresponding DBMS. According to the call of 43, the integrity check of the database 41 is performed, and the result is notified to the DBMS 43.

Referring to the flowchart of FIG. 3, a method for guaranteeing an exchange database integrity according to an exemplary embodiment of the present invention is as follows.

First, when a developer who develops an exchanger application defines a relation, the relation definition unit 31 in the workstation 30 checks the integrity of the relation schema and database used by the application according to the relation definition of the developer. Define a data integrity rule for (step S1). Here, the data integrity rule is information that can guarantee the integrity of an attribute, and indicates the relationship between the attribute and the attribute of another relation, the constraints of the attribute, and the information of the tuple that the attribute should have. The data integrity rules are defined using EDML and C, which are data processing languages.

Accordingly, the relation schema portion defined through the relation definition unit 31 is combined with data by the loading unit 34 of the workstation 30 to form a database, and thus, a main memory portion of the exchange 40. It loads into the database 41 (step S2).

The data integrity rule portion defined through the relation definition unit 31 is a common library conversion unit of the workstation 30 according to a command of a person in charge of producing all packages loaded on the exchanger 40. In (32), the integrity rules of all the attributes are gathered into one common library (33). That is, the common library converting unit 32 compiles the form of the integrity rule created by the relation defining unit 31 and forms the form of one common library integrating the integrity rules of all relations (step S3). At this time, the upper part of the common library 33 created in the third step (S3) has an address for executing each attribute, the next part is the attribute integrity rules.

Accordingly, the common library 33 created in the third step S3 is linked when the DBMS 43 of the exchange 40 is compiled to include the address of each attribute when called. The library 33 is shared library area 44 of the exchanger 40 with other packages, eg exchanger application, OS, DBMS, office data, etc., upon loading of the exchanger program by the loading section 34. (Step S4). At this time, each part of the shared library loaded in the shared library area 44 is in the form of a single executable file, which can be executed alone.

Then, with the operation of the switch 40, the internal application 42 requests the DBMS 43 to change the data (step S5), and the DBMS 43 of the application 42 The common library area 44 is called by request, that is, the DBMS 43 receiving the data change request of the corresponding application program 42 uses the factor inputted at the time of the data change request. The area containing the portion of the whole to be changed in data is called (step S6).

Accordingly, the common library area 44 called by the DBMS 43 has an execution program form for each attribute, and receives the relation, attribute, and tuple information received during the call, and stores the received information in the database 41 of the main memory. The integrity of the data is checked (step S7), and the result is notified to the DBMS 43.

Accordingly, the DBMS 43 receives the test result from the common library area 44, determines whether the database 41 is changed, and executes the change, and then notifies the application program 42 of the result. give.

In other words, in the seventh step S7, it is checked whether the change of data is valid as a result of the integrity check (step S8). If the change of data is not valid in the eighth step S8, that is, the value to be changed. If the integrity rule is not satisfied, the common library area 44 notifies the DBMS 43 of the error, and the DBMS 43 notifies the application 42 of the error so that it can be processed. (Step S9).

On the other hand, if the change of the data in the eighth step (S8) is reasonable, the DBMS 43 executes the change of the database 41 (step S10), and the result is sent to the application program 42. Notify me.

As described above, in the past, the change of the database has changed the database by accepting the change request of the application as it is in the DBMS, but the change causing the error of the database directly by performing the integrity check on the change request of the database according to the present invention. Can control the integrity of the database.

Claims (6)

An exchange that includes a database that stores data, an application that requires the change of the database and is notified of the result, and a DBMS that executes the change of the database according to the database change request of the application and notifies the result. , A relation definition unit that defines and generates a relation schema and data integrity rules according to a relation definition of an exchange application program developer; A common library converting unit which compiles the integrity rule generated by the relation definition unit and forms a common library by integrating all the integrity rules of the relation into a common library form; A loading unit which combines the relation schema part generated by the relation definition unit with data and loads the data into the database, and loads the common library formed by the common library converting unit when the exchange program is loaded; And a checker which loads a common library by the loading unit, and performs an integrity check of the database according to a database change request of the application through the DBMS and notifies the DBMS of the result. Database integrity guarantee device. Defining, in the relation definition unit, a data integrity rule and a relation schema for checking the integrity of the database according to the relation definition of the exchange application program developer; Loading the relation schema with data in a loading unit, loading the relation schema into a database, compiling the data integrity rules, and then loading the relation schema into one common library integrating the integrity rules of all relations; And calling a common library area in a DBMS according to a request of an application, and performing an integrity check on data stored in the database in the public library area. The method of claim 2, The data integrity rule is information that can guarantee the integrity of an attribute. The exchange database integrity characterized by indicating the relationship between the attribute and the attribute of another relation, the constraint of the attribute, and the information of the tuple that the attribute should have. How to Guarantee. The method of claim 2, The common library loading process includes: compiling data integrity rules of all attributes in the loading unit; Integrating the compiled integrity rules of all the relations in the loading unit and generating them into one common library; And loading the generated common library in the common library area of the exchange together with other packages when the exchange program is loaded in the loading unit. The method of claim 2, The performing of the integrity check may include: receiving a database change request from an application program at the DBMS, calling the common library area; Receiving relations, attributes, and tuple information when the DBMS is called in the common library area, and checking integrity of data stored in the database to confirm whether data change is valid; And notifying the DBMS of an error when the data to be changed in the common library area does not satisfy the integrity rule. The method of claim 5, The performing of the integrity check further comprises notifying the DBMS of the result when the data to be changed in the common library area satisfies the integrity rule, and executing the change of the database. How to ensure exchange database integrity.