WO2019047071A1

WO2019047071A1 - Method and terminal for responding to database fault

Info

Publication number: WO2019047071A1
Application number: PCT/CN2017/100750
Authority: WO
Inventors: 卢汉利
Original assignee: 富璟科技（深圳）有限公司
Priority date: 2017-09-06
Filing date: 2017-09-06
Publication date: 2019-03-14
Also published as: CN110063042B; CN110063042A

Abstract

A method and terminal for responding to a database fault. The method comprises: acquiring fault event information about a database (S101); determining, based on a fault characteristic parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault handling user (S102); starting a fault event monitoring process (S103); pushing a fault repair result to an audit account corresponding to the fault handling user (S104); and if a fault repair confirmation instruction returned by the audit account is received, ending the fault event monitoring process (S105). The present invention solves the problems that existing response technology of a database fault mainly detects a fault included in the database by means of a pre-set fault detection algorithm, such that the timeliness of database fault repair is relatively low, wherein same may even aggravate the fault degree of the database and increases the difficulty of repairing same, and such that a fault handling user needs to frequently log in to the database to detect whether there is a fault report, thereby reducing the operating efficiency of the fault handling user.

Description

Method for responding to database failure and terminal thereof

Technical field

[0001] The present invention belongs to the field of database technologies, and in particular, to a method for responding to a database failure and a terminal thereof.

Background technique

[0002] With the in-depth development of informatization, the importance of database storage and extraction operations, the importance of the database is becoming more and more prominent. How to ensure that the database system can continue to work efficiently has become an important part of the development of information technology. ring. The existing database failure response technology mainly detects the faults contained in the database through a preset fault detection algorithm, and outputs a corresponding fault report locally in the database, and the fault repair manager cannot log in to the database. Know the fault condition of the database, which reduces the ambiguity of database fault repair, and may even increase the degree of database failure and increase the difficulty of repair. On the other hand, the fault handling user needs to frequently log in to the database to detect whether there is a fault report, which reduces the operation efficiency of the fault handling user.

technical problem

[0003] In view of this, the embodiment of the present invention provides a database fault response method and a terminal thereof, to solve the existing database fault response technology, mainly by detecting a fault included in the database by using a preset fault detection algorithm. And output the corresponding fault report locally in the database. If the fault repair manager does not log in to the database, the fault condition of the database cannot be known, thereby reducing the deficiencies of the database fault repair, and may even increase the fault degree of the database. Increased the difficulty of repairing. On the other hand, the fault handling user needs to frequently log in to the database to detect whether there is a fault report, which reduces the problem of the operation efficiency of the fault handling user.

Problem solution

Technical solution

A first aspect of the embodiments of the present invention provides a method for responding to a database fault, where the response method of the database fault includes:

[0005] acquiring fault event information of the database; wherein the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter; [0006] determining, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault processing user;

[0007] starting a fault event monitoring process, to collect fault repair data generated by the fault handling user to repair the fault event information, and a fault repair result;

[0008] pushing the fault repair result to an audit account corresponding to the fault processing user;

[0009] If the fault repair confirmation instruction returned by the audited account is received, the fault event monitoring process is closed.

[0010] A second aspect of the embodiment of the present invention provides a response terminal of a database failure, where the response terminal of the database failure includes:

[0011] acquiring fault event information of the database; wherein the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter;

[0012] determining, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault processing user;

[0013] starting a fault event monitoring process, to collect fault repair data generated by the fault handling user to repair the fault event information, and a fault repair result;

[0014] pushing the fault repair result to an audit account corresponding to the fault processing user;

[0015] if the fault repair confirmation instruction returned by the audited account is received, the fault event monitoring process is closed

A third aspect of an embodiment of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and operable on the processor, the processor executing the The computer program implements the following steps:

[0017] acquiring fault event information of the database; wherein the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter;

[0018] determining, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault processing user;

[0019] starting a fault event monitoring process, to collect fault repair data generated by the fault handling user to repair the fault event information, and a fault repair result;

[0020] pushing the fault repair result to an audit account corresponding to the fault processing user; [0021] if the fault repair confirmation instruction returned by the audited account is received, the fault event monitoring process is closed

[0022] A fourth aspect of the embodiments of the present invention provides a computer readable storage medium storing a computer program, the computer program being executed by a processor, to implement the following steps: [0023] obtaining The fault event information of the database; wherein the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter;

[0024] determining, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault processing user;

[0025] starting a fault event monitoring process, to collect fault repair data and fault repair results generated by the fault handling user to repair the fault event information;

[0026] pushing the fault repair result to an audit account corresponding to the fault processing user;

[0027] if receiving the fault repair confirmation instruction returned by the audited account, closing the fault event monitoring process

Beneficial effect

[0028] A method for responding to a database failure and a terminal thereof provided by embodiments of the present invention have the following beneficial effects:

[0029] The embodiment of the present invention can determine that there is a fault event in the database, that is, feedback the fault condition to the corresponding fault processing user, thereby reducing the inter-turn difference between the fault occurrence and the fault finding, and realizing the fault reporting situation. The purpose is to eliminate the need for users to log in to the database frequently to confirm whether there is a fault event and to avoid the situation of the fault. On the other hand, after obtaining the repair result, the embodiment of the present invention pushes the corresponding repair result to the corresponding audit account, so that the repair result passes through a multiple review process, and the accuracy of the repair result is ensured.

