WO2019047070A1 - 一种数据库维护方法及其*** - Google Patents

一种数据库维护方法及其*** Download PDF

Info

Publication number
WO2019047070A1
WO2019047070A1 PCT/CN2017/100749 CN2017100749W WO2019047070A1 WO 2019047070 A1 WO2019047070 A1 WO 2019047070A1 CN 2017100749 W CN2017100749 W CN 2017100749W WO 2019047070 A1 WO2019047070 A1 WO 2019047070A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
repair
information
database
terminal
Prior art date
Application number
PCT/CN2017/100749
Other languages
English (en)
French (fr)
Inventor
卢汉利
Original Assignee
富璟科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富璟科技（深圳）有限公司 filed Critical 富璟科技（深圳）有限公司
Priority to CN201780000988.3A priority Critical patent/CN110088744B/zh
Priority to PCT/CN2017/100749 priority patent/WO2019047070A1/zh
Publication of WO2019047070A1 publication Critical patent/WO2019047070A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases

Definitions

  • Invention name A database maintenance method and system thereof
  • the present invention belongs to the field of database technologies, and in particular, to a database maintenance method and system thereof.
  • the maintenance technology of the existing database mainly determines the existence status of the database by the database engineer to collect information on the site and manually analyze the running status of the database, but the method depends on the professional level of the database engineer, and different engineers
  • the detection criteria are inconsistent, resulting in a large difference in the abnormality determination, the detection accuracy is low, and the operating cost is large.
  • the embodiments of the present invention provide a database maintenance method and a system thereof, to solve the existing database maintenance technology, rely on the professional technical level of the database engineer, and the detection standards between different engineers are inconsistent. Therefore, there is a large difference in the abnormality determination, the detection accuracy is low, the operation cost is large, the detection efficiency is low, and the problem of abnormality is often not found.
  • Embodiments of the present invention provide a database maintenance method and system thereof, wherein the database maintenance system includes a detection terminal and a fault response terminal;
  • the maintenance method of the database includes:
  • the detecting terminal acquires running state data of the database based on a patrol algorithm matching a feature of the database;
  • the detecting terminal imports the operating state data into a preset database fault analysis model, and generates fault analysis data corresponding to the operating state data; wherein the fault analysis data includes fault information.
  • the detecting terminal extracts the fault information and the fault warning information included in the fault analysis data, and determines each of the fault information and a repairing scheme corresponding to the fault warning information;
  • the detecting terminal sends the repairing solution to the fault response terminal
  • the fault response terminal receives the repairing scheme sent by the detecting terminal, and respectively performs a repairing operation corresponding to the repairing scheme to repair a fault condition of the database.
  • a database maintenance method and a system thereof provided by embodiments of the present invention have the following beneficial effects: [0012]
  • the embodiment of the present invention does not rely on the expertise of a database engineer to perform troubleshooting on a database, but is based on detecting a terminal.
  • the characteristics of the database itself are matched to the corresponding patrol algorithm, so that the running state data obtained by the patrol algorithm can better characterize whether the database contains the fault condition, and obtain the fault analysis data through the preset database fault analysis model. It can be seen that the above operations do not require the intervention of the database engineer, which reduces the dependence on the level of artificial professional technology, thereby reducing the labor cost and the operating cost of the database, and the inspection algorithm is selected according to the characteristics of different databases, and the detection accuracy is obtained. Also greatly improved.
  • the fault response terminal can also automatically repair the fault condition according to the matched repair scheme, which improves the efficiency of detection and the ambiguity of repair.
  • FIG. 1 is a flowchart of an implementation of a database maintenance method according to a first embodiment of the present invention
  • FIG. 2 is a flowchart of a physical implementation of a database maintenance method S103 according to a second embodiment of the present invention
  • FIG. 3 is a flowchart of a specific implementation of a database maintenance method S203 according to a third embodiment of the present invention
  • FIG. 4 is a flowchart of a specific implementation of a database maintenance method according to a fourth embodiment of the present invention
  • FIG. 5 is a flowchart of a specific implementation of a database maintenance method according to a fifth embodiment of the present invention.
  • FIG. 6 is a flowchart of a specific implementation of a database maintenance method according to a sixth embodiment of the present invention.
  • FIG. 7 is a structural block diagram of a database maintenance system according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a database maintenance system according to another embodiment of the present invention. Embodiments of the invention
  • the embodiments of the present invention solve the existing database maintenance technology, the detection accuracy is low, the operation cost is large, the detection efficiency is low, and the problem of abnormal conditions is often not found.
  • a database maintenance method is applied to a database maintenance system, where the maintenance system of the database includes a detection terminal and a fault response terminal, and the maintenance system of the database maintained by the two terminal devices includes Database.
  • the fault response terminal is specifically a terminal device in which a response program of a database failure is installed.
  • the detection terminal and/or the fault response terminal in the maintenance system can be integrated into the database server, and the database server directly calls the local application to implement the database failure detection and/or failure response operation.
  • the database maintenance system may include multiple database servers, and the detection terminal and the fault response terminal jointly perform maintenance operations on multiple databases in the system.
  • FIG. 1 is a flowchart showing an implementation of a database maintenance method according to a first embodiment of the present invention, which is described in detail as follows:
  • the detecting terminal acquires running state data of the database based on a patrol algorithm matching a feature of the database.
  • the detecting terminal first acquires a feature of the database, where the feature includes but is not limited to one or a combination of at least two: a type of the database, a sender information, a stored amount of data, and The data type, the version information of the database, etc., according to the characteristics of the above database, the basic characteristics of the database can be determined, and the patrol plan corresponding to the patrol algorithm library is obtained by matching the basic characteristics.
  • the detecting terminal may acquire the patrol algorithm by means of a database administrator, in addition to obtaining the patrol algorithm by the upper server, in which case the detecting terminal may receive the corresponding manager.
  • the detecting terminal sends the completed patrol detection algorithm, and after detecting the patrol algorithm, the detecting terminal establishes a correspondence between the database and the patrol algorithm.
  • the detection terminal determines the patrol detection algorithm corresponding to the database for performing the patrol inspection
  • the running state data of the database is obtained.
  • the status running data includes but is not limited to: data redundancy rate of the database, average read/write rate of the database, data storage status of each partition in the database, allocation of storage addresses of each partition, database medium running status, and operation overflow Rate and so on.
  • the detecting terminal imports the operating state data into a preset database failure analysis model, and generates fault analysis data corresponding to the operating state data; wherein the fault analysis data includes fault information and Fault warning information.
  • the detecting terminal stores a database fault analysis model, and is configured to determine, according to the input operating state data, whether the fault state situation is included in the operating state data, and the fault risk situation specifically includes whether the fault has occurred.
  • the fault information, and the fault warning information that may be faulty define the fault information and the fault warning information as multiple risk points, and generate fault analysis data corresponding to the running state data. Therefore, after acquiring the running state data of the database, the detecting terminal imports the running state data into the database fault analysis model to obtain the fault analysis data corresponding to the database.
  • the database analysis model can be obtained by training and learning.
  • the detecting terminal extracts the fault information and the fault warning information included in the fault analysis data, and determines each fault information and a repairing scheme corresponding to the fault warning information.
  • the fault information is specifically: During the patrol inspection, the related information that the database is in a fault state is detected, including the location where the fault occurs, the function affected, and the fault operation parameter.
  • the fault warning information is specifically: During the inspection process, according to the detected operating state, it is predicted that a certain module or function of the database may be abnormal, or the stability and reliability of a certain module or function are lower than the normal level. ⁇ Collect the relevant information of the function or module as the fault warning information. Therefore, the detection terminal is not limited to the point of failure where the failure has occurred, and the risk points that may cause the failure are also repaired.
  • the detecting terminal After the detection terminal determines all the fault information in the fault analysis data and the repair scheme corresponding to the fault warning information, the detecting terminal performs the related operation of S104.
  • the detecting terminal sends the repairing scheme to the fault responding terminal.
  • each repairing solution obtained by the detecting terminal in S103 is sent to the fault responding terminal, so that the fault responding terminal repairs the fault of the database according to the above repairing scheme.
  • the detecting terminal determines a fault response terminal corresponding thereto according to the fault information or the fault early warning information, and The fault information or the repair solution corresponding to the fault warning information is sent to the corresponding fault response terminal for response.
  • the fault response terminal receives the repairing scheme sent by the detecting terminal, and respectively performs a repairing operation corresponding to the repairing scheme to repair a fault condition of the database.
  • the repair operation corresponding to the repair scheme is performed on the database to repair the corresponding fault condition in the database, and the fault condition also includes the fault information.
  • the fault condition corresponding to the fault warning information is performed on the database to repair the corresponding fault condition in the database.
  • the database maintenance method determines the matching patrol algorithm by detecting the characteristics of the database, and then obtains the running state data of the database based on the patrol algorithm; After obtaining the running state data, the terminal imports the data into a preset database failure analysis model, and determines whether the running state data includes a fault condition or a fault early warning situation, and generates corresponding fault analysis data. Then, according to the fault information and the fault warning information included in the fault analysis data, respectively determine the repair scheme corresponding to each information, and then send each repair scheme to the fault response terminal, and perform a corresponding repair operation through the fault response terminal, thereby realizing automatic matching.
  • the database detects and fixes the purpose of the failure.
  • the embodiment of the present invention does not rely on the expertise of the database engineer to perform troubleshooting on the database, but the detection terminal matches the corresponding inspection algorithm based on the characteristics of the database itself, thereby
  • the running state data obtained by the patrol algorithm can better characterize whether the database contains the fault condition, and obtain the fault analysis data through the preset database fault analysis model. It can be seen that the above operation does not require the intervention of the database engineer, thereby reducing the manual expertise.
  • the horizontal dependence reduces the labor cost and the operating cost of the database, and the inspection algorithm is selected according to the characteristics of different databases, and the detection accuracy is also greatly improved.
  • the fault response terminal can also automatically repair the fault condition according to the matched repair scheme, thereby improving the efficiency of detection and the ambiguity of repair.
  • a database maintenance method S103 includes S201 ⁇ S203, which are as follows:
  • the detecting terminal extracts the fault information and the fault warning information included in the fault analysis data, and determines each fault information and the repairing scheme corresponding to the fault warning information, including:
  • the detecting terminal determines the fault information and the fault type corresponding to the fault warning information according to a preset fault type classification algorithm.
  • the detecting terminal determines the fault type of each fault information and the fault warning information according to a preset fault type classification algorithm.
  • the fault type corresponding to the fault information is taken as an example, and the detecting terminal acquires the location of the fault and the affected function included in the fault information, locates the module category to which the fault information belongs, and then runs according to the fault included in the fault information.
  • the parameter determines the corresponding hardware component or program in the module to which the module belongs, thereby obtaining the fault type corresponding to the fault information.
  • the fault warning information can also be determined by the above steps.
  • the detecting terminal divides the multiple fault types into two categories according to the setting of the user, and respectively, one type of fault information and two types of fault information, wherein one type of fault information is specifically allocated
  • the fault response terminal can repair faults of a type of fault information according to the fault repair algorithm, without notifying the fault handling user; and the second type of fault information is specifically that the detecting terminal can perform partial emergency repair, but the fault processing user is required. Manual intervention for repair.
  • the detecting terminal extracts a fault repair algorithm that matches the one type of fault information from the fault repair algorithm library, and The repair scheme is generated according to the fault repair algorithm.
  • the detection terminal is provided with a fault repair algorithm library, which includes a fault repair algorithm corresponding to each type of fault information. Therefore, after determining that the fault information or the fault warning information is a type of fault information, the detecting terminal matches the fault information of the fault with the fault repair algorithm in the fault repair algorithm database, and then determines the fault repair algorithm corresponding thereto. And generating the above repair solution based on the fault repair algorithm and the fault information or the fault warning information.
  • the detecting terminal In S203, if the fault information or the fault warning information is the second type of fault information, the detecting terminal generates a fault handling event corresponding to the type 2 fault information, and submits the fault handling event to The fault responds to the terminal.
  • the detecting terminal needs to notify the fault processing user that the repaired user needs to perform repair, and thus generates two according to the fault information or the fault warning information.
  • the fault handling event corresponding to the fault information of the class.
  • the detecting terminal after detecting the fault handling event, submits the fault handling event to the fault handling user to start the fault repair process.
  • the fault handling user can obtain the fault handling event through the office system or mail, and perform the repair strategy by itself to repair the fault information or the fault warning information.
  • the database is repaired by two different means, thereby improving the flexibility of the database repair, and the simpler and lower authority.
  • the fault can be repaired by the detecting terminal itself.
  • it is recommended to manually intervene and repair, and provide fault handling events including repair suggestions to the fault handling user, thereby reducing the repair of the fault handling user. Difficulty.
  • FIG. 3 is a flowchart showing a specific implementation of S203 in a database maintenance method according to a third embodiment of the present invention. As shown in FIG. 3, with respect to the embodiment shown in FIG. 2, in the database maintenance method provided in this embodiment, S203 includes the following steps, which are as follows:
  • the fault response terminal receives the repairing scheme sent by the detecting terminal, and performs a repairing operation corresponding to the repairing solution to repair the fault condition of the database, including:
  • the fault response terminal receives the fault event information of the database submitted by the detecting terminal, where the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter.
  • the fault response terminal receives the fault information submitted by the detecting terminal through the communication connection with the detecting terminal, so as to process the fault condition corresponding to the fault information.
  • the fault response terminal determines a fault handling user corresponding to the fault event information based on the fault characteristic parameter, and pushes the fault event information to the fault processing user.
  • the fault response terminal 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. Handle users for failures. Specifically, if the fault feature parameter corresponds to multiple fault modes If the faulty function or the faulty function is managed by different users, the fault event information may correspond to multiple fault handling users, and the fault event information may be pushed to multiple fault handling users.
  • the fault response terminal 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.
  • the fault response terminal after determining the fault handling user, 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.
  • the fault response terminal 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 processing event, and the fault processing event is Push to the faulty user on the corresponding account in the office system.
  • the fault response terminal starts a fault event monitoring process to collect fault repair data and fault repair result generated by the fault processing user to repair the fault event information.
  • the fault processing user after receiving the fault event information, performs a repair operation on the fault condition of the database to manually repair the fault that the database cannot be automatically repaired.
  • the fault response terminal also starts a fault event monitoring process, which is used to collect the fault repair data generated by the fault handling user corresponding to the fault condition corresponding to the fault event information.
  • the fault response terminal will initiate an independent thread through which the parameter modification operation in the database is continuously monitored, and the parameters include the running parameters of the database, the script file, the table structure, and the change of the stored data.
  • the fault response terminal 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.
  • the fault response terminal can simultaneously initiate multiple threads for collecting fault repair data of different fault event information.
  • the database failure check terminal or the fault response terminal may check that there are multiple fault conditions in the database within a certain time interval, thereby generating multiple fault event information, so the fault response terminal determines the repair situation corresponding to each fault event information. Then, multiple threads are opened, and each thread detects fault repair data corresponding to one fault event information, and stores them in respective corresponding storage areas.
  • the manner in which the fault response terminal collects the fault repair data is specifically: the fault response terminal Obtaining various parameters in the database at a preset interval, and comparing the currently collected parameters with the parameters corresponding to the previous collection engraving, determining the changed parameters, and using the changed parameters as the The fault repair data of the secondary repair process realizes incremental storage of the fault repair data to reduce the data amount of the fault repair data and the storage pressure of the fault response terminal.
  • the fault response terminal pushes the fault repair result to an audit account corresponding to the fault processing user.
  • the fault processing result is subjected to the operation of confirming and confirming the fault to ensure that the fault repair result is correct.
  • the fault response terminal will query the audit account corresponding to the fault handling user of the repair operation, and the audit account may be the upper user of the fault handling user or the administrator of the database, and the administrator of the database is responsible for the monitoring and management of the entire database. Permissions.
  • 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 handling result and determines that the fault repairing operation has been completed, a fault repair confirmation command is generated and sent to the fault responding terminal; if the auditing account does not agree with the fault processing result, the fault handling user needs to re-resolve the fault. Processing the event for repair processing, generating a fault re-repair command to the fault responding terminal. In this case, if the fault responding terminal receives the fault re-repair command, it returns to perform the operation of S102 to prompt the fault processing user to re-review the fault event. Process it.
  • the embodiment of the present invention when it is determined that there is a fault event in the database, that is, the fault condition is fed back to the corresponding fault processing user, thereby reducing the inter-turn difference between the fault occurrence and the fault finding, thereby realizing the implementation.
  • the purpose of reporting a fault condition is that the user does not need to log in to the database frequently to confirm whether there is a fault event, and the fault condition is intensified.
  • 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.
  • FIG. 4 is a flowchart of a specific implementation of a database maintenance method according to a fourth embodiment of the present invention.
  • a database maintenance method provided by this embodiment is further provided with respect to the embodiment shown in FIG. Contains S401 ⁇ S403, as detailed below:
  • the fault response terminal extracts the repair feature parameter of the fault repair data, and matches the repair feature parameter with a preset repair plan library.
  • the fault response terminal learns the repair process of the fault processing user to improve the number of schemes of the fault repair scheme library.
  • the fault response terminal 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, wherein the repair feature parameter Specifically, the fault handling user eliminates the fault event information and modifies the database parameters.
  • the parameter includes one or a combination of at least two types: database running parameters, script files, table structure, and storage data changes.
  • the fault response terminal 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.
  • the fault response terminal 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 fault response terminal.
  • the fault response terminal may directly read the local storage module to obtain data included in the repair solution library; It can also be stored in a separate database server or other fault response terminal.
  • the fault response terminal needs to establish a communication connection with the database server or other fault response terminal, and send a call request of the repair solution library to obtain the Fix the data in the scenario library.
  • the fault response terminal 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.
  • 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.
  • the fault repair scheme template corresponding to each repair scheme library may be different. Therefore, the fault response terminal needs to obtain the scheme template from the repair scheme library before creating a new fault repair scheme.
  • the fault response terminal imports the repair feature parameter into the newly created fault repair solution, and stores it in the preset repair solution library.
  • each faulty parameter included in the extracted repair feature parameter is imported into the location corresponding to the fault repairing scheme.
  • the fault response terminal further introduces the fault characteristic parameter in the fault event information into the fault repair scheme, so as to determine the fault repair scheme corresponding to the fault event information in the future, and may establish the fault event information imported according to the fault repair scheme. , to determine if the two match.
  • the fault response terminal 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, thereby encountering Similar fault conditions ⁇ , the fault response terminal can automatically repair the database according to the repair operation of the fault repair scheme, or encounter the relevant fault condition.
  • the fault response terminal can also push the fault repair scheme to the fault processing user for reference. .
  • 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. 5 is a flowchart showing a specific implementation of a database maintenance method according to a fifth embodiment of the present invention.
  • a database maintenance method provided by this embodiment further includes the following S501 and S502, which are described in detail as follows:
  • the detecting terminal acquires the processing result of each of the fault information and the fault warning information, and generates a database detection report according to the processing result.
  • the detecting terminal summarizes the fault information returned by the fault responding terminal and the processing result corresponding to the fault warning information.
  • the processing result includes the processing result of the repair success to repair the failure, and also the processing result of the fault determination error.
  • the detection terminal processes the processing result according to each fault information and the fault warning information.
  • Generating a database test report which lists the fault information obtained by the current inspection and the corresponding processing result, and the fault warning information and the corresponding processing result thereof.
  • the database failure rate and resources are also updated. The occupancy situation, so that the user can accurately obtain the fault condition of the entire database according to the query report of the database.
  • the detecting terminal inputs the fault information and the processing result corresponding to the fault warning information into the database fault analysis model to perform training update on the database fault analysis model.
  • the terminal device inputs the processing result corresponding to the fault information and the fault warning information to the database fault analysis model, and the database fault analysis model is used to detect whether the fault data of the database includes the fault condition.
  • the fault information and the fault warning information also include the operating state data corresponding to the occurrence or failure of the database, so the above processing result is input into the fault analysis model, and training and updating thereof can improve the fault of the database. Analyze the accuracy of the model.
  • a database detection report is generated, which is convenient for the user to consult and learn the operation status of the database, so as to map the database. Use decision.
  • the training information of the fault information and the fault warning information is trained and updated on the database analysis model, which can further improve the sensitivity of the database fault analysis model to the fault, thereby improving the accuracy of the detection.
  • FIG. 6 is a flowchart showing a specific implementation of a database maintenance method according to a sixth embodiment of the present invention.
  • the fault response terminal initiates a fault event monitoring process in the database maintenance method provided by the embodiment, to collect the fault processing user and repair the
  • the fault repair data generated by the fault event information and the fault repair result also include the following S601 S603, which are detailed as follows:
  • the fault response terminal receives the repair resource request instruction initiated by the fault repair user, and the resource scheduling information generated according to the repair resource request instruction.
  • the fault processing user needs to apply for additional repair resources, and may send a repair resource request instruction to the fault response terminal, or may be built in through the fault response terminal.
  • Client generating the above repair resource request instruction for fault response
  • the terminal may apply to the corresponding responsible person for the repair resource required in the fault repair process based on the repair resource request instruction.
  • 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 fault response terminal can generate a filling interface for repairing the 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. .
  • the fault response terminal after receiving the user-initiated repair resource request instruction, the fault response terminal generates a resource scheduling information for each request content based on the resource request content included in the repair resource request instruction.
  • the fault response terminal determines, according to a preset resource management responsibility list, a resource management account corresponding to the repair resource request instruction, and pushes the resource scheduling information to the resource management account.
  • the fault response terminal 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 fault response terminal first determines the target object corresponding to the request according to the repair resource request instruction.
  • the fault response terminal adds the usage right of the repair resource corresponding to the repair resource request instruction to the permission of the fault repair user. In the parameter.
  • the resource management account after receiving the resource scheduling information pushed by the fault response terminal, 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 fault response terminal, and performing the related operation of S603; otherwise, if the resource management account does not agree with the fault processing user's request, returning a schedule The command is rejected to the fault responding terminal, and the scheduling application process is terminated.
  • the scheduling suspension command is sent, and the fault responding terminal acquires the available resources at a preset time interval, and if the detected existence exists If sufficient resources are available, the related operations of S603 are performed.
  • the fault response terminal after receiving the scheduling confirmation instruction, acquires the usage right of the repair resource corresponding to the repair resource request instruction, and optionally, the use right may be a dynamic key. Before the resource is repaired, the identity of the caller needs to be verified. After that, the user can use the dynamic key to perform an authentication operation to obtain the permission to use the resource.
  • the fault response terminal After the fault response terminal obtains the use permission of the repair resource, the fault information is added to the permission parameter of the fault processing user, and the fault processing user only needs to pass the corresponding account name or the corresponding device, or the identity certification information. Call the above repair resources to fix the database failure.
  • the fault handling user can apply for additional fault repair resources through the fault response terminal, so that the database fault can be repaired more quickly.
  • FIG. 7 is a structural block diagram of a database maintenance system according to an embodiment of the present invention.
  • the units included in the database maintenance terminal are used to execute the steps in the embodiment corresponding to FIG. 1.
  • please refer to the related description in the embodiment corresponding to FIG. 1 and FIG. For the convenience of explanation, only the portions related to the present embodiment are shown.
  • the database maintenance system includes a database 71, a detection terminal 72, and a fault response terminal 73;
  • the detecting terminal 72 is configured to acquire running state data of the database 71 based on a patrol algorithm matching the features of the database 71;
  • the detecting terminal 72 is configured to import the running state data into a preset database failure analysis model
  • failure analysis data includes failure information and failure warning information
  • the detecting terminal 72 is configured to extract the fault information and the fault warning information included in the fault analysis data, and determine each of the fault information and a repairing scheme corresponding to the fault warning information.
  • the detecting terminal 72 is configured to send the repairing solution to the fault response terminal 73;
  • the fault response end 73 is configured to receive, by the terminal, the repairing scheme sent by the detecting terminal 72, and perform respectively The repairing operation corresponding to the repairing scheme repairs the fault condition of the database 71.
  • the detecting terminal 72 is configured to extract the fault information and the fault warning information included in the fault analysis data, and determine each of the fault information and the repair corresponding to the fault warning information.
  • the program including:
  • the detecting terminal 72 is configured to determine, according to a preset fault type classification algorithm, the fault information and a fault type corresponding to the fault early warning information;
  • the detecting terminal 72 is configured to: if the fault information or the fault warning information is a type of fault information, extract a fault repair algorithm that matches the fault information of the fault type from the fault repair algorithm database, and Generating the repair solution according to the fault repair algorithm;
  • the detecting terminal 72 is configured to generate a fault handling event corresponding to the second type of fault information, and submit the fault handling event to the fault information if the fault information or the fault early warning information is the second type of fault information.
  • the fault responds to the terminal 73.
  • the fault response terminal 73 is configured to receive the repairing scheme sent by the detecting terminal 72, and perform a repairing operation corresponding to the repairing solution, respectively, to repair a fault condition of the database 71, including :
  • the fault response terminal 73 is configured to receive fault event information of the database 71 submitted by the detecting terminal 72, where the fault event information includes a fault feature parameter and a fault repairing scheme that matches the fault feature parameter. ;
  • the fault response terminal 73 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;
  • the fault response terminal 73 is configured to start a fault event monitoring process, to collect fault repair data generated by the fault processing user to repair the fault event information, and a fault repair result;
  • the fault response terminal 73 is configured to push the fault repair result to an audit account corresponding to the fault processing user;
  • the fault response terminal 73 is configured to close the fault event monitoring process if receiving a fault repair confirmation command returned by the audited account.
  • the fault response terminal 73 is further configured to:
  • the fault response terminal 73 is configured to extract a repair feature parameter of the fault repair data, and The repair feature parameter is matched with the preset repair plan library;
  • the fault response terminal 73 is configured to: if the repair feature parameter does not have a fault repair solution matching the preset repair solution database, create a fault repair solution;
  • the fault response terminal 73 is configured to import the repair feature parameter into the newly created fault repair solution, and store it in the preset repair plan library.
  • the detecting terminal 72 is further configured to:
  • the detection terminal is obtained 72, configured to take the processing result of each of the fault information and the fault warning information, and generate a database detection report according to the processing result;
  • the detecting terminal 72 is configured to input the fault information and the processing result corresponding to the fault warning information into the database fault analysis model to perform training update on the database fault analysis model.
  • the fault response terminal 73 is configured to start a fault event monitoring process, to collect the fault repair data and the fault repair result generated by the fault processing user to repair the fault event information, and further include:
  • the fault response terminal 73 is configured to receive a repair resource request instruction initiated by the fault repair user, and generate resource scheduling information according to the repair resource request instruction;
  • the fault response terminal 73 is 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; [0123] The fault response terminal 73 is configured to: if the scheduling confirmation instruction returned by the resource management account is received, add the usage right of the repair resource corresponding to the repair resource request instruction to the permission parameter of the fault repair user.
  • the database maintenance system provided by the embodiment of the present invention can also perform troubleshooting on the database without relying on the expertise of the database engineer, but by detecting that the terminal matches the corresponding inspection algorithm based on the characteristics of the database itself. Therefore, the running state data obtained by the patrol algorithm can better characterize whether the database contains a fault condition, and obtain fault analysis data through a preset database fault analysis model, and the detection accuracy thereof is also greatly improved.
  • the fault response terminal can also automatically repair the fault condition according to the matched repair scheme, which improves the efficiency of detection and the ambiguity of repair.
  • FIG. 8 is a schematic diagram of a database maintenance system according to another embodiment of the present invention.
  • the database maintenance system includes a database 81, a detection terminal 82, a fault response terminal 83, and a repair solution library 84.
  • the database 81 is respectively connected to the detecting terminal 82 and the fault responding terminal 83, and detects and repairs the fault condition of the database 81 by the two terminal devices.
  • the detecting terminal 82 and the fault responding terminal 83 perform a communication connection to transmit the obtained fault condition of the database 81 to the fault responding terminal for fault processing.
  • the detecting terminal 82 further acquires corresponding fault repair data from the plurality of libraries, and performs update learning on the repair plan library 84, the fault repair algorithm library 85, and the database analysis model 86, respectively.
  • the fault response terminal 83 is also in communication with the repair scheme library 84 to supplement the number of schemes in the repair scheme library.
  • the fault responding terminal also communicates with the fault handling user 87 and the terminal device corresponding to the audit account 88, respectively, to push relevant information to the user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种数据库维护方法及其***，适用于数据库技术领域，所述方法包括：所述检测终端基于与数据库的特征相匹配的巡检算法，获取所述数据库的运行状态数据（S101）；所述检测终端将所述运行状态数据导入至预设的数据库故障分析模型，生成所述运行状态数据对应的故障分析数据（S102）；所述检测终端提取所述故障分析数据包含的所述故障信息以及所述故障预警信息，并确定各个所述故障信息以及所述故障预警信息对应的修复方案（S103）；所述检测终端将所述修复方案发送至所述故障响应终端（S104）；所述故障响应终端接收所述检测终端发送的修复方案，并分别执行所述修复方案对应的修复操作，以修复所述数据库的故障情况（S105）。所述方法解决了数据库的维护技术，检测的准确性较低，运营成本较大，并且需要人工到数据库现场进行故障排查，检测效率较低，常常无法及时发现异常情况的问题。

