JPH11232158A - Data base maintenance and management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data base maintenance and management system which automatically performs maintenance of data base during operation. SOLUTION: A master management part 28 which updates a master data base based on master data for update which are sent from the outside and received by a file transfer client 23, a history data base management part 30 which executes backup at the time when an idle capacity is reduced to a required quantity or smaller, backup/restore processing parts 33 and 34 which execute the backup/restore processing at the time set to a parameter table 29, an index update part 36 which updates the index of the data base, and a purge processing part 37 which physically deletes a deletion file are provided, and a function execution control part 38 periodically starts these parts to automatically execute various function processings such as master data update, backup/restore, automatic adjustment of a disk space, and prevention of degradation in retrieval performance.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database maintenance management system which is mounted on a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. In particular, it relates to automation of database maintenance.

[0002]

2. Description of the Related Art FIG. 17 is an overall configuration diagram of a system for performing maintenance management of equipment. Elevators, building facilities, and the like (hereinafter, simply referred to as "facilities") 1 scattered in various places are managed by respective information centers 2 installed for each of a plurality of blocks nationwide. Each information center 2 monitors each facility 1 within its jurisdiction 24 hours a day, and centrally manages information on each customer and trouble information for reporting abnormalities that have occurred in a client while accumulating them in a database 3 while centrally managing the entire system. Information is exchanged with another information center 2 via the connected network 4. The network 4 is also connected to sales offices 5 installed all over the country. Each of the offices 5 accesses the database 3 of the information center 2 from the installed information terminal to collect various information. Have acquired. The host computer 6 connects the information center 2 and the maintenance management system connected to the network 4 to other systems.

Each information center 2 has a configuration in which a router 7, a processing client 8, an operation client 9, a server 10, and a backup server 11 are connected via a LAN 12. Since the information center 2 must monitor the facilities in the maintenance management area on a 24-hour basis, a backup server 11 is provided in addition to the server 10 which manages the database 3 for ordinary business processing. I have. The backup server 11 has the same database 3 as the server 10 by copying updated information as appropriate. The processing client 8 performs system management such as data security processing such as execution of backup of the database 3. In addition, the operation client 9 performs normal business processing such as management and operation of facilities and customers based on the data accumulated in the database 3.

The database 3 contains information on contracted customers, equipment, information on telephone reports, information on detected faults, and updates of master data sent from another information system via the host computer 6. Various data such as information is registered and stored, and is classified into a plurality according to the purpose and the like and managed.
The database 3 also processes the collected information and collects and accumulates various statistical information for business processing. The data stored in the database 3 includes data that is periodic and quantitative, such as a periodic maintenance report, and data that has an undetermined timing and generated data amount as represented by failure information. Therefore, an administrator assigned to each information center monitors the usage status of the database 3 and takes appropriate backups, moves files, and maintains the database 3.

[0005]

However, in the past, detailed database maintenance and management was manually performed and could not be performed automatically. For example, although it was possible to manually back up the entire database, it was not possible to isolate unnecessary data or important data and automatically perform appropriate processing such as backup.

In addition, the process of reflecting the master data for update sent from another information center in the master database cannot be automatically performed.

Further, there is no function for automatically recovering when the performance such as the search time of the database is deteriorated.

[0008] Since such database maintenance and management work requires specialized knowledge, conventionally, technicians with specialized skills have been assigned to each information center to respond. However, the maintenance management system
Because it is operated for 4 hours, it puts a heavy burden on the database administrator, or it must be handled by assigning a plurality of database administrators to each information center. I can't say that.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a database maintenance management system capable of automatically performing database maintenance during business operation. is there.

[0010]

In order to achieve the above object, a database maintenance and management system according to a first aspect of the present invention is capable of executing 24
In a database maintenance management system that is installed in a system that is performed continuously over time and performs maintenance of the database without stopping its normal business processing, master data that receives update master data sent from another system It has a receiving means, and a master managing means for automatically reflecting the master data in a master database when the master data receiving means receives the master data, and automatically performs a master maintenance function process.