Brief description of the drawing

DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are merely Some embodiments of the present invention are not laborious for those skilled in the art. Further drawings can also be obtained from these drawings.

1 is a flowchart of a method for responding to a database failure according to a first embodiment of the present invention;

2 is a flowchart of a specific implementation of a database fault response method according to a second embodiment of the present invention; [0033] FIG. 3 is a specific implementation of a database fault response method S103 according to a third embodiment of the present invention; Flow chart

4 is a flowchart of a specific implementation of a method for responding to a database failure according to a fourth embodiment of the present invention; [0034] FIG.

5 is a flowchart of a specific implementation of a method for responding to a database failure according to a fifth embodiment of the present invention;

6 is a structural block diagram of a response terminal for a database failure according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a terminal device according to an embodiment of the present invention.

Embodiments of the invention

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0039] The embodiment of the present invention solves the existing response technology of database failure, mainly detects a fault included in the database by using a preset fault detection algorithm, and outputs a corresponding fault report locally in the database, and the fault repair manager if If you do not log in to the database, you will not be able to know the fault condition of the database, which will reduce the ambiguity of database fault repair, and may even increase the degree of database failure and increase the difficulty of repair. On the other hand, the fault handling user needs to frequently log in to the database to detect whether there is a fault report, which reduces the problem of the operational efficiency of the fault handling user.

[0040] In the embodiment of the present invention, the execution body of the process is a terminal device in which a response program of a database failure is installed. FIG. 1 is a flowchart of an implementation of a method for responding to a database failure according to a first embodiment of the present invention, which is described in detail as follows:

[0041] In S101, acquiring fault event information of the database; wherein the fault event information includes a fault feature parameter and a fault repair scheme matching the fault feature parameter.

[0042] In this embodiment, if the terminal device receives the fault event information of the database, the terminal device triggers a response process of the database fault, thereby repairing the fault condition in the database. Specifically, the fault event information includes data a category, the terminal device reads the data category of the data information every time a data information is received, and determines whether the data information is fault event information according to a preset data category identifier list, if

Then, the operation of S101 is performed.

[0043] In this embodiment, the terminal device may determine whether the database has a fault condition through a local database fault detection program, and then obtain fault event information corresponding to the database; the terminal device may also pass an independent database fault detection terminal. Detecting the fault information contained in the database, and then obtaining the fault event information sent by the terminal device and the detection terminal of the database fault detection terminal

[0044] In this embodiment, the fault event information includes a fault feature parameter, and the fault feature parameter is specifically used to indicate a specific situation in which the database is faulty, including but not limited to: a location where the fault occurs, a fault level, and a database fault module. The data is run, so that the user locates the cause of the fault and the affected database module according to the fault characteristic parameter, so as to determine whether it is necessary to perform service support through the backup database and repair the required time before repairing.

[0045] In this embodiment, the fault event information further includes a fault repair scheme that matches the fault feature parameter. The terminal device or the database failure check terminal may perform a matching operation according to the collected fault feature parameter and the preset repair plan library, and automatically generate a recommended fault repair solution corresponding to the fault, so that the user receives the fault event information, You can refer to the fault repair scheme to repair the database. It should be noted that the fault repairing information included in the fault event information may be one or two or more. In particular, if the fault event information includes two or more fault repairing schemes, it may indicate that the database fault is caused. The reason may be one of the causes of two or more faults, and the terminal device cannot be accurately located. Therefore, the fault repair solution corresponding to multiple fault causes is recommended to the user, and the user may select one of the fault causes of the database. The fault repair plan fixes it.

[0046] Optionally, in this embodiment, if the terminal device is configured to detect a fault condition of multiple databases, the fault event information may further include a database identifier, and the terminal device may locate the faulty database based on the database identifier. . In particular, the terminal device can prompt the user to fail the database by means of red or flashing on the database map marked with all databases.

[0047] In S102, determining, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and pushing the fault event information to the fault processing user. [0048] In this embodiment, the terminal device extracts the fault feature parameter contained therein from the fault event information, locates the faulty module or function in the database, and then determines the user who manages the module or function, and identifies the user as Troubleshoot the user. Specifically, if the fault feature parameter corresponds to multiple faulty modules or fault functions, and multiple faulty modules or fault functions are managed by different users, the fault event information may correspond to multiple fault handling users, and the fault events may be Information peers are pushed to multiple fault handling users. Preferably, the terminal device decomposes the fault event information into multiple fault sub-event information based on different fault modules or fault functions, and pushes each fault sub-event information to the corresponding fault-handling user.

[0049] In this embodiment, after determining the fault handling user, the terminal device sends fault event information to the user equipment according to the user equipment corresponding to the fault processing user and the communication address of the user equipment. Optionally, the terminal device may further generate a fault handling event in the office system corresponding to the fault handling user according to the fault processing user, import the fault event information into the fault handling event, and push the fault handling event. Give the faulty user the corresponding account in the office system.

[0050] In S103, a fault event monitoring process is started to collect fault repair data and fault repair result generated by the fault handling user to repair the fault event information.

