CN110063042B - Database fault response method and terminal thereof - Google Patents

Abstract

A method for responding to a database fault and a terminal thereof, comprising: obtaining fault event information of a database (S101); determining a fault processing user corresponding to the fault event information based on fault characteristic parameters, and pushing the fault event information to the fault processing user (S102 ); start the fault event monitoring process (S103); push the fault repair result to the audit account corresponding to the fault handling user (S104); if the fault repair confirmation instruction returned by the audited account is received, then close the fault event monitoring process ( S105). It solves the existing database failure response technology, which mainly detects the failures contained in the database through the preset failure detection algorithm. The timeliness of database failure repair is low, and may even aggravate the degree of database failure and increase the difficulty of repair. , and the fault handling user needs to frequently log in to the database to check whether there is a fault report, which reduces the problem of the fault handling user's operational efficiency.

Description

A database failure response method and its terminal

technical field

The invention belongs to the technical field of databases, and in particular relates to a database failure response method and a terminal thereof.

Background technique

With the in-depth development of informatization, data storage and extraction operations are inseparable, so the importance of databases has become 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 informatization. However, the existing database fault response technology mainly detects the faults contained in the database through the preset fault detection algorithm, and outputs the corresponding fault report locally in the database. Knowing the failure situation of the database reduces the timeliness of database failure repair, and may even aggravate 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 check whether there is a fault report, which reduces the operating efficiency of the fault handling user.

Contents of the invention

In view of this, the embodiment of the present invention provides a database fault response method and its terminal to solve the existing database fault response technology, mainly detecting faults contained in the database through a preset fault detection algorithm, and The database outputs the corresponding fault report locally. If the fault repair manager does not log in to the database, he will not be able to know the fault situation of the database, thereby reducing the timeliness of database fault repair, and may even aggravate the fault degree of the database and increase the repair time. difficulty. On the other hand, the fault handling user needs to frequently log in to the database to check whether there is a fault report, which reduces the operating efficiency of the fault handling user.

The first aspect of the embodiments of the present invention provides a method for responding to a database failure, the method for responding to a database failure includes:

Acquiring fault event information of the database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan matching the fault characteristic parameters;

Based on the fault characteristic parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user;

Start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

Pushing the fault repair result to the audit account corresponding to the fault handling user;

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

The second aspect of the embodiments of the present invention provides a database fault response terminal, the database fault response terminal includes:

Acquiring fault event information of the database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan matching the fault characteristic parameters;

Based on the fault characteristic parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user;

Start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

Pushing the fault repair result to the audit account corresponding to the fault handling user;

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

A third aspect of the embodiments 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, when the processor executes the computer program Implement the following steps:

Acquiring fault event information of the database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan matching the fault characteristic parameters;

Based on the fault characteristic parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user;

Start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

Pushing the fault repair result to the audit account corresponding to the fault handling user;

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

A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

Acquiring fault event information of the database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan matching the fault characteristic parameters;

Based on the fault characteristic parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user;

Start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

Pushing the fault repair result to the audit account corresponding to the fault handling user;

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

Implementing a database fault response method and its terminal provided by the embodiment of the present invention has the following beneficial effects:

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 processing user, so that the user can Parameters and a fault repair plan that matches the fault characteristic parameters to repair the faults contained in the database. At the same time, the database fault response terminal will start the fault event monitoring process to collect fault processing in real time. The user is repairing the fault event information process , the fault repair data obtained, and the fault repair result generated after the repair is completed, and the fault repair result is automatically pushed to the audit account corresponding to the fault handling user to confirm whether the fault event information has been processed. The fault repair confirmation instruction returned by the account indicates that the fault repair event has been correctly repaired, and the fault response process can be ended. Compared with the existing database failure response technology, the embodiment of the present invention can immediately feed back the failure situation to the corresponding failure handling user when it is determined that there is a failure event in the database, thereby reducing the time difference between the occurrence of the failure and the discovery of the failure. To achieve the purpose of real-time reporting of fault conditions, users do not need to frequently log in to the database to confirm whether there are fault events, and avoid the aggravation of fault conditions. On the other hand, in the embodiment of the present invention, after obtaining the repair result, the corresponding repair result is pushed to the corresponding audit account, so that the repair result goes through an additional review process, ensuring the accuracy of the repair result.

Description of drawings

Fig. 1 is the implementation flowchart of a kind of response method of database failure provided by the first embodiment of the present invention;

Fig. 2 is a specific implementation flowchart of a database fault response method provided by the second embodiment of the present invention;

FIG. 3 is a specific implementation flowchart of a database fault response method S103 provided in the third embodiment of the present invention;

FIG. 4 is a specific implementation flowchart of a database fault response method S101 provided in the fourth embodiment of the present invention;

Fig. 5 is a specific implementation flowchart of a database failure response method provided by the fifth embodiment of the present invention;

FIG. 6 is a structural block diagram of a database fault response terminal provided by an embodiment of the present invention;

Fig. 7 is a schematic diagram of a terminal device provided by an embodiment of the present invention.

detailed description

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

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 processing user, so that the user can Parameters and a fault repair plan that matches the fault characteristic parameters to repair the faults contained in the database. At the same time, the database fault response terminal will start the fault event monitoring process to collect fault processing in real time. The user is repairing the fault event information process , the fault repair data obtained, and the fault repair result generated after the repair is completed, and the fault repair result is automatically pushed to the audit account corresponding to the fault handling user to confirm whether the fault event information has been processed. The fault repair confirmation command returned by the account indicates that the fault repair event has been correctly repaired, and the fault response process can be ended, which solves the existing database fault response technology, mainly through the preset fault detection algorithm to detect Include faults, and output the corresponding fault report locally in the database. If the fault repair manager does not log in to the database, he will not be able to know the fault status of the database, thereby reducing the timeliness of database fault repair, and may even aggravate the database fault. degree, increasing the difficulty of restoration. On the other hand, the fault handling user needs to frequently log in to the database to check whether there is a fault report, which reduces the operating efficiency of the fault handling user.

In the embodiment of the present invention, the execution subject of the process is a terminal device installed with a database fault response program, and the terminal device includes terminals such as servers, computer devices, and tablet computers, which are used to respond to fault events of various databases, and respond to fault events that occur Perform corresponding response operations. In particular, the terminal device is a fault response device connected to the database system, receives fault event information sent by each database through the network of the database system, and then repairs the faults of the databases included in the entire database system. Fig. 1 shows the implementation flow chart of the response method of the database fault provided by the first embodiment of the present invention, detailed description is as follows:

In S101, the fault event information of the database is acquired; wherein, the fault event information includes fault characteristic parameters and a fault recovery solution matching the fault characteristic parameters.

In this embodiment, if the terminal device receives the fault event information of the database, it triggers the response process of the database fault, thereby repairing the fault condition in the database. Specifically, the fault event information includes a data category, and each time a terminal device receives a piece of data information, it will read the data category of the data information, and determine whether the data information is fault event information according to the preset data category identification list , if yes, perform the operation of S101.

In this embodiment, the terminal device can determine whether there is a fault in the database through the local database fault detection program, and then obtain the fault event information corresponding to the database; the terminal device can also detect the fault event information through an independent database fault detection terminal. The fault information contained in the database, and then through the communication connection between the terminal device and the database fault detection terminal, obtains the fault event information sent by it.

In this embodiment, the failure event information includes failure characteristic parameters, which are specifically used to indicate the specific circumstances of the failure of the database, including but not limited to: the location of the failure, failure level, operating data of the database failure module, etc. , so that the user can locate the cause of the fault and the database module affected according to the fault characteristic parameters, so as to determine whether business support through the backup database is required and the time required for repair before repairing.

In this embodiment, the fault event information also includes a fault recovery solution that matches the fault characteristic parameters. The inspection terminal for terminal equipment or database faults can match the collected fault characteristic parameters with the preset repair plan library, and automatically generate the recommended fault repair plan corresponding to the fault, so that when users receive fault event information, they can Refer to this fault recovery plan to perform fault recovery on the database. It should be noted that the fault recovery plan contained in the fault event information may be one, or two or more. In particular, if the fault event information contains two or more fault recovery plans, it may indicate that the database failure The reason may be one of two or more fault causes, and the terminal equipment cannot be accurately located. Therefore, the fault repair plan corresponding to multiple fault causes is recommended to the user. After locating the fault cause in the database, the user can select one of them. The failure fix fixes it.

Optionally, in this embodiment, if the terminal device is used to detect failures of multiple databases, the failure event information may further include database identifiers, and the terminal device may locate the faulty database based on the database identifiers. In particular, the terminal device can prompt the user of the failed database by marking red or flashing on the database map marked with all databases.

In S102, based on the fault feature parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user.

In this embodiment, the terminal device extracts the fault characteristic parameters contained in 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 above user as the fault handling user . Specifically, if the fault characteristic parameters correspond to multiple fault modules or fault functions, and the multiple fault modules or fault functions are managed by different users, then the fault event information corresponds to multiple fault processing users, and the fault event information Information is simultaneously pushed to multiple troubleshooting users. Preferably, the terminal device decomposes the fault event information into a plurality of fault sub-event information based on different fault modules or fault functions, and pushes each fault sub-event information to corresponding fault handling users.

