KR940007843B1 - Schema managing method on dbms - Google Patents

Abstract

The database schema managing method includes the steps of: if a memory allocation request is received, confirming whether a necessary memory is allocated and transmitting a response; if a schema alteration is requested, altering a schema, generating a log and transmitting a schema alteration completion message; if a schema restoration request is not received, transmitting the generated log and receiving a disk backup completion message; if there is the schema restoration request, restoring the schema to a previous state and transmitting a schema restoration completion message, thereby generating, erasing and altering a relation without stopping a system.

Description

Real-time database management system (DBMS) database schema management method

1 is a structural diagram of a DBMS having a distributed structure configured in an electronic switching system.

2 is a block diagram showing the configuration of the block and the flow of messages related to the present invention.

3 is an overall processing flow diagram of the present invention.

* Explanation of symbols for main parts of the drawings

1: subscriber exchange subsystem (ASS) 2: network subsystem (INS)

3: Central Control Subsystem (CCS) 4: DBMS

5: local database 6: ASP

7: INP 8: NTP

9: OMP 10: MMP

DBSG: Database Support Group Block

DBKG: Database Kernel Group Block

DBBG: Database Backup Group Block

DBQG: Database Query Group Block

The present invention relates to a schema management method of a database, and more particularly, to a database schema management method applied to a real-time database management system (hereinafter referred to as DBMS).

Most existing exchanges do not have a schema management function in the DBMS, so once the exchange data has been produced through the data generator on the host (off-line), new exchanges, deletion of existing data, modification of existing data structures, etc. When the structure of the system data is required to be changed or added due to the change or addition of the exchange function during the operation of the exchange, it is necessary to register new data on the host to create a data file through the data generator, I had to go through the loading process.

However, the above process requires a preliminary work on the host and time accordingly in order to apply a new function to the system, and also has the problem of temporarily stopping the operation of the system for loading the database file.

Therefore, the present invention devised to solve the above problems of the prior art manages the schema of the exchange system database so as to enable the generation, deletion, structural change, etc. of data required through query during operation of the system. The objective is to provide a database schema management method that facilitates the development of functions and enables the continuous service of the system regardless of the addition of functions.

In order to achieve the above object, the present invention provides a database management system (hereinafter referred to as BMS) that is composed of a database support group (hereinafter referred to as DBSG) block and a database kernel group (hereinafter referred to as DBKG) block. Subscriber Switching Subsystem (ASS) with Onboard Processor (ASP), Network Subsystem (INS) with Processor (INP, NTP) with DBMS comprising DBSG and DBKG, DBSG and DBKG And a central control subsystem (CCS) with a processor (0MP) with a DBMS comprising a database backup group (DBBG) block and a processor (MMP) with the DBSG, DBKG, and database query group block (DBQG). In the database schema management method applied to the electronic switch which is composed of; When the memory allocation request for schema creation and modification comes in, the first step is to check whether the required memory can be secured for each requirement and to transmit whether it is available. A second step of generating a log and transmitting a message indicating completion of the schema change; and after performing the second step, if there is no schema recovery request, the generated log is transmitted, and after receiving a disk backup completion message, After performing the third step and the second step, if there is a schema recovery request, the schema is restored to the state before the change to ensure the consistency of the schema, and after the recovery completion message is sent, the fourth step ends. It is characterized by being performed by.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a structural diagram of a DBMS having a distributed structure configured in an electronic electronic system, in which 1 is a subscriber exchange subsystem (ASS), 2 is a network subsystem (INS), 3 is a central control subsystem (CCS), 4 for DBMS, 5 for local database, 6 for ASP, 7 for INP, 8 for NTP, 9 for OMP, 10 for MMP, DBSG for database support group block, DBKG for database kernel group block, DBBG for database The backup group block and DBQG each represent a database query group block.

As shown in the figure, the electronic switchboard is composed of three subsystems of ASS (1; Access Switching Subsystem), INS (2; Interconnection Network Subsystem), and CCS (3; Central Control Subsystem).

ASS (1) is installed in accordance with a plurality of subscribers, and has an Access Switching Processor (ASP) 6 to perform a distributed call processing function, INS (2) is an INP (7) performing a centralized call processing function portion; Interconnection Network Processor) and NTP (8: Number Translation Processor). The CCS 3 performs a centralization function related to operation and maintenance, and includes an OMP (9; Operation and Maintenance Processor) and an MMP (10; Man-Machine Processor).

In all processors 6 to 10 in which a database exists, there is a DBMS 4 including a DBSG containing a schema manager (SM).

The DBMS 4 of 0MP 9 is composed of three blocks of DBBG, DBSG, and DBKG, and the DBMS 4 of MMP 10 is composed of three blocks of DBQG, DBSG, and DBKG. The remaining processors 6-8 consist of two blocks, DBSG and DBKG.

The DBSG performs the user matching function and the communication function between the DBMS 4 and the DBQG performs the processing of the database query word coming through the MMP 10. DBBG performs change control, data backup and recovery of duplicate data, and DBKG actually retrieves, changes, inserts and deletes the database.

FIG. 2 is a structural diagram illustrating a flow and configuration of messages between volumes related to the present invention, in which SM represents a schema manager.

When the user creates, deletes, or changes a relation of a user through a database query of the MMP 10, the DBQG block of the MMP 10 verifies the requirements by referring to an existing schema, and checks each request for the schema change. Requests memory allocation according to schema change as schema manager.

The schema manager of each processor refers to the free memory information table to check whether memory allocation is possible according to the schema change, and sends a message to the DBQG block of the MMP 10 as a result. When the response to the memory allocation request from all the processors involved in the schema change is good, DBQG sends the relation information received from the user to each relevant processor to request the respective schema change. The information content at this time is the nature and configuration information and attribute information of the relation when the relation is created or changed, and the relation unique number (ID) when the relation deletion is requested.

The schema manager of each processor receives the relation information, analyzes it, manipulates the information according to the schema content to be changed, and then calls DBKG to perform the actual schema change. If all schema changes are successful in each of the related processors, the free memory details used to create the schema are reflected in the free memory information table, and the schema changes are backed up to disk through DBBG. If any one of the processors fails, the processors whose schema changes were made by DBQG's request go into recovery to maintain the previous state.

3 is an overall process flow diagram of the present invention.

When a memory allocation request for creating and changing a schema is received from DBQG (11), the schema manager checks whether the required memory is secured for each request content (12) and transmits the information to DBQG (13).

When a request for a schema change is received from DBQG (14), the schema is changed according to the contents of the request, a log is generated accordingly, and a message is sent to DBQG informing that the schema change is completed (15).

Then, if there is no request for schema recovery from DBQG (16), if there is no request, the generated log is sent to the DBBG of the OMP 9 (17). After receiving the disk backup completion message from the DBBG, the process ends (18). However, if there is a request for schema recovery from DBQG, the schema is restored to the state before the change by referring to the log contents generated (19) to ensure the consistency of the schema (19) After completing the recovery, the message is sent to DBQG and terminated. (20).

Therefore, the present invention carried out by the above processing procedure has the following application effects.

First, when a user who writes an application program in an electronic switchgear develops a function, and a relation that needs to be newly created, deleted, or changed is created, the user does not need to register offline, so the user's function development is convenient. Second, it is possible to operate in an existing database without making a new database file, thus shortening the application time of new function development. Third, if a new database file is created by registering a relation offline, the processor should be temporarily suspended for loading into the system.However, the schema can be managed to create, delete, and delete relations without interrupting the system's operation. Changes are possible.

Claims (1)

Processor (6; ASP) equipped with a database management system (4; hereinafter referred to as DBMS) that consists of a database support group (hereinafter referred to as DBSG) block and a database kernel group (hereinafter referred to as DBKG) block. A subscriber network subsystem (1.ASS), and a network subsystem (2; INS) having a processor (7,8; INP, NTP) equipped with a DBMS (4) consisting of the DBSG and the DBKG; . A processor (9; OMP) equipped with a DBMS (4) composed of the DBSG, a DBKG, and a database backup group (DBBG) block; and a processor (10) equipped with the DBSG, a DBKG, and a database query group block (DBQG); In the database schema management method applied to an electronic switch system comprising a central control subsystem (CCS) having an MMP), when a memory allocation request for creating and changing a schema comes in, After performing the first steps (11 to 13) and the first step (11 to 13) to check whether it can be secured or not, if a request for a schema change is received, the schema is changed according to the request contents and the log accordingly After the second steps (14, 15) to send a message indicating the completion of the schema change, and after performing the second steps (14, 15), if there is no schema recovery request, the generated log is transmitted, and the disk After receiving the backup completion message, and after completing the third step (17, 18) and the second step (17, 15), if there is a request to recover the schema, the schema is restored to the state before the change by matching the schema And a fourth step (19, 20) of terminating after sending the recovery completion result message.