[0051] In this embodiment, after receiving the fault event information, the fault processing user performs a repair operation on the fault condition of the database to manually repair the fault that the database cannot be automatically repaired. At the same time, the terminal device also starts a fault event monitoring process, which is used to collect fault repair data generated by the fault handling user to repair the fault condition corresponding to the fault event information. Specifically, the terminal device will initiate an independent thread, and continuously monitor the parameter modification operation in the database through the thread, and the parameter includes a running parameter of the database, a script file, a table structure, and a change of the stored data. The terminal device stores the obtained fault repair data in a storage area corresponding to the fault event information, where the storage area includes an event identifier of the fault event information.

[0052] In this embodiment, the terminal device can open multiple threads for collecting fault repair data of different fault event information. The check terminal of the database fault or the terminal device may check that there are multiple fault conditions in the database within a certain time interval, thereby generating multiple fault event information, so the terminal device determines the repair situation corresponding to each fault event information, A plurality of threads are opened, and each thread detects fault repair data corresponding to a fault event information, and stores them in respective corresponding storage areas. [0053] In this embodiment, the manner in which the terminal device collects the fault repair data is specifically: the terminal device acquires various parameters in the database by using a preset interval, and compares the currently collected parameters with the previous collection. Corresponding parameters are compared, the changed parameters are determined, and the changed parameters are used as fault repair data of the repair process, thereby implementing incremental storage of the fault repair data, thereby reducing the amount of data of the fault repair data and The storage pressure of the terminal device.

[0054] In this embodiment, if the terminal device receives the fault repair completion command sent by the fault processing user, it determines that the fault event information has been repaired, and identifies the processing result included in the fault repair completion command as a fault. Fix the result. Optionally, if the terminal device does not detect the change of the parameter of the database in the preset maximum repair waiting time, that is, the user does not repair the data, and the repair operation is completed, and thus the situation is Next, the terminal device will also recognize that the fault event information has been processed, and obtain a corresponding fault repair result according to the current database running condition.

[0055] Optionally, in this embodiment, after the terminal device obtains the fault repair result, the fault repair data may be suspended. In this case, if the terminal device receives the fault repair confirmation command returned by the audit account, the related operation of S105 is performed; otherwise, if the terminal device does not receive the fault repair confirmation command returned by the audit account, the fault event is restarted. Monitor the process to continue collecting fault repair data.

[0056] In S104, the fault repair result is pushed to an audit account corresponding to the fault processing user.

[0057] In this embodiment, after determining that the fault event information of the database has been repaired, the terminal device performs an operation of confirming and confirming the fault processing result to ensure that the fault repair result is correct. The terminal device queries the audit account corresponding to the fault handling user who performs the repair operation. The audit account may be the upper-level user of the fault-handling user or the administrator of the database. The administrator of the database is responsible for the monitoring and management of the entire database. .

[0058] Optionally, in this embodiment, the terminal device further sends the fault repair result to the fault handling user. Because some repair operations may require the database to automatically run for a long period of time, and the fault handling user does not need to pay attention to the database during the automatic running process, and when the database will automatically repair the program is completed, the corresponding fault can be The repair result is pushed to the fault handling user so that the fault handling user confirms that the repair operation has been completed.

[0059] Corresponding to the manner of pushing the fault processing user, in this embodiment, the manner in which the terminal device pushes the fault processing result to the auditing account includes: after the terminal determines the auditing account, querying the auditing account correspondingly The device and the communication address of the device, and send the fault processing result to the device. The push mode includes: The terminal device generates a fault audit event in the office system, and imports the fault processing result into the fault audit event, and pushes the fault audit event to the audit account corresponding to the fault processing user in the office system.

[0060] In S105, if the fault repair confirmation command returned by the audited account is received, the fault event monitoring process is closed.

[0061] In this embodiment, after receiving the fault processing result pushed by the terminal device, the auditing account may determine whether the fault repairing operation has been completed based on the fault processing result. If the auditing account agrees with the fault processing result and determines that the fault repairing operation has been completed, a fault repair confirmation command is generated and sent to the terminal device; if the auditing account does not agree with the fault processing result, the fault processing user needs to re-process the fault. If the event is repaired, the fault re-repair command is generated to the terminal device. In this case, if the terminal device receives the fault re-repair command, the terminal device returns to perform the operation of S102 to prompt the fault processing user to re-process the fault event.

[0062] In this embodiment, after receiving the fault repair confirmation instruction returned by the audit account, the terminal device determines that the fault event information has been successfully repaired, so that the repair data is not required to be collected for the event, so the terminal will be closed. The fault event monitoring process, and the fault repair data and the corresponding fault repair result are encapsulated in a data packet, and the data packet is saved as a repair record of the database.

[0063] It can be seen that the response method of the database fault provided by the embodiment of the present invention determines the fault handling user corresponding to the fault event information by acquiring the fault event information of the database, and pushes the fault event information to the determined fault. The user is faulty, so that the user can repair the faults included in the database according to the fault feature parameters included in the fault event information and the fault repair scheme matching the fault feature parameters. Similarly, the response terminal of the database fault will be The fault event monitoring process is started to collect the fault repair data obtained by the fault processing user in the process of repairing the fault event information, and the fault repair result generated after the repair is completed, and automatically push the fault repair result to the fault processing user. Corresponding audit account, to confirm whether the fault event information has been processed. If the fault repair confirmation command returned by the audit account is received, it indicates that the fault repair event has been correctly repaired, and the fault response process can be ended. Compared with the existing response technology of the database failure, the embodiment of the present invention can feedback the fault condition to the corresponding fault processing after determining that the database has a fault event. The user, thereby reducing the gap between the fault and the fault discovery, achieves the purpose of reporting the fault condition, without requiring the user to frequently log in to the database to confirm whether there is a fault event, and to avoid the intensification of the fault condition. On the other hand, after obtaining the repair result, the embodiment of the present invention pushes the corresponding repair result to the corresponding audit account, so that the repair result passes through a multiple review process, and the accuracy of the repair result is ensured.