In this embodiment, after determining the fault handling user, the terminal device sends fault event information to the user equipment according to querying the user equipment corresponding to the fault handling user and the communication address of the user equipment. Optionally, the terminal device can also generate a fault processing event in the office system corresponding to the fault processing user according to the fault processing user, import the fault event information into the fault processing event, and push the fault processing event to Give the troubleshooting user the corresponding account in the office system.

In S103, a fault event monitoring process is started to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information.

In this embodiment, after receiving the fault event information, the fault handling user will perform a repair operation on the fault condition of the database, so as to manually repair the faults that cannot be automatically repaired in the database. At the same time, the terminal device also starts the fault event monitoring process for collecting fault repair data generated when the fault handling user repairs the fault situation corresponding to the fault event information. Specifically, the terminal device will start an independent thread, and continuously monitor the parameter modification operation in the database through this thread, and the parameters include the operating parameters of the database, script files, table structures, changes in stored data, and the like. The terminal device stores the obtained fault recovery data in a storage area corresponding to the fault event information, and the storage area includes an event identifier of the fault event information.

In this embodiment, the terminal device can simultaneously open multiple threads for collecting fault repair data of different fault event information. Database fault inspection terminal or terminal equipment may detect multiple faults in the database within a certain period of time, thereby generating multiple fault event information. Therefore, in order to determine the repair status corresponding to each fault event information, the terminal device opens multiple Threads, each thread detects fault repair data corresponding to a fault event information, and stores it in its corresponding storage area.

In this embodiment, the method for the terminal device to collect fault repair data is as follows: the terminal device obtains various parameters in the database at a preset time interval, and compares the currently collected parameters with the parameters corresponding to the previous collection time. Compare and determine the changed parameters, and use the changed parameters as the fault repair data of this repair process, so as to realize incremental storage of fault repair data, so as to reduce the data volume of fault repair data and the storage pressure of terminal equipment .

In this embodiment, if the terminal device receives the fault repair completion instruction sent by the fault processing user, it determines that the fault event information has been repaired, and recognizes the processing result included in the fault repair completion instruction as the fault repair result. Optionally, if the terminal device does not detect that the parameters of the database have changed beyond the preset maximum repair waiting time, it means that the user will no longer repair it, and it also indicates that the repair operation has been completed. Therefore, in this case , the terminal device will also recognize that the fault event information has been processed, and obtain the corresponding fault repair result according to the current operation status of the database.

Optionally, in this embodiment, when the terminal device obtains the fault repair result, it may suspend collecting the fault repair data. In this case, if the terminal device receives the fault repair confirmation instruction returned by the audit account, then perform the relevant operations of S105; otherwise, if the terminal device does not receive the fault repair confirmation instruction returned by the audit account, restart the fault event Monitor the process to continue collecting fault recovery data.

In S104, the fault repair result is pushed to an audit account corresponding to the fault handling user.

In this embodiment, after determining that the fault event information in the database has been repaired, the terminal device performs an operation of approving and confirming the fault processing result to ensure that the fault repair result is correct. The terminal device will query the audit account corresponding to the troubleshooting user who performs the repair operation. The audit account can be the superior user of the troubleshooting user, or the administrator of the database. The administrator of the database is responsible for the monitoring management and authority of the entire database.

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

Corresponding to the method of pushing to the fault handling user, in this embodiment, the method for the terminal device to push the fault handling result to the audit account includes: after the terminal determines the audit account, query the device corresponding to the audit account and the communication of the device. address, and send the fault handling result to the device. The push method includes: the terminal device generates a fault review event in the office system, imports the fault processing result into the fault review event, and pushes the fault review event to the review account corresponding to the fault processing user in the office system.

In S105, if a failure repair confirmation instruction returned by the audited account is received, the failure event monitoring process is closed.

In this embodiment, when the audit account receives the fault processing result pushed by the terminal device, it can determine whether the fault repair operation has been completed based on the fault processing result. If the audit account agrees with the fault handling result and confirms that the fault repair operation has been completed, a fault repair confirmation command will be generated and sent to the terminal device; if the audit account does not agree with the fault handling result, the fault handling user needs to handle the fault again After the event is repaired, a fault re-recovery command is generated to the terminal device. In this case, if the terminal device receives the fault re-recovery command, it returns to S102 to prompt the fault handling user to process the fault event again.

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 there is no need to collect repair data for this event, so the fault event monitoring will be closed process, and encapsulate the fault repair data and corresponding fault repair results in a data package, and save the data package as a repair record of the database.