[0011] In the database maintenance management system according to the second invention, the normal business processing using the database is performed by 24
In a database maintenance management system that is installed in a system that is performed continuously for a time and performs maintenance management of the database without stopping its normal business processing, a data storage period to any one of the databases set in advance, a save target Database management parameter storage means for storing data to be saved and required free space for the database, data storage means for saving data stored in the database, and free space for the database When data becomes equal to or less than the required free space, data stored in the database is data to be saved based on the information to be saved and data that has passed the data saving period is moved to the data saving means, and Data that automatically secures free space for the database And a base management means, is intended for automatically save / delete function processing of data.

[0012] In the database maintenance management system according to the third invention, the normal business processing using the database is performed by 24
In a database maintenance management system that is mounted on a system that is performed continuously for a time and performs maintenance of the database without stopping its normal business processing, a database to be backed up in advance and a backup start time of each database are set. It has a database management parameter storage means to hold and a backup processing means to back up the corresponding database at the time when the backup start time comes, and automatically executes the database backup function processing.

[0013] In a fourth aspect of the present invention, in the database maintenance management system according to the third aspect, the database management parameter storage means further includes a secondary database generated based on a preset backup database and each of the secondary databases. Database generation processing means for holding a generation processing start time of the secondary database, and automatically performing the generation processing of the secondary database corresponding to the generation processing start time, and Access control means for distributing the data to the database or the secondary database.

According to a fifth aspect of the present invention, in the database maintenance management system according to the third aspect, the database management parameter storage means holds a preset statistical data update start time and updates an index of the database. It has an updating means.

[0015] In the database maintenance management system according to the sixth aspect of the present invention, the normal business processing using the database is performed in 24 hours.
In a database maintenance management system that is mounted on a system that is performed continuously for a time and performs maintenance management of the database without stopping normal business processing, a database management parameter storage unit that holds a preset purge process start time, Purge processing means for automatically automatically deleting deleted files remaining in the database at the time when the purge processing start time comes, and automatically executing the purge function processing of the database.

A database maintenance management system according to a seventh aspect of the present invention is the database maintenance management system according to the first to sixth aspects, further comprising function execution control means for executing the function processing at a constant cycle.

[0017] In the database maintenance management system according to the eighth invention, the normal business processing using the database is performed by 24
In a database maintenance management system that is installed in a system that is performed continuously for a period of time and performs maintenance management of the database without stopping its normal business processing, a database to be backed up set in advance, a backup start time of each database, A database management parameter storage unit for storing a data storage period for each database and a required free space for each database; a data storage unit for saving the database; and When the database is backed up and at the time when the free space of the database becomes less than the required free space, the data that has passed the data storage period among the data stored in the database is moved to the data storage unit and data And a database management means for automatically free up space for over scan, is to automatically execute the backup process at regular and irregular timing.

[0018]

Preferred embodiments of the present invention will be described below with reference to the drawings. In the present embodiment, each function provided by the database maintenance management system according to the present invention will be described in each embodiment.

Embodiment 1 FIG. 1 is an overall configuration diagram of a system for performing maintenance management of equipment to which a first embodiment of a database maintenance management system according to the present invention is applied. The basic configuration is the same as in the conventional example. That is, the equipment 1 included in each of the plurality of divided blocks is maintained and managed by the information center 20 installed for each block. Each information center 20 monitors each facility 1 within its jurisdiction around the clock, centrally manages customer information and trouble information while accumulating them in a database, and performs other information centers via a network 4 connecting the entire system. 20 and exchange information. Also, this network 4
Sales offices 5 installed in various parts of the country are also connected, and each office 5 can access various information by accessing the database of the information center 20 from the installed information terminals (hereinafter, referred to as “remote clients”). Have acquired. The host computer 6 connects the information center 20 and the maintenance management system connected to the network 4 to other systems.

FIG. 2 is an overall configuration diagram of a database maintenance management system installed in each information center 20 in the present embodiment. FIG. 2 shows a router 21, a plurality of servers 22, a file transfer client 23, and a database monitoring client 24. These are L
They are connected by AN25. This information center 20
Each of the facilities 1 maintained and managed by the server is accessed via the router 21. The server 22 includes one or more external storage devices, for example, magnetic disk devices, and stores various databases in each magnetic disk device in a distributed manner. Basically, the database is classified by function.