2 is a flow chart showing a specific implementation of a method for responding to a database failure according to a second embodiment of the present invention. As shown in FIG. 2, with respect to the embodiment shown in FIG. 1, the method for responding to a database failure provided by this embodiment further includes S201~S203, which are as follows:

[0065] Further, after receiving the fault repair confirmation instruction returned by the audited account, after the fault event monitoring process is closed, the method further includes:

[0066] In S201, the repair feature parameter of the fault repair data is extracted, and the repair feature parameter is matched with a preset repair plan library.

[0067] In this embodiment, after completing the fault repair operation of the database, the terminal device learns the repair process of the fault handling user to improve the number of solutions of the fault repair solution library. The terminal device first determines the fault type of the fault event information, and obtains the fault repair data corresponding to the fault event from the storage area corresponding to the fault event monitoring process, and extracts the repair feature parameter from the fault repair data, where the repair feature parameter is specific The parameter for modifying the fault event information for the fault handling user and modifying the database, as described above, the parameter includes one or a combination of at least two: a running parameter of the database, a script file, a table structure, and a change in the stored data. Optionally, the terminal device may further compare the database parameters of the fault occurrence and the database parameters of the fault repair completion, and then obtain the repair feature parameters.

[0068] In this embodiment, the terminal device is pre-configured with a repair solution library for recording a fault repair solution corresponding to different fault types. The repair solution library may be stored in a storage module built in the terminal device. In this case, the terminal device may directly read the local storage module to obtain data included in the repair solution library; the repair solution library may also Stored in a separate database server or other terminal device, in which case the terminal device needs to establish a communication connection with the database server or other terminal device, and send a call request of the repair solution library to obtain the repair solution library. data.

[0069] In this embodiment, after the terminal device obtains the repair feature parameter, it will be included in the repair solution library. The repair feature parameters of each fault repair scheme are matched to determine whether the fault repair means has been recorded in the repair scheme library. Since the repair feature parameter is extracted within the fault repair data in the process of repairing the fault event information, the repair feature parameter may represent a fault repair solution corresponding to the user performing database repair. If the repair feature parameter matches any fault repair scheme, it means that the repair methods of the two are consistent and belong to the same fault repair scheme; if the repair feature parameter does not match any fault repair scheme in the repair scheme library, it indicates the fault. The repair process corresponding to the repair data belongs to a new repair scheme, so the operations of S202 and S203 will be performed to add the new repair scheme to the repair scheme library.

[0070] In S202, if the repair feature parameter does not have a fault repair solution matched in the preset repair plan library, a fault repair solution is created.

[0071] In this embodiment, if the terminal device cannot find a fault repair solution that matches the repair feature parameter in the repair solution library, create a fault repair solution in the repair solution library to record the unrecovered fault repair. means. Optionally, the terminal device may also newly create a fault repair solution locally, and then send it to the repair solution library after the generation is completed, so as to repair the solution inventory and store the fault repair solution.

[0072] In this embodiment, the fault repairing scheme is specifically a scheme template, which includes a plurality of content to be filled in and a part of standard format content, and sets a scheme unique identifier for the scheme module. Specifically, the fault repair scheme template corresponding to each repair scheme library may be different. Therefore, before the fault repair scheme is created, the terminal device needs to obtain the scheme template from the repair scheme library.

[0073] In S203, the repair feature parameter is imported into the newly created fault repair solution, and stored in the preset repair plan library.

[0074] In this embodiment, after the terminal device creates a fault repairing scheme, the terminal device imports the parameter items included in the extracted repair feature parameters into the location corresponding to the fault repair solution. Preferably, the terminal device further introduces the fault feature parameter in the fault event information into the fault repair solution, so as to determine the fault repair solution corresponding to the fault event information, and may establish the fault event information imported based on the fault repair solution. , to determine if the two match.

[0075] In this embodiment, after the terminal device imports the repair feature parameter into the fault repair solution, the fault repair solution is established, so the fault repair solution is stored in the repair solution library, so that The fault condition 吋, the terminal device can directly respond to the repair operation of the fault repair scheme automatically After the database is repaired, or the related fault condition is encountered, the terminal device can also push the fault repair solution to refer to the fault handling user.

[0076] In the embodiment of the present invention, after each repair is completed, the repair feature parameter corresponding to the repair operation is obtained, and it is determined whether the repair operation has been recorded, and a new database repair means is created. The fault repair scheme is saved, so that after each operation, the fault repair scheme can be learned, and the automatic repair capability of the repair scheme library is improved, thereby reducing the number of fault repair users on-site repair and improving the repair efficiency.

FIG. 3 is a flowchart showing a specific implementation of S103 in a method for responding to a database failure according to a third embodiment of the present invention. As shown in FIG. 3, with respect to the embodiment shown in FIG. 1, a method for responding to a database failure provided by this embodiment includes the following steps, which are as follows:

[0078] Further, the initiating fault event monitoring process is configured to collect the fault repair data and the fault repair result generated by the fault processing user to repair the fault event information, including:

[0079] In S301, receiving a repair resource request instruction initiated by the fault processing user, and generating resource scheduling information based on the repair resource request instruction.

[0080] In this embodiment, the fault processing user needs to apply for an additional repair resource in the process of repairing the fault information of the database, and may send a repair resource request instruction to the terminal device, or through the built-in client of the terminal device. End, generating the above-mentioned repair resource request instruction, so that the terminal device can apply for the repair resource required in the fault repair process to the corresponding responsible person based on the repair resource request instruction.

[0081] In this embodiment, the repair resource request instruction includes the repair resource category and the number of resources required by the user, and in particular, may include the limit information of the resource call. The terminal device can generate a filling interface for repairing resource request information through the display module. After the fault processing user fills in the information and fills in the required information in the interface, the corresponding repair resource request instruction is generated, and the application process of the additional resource repair instruction is started.

[0082] In this embodiment, after receiving the user-initiated repair resource request instruction, the terminal device generates a resource scheduling information for each request content based on the resource request content included in the repair resource request instruction.

[0083] In S302, determining, according to the preset resource management responsibility list, a resource management account corresponding to the repair resource request instruction, and pushing the resource scheduling information to the resource management account. [0084] In this embodiment, the terminal device storage module records the management responsibility person corresponding to each resource, that is, the resource management account described above. The foregoing resources include but are not limited to: database resources, network resources, peripheral module resources, and rights resources. Different resources are managed by different resource owners. Therefore, the terminal device first determines the target object corresponding to the request according to the repair resource request instruction.

[0085] In this embodiment, the terminal device extracts a resource category included in the repair resource request instruction, and queries a preset resource management responsibility list, and determines a resource management responsible person corresponding to the resource category and a corresponding one of the responsible person. The resource management account, and the resource scheduling information generated in S301 is pushed to the resource management account.

[0086] Specifically, in this embodiment, the manner of pushing is consistent with the manner of pushing the user to the fault processing, and the resource scheduling information may be directly sent to the terminal device corresponding to the resource management account, or a resource may be generated in the office system. Schedule the event and add the resource scheduling event to the pending event of the resource management account. Preferably, the terminal device further determines a processing limit of the resource management account according to the database fault level and the requested resource type, so that the resource management account and the resource request instruction perform corresponding processing.

[0087] In S303, if the scheduling confirmation instruction returned by the resource management account is received, the usage right of the repair resource corresponding to the repair resource request instruction is added to the permission parameter of the fault processing user.

[0088] In this embodiment, after receiving the resource scheduling information pushed by the terminal device, the resource management account determines, according to the actual situation, an application that agrees to the fault processing user to additionally repair the resource. Specifically, if the resource management account agrees to the fault processing user's request, returning a scheduling confirmation command to the terminal device, and performing the related operation of S303; otherwise, if the resource management account does not agree with the fault processing user's request, returning a scheduling rejection The command is sent to the terminal device, and the scheduling application process is ended. Specifically, if the resource management account agrees to the user of the fault handling user, but there is currently no callable resource, the scheduling suspension command is sent, and the terminal device obtains the available resources at a preset time interval, and if sufficient The resources are executed, and the related operations of S303 are performed.

[0089] In this embodiment, after receiving the scheduling confirmation instruction, the terminal device acquires the usage right of the repair resource corresponding to the repair resource request instruction. Optionally, the use permission may be a dynamic key, and the repair is invoked. Before the resource, the identity of the caller needs to be verified. Therefore, the user can use the dynamic key to perform the verification. Line authentication operation to obtain the usage rights of the resource. After obtaining the usage right of the repair resource, the terminal device adds the permission information to the permission parameter of the fault processing user, and the fault processing user can call the corresponding account name or the corresponding device or the identity certification information. The above repair resources repair the database failure.

[0090] Optionally, in this embodiment, after the fault processing user completes the repair of the fault event information, after S1 05, the terminal device applies the permission content of the repair resource to the permission parameter of the fault processing user. Delete, and/or adjust the calling rules of the repair resource, and adjust the usage status of the corresponding repair resource to idle, so that other users can make the call request.

In the embodiment of the present invention, the fault handling user can apply for additional fault repair resources through the terminal device, so that the fault of the database can be repaired more quickly.

FIG. 4 is a flowchart showing a specific implementation of a database failure response method S101 according to a fourth embodiment of the present invention. As shown in FIG. 4, with respect to the embodiment shown in FIG. 1 to FIG. 3, a database fault response method provided by the embodiment further includes S401~S403, and the following details are as follows:

[0093] In S401, if it is detected that the database has a fault condition, the fault feature parameter of the fault condition is acquired.

[0094] In this embodiment, the terminal device can determine whether the database has a fault condition by using a built-in fault detection algorithm. In contrast, the terminal device can also obtain the fault triggering command sent by another device or the database server to learn the database. Is there a fault condition?

[0095] In this embodiment, after detecting that the database has a fault condition, the terminal device acquires a fault feature parameter of the database by using a preset fault feature parameter extraction algorithm. The state operation data includes but is not limited to: a data redundancy rate of the database, a decrease ratio of the average read/write rate of the database, a data storage condition of each partition in the database, an abnormality of the storage address of each partition, and a running state of the database medium. , operation overflow rate, etc.