Description

发明名称：一种数据库维护方法及其***
技术领域
[0001] 本发明属于数据库技术领域， 尤其涉及一种数据库维护方法及其***。
背景技术
[0002] 随着信息化的深入发展， 离不幵对数据的存储以及提取操作， 因而数据库的重 要性也愈来愈突出， 如何保证数据库***能够持续高效工作已成为信息化进程 发展的重要一环。 而现有的数据库的维护技术， 主要通过数据库工程师定吋现 场收集信息并手动分析数据库的运行现状， 从而判别数据库是否存在异常情况 ， 但该手段依赖于数据库工程师的专业技术水平， 并且不同工程师之间的检测 标准不一致， 从而导致异常判定存在较大的差异， 检测的准确性较低， 运营成 本较大。 并且需要人工到数据库现场进行故障排査， 检测效率较低， 常常无法 及吋发现异常情况。
技术问题
[0003] 有鉴于此， 本发明实施例提供了一种数据库维护方法及其***， 以解决现有的 数据库的维护技术， 依赖于数据库工程师的专业技术水平， 并且不同工程师之 间的检测标准不一致， 从而导致异常判定存在较大的差异， 检测的准确性较低 ， 运营成本较大， 检测效率较低， 常常无法及吋发现异常情况的问题。
问题的解决方案
技术解决方案
[0004] 本发明实施例的提供了一种数据库的维护方法及其***， 其特征在于， 所述数 据库的维护***包括检测终端以及故障响应终端；
[0005] 所述数据库的维护方法包括：
[0006] 所述检测终端基于与数据库的特征相匹配的巡检算法， 获取所述数据库的运行 状态数据；
[0007] 所述检测终端将所述运行状态数据导入至预设的数据库故障分析模型， 生成所 述运行状态数据对应的故障分析数据； 其中， 所述故障分析数据包含故障信息 [0008] 所述检测终端提取所述故障分析数据包含的所述故障信息以及所述故障预警信 息， 并确定各个所述故障信息以及所述故障预警信息对应的修复方案；
[0009] 所述检测终端将所述修复方案发送至所述故障响应终端；
[0010] 所述故障响应终端接收所述检测终端发送的修复方案， 并分别执行所述修复方 案对应的修复操作， 以修复所述数据库的故障情况。
发明的有益效果
有益效果
[0011] 实施本发明实施例提供的一种数据库维护方法及其***具有以下有益效果： [0012] 本发明实施例不依赖数据库工程师的专业知识对数据库进行故障排査， 而是通 过检测终端基于数据库本身的特征匹配到与之对应的巡检算法， 从而通过该巡 检算法获得的运行状态数据能够较好的表征数据库是否包含故障情况， 并通过 预设的数据库故障分析模型得到故障分析数据， 可见， 上述操作无需数据库工 程师进行介入， 减少了对人工专业技术水平的依赖， 从而减少了人工成本以及 数据库的运营成本， 并且巡检算法是根据不同数据库的特性选取得到的， 其检 测的准确性也大大提高。 故障响应终端也可以根据匹配的修复方案自动对故障 情况进行修复， 提高了检测的效率以及修复的及吋性。
对附图的简要说明
附图说明
[0013] 图 1是本发明第一实施例提供的一种数据库维护方法的实现流程图；
[0014] 图 2是本发明第二实施例提供的种数据库维护方法 S103的体实现流程图； [0015] 图 3是本发明第三实施例提供的一种数据库维护方法 S203的具体实现流程图； [0016] 图 4是本发明第四实施例提供的一种数据库维护方法的具体实现流程图；
[0017] 图 5是本发明第五实施例提供的一种数据库维护方法的具体实现流程图；
[0018] 图 6是本发明第六实施例提供的一种数据库维护方法的具体实现流程图；
[0019] 图 7是本发明一实施例提供的一种数据库的维护***的结构框图；
[0020] 图 8是本发明另一实施例提供的一种数据库的维护***的示意图。 本发明的实施方式
[0021] 为了使本发明的目的、 技术方案及优点更加清楚明白， 以下结合附图及实施例 ， 对本发明进行进一步详细说明。 应当理解， 此处所描述的具体实施例仅仅用 以解释本发明， 并不用于限定本发明。
[0022] 本发明实施例解决了现有的数据库的维护技术， 检测的准确性较低， 运营成本 较大， 检测效率较低， 常常无法及吋发现异常情况的问题。
[0023] 在本发明实施例中， 数据库的维护方法， 应用于数据库的维护***， 该数据库 的维护***中包含检测终端以及故障响应终端， 通过上述两个终端设备维护该 数据库的维护***中包含的数据库。 相对地， 故障响应终端具体为安装有数据 库故障的响应程序的终端设备。 特别地， 该维护***中检测终端和 /或故障响应 终端可集成于数据库服务器内， 数据库服务器直接调用本地的应用程序继而实 现数据库的故障检测和 /或故障响应操作。 当然， 数据库的维护***中可包含多 个数据库服务器， 检测终端以及故障响应终端共同对***中的多个数据库进行 维护操作。 图 1示出了本发明第一实施例提供的数据库维护方法的实现流程图， 详述如下：
[0024] 在 S101中， 所述检测终端基于与数据库的特征相匹配的巡检算法， 获取所述数 据库的运行状态数据。
[0025] 在本实施例中， 检测终端首先获取数据库的特征， 其中， 该特征包括但不限于 以下一种或至少两种的组合： 数据库的种类、 幵发商信息、 已存储的数据量以 及数据类型、 数据库的版本信息等， 根据上述数据库的特征， 可确定该数据库 的基本特性， 从而通过该基本特性， 从巡检算法库中匹配得到与之对应的巡检 方案。
[0026] 在本实施例中， 检测终端除了通过上位服务器获取巡检算法外， 还可以通过数 据库的管理人员输入的方式获取该巡检算法， 在该情况下， 检测终端可接收管 理人员对应的检测终端发送编写完成的巡检算法， 检测终端在接收到该巡检算 法后， 将建立数据库与巡检算法的对应关系。
[0027] 在本实施例中， 检测终端在确定了进行巡检的数据库对应的巡检算法后， 则通 过该巡检算法， 获取该数据库的运行状态数据。 其中， 该状态运行数据包括但 不限于： 数据库的数据冗余率、 数据库的平均读写速率、 数据库中各个分区的 数据存储情况、 各个分区的存储地址的分配情况、 数据库介质运行状态、 运算 溢出率等。
[0028] 在 S102中， 所述检测终端将所述运行状态数据导入至预设的数据库故障分析模 型， 生成所述运行状态数据对应的故障分析数据； 其中， 所述故障分析数据包 含故障信息以及故障预警信息。
[0029] 在本实施例中， 检测终端存储有数据库故障分析模型， 用于根据输入的运行状 态数据， 判定该运行状态数据中是否包含故障风险情况， 该故障风险情况具体 为是否包含已经发生故障的故障信息， 以及可能发生故障的故障预警信息， 将 上述故障信息以及故障预警信息定义为多个风险点， 并生成与运行状态数据对 应的故障分析数据。 因此， 检测终端在获取到数据库的运行状态数据后， 则将 该运行状态数据导入到该数据库故障分析模型， 以得到巡检吋刻该数据库对应 的故障分析数据。
[0030] 在本实施例中， 数据库分析模型可通过训练学习的方式得到。
[0031] 在 S103中， 所述检测终端提取所述故障分析数据包含的所述故障信息以及所述 故障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的修复方 案。
[0032] 在本实施例中， 故障信息具体为： 在巡检过程中， 检测到数据库正处于故障状 态的相关信息， 包括故障发生的位置、 影响的功能以及故障运行参数等信息。 故障预警信息具体为： 在巡检过程中， 根据检测到的运行状态预判数据库某一 模块或功能可能将会发生异常， 或某一模块或功能的稳定性以及可靠性低于正 常水平， 此吋则汇总该功能或模块的相关信息作为故障预警信息。 因此， 检测 终端进行修复的并不限于已经发生故障的故障点， 还能将可能导致故障的风险 点也一并修复。
[0033] 在本实施例中， 检测终端在确定了故障分析数据中所有故障信息以及故障预警 信息对应的修复方案后， 则执行 S104的相关操作。
[0034] 在 S104中， 所述检测终端将所述修复方案发送至所述故障响应终端。 [0035] 在本实施例中， 检测终端在 S103中获取得到的各个修复方案， 发送给故障响应 终端， 以便故障响应终端根据上述修复方案对数据库的故障进行修复。 可选地 ， 若数据库的维护***中包含多个故障响应终端， 由不同的故障响应终端处理 不同类型的故障情况， 则检测终端根据故障信息或故障预警信息确定与之对应 的故障响应终端， 并将该故障信息或故障预警信息对应的修复方案发送给对应 的故障响应终端进行响应。
[0036] 在 S 105中， 所述故障响应终端接收所述检测终端发送的修复方案， 并分别执行 所述修复方案对应的修复操作， 以修复所述数据库的故障情况。
[0037] 在本实施例中， 故障响应终端在确定了多个修复方案后， 将对数据库执行修复 方案对应的修复操作， 用以修复数据库中对应的故障情况， 该故障情况也包含 故障信息以及故障预警信息对应的故障情况。
[0038] 以上可以看出， 本发明实施例提供的一种数据库维护方法通过检测终端获取数 据库的特征， 确定与之匹配的巡检算法， 继而基于该巡检算法获取数据库的运 行状态数据； 检测终端在获取了运行状态数据后， 将其导入至预设的数据库故 障分析模型， 判断该运行状态数据中是否包含故障情况或可能发生故障的故障 预警情况， 并生成与之对应的故障分析数据， 然后根据该故障分析数据包含的 故障信息以及故障预警信息， 分别确定各个信息对应的修复方案， 继而将各个 修复方案发送给故障响应终端， 通过故障响应终端执行对应的修复操作， 从而 实现了自动对数据库进行检测并修复故障的目的。 与现有的数据库维护技术相 比， 本发明实施例不依赖数据库工程师的专业知识对数据库进行故障排査， 而 是通过检测终端基于数据库本身的特征匹配到与之对应的巡检算法， 从而通过 该巡检算法获得的运行状态数据能够较好的表征数据库是否包含故障情况， 并 通过预设的数据库故障分析模型得到故障分析数据， 可见， 上述操作无需数据 库工程师进行介入， 减少了对人工专业技术水平的依赖， 从而减少了人工成本 以及数据库的运营成本， 并且巡检算法是根据不同数据库的特性选取得到的， 其检测的准确性也大大提高。 故障响应终端也可以根据匹配的修复方案自动对 故障情况进行修复， 提高了检测的效率以及修复的及吋性。
[0039] 图 2示出了本发明第二实施例提供的一种数据库维护方法 S103的具体实现流程 图。 参见图 2所示， 相对于图 1所述实施例， 本实施例提供的一种数据库维护方 法 S103包括 S201~S203， 详述如下：
[0040] 进一步地， 所述检测终端提取所述故障分析数据包含的所述故障信息以及所述 故障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的修复方 案， 包括：
[0041] 在 S201中， 所述检测终端根据预设的故障类型分类算法， 确定所述故障信息以 及所述故障预警信息对应的故障类型。
[0042] 在本实施例中， 检测终端根据预设的故障类型分类算法， 分别判断各个故障信 息以及故障预警信息的故障类型。 具体地， 以确定故障信息对应的故障类型为 例， 检测终端获取故障信息中包含的故障发生的位置以及影响的功能， 定位该 故障信息所属的模块类别， 继而根据该故障信息中包含的故障运行参数， 确定 该所属模块中对应的硬件元件或程序， 从而得到该故障信息对应的故障类型。 相似地， 故障预警信息也可以通过上述步骤进行确定。
[0043] 在本实施例中， 检测终端根据用户的设置， 将上述的多个故障类型统一划分为 两个类别， 分别一类故障信息以及二类故障信息， 其中一类故障信息具体为分 配有对应的故障修复算法， 故障响应终端可自行根据故障修复算法对一类故障 信息进行故障修复， 无需通知故障处理用户； 而二类故障信息具体为检测终端 可进行部分应急修复， 但需要故障处理用户人工介入进行修复。
[0044] 在 S202中， 若所述故障信息或所述故障预警信息为一类故障信息， 则所述检测 终端从故障修复算法库中提取与所述一类故障信息匹配的故障修复算法， 并根 据所述故障修复算法生成所述修复方案。
[0045] 在本实施例中， 检测终端设置有故障修复算法库， 其中包含各个一类故障信息 对应的故障修复算法。 因此， 检测终端在确定该故障信息或故障预警信息为一 类故障信息后， 则将该一类故障信息与故障修复算法库中的各个故障修复算法 进行匹配， 继而确定与之对应的故障修复算法， 并基于该故障修复算法以及故 障信息或故障预警信息， 生成上述修复方案。
[0046] 在 S203中， 若所述故障信息或所述故障预警信息为二类故障信息， 则所述检测 终端生成所述二类故障信息对应的故障处理事件， 并提交所述故障处理事件至 所述故障响应终端。
[0047] 在本实施例中， 检测终端在确定了该二类故障信息对应的故障处理用户后， 需 要告知该故障处理用户需要及吋进行修复， 因而将根据该故障信息或故障预警 信息生成二类故障信息对应的故障处理事件。
[0048] 在本实施例中， 检测终端在生成该故障处理事件后， 将提交该故障处理事件至 该故障处理用户， 以启动故障修复流程。 故障处理用户可通过办公***或邮件 等方式获取到该故障处理事件， 并自行执行修复策略， 以便对该故障信息或故 障预警信息进行修复。
[0049] 在本发明实施例中， 通过获取故障信息或故障预警信息的故障类型， 采用两种 不同的手段对数据库进行修复， 提高了数据库的修复的灵活性， 对于较为简单 以及权限较低的故障， 可交由检测终端自行修复； 而对于较为复杂以及权限较 高的故障， 则建议人工介入修复， 并且提供包含修复建议的故障处理事件给到 故障处理用户， 从而降低了故障处理用户的修复难度。
[0050] 图 3示出了本发明第三实施例提供的一种数据库维护方法中 S203的具体实现流 程图。 参见图 3所示， 相对于图 2所述实施例， 本实施例提供的一种数据库维护 方法中 S203包括以下步骤， 详述如下：
[0051] 进一步地， 所述故障响应终端接收所述检测终端发送的修复方案， 并分别执行 所述修复方案对应的修复操作， 以修复所述数据库的故障情况， 包括：
[0052] 在 S301中， 所述故障响应终端接收所述检测终端提交的数据库的故障事件信息 ； 其中， 所述故障事件信息包含故障特征参数以及与所述故障特征参数匹配的 故障修复方案。
[0053] 在本实施例中， 故障响应终端通过与检测终端之间的通信连接， 接收检测终端 提交的故障吋间信息， 以便对该故障吋间信息对应的故障情况进行处理。
[0054] 在 S302中， 所述故障响应终端基于所述故障特征参数， 确定所述故障事件信息 对应的故障处理用户， 并将所述故障事件信息推送给所述故障处理用户。
[0055] 在本实施例中， 故障响应终端从故障事件信息中提取其中包含的故障特征参数 ， 定位该数据库中发生故障的模块或功能， 继而确定管理该模块或功能的用户 ， 将上述用户识别为故障处理用户。 具体地， 若故障特征参数对应多个故障模 块或故障功能， 且多个故障模块或故障功能由不同的用户进行管理， 则该故障 事件信息对应的故障处理用户可以为多个， 并将故障事件信息同吋推送给多个 故障处理用户。 优选地， 故障响应终端基于不同的故障模块或故障功能， 将故 障事件信息分解为多个故障子事件信息， 并将各个故障子事件信息推送给对应 的故障处理用户。
[0056] 在本实施例中， 故障响应终端在确定故障处理用户后， 则根据査询该故障处理 用户对应的用户设备以及该用户设备的通信地址， 向该用户设备发送故障事件 信息。 可选地， 故障响应终端还可以根据该故障处理用户， 在该故障处理用户 对应的办公***中生成一个故障处理事件， 将该故障事件信息导入到该故障处 理事件中， 并将该故障处理事件推送给故障处理用户在办公***中对应的账户 上。
[0057] 在 S303中， 所述故障响应终端启动故障事件监测流程， 以采集所述故障处理用 户修复所述故障事件信息吋产生的故障修复数据以及故障修复结果。
[0058] 在本实施例中， 故障处理用户在接收到故障事件信息后， 将对数据库的故障情 况进行修复操作， 以对数据库无法自动修复的故障进行人工修复。 与此同吋， 故障响应终端也启动故障事件监测流程， 用于采集故障处理用户修复故障事件 信息对应的故障情况吋产生的故障修复数据。 具体地， 故障响应终端将幵启一 条独立的线程， 通过该线程持续监测该数据库中的参数修改操作， 该参数包括 数据库的运行参数、 脚本文件、 表结构、 存储数据的变更情况等。 故障响应终 端将获取得到的故障修复数据存储于该故障事件信息对应的存储区域中， 该存 储区域包含故障事件信息的事件标识。
[0059] 在本实施例中， 故障响应终端可同吋幵启多条线程， 用于采集不同故障事件信 息的故障修复数据。 数据库故障的检査终端或故障响应终端可能在一定的吋间 内， 检査到数据库存在多个故障情况， 从而生成多个故障事件信息， 因此故障 响应终端为了确定各个故障事件信息对应的修复情况， 则幵启多条线程， 每一 条线程检测一个故障事件信息对应的故障修复数据， 并存储至各自对应的存储 区域中。
[0060] 在本实施例中， 故障响应终端采集故障修复数据的方式具体为： 故障响应终端 以预设的吋间间隔获取数据库中的各项参数， 并将该当前采集到的参数与上一 采集吋刻对应的参数进行比对， 确定变更的参数情况， 并将变更的参数情况作 为该次修复过程的故障修复数据， 从而实现对故障修复数据实现增量存储， 以 减少故障修复数据的数据量以及故障响应终端的存储压力。
[0061] 在 S304中， 所述故障响应终端将所述故障修复结果推送给所述故障处理用户对 应的审核账户。
[0062] 在本实施例中， 故障响应终端在确定数据库的故障事件信息已被修复完成后， 则进行故障处理结果进行审批确认的操作， 以确保该故障修复结果正确无误。 故障响应终端将査询进行修复操作的故障处理用户对应的审核账户， 该审核账 户可以为故障处理用户的上级用户， 也可以是数据库的管理员， 该数据库的管 理员负责整个数据库具有监控管理、 权限。
[0063] 在 S305中， 所述故障响应终端若接收到所审核账户返回的故障修复确认指令， 则关闭所述故障事件监测流程。
[0064] 在本实施例中， 审核账户在接收到故障响应终端推送的故障处理结果吋， 可基 于该故障处理结果， 判定该次故障修复操作是否已经完成。 若审核账户认同该 故障处理结果并确定该次故障修复操作已完成， 将生成故障修复确认指令， 并 发送给故障响应终端； 若审核账户不认同该故障处理结果， 需要故障处理用户 重新对该故障处理事件进行修复处理， 则生成故障重修复指令给故障响应终端 ， 在该情况下， 故障响应终端若接收到故障重修复指令， 则返回执行 S102的操 作， 以提示故障处理用户重新对该故障事件进行处理。
[0065] 在本发明实施例中， 能够在确定数据库存在故障事件吋， 即吋将故障情况反馈 给对应的故障处理用户， 从而缩减了故障发生到故障发现之间的吋间差， 实现 实吋汇报故障情况的目的， 无需用户频繁登录数据库确认是否存在故障事件， 避免故障情况加剧。 另一方面， 本发明实施例在得到修复结果后， 还将对应的 修复结果推送给对应的审核账户， 从而使得修复结果经过多一重审核流程， 确 保了修复结果的准确性。
[0066] 图 4示出了本发明第四实施例提供的一种数据库维护方法的具体实现流程图。
参见图 4所示， 相对于图 3所述实施例， 本实施例提供的一种数据库维护方法还 包含 S401~S403， 详述如下：
[0067] 在 S401中， 所述故障响应终端提取所述故障修复数据的修复特征参数， 并将所 述修复特征参数与预设的修复方案库进行匹配。
[0068] 在本实施例中， 故障响应终端在完成数据库的故障修复操作之后， 将对本次故 障处理用户的修复过程进行学习， 以提高故障修复方案库的方案数量。 故障响 应终端首先确定故障事件信息的故障类型， 并从故障事件监测流程对应的存储 区域中获取该故障事件对应的故障修复数据， 并从该故障修复数据中提取修复 特征参数， 其中该修复特征参数具体为故障处理用户消除故障事件信息吋对数 据库进行修改的参数， 如上所述， 该参数包括以下一种或至少两种的组合： 数 据库的运行参数、 脚本文件、 表结构、 存储数据的变更情况。 可选地， 故障响 应终端还可以将故障发生吋刻的数据库参数以及故障修复完成吋的数据库参数 逐一进行比对， 继而得到该修复特征参数。
[0069] 在本实施例中， 故障响应终端预设有修复方案库， 用于记录不同故障类型对应 的故障修复方案。 其中， 该修复方案库可存储于故障响应终端内置的存储模块 中， 在该情况下， 故障响应终端可直接读取本地的存储模块即可获取到修复方 案库中包含的数据； 该修复方案库也可以存储于独立的数据库服务器或其他故 障响应终端中， 在该情况下， 故障响应终端则需要与该数据库服务器或其他故 障响应终端建立通信连接， 并发送修复方案库的调用请求， 以获取该修复方案 库中的数据。
[0070] 在 S402中， 若所述修复特征参数在所述预设的修复方案库中不存在与之匹配的 故障修复方案， 则所述故障响应终端新建一个故障修复方案。
[0071] 在本实施例中， 故障响应终端若在修复方案库中无法寻找到与修复特征参数匹 配的故障修复方案， 则在修复方案库中新建一个故障修复方案以记录该未被收 录的故障修复手段。 可选地， 故障响应终端也可以在本地新建一个故障修复方 案， 在生成完毕后再发送给修复方案库， 以便修复方案库存储该故障修复方案
[0072] 在本实施例中， 该故障修复方案具体为一个方案模板， 其中包含多个待填写的 内容以及部分标准格式内容， 并为该方案模块设置一个方案唯一标识码。 具体 地， 每个修复方案库对应的故障修复方案模板将可能存在差异， 因此， 故障响 应终端在新建故障修复方案前， 需要从修复方案库中获取该方案模板。
[0073] 在 S403中， 所述故障响应终端将所述修复特征参数导入至新建的所述故障修复 方案， 并存储于所述预设的修复方案库内。
[0074] 在本实施例中， 故障响应终端在新建一个故障修复方案后， 将提取得到的修复 特征参数中包含的各个参数项导入到该故障修复方案对应的位置内。 优选地， 故障响应终端还将故障事件信息中的故障特征参数导入至该故障修复方案内， 以便日后确定故障事件信息对应的故障修复方案吋， 可基于该故障修复方案建 立吋导入的故障事件信息， 确定两者是否匹配。
[0075] 在本实施例中， 故障响应终端将修复特征参数导入到该故障修复方案后， 则该 故障修复方案已建立完成， 因此将该故障修复方案存储于修复方案库内， 从而 在遇到类似的故障情况吋， 故障响应终端可直接根据该故障修复方案的修复操 作自动对数据库进行修复， 或者遇到相关的故障情况吋， 故障响应终端也可以 推送该故障修复方案给故障处理用户进行参考。
[0076] 在本发明实施例中， 通过每次修复完成后， 获取该次修复操作对应的修复特征 参数， 确定该次修复操作是否已被记录， 对于新的数据库的修复手段， 将创建 一个新的故障修复方案予以保存， 从而在每次操作后， 均可实现故障修复方案 的学习， 提高了修复方案库的自动修复能力， 从而减少故障处理用户现场修复 的次数， 提高了修复的效率。
[0077] 图 5示出了本发明第五实施例提供的一种数据库维护方法的具体实现流程图。
参见图 5所示， 相对于图 1至图 4所述实施例， 本实施例提供的一种数据库维护方 法还包括以下 S501以及 S502， 详述如下：
[0078] 在 S501中， 所述检测终端获取各个所述故障信息以及所述故障预警信息的处理 结果， 并根据所述处理结果生成数据库检测报告。
[0079] 在本实施例中， 检测终端将汇总故障响应终端返回的各个故障信息以及故障预 警信息对应的处理结果。 对应地， 该处理结果包含修复成功以修复失败的处理 结果， 也包含故障判定错误的处理结果。
[0080] 在本实施例中， 检测终端根据各个故障信息以及故障预警信息对应的处理结果 生成数据库检测报告， 该数据库检测报告列举了本次巡检检测得到的故障信息 及其对应的处理结果， 以及故障预警信息及其对应的处理结果， 优选地， 还更 新了数据库的故障率以及资源占用情况， 从而用户根据査询该数据库检测报告 ， 可准确获取到数据库整体的故障情况。
[0081] 在 S502中， 所述检测终端将所述故障信息以及所述故障预警信息对应的处理结 果输入所述数据库故障分析模型， 以对所述数据库故障分析模型进行训练更新
[0082] 在本实施例中， 终端设备根据上述获取得到故障信息以及故障预警信息对应的 处理结果输入至数据库故障分析模型， 由于数据库故障分析模型用于检测数据 库的运行数据中是否包含故障情况， 而故障信息以及故障预警信息中也包含了 数据库在故障发生或即将发生吋对应的运行状态数据， 因此将上述处理结果输 入至该故障分析模型中， 对其进行训练更新， 可以提高该数据库的故障分析模 型的准确率。
[0083] 在本发明实施例中， 通过汇总各个故障信息以及故障预警信息对应的处理结果 ， 继而生成数据库检测报告， 便于用户进行査阅以及获知数据库实吋的运行情 况， 以便对数据库的制定对应的使用决策。 另一方面， 将故障信息以及故障预 警信息的处理结果对数据库分析模型进行训练更新， 可进一步提高数据库故障 分析模型对于故障的敏感度， 从而提高检测的准确率。
[0084] 图 6示出了本发明第六实施例提供的一种数据库维护方法的具体实现流程图。
参见图 6所示， 相对于图 3或图 4所述实施例， 本实施例提供的一种数据库维护方 法中所述故障响应终端启动故障事件监测流程， 以采集所述故障处理用户修复 所述故障事件信息吋产生的故障修复数据以及故障修复结果， 还包括以下 S601 S603 , 详述如下：
[0085] 在 S601中， 所述故障响应终端接收所述故障修复用户发起的修复资源请求指令 ， 基于所述修复资源请求指令生成的资源调度信息。
[0086] 在本实施例中， 故障处理用户在修复数据库的故障吋间信息的过程中， 需要申 请额外的修复资源吋， 可向故障响应终端发送一个修复资源请求指令， 或者通 过故障响应终端内置的客户端， 生成上述的修复资源请求指令， 以便故障响应 终端可基于该修复资源请求指令向对应的负责人申请故障修复过程中所需的修 复资源。
[0087] 在本实施例中， 该修复资源请求指令中包含用户所需的修复资源类别以及资源 数量， 特别地， 还可以包含资源调用的吋限信息。 故障响应终端可通过显示模 块生成一个修复资源请求信息的填写界面， 故障处理用户通过填写该信息填写 界面中所需的资料后， 则生成对应的修复资源请求指令， 启动额外资源修复指 令的申请流程。
[0088] 在本实施例中， 故障响应终端在接收到用户发起的修复资源请求指令后， 则基 于该修复资源请求指令中包含的资源请求内容， 为每一项请求内容生成一个资 源调度信息。
[0089] 在 S602中， 所述故障响应终端根据预设的资源管理责任列表， 确定所述修复资 源请求指令对应的资源管理账户， 推送所述资源调度信息至所述资源管理账户
[0090] 在本实施例中， 故障响应终端存储模块中记载有各个资源对应的管理责任人， 即上述的资源管理账户。 其中， 上述资源包括但不限于： 数据库资源、 网络资 源、 外设模块资源、 权限资源等。 不同的资源由不同的资源责任人管理。 因此 ， 故障响应终端首先根据修复资源请求指令， 确定该请求对应的目标对象。
[0091] 在 S603中， 若接收到所述资源管理账户返回的调度确认指令， 则所述故障响应 终端将所述修复资源请求指令对应的修复资源的使用权限添加至所述故障修复 用户的权限参数中。
[0092] 在本实施例中， 资源管理账户在接收到故障响应终端推送的资源调度信息后， 将根据实际情况， 确定同意故障处理用户额外修复资源的申请。 具体地， 若资 源管理账户同意故障处理用户的请求， 则返回一个调度确认指令给故障响应终 端， 并执行 S603的相关操作； 反之， 若资源管理账户不同意故障处理用户的请 求， 则返回一个调度拒绝指令给故障响应终端， 并结束本次调度申请流程。 特 别地， 若资源管理账户同意故障处理用户的申请， 但当前并不存在可调用的资 源， 则发送调度暂缓指令， 并且故障响应终端以预设的吋间间隔获取可用资源 情况， 若检测到存在足够的资源， 则执行 S603的相关操作。 [0093] 在本实施例中， 故障响应终端在接收到调度确认指令后， 则获取修复资源请求 指令对应的修复资源的使用权限， 可选地， 该使用权限可以为一动态密钥， 在 调用修复资源前， 需要对调用方的身份进行校验， 此吋， 用户可利用该动态密 钥执行鉴权操作， 以获取该资源的使用权限。 故障响应终端在获取了修复资源 的使用权限后， 将该权限信息添加到故障处理用户的权限参数中， 故障处理用 户只需通过对应的账户名或对应的设备， 抑或是身份证明信息， 即可调用上述 修复资源对数据库的故障进行修复。
[0094] 在本发明实施例中， 故障处理用户可通过故障响应终端申请额外的故障修复资 源， 从而能够更快捷地对数据库的故障进行修复。
[0095] 应理解， 上述实施例中各步骤的序号的大小并不意味着执行顺序的先后， 各过 程的执行顺序应以其功能和内在逻辑确定， 而不应对本发明实施例的实施过程 构成任何限定。
[0096] 图 7示出了本发明一实施例提供的一种数据库的维护***的结构框图， 该数据 库维护终端包括的各单元用于执行图 1对应的实施例中的各步骤。 具体请参阅图 1与图 1所对应的实施例中的相关描述。 为了便于说明， 仅示出了与本实施例相 关的部分。
[0097] 参见图 7， 所述数据库的维护***包括数据库 71、 检测终端 72以及故障响应终 端 73;
[0098] 所述检测终端 72， 用于基于与数据库 71的特征相匹配的巡检算法， 获取所述数 据库 71的运行状态数据；
[0099] 所述检测终端 72， 用于将所述运行状态数据导入至预设的数据库故障分析模型
， 生成所述运行状态数据对应的故障分析数据； 其中， 所述故障分析数据包含 故障信息以及故障预警信息；
[0100] 所述检测终端 72， 用于提取所述故障分析数据包含的所述故障信息以及所述故 障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的修复方案
[0101] 所述检测终端 72， 用于将所述修复方案发送至所述故障响应终端 73;
[0102] 所述故障响应终 73， 用于端接收所述检测终端 72发送的修复方案， 并分别执行 所述修复方案对应的修复操作， 以修复所述数据库 71的故障情况。
[0103] 可选地， 所述检测终端 72， 用于提取所述故障分析数据包含的所述故障信息以 及所述故障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的 修复方案， 包括：
[0104] 所述检测终端 72， 用于根据预设的故障类型分类算法， 确定所述故障信息以及 所述故障预警信息对应的故障类型；
[0105] 所述检测终端 72， 用于若所述故障信息或所述故障预警信息为一类故障信息， 则从故障修复算法库中提取与所述一类故障信息匹配的故障修复算法， 并根据 所述故障修复算法生成所述修复方案；
[0106] 所述检测终端 72， 用于若所述故障信息或所述故障预警信息为二类故障信息， 则生成所述二类故障信息对应的故障处理事件， 并提交所述故障处理事件至所 述故障响应终端 73。
[0107] 可选地， 所述故障响应终端 73， 用于接收所述检测终端 72发送的修复方案， 并 分别执行所述修复方案对应的修复操作， 以修复所述数据库 71的故障情况， 包 括：
[0108] 所述故障响应终端 73， 用于接收所述检测终端 72提交的数据库 71的故障事件信 息； 其中， 所述故障事件信息包含故障特征参数以及与所述故障特征参数匹配 的故障修复方案；
[0109] 所述故障响应终端 73， 用于基于所述故障特征参数， 确定所述故障事件信息对 应的故障处理用户， 并将所述故障事件信息推送给所述故障处理用户；
[0110] 所述故障响应终端 73， 用于启动故障事件监测流程， 以采集所述故障处理用户 修复所述故障事件信息吋产生的故障修复数据以及故障修复结果；
[0111] 所述故障响应终端 73， 用于将所述故障修复结果推送给所述故障处理用户对应 的审核账户；
[0112] 所述故障响应终端 73， 用于若接收到所审核账户返回的故障修复确认指令， 则 关闭所述故障事件监测流程。
[0113] 可选地， 所述故障响应终端 73， 还用于：
[0114] 所述故障响应终端 73， 用于提取所述故障修复数据的修复特征参数， 并将所述 修复特征参数与预设的修复方案库进行匹配；
[0115] 所述故障响应终端 73， 用于若所述修复特征参数在所述预设的修复方案库中不 存在与之匹配的故障修复方案， 则新建一个故障修复方案；
[0116] 所述故障响应终端 73， 用于将所述修复特征参数导入至新建的所述故障修复方 案， 并存储于所述预设的修复方案库内。
[0117] 可选地， 所述检测终端 72还用于：
[0118] 所述检测终端获 72， 用于取各个所述故障信息以及所述故障预警信息的处理结 果， 并根据所述处理结果生成数据库检测报告；
[0119] 所述检测终端 72， 用于将所述故障信息以及所述故障预警信息对应的处理结果 输入所述数据库故障分析模型， 以对所述数据库故障分析模型进行训练更新。
[0120] 可选地， 所述故障响应终端 73， 用于启动故障事件监测流程， 以采集所述故障 处理用户修复所述故障事件信息吋产生的故障修复数据以及故障修复结果， 还 包括：
[0121] 所述故障响应终端 73， 用于接收所述故障修复用户发起的修复资源请求指令， 基于所述修复资源请求指令生成资源调度信息；
[0122] 所述故障响应终端 73， 用于根据预设的资源管理责任列表， 确定所述修复资源 请求指令对应的资源管理账户， 推送所述资源调度信息至所述资源管理账户； [0123] 所述故障响应终端 73， 用于若接收到所述资源管理账户返回的调度确认指令， 则将所述修复资源请求指令对应的修复资源的使用权限添加至所述故障修复用 户的权限参数中。
[0124] 因此， 本发明实施例提供的数据库维护***同样可以不依赖数据库工程师的专 业知识对数据库进行故障排査， 而是通过检测终端基于数据库本身的特征匹配 到与之对应的巡检算法， 从而通过该巡检算法获得的运行状态数据能够较好的 表征数据库是否包含故障情况， 并通过预设的数据库故障分析模型得到故障分 析数据， 其检测的准确性也大大提高。 故障响应终端也可以根据匹配的修复方 案自动对故障情况进行修复， 提高了检测的效率以及修复的及吋性。
[0125] 参见图 8所示， 是本发明另一实施例提供的数据库的维护***的示意图， 该数 据库的维护***包括数据库 81、 检测终端 82、 故障响应终端 83、 修复方案库 84 、 故障修复算法库 85、 数据库分析模型 86、 故障处理用户 87以及审核账户 88。
[0126] 其中， 所示数据库 81分别与检测终端 82以及故障响应终端 83通信连接， 通过上 述两个终端设备检测以及修复数据库 81的故障情况。
[0127] 检测终端 82以及故障响应终端 83之间进行通信连接， 以将获取得到的数据库 81 的故障情况发送给故障响应终端进行故障处理。
[0128] 检测终端 82还分别与修复方案库 84、 故障修复算法库 85、 数据库分析模型 86， 从上述多个库中获取相应的故障修复数据， 并对其进行更新学习。
[0129] 故障响应终端 83还与修复方案库 84进行通信连接， 用以补充该修复方案库中的 方案数量。 另一方面， 故障响应终端还分别与故障处理用户 87以及审核账户 88 对应的终端设备通信连接， 以推送相关的信息给上述用户。
[0130] 上述多个终端以及用户之间的数据交互可参见上述内容， 在此不再赘述。
[0131] 以上所述实施例仅用以说明本发明的技术方案， 而非对其限制； 尽管参照前述 实施例对本发明进行了详细的说明， 本领域的普通技术人员应当理解： 其依然 可以对前述各实施例所记载的技术方案进行修改， 或者对其中部分技术特征进 行等同替换； 而这些修改或者替换， 并不使相应技术方案的本质脱离本发明各 实施例技术方案的精神和范围， 均应包含在本发明的保护范围之内。

Claims

权利要求书
[权利要求 1] 一种数据库的维护方法， 应用于数据库的维护***， 其特征在于， 所 述数据库的维护***包括检测终端以及故障响应终端；
所述数据库的维护方法包括：
所述检测终端基于与数据库的特征相匹配的巡检算法， 获取所述数据 库的运行状态数据；
所述检测终端将所述运行状态数据导入至预设的数据库故障分析模型 ， 生成所述运行状态数据对应的故障分析数据； 其中， 所述故障分析 数据包含故障信息以及故障预警信息；
所述检测终端提取所述故障分析数据包含的所述故障信息以及所述故 障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的 修复方案；
所述检测终端将所述修复方案发送至所述故障响应终端；
所述故障响应终端接收所述检测终端发送的修复方案， 并分别执行所 述修复方案对应的修复操作， 以修复所述数据库的故障情况。
[权利要求 2] 根据权利要求 1所述的维护方法， 其特征在于， 所述检测终端提取所 述故障分析数据包含的所述故障信息以及所述故障预警信息， 并确定 各个所述故障信息以及所述故障预警信息对应的修复方案， 包括： 所述检测终端根据预设的故障类型分类算法， 确定所述故障信息以及 所述故障预警信息对应的故障类型；
若所述故障信息或所述故障预警信息为一类故障信息， 则所述检测终 端从故障修复算法库中提取与所述一类故障信息匹配的故障修复算法
， 并根据所述故障修复算法生成所述修复方案； 若所述故障信息或所述故障预警信息为二类故障信息， 则所述检测终 端生成所述二类故障信息对应的故障处理事件， 并提交所述故障处理 事件至所述故障响应终端。
[权利要求 3] 根据权利要求 2所述的维护方法， 其特征在于， 所述故障响应终端接 收所述检测终端发送的修复方案， 并分别执行所述修复方案对应的修 复操作， 以修复所述数据库的故障情况， 包括：
所述故障响应终端接收所述检测终端提交的数据库的故障事件信息； 其中， 所述故障事件信息包含故障特征参数以及与所述故障特征参数 匹配的故障修复方案；
所述故障响应终端基于所述故障特征参数， 确定所述故障事件信息对 应的故障处理用户， 并将所述故障事件信息推送给所述故障处理用户
所述故障响应终端启动故障事件监测流程， 以采集所述故障处理用户 修复所述故障事件信息吋产生的故障修复数据以及故障修复结果； 所述故障响应终端将所述故障修复结果推送给所述故障处理用户对应 的审核账户； 所述故障响应终端若接收到所审核账户返回的故障修复确认指令， 则 关闭所述故障事件监测流程。
[权利要求 4] 根据权利要求 3所述的维护方法， 其特征在于， 所述数据库的维护方 法， 还包括：
所述故障响应终端提取所述故障修复数据的修复特征参数， 并将所述 修复特征参数与预设的修复方案库进行匹配；
若所述修复特征参数在所述预设的修复方案库中不存在与之匹配的故 障修复方案， 则所述故障响应终端新建一个故障修复方案； 所述故障响应终端将所述修复特征参数导入至新建的所述故障修复方 案， 并存储于所述预设的修复方案库内。
[权利要求 5] 根据权利要求 1-4任一项所述的维护方法， 其特征在于， 所述数据库 的维护方法还包括：
所述检测终端获取各个所述故障信息以及所述故障预警信息的处理结 果， 并根据所述处理结果生成数据库检测报告； 所述检测终端将所述故障信息以及所述故障预警信息对应的处理结果 输入所述数据库故障分析模型， 以对所述数据库故障分析模型进行训 练更新。
[权利要求 6] 根据权利要求 3或 4所述的维护方法， 其特征在于， 所述故障响应终端 启动故障事件监测流程， 以采集所述故障处理用户修复所述故障事件 信息吋产生的故障修复数据以及故障修复结果， 还包括：
所述故障响应终端接收所述故障修复用户发起的修复资源请求指令， 基于所述修复资源请求指令生成的资源调度信息； 所述故障响应终端根据预设的资源管理责任列表， 确定所述修复资源 请求指令对应的资源管理账户， 推送所述资源调度信息至所述资源管 理账户；
若接收到所述资源管理账户返回的调度确认指令， 则所述故障响应终 端将所述修复资源请求指令对应的修复资源的使用权限添加至所述故 障修复用户的权限参数中。
[权利要求 7] —种数据库的维护***， 其特征在于， 所述数据库的维护***包括检 测终端以及故障响应终端；
所述检测终端， 用于基于与数据库的特征相匹配的巡检算法， 获取所 述数据库的运行状态数据；
所述检测终端， 用于将所述运行状态数据导入至预设的数据库故障分 析模型， 生成所述运行状态数据对应的故障分析数据； 其中， 所述故 障分析数据包含故障信息以及故障预警信息；
所述检测终端， 用于提取所述故障分析数据包含的所述故障信息以及 所述故障预警信息， 并确定各个所述故障信息以及所述故障预警信息 对应的修复方案；
所述检测终端， 用于将所述修复方案发送至所述故障响应终端； 所述故障响应终， 用于端接收所述检测终端发送的修复方案， 并分别 执行所述修复方案对应的修复操作， 以修复所述数据库的故障情况。
[权利要求 8] 根据权利要求 7所述的维护***， 其特征在于， 所述检测终端， 用于 提取所述故障分析数据包含的所述故障信息以及所述故障预警信息， 并确定各个所述故障信息以及所述故障预警信息对应的修复方案， 包 括： 所述检测终端， 用于根据预设的故障类型分类算法， 确定所述故障信 息以及所述故障预警信息对应的故障类型；
所述检测终端， 用于若所述故障信息或所述故障预警信息为一类故障 信息， 则从故障修复算法库中提取与所述一类故障信息匹配的故障修 复算法， 并根据所述故障修复算法生成所述修复方案；
所述检测终端， 用于若所述故障信息或所述故障预警信息为二类故障 信息， 则生成所述二类故障信息对应的故障处理事件， 并提交所述故 障处理事件至所述故障响应终端。
[权利要求 9] 根据权利要求 8所述的维护***， 其特征在于， 所述故障响应终端， 用于接收所述检测终端发送的修复方案， 并分别执行所述修复方案对 应的修复操作， 以修复所述数据库的故障情况， 包括：
所述故障响应终端， 用于接收所述检测终端提交的数据库的故障事件 信息； 其中， 所述故障事件信息包含故障特征参数以及与所述故障特 征参数匹配的故障修复方案；
所述故障响应终端， 用于基于所述故障特征参数， 确定所述故障事件 信息对应的故障处理用户， 并将所述故障事件信息推送给所述故障处 理用户；
所述故障响应终端， 用于启动故障事件监测流程， 以采集所述故障处 理用户修复所述故障事件信息吋产生的故障修复数据以及故障修复结 果；
所述故障响应终端， 用于将所述故障修复结果推送给所述故障处理用 户对应的审核账户； 所述故障响应终端， 用于若接收到所审核账户返回的故障修复确认指 令， 则关闭所述故障事件监测流程。
[权利要求 10] 根据权利要求 9所述的维护***， 其特征在于， 所述故障响应终端， 还用于：
所述故障响应终端， 用于提取所述故障修复数据的修复特征参数， 并 将所述修复特征参数与预设的修复方案库进行匹配； 所述故障响应终端， 用于若所述修复特征参数在所述预设的修复方案 库中不存在与之匹配的故障修复方案， 则新建一个故障修复方案； 所述故障响应终端， 用于将所述修复特征参数导入至新建的所述故障 修复方案， 并存储于所述预设的修复方案库内。
[权利要求 11] 根据权利要求 7-10任一项所述的维护***， 其特征在于， 所述检测终 端还用于：
所述检测终端获， 用于取各个所述故障信息以及所述故障预警信息的 处理结果， 并根据所述处理结果生成数据库检测报告；
所述检测终端， 用于将所述故障信息以及所述故障预警信息对应的处 理结果输入所述数据库故障分析模型， 以对所述数据库故障分析模型 进行训练更新。
[权利要求 12] 根据权利要求 9或 10所述的维护***， 其特征在于， 所述故障响应终 端， 用于启动故障事件监测流程， 以采集所述故障处理用户修复所述 故障事件信息吋产生的故障修复数据以及故障修复结果， 还包括： 所述故障响应终端， 用于接收所述故障修复用户发起的修复资源请求 指令， 基于所述修复资源请求指令生成资源调度信息；
所述故障响应终端， 用于根据预设的资源管理责任列表， 确定所述修 复资源请求指令对应的资源管理账户， 推送所述资源调度信息至所述 资源管理账户；
所述故障响应终端， 用于若接收到所述资源管理账户返回的调度确认 指令， 则将所述修复资源请求指令对应的修复资源的使用权限添加至 所述故障修复用户的权限参数中。
PCT/CN2017/100749 2017-09-06 2017-09-06 一种数据库维护方法及其*** WO2019047070A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201780000988.3A CN110088744B (zh) 2017-09-06 2017-09-06 一种数据库维护方法及其***
PCT/CN2017/100749 WO2019047070A1 (zh) 2017-09-06 2017-09-06 一种数据库维护方法及其***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/100749 WO2019047070A1 (zh) 2017-09-06 2017-09-06 一种数据库维护方法及其***