As can be seen from the above, the method for responding to a database fault provided by the embodiment of the present invention determines the fault handling user corresponding to the fault event information by obtaining the fault event information of the database, and pushes the fault event information to the determined fault processing user , so that the user can repair the fault contained in the database according to the fault characteristic parameters contained in the fault event information and the fault repair plan matching the fault characteristic parameters. At the same time, the response terminal of the database fault will start the fault event monitoring process , to collect the fault repair data obtained by the fault handling user in the process of repairing the fault event information in real time, as well as the fault repair result generated after the repair is completed, and automatically push the fault repair result to the corresponding audit account of the fault handling user, so as to Confirm whether the fault event information has been processed. If the fault repair confirmation instruction returned by the audit account is received, it means that the fault repair event has been correctly repaired, and the fault response process can be ended. Compared with the existing database failure response technology, the embodiment of the present invention can immediately feed back the failure situation to the corresponding failure handling user when it is determined that there is a failure event in the database, thereby reducing the time difference between the occurrence of the failure and the discovery of the failure. To achieve the purpose of real-time reporting of fault conditions, users do not need to frequently log in to the database to confirm whether there are fault events, and avoid the aggravation of fault conditions. On the other hand, in the embodiment of the present invention, after obtaining the repair result, the corresponding repair result is pushed to the corresponding audit account, so that the repair result goes through an additional review process, ensuring the accuracy of the repair result.

FIG. 2 shows a specific implementation flowchart of a method for responding to a database failure provided by the second embodiment of the present invention. Referring to FIG. 2, compared to the embodiment described in FIG. 1, a database failure response method provided in this embodiment further includes S201-S203, which are described in detail as follows:

Further, if the fault repair confirmation instruction returned by the audited account is received, after closing the fault event monitoring process, it also includes:

In S201, extract the repair feature parameters of the fault repair data, and match the repair feature parameters with a preset repair solution library.

In this embodiment, after completing the fault repair operation of the database, the terminal device will learn the repair process of the fault handling user this time, so as to increase the number of solutions in 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 characteristic parameters from the fault repair data, wherein the repair characteristic parameters are specific Parameters for modifying the database when users eliminate fault event information for fault handling. As mentioned above, the parameters include one or a combination of at least two of the following: operating parameters of the database, script files, table structures, and changes in stored data. Optionally, the terminal device can also compare the database parameters at the moment when the fault occurs and the database parameters when the fault is repaired one by one, and then obtain the repair characteristic parameter.

In this embodiment, the terminal device is preset with a repair plan library for recording fault repair plans corresponding to different fault types. Wherein, the repair solution library can be stored in the built-in storage module of the terminal device. In this case, the terminal device can directly read the local storage module to obtain the data contained in the repair solution library; the repair solution library can also be Stored in an independent database server or other terminal device, in this case, the terminal device needs to establish a communication connection with the database server or other terminal device, and send a call request for the repair plan library to obtain the repair plan library. data.

In this embodiment, after the terminal device obtains the repair feature parameters, it will match the repair feature parameters of each fault repair plan contained in the repair plan library, so as to determine whether the means of the fault repair has been recorded in the repair plan library . Since the repair feature parameter is extracted from the fault repair data in the process of repairing the fault event information, the repair feature parameter can represent a corresponding fault repair solution when the user performs database repair. If the repair feature parameters match any fault repair plan, it means that the repair methods of the two are consistent and belong to the same fault repair plan; if the repair feature parameters do not match any fault repair plan in the repair plan library, it means that the fault The repair process corresponding to the repair data belongs to a new repair plan, so the operations of S202 and S203 are performed to add the new repair plan to the repair plan library.

In S202, if there is no fault repair solution matching the repair feature parameter in the preset repair solution library, create a new fault repair solution.

In this embodiment, if the terminal device cannot find a fault repair solution that matches the repair feature parameters in the repair solution library, it creates a new fault repair solution in the repair solution library to record the failure repair method that has not been included. Optionally, the terminal device can also create a new fault repair plan locally, and send it to the repair plan library after the generation is completed, so that the repair plan library can store the fault repair plan.

In this embodiment, the fault recovery plan is specifically a plan template, which includes multiple contents to be filled in and some content in a standard format, and a plan unique identification code is set for the plan module. Specifically, the fault recovery solution templates corresponding to each recovery solution library may be different, therefore, the terminal device needs to obtain the solution template from the recovery solution library before creating a new fault recovery solution.

In S203, import the repair feature parameters into the newly created fault repair solution, and store them in the preset repair solution library.

In this embodiment, after creating a fault repair plan, the terminal device imports each parameter item included in the extracted repair feature parameters into a position corresponding to the fault repair plan. Preferably, the terminal device also imports the fault characteristic parameters in the fault event information into the fault repair plan, so that when determining the fault repair plan corresponding to the fault event information in the future, based on the fault event information imported when the fault repair plan is established, Determine if the two match.

