CN110063042A - A kind of response method and its terminal of database failure - Google Patents
A kind of response method and its terminal of database failure Download PDFInfo
- Publication number
- CN110063042A CN110063042A CN201780000980.7A CN201780000980A CN110063042A CN 110063042 A CN110063042 A CN 110063042A CN 201780000980 A CN201780000980 A CN 201780000980A CN 110063042 A CN110063042 A CN 110063042A
- Authority
- CN
- China
- Prior art keywords
- fault
- repair
- database
- repairing
- scheme
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis
Abstract
A kind of response method and its terminal of database failure, comprising: obtain the event of failure information (S101) of database；Based on Fault characteristic parameters, the corresponding troubleshooting user of event of failure information is determined, and event of failure information is pushed to troubleshooting user (S102)；Startup separator event monitoring process (S103)；Fault restoration result is pushed to the corresponding audit account (S104) of troubleshooting user；If receiving the fault restoration confirmation instruction that audited account returns, event of failure monitoring process (S105) is closed.Solves the response technology of existing database failure, failure mainly by including in preset fault detection algorithm Test database, the timeliness of database failure reparation is lower, possibly even aggravate the fault degree of database, increase the difficulty of reparation, and troubleshooting user needs the problem of continually log database detects whether faulty report, reduces the operating efficiency of troubleshooting user.
Description
Database fault response method and terminal thereof
Technical Field
[0001] The invention belongs to the technical field of databases, and particularly relates to a database fault response method and a terminal thereof.
Background
[0002] With the deep development of informatization, data storage and extraction operations are not distributed, so that the importance of the database is more and more prominent, and how to ensure that a database system can continuously and efficiently work becomes an important part of the development of the informatization process. The existing database fault response technology mainly detects faults contained in the database through a preset fault detection algorithm, and outputs a corresponding fault report locally in the database, and if a manager for fault repair does not log in the database, the manager cannot know the fault condition of the database, so that the fault repair and the time-out performance of the database are reduced, the fault degree of the database may even be aggravated, and the repair difficulty is increased. On the other hand, the fault handling user needs to frequently log in the database to detect whether a fault report exists, and the operation efficiency of the fault handling user is reduced.
Technical problem
[0003] In view of this, embodiments of the present invention provide a database fault response method and a terminal thereof, so as to solve the problem of the existing database fault response technology, where a preset fault detection algorithm is mainly used to detect a fault included in a database, and a corresponding fault report is locally output in the database, and a manager of fault repair cannot know the fault condition of the database unless logging in the database, so that the fault repair and the inch performance of the database are reduced, and even the fault degree of the database may be aggravated, and the repair difficulty is increased. On the other hand, the fault handling user needs to frequently log in the database to detect whether a fault report exists, which reduces the operating efficiency of the fault handling user.
Solution to the problem
Technical solution
[0004] A first aspect of an embodiment of the present invention provides a method for responding to a database fault, where the method for responding to a database fault includes:
[0005] acquiring fault event information of a database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters; [0006] determining a fault handling user corresponding to the fault event information based on the fault characteristic parameters, and pushing the fault event information to the fault handling user;
[0007] starting a fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user in repairing the fault event information inch;
[0008] pushing the fault repairing result to an auditing account corresponding to the fault processing user;
[0009] if a fault repair confirmation instruction returned by the checked account is received, the fault event monitoring process is closed
[0010] A second aspect of the embodiments of the present invention provides a database fault response terminal, where the database fault response terminal includes:
[0011] acquiring fault event information of a database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;
[0012] determining a fault handling user corresponding to the fault event information based on the fault characteristic parameters, and pushing the fault event information to the fault handling user;
[0013] starting a fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user in repairing the fault event information inch;
[0014] pushing the fault repairing result to an auditing account corresponding to the fault processing user;
[0015] if a fault repair confirmation instruction returned by the checked account is received, the fault event monitoring process is closed
[0016] 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 executable on the processor, where the processor executes the computer program to implement the following steps:
[0017] acquiring fault event information of a database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;
[0018] determining a fault handling user corresponding to the fault event information based on the fault characteristic parameters, and pushing the fault event information to the fault handling user;
[0019] starting a fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user in repairing the fault event information inch;
[0020] pushing the fault repairing result to an auditing account corresponding to the fault processing user; [0021] if a fault repair confirmation instruction returned by the checked account is received, the fault event monitoring process is closed
[0022] A fourth aspect of an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor in inches to perform the following steps: [0023] acquiring fault event information of the database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;
[0024] determining a fault handling user corresponding to the fault event information based on the fault characteristic parameters, and pushing the fault event information to the fault handling user;
[0025] starting a fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user in repairing the fault event information inch;
[0026] pushing the fault repairing result to an auditing account corresponding to the fault processing user;
[0027] if a fault repair confirmation instruction returned by the audited account is received, the fault event monitoring process is closed
Advantageous effects
[0028] The database fault response method and the terminal thereof provided by the embodiment of the invention have the following beneficial effects:
[0029] the embodiment of the invention can determine that the database is in the failure event inches, namely the inches feed back the failure condition to the corresponding failure processing user, thereby reducing the difference between the inches from failure occurrence to failure discovery, realizing the purpose of reporting the failure condition in real inches, avoiding the problem that the failure condition is aggravated by not needing the user to frequently log in the database to confirm whether the failure event exists or not. On the other hand, after the repair result is obtained, the corresponding repair result is pushed to the corresponding audit account, so that the repair result passes through more review processes, and the accuracy of the repair result is ensured.
Brief description of the drawings
Drawings
[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for describing the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without inventive labor.
[0031] FIG. 1 is a flow chart of a database failure response method according to a first embodiment of the present invention;
[0032] fig. 2 is a flowchart of a specific implementation of a database fault response method according to a second embodiment of the present invention; 0033 fig. 3 is a flowchart of a specific implementation of a database failure response method S103 according to a third embodiment of the present invention;
[0034] fig. 4 is a flowchart of a detailed implementation of a database fault response method S101 according to a fourth embodiment of the present invention;
[0035] fig. 5 is a flowchart of a detailed implementation of a database fault response method according to a fifth embodiment of the present invention;
[0036] fig. 6 is a block diagram of a database failure response terminal according to an embodiment of the present invention;
[0037] fig. 7 is a schematic diagram of a terminal device according to an embodiment of the present invention.
Modes for carrying out the invention
[0038] In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
[0039] The embodiment of the invention solves the problem of the existing database fault response technology, mainly detects the fault contained in the database through a preset fault detection algorithm, and locally outputs a corresponding fault report in the database, and if a manager for fault repair does not log in the database, the manager for fault repair cannot know the fault condition of the database, so that the fault repair and the inch property of the database are reduced, the fault degree of the database is possibly even intensified, and the repair difficulty is increased. On the other hand, the fault handling user needs to frequently log in the database to detect whether a fault report exists, and the operating efficiency of the fault handling user is reduced.
[0040] In the embodiment of the invention, the execution main body of the flow is the terminal equipment provided with the response program of the database fault. Fig. 1 shows a flowchart of an implementation of a response method for a database fault according to a first embodiment of the present invention, which is detailed as follows:
[0041] in S101, acquiring fault event information of a database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters.
[0042] In this embodiment, if the terminal device receives the failure event information of the database, a response procedure of the database failure is triggered, so as to repair the failure condition in the database. Specifically, the fault event information includes a data category, and when the terminal device receives a data information inch, the terminal device reads the data category of the data information, and determines whether the data information is the fault event information according to a preset data category identification list, and if so, determines whether the data information is the fault event information
Then the operation of S101 is performed.
[0043] In this embodiment, the terminal device may determine whether the database has a fault condition through a local database fault detection program, and then obtain fault event information corresponding to the database; the terminal equipment can also detect the fault information contained in the database through the independent database fault detection terminal, and then acquire the fault event information sent by the terminal equipment through the communication connection between the terminal equipment and the database fault detection terminal
[0044] In this embodiment, the fault event information includes fault characteristic parameters, where the fault characteristic parameters are specifically used to indicate specific situations of the database fault, including but not limited to: the position of the fault, the fault level, the operation data of the database fault module and the like are convenient for a user to position the cause of the fault and the affected database module according to the fault characteristic parameters, so that whether business support needs to be carried out through a backup database and time required for repair is judged before repair.
[0045] In this embodiment, the fault event information further includes a fault repair scheme matching the fault characteristic parameters. The terminal equipment or the database fault examination terminal can carry out matching operation according to collected fault characteristic parameters and a preset repair scheme library, and automatically generate a recommended fault repair scheme corresponding to the fault, so that a user can perform fault repair on the database by referring to the fault repair scheme when receiving fault event information inches. It should be noted that the failure event information may include one or two or more failure recovery schemes, and particularly, if the failure event information includes two or more failure recovery schemes, it may indicate that a cause causing the database failure may be one of two or more failure causes, and the terminal device cannot be accurately located, so that the failure recovery schemes corresponding to the multiple failure causes are recommended to the user, and the user may select one of the failure recovery schemes to recover the failure cause of the database after locating the failure cause.
[0046] Optionally, in this embodiment, if the terminal device is configured to detect a failure condition of multiple databases, the failure event information may further include a database identifier, and the terminal device may locate the database in which the failure occurs based on the database identifier. Particularly, the terminal device may prompt the user of the database with the fault by marking red or blinking on a database map marked with all databases.
[0047] In S102, based on the fault characteristic parameter, a fault handling user corresponding to the fault event information is determined, and the fault event information is pushed to the fault handling user. [0048] In this embodiment, the terminal device extracts the fault feature parameters included in the fault event information, locates the module or function that has a fault in the database, determines the user that manages the module or function, and identifies the user as the fault handling user. Specifically, if the fault characteristic parameter corresponds to a plurality of fault modules or fault functions, and the plurality of fault modules or fault functions are managed by different users, the number of fault handling users corresponding to the fault event information may be multiple, and the fault event information is pushed to the plurality of fault handling users in the same time. 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 a corresponding fault handling user.
[0049] In this embodiment, after determining a failure processing user, the terminal device checks the user device corresponding to the failure processing user and the communication address of the user device, and transmits failure event information to the user device. Optionally, the terminal device may further generate a fault handling event in the office system corresponding to the fault handling user according to the fault handling user, import the fault event information into the fault handling event, and push the fault handling event to an account corresponding to the fault handling user in the office system.
[0050] In S103, a fault event monitoring process is started to acquire fault repair data and a fault repair result generated when the fault processing user repairs the fault event information.
[0051] In this embodiment, after receiving the failure event information, the failure processing user performs a repair operation on the failure condition of the database, so as to perform manual repair on a failure that cannot be automatically repaired by the database. And meanwhile, the terminal equipment also starts a fault event monitoring process for acquiring fault repair data generated by the fault condition inches corresponding to the fault event repair information of the fault processing user. Specifically, the terminal device launches an independent thread, and the thread continuously monitors parameter modification operation in the database, wherein the parameters comprise running parameters of the database, script files, table structures, change conditions of stored data and the like. And the terminal equipment stores the acquired fault repairing data in a storage area corresponding to the fault event information, wherein the storage area contains the event identifier of the fault event information.
[0052] In this embodiment, the terminal device may launch multiple threads with the inch enable module, and is configured to acquire fault repair data of different fault event information. The database fault examination terminal or the terminal device may examine that the database is in a plurality of fault conditions within a certain time interval, so as to generate a plurality of fault event information, and therefore, in order to determine the repair condition corresponding to each fault event information, the terminal device launches a plurality of threads, and each thread detects fault repair data corresponding to one fault event information and stores the fault repair data into a corresponding storage region. [0053] In this embodiment, the manner of acquiring the fault repair data by the terminal device specifically includes: the terminal equipment obtains various parameters in the database at preset time intervals, compares the currently acquired parameters with the parameters corresponding to the last acquired time, determines the changed parameter condition, and takes the changed parameter condition as the fault repair data in the repair process, thereby realizing incremental storage of the fault repair data and reducing the data volume of the fault repair data and the storage pressure of the terminal equipment.
[0054] In this embodiment, if the terminal device receives a fault repair completion instruction sent by a fault processing user, it determines that the fault event information has been repaired, and identifies a processing result included in the fault repair completion instruction as a fault repair result. Optionally, if the terminal device does not detect that the parameter of the database changes outside the preset maximum repair waiting time, it indicates that the user does not repair the database any more, and also indicates that the repair operation is completed, so that in this case, the terminal device also recognizes that the fault event information has been processed, and obtains a corresponding fault repair result according to the current operation condition of the database.
[0055] Optionally, in this embodiment, the terminal device acquires the failure repair result inch, and may suspend collecting the failure repair data. In this case, if the terminal device receives a failure repair confirmation instruction returned by the audit account, the related operation of S105 is executed; otherwise, if the terminal device does not receive the fault repairing confirmation instruction returned by the audit account, the fault event monitoring process is restarted to continue to collect the fault repairing data.
[0056] In S104, the fault repairing result is pushed to an audit account corresponding to the fault handling user.
[0057] In this embodiment, after determining that the fault event information of the database has been repaired, the terminal device performs an operation of approving and confirming the fault processing result, so as to ensure that the fault repairing result is correct and error-free. The terminal device checks an audit account corresponding to a fault processing user who inquires to perform repair operation, wherein the audit account can be a superior user of the fault processing user or an administrator of the database, and the administrator of the database is responsible for monitoring, managing and permission of the whole database.
[0058] Optionally, in this embodiment, the terminal device further sends the fault repairing result to the fault processing user. Because some repairing operations may require the database to automatically run for a long period of time, the fault handling user does not need to keep track of the database during the automatic running process, and after the automatic repairing program is run by the database, the corresponding fault repairing result can be pushed to the fault handling user, so that the fault handling user can confirm that the repairing operations are completed.
[0059] Corresponding to the manner of pushing the failure processing result to the failure processing user, in this embodiment, the manner of pushing the failure processing result to the audit account by the terminal device includes: after the terminal determines the audit account, the device corresponding to the audit account and the communication address of the device are inquired, and a fault processing result is sent to the device. The pushing mode comprises the following steps: the terminal equipment generates a fault checking event in the office system, the fault processing result is imported into the fault checking event, and the fault checking event is pushed to a checking account corresponding to a fault processing user in the office system.
[0060] In S105, if a failure repair confirmation instruction returned from the checked account is received, the failure event monitoring process is closed.
[0061] In this embodiment, when the audit account receives a failure processing result inch pushed by the terminal device, it may be determined whether the failure repairing operation is completed based on the failure processing result. If the audit account accepts the fault processing result and determines that the fault repairing operation is completed, a fault repairing confirmation instruction is generated and sent to the terminal equipment; and if the audit account does not accept the fault processing result and the fault processing user needs to perform repair processing on the fault processing event again, generating a fault repair instruction to the terminal device, and if the terminal device receives the fault repair instruction, returning to execute the operation of S102 to prompt the fault processing user to perform processing on the fault event again.
[0062] In this embodiment, after receiving the failure repair confirmation instruction returned by the audit account, the terminal device determines that the failure event information has been successfully repaired, and therefore, it is not necessary to collect repair data for the event, and therefore, the failure event monitoring process is closed, the failure repair data and the corresponding failure repair result are encapsulated in a data packet, and the data packet is stored as a repair record of the database.
[0063] As can be seen from the above, the response method for a database fault according to the embodiments of the present invention determines a 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 handling user, so that the user can repair the fault contained in the database according to the fault characteristic parameter contained in the fault event information and the fault repair scheme matched with the fault characteristic parameter, and as long as this time, the response terminal for the database fault starts the fault event monitoring process, so as to acquire fault repair data obtained by the fault handling user during the process of repairing the fault event information and the fault repair result generated after the repair are completed in time, and automatically push the fault repair result to the audit account corresponding to the fault handling user, and if a fault repair confirmation instruction returned by the audit account is received, the fault repair event is correctly repaired, and the fault response process can be ended. Compared with the existing database fault response technology, the embodiment of the invention can determine that the database has the fault event inches, namely the inches feed back the fault condition to the corresponding fault processing user, thereby reducing the difference between the inches between the fault occurrence and the fault discovery, realizing the purpose of real inch reporting the fault condition, avoiding the need that the user frequently logs in the database to confirm whether the fault event exists or not, and avoiding the aggravation of the fault condition. On the other hand, after the repair result is obtained, the embodiment of the invention also pushes the corresponding repair result to the corresponding audit account, so that the repair result passes through more review processes, and the accuracy of the repair result is ensured.
[0064] Fig. 2 shows a flowchart of a specific implementation of a database fault response method according to a second embodiment of the present invention. Referring to fig. 2, with respect to the embodiment shown in fig. 1, the method for responding to a database fault according to this embodiment further includes steps S201 to S203, which are detailed as follows:
[0065] further, if a failure recovery confirmation instruction returned by the audited account is received, after the failure event monitoring process is closed, the method further includes:
[0066] in S201, the repair feature parameters of the fault repair data are extracted, and the repair feature parameters are matched with a preset repair scheme library.
[0067] In this embodiment, after completing the fault repairing operation of the database, the terminal device learns the repairing process of the fault handling user, so as to increase the number of solutions in the fault repairing solution library. The method comprises the steps that a terminal device firstly determines the fault type of fault event information, acquires fault repair data corresponding to a fault event from a storage area corresponding to a fault event monitoring process, and extracts repair characteristic parameters from the fault repair data, wherein the repair characteristic parameters are parameters for a fault processing user to modify a database by eliminating fault event information inches, and the parameters comprise one or a combination of at least two of the following parameters: the running parameters of the database, the script file, the table structure and the change condition of the stored data. Optionally, the terminal device may further compare the database parameters of the time-out failure and the database parameters of the time-out failure repair completion time one by one, so as to obtain the repair characteristic parameters.
[0068] In this embodiment, the terminal device is preset with a repair scheme library for recording fault repair schemes corresponding to different fault types. The repair scheme library can be stored in a storage module built in the terminal equipment, and under the condition, the terminal equipment can directly read a local storage module to obtain data contained in the repair scheme library; the repair plan library may also be stored in an independent database server or other terminal device, and 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 of the repair plan library to acquire data in the repair plan library.
[0069] In this embodiment, after acquiring the repair characteristic parameters, the terminal device matches the repair characteristic parameters of each fault repair scheme included in the repair scheme library, thereby determining whether the fault repair means is recorded in the repair scheme library. The repair characteristic parameter is extracted from the fault repair data in the process of repairing the fault event information, so that the repair characteristic parameter can represent a fault repair scheme corresponding to the database repair time performed by the user. If the repair characteristic parameters are matched with any fault repair scheme, the repair means of the two are consistent, and the two belong to the same fault repair scheme; if the repair characteristic parameter is not matched with any fault repair scheme in the repair scheme library, it indicates that the repair process corresponding to the fault repair data belongs to a new repair scheme, so the operations of S202 and S203 are executed to add the new repair scheme to the repair scheme library.
[0070] In S202, if the repair characteristic parameter does not have a matching fault repair scheme in the preset repair scheme library, a fault repair scheme is newly created.
[0071] In this embodiment, if the terminal device cannot find the fault repairing scheme matching the repairing characteristic parameter in the repairing scheme library, a new fault repairing scheme is established in the repairing scheme library to record the fault repairing means that is not included. Optionally, the terminal device may also build a failure recovery scheme locally, and send the failure recovery scheme to the recovery scheme library after the generation is completed, so that the recovery scheme library stores the failure recovery scheme.
[0072] In this embodiment, the fault repairing scheme is specifically a scheme template, which includes a plurality of contents to be filled and a part of standard format contents, and sets a scheme unique identification code for the scheme module. Specifically, the fault repairing scheme templates corresponding to each repairing scheme library may have differences, and therefore, before a new fault repairing scheme is created, the terminal device needs to obtain the scheme template from the repairing scheme library.
[0073] In S203, the repair characteristic parameter is imported to the newly-built fault repair scheme and stored in the preset repair scheme library.
[0074] In this embodiment, after a fault repairing scheme is newly created, the terminal device imports each parameter item included in the extracted repairing characteristic parameters into a position corresponding to the fault repairing scheme. Preferably, the terminal device further imports the fault characteristic parameter in the fault event information into the fault repairing scheme, so as to determine a fault repairing scheme inch corresponding to the fault event information later, and can establish the fault event information imported in the inch based on the fault repairing scheme to determine whether the fault event information and the fault repairing scheme are matched.
[0075] In this embodiment, after the terminal device imports the repair characteristic parameter into the fault repair scheme, the fault repair scheme is already established, and therefore the fault repair scheme is stored in the repair scheme library, so that when a similar fault condition inch is encountered, the terminal device can directly automatically repair the database according to the repair operation of the fault repair scheme, or when a related fault condition inch is encountered, the terminal device can also push the fault repair scheme to the fault handling user for reference.
[0076] In the embodiment of the invention, after each repair is finished, the repair characteristic parameter corresponding to the repair operation is obtained, whether the repair operation is recorded or not is determined, and a new fault repair scheme is created and stored for the repair means of a new database, so that the fault repair scheme can be learned after each operation, the automatic repair capability of the repair scheme library is improved, the field repair times of fault processing users are reduced, and the repair efficiency is improved.
[0077] Fig. 3 shows a flowchart of a specific implementation of S103 in the method for responding to a database fault according to the third embodiment of the present invention. Referring to fig. 3, with respect to the embodiment described in fig. 1, S103 in the method for responding to a database fault according to this embodiment includes the following steps, which are detailed as follows:
[0078] further, the starting of the fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user repairing the fault event information inch includes:
[0079] in S301, a resource repair request instruction initiated by the fault handling user is received, and resource scheduling information is generated based on the resource repair request instruction.
[0080] In this embodiment, in the process of repairing information between fault inches in the database, the fault handling user needs to apply for an additional resource inch to be repaired, and may send a resource repair request instruction to the terminal device, or generate the resource repair request instruction through a client built in the terminal device, so that the terminal device may apply for a repair resource required in the fault repair process to a corresponding principal based on the resource repair request instruction.
[0081] In this embodiment, the repair resource request instruction includes a repair resource type and a resource quantity required by the user, and particularly, may further include time limit information of resource invocation. The terminal equipment can generate a filling interface for repairing the resource request information through the display module, and after the fault processing user fills the required data in the information filling interface, a corresponding repairing resource request instruction is generated, and an application flow of an additional resource repairing instruction is started.
[0082] In this embodiment, after receiving a request instruction for repairing resources initiated by a user, a terminal device generates resource scheduling information for each request content based on resource request content included in the request instruction for repairing resources.
[0083] In S302, according to a preset resource management responsibility list, a resource management account corresponding to the resource repairing request instruction is determined, and the resource scheduling information is pushed to the resource management account. [0084] In this embodiment, the terminal device storage module records the management responsible person corresponding to each resource, that is, the resource management account. Wherein the resources include, but are not limited to: database resources, network resources, peripheral module resources, privilege resources, and the like. Different resources are managed by different resource accountants. Therefore, the terminal device first determines a target object corresponding to the request according to the repair resource request instruction.
[0085] In this embodiment, the terminal device extracts the resource type included in the repaired resource request instruction, checks a preset resource management responsibility list, determines a resource management responsible person corresponding to the resource type and a resource management account corresponding to the responsible person, and pushes the resource scheduling information generated in S301 to the resource management account.
[0086] Specifically, in this embodiment, the pushing manner is consistent with the manner of pushing to the fault handling user, the resource scheduling information may be directly sent to the terminal device corresponding to the resource management account, or a resource scheduling event may be generated in the office system, and the resource scheduling event is added to the to-do event of the resource management account. Preferably, the terminal device further determines a processing inch limit of the resource management account according to the database fault level and the requested resource type, so that the resource management account and the inch perform corresponding processing to the resource request instruction.
[0087] In S303, if a scheduling confirmation instruction returned by the resource management account is received, adding the usage right of the repair resource corresponding to the repair resource request instruction to the right parameter of the fault handling user
[0088] In this embodiment, after receiving the resource scheduling information pushed by the terminal device, the resource management account determines to agree to an application of the fault handling user for additionally repairing the resource according to the actual situation. Specifically, if the resource management account agrees with the request of the fault handling user, a scheduling confirmation instruction is returned to the terminal device, and the relevant operation of S303 is executed; otherwise, if the resource management account does not agree with the request of the fault processing user, returning a scheduling refusing instruction to the terminal equipment, and ending the scheduling application process. Specifically, if the resource management account agrees with the application of the fault handling user, but no resource that can be called currently exists, a scheduling suspension instruction is sent, the terminal device acquires the available resource condition at preset time intervals, and if it is detected that sufficient resources exist, the relevant operation of S303 is executed.
[0089] In this embodiment, after receiving the scheduling confirmation instruction, the terminal device obtains the usage right of the repair resource corresponding to the repair resource request instruction, optionally, the usage right may be a dynamic key, and before invoking the repair resource, the identity of the caller needs to be checked. After the terminal device acquires the use right of the repair resource, the right information is added into the right parameter of the fault processing user, and the fault processing user can call the repair resource to repair the fault of the database only through the corresponding account name or the corresponding device or the identification information.
[0090] Optionally, in this embodiment, after the fault handling user completes the repair of the fault event information, after S105, the terminal device performs a logout on the permission content of the permission applied to call the repair resource in the permission parameter of the fault handling user, and/or adjusts a call rule of the repair resource, and adjusts the use state of the corresponding repair resource to be idle, so that other users call and apply the permission.
[0091] In the embodiment of the invention, the fault processing user can apply for additional fault repairing resources through the terminal equipment, so that the fault of the database can be repaired more quickly.
[0092] Fig. 4 shows a flowchart of a concrete implementation of the database fault response method S101 according to the fourth embodiment of the present invention. Referring to fig. 4, in comparison with the embodiments shown in fig. 1 to 3, the method for responding to a database failure according to the present embodiment further includes steps S401 to S403, which are detailed as follows:
[0093] in S401, if it is detected that the database is in a failure condition, a failure characteristic parameter of the failure condition is obtained.
[0094] In this embodiment, the terminal device may determine whether a failure condition exists in the database through a built-in failure detection algorithm; correspondingly, the terminal device can also acquire whether the database has a fault condition by receiving a fault trigger instruction sent by other devices or the database server.
[0095] In this embodiment, when the terminal device detects that the database is in a failure condition, the fault characteristic parameter of the database is obtained through a preset fault characteristic parameter extraction algorithm. Wherein the status operation data includes but is not limited to: the data redundancy rate of the database, the average read-write rate reduction ratio of the database, the data storage condition of each partition in the database, the distribution abnormal condition of the storage address of each partition, the operation state of the database medium, the operation overflow rate and the like.
[0096] Optionally, if the terminal device determines that the database has a fault condition through a fault trigger instruction sent by another device or the database server, the fault trigger instruction includes an operation parameter of the database. And the terminal equipment determines the abnormal module and function of the database by matching the operation parameters with the preset standard operation parameters, and takes the operation parameters corresponding to the module and the function as fault characteristic parameters. [0097] In S402, the fault repairing scheme matching the fault characteristic parameter is determined based on a preset fault repairing scheme determining algorithm.
[0098] In this embodiment, the preset fault repairing scheme determining algorithm specifically includes: and the terminal equipment matches the extracted fault characteristic parameters with the fault characteristic parameters of each fault repairing scheme, and then determines the fault repairing scheme corresponding to the fault characteristic parameters. Wherein the fault repair scheme is stored in a repair scheme library
[0099] In this embodiment, the preset fault repairing scheme determining algorithm may also be: the method comprises the steps that the terminal equipment locates a plurality of causes possibly causing the fault according to fault characteristic parameters, such as the position of the fault, affected function modules, fault operation parameters and other related information, tests one by one through a preset fault cause determining algorithm, determines abnormal information causing the fault, and extracts a corresponding repair scheme from a repair scheme resource library according to the abnormal information.
[0100] In S403, the fault event f pi information is generated according to the fault repairing scheme and the fault characteristic parameter.
[0101] In this embodiment, the terminal device encapsulates the acquired fault characteristic parameter and the fault repairing scheme matched with the fault characteristic parameter in the fault event information to generate the fault event information.
[0102] In the embodiment of the invention, when the terminal equipment detects the time of the fault condition of the database, the terminal equipment actively acquires the fault characteristic parameters of the fault condition and matches the corresponding fault repairing scheme, thereby improving the fault repairing performance and time property and further improving the repairing efficiency.
[0103] Fig. 5 is a flowchart illustrating a specific implementation of a database fault response method according to a fifth embodiment of the present invention. Referring to fig. 5, with respect to the embodiment shown in fig. 2, the method for responding to a database fault according to this embodiment further includes the following steps, which are detailed as follows:
[0104] further, before the obtaining the failure event information of the database, the method further includes:
[0105] in S5011, fault recovery schemes for other databases are acquired at preset intervals of inches.
[0106] In this embodiment, the terminal device may expand the amount of the scheme of the preset repair scheme library in a manner of sharing the fault repair scheme to other database servers, in addition to generating the fault repair scheme through the fault repair data of the fault handling user.
[0107] In this embodiment, the terminal device may be configured to repair the fault event information of one database, and in this case, the other databases may be located in the same database system as the database and connected to the database system through an intranet of the database system, so that the terminal device may also obtain, through the internal network of the database system, the fault repair solution stored in the repair solution library of the other database.
[0108] In this embodiment, the terminal device may also be configured to repair failure event information of a plurality of databases of one database system, and in this case, the other databases may be databases located outside the database system, so that the terminal device is in communication connection with the other databases through an external communication network, and obtains a failure repair scheme for the other databases at preset time intervals.
[0109] In S5012, a fault repairing scheme sent by the server corresponding to the database is received at preset time intervals.
[0110] In this embodiment, the terminal device may obtain a new fault repairing scheme from the repairing scheme library of another database, and may also obtain a newly updated fault repairing scheme through a higher-level server corresponding to the database. The superior server may be: and a server for performing update operations such as version update on the database. The upper-level server uploads a fault repairing scheme aiming at version bugs or common problems within preset inches, and the terminal equipment can acquire the fault repairing scheme corresponding to the version information of the database in real inches through the upper-level server.
[0111] In this embodiment, the upper level server may also be a server dedicated to collecting the failure recovery schemes of the vendors and the regional databases. The terminal equipment further obtains the fault repairing schemes corresponding to different fault repairing users at home and abroad by sending the fault repairing schemes to the superior server, so that the number of the schemes in the repairing scheme library is greatly increased.
[0112] In S502, the failure repair scenario is added to the preset repair scenario library.
[0113] In this embodiment, the terminal device uploads the fault repairing schemes collected in S5011 and S5012 to a preset repairing scheme library, thereby achieving the purpose of intelligent learning of the repairing scheme library.
[0114] In the embodiment of the invention, the fault repairing scheme is learned to other databases or superior servers, so that the repairing range and the repairing type of the terminal equipment can be improved, and the repairing efficiency of the database is improved.
[0115] It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
[0116] Fig. 6 shows a block diagram of a database failure response terminal according to an embodiment of the present invention, where the database failure response terminal includes units for executing the steps in the embodiment corresponding to fig. 1. Please refer to fig. 1 and the related description of the embodiment corresponding to fig. 1. For convenience of explanation, only the portions related to the present embodiment are shown.
[0117] Referring to fig. 6, the response terminal to the database failure includes:
[0118] a failure event information obtaining module 61, configured to obtain failure event information of the database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters; [0119] a fault handling user determining module 62, configured to determine, based on the fault characteristic parameter, a fault handling user corresponding to the fault event information, and push the fault event information to the fault handling user; 0120, a fault event monitoring process starting module 63, configured to start a fault event monitoring process, so as to collect fault repair data and a fault repair result generated when the fault processing user repairs the fault event information inch; 0121, an audit account information pushing module 64, configured to push the fault repairing result to an audit account corresponding to the fault handling user;
[0122] and the fault repairing confirmation instruction receiving module 65 is configured to close the fault event monitoring process if a fault repairing confirmation instruction returned by the checked account is received.
[0123] Optionally, the response terminal of the database failure further includes:
[0124] the repair characteristic parameter matching module is used for extracting repair characteristic parameters of the fault repair data and matching the repair characteristic parameters with a preset repair scheme library;
[0125] a failure recovery scheme creating module, configured to create a failure recovery scheme if the recovery characteristic parameter does not have a failure recovery scheme matching the failure recovery characteristic parameter in the preset recovery scheme library;
[0126] and the fault repairing scheme learning module is used for importing the repairing characteristic parameters into the newly-built fault repairing scheme and storing the repairing characteristic parameters in the preset repairing scheme library.
[0127] Optionally, the fault event monitoring process starting module 63 includes:
[0128] a repair resource request instruction receiving module, configured to receive a repair resource request instruction initiated by the fault repair user, and generate resource scheduling information based on the repair resource request instruction;
[0129] the resource management system comprises a resource management request module, a repair resource application module and a resource management module, wherein the resource management request module is used for sending a resource request instruction to a resource management account; [0130] a repair resource permission adding module for receiving the scheduling confirmation instruction returned by the resource management account
And adding the use permission of the repair resource corresponding to the repair resource request instruction to the permission parameter of the fault repair user. [0131] Optionally, the failure event information obtaining module 61 includes:
[0132] the fault characteristic parameter extraction module is used for acquiring fault characteristic parameters of the fault condition if the database is detected to be in the fault condition;
[0133] the fault repairing scheme determining module is used for determining the fault repairing scheme matched with the fault characteristic parameters based on a preset fault repairing scheme determining algorithm;
[0134] and the fault event information generating module is used for generating the fault event information according to the fault repairing scheme and the fault characteristic parameters.
[0135] Optionally, the response terminal for the database failure further includes:
[0136] the first repair scheme acquisition module is used for acquiring fault repair schemes of other databases at preset time intervals; and/or
[0137] A second repair scheme acquisition module, configured to receive, at preset time intervals, a fault repair scheme sent by a server corresponding to the database;
[0138] and the fault repairing scheme base adding module is used for adding the fault repairing scheme to the preset repairing scheme base.
[0139] Therefore, the response terminal for the database fault provided by the embodiment of the present invention can also determine the fault handling user corresponding to the fault event information by obtaining the fault event information of the database, and push the fault event information to the determined fault handling 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 scheme matched with the fault characteristic parameters, and as well, the response terminal for the database fault starts the fault event monitoring process, so as to acquire the fault repair data obtained by the fault handling user in the process of repairing the fault event information in time, and the fault repair result generated after the repair is completed, and automatically push the fault repair result to the audit account corresponding to the fault handling user, and if a fault repair confirmation instruction returned by the audit account is received, the fault repair event is correctly repaired, and the fault response process can be finished. Compared with the existing database fault response technology, the embodiment of the invention can determine the database to be in the fault event inches, namely the inches feed back the fault condition to the corresponding fault processing user, thereby reducing the difference between the inches from the fault occurrence to the fault discovery, realizing the purpose of real inch reporting the fault condition, avoiding the need of frequently logging in the database by the user to confirm whether the fault event exists or not and avoiding the aggravation of the fault condition. On the other hand, after the repair result is obtained, the embodiment of the invention also pushes the corresponding repair result to the corresponding audit account, so that the repair result passes through more review processes, and the accuracy of the repair result is ensured
[0140] Fig. 7 is a schematic diagram of a terminal device according to another embodiment of the present invention. As shown in fig. 7, the terminal device 7 of this embodiment includes: a processor 70, a memory 71 and a computer program 72 stored in said memory 71 and operable on said processor 70, such as a response program to a database failure. The processor 70 executes the computer program 72 inches to implement the steps in the response method embodiment of the above database failure, for example, S101 to S105 shown in fig. 1. Alternatively, the processor 70 executes the computer program 72 inches to implement 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.
[0141] Illustratively, the computer program 72 may be divided into one or more units, which are stored in the memory 71 and executed by the processor 70 to accomplish the present invention. The one or more units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 72 in the terminal device 7. For example, the computer program 72 may be divided into an operation failure event information obtaining module, a failure processing user determining module, a failure event monitoring process starting module, an audit account information pushing module, and a failure repair confirmation instruction receiving module, where the specific functions of each unit are as follows:
[0142] the fault event information acquisition module is used for acquiring fault event information of the database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;
[0143] the fault processing user determining module is used for determining a fault processing user corresponding to the fault event information based on the fault characteristic parameters and pushing the fault event information to the fault processing user;
[0144] a fault event monitoring process starting module, configured to start a fault event monitoring process to acquire fault repair data and a fault repair result, where the fault event information inch is repaired by the fault processing user;
[0145] the audit account information pushing module is used for pushing the fault repairing result to an audit account corresponding to the fault processing user;
[0146] and the fault repairing confirmation instruction receiving module is used for closing the fault event monitoring process if a fault repairing confirmation instruction returned by the checked account is received. .
[0147] The terminal device 7 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 70, a memory 71. It will be appreciated by those skilled in the art that fig. 7 is merely an example of a terminal device 7 and does not constitute a limitation of the terminal device 7 and may comprise more or less components than shown, or some components may be combined, or different components, for example the terminal device may further comprise input output devices, network access devices, buses, etc.
[0148] The Processor 70 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), or an Application Specific Integrated Circuit (ASIC)
An ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
[0149] The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (12)
- Claims
- [ claim 1] A database failure response method, comprising:acquiring fault event information of a database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;determining a fault processing user corresponding to the fault event information based on the fault characteristic parametersAnd pushing the fault event information to the fault processing user;starting a fault event monitoring process to acquire fault repair data and fault repair results generated by the fault processing user in repairing the fault event information inch; pushing the fault repairing result to an auditing account corresponding to the fault processing user; and if a fault repairing confirmation instruction returned by the checked account is received, closing the fault event monitoring process.
- [ claim 2] the response method according to claim 1, characterized in that the response method of the database failure further comprises:extracting the repair characteristic parameters of the fault repair data, and matching the repair characteristic parameters with a preset repair scheme library;if the repair characteristic parameters do not have fault repair schemes matched with the repair characteristic parameters in the preset repair scheme library, a fault repair scheme is newly established;and importing the repair characteristic parameters into the newly-built fault repair scheme, and storing the repair characteristic parameters in the preset repair scheme library.
- The response method according to claim 3, wherein the starting of the fault event monitoring process to collect fault repair data generated by the fault processing user repairing the fault event information and fault repair results comprises:receiving a resource repairing request instruction initiated by the fault processing user, and generating resource scheduling information based on the resource repairing request instruction;determining a resource management account corresponding to the resource repairing request instruction according to a preset resource management responsibility list, and pushing the resource scheduling information to the resource management account; and if a scheduling confirmation instruction returned by the resource management account is received, adding the use permission of the repaired resource corresponding to the repaired resource request instruction to the permission parameter of the fault processing user.
- [ claim 4] the response method according to any one of claims 1 to 3, wherein the acquiring fault event information of the database includes:if the database is detected to be in a fault condition, acquiring fault characteristic parameters of the fault condition;determining the fault repairing scheme matched with the fault characteristic parameters based on a preset fault repairing scheme determination algorithm;and generating the fault event information according to the fault repairing scheme and the fault characteristic parameters.
- [ claim 5] the response method according to claim 2, characterized in that the response method further comprisesAcquiring fault repairing schemes of other databases at preset time intervals; and/or receiving a fault repairing scheme sent by a server corresponding to the database at preset time intervals, and adding the fault repairing scheme into the preset repairing scheme library.
- [ claim 6] A database failure response terminal, comprising:the fault event information acquisition module is used for acquiring fault event information of the database; the fault event information comprises fault characteristic parameters and fault repair schemes matched with the fault characteristic parameters;the fault processing user determining module is used for determining a fault processing user corresponding to the fault event information based on the fault characteristic parameters and pushing the fault event information to the fault processing user;a fault event monitoring process starting module, configured to start a fault event monitoring process to acquire fault repair data and a fault repair result, where the fault event information is repaired by the fault processing user;the audit account information pushing module is used for pushing the fault repairing result to an audit account corresponding to the fault processing user;and the fault repairing confirmation instruction receiving module is used for closing the fault event monitoring process if a fault repairing confirmation instruction returned by the checked account is received.
- [ claim 7] the response terminal according to claim 6, wherein the response terminal for the database failure further comprises:the repair characteristic parameter matching module is used for extracting repair characteristic parameters of the fault repair data and matching the repair characteristic parameters with a preset repair scheme library;a failure recovery scheme creating module, configured to create a failure recovery scheme if the recovery characteristic parameter does not have a failure recovery scheme matching the failure recovery characteristic parameter in the preset recovery scheme libraryAnd the fault repairing scheme learning module is used for importing the repairing characteristic parameters into the newly-built fault repairing scheme and storing the repairing characteristic parameters in the preset repairing scheme library.
- [ claim 8] the response terminal according to claim 6, wherein the fault event monitoring procedure starting module comprises:a resource repair request instruction receiving module, configured to receive a resource repair request instruction initiated by the fault handling user, and generate resource scheduling information based on the resource repair request instruction; the repair resource application module is used for determining a resource management account corresponding to the repair resource request instruction according to a preset resource management responsibility list and pushing the resource scheduling information to the resource management account;and the repaired resource permission adding module is used for adding the use permission of the repaired resource corresponding to the repaired resource request instruction to the permission parameter of the fault processing user if the scheduling confirmation instruction returned by the resource management account is received.
- The fault repairing scheme determining module is used for determining the fault repairing scheme matched with the fault characteristic parameters based on a preset fault repairing scheme determining algorithm; and the fault event information generating module is used for generating the fault event information according to the fault repairing scheme and the fault characteristic parameters. [ claim 10] the response terminal according to claim 7, wherein the response terminal of the database failure further comprises:the first repair scheme acquisition module is used for acquiring fault repair schemes of other databases at preset time intervals; and/orA second repair scheme acquisition module, configured to receive, at preset time intervals, a fault repair scheme sent by a server corresponding to the database;and the fault repairing scheme base adding module is used for adding the fault repairing scheme to the preset repairing scheme base.
- [ claim 11] A terminal device comprising a memory, a processor and a computer program stored in said memory and executable on said processor, characterized in that said processor executes said computer program to implement the steps of the method according to any one of claims 1 to 5.
- [ claim 12] A computer-readable storage medium having stored thereon a computer program, characterized in that the computer program is executable by a processor for implementing the steps of the method according to any one of claims 1 to 5 in inches.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2017/100750 WO2019047071A1 (en) | 2017-09-06 | 2017-09-06 | Method and terminal for responding to database fault |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110063042A true CN110063042A (en) | 2019-07-26 |
| CN110063042B CN110063042B (en) | 2022-12-16 |
Family
ID=65633618
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201780000980.7A Active CN110063042B (en) | 2017-09-06 | 2017-09-06 | Database fault response method and terminal thereof |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110063042B (en) |
| WO (1) | WO2019047071A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113886132A (en) * | 2021-12-07 | 2022-01-04 | 深圳市明源云科技有限公司 | Intelligent web-side error repairing method and device and computer-readable storage medium |
| CN117035747A (en) * | 2023-10-09 | 2023-11-10 | 国网山东省电力公司博兴县供电公司 | Multi-system fault diagnosis processing method, system, equipment and medium for machine room |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245077A (en) * | 2019-05-22 | 2019-09-17 | 深圳壹账通智能科技有限公司 | A kind of response method and equipment of program exception |
| CN113741998B (en) * | 2021-08-16 | 2023-10-20 | 国网河北省电力有限公司检修分公司 | Data processing system and method of relay protection device with multiple plug-ins |
| CN115423129A (en) * | 2022-09-03 | 2022-12-02 | 太原市海通自动化技术有限公司 | Equipment fault defect management system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020193926A1 (en) * | 2001-05-08 | 2002-12-19 | Hitachi, Ltd. | Repair and maintenance support system and a car corresponding to the system |
| CN101605346A (en) * | 2008-06-10 | 2009-12-16 | 中兴通讯股份有限公司 | The fault restoration method and apparatus |
| CN102999394A (en) * | 2012-12-06 | 2013-03-27 | 大连奥林匹克电子城文豪电子经销处 | Computer software fault diagnosis and repair system |
| CN103678539A (en) * | 2013-12-04 | 2014-03-26 | 云南电力试验研究院（集团）有限公司电力研究院 | Maintenance strategy evaluation database system for electric transmission and transformation equipment |
| CN104202179A (en) * | 2014-08-18 | 2014-12-10 | 中国建设银行股份有限公司 | Fault management system of self-service equipment and background server |
| CN104795896A (en) * | 2015-04-17 | 2015-07-22 | 国家电网公司 | Automatic point-to-point short message notification method for client power failure information |
| CN105262616A (en) * | 2015-09-21 | 2016-01-20 | 浪潮集团有限公司 | Failure repository-based automated failure processing system and method |
| CN106169962A (en) * | 2016-09-13 | 2016-11-30 | 郑州云海信息技术有限公司 | A kind of storage system failure monitoring method and system |
| CN106407030A (en) * | 2016-09-13 | 2017-02-15 | 郑州云海信息技术有限公司 | Failure processing method and system for storage cluster system |
| CN106774078A (en) * | 2016-12-29 | 2017-05-31 | 深圳市捷顺科技实业股份有限公司 | A kind of parking lot intelligent management, equipment and system |
-
2017
- 2017-09-06 WO PCT/CN2017/100750 patent/WO2019047071A1/en active Application Filing
- 2017-09-06 CN CN201780000980.7A patent/CN110063042B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020193926A1 (en) * | 2001-05-08 | 2002-12-19 | Hitachi, Ltd. | Repair and maintenance support system and a car corresponding to the system |
| CN101605346A (en) * | 2008-06-10 | 2009-12-16 | 中兴通讯股份有限公司 | The fault restoration method and apparatus |
| CN102999394A (en) * | 2012-12-06 | 2013-03-27 | 大连奥林匹克电子城文豪电子经销处 | Computer software fault diagnosis and repair system |
| CN103678539A (en) * | 2013-12-04 | 2014-03-26 | 云南电力试验研究院（集团）有限公司电力研究院 | Maintenance strategy evaluation database system for electric transmission and transformation equipment |
| CN104202179A (en) * | 2014-08-18 | 2014-12-10 | 中国建设银行股份有限公司 | Fault management system of self-service equipment and background server |
| CN104795896A (en) * | 2015-04-17 | 2015-07-22 | 国家电网公司 | Automatic point-to-point short message notification method for client power failure information |
| CN105262616A (en) * | 2015-09-21 | 2016-01-20 | 浪潮集团有限公司 | Failure repository-based automated failure processing system and method |
| CN106169962A (en) * | 2016-09-13 | 2016-11-30 | 郑州云海信息技术有限公司 | A kind of storage system failure monitoring method and system |
| CN106407030A (en) * | 2016-09-13 | 2017-02-15 | 郑州云海信息技术有限公司 | Failure processing method and system for storage cluster system |
| CN106774078A (en) * | 2016-12-29 | 2017-05-31 | 深圳市捷顺科技实业股份有限公司 | A kind of parking lot intelligent management, equipment and system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113886132A (en) * | 2021-12-07 | 2022-01-04 | 深圳市明源云科技有限公司 | Intelligent web-side error repairing method and device and computer-readable storage medium |
| CN117035747A (en) * | 2023-10-09 | 2023-11-10 | 国网山东省电力公司博兴县供电公司 | Multi-system fault diagnosis processing method, system, equipment and medium for machine room |
| CN117035747B (en) * | 2023-10-09 | 2024-02-02 | 国网山东省电力公司博兴县供电公司 | Multi-system fault diagnosis processing method, system, equipment and medium for machine room |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110063042B (en) | 2022-12-16 |
| WO2019047071A1 (en) | 2019-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032824B (en) | Database verification method, database verification device, computer equipment and storage medium | |
| CN110063042B (en) | Database fault response method and terminal thereof | |
| US11263111B2 (en) | Validating software functionality | |
| KR102268355B1 (en) | Cloud deployment infrastructure validation engine | |
| US8954930B2 (en) | System and method for reducing test effort by object risk analysis | |
| US9417865B2 (en) | Determining when to update a package manager software | |
| CN110088744B (en) | Database maintenance method and system | |
| US20140068568A1 (en) | System and method for dynamically debugging data in a multi-tenant database environment | |
| US7624309B2 (en) | Automated client recovery and service ticketing | |
| CN110825420A (en) | Configuration parameter updating method, device, equipment and storage medium for distributed cluster | |
| CN112101803A (en) | Business process monitoring method, device, system, equipment and medium | |
| US9164857B2 (en) | Scalable structured data store operations | |
| CN110971464A (en) | Operation and maintenance automatic system suitable for disaster recovery center | |
| JP2022100301A (en) | Method for determining potential impact on computing device by software upgrade, computer program, and update recommendation computer server (recommendation of stability of software upgrade) | |
| CN111737227A (en) | Data modification method and system | |
| US8090994B2 (en) | System, method, and computer readable media for identifying a log file record in a log file | |
| CN111538754A (en) | Data collection management system, method, device, equipment and storage medium | |
| CN112269697B (en) | Equipment storage performance testing method, system and related device | |
| CN111737351A (en) | Transaction management method and device for distributed management system | |
| CN109116818B (en) | Real-time data dump method and device during SCADA system upgrade | |
| CN111694724A (en) | Testing method and device of distributed table system, electronic equipment and storage medium | |
| Cao et al. | Research on reliability evaluation of big data system | |
| US11323315B1 (en) | Automated host management service | |
| CN116149707B (en) | Method and device for detecting and avoiding upgrading risk of distributed system | |
| CN110008114B (en) | Configuration information maintenance method, device, equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |