Failure object processing method and device, equipment, medium and program product

Abstract

The invention provides a failure object processing method. The method can be applied to the distributed technical field and the big data technical field. The method comprises the steps of obtaining connection information of n databases, and performing data connection with the n databases based on the connection information of the n databases to generate m target databases completing data connection. And performing first failure object detection on the m target databases, and determining a target failure objects in the m target databases. And obtaining a target submission record of each target failure object in the a target failure objects, and determining a target submission interface corresponding to each target failure object in the a target failure objects based on the target submission record of each target failure object in the a target failure objects. And sending the a target failure objects based on the target submission interface corresponding to each target failure object in the a target failure objects. The invention further provides a failure object processing device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] This application relates to the field of big data technology, specifically to the field of distributed technology, and in particular to a method, apparatus, device, medium, and program product for handling failed objects. Background Technology

[0002] With the advancement of computer technology, enterprises, including banks, have gradually increased their demand for databases. During the use of databases, a large number of invalid objects will be generated in the database. In order to ensure the stability of the database, it is necessary to process the invalid objects in the data.

[0003] Current technologies for handling database failures typically rely on periodic manual checks, requiring the retrieval of a list of failed objects and manual tracing of script submission records. This method is prone to inefficiency, poor accuracy, and low reliability, leading to excessively long repair cycles and impacting the overall stability of the database system. Summary of the Invention

[0004] In view of the above problems, this application provides a method, apparatus, device, medium and program product for handling failed objects.

[0005] According to a first aspect of this application, a method for handling failed objects is provided. The method includes: acquiring connection information for n databases; establishing data connections with the n databases based on the connection information to generate m target databases with completed data connections, where n is an integer greater than 1, m is an integer greater than 0, and m is less than or equal to n; performing a first failed object detection on the m target databases to determine a target failed objects in the m target databases, where a is an integer greater than 1; acquiring the target submission record for each of the a target failed objects; determining the target submission interface corresponding to each of the a target failed objects based on the target submission record; and sending the a target failed objects based on the target submission interface corresponding to each of the a target failed objects.

[0006] According to an embodiment of this application, based on the connection information of the n databases, data connections are established with the n databases to generate m target databases with completed data connections. This includes: establishing network connections with the n databases based on the connection information of the n databases to generate n databases with completed network connections; sending preset verification data to the n databases with completed network connections to confirm the availability and access permissions of the databases; and establishing data connections with the m databases that return result data to generate m target databases with completed data connections, wherein the result data is the result data corresponding to the sent preset verification data.

[0007] According to an embodiment of this application, a first failure object detection is performed on the m target databases to determine a target failure objects in the m target databases, including: determining the database type of each database in the m target databases, the database type including: distributed relational database and centralized relational database; based on the database type of each database in the m target databases, a second failure object detection is performed on the m target databases to determine b failure objects in the m target databases, where b is an integer and b is greater than a; and a second compilation verification is performed on the b failure objects in the m target databases to determine a target failure objects in the m target databases.

[0008] According to an embodiment of this application, based on the database type of each of the m target databases, a second failure object detection is performed on the m target databases to determine b failure objects in the m target databases. This includes: determining i distributed relational databases among the m target databases; performing a joint search on the i distributed relational databases to determine c failure objects in the i distributed relational databases; wherein the joint search includes: performing a joint search on data packets, functions, and stored procedures, where i is an integer, i is greater than 0 and i is less than m, c is an integer, c is greater than 0 and c is less than b; determining j centralized relational databases among the m target databases; performing an invalid status identifier query on the j centralized relational databases to determine d failure objects in the j distributed relational databases, where j is an integer and j is greater than 0, the sum of i and j equals m, d is an integer and d is greater than 0, and the sum of d and c equals b; and merging the c failure objects and the d failure objects to generate b failure objects in the m target databases.

[0009] According to an embodiment of this application, performing secondary compilation verification on b failed objects in the m target databases to determine a target failed objects in the m target databases includes: performing secondary compilation on the b failed objects in the m target databases to generate b failed objects in the m target databases after secondary compilation; and performing third failed object detection on the b failed objects in the m target databases to determine a target failed objects in the m target databases.