[0096] Optionally, if the terminal device determines that the database has a fault condition by using a fault triggering command sent by the other device or the database server, the fault triggering instruction includes an operating parameter of the database. The terminal device determines the module and function of the database abnormality by matching the running parameter with the preset standard operating parameter, and uses the operating parameter corresponding to the module and the function as the fault feature parameter. [0097] In S402, the fault repairing scheme matching the fault feature parameter is determined based on a preset fault repair scheme determining algorithm.

[0098] In this embodiment, the preset fault repairing scheme determining algorithm is specifically: the terminal device matches the extracted fault feature parameter with the fault feature parameter of each fault repairing scheme, and then determines the corresponding fault feature parameter. Fault repair plan. The fault repair solution is stored in the repair solution library.

[0099] In this embodiment, the preset fault repairing scheme determining algorithm may further be: the terminal device may cause the fault according to the fault characteristic parameter, such as the location where the fault occurs, the affected functional module, and the fault operating parameter. The multiple causes are generated, and the preset fault cause determining algorithm is used to perform the troubleshooting, and then the abnormal information that causes the fault is determined, and the repairing scheme corresponding to the fault is extracted from the repairing solution resource library according to the abnormality information.

[0100] In S403, the fault event f π is generated according to the fault repairing scheme and the fault feature parameter.

[0101] In this embodiment, the terminal device encapsulates the acquired fault feature parameter and the fault repair solution matched with the fault feature parameter in the fault event information to generate fault event information.

[0102] In the embodiment of the present invention, after detecting that the database is faulty, the terminal device actively acquires the fault feature parameter of the fault condition and matches the corresponding fault repair solution, thereby improving the fault repairability. This in turn improves the repair efficiency.

[0103] FIG. 5 is a flowchart showing a specific implementation of a method for responding to a database failure according to a fifth embodiment of the present invention. As shown in FIG. 5, with respect to the embodiment shown in FIG. 2, the method for responding to a database failure provided by this embodiment further includes the following steps, which are detailed as follows:

[0104] Further, before the obtaining the fault event information of the database, the method further includes:

[0105] In S5011, a fault repair scheme of other databases is acquired at a preset time interval.

[0106] In this embodiment, in addition to generating a fault repair solution by using the fault repair data of the fault processing user, the terminal device may also expand the preset repair solution database by performing a fault repair scheme sharing between other database servers. The amount of the program.

[0107] In this embodiment, the terminal device can be used to repair fault event information of a database. In this case, other databases can be in the same database system as the database, and pass through the database system. The network is connected, so the terminal device can also obtain the fault repair solution stored in the repair solution library of other databases through the internal network of the database system.

[0108] In this embodiment, the terminal device may also be used to repair fault event information of multiple databases of a database system. In this case, other databases may be databases located outside the database system, and thus the terminal device passes The external communication network communicates with other databases, and obtains fault recovery plans of other databases at preset intervals.

[0109] In S5012, the fault repairing scheme sent by the server corresponding to the database is received at a preset time interval.

In this embodiment, in addition to obtaining a new fault repair solution from the repair solution library of other databases, the terminal device may obtain the latest updated fault repair solution through the upper-level server corresponding to the database. The superior server can be: A server that performs update operations such as version updates on the database. The upper-level server uploads a fault repair solution for a version vulnerability or a common problem in a preset time. The terminal device can obtain a fault repair solution corresponding to the version information of the database through the upper server.

[0111] In this embodiment, the upper-level server may also be a server dedicated to collecting fault repair solutions of various vendors and regional databases. The terminal device obtains the fault repairing scheme corresponding to different fault repairing users at home and abroad by the upper-level server, and greatly improves the number of schemes of the repairing scheme library.

[0112] In S502, the fault repairing scheme is added to the preset repair scheme library.

[0113] In this embodiment, the terminal device uploads the fault repairing scheme collected in S5011 and S5012 to the preset repair scheme database, thereby achieving the purpose of intelligent learning of the repair scheme library.

[0114] In the embodiment of the present invention, by learning the fault repair solution from other databases or upper-level servers, the repair range and the repair type of the terminal device can be improved, and the repair efficiency of the database is improved.

It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution sequence, and the execution order of each process should be determined by its function and internal logic, and should not be implemented by the implementation process of the embodiment of the present invention. Any restrictions.

FIG. 6 is a structural block diagram of a response terminal of a database fault according to an embodiment of the present invention. The unit included in the response terminal of the database fault is used to execute each step in the embodiment corresponding to FIG. 1. With Please refer to the related description in the embodiment corresponding to FIG. 1 and FIG. For the convenience of explanation, only the parts related to the present embodiment are shown.

[0117] Referring to FIG. 6, the response terminal of the database failure includes:

[0118] The fault event information obtaining module 61 is configured to acquire fault event information of the database, where the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter; [0119] the fault handling user determines The module 62 is configured to determine, according to the fault feature parameter, a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user; [0120] a fault event monitoring process starting module 63, And configured to start a fault event monitoring process, to collect the fault repair data generated by the fault handling user to repair the fault event information, and the fault repair result; [0121] an audit account information pushing module 64, configured to use the fault repair result Pushing to the audit account corresponding to the fault handling user;

[0122] The fault repair confirmation command receiving module 65 is configured to close the fault event monitoring process if receiving the fault repair confirmation command returned by the audited account.

[0123] Optionally, the responding terminal of the database failure further includes:

[0124] a repair feature parameter matching module, configured to extract a repair feature parameter of the fault repair data, and match the repair feature parameter with a preset repair plan library;