In this embodiment, after the terminal device imports the repair feature parameters into the fault repair plan, the fault repair plan has been established, so the fault repair plan is stored in the repair plan library, so that when a similar fault situation is encountered , the terminal device can automatically repair the database directly according to the repair operation of the fault repair plan, or when encountering a related fault situation, the terminal device can also push the fault repair plan to the fault handling user for reference.

In the embodiment of the present invention, after each repair is completed, the repair characteristic parameters corresponding to the repair operation are obtained to determine whether the repair operation has been recorded, and a new fault repair method will be created for the new database repair means. The plan is saved, so that after each operation, the learning of the fault repair plan can be realized, and the automatic repair capability of the repair plan library is improved, thereby reducing the number of on-site repairs by the fault handling user and improving the repair efficiency.

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

Further, the starting fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information includes:

In S301, a repair resource request instruction initiated by the fault handling user is received, and resource scheduling information is generated based on the repair resource request instruction.

In this embodiment, when the fault handling user needs to apply for additional repair resources in the process of repairing the fault time information of the database, he can send a repair resource request command to the terminal device, or generate the above-mentioned The repair resource request instruction, so that the terminal device can apply to the corresponding person in charge for the repair resources required in the fault repair process based on the repair resource request instruction.

In this embodiment, the repair resource request instruction includes the repair resource type and resource quantity required by the user, and in particular, may also include resource call time limit information. The terminal device can generate an interface for filling in the repair resource request information through the display module. After the fault handling user fills in the information and fills in the required information in the interface, a corresponding repair resource request instruction is generated and the application process for additional resource repair instructions is started.

In this embodiment, after receiving the resource repair request instruction initiated by the user, the terminal device generates resource scheduling information for each item of request content based on the resource request content included in the resource repair request instruction.

In S302, according to the preset resource management responsibility list, determine the resource management account corresponding to the repair resource request instruction, and push the resource scheduling information to the resource management account.

In this embodiment, the management responsible person corresponding to each resource is recorded in the storage module of the terminal device, that is, the above-mentioned resource management account. Wherein, the above-mentioned resources include but are not limited to: database resources, network resources, peripheral module resources, authority resources, and the like. 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.

In this embodiment, the terminal device extracts the resource category contained in the resource repair request instruction, and queries the preset resource management responsibility list to determine the resource management responsible person corresponding to the resource category and the resource management account corresponding to the responsible person, And push the resource scheduling information generated in S301 to the resource management account.

Specifically, in this embodiment, the push method is consistent with the push method to the fault handling user, and the resource scheduling information can be directly sent to the terminal device corresponding to the resource management account, or a resource scheduling event can be generated in the office system, And add the resource scheduling event to the to-do event of the resource management account. Preferably, the terminal device also determines the processing time limit of the resource management account according to the fault level of the database and the requested resource type, so that the resource management account can respond to the resource request instruction in time.

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

In this embodiment, after receiving the resource scheduling information pushed by the terminal device, the resource management account will, according to the actual situation, determine to agree to the fault handling user's application for additional repair of resources. Specifically, if the resource management account agrees with the fault handling user's request, a scheduling confirmation instruction is returned to the terminal device, and the relevant operations of S303 are performed; otherwise, if the resource management account does not agree with the fault handling user's request, a scheduling rejection is returned Instructions are given to the terminal equipment, and the scheduling application process is ended. In particular, if the resource management account agrees to the user's application for fault handling, but there is currently no callable resource, a dispatch suspension instruction will be sent, and the terminal device will obtain available resources at a preset time interval. resources, perform the related operations in S303.

In this embodiment, after the terminal device receives the scheduling confirmation instruction, it obtains the use right of the repair resource corresponding to the repair resource request instruction. Optionally, the use right can be a dynamic key, and before invoking the repair resource, The identity of the caller needs to be verified. At this time, the user can use the dynamic key to perform authentication operations to obtain the permission to use the resource. After obtaining the permission to use the repair resources, the terminal device will add the permission information to the permission parameter of the fault handling user. The fault handling user only needs to pass the corresponding account name or corresponding device, or the identification information, to call The above repair resource repairs the failure of the database.

Optionally, in this embodiment, after the fault handling user finishes repairing the fault event information, after S105, the terminal device deletes the permission content of the application for invoking the repair resource in the fault handling user's permission parameters, and /or adjust the invocation rules of the repair resources, and adjust the use status of the corresponding repair resources to idle, so that other users can apply for invocation.

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 shows a specific implementation flowchart of a database failure response method S101 provided in the fourth embodiment of the present invention. Referring to FIG. 4 , compared to the embodiments described in FIGS. 1 to 3 , the method for responding to a database fault provided by this embodiment further includes S401 to S403 in obtaining database fault event information, which are described in detail as follows:

In S401, if it is detected that there is a fault condition in the database, acquire a fault characteristic parameter of the fault condition.

In this embodiment, the terminal device can determine whether there is a fault in the database through the built-in fault detection algorithm; relatively, the terminal device can also know whether there is a fault in the database by receiving fault trigger instructions sent by other devices or database servers Condition.

In this embodiment, when the terminal device detects that there is a fault in the database, it obtains the fault characteristic parameters of the database through a preset fault characteristic parameter extraction algorithm. Among them, the state operation data includes but is not limited to: the data redundancy rate of the database, the reduction ratio of the average read and write rate of the database, the data storage situation of each partition in the database, the abnormal distribution of storage addresses of each partition, and the operation status of the database media , Operational overflow rate, etc.

Optionally, if the terminal device determines that there is a fault in the database through a fault trigger command sent by other devices or the database server, the fault trigger command includes operating parameters of the database. The terminal device determines the abnormal module and function of the database by matching the operating parameters with the preset standard operating parameters, and uses the corresponding operating parameters of the module and function as the fault characteristic parameters.

In S402, based on a preset fault recovery solution determination algorithm, determine the fault recovery solution that matches the fault characteristic parameter.

In this embodiment, the preset algorithm for determining the fault recovery scheme is specifically: the terminal device matches the extracted fault characteristic parameters with the fault characteristic parameters of each fault recovery scheme, and then determines the fault recovery scheme corresponding to the fault characteristic parameters . Wherein, the fault recovery solution is stored in the recovery solution library.

In this embodiment, the preset fault recovery scheme determination algorithm may also be: the terminal device locates multiple faults that may cause the fault according to the fault characteristic parameters, such as the location where the fault occurs, the affected functional modules, and fault operating parameters. According to the abnormal information, the corresponding repair plan is extracted from the repair plan resource library according to the abnormal information.

In S403, the fault event information is generated according to the fault repair solution and the fault characteristic parameters.

In this embodiment, the terminal device encapsulates the acquired fault characteristic parameter and the fault recovery solution matching the fault characteristic parameter into the fault event information to generate the fault event information.

In the embodiment of the present invention, when the terminal device detects a failure in the database, it actively acquires the failure characteristic parameters of the failure and matches the corresponding failure recovery plan, thereby improving the timeliness of failure recovery, and then improving the repair efficiency. efficiency.

FIG. 5 shows a specific implementation flowchart of a method for responding to a database failure provided by a fifth embodiment of the present invention. Referring to FIG. 5, compared to the embodiment described in FIG. 2, a method for responding to a database failure provided by this embodiment further includes the following steps, which are described in detail as follows:

Further, before the acquisition of the failure event information of the database, it also includes:

In S5011, the failure recovery solutions of other databases are obtained at preset time intervals.

In this embodiment, in addition to generating a fault repair plan by fault processing user's fault repair data, the terminal device can also expand the amount of preset repair plan databases by sharing the fault repair plan with other database servers.

In this embodiment, the terminal device can be used to repair the failure event information of a database. In this case, other databases can be in the same database system as the database and connected through the internal network of the database system, so the terminal device can also be connected through The internal network of the database system acquires the fault recovery solutions stored in the recovery solution libraries of other databases.

In this embodiment, the terminal device can also be used to repair the fault event information of multiple databases of a database system. In this case, other databases can be databases located outside the database system, so the terminal device can Communicate with other databases and obtain fault recovery solutions of other databases at preset time intervals.

In S5012, receiving a fault recovery solution sent by the server corresponding to the database at a preset time interval.

In this embodiment, in addition to acquiring new fault recovery solutions from the recovery solution libraries of other databases, the terminal device can also obtain the latest updated fault recovery solution through the upper-level server corresponding to the database. The upper-level server may be: a server performing update operations such as version update on the database. The upper-level server will upload the fault repair plan for version vulnerabilities or common problems at a preset time, and the terminal device can obtain the fault repair plan corresponding to the version information of the database in real time through the upper-level server.

In this embodiment, the upper-level server may also be a server dedicated to collecting fault recovery solutions of various manufacturers and regional databases. The terminal equipment then obtains the fault repair solutions corresponding to different fault repair users at home and abroad through the upper-level server, which greatly increases the number of solutions in the repair solution library.

In S502, the fault recovery solution is added to the preset recovery solution library.

In this embodiment, the terminal device uploads the fault repair solutions collected in S5011 and S5012 to a preset repair solution library, thereby realizing the purpose of intelligent learning of the repair solution library.

In the embodiment of the present invention, by learning the fault repair scheme from other databases or upper-level servers, the repair scope and repair type of the terminal equipment can be improved, and the repair efficiency of the database can be improved.