[0010] According to an embodiment of this application, the object name of each of the a target failed objects is obtained; the object name of each of the a target failed objects is used as a keyword to retrieve e data submission records corresponding to each keyword, where e is an integer and e is greater than 0; the e data submission records corresponding to each keyword are partitioned and sorted in reverse chronological order using a partitioning window function; and the data submission record ranked first among the e data submission records corresponding to each keyword is obtained as the target submission record of each of the a target failed objects.

[0011] According to an embodiment of this application, the method further includes: obtaining repair objects and repair information for a target failed objects, and generating visual statistical data based on the repair objects and repair information for the a target failed objects.

[0012] According to a second aspect of this application, a failure object processing apparatus is provided, comprising: a first generation module, configured to acquire connection information of n databases, establish data connections with the n databases based on the connection information, and generate m target databases with completed data connections, wherein n is an integer and greater than 1, m is an integer and greater than 0, and m is less than or equal to n; a first determination module, configured to perform a first failure object detection on the m target databases and determine a target failure objects in the m target databases, wherein a is an integer and greater than 1; a second determination module, configured to acquire a target submission record for each of the a target failure objects, and determine a corresponding target submission interface for each of the a target failure objects based on the target submission record; and a first sending module, configured to send the a target failure objects based on the corresponding target submission interface of each of the a target failure objects.

[0013] According to a third aspect of this application, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0015] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0016] This application employs a technical approach that connects to multiple databases, performs failure object detection on each database, determines the corresponding commit interface for each failure object, and then sends the failure object to the appropriate database. By processing only databases with completed data connections, it avoids process interruptions caused by partial database connection failures, thus improving the stability and robustness of failure object handling. Simultaneously connecting to multiple databases for batch failure object detection improves processing efficiency. Determining the target commit interface and sending the target failure object ensures that the failure object is sent to the correct interface, improving the accuracy of failure object handling. Overall, this application effectively improves the efficiency, accuracy, stability, and robustness of failure object handling. It addresses the technical problem in existing technologies where database failure object management relies primarily on manual periodic checks, requiring manual tracing of script commit records from the version control system's failure object list. This results in low efficiency, poor accuracy, and low reliability, leading to excessively long repair cycles and impacting the overall stability of the database system. Attached Figure Description

[0017] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0018] Figure 1 The illustrations depict application scenarios of the failure object handling method, apparatus, device, medium, and program product according to embodiments of this application.

[0019] Figure 2 A flowchart illustrating a method for handling failed objects according to an embodiment of this application is shown schematically.

[0020] Figure 3 This illustration schematically shows a flowchart of generating m target databases with completed data connections in a failed object handling method according to an embodiment of this application;

[0021] Figure 4 This illustration schematically shows a flowchart of determining a target failed objects from m target databases in a failed object processing method according to an embodiment of this application;

[0022] Figure 5This illustration schematically shows a flowchart of determining b failed objects from m target databases in a failed object processing method according to an embodiment of this application;

[0023] Figure 6 This illustration schematically shows a flowchart of a secondary compilation verification process in a failed object handling method according to an embodiment of this application;

[0024] Figure 7 This illustration schematically shows a flowchart of obtaining the target submission record in the failed object handling method according to an embodiment of this application;

[0025] Figure 8 This schematic diagram illustrates a structural block diagram of a failed object processing apparatus according to an embodiment of the present application;

[0026] Figure 9 A block diagram schematically illustrates an electronic device suitable for implementing a failed object handling method according to an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0029] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0030] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0031] The accompanying drawings show some block diagrams and / or flowcharts. It should be understood that some blocks or combinations thereof in the block diagrams and / or flowcharts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable control device, so that when executed by the processor, these instructions can create means for implementing the functions / operations described in these block diagrams and / or flowcharts.

[0032] First, the technical terms used in this article are explained as follows:

[0033] Failed objects refer to database objects that cannot be used normally due to dependency changes, structural changes, or compilation errors, specifically failed stored procedures and failed indexes.

[0034] An IP (Internet Protocol) address is a fundamental protocol of the Internet and a unique logical representation of a device in a network. It is generally used to achieve precise addressing and communication between devices.

[0035] SQL (Structured Query Language) is a standard programming language used for managing and manipulating relational databases. It allows users to store, query, update, and manage data.

[0036] This application provides a method for handling failed objects, comprising: acquiring connection information of n databases; establishing data connections with the n databases based on the connection information to generate m target databases with completed data connections, wherein n is an integer greater than 1, m is an integer greater than 0, and m is less than or equal to n; performing a first failed object detection on the m target databases to determine a target failed objects in the m target databases, wherein a is an integer greater than 1; acquiring the target submission record of each of the a target failed objects; determining the target submission interface corresponding to each of the a target failed objects based on the target submission record of each of the a target failed objects; and sending the a target failed objects based on the target submission interface corresponding to each of the a target failed objects.