The provision of various databases including those for backup in which magnetic disk device of which server 22 is a mere design matter unless otherwise described. The file transfer client 23 is a communication terminal device for performing data communication via the network 4 in the maintenance management system. The database monitoring client 24 forms a main part of the database maintenance management system, and performs maintenance management of the database stored in each server 22.
In addition, in the information center 20, a client computer or the like corresponding to the operation client shown in FIG. 17 is connected to the LAN 25, but is omitted from FIG. 2 because it is not a characteristic component of the present embodiment. doing.
The system configuration shown in FIG.
The same applies to に お い て 5.

FIG. 3 is a functional block diagram of the system configuration shown in FIG. 2, and shows only components necessary for explaining a characteristic master maintenance function of the present embodiment. In FIG. 3, the file transfer client 23
It has a master data receiving unit 26 for receiving master data for update sent from another system via a host computer. Database monitoring client 2
4 has a master management unit 28 for automatically reflecting the master data received by the file transfer client 23 on the master database 27. Master database 2
7 stores data such as information on the equipment of the maintenance management destination in common with other systems as well as this system. In practice, the master database 27
Are provided, but in the present embodiment, one is provided for convenience.
Only one is shown.

A feature of the present embodiment is that the provision of the above-described configuration enables the master database 27 to be automatically updated when master data is received from another system.

Next, the processing of the master maintenance function in this embodiment will be described with reference to the flowchart shown in FIG.

In the maintenance management system, master data, for example, information on a new or canceled customer is sent to the information center 20 every day. The transmitted information is difference information of master data obtained by comparing the master data of the previous day and the master data of the current day by the host computer 6. More specifically, the master data to be updated and the new / change / deletion processing for which master database are included in the information. The master data receiving unit 26 of the file transfer client 23 receives the master data transmitted from the host computer 6 via the network 4 (Step 101). Upon receiving the master data, the file transfer client 23 notifies the database monitoring client 24 of the reception together with the master data (step 10).
2). The master management unit 28 of the database monitoring client 24 reflects the master data on the master database 27 at the time of receiving the notification (step 1).
03).

According to the present embodiment, since the operation is performed as described above, the master database 2 can be operated without manual operation.
7 can be updated automatically. When a plurality of master databases 27 exist, the master database name to be sent is added to the master data, so that the master database 27 to be updated can be easily specified. Further, the master management unit 28 can similarly update the master database 27 based on the update information of the master data internally generated in the information center 20 based on the update information.

Embodiment 2 FIG. FIG. 5 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. As in FIG. 3, only the components necessary for describing the characteristic history data storage / deletion function of the present embodiment are shown. The overall configuration of the maintenance management system and the configuration of the information center 20 in the present embodiment are the same as those in the first embodiment. The database monitoring client 24 has a parameter table 29 and a history database management unit 30. In this embodiment, the history database (D
B) The data storage / deletion function for organizing the history data such as the failure history, alarm history, and follow history stored in 31 is provided. Parameters necessary for execution control are set in advance in a parameter table 29 provided as a database management parameter storage unit. In the present embodiment, the period for storing the history data in the history database 31, the save target information specifying the history data to be saved, and the required free space for the history database 31 are set. Among these, the evacuation target information that specifies the history data to be evacuation is information set for the following reasons. That is, in the history data,
This may be a certain period, but during that period, there are some which should not be evacuated because they are always referred to in performing business operations. Therefore, history data that may be saved is set in the save target information. The certain period corresponds to a history data storage period. The save target information may be set in units suitable for operation, such as a history data unit, a history data table unit, and a history database unit.
Further, assuming that the history database 31 is stored in the server A as shown in FIG. 5, the storage history database 32 of the other server B is used as a data storage unit that saves history data. Further, the history database management unit 30 moves the history data in the history database 31 to the storage history database (DB) 32 of the server B under the conditions described later. Note that one or a plurality of history databases 31 and storage history databases 32 in the present embodiment can be provided in any magnetic disk device of any server 22. Here, one is shown for convenience. .

Next, the history data storage / deletion function processing according to the present embodiment will be described with reference to the flowchart shown in FIG.

The above-mentioned history data is accumulated in the history database 31 every day if nothing is done, and becomes enormous. Therefore, the history database management unit 30 is constantly operated, and the free space of the history database 31 is constantly monitored at regular intervals (step 201). When the history database management unit 30 detects that the free space of the history database 31 has become equal to or less than the required free space set in the parameter table 29, the history database management unit 30 saves the history data accumulated in the history database 31 at that time. Move to the history database 32. That is, the history data to be moved is copied to the storage history database 32 (step 202), and the history data is deleted from the history database 31 (step 203). At this time, the history database management unit 30
The history data, which is the save target based on the save target information set in the history data and has passed the history data storage period, is set as the movement target to the storage history database 32. In the parameter table 29, a history data storage period can be set for each history data.