[0125] a fault repairing scheme, a new module, configured to create a fault repairing scheme if the repairing feature parameter does not have a fault repairing scheme matching the preset repairing scheme database;

[0126] The fault repairing solution learning module is configured to import the repair feature parameter into the newly created fault repair solution, and store it in the preset repair solution library.

[0127] Optionally, the fault event monitoring process startup module 63 includes:

[0128] a repair resource request instruction receiving module, configured to receive a repair resource request instruction initiated by the fault repair user, and generate resource scheduling information based on the repair resource request instruction;

[0129] a repair resource requesting module, configured to determine, according to a preset resource management responsibility list, a resource management account corresponding to the repair resource request instruction, and push the resource scheduling information to the resource management account; [0130] repairing resources a permission adding module, configured to receive a scheduling confirmation instruction returned by the resource management account

And adding the usage right of the repair resource corresponding to the repair resource request instruction to the permission parameter of the fault repair user. [0131] Optionally, the fault event information obtaining module 61 includes:

[0132] a fault feature parameter extraction module, configured to acquire a fault feature parameter of the fault condition if a fault condition of the database is detected;

[0133] a fault repairing scheme determining module, configured to determine, according to a preset fault repairing scheme determining algorithm, the fault repairing scheme that matches the fault feature parameter;

[0134] The fault event information generating module is configured to generate the fault event information according to the fault repairing scheme and the fault feature parameter.

[0135] Optionally, the responding terminal of the database failure further includes:

[0136] a first repair solution acquisition module, configured to acquire a fault repair solution of another database at a preset time interval; and/or

[0137] a second repairing solution acquiring module, configured to receive, by using a preset inter-time interval, a fault repairing scheme sent by a server corresponding to the database;

[0138] A fault repair scheme library adding module, configured to add the fault repair scheme to the preset repair scenario library.

[0139] Therefore, the response terminal of the database failure provided by the embodiment of the present invention can also obtain the fault event user corresponding to the fault event information by acquiring the fault event information of the database, and push the fault event information to the determined fault processing user. Therefore, the user can repair the faults included in the database according to the fault characteristic parameters included in the fault event information and the fault repair scheme matched with the fault feature parameters, and the response terminal of the database fault will initiate the fault event. The monitoring process is used to collect the fault repair data obtained by the fault-solving user in the process of repairing the fault event information, and the fault repair result generated after the repair is completed, and automatically push the fault repair result to the audit corresponding to the fault-processing user. The account is used to confirm whether the fault event information has been processed. If the fault repair confirmation command returned by the audit account is received, it indicates that the fault repair event has been correctly repaired, and the fault response process can be ended. Compared with the existing response technology of the database failure, the embodiment of the present invention can reduce the fault occurrence to the fault discovery after determining that the database has a fault event, that is, feeding the fault condition to the corresponding fault processing user. The purpose of the fault is to achieve the purpose of reporting the fault condition. It is not necessary for the user to log in to the database frequently to confirm whether there is a fault event and to avoid the fault situation. On the other hand, after obtaining the repair result, the embodiment of the present invention pushes the corresponding repair result to the corresponding one. Review the account, so that the repair results go through a multiple review process to ensure the accuracy of the repair results

FIG. 7 is a schematic diagram of a terminal device according to another embodiment of the present invention. As shown in FIG. 7, the terminal device 7 of this embodiment includes: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and operable on the processor 70, such as a database failure response program. . The processor 70 executes the steps in the computer program 72 to implement the above-described respective database failure response method embodiments, such as S101 to S105 shown in FIG. Alternatively, the processor 70 executes the computer program 72 to implement the functions of the various units in the various apparatus embodiments described above, such as the functions of the modules 61 to 65 shown in FIG.

[0141] Illustratively, the computer program 72 may be divided into one or more units, the one or more units being stored in the memory 71 and executed by the processor 70 to complete the present invention. The one or more units may be a series of computer program instructions that are capable of performing a particular function, and are used to describe the execution of the computer program 72 in the terminal device 7. For example, the computer program 72 can be divided into an operation fault event information acquisition module, a fault processing user determination module, a fault event monitoring process startup module, an audit account information push module, and a fault repair confirmation command receiving module. The specific functions of each unit are as follows:

[0142] a fault event information obtaining module, configured to acquire fault event information of the database, where the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter;

[0143] a fault processing user determining module, configured to determine, according to the fault characteristic parameter, a fault processing user corresponding to the fault event information, and push the fault event information to the fault processing user;

[0144] a fault event monitoring process startup module, configured to start a fault event monitoring process, to collect fault repair data generated by the fault handling user to repair the fault event information, and a fault repair result;

[0145] an audit account information pushing module, configured to push the fault repair result to an audit account corresponding to the fault processing user;

[0146] The fault repair confirming instruction receiving module is configured to close the fault event monitoring process if receiving the fault repair confirming instruction returned by the audited account. .

[0147] The terminal device 7 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device may include, but is not limited to, a processor 70 and a memory 71. It will be understood by those skilled in the art that FIG. 7 is only an example of the terminal device 7, and does not constitute a limitation on the terminal device 7. To include more or less components than illustrated, or to combine certain components, or different components, for example, the terminal device may also include input and output devices, network access devices, buses, and the like.

The processor 70 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (Application Specific Integrated).

Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor can be a microprocessor or the processor can be any conventional processor or the like.