[0037] According to the embodiments of this application, a technical means of connecting multiple databases, detecting failed objects in multiple databases, determining the corresponding submission interface for each failed object, and sending the failed object is adopted. By processing only databases with completed data connections, process interruptions caused by partial database connection failures are avoided, thus improving the stability and robustness of failed object processing. By simultaneously connecting multiple databases for batch failed object detection, the efficiency of failed object processing is improved. By determining the target submission interface and sending the target failed object, it is ensured that the failed object is sent to the correct interface, thus improving the accuracy of failed object processing. Overall, this achieves the technical effect of effectively improving the efficiency of failed object processing and significantly improving the accuracy, stability, and robustness of failed object processing. It solves the technical problem in the prior art where the governance of database failed objects mainly relies on manual periodic checks, which requires manually tracing script submission records from the version control system from the failed object list in the database. This results in low efficiency, poor accuracy, and low reliability of failed object processing, leading to excessively long repair cycles for failed objects and affecting the overall stability of the database system.

[0038] Figure 1 The illustration schematically depicts application scenarios of the failure object handling method, apparatus, device, medium, and program product according to embodiments of this application. It should be noted that... Figure 1 The examples shown are merely examples of scenarios in which the embodiments of this application can be applied, to help those skilled in the art understand the technical content of this application, but do not mean that the embodiments of this application cannot be used in other devices, systems, environments or scenarios.

[0039] like Figure 1 As shown, application scenario 100 according to this embodiment may include an application scenario for handling failed objects. Network 104 is used as a medium to provide a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0040] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 via the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0041] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0042] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0043] It should be noted that the failure object handling method provided in this application embodiment can generally be executed by server 105. Correspondingly, the failure object handling device provided in this application embodiment can generally be located in server 105. The failure object handling method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the failure object handling device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0044] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0045] The following will be based on Figure 1 The described scene, through Figures 2-7 The method for handling failed objects according to the disclosed embodiments is described in detail. It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of this application, and the implementation methods of this application are not limited in any way. Rather, the implementation methods of this application can be applied to any applicable scenario.

[0046] Figure 2 A flowchart illustrating a method for handling failed objects according to an embodiment of this application is shown schematically.

[0047] like Figure 2 As shown, the method 200 includes steps S201 to S204.

[0048] Step S201: Obtain connection information for n databases, establish data connections with the n databases based on the connection information, and generate m target databases with completed data connections, where n is an integer and greater than 1, m is an integer and greater than 0, and m is less than or equal to n.

[0049] Figure 3 The flowchart illustrating the generation of m target databases with completed data connections in the failed object handling method according to an embodiment of this application is shown in the illustration.

[0050] like Figure 3 As shown, the method 300 includes steps S301 to S303.

[0051] Step S301: Based on the connection information of the n databases, establish a network connection with the n databases to generate n databases after the network connection is completed.

[0052] For example, in response to a failed object handling request, a database connection information submitted by n users through a network interface can be obtained. This database connection information includes direct connection information and indirect identifiers. Direct connection information typically includes IP address, port, username, and password, while indirect identifiers are generally management identifiers belonging to the same configuration group. The database network connection process generally establishes a network connection with the data based on the direct connection information, generating a database after the network connection is complete. In some databases, indirect identifiers may also be used to complete the network connection process.

[0053] Step S302: Send preset verification data to the n databases after the network connection is completed to confirm the availability and access permissions of the databases.

[0054] For example, the preset verification data is usually a predefined, lightweight SQL command used for verification, mainly to confirm the availability of the database service and account access permissions.

[0055] Step S303: Connect the m databases that return result data to generate m target databases with completed data connections, wherein the result data is the result data corresponding to the sent preset verification data.

[0056] For example, if the SQL command used for verification in the database executes successfully and returns the expected result corresponding to the SQL command, the verification is considered successful. The connection status of this database can be marked as a normal connection. This database is also identified as the target database for the completed data connection. If the SQL command used for verification in the database fails to execute, the verification is considered successful. Reasons for unsuccessful execution of the SQL command generally include network timeout, authentication errors, or insufficient permissions. In this case, the connection status of this database can be marked as disconnected, and this database can be identified as an abnormal database. For abnormal databases, the user can be prompted to re-check and resubmit the connection information for secondary verification.

[0057] By refining the data connection process to first establish a network connection, then perform permission and availability verification, and finally establish a data connection after verification, it is possible to filter valid databases, avoid process interruptions caused by database connection failures, improve the efficiency of handling failed objects, and ensure the reliability and stability of handling failed objects.

[0058] Return to reference Figure 2 In step S202, a first failure object detection is performed on the m target databases to determine a target failure objects in the m target databases, where a is an integer and a is greater than 1.

[0059] Figure 4 The flowchart illustrating the process of determining a target failed objects from m target databases in the failed object processing method according to an embodiment of this application is shown in the illustration.

[0060] like Figure 4 As shown, the method 400 includes steps S401 to S403.

[0061] Step S401: Determine the database type of each database in the m target databases. The database types include: distributed relational databases and centralized relational databases.

[0062] Step S402: Based on the database type of each database in the m target databases, perform a second failure object detection on the m target databases to determine b failure objects in the m target databases, where b is an integer and b is greater than a.

[0063] For example, a second failure object detection can be performed on m target databases at regular intervals. For instance, a preset second failure object detection scan time can be set for each database to be checked every hour on the hour. For databases that have reached the execution time, a second failure object detection scan task is generated and added to the thread pool queue.

[0064] Figure 5The flowchart illustrating the process of determining b failed objects from m target databases in a failed object processing method according to an embodiment of this application is shown.

[0065] like Figure 5 As shown, the method 500 includes steps S501 to S503.

[0066] Step S501: Determine i distributed relational databases among the m target databases, and perform a joint search on the i distributed relational databases to determine c invalid objects among the i distributed relational databases. The joint search includes: joint search on data packets, functions and stored procedures, where i is an integer, i is greater than 0 and i is less than m, and c is an integer, c is greater than 0 and c is less than b.

[0067] Step S502: Determine j centralized relational databases among the m target databases, and perform invalid status identification queries on the j centralized relational databases to determine d invalid objects among the j distributed relational databases, where j is an integer and j is greater than 0, the sum of i and j equals m, d is an integer and d is greater than 0, and the sum of d and c equals b.

[0068] Step S503: Merge the data of the c failed objects and the d failed objects to generate b failed objects in the m target databases.

[0069] By combining distributed relational databases for joint retrieval and centralized relational databases for invalid status identification, the technical means of identifying failed objects can effectively improve the accuracy of identifying failed objects in both distributed and centralized relational databases. Overall, this significantly improves the coverage and reliability of failed object detection in complex heterogeneous environments, enhances the efficiency of failed object detection, and avoids the waste of computer resources caused by misjudgments.

[0070] Step S403: Perform secondary compilation verification on b failed objects in the m target databases to determine a failed target objects in the m target databases.

[0071] Figure 6 The flowchart illustrating the secondary compilation verification in the failure object handling method according to an embodiment of this application is shown in the illustration.

[0072] like Figure 6 As shown, the method 600 includes steps S601 to S602.

[0073] Step S601: Perform secondary compilation on b failed objects in the m target databases to generate b failed objects in the m target databases after secondary compilation.

[0074] For example, each of the b failed objects in m target databases can be sequentially or concurrently traversed to obtain key information from its attributes. This key information typically includes: object owner, object name, and object type. The object type generally includes: stored procedure type, function type, package type, or trigger type, etc. The database type and syntax rules of each of the b failed objects are then obtained. Based on the key information, database type, and syntax rules of each of the b failed objects, the corresponding secondary compilation SQL command is dynamically assembled and generated. In the current connection session of the target database, the above secondary compilation SQL command is executed to generate the b failed objects in the m target databases after secondary compilation.

[0075] Step S602: Perform third failure object detection on b failed objects in the m target databases to determine a target failed objects in the m target databases.

[0076] For example, a third failure object detection is performed on b failed objects in a database of m targets to identify a failed target objects in the database. The detection steps for this third failure object detection are the same as those for the second failure object detection.

[0077] By using secondary compilation and third-party failure object detection, misjudgments caused by temporary failure objects due to lock conflicts can be effectively eliminated, significantly improving the accuracy and precision of identifying target failure objects.