It should be understood that the sequence numbers of the steps in the above embodiments do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation to the implementation process of the embodiment of the present invention.

FIG. 6 shows a structural block diagram of a database failure response terminal provided by an embodiment of the present invention. The units included in the database failure response terminal are used to execute the steps in the embodiment corresponding to FIG. 1 . For details, please refer to FIG. 1 and related descriptions in the embodiment corresponding to FIG. 1 . For ease of description, only the parts related to this embodiment are shown.

Referring to Fig. 6, the response terminal of the database failure includes:

The fault event information acquisition module 61 is used to obtain the fault event information of the database; wherein, the fault event information includes a fault characteristic parameter and a fault recovery scheme matching the fault characteristic parameter;

A failure handling user determination module 62, configured to determine a failure handling user corresponding to the failure event information based on the failure characteristic parameters, and push the failure event information to the failure handling user;

The fault event monitoring process starting module 63 is used to start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

Audit account information push module 64, configured to push the fault repair result to the audit account corresponding to the fault handling user;

The fault repair confirmation instruction receiving module 65 is configured to close the fault event monitoring process if the fault repair confirmation instruction returned by the audited account is received.

Optionally, the response terminal for the database failure also includes:

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

A fault repair plan creation module, used to create a new fault repair plan if the repair feature parameter does not have a matching fault repair plan in the preset repair plan library;

The fault repair plan learning module is used to import the repair feature parameters into the newly created fault repair plan and store them in the preset repair plan library.

Optionally, the fault event monitoring process start module 63 includes:

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;

The repair resource application module is configured to determine the resource management account corresponding to the repair resource request instruction according to the preset resource management responsibility list, and push the resource scheduling information to the resource management account;

The repair resource permission adding module is configured to add the repair resource usage permission corresponding to the repair resource request instruction to the permission parameter of the fault repair user if the scheduling confirmation instruction returned by the resource management account is received.

Optionally, the fault event information acquisition module 61 includes:

A fault feature parameter extraction module, configured to obtain the fault feature parameters of the fault if it is detected that the database has a fault;

A fault repair plan determination module, configured to determine the fault repair plan that matches the fault characteristic parameters based on a preset fault repair plan determination algorithm;

A fault event information generating module, configured to generate the fault event information according to the fault repair scheme and the fault characteristic parameters.

Optionally, the response terminal of the database fault also includes:

The first repair plan obtaining module is used to obtain fault repair plans of other databases at preset time intervals; and/or

The second repair plan acquisition module is used to receive the fault repair plan sent by the server corresponding to the database at a preset time interval;

The failure recovery solution library adding module is used to add the failure recovery solution to the preset recovery solution library.

Therefore, the database failure response terminal provided by the embodiment of the present invention can also immediately feed back the failure situation to the corresponding failure handling user when it is determined that there is a failure event in the database, thereby reducing the time difference between the occurrence of the failure and the discovery of the failure, and realizing real-time The purpose of reporting failures is to avoid the need for users to frequently log in to the database to confirm whether there are failures, so as to avoid the aggravation of failures. On the other hand, in the embodiment of the present invention, after obtaining the repair result, the corresponding repair result is pushed to the corresponding audit account, so that the repair result goes through an additional review process, ensuring the accuracy of the repair result.

Fig. 7 is a schematic diagram of a terminal device provided by another embodiment of the present invention. As shown in Figure 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 response program for a database failure . When the processor 70 executes the computer program 72, it implements the steps in the above embodiments of the response method for each database failure, such as S101 to S105 shown in FIG. 1 . Alternatively, when the processor 70 executes the computer program 72, it realizes the functions of the units in the above-mentioned device embodiments, such as the functions of the modules 61 to 65 shown in FIG. 6 .

Exemplarily, the computer program 72 can be divided into one or more units, and the one or more units are stored in the memory 71 and executed by the processor 70 to implement the present invention. The one or more units may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process 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 start module, an audit account information push module, and a fault repair confirmation instruction receiving module. The specific functions of each unit are as follows:

A fault event information acquisition module, configured to obtain fault event information from a database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan that matches the fault characteristic parameters;

A failure handling user determination module, configured to determine a failure handling user corresponding to the failure event information based on the failure characteristic parameters, and push the failure event information to the failure handling user;

A fault event monitoring process start module, configured to start a fault event monitoring process, to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information;

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

The fault repair confirmation instruction receiving module is configured to close the fault event monitoring process if the fault repair confirmation instruction returned by the audited account is received. .

The above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still carry out the foregoing embodiments Modifications to the technical solutions recorded in the examples, or equivalent replacement of some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should be included in within the protection scope of the present invention.