The above described embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. It should be included in the scope of protection of the present invention.

Claims

Claim

[Claim 1] A method for responding to a database fault, comprising:

Obtaining fault event information of the database, where the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter;

Determining a fault handling user corresponding to the fault event information based on the fault feature parameter

And pushing the fault event information to the fault handling user;

The fault event monitoring process is started to collect the fault repair data generated by the fault handling user to repair the fault event information, and the fault repair result; and the fault repair result is pushed to the audit account corresponding to the fault processing user; The fault event monitoring process is closed when the fault repair confirmation command returned by the audited account is returned.

[Claim 2] The response method according to claim 1, wherein the response method of the database failure further includes:

Extracting a repair feature parameter of the fault repair data, and matching the repair feature parameter with a preset repair plan library;

If the repair feature parameter does not have a fault repair solution matching the preset repair plan library, create a fault repair solution;

And importing the repair feature parameter into the newly created fault repair solution, and storing the file in the preset repair plan library.

[Claim 3] The response method according to claim 1, wherein the triggering a fault event monitoring process is configured to collect fault repair data and fault repair results generated by the fault processing user to repair the fault event information , including:

Receiving, by the fault processing user, a repair resource request instruction, and generating resource scheduling information based on the repair resource request instruction;

Determining, according to a preset resource management responsibility list, a resource management account corresponding to the repair resource request instruction, and pushing the resource scheduling information to the resource management account; if receiving a scheduling confirmation instruction returned by the resource management account, Adding the usage right of the repair resource corresponding to the repair resource request instruction to the permission of the fault processing user In the parameter.

[Claim 4] The response method according to any one of claims 1-3, wherein the obtaining the fault event information of the database comprises:

If it is detected that the database has a fault condition, acquiring a fault feature parameter of the fault condition;

Determining an algorithm based on a preset fault repair scheme to determine the fault repair scheme that matches the fault feature parameter;

The fault event information is generated according to the fault repair scheme and the fault feature parameter.

[Claim 5] The response method according to claim 2, wherein the response method further comprises

Obtaining a fault repair scheme of another database at a preset time interval; and/or receiving a fault repair scheme sent by a server corresponding to the database at a preset time interval, adding the fault repair scheme to the preset Repair the solution library.

[Claim 6] A response terminal for database failure, comprising:

The fault event information obtaining module is configured to acquire fault event information of the database, where the fault event information includes a fault feature parameter and a fault repairing scheme matching the fault feature parameter;

a fault processing user determining module, configured to determine, according to the fault characteristic parameter, a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user;

The fault event monitoring process startup module is configured to start a fault event monitoring process, to collect the fault repair data generated by the fault handling user to repair the fault event information, and the fault repair result;

An audit account information pushing module, configured to push the fault repair result to an audit account corresponding to the fault processing user;

The fault repair confirmation command receiving module is configured to repair the fault returned by the audited account. If the instruction is confirmed, the fault event monitoring process is closed.

[Claim 7] The response terminal according to claim 6, wherein the response terminal of the database failure further includes:

a repair feature matching module, configured to extract a repair feature parameter of the fault repair data, and match the repair feature parameter with a preset repair plan library;

The fault repairing scheme is a new module, configured to create a fault repairing scheme if the repairing feature parameter does not have a fault repairing scheme matching the preset repairing scheme database.

The fault repair solution learning module is configured to import the repair feature parameter into the newly created fault repair solution, and store the fault repair solution in the preset repair plan library.

[Claim 8] The response terminal according to claim 6, wherein the fault event monitoring process starting module comprises:

a repair resource request instruction receiving module, configured to receive a repair resource request instruction initiated by the fault processing user, generate resource scheduling information based on the repair resource request instruction, and a repair resource application module, configured to use the preset resource management responsibility list, Determining, by the resource management account corresponding to the repair resource request instruction, pushing the resource scheduling information to the resource management account;

And a repair resource permission adding module, configured to add the use permission of the repair resource corresponding to the repair resource request instruction to the permission parameter of the fault processing user, if receiving the scheduling confirmation instruction returned by the resource management account.

[Claim 9] The response terminal according to any one of claims 6-8, wherein the fault event information acquisition module comprises:

a fault feature parameter extraction module, configured to acquire a fault feature parameter of the fault condition if a fault condition of the database is detected;

a fault repairing solution determining module, configured to determine, according to a preset fault repairing scheme determining algorithm, the fault repairing scheme that matches the fault characteristic parameter, and a fault event information generating module, configured to be according to the fault repairing scheme and the The fault characteristic parameter generates the fault event information.

[Claim 10] The response terminal according to claim 7, wherein the response terminal of the database failure further comprises:

a first repair solution acquisition module, configured to acquire a fault repair solution of another database at a preset time interval; and/or

a second repairing solution acquiring module, configured to receive, by using a preset inter-time interval, a fault repairing scheme sent by a server corresponding to the database;

The fault repair solution library adding module is configured to add the fault repair solution to the preset repair plan library.

[Claim 11] A terminal device comprising a memory, a processor, and a computer program stored in the memory and operable on the processor, wherein the processor executes the computer program The steps of the method of any of claims 1 to 5.

[Claim 12] A computer readable storage medium storing a computer program, wherein the computer program is executed by a processor, implementing the method of any one of claims 1 to 5 The steps of the method.