[0078] By performing targeted and adaptive failure object detection on distributed and centralized relational databases, and then verifying it through secondary compilation, the accuracy and completeness of failure object detection can be effectively improved, avoiding false alarms and affecting user experience.

[0079] Return to reference Figure 2 In step S203, the target submission record of each target failure object among the a target failure objects is obtained, and the target submission interface corresponding to each target failure object among the a target failure objects is determined based on the target submission record of each target failure object among the a target failure objects.

[0080] Figure 7 The flowchart illustrating the process of obtaining the target submission record in the failed object handling method according to an embodiment of this application is shown in the illustration.

[0081] like Figure 7 As shown, the method 700 includes steps S701 to S703.

[0082] Step S701: Obtain the object name of each of the a target failed objects. Using the object name of each of the a target failed objects as a keyword, retrieve the e data submission records corresponding to each keyword, where e is an integer and e is greater than 0.

[0083] Step S702: Using a partition window function, partition the e data submission records corresponding to each keyword and sort them in reverse chronological order.

[0084] Step S703: Obtain the data submission record ranked first among the e data submission records corresponding to each keyword, and use it as the target submission record for each of the a target invalid objects.

[0085] By retrieving e data submission records corresponding to each of the a keywords, and sorting by partition to obtain the latest record, the system can locate the latest record without manual intervention by querying version history and time. It can accurately locate the target submission record in a massive number of submission records at a speed of milliseconds, effectively improving the efficiency of obtaining the target submission record and significantly enhancing the user experience.

[0086] Return to reference Figure 2 In step S204, the a target failure objects are sent based on the target submission interface corresponding to each of the a target failure objects.

[0087] For example, sending messages to the a target invalid objects may include: calling the office automation message interface, pushing structured content, and classifying and grading the exclusive content and batch list content for sending.

[0088] According to an embodiment of this application, the method further includes: obtaining repair objects and repair information for a target failed objects, and generating visual statistical data based on the repair objects and repair information for the a target failed objects.

[0089] For example, one can obtain the repair objects and repair information for 'a' target failed objects, specifically including: object name, database to which it belongs, detection time, reason for failure, repair status, and relevant personnel. Based on the repair objects and repair information for these 'a' target failed objects, visualized statistical data is generated. This visualized statistical data can be used for trend analysis and backlog management of failed objects. For example, trend analysis can be performed by generating a curve showing the recent changes in the number of failed objects for each application; backlog management can be performed by creating a list of failed objects arranged in order of consecutive days of failure.

[0090] By generating visual statistical data based on the repair objects and repair information of the a target failed objects, the specific status of the failed objects can be displayed intuitively, which is convenient for users to review and can improve the efficiency of subsequent failed object repair and enhance the stability of the overall database system.

[0091] Figure 8 A schematic block diagram of a failure object processing apparatus according to an embodiment of this application is shown.

[0092] like Figure 8 As shown, the device 800 includes: a first generation module 801, a first determination module 802, a second determination module 803, and a first transmission module 804.

[0093] The first generation module 801 is used to obtain connection information of n databases, establish data connections with the n databases based on the connection information, and generate m target databases with completed data connections, where n is an integer greater than 1, m is an integer greater than 0, and m is less than or equal to n. In one embodiment, the first generation module 801 can be used to execute step S201 described above.

[0094] The first generation module 801 includes: a second generation module, a second sending module, and a third generation module.

[0095] The second generation module is used to establish network connections with the n databases based on the connection information of the n databases, and generate n databases after the network connection is completed. In one embodiment, the second generation module can be used to execute step S301 described above, which will not be repeated here.

[0096] The second sending module is used to send preset verification data to the n databases after the network connection is completed, to confirm the availability and access permissions of the databases. In one embodiment, the second sending module can be used to execute step S302 described above, which will not be repeated here.

[0097] The third generation module is used to connect the m databases that return result data, and generate m target databases with completed data connections, wherein the result data is the result data corresponding to the sent preset verification data. In one embodiment, the third generation module can be used to execute step S303 described above, which will not be repeated here.

[0098] The first determining module 802 is used to perform a first failure object detection on the m target databases and determine a target failure objects in the m target databases, where a is an integer and a is greater than 1. In one embodiment, the first determining module 802 can be used to execute step S202 described above.

[0099] The first generation module 801 includes: a third determination module, a fourth determination module, and a fifth determination module.