According to the present embodiment, when the free space in the history database 31 falls below a certain level, the history data meeting the conditions is moved to the storage history database 32. A free area can be automatically secured. Further, the history data to be moved is specified in consideration of the usage status in the system, that is, the type of the history data and the elapsed time since the accumulation.

In the above description, the save destination of the history data is the single storage history database 32, but the history data storage means is provided in a different magnetic disk device or a different server 22 depending on the type of the history data. Is also good. In addition, the parameter table 29 as a database management parameter storage unit can be expanded on a memory or stored in a file format.
Further, the data to be handled is not limited to the history data.

Embodiment 3 FIG. FIG. 7 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. As in FIG. 3, only the components necessary for describing the characteristic backup function of the present embodiment are shown. The overall configuration of the maintenance management system and the configuration of the information center 20 in the present embodiment are the same as those in the first embodiment. In FIG. 7, the database monitoring client 24
Is the parameter table 29 and the backup processing unit 33
And In the parameter table 29 in the present embodiment, the name of the database to be backed up, the backup start time of each database, and the backup destination are set in advance. That is, a database name to be backed up to a predetermined backup destination at a predetermined time (backup start time) is set. FIG. 8 shows an example of setting in the parameter table 29. The backup processing unit 33 is a means for automatically executing the backup processing. In this embodiment, since two generations of databases are stored, two backup destinations are set for each database as shown in FIG.

Next, the backup function processing in this embodiment will be described with reference to the flowchart shown in FIG.

The backup processing unit 33 always compares the system time with the backup start time set in the parameter table 29 at predetermined time intervals (step 301). Here, when the system time reaches one of the backup start times, the backed-up database (hereinafter referred to as “backup file”) of the destination generation existing in the backup destination of the corresponding database is deleted (steps 302 and 303). ). The switching control of the backup destination is performed based on flag information or the like. Then, after initializing the backup destination volume (magnetic disk device) (step 304), the database is copied to the directory set in the parameter table 29 (step 305). Of course, if another file exists in the volume, the file is not initialized. When a database is accessed during backup, the access log is recorded. The recorded log file is backed up together with the database. Thereafter, the next backup destination is designated by rewriting the flag information (step 30).
6).

According to the present embodiment, the specified database can be automatically backed up at the specified time (backup start time) without stopping the equipment maintenance management system. Therefore, there is no need to manually input a large number of file names even when the number of databases to be backed up is very large.
This feature is available, for example, from Oracle's SQLBase
This can be realized by executing a command (BACKUP SNAPSHOT) provided by the online backup function of 5.1.4J.

Embodiment 4 FIG. FIG. 10 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. Like FIG. 3, only the components necessary for explaining the characteristic restore function of the present embodiment are shown.
The overall configuration of the maintenance management system and the configuration of the information center 20 in the present embodiment are the same as those in the first embodiment.
In FIG. 10, the database monitoring client 24
Has a parameter table 29, a restore processing unit 34, and an access control unit 35. In the parameter table 29 in the present embodiment, the names of the secondary databases to be generated based on the backed up databases, the generation start time of the respective secondary databases,
The restore destination is set in advance. That is, a database name for generating a secondary database at a predetermined restoration destination at a predetermined time (restore start time) is set. The secondary database here is a database generated for the purpose of distributing the access load to the original database and having basically the same contents as the original database. In the present embodiment, by using the backup file as the original data, the load on the server 22 having the original database can be reduced by executing this processing. The parameter table 29 in the present embodiment is also set in the same manner as in FIG. In the present embodiment, the secondary database is called a statistical database. The restore processing unit 34
This is a means for automatically executing the restore processing. The access control unit 35 distributes the access destination of the database to the original database or the secondary database in response to a request from each client to the database.

Next, the restore function processing according to the present embodiment will be described with reference to the flowchart shown in FIG.

The restore processing unit 34 always compares the system time with the restore start time set in the parameter table 29 at predetermined time intervals (step 40).
1). Here, when the system time reaches one of the restore start times, the corresponding statistical database existing in the restore destination of the corresponding database is deleted (steps 402 and 403). Then, after initializing the volume (magnetic disk device) storing the deleted statistical database as needed (step 404), the statistical database is generated in the directory set in the parameter table 29 based on the backup file. (Step 405).

According to this embodiment, the designated statistical database can be automatically regenerated without stopping the equipment maintenance management system at the designated time (restoration start time). Therefore, even when there are many databases to be restored, it is not necessary to manually input many file names. This feature
For example, a command (REST) provided by the online restore function of SQLBase 5.1.4J of Oracle Corporation
ORE SNAPSHOT).

As described above, in this embodiment, the statistical database is generated.
Allows a predetermined client, for example, a remote client installed in a business office, to access a backup file or a statistics database, while allowing a client in an information center to access the original database. That is, in the related art, accesses from a plurality of clients are concentrated on the same database 22. However, in the present embodiment, the access load can be distributed by distributing the access destinations by the clients that access the database. .

Embodiment 5 FIG. FIG. 12 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. As in FIG. 3, only the components necessary for explaining the characteristic statistical information (index) updating function of the present embodiment are shown. The overall configuration of the maintenance management system and the configuration of the information center 20 in the present embodiment are the same as those in the first embodiment. 12, the database monitoring client 24 has a parameter table 29 and an index updating unit 36. In the parameter table 29 in the present embodiment, a statistical data update start time is set in advance. The index updating unit 36
When a predetermined time (restore start time) comes, the index of the database is updated. The statistical information (index) updating function in the present embodiment is provided for the following purpose.

That is, the storage destination of each data registered in the database to shorten the search time is set separately from the actual data as statistical information (index). This statistical information is organized according to a certain rule at the time of constructing the database. However, if data is repeatedly added or deleted, the statistical information itself is stored in a scattered manner even if the above rule is followed. This variation leads to an increase in access time, and as a result, degradation in search performance.

Therefore, in this embodiment, the provision of the index updating section 36 enables automatic updating of statistical information periodically, that is, at the time set in the parameter table 29 every day. This feature, for example,
Commands provided by the update function of Oracle's SQLBase 5.1.4J (UPDATE STATISTIC)
S ..) can be realized. This update function is provided with a method of performing update for each database and a method of performing update for each table. In the present embodiment,
Update is performed in table units in order to reduce the unit of exclusive control.

Embodiment 6 FIG. FIG. 13 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. As in FIG. 3, only the components necessary for describing the characteristic purge function of the present embodiment are shown. The overall configuration of the maintenance management system and the configuration of the information center 20 in the present embodiment are the same as those in the first embodiment. In FIG. 13, the database monitoring client 24
It has a parameter table 29 and a purge processing unit 37. In the parameter table 29 according to the present embodiment, a preset purge processing start time is set in advance. That is, the predetermined purging process is automatically executed by the purge processing unit 37 at a predetermined time (purge start time). The purge function in the present embodiment
It is provided for the following purposes.

That is, for example, when a file or directory on a network constructed by Network provided by Novell of the United States is deleted, the file is deleted, for example, by the SQLBase 5.1.4J of Oracle Corporation.
It is not physically deleted so that it can be recovered by the LAGE command. In the case of SQLBase, when a database is accessed, a log file and a temporary file are generated in accordance with the access.
These files are temporary and are deleted when they are no longer needed. Therefore, the area used for these files is counted as a free area on the volume, but is physically stored as a deleted file. Therefore, unless the file is physically deleted, the storage area of the file cannot be used by another file.

Therefore, in the present embodiment, the provision of the purge processing section 37 for physically deleting a file enables provision of a physical free area. This function can be realized by executing a purge command (PURGE) provided by Novell's NetWare. That is, according to the present embodiment, it is possible to execute the purge process periodically at a time set in the parameter table 29 every day without manual intervention.

Embodiment 7 FIG. In each of the above embodiments, each function provided by the database maintenance management system according to the present invention has been described. However, these functions do not need to be provided exclusively, but can be provided in the same database monitoring client 24 and function simultaneously. FIG. 14 is a functional block configuration diagram of the database maintenance management system according to the present embodiment. In the present embodiment, the function execution control unit 38 that executes each function process described in each of the above embodiments at a constant cycle. It is characterized by having provided.

Next, the processing of the function execution control unit 38 in the present embodiment will be described with reference to the flowchart shown in FIG.