Publications (1)

Publication Number Publication Date
WO2019047070A1 true WO2019047070A1 (zh) 2019-03-14

Family

ID=65633594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/100749 WO2019047070A1 (zh) 2017-09-06 2017-09-06 一种数据库维护方法及其***

Country Status (2)

Country Link
CN (1) CN110088744B (zh)
WO (1) WO2019047070A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111274107A (zh) * 2020-01-15 2020-06-12 酷得少年(天津)文化传播有限公司 一种用于直播的故障修复***及方法
CN113051403A (zh) * 2019-12-27 2021-06-29 北京国双科技有限公司 数据库故障处理知识图谱构建方法、装置和计算机设备
CN114627627A (zh) * 2020-12-14 2022-06-14 深圳Tcl新技术有限公司 设备异常处理方法、装置、终端及计算机可读存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112434819B (zh) * 2019-08-09 2023-09-05 ***通信集团浙江有限公司 业务保障方法及装置
CN111258851B (zh) * 2020-01-14 2024-03-01 广州虎牙科技有限公司 一种集群的告警方法、装置、设置及存储介质
CN113468158B (zh) * 2021-07-13 2023-10-31 广域铭岛数字科技有限公司 数据修复方法、***、电子设备及介质
CN113886130A (zh) * 2021-10-21 2022-01-04 深信服科技股份有限公司 一种处理数据库故障的方法，装置及介质
CN114356712B (zh) * 2022-01-04 2024-07-19 腾讯科技(成都)有限公司 数据处理方法、装置、设备、可读存储介质及程序产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101008917A (zh) * 2007-01-29 2007-08-01 中南大学 基于人工免疫***的移动机器人软件故障诊断***
CN101321207A (zh) * 2008-07-22 2008-12-10 ***通信集团江苏有限公司 一种电信客户服务***数据库故障处理方法
CN103473143A (zh) * 2012-06-07 2013-12-25 中兴通讯股份有限公司 故障修复的处理、故障的修复方法及装置
CN103902542A (zh) * 2012-12-25 2014-07-02 百度在线网络技术（北京）有限公司 一种测试环境中数据库的运维方法及***
CN106407030A (zh) * 2016-09-13 2017-02-15 郑州云海信息技术有限公司 一种存储集群***故障处理方法及***

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002132987A (ja) * 2000-10-19 2002-05-10 Nec Corp インターネットを利用した集中保守管理システム及び方法
CN101719836A (zh) * 2008-10-09 2010-06-02 联想(北京)有限公司 一种故障检测方法及装置
CN103034802B (zh) * 2012-11-29 2015-10-28 广东全通教育股份有限公司 一种基于智能规则匹配的自动巡检***及方法
CN105337765B (zh) * 2015-10-10 2018-10-12 上海新炬网络信息技术股份有限公司 一种分布式hadoop集群故障自动诊断修复***
CN106227190B (zh) * 2016-08-03 2019-07-30 重庆交通开投科技发展有限公司 车辆故障处理方法、装置及***
CN106254138A (zh) * 2016-08-31 2016-12-21 广州和运科技发展有限公司 机房智能运维***故障分析方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101008917A (zh) * 2007-01-29 2007-08-01 中南大学 基于人工免疫***的移动机器人软件故障诊断***
CN101321207A (zh) * 2008-07-22 2008-12-10 ***通信集团江苏有限公司 一种电信客户服务***数据库故障处理方法
CN103473143A (zh) * 2012-06-07 2013-12-25 中兴通讯股份有限公司 故障修复的处理、故障的修复方法及装置
CN103902542A (zh) * 2012-12-25 2014-07-02 百度在线网络技术（北京）有限公司 一种测试环境中数据库的运维方法及***
CN106407030A (zh) * 2016-09-13 2017-02-15 郑州云海信息技术有限公司 一种存储集群***故障处理方法及***

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113051403A (zh) * 2019-12-27 2021-06-29 北京国双科技有限公司 数据库故障处理知识图谱构建方法、装置和计算机设备
CN111274107A (zh) * 2020-01-15 2020-06-12 酷得少年(天津)文化传播有限公司 一种用于直播的故障修复***及方法
CN114627627A (zh) * 2020-12-14 2022-06-14 深圳Tcl新技术有限公司 设备异常处理方法、装置、终端及计算机可读存储介质