[0100] The third determining module is used to determine the database type of each of the m target databases, wherein the database types include: distributed relational databases and centralized relational databases. In one embodiment, the third determining module can be used to execute step S401 described above, which will not be repeated here.

[0101] The fourth determining module is used to perform a second failure object detection on the m target databases based on the database type of each database in the m target databases, and to determine b failure objects in the m target databases, where b is an integer and b is greater than a. In one embodiment, the fourth determining module can be used to execute step S402 described above.

[0102] The fourth determining module includes: the sixth determining module, the seventh determining module, and the fourth generating module.

[0103] The sixth determining module is used to determine i distributed relational databases among the m target databases, and to perform a joint search on the i distributed relational databases to determine c invalid objects among the i distributed relational databases. The joint search includes a joint search of data packets, functions, and stored procedures, where i is an integer greater than 0 and less than m, and c is an integer greater than 0 and less than b. In one embodiment, the sixth determining module can be used to execute step S501 described above, which will not be repeated here.

[0104] The seventh determining module is used to determine j centralized relational databases among the m target databases, and to perform invalid status identification queries on the j centralized relational databases to determine d invalid objects among the j distributed relational databases, where j is an integer and greater than 0, the sum of i and j equals m, d is an integer and greater than 0, and the sum of d and c equals b. In one embodiment, the seventh determining module can be used to execute step S502 described above, which will not be repeated here.

[0105] The fourth generation module is used to merge the data of the c failed objects and the d failed objects to generate b failed objects in m target databases. In one embodiment, the fourth generation module can be used to execute step S503 described above, which will not be repeated here.

[0106] The fifth determining module is used to perform secondary compilation verification on b failed objects in the m target databases to determine a target failed objects in the m target databases. In one embodiment, the fifth determining module can be used to execute step S403 described above.

[0107] The fifth determining module includes: the fifth generating module and the eighth determining module.

[0108] The fifth generation module is used to perform secondary compilation on the b failed objects in the m target databases to generate b failed objects in the m target databases after secondary compilation. In one embodiment, the fifth generation module can be used to execute step S601 described above, which will not be repeated here.

[0109] The eighth determining module is used to perform a third failure object detection on b failed objects in the m target databases to determine a target failed objects in the m target databases. In one embodiment, the eighth determining module can be used to execute step S602 described above, which will not be repeated here.

[0110] The second determining module 803 is used to obtain the target submission record of each of the a target failed objects, and based on the target submission record of each of the a target failed objects, determine the target submission interface corresponding to each of the a target failed objects. In one embodiment, the second determining module 803 can be used to execute step S203 described above.

[0111] The second determining module 803 includes: a first obtaining module, a first sorting module, and a sixth generating module.

[0112] The first acquisition module is used to acquire the object name of each of the a target failed objects, and to retrieve e data submission records corresponding to each keyword, using the object name of each of the a target failed objects as a keyword, where e is an integer and e is greater than 0. In one embodiment, the first acquisition module can be used to execute step S701 described above, which will not be repeated here.

[0113] The first sorting module is used to partition the e data submission records corresponding to each keyword using a partitioning window function and sort them in reverse chronological order. In one embodiment, the first sorting module can be used to execute step S702 described above, which will not be repeated here.

[0114] The sixth generation module is used to obtain the top-ranked data submission record among the e data submission records corresponding to each keyword, and use it as the target submission record for each of the a target invalid objects. In one embodiment, the sixth generation module can be used to execute step S703 described above, which will not be repeated here.

[0115] The first sending module 804 is used to send the a target failed objects based on the target submission interface corresponding to each of the a target failed objects. In one embodiment, the first sending module 804 can be used to execute step S204 described above, which will not be repeated here.

[0116] According to an embodiment of this application, the device further includes: a sixth generation module, used to obtain repair objects and repair information of a target failed objects, and generate visual statistical data based on the repair objects and repair information of the a target failed objects.

[0117] According to embodiments of this application, any plurality of modules among the first generation module 801, the first determination module 802, the second determination module 803, and the first transmission module 804 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the first generation module 801, the first determination module 802, the second determination module 803, and the first transmission module 804 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these. Alternatively, at least one of the first generation module 801, the first determination module 802, the second determination module 803, and the first sending module 804 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0118] Figure 9 A block diagram schematically illustrates an electronic device suitable for implementing a failed object handling method according to an embodiment of this application.