The function execution controller 38 first obtains the contents set in the parameter table 29 (step 50).
1) A function process to be executed is determined and recognized based on the content (step 502). Subsequent processing is repeatedly performed at a fixed cycle (in this embodiment, at one-minute intervals) (step 503). First, when executing the master maintenance function, it is confirmed whether the master data for update is registered in a predetermined file from the file transfer client 23 (steps 504 and 505). In the first embodiment, the process is started when the master data for update is received from the file transfer client 23.
In the parameter table 29 of the present embodiment, flag information on whether or not the master maintenance function is to be executed is set, and the execution of the master maintenance function is controlled by the flag information. When receiving the update master data from another system, the file transfer client 23 sequentially writes the updated master data in a predetermined directory provided in the database monitoring client 24. Since the data written in the directory is queue-managed, the function execution control unit 38 sequentially updates the master database based on the queue information of the data when the master data for update exists in the directory (step 506).

On the other hand, when not executing the master maintenance function, the function execution control
The start time of each function set to 9 and the system time are compared, and if there is a function that has reached the processing start time, that function is executed (steps 507 and 508). In the above embodiments, each function is executed autonomously.
In the present embodiment, the execution is controlled so as to be activated by the function execution control unit 38. Here, the functions to be started are a save / delete function of the history data, a backup function, a restore function, a statistical information update function, and a purge function.

Embodiment 8 FIG. FIG. 16 is an overall configuration diagram of a database maintenance management system installed in each information center in the eighth embodiment. The present embodiment particularly relates to handling of a voice database in a system for performing maintenance management of facilities. Therefore, an audio reproduction client 39 is provided in the information center instead of the above embodiments. The audio playback client 39 includes:
Parameter table 40, voice database management unit 41
And an audio data storage unit 42. Further, a removable external storage device 43 for backup is externally attached. In the present embodiment, the voice database 4
The backup destination of No. 4 is the audio data storage unit 42 on the audio reproduction client 39 side. Further, an external storage device 43 is provided for backing up the audio data storage unit 42. In the parameter table 40, various parameter values are set in advance as in the above embodiments.
In the present embodiment, the start time of the process for backing up the audio database 44 to the audio data storage unit 42, the audio data storage period in the audio database 44, and the required free space for the audio database 44 are set. . Further, a start time of a process for backing up the audio data storage unit 42 to the external storage device 43, an audio data storage period in the audio data storage unit 42, and a necessary free space for the audio data storage unit 42 are set. I have. Also,
The command board client 45 is a client for making a telephone conversation with a customer, and generates one voice data for each conversation.

Next, the processing in this embodiment will be described. The function of the present embodiment is basically a storage / deletion function of the history data for constantly monitoring the free space of the disk device and backing it up irregularly as described in the second embodiment, and the function of the third embodiment. It is based on the combination with the described backup function that takes a regular backup.

First, the content of a conversation with the customer at the command desk client 45 is stored in the predetermined voice database 44 of the predetermined server 22 as voice data. This voice data can be reproduced later in the command console client 45, so that the contents of the conversation can be confirmed or heard by a technician or the like who is performing maintenance work on the equipment on site.

The voice database management unit 41 always has a system time and a backup start time set in the parameter table 40 at predetermined time intervals, that is, a start time of a process for backing up the voice database 44 to the voice data storage unit 42. And the start time of the process for backing up the audio data storage unit 42 to the external storage device 43. Here, when the system time reaches any backup start time, the audio data stored in the audio database 44 / audio data storage unit 42 is backed up in the audio data storage unit 42 / external storage device 43. This process is executed daily as a regular process.

On the other hand, the voice database management section 41 constantly monitors the free space of the voice database 44 / voice data storage section 42 at regular intervals. The voice database 4
The process of backing up the voice data storage unit 42 in the voice data storage unit 42 and the process of backing up the voice data storage unit 42 in the external storage device 43 are almost the same.
4 will be described in the case where a backup is made in the audio data storage unit 42. When detecting that the free space of the voice database 44 has become equal to or less than the required free space set in the parameter table 40, the voice database management unit 41 deletes the voice data stored in the voice database 44 at that time. The data is copied to the storage unit 42 and deleted from the audio database 44. In this way, a free area can be automatically secured for the voice database 44 having a small free space. As described above, the same applies to the case where the audio data storage unit 42 is backed up in the external storage device 43, and an empty area can be automatically secured in the audio data storage unit 42 with a reduced free space. The external storage device 4
The storage medium 3 itself can be replaced, and may be replaced as appropriate.