Also Published As

Publication number Publication date
CN110088744B (zh) 2023-04-21
CN110088744A (zh) 2019-08-02

Similar Documents

Publication Publication Date Title
WO2019047070A1 (zh) 一种数据库维护方法及其***
US11733991B2 (en) Data processing method based on intelligent contract, device, and storage medium
CN111209131B (zh) 一种基于机器学习确定异构***的故障的方法和***
CN108234170B (zh) 一种服务器集群的监控方法和装置
CN110063042B (zh) 一种数据库故障的响应方法及其终端
CN104252500A (zh) 一种数据库管理平台的故障修复方法和装置
CN104483842A (zh) 一种调控一体自动化主站比对方法
WO2019047072A1 (zh) 一种数据库的检测方法及其终端
CN110971464A (zh) 一种适合灾备中心的运维自动化***
CN111782345A (zh) 容器云平台日志收集及分析告警方法
CN112163198B (zh) 一种主机登录安全检测方法、***、装置及存储介质
CN105872127A (zh) 一种ip地址管理***
CN103152219B (zh) 一种计算机网络***的事件监控***及事件监控方法
US7962789B2 (en) Method and apparatus for automated testing of a utility computing system
CN114172921A (zh) 一种调度录音***的日志审计方法及装置
WO2016188223A1 (zh) 故障信息采集的方法及装置
CN113629878B (zh) 一种配电网三遥开关遥控控制校验方法及***
US10353365B2 (en) Electric power facilities identification number generation apparatus and method
CN114662716A (zh) 基于区块链的电梯维护处理方法、装置以及存储介质
WO2019056545A1 (zh) 测试机自动化管理方法、装置、设备及存储介质
CN109412861B (zh) 一种终端网络建立安全关联展示方法
KR102668343B1 (ko) 인터페이스 관리 방법, 인터페이스 거버넌스 시스템, 및 인터페이스를 관리하는, 컴퓨터로 실행가능한 프로그램을 저장하는 저장매체
JP7446142B2 (ja) サイバーセキュリティ監査システム
CN111176257B (zh) 一种新能源控制***参数调试方法及***
CN117472684A (zh) 故障处理方法、装置、终端设备以及存储介质

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17924369

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17924369

Country of ref document: EP

Kind code of ref document: A1