[0119] like Figure 9As shown, an electronic device 900 according to an embodiment of this application includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0120] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0121] According to embodiments of this application, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output (I / O) interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0122] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0123] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0124] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the failure object handling method provided in the embodiments of this application.

[0125] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0126] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0127] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0128] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0129] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0130] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for handling failed objects, characterized in that, The method includes: Obtain connection information for n databases, establish data connections with the n databases based on the connection information, and generate m target databases with completed data connections, where n is an integer and greater than 1, m is an integer and greater than 0, and m is less than or equal to n; Perform a first failure object detection on the m target databases to determine a target failure objects in the m target databases, where a is an integer and a is greater than 1; Obtain the target commit record for each of the a target failed objects; based on the target commit record for each of the a target failed objects, determine the target commit interface corresponding to each of the a target failed objects; and Based on the target submission interface corresponding to each of the a target failure objects, the a target failure objects are sent.

2. The method according to claim 1, characterized in that, Based on the connection information of the n databases, data connections are established with the n databases to generate m target databases with completed data connections, including: Based on the connection information of the n databases, establish a network connection with the n databases to generate n databases after the network connection is completed; Send preset verification data to n databases after the network connection is established to confirm the availability and access permissions of the databases; and Data connections are made to m databases that return result data to generate m target databases with completed data connections, wherein the result data is the result data corresponding to the sent preset verification data.

3. The method according to claim 1, characterized in that, A first failure object detection is performed on the m target databases to determine a target failure objects in the m target databases, including: Determine the database type of each of the m target databases, where the database types include: distributed relational databases and centralized relational databases; Based on the database type of each of the m target databases, a second failure object detection is performed on the m target databases to determine b failure objects in the m target databases, where b is an integer and b is greater than a; and A second compilation verification is performed on b failed objects in the m target databases to determine a failed target objects in the m target databases.

4. The method according to claim 3, characterized in that, Based on the database type of each of the m target databases, a second failure object detection is performed on the m target databases to determine b failure objects in the m target databases, including: Identify i distributed relational databases from the m target databases, and perform a joint search on the i distributed relational databases to identify c invalid objects in the i distributed relational databases. The joint search includes: joint search on data packets, functions, and stored procedures, where i is an integer, i is greater than 0 and i is less than m, and c is an integer, c is greater than 0 and c is less than b. Identify j centralized relational databases among the m target databases, and perform invalid status identification queries on the j centralized relational databases to identify d invalid objects in the j distributed relational databases, where j is an integer greater than 0, the sum of i and j equals m, d is an integer greater than 0, and the sum of d and c equals b; and The c failed objects and the d failed objects are merged to generate b failed objects in m target databases.

5. The method according to claim 3, characterized in that, A secondary compilation verification is performed on b failed objects in the m target databases to determine a failed target objects in the m target databases, including: The b failed objects in the m target databases are recompiled to generate b failed objects in the m target databases after secondary compilation; and A third failure object detection is performed on b failed objects in the m target databases to determine a target failed objects in the m target databases.

6. The method according to claim 1, characterized in that, Retrieve the target submission record for each of the a target failure objects, including: Obtain the object name of each of the a target failed objects. Using the object name of each of the a target failed objects as a keyword, retrieve the e data submission records corresponding to each keyword, where e is an integer and e is greater than 0. The partitioning window function is used to partition the e data submission records corresponding to each keyword and sort them in reverse chronological order; and Obtain the data submission record ranked first among the e data submission records corresponding to each keyword, and use it as the target submission record for each of the a target failure objects.

7. The method according to any one of claims 1 to 6, further comprising: Obtain the repair objects and repair information for a target failed objects, and generate visual statistical data based on the repair objects and repair information for the a target failed objects.

8. A device for handling failed objects, characterized in that, The device includes: The first generation module is used to obtain connection information of n databases, establish data connections with the n databases based on the connection information of the n databases, and generate m target databases with completed data connections, where n is an integer and n is greater than 1, m is an integer and m is greater than 0, and m is less than or equal to n. The first determining module is used to perform a first failure object detection on the m target databases and determine a target failure objects in the m target databases, where a is an integer and a is greater than 1; The second determining module is used to obtain the target submission record of each of the a target failed objects, and based on the target submission record of each of the a target failed objects, determine the corresponding target submission interface of each of the a target failed objects; and The first sending module is used to send the a target failure objects based on the target submission interface corresponding to each of the a target failure objects.

9. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images