According to the present embodiment, the backup of the voice database 44 and the voice data storage unit 42 is automatically performed at the specified time (backup start time) without stopping the equipment maintenance management system. In addition, a free space can be automatically secured in the voice database 44 and the voice data storage unit 42.

It is needless to say that the components handling audio data described in the present embodiment can be formed on the same system as the components described in the first to seventh embodiments. The reproduction client 39 may be the same client.

In each of the above embodiments, each server 22 has one or more disk devices.
One or more databases are stored in each disk device. The backup file of each database stored in the server 22 is stored in a different disk device on the same server as the original database or in a disk device of a different server 22 in consideration of safety, maintainability, load distribution, and the like. It is desirable that the server 22 be held on which server 22 is a system design item determined by the number of servers, the number of disk devices included in each server, and the like.

Although the backup start time and the like set in the parameter table in each of the above embodiments do not show a specific example, each parameter value is set to a value considering the scale and operation of the system. It is desirable to do.

Further, in each of the above embodiments, the case where the database maintenance management system according to the present invention is applied to a system for monitoring building equipment and the like has been described as an example. The present invention can also be applied to other systems that are continuously performed, and can provide the same effects as described above.

[0061]

According to the present invention, the contents of the update master data can be automatically reflected in the master database without any manual operation.

Further, when the free space of the history database becomes equal to or less than the required free space, the history data meeting the condition is moved to the history data storage means. Can be secured. Therefore, it is possible to prevent the occurrence of a failure due to the overflow of the database.

Further, at the time when the backup start time comes, the database can be automatically backed up without stopping the equipment maintenance management system.

Further, it is possible to automatically generate a secondary database, and by providing this, the access load can be distributed.

Further, since the database index can be automatically updated, it is possible to prevent the database retrieval performance from deteriorating without manual intervention.

Further, the deleted file remaining on the database can be automatically deleted without manual operation.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram of a system for performing maintenance management of equipment to which a first embodiment of a database maintenance management system according to the present invention is applied.

FIG. 2 is an overall configuration diagram of a database maintenance management system installed in each information center in the first embodiment.

FIG. 3 is a functional block configuration diagram of a database maintenance management system according to the first embodiment.

FIG. 4 is a flowchart showing a master maintenance function process according to the first embodiment.

FIG. 5 is a functional block configuration diagram of a database maintenance management system according to a second embodiment.

FIG. 6 is a flowchart showing a history data storage / deletion function process according to the second embodiment.

FIG. 7 is a functional block configuration diagram of a database maintenance management system according to a third embodiment.

FIG. 8 is a diagram showing an example of setting in a parameter table according to the third embodiment.

FIG. 9 is a flowchart showing a backup function process according to the third embodiment.

FIG. 10 is a functional block configuration diagram of a database maintenance management system according to a fourth embodiment.

FIG. 11 is a flowchart showing a restore function process according to the fourth embodiment.

FIG. 12 is a functional block configuration diagram of a database maintenance management system according to a fifth embodiment.

FIG. 13 is a functional block configuration diagram of a database maintenance management system according to a sixth embodiment.

FIG. 14 is a functional block configuration diagram of a database maintenance management system according to a seventh embodiment.

FIG. 15 is a flowchart showing a function execution control process according to the seventh embodiment.

FIG. 16 is an overall configuration diagram of a database maintenance management system installed in each information center in an eighth embodiment.

FIG. 17 is an overall configuration diagram of a system that performs maintenance management of equipment to which a conventional database maintenance management system is applied.

[Explanation of symbols]

1 customer, 4 networks, 5 sales offices, 6 host computers, 20 information centers, 21 routers, 22
Server, 23 file transfer client, 24 database monitoring client, 25 LAN, 26 master data receiving unit, 27 master database, 28 master management unit, 29, 40 parameter table, 30
History database management unit, 31 History database (D
B), 32 Storage history database (DB), 33
Backup processing unit, 34 restore processing unit, 35 access control unit, 36 index update unit, 37 purge processing unit, 38 function execution control unit, 39 audio playback client, 41 audio database management unit, 42 audio database storage unit, 43 external storage Equipment, 44 voice database, 45 command line client.

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] December 25, 1998

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Claims