Claims (8)

1. A response method for a database fault, characterized in that, comprising: Acquiring fault event information of the database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan matching the fault characteristic parameters; Based on the fault characteristic parameters, determine a fault handling user corresponding to the fault event information, and push the fault event information to the fault processing user; Start the fault event monitoring process to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information; Pushing the fault repair result to the audit account corresponding to the fault handling user; If the fault repair confirmation instruction returned by the audit account is received, the fault event monitoring process is closed, and if the fault repair confirmation instruction returned by the audit account is not received, the fault event monitoring process is restarted; The process of starting a fault event monitoring process to collect fault repair data and fault repair results generated when the fault handling user repairs the fault event information includes: receiving a repair resource request instruction initiated by the fault handling user, and generating resource scheduling information based on the repair resource request instruction; Determine the resource management account corresponding to the repair resource request instruction according to the preset resource management responsibility list, and push the resource scheduling information to the resource management account; If the scheduling confirmation instruction returned by the resource management account is received, the use authority of the repair resource corresponding to the repair resource request instruction is added to the authority parameter of the fault handling user, wherein, if the resource management account agrees to fault handling When the user applies for an application, but currently there is no callable resource, a scheduling suspension instruction is sent until there is a callable resource, and the scheduling confirmation instruction is returned, and the repair resource usage permission corresponding to the repair resource request instruction is added to the In the permission parameters of the fault handling user described above. 2. The response method according to claim 1, wherein the response method of the database fault further comprises: Extracting the repair feature parameters of the fault repair data, and matching the repair feature parameters with a preset repair plan library; If the repair feature parameter does not have a matching fault repair plan in the preset repair plan library, create a new fault repair plan; Importing the repair feature parameters into the newly created fault repair plan, and storing them in the preset repair plan library. 3. The response method according to claim 1 or 2, wherein the acquisition of the failure event information of the database comprises: If it is detected that there is a fault condition in the database, acquiring the fault characteristic parameter of the fault condition; Determining the fault repair plan that matches the fault characteristic parameters based on a preset fault repair plan determination algorithm; The fault event information is generated according to the fault recovery scheme and the fault characteristic parameters. 4. The response method according to claim 2, wherein the response method further comprises: Get failure fixes for other databases at preset intervals; and/or receiving a fault recovery plan sent by a server corresponding to the database at a preset time interval; Adding the failure repair solution to the preset repair solution library. 5. A response terminal for database failure, characterized in that, comprising: A fault event information acquisition module, configured to obtain fault event information from a database; wherein, the fault event information includes fault characteristic parameters and a fault recovery plan that matches the fault characteristic parameters; A failure handling user determination module, configured to determine a failure handling user corresponding to the failure event information based on the failure characteristic parameters, and push the failure event information to the failure handling user; A fault event monitoring process start module, configured to start a fault event monitoring process, to collect fault repair data and fault repair results generated when the fault processing user repairs the fault event information; An audit account information push module, configured to push the fault repair result to the audit account corresponding to the fault handling user; The fault repair confirmation instruction receiving module is used to close the fault event monitoring process if the fault repair confirmation instruction returned by the audit account is received, and restart if the fault repair confirmation instruction returned by the audit account is not received. The failure event monitoring process; The start-up module of the fault event monitoring process includes: A repair resource request instruction receiving module, configured to receive a repair resource request instruction initiated by the fault handling user, and generate resource scheduling information based on the repair resource request instruction; The repair resource application module is configured to determine the resource management account corresponding to the repair resource request instruction according to the preset resource management responsibility list, and push the resource scheduling information to the resource management account; The repair resource permission adding module is configured to add the repair resource usage permission corresponding to the repair resource request instruction to the permission parameter of the fault handling user if the scheduling confirmation instruction returned by the resource management account is received, wherein , if the resource management account agrees to the user's application for fault handling, but there is no callable resource at present, then send the scheduling suspend command until there is a callable resource and return the scheduling confirmation command, and the repair resource request corresponding to the The usage permission of the repair resource is added to the permission parameter of the fault handling user. 6. The response terminal according to claim 5, wherein the response terminal of the database fault further comprises: A repair feature parameter matching module, configured to extract the repair feature parameters of the fault repair data, and match the repair feature parameters with a preset repair plan library; A fault repair plan creation module, used to create a new fault repair plan if the repair feature parameter does not have a matching fault repair plan in the preset repair plan library; The fault repair plan learning module is used to import the repair feature parameters into the newly created fault repair plan and store them in the preset repair plan library. 7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and operable on the processor, characterized in that, when the processor executes the computer program, the computer program according to claim The step of any one of 1 to 4. 8. A computer-readable storage medium, the computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are realized .

Images