[Correction method] Change

[Correction contents]

[Claims]

2. The database maintenance management system according to claim 1, further comprising function execution control means for executing the function processing at a constant cycle.

[Procedure amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0010

[Correction method] Change

[Correction contents]

[0010]

In order to achieve the above object, a database maintenance management system according to the present invention is mounted on a system in which normal business processing using a database is performed continuously for 24 hours. in the database maintenance system for performing maintenance of the database without stopping the normal business process, preset
The database to be backed up and the respective data
Base backup start time, backed up data
Secondary database generated based on the
Holds the generation start time of each secondary database
Database management parameter storage means;
The database corresponding to the time at which the
Backup processing means for backing up data,
The secondary data corresponding to the time when the
Database generation processing that automatically performs database generation processing
And the access destination to the database.
Access to the source or the secondary database
And control means .

[Procedure amendment 3]

[Document name to be amended] Statement

[Correction target item name] 0011

[Correction method] Deleted

[Procedure amendment 4]

[Document name to be amended] Statement

[Correction target item name] 0012

[Correction method] Deleted

[Procedure amendment 5]

[Document name to be amended] Statement

[Correction target item name] 0013

[Correction method] Deleted

[Procedure amendment 6]

[Document name to be amended] Statement

[Correction target item name] 0014

[Correction method] Deleted

[Procedure amendment 7]

[Document name to be amended] Statement

[Correction target item name] 0015

[Correction method] Deleted

[Procedure amendment 8]

[Document name to be amended] Statement

[Correction target item name] 0016

[Correction method] Change

[Correction contents]

Further , in the above invention, there is provided a function execution control means for executing the function processing at a constant cycle.

[Procedure amendment 9]

[Document name to be amended] Statement

[Correction target item name] 0017

[Correction method] Deleted

Claims (8)

[Claims] 1. A database maintenance management system which is installed in a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. Master data receiving means for receiving the transmitted master data for update, and master managing means for automatically reflecting the master data in the master database when the master data receiving means receives the master data. And a database maintenance management system that automatically performs master maintenance function processing. 2. A database maintenance management system which is installed in a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. A database management parameter storage unit for storing a data storage period in any one of the databases, save target information specifying data to be saved, and a necessary free space for the database; A data storage unit serving as a save destination; and when the free space of the database becomes equal to or less than the required free space, data stored in the database is set as a save target based on the save target information and the data storage period. Move the data past the And a database management means for automatically securing a free area for the database, wherein the data storage / deletion function processing is automatically performed. 3. A database maintenance management system which is installed in a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. A database management parameter storage unit for storing a database to be backed up and a backup start time of each database; anda backup processing unit for backing up the corresponding database at the time when the backup start time comes, A database maintenance management system characterized by automatically executing a database backup function process. 4. The database management parameter storage unit further stores a secondary database generated based on a preset backed-up database and a generation processing start time of each of the secondary databases. Database generation processing means for automatically performing the generation processing of the secondary database corresponding to the time, and access control means for allocating an access destination to a database to the database or the secondary database. 4. The database maintenance management system according to claim 3, wherein: 5. The database maintenance method according to claim 3, wherein said database management parameter storage means has index update means for holding a preset statistical data update start time and updating an index of said database. Management system. 6. A database maintenance management system which is installed in a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. A database management parameter storage unit that holds a purge processing start time; and a purge processing unit that physically and automatically deletes deleted files remaining in the database at the time when the purge processing start time comes. A database maintenance management system characterized by automatically executing a purge function process. 7. The database maintenance management system according to claim 1, further comprising a function execution control unit that executes the function processing at a constant cycle. 8. A database maintenance management system which is mounted on a system in which normal business processing using a database is performed continuously for 24 hours and performs maintenance management of the database without stopping the normal business processing. Database to be backed up,
A database management parameter storage unit that stores a backup start time of each database, a data storage period in each database, and a necessary free space for each database; a data storage unit that is a save destination of the database; At the time when the start time comes, the database is backed up and at the time when the free space of the database becomes less than the required free space, of the data stored in the database, Database management means for moving to data storage means to automatically secure a free area for the database, wherein backup processing is automatically executed at regular and irregular timings. Database maintenance management system.