Three-party database diagnosis method and device, electronic equipment and storage medium

Through configuration, transmission and integrity diagnosis, data transmission problems between the platform and the tripartite database are solved, ensuring the integrity and stability of data transmission and saving human resources.

CN119127560AInactive Publication Date: 2024-12-13HANGZHOU HIKVISION DIGITAL TECHNOLOGY CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411620562.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-13
Publication Date
2024-12-13
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In the prior art, when the platform transmits user data to a three-party database, it is difficult to count whether the connection and data transmission are normal, resulting in difficulty in ensuring the integrity and stability of user data transmission and waste of human resources.

Method used

Provide a diagnosis method for a tripartite database, including configuration diagnosis, transmission diagnosis and integrity diagnosis, through these diagnosis, the communication connection between the platform and the tripartite database and the data transmission status are determined to ensure the integrity and stability of data transmission.

Benefits of technology

Through diagnostic methods, data transmission problems can be automatically detected and solved, human resources can be saved, and the reliability and efficiency of data transmission can be improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119127560A_ABST
    Figure CN119127560A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a diagnosis method and device of a three-party database, electronic equipment and a storage medium, and relates to the technical field of data transmission. The method is applied to a platform for sending user data to a three-party database, and comprises the following steps: in response to a diagnosis instruction, performing configuration class diagnosis on a target three-party database indicated by the diagnosis instruction; under the condition that the diagnosis result of the configuration class diagnosis meets the first dependency relationship, transmission class diagnosis is carried out on the target three-party database; and under the condition that the diagnosis result of the transmission type diagnosis meets the second dependency relationship, performing integrity diagnosis on the user data transmitted by the platform and the target three-party database to obtain a diagnosis result of the target three-party database. Therefore, the platform diagnoses the target three-party database based on the dependency relationship among the three types of diagnoses, and determines whether the communication connection and data transmission between the platform and the target three-party database are normal, thereby ensuring the integrity and stability of user data transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of data transmission, and in particular to a diagnostic method, device, electronic device and storage medium for a three-party database. Background Art

[0002] With the rapid development of Internet technology, the production activities involving platform users generate a large amount of user data. In some cases, platform users need to send the generated user data to a third-party database for storage and management.

[0003] Currently, the platform supports the transmission of user data to a third-party database to facilitate users to receive user data for the processing required by the user. The platform saves the name, database table name, field name, etc. of the third-party database specified by the user, and then connects to the third-party database specified by the user, and when user data needs to be sent to the third-party database, it transmits user data to the third-party database based on the established connection. Taking the attendance system as an example, the manufacturer of the attendance platform and the attendance equipment may not be the same. When the third-party database wants to get the data of the attendance equipment, in addition to the need to adapt the protocol, it also needs to ensure the smoothness of the data transmission channel. However, in the actual operation process, it was found that the data transmission channel between the third-party database and the attendance platform often has problems, but the specific causes of the problems need to rely on experienced managers to check one by one, which leads to high requirements for managers and requires a lot of human resources.

[0004] It can be seen that, at present, in the process of transmitting user data from the platform to the third-party database, it is difficult to count whether the connection and data transmission between the two are normal, and it is impossible to guarantee the integrity and stability of user data transmission, and it wastes human resources. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a diagnostic method, device, electronic device and storage medium for a third-party database, so as to solve the problem that it is difficult to count whether the communication connection and data transmission between the platform and the third-party database are normal, and waste human resources. The specific technical solution is as follows:

[0006] In a first aspect, an embodiment of the present application provides a method for diagnosing a third-party database, which is applied to a platform, wherein the platform is used to send user data to the third-party database, and the method includes:

[0007] In response to the diagnostic instruction, performing configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database;

[0008] In the case where the diagnosis result of the configuration diagnosis satisfies the first dependency relationship, performing a transmission diagnosis on the target third-party database, wherein the first dependency relationship is a preset dependency relationship between the transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database;

[0009] When the diagnostic result of the transmission type diagnosis satisfies the second dependency relationship, an integrity diagnosis is performed on the user data transmitted between the platform and the target third-party database to obtain the diagnostic result of the target third-party database, wherein the second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission type diagnosis and the configuration type diagnosis.

[0010] Optionally, the first dependency relationship is that the preset transmission-type diagnosis depends on the configuration-type diagnosis;

[0011] The step of performing transmission diagnosis on the target third-party database when the diagnosis result of the configuration diagnosis satisfies the first dependency relationship includes:

[0012] When the diagnostic result of the configuration-type diagnosis indicates that the platform has been configured with the data source corresponding to the target third-party database, the data transmission status between the platform and the target third-party database corresponding to the configured data source is determined based on the communication connection between the platform and the target third-party database to obtain the diagnostic result of the transmission-type diagnosis.

[0013] Optionally, the step of determining the data transmission status between the platform and the target third-party database corresponding to the configured data source based on the communication connection between the platform and the target third-party database, and obtaining the diagnosis result of the transmission diagnosis includes:

[0014] Determine whether the communication connection between the platform and the target third-party database is normal, and determine whether there is user data that fails to be transmitted among the user data sent by the platform to the target third-party database corresponding to the configured data source;

[0015] In a case where the communication connection is normal and there is no user data that fails to be transmitted, determining that the diagnosis result of the transmission type diagnosis is normal transmission;

[0016] In a case where the communication connection is normal and there is user data that fails to be transmitted, determining that the diagnosis result of the transmission type diagnosis is a transmission failure;

[0017] In the case where the communication connection is abnormal, it is determined that the diagnosis result of the transmission type diagnosis is a connection failure.

[0018] Optionally, the second dependency relationship is that the preset integrity diagnosis depends on the transmission diagnosis and the configuration diagnosis;

[0019] The step of performing integrity diagnosis on the user data transmitted between the platform and the target third-party database when the diagnosis result of the transmission-related diagnosis satisfies the second dependency relationship includes:

[0020] When the diagnosis result of the transmission type diagnosis indicates that the data transmission status between the platform and the target third-party database is normal, the integrity of the user data transmitted between the platform and the target third-party database is diagnosed to ensure the integrity of the user data transmitted between the platform and the target third-party database.

[0021] Optionally, the step of diagnosing the integrity of the user data transmitted between the platform and the target third-party database includes at least one of the following:

[0022] In response to the test data transmission instruction, based on the acquired database information of the target third-party database, the test data is sent to the target third-party database, and whether the database information of the target third-party database is correct is determined according to the transmission result. If the database information of the target third-party database is correct, the database information of the target third-party database is saved, wherein the database information includes a database table name and a field name;

[0023] In response to the transmission failure cause diagnosis instruction, based on the preset error code analysis file, the error code sent by the target third-party database is parsed to obtain the user data transmission failure cause, and the error code and the corresponding user data transmission failure cause are saved, wherein the error code is sent by the target third-party database to the platform when the platform fails to transmit user data to the target third-party database;

[0024] In response to the breakpoint resume instruction, the saved user data that failed to be transmitted is transmitted to the target third-party database according to the preset time point included in the breakpoint resume instruction;

[0025] In response to the data synchronization instruction, the user data to be synchronized within the time range indicated by the data synchronization instruction is obtained from the data source corresponding to the configured target third-party database, and the user data to be synchronized is transmitted to the target third-party database.

[0026] Optionally, after the step of saving the error code and the corresponding reason for the failure of user data transmission, the method further includes:

[0027] In response to a query instruction issued by a user, based on a target error code corresponding to the user data whose transmission fails as indicated by the query instruction, searching for a user data transmission failure cause corresponding to the target error code from the saved error codes and the corresponding user data transmission failure causes;

[0028] The found reasons for the failure in transmitting the user data are displayed, so that the user can view the reasons for the failure in transmitting the user data corresponding to the failed transmission.

[0029] Optionally, before the step of performing configuration diagnosis on the target third-party database indicated by the diagnostic instruction in response to the diagnostic instruction, the method further includes:

[0030] Acquire configuration information and database type of a third-party database, wherein the third-party database includes the target third-party database;

[0031] For each third-party database, create a corresponding database instance according to the configuration information and database type of the third-party database;

[0032] The database driver corresponding to the database type is called through the database instance, and a communication connection is established with the third-party database using the database driver.

[0033] Optionally, the method further includes:

[0034] In the case where the diagnosis result of the configuration diagnosis indicates that the platform is not configured with the data source corresponding to the target third-party database, the diagnosis result of the configuration diagnosis and the first prompt information are returned, and the transmission diagnosis and the integrity diagnosis are not performed, wherein the first prompt information is used to prompt the user that the platform is not configured with the data source corresponding to the target third-party database;

[0035] In the case where the diagnosis result of the transmission diagnosis is a transmission failure or a connection failure, the diagnosis result of the transmission diagnosis and the second prompt information are returned, and the integrity diagnosis is not performed, wherein the second prompt information is used to prompt the user to determine that the diagnosis result of the transmission diagnosis is the cause of the transmission failure or the connection failure;

[0036] When the diagnosis result of the integrity diagnosis is that the user data transmitted between the platform and the target third-party database is incomplete, the diagnosis result of the integrity diagnosis and a third prompt message are returned, wherein the third prompt message is used to prompt that the user data transmitted between the platform and the target third-party database is incomplete.

[0037] Optionally, the first prompt information includes: an entry path to a configuration page for configuring a data source corresponding to a target third-party database for the platform or a configuration window for configuring a data source corresponding to a target third-party database for the platform; and / or,

[0038] The second prompt information includes at least one of: suggesting that the user confirm with the device manufacturer of the target third-party database whether the server to which the target third-party database belongs is working normally, and prompting the user to store the user data that failed to be transmitted in the platform; and / or,

[0039] The third prompt information includes: prompting the user to send the test data to the target third-party database, prompting the user to check the reason for the transmission failure, prompting the administrator to set a preset time point included in the breakpoint resume instruction so that the platform can transfer the saved user data that failed to be transmitted to the target third-party database at the preset time point, and prompting the user to start the data synchronization instruction so that the platform can synchronize the user data to be synchronized in the data source corresponding to the target third-party database.

[0040] In a second aspect, an embodiment of the present application provides a diagnostic device for a third-party database, which is applied to a platform, and the platform is used to send user data to the third-party database, and the device includes:

[0041] A configuration diagnosis module, configured to perform configuration diagnosis on a target third-party database indicated by the diagnosis instruction in response to the diagnosis instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database;

[0042] A transmission diagnosis module, configured to perform transmission diagnosis on the target third-party database if the diagnosis result of the configuration diagnosis satisfies a first dependency relationship, wherein the first dependency relationship is a preset dependency relationship between the transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database;

[0043] An integrity diagnosis module is used to perform integrity diagnosis on the user data transmitted between the platform and the target third-party database to obtain the diagnosis result of the target third-party database when the diagnosis result of the transmission type diagnosis satisfies the second dependency relationship, wherein the second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission type diagnosis and the configuration type diagnosis.

[0044] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0045] Memory, used to store computer programs;

[0046] The processor is used to implement any method described in the first aspect when executing a program stored in the memory.

[0047] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any method described in the first aspect is implemented.

[0048] Beneficial effects of the embodiments of the present application:

[0049] In the scheme provided by the embodiment of the present application, the platform can respond to the diagnostic instruction and perform configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with the data source corresponding to the target third-party database, and then, if the diagnostic result of the configuration diagnosis satisfies the first dependency, the target third-party database is subjected to transmission diagnosis, wherein the first dependency is the dependency between the preset transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database, and then, if the diagnostic result of the transmission diagnosis satisfies the second dependency, the user data transmitted by the platform and the target third-party database is subjected to integrity diagnosis to obtain the diagnostic result of the target third-party database, wherein the second dependency is the dependency between the preset integrity diagnosis and the transmission diagnosis and the configuration diagnosis. In this way, the platform diagnoses the target third-party database based on the dependency between the configuration diagnosis, the transmission diagnosis and the integrity diagnosis, and determines whether the communication connection and data transmission between the platform and the target third-party database are normal, thereby ensuring the integrity and stability of the user data transmission. Moreover, the diagnostic result can guide the direction of troubleshooting, without the need for manual aimless troubleshooting, saving human resources. Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0051] Figure 1 A flowchart of a diagnostic method for a third-party database provided in an embodiment of the present application;

[0052] Figure 2 Based on Figure 1 A schematic diagram of the dependency relationship between configuration diagnosis, transmission diagnosis, and integrity diagnosis in the illustrated embodiment;

[0053] Figure 3 Based on Figure 1 A flow chart of step S102 in the illustrated embodiment;

[0054] Figure 4 Based on Figure 1 A flow chart of establishing a communication connection between the platform and a third-party database in the embodiment shown;

[0055] Figure 5 Based on Figure 1 A schematic diagram of the diagnostic tool of the illustrated embodiment diagnosing a three-party database;

[0056] Figure 6 Based on Figure 1 A schematic diagram of a user data transmission process of the illustrated embodiment;

[0057] Figure 7 Based on Figure 1 A schematic diagram of diagnosing a target third-party database in the embodiment shown;

[0058] Figure 8 A schematic diagram of the structure of a diagnostic device for a three-party database provided in an embodiment of the present application;

[0059] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0061] In order to determine whether the communication connection and data transmission between the platform and the third-party database are normal and to ensure the integrity and stability of user data transmission, the present application embodiment provides a third-party database diagnosis method, device, electronic device, computer-readable storage medium and computer program product. The following first introduces a third-party database diagnosis method provided by the present application embodiment.

[0062] The diagnostic method for a third-party database provided in an embodiment of the present application can be applied to any platform that needs to diagnose a third-party database, for example, it can be an attendance platform, an access control card swiping software platform, a security gate service platform, etc., without specific limitation here. For the sake of clear description, it is referred to as a platform in the following.

[0063] like Figure 1As shown, a diagnostic method for a third-party database is applied to a platform, and the platform is used to send user data to the third-party database. The method includes:

[0064] S101, in response to a diagnostic instruction, performing configuration diagnosis on a target third-party database indicated by the diagnostic instruction;

[0065] The configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database.

[0066] S102, when the diagnosis result of the configuration diagnosis satisfies the first dependency relationship, performing transmission diagnosis on the target third-party database;

[0067] The first dependency relationship is a preset dependency relationship between the transmission-type diagnosis and the configuration-type diagnosis, and the transmission-type diagnosis is used to determine the data transmission status between the platform and the target third-party database.

[0068] S103, when the diagnosis result of the transmission diagnosis satisfies the second dependency relationship, performing integrity diagnosis on the user data transmitted between the platform and the target third-party database to obtain the diagnosis result of the target third-party database;

[0069] The second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission diagnosis and the configuration diagnosis.

[0070] It can be seen that in the scheme provided by the embodiment of the present application, the platform can respond to the diagnostic instruction and perform configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with the data source corresponding to the target third-party database, and then, if the diagnostic result of the configuration diagnosis satisfies the first dependency, the target third-party database is subjected to transmission diagnosis, wherein the first dependency is the dependency between the preset transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database, and then, if the diagnostic result of the transmission diagnosis satisfies the second dependency, the user data transmitted by the platform and the target third-party database is subjected to integrity diagnosis to obtain the diagnostic result of the target third-party database, wherein the second dependency is the dependency between the preset integrity diagnosis and the transmission diagnosis and the configuration diagnosis. In this way, the platform diagnoses the target third-party database based on the dependency between the configuration diagnosis, the transmission diagnosis and the integrity diagnosis, and determines whether the communication connection and data transmission between the platform and the target third-party database are normal, thereby ensuring the integrity and stability of the user data transmission. Moreover, the diagnostic result can guide the direction of troubleshooting, without the need for manual aimless troubleshooting, saving human resources.

[0071] A large amount of user data will be generated in the production activities involved by platform users. In some cases, the user data generated by platform users needs to be sent to a designated third-party database for storage and management. In order to ensure the integrity and stability of user data transmission, the platform can diagnose whether the communication connection and data transmission between the platform and the database designated by the user, i.e., the target third-party database, are normal.

[0072] For example, an enterprise uses an attendance platform to determine the working hours of employees. It uses the attendance platform and the supporting attendance equipment, but does not need to use the rules of the attendance platform to manage the attendance data. Therefore, users who use the attendance platform can transfer the attendance data in the attendance platform to the target third-party database specified by the enterprise, and the target third-party database stores and manages the attendance data. Alternatively, users use the attendance platform and existing third-party attendance equipment to perform attendance statistics. The data of each third-party attendance device is stored locally in the attendance device. The attendance platform establishes a data transmission channel with the third-party attendance equipment, thereby pulling the attendance data of the third-party attendance equipment into the attendance platform, and then sending it to the target third-party database specified by the user to analyze these attendance data.

[0073] However, the attendance platform and the target third-party database may lose communication due to power failure of the server where the target third-party database is located, the attendance platform is updated, etc., making it impossible to transmit the attendance data to the target third-party database. For users, when the attendance platform is disconnected from the target third-party database, users will only look for the administrator of the platform and will not think that it is a problem with the target third-party database. However, problems such as power failure of the target third-party database or failure of the server where the target third-party database is located are unknown to the administrator of the platform. Only experienced administrators can roughly infer them. Inexperienced administrators may further investigate other reasons, resulting in a waste of manpower.

[0074] Therefore, in order to ensure the integrity and stability of attendance data transmission, the attendance platform can diagnose whether the communication connection and data transmission between it and the target third-party database are normal, saving human resources.

[0075] If the diagnosis result of the configuration diagnosis is wrong, that is, the diagnosis result indicates that the attendance platform is not configured with the data source corresponding to the target third-party database, then the prompt can be: It is recommended that the user check whether the attendance platform is configured with the data source platform corresponding to the target third-party database; if the diagnosis result of the transmission diagnosis is wrong, that is, the diagnosis result is transmission failure or connection failure, the attendance platform can prompt: It is recommended that the user confirm with the equipment manufacturer of the target third-party database whether the server is working normally, etc.; if the diagnosis result of the integrity diagnosis is wrong, that is, the user data transmitted between the platform and the target third-party database is incomplete, the attendance platform can prompt: It is recommended that the user send test data to the target third-party database, or prompt the user to start the data synchronization instruction so that the attendance data of the data source can be synchronized to the target third-party database.

[0076] In this way, by returning prompt information when the diagnostic results are wrong, the diagnostic results can guide users and managers in the direction of troubleshooting the problem, so that users and managers can basically understand the reasons that caused the attendance platform to be disconnected from the target third-party database, without the need for manual aimless troubleshooting, saving human resources.

[0077] Specifically, three types of diagnosis are used to diagnose the target third-party database, where the three types of diagnosis are configuration diagnosis, transmission diagnosis and integrity diagnosis, and there is a dependency relationship between the three types of diagnosis. Figure 2 As shown, configuration diagnosis 201 is the basis of the three types of diagnosis; there is a first dependency relationship between transmission diagnosis 202 and configuration diagnosis 201. Only when the diagnosis result of configuration diagnosis 201 satisfies the first dependency relationship, that is, there is no abnormality in the diagnosis result of configuration diagnosis 201, can the platform perform transmission diagnosis 202 on the target third-party database.

[0078] There is a second dependency relationship between integrity diagnosis 203 and configuration diagnosis 201 and transmission diagnosis 202. Only when the diagnostic results of configuration diagnosis 201 and transmission diagnosis 202 meet the second dependency relationship, that is, when there are no abnormalities in the diagnostic results of configuration diagnosis 201 and transmission diagnosis 202, can the platform perform integrity diagnosis 203 on the target third-party database. If any of the diagnostic results of configuration diagnosis 201 and transmission diagnosis 202 is abnormal, the platform will not perform integrity diagnosis 203 on the target third-party database.

[0079] In order to ensure that user data can be accurately sent from the platform to the third-party database, in the above step S101, the platform responds to the diagnostic instruction and performs configuration diagnosis on the target third-party database indicated by the diagnostic instruction. The diagnostic instruction can be issued by the administrator of the platform when the third-party database needs to be diagnosed, or by the user of the platform. Of course, it can also be issued by the platform after reaching a preset diagnostic cycle. This is all reasonable and is not specifically limited here.

[0080] Since the data source configured on the platform stores information about the communication connection relationship established between the platform and the target third-party database indicated by the user, whether the platform is configured with a data source corresponding to the target third-party database is an important factor in whether the user data obtained by the platform can be transmitted to the target third-party database. Therefore, after the platform responds to the diagnostic instruction, it first performs a configuration diagnosis on the target third-party database indicated by the diagnostic instruction to determine whether the platform is configured with a data source corresponding to the third-party database. Among them, the platform can establish a communication connection relationship with only one third-party database, or it can establish a communication connection relationship with multiple different or the same third-party databases, which is reasonable and is not specifically limited here.

[0081] Only when the platform is configured with an event source corresponding to the target third-party database that stores user data, can the user data obtained by the platform be transmitted to the target third-party database. When the platform is an attendance platform, the user data can be attendance data, such as employee attendance time, employee working hours, etc.; when the platform is an access control card swiping software platform, the user data can be access rights, card swiping time, etc.; when the platform is a security gate service platform, the user data can be security check location, security check time, etc., without specific limitation here.

[0082] As an implementation method, the diagnostic instruction includes information of the specified target third-party database, such as the identifier of the specified target third-party database or the name of the specified target third-party database, so after the platform responds to the diagnostic instruction, it can perform configuration diagnosis on the target third-party database specified by the diagnostic instruction. For the target third-party database specified by the diagnostic instruction, it is determined whether a data source corresponding to the target third-party database is configured on the platform.

[0083] As an implementation method, the diagnostic instruction does not include information about the specified target third-party database, such as the identifier of the specified target third-party database or the name of the specified target third-party database, so after the platform responds to the diagnostic instruction, configuration diagnosis can be performed on all target third-party databases that have established communication connections with the platform. For each target third-party database, determine whether a data source corresponding to the target third-party database is configured on the platform.

[0084] After the platform performs configuration diagnosis on the target third-party database indicated by the diagnostic instruction and obtains the diagnosis result of the configuration diagnosis, in order to determine the data transmission status between the platform and the target third-party database, if the diagnosis result of the configuration diagnosis satisfies the first dependency relationship, then, in the above step S102, the platform can perform transmission diagnosis on the target third-party database, and determine the data transmission status between the platform and the target third-party database through transmission diagnosis. Among them, the first dependency relationship is the dependency relationship between the preset transmission diagnosis and the configuration diagnosis.

[0085] After completing the configuration of the target third-party database, the communication connection between the platform and the target third-party database may be disconnected due to power failure or downtime of the server where the target third-party database is located, or the platform needs to be updated. When the platform transmits user data to the target third-party database, the user data cannot be successfully stored in the target third-party database due to reasons such as the length of the user data is too long or the data type of the user data is incorrect. Therefore, it is necessary to diagnose the data transmission status between the platform and the target third-party database.

[0086] As an implementation method, if the diagnostic result of the configuration-type diagnosis indicates that the data source corresponding to the target third-party database is configured on the platform, that is, there is no abnormality in the diagnostic result of the configuration-type diagnosis, then the platform can directly perform a transmission-type diagnosis on the target third-party database to determine the data transmission status between the platform and the target third-party database.

[0087] If the diagnostic result of the configuration diagnosis shows that the data source corresponding to the target third-party database is not configured on the platform, that is, the diagnostic result of the configuration diagnosis is abnormal, for example, no data source is configured on the platform or the data source configured on the platform does not correspond to the target third-party database, the configuration diagnosis result can be displayed. After the administrator or user updates the data source configured on the platform and the diagnostic result of the configuration diagnosis shows that the data source corresponding to the target third-party database is configured on the platform, the platform can perform transmission diagnosis on the target third-party database.

[0088] If the above diagnostic instruction includes information about a specified target third-party database, after the platform responds to the diagnostic instruction, it performs configuration diagnosis on the target third-party database specified by the diagnostic instruction. If the diagnostic result of the configuration diagnosis satisfies the first dependency relationship, when the platform performs transmission diagnosis on the target third-party database, the platform also only determines the data transmission status between it and the specified target third-party database. Even if the platform has established a communication connection with a target third-party database other than the above specified target third-party database, due to the first dependency relationship between configuration diagnosis and transmission diagnosis, the platform will not perform transmission diagnosis on target third-party databases other than the specified target third-party database.

[0089] If the above diagnostic instruction does not include the information of the specified target third-party database, after the platform responds to the diagnostic instruction, configuration-type diagnosis is performed on all target third-party databases that have established communication connections with the platform. Then, if the diagnostic results of the configuration-type diagnosis satisfy the first dependency relationship, the data transmission status between the platform and the target third-party database is determined for each target third-party database.

[0090] After obtaining the diagnosis result of the transmission diagnosis, in order to determine the integrity of the user data transmitted between the platform and the target third-party database, if the diagnosis result of the transmission diagnosis satisfies the second dependency relationship, then in the above step S103, the platform can perform integrity diagnosis on the user data transmitted between it and the target third-party database. The second dependency relationship is the dependency relationship between the preset integrity diagnosis and the transmission diagnosis and the configuration diagnosis.

[0091] As an implementation method, if the diagnostic results of the configuration diagnosis indicate that the data source corresponding to the target third-party database is configured on the platform, and the diagnostic results of the transmission diagnosis indicate that the data transmission status between the three-party databases is normal, that is, there are no abnormalities in the diagnostic results of the configuration diagnosis and the transmission diagnosis, then the platform can directly perform an integrity diagnosis on the user data transmitted between the platform and the target third-party database to determine whether the user data stored in the target third-party database is complete.

[0092] If at least one of the diagnostic results of configuration diagnosis or transmission diagnosis contains an abnormality, the platform will not perform the above integrity diagnosis and will display the diagnostic results with the abnormality. Only when the administrator or user handles the abnormality and the diagnostic results after processing do not contain any abnormality, can the platform perform integrity diagnosis on the target third-party database.

[0093] It can be seen that in the embodiment of the present application, the platform diagnoses the target third-party database based on the dependency relationship between configuration diagnosis, transmission diagnosis and integrity diagnosis to determine whether the communication connection and data transmission between the platform and the target third-party database are normal, thereby ensuring the integrity and stability of user data transmission.

[0094] As an implementation of an embodiment of the present application, the first dependency relationship may be that a preset transmission diagnosis depends on the configuration diagnosis; when the diagnosis result of the configuration diagnosis satisfies the first dependency relationship, the step of performing transmission diagnosis on the target third-party database may include:

[0095] When the diagnostic result of the configuration-type diagnosis indicates that the platform has been configured with a data source corresponding to the target third-party database, the data transmission status between the platform and the target third-party database corresponding to the configured data source is determined based on the communication connection between the platform and the target third-party database to obtain the diagnostic result of the transmission-type diagnosis.

[0096] Since the data source stores information about the communication connection between the platform and the target third-party database, whether the platform is configured with a data source corresponding to the target third-party database is the basis for whether the user data obtained by the platform can be transmitted to the target third-party database. If the platform is not configured with a data source, or the data source configured in the platform does not correspond to the target third-party database, it is difficult for the platform to determine which third-party database to transmit the user data to.

[0097] Only when the diagnostic result of the configuration-type diagnosis indicates that the platform has configured a data source and the data source is the corresponding target third-party database, will the platform determine the data transmission status between the platform and the target third-party database corresponding to the configured data source based on the communication connection between the platform and the target third-party database, and obtain the diagnostic result of the transmission-type diagnosis.

[0098] If the above data transmission status is in a normal state, then the diagnostic result of the transmission type diagnosis is that there is no abnormality; if the above data transmission status is in an abnormal state, then the diagnostic result of the transmission type diagnosis is that there is an abnormality. The platform can display the diagnostic result to facilitate managers and users to deal with the abnormal status.

[0099] Among them, the above-mentioned transmission diagnosis can determine whether the communication connection between the platform and the corresponding target third-party database is normal; it can also determine whether there is user data that fails to be transmitted when the platform transmits user data to the target third-party database; it can also determine the transmission duration when the platform transmits user data to the target third-party database. These are all reasonable and are not specifically limited here.

[0100] It can be seen that in the embodiment of the present application, when the diagnosis result of the configuration class is that the platform is configured with a data source corresponding to the target third-party database, the platform determines the data transmission status between the two based on the communication connection between the platform and the target third-party database. In this way, by determining the above data transmission status, the platform can timely understand whether there are any abnormalities in the process of user data transmission, and can display them to managers and users when there are abnormalities, so that managers and users can handle the abnormalities, thereby ensuring the stability and accuracy of user data transmission.

[0101] As an implementation method of the present application, Figure 3As shown, the above step of determining the data transmission status between the platform and the target third-party database corresponding to the configured data source based on the communication connection between the platform and the target third-party database, and obtaining the diagnosis result of the transmission diagnosis may include:

[0102] S301, determining whether the communication connection between the platform and the target third-party database is normal, and determining whether there is any user data that fails to be transmitted among the user data sent by the platform to the target third-party database corresponding to the configured data source.

[0103] After determining that the platform is configured with a data source corresponding to the target third-party database, the platform determines the communication connection between the platform and the target third-party database through transmission diagnosis, and whether there is user data that fails to be transmitted during the process of the platform transmitting user data to the target third-party database, and obtains the data transmission status between the platform and the target third-party database. In addition, according to different data transmission states, alarm information for different data transmission states can be set, and an alarm can be triggered to the platform. When the user sees the alarm information, he can go to the page of the target third-party database to make changes in time.

[0104] In one implementation, the platform can simultaneously determine the communication connection status and whether there is user data that fails to be transmitted during the data transmission process, and thus obtain a diagnosis result of the transmission type diagnosis.

[0105] In one implementation, the platform may first determine whether there is user data that fails to be transmitted during the data transmission process, and determine whether it is necessary to determine the communication connection status based on the first result obtained. Since the platform can only transmit the user data to the target third-party database when the communication connection between the platform and the target third-party database is normal. Therefore, when the first result is that there is no user data that fails to be transmitted in the user data sent by the platform, it can be directly determined that the above communication connection status is normal.

[0106] When the first result is that there is user data sent by the platform that fails to be transmitted, there are many factors that may lead to user data transmission failure, such as abnormal communication connection between the platform and the target third-party database, or too long data length of user data transmitted to the target third-party database, etc. Therefore, after obtaining the above first result, it is necessary to further determine whether the communication connection between the platform and the target third-party database is normal to clarify whether the cause of the user data transmission failure is the abnormal communication connection; if not, the platform needs to further determine whether it is caused by other factors.

[0107] Among them, the platform can determine the above-mentioned communication connection status through heartbeat detection. Specifically, when there is no abnormality in the diagnosis result of the configuration diagnosis, according to the preset diagnosis cycle, every period of the above-mentioned diagnosis cycle, it is detected whether the heartbeat information reported by the target third-party database is obtained. When the reported heartbeat information is obtained, it is determined that the communication connection between the platform and the target third-party database is normal; when the reported heartbeat information is not obtained, it is determined that the communication connection between the platform and the target third-party database is abnormal.

[0108] Alternatively, the platform sends a communication connection detection request to the target third-party database. If the target third-party database responds to the communication connection detection request, it is determined that the communication connection between the platform and the target third-party database is normal. This is reasonable and is not specifically limited here.

[0109] When determining whether there is user data that fails to be transmitted during the process of the platform transmitting user data to the target third-party database, it can be determined by checking whether there is user data that fails to be transmitted in the platform's database. If so, it is determined that there is user data that fails to be transmitted during the data transmission process; if not, it is determined that there is no user data that fails to be transmitted during the data transmission process.

[0110] Alternatively, the user data actually stored in the target third-party database can be compared with the user data recorded by the platform and has been transmitted to the target third-party database to see if they are consistent. If they are inconsistent, it is determined that there is user data that failed to be transmitted during the data transmission process; if they are consistent, it is determined that there is no user data that failed to be transmitted during the data transmission process. This is all reasonable and is not specifically limited here.

[0111] S302: When the communication connection is normal and there is no user data with transmission failure, determine that the diagnosis result of the transmission type diagnosis is normal transmission.

[0112] If the communication connection between the platform and the target third-party database is normal and there is no user data that fails to be transmitted, then there is no abnormality in the data transmission status between the platform and the target third-party database corresponding to the configured data source, and the diagnosis result of the transmission diagnosis is determined to be normal transmission.

[0113] S303: When the communication connection is normal and there is user data that has failed to be transmitted, determine that the diagnosis result of the transmission type diagnosis is transmission failure.

[0114] If the communication connection between the platform and the target third-party database is normal, but there is user data that fails to be transmitted during the data transmission process, then the data transmission status between the platform and the target third-party database corresponding to the configured data source is abnormal during the data transmission process, and the diagnosis result of the transmission type diagnosis is determined to be transmission failure.

[0115] S304: When the communication connection is abnormal, determine that the diagnosis result of the transmission type diagnosis is a connection failure.

[0116] If the communication connection between the platform and the target third-party database is abnormal, the communication connection between the platform and the target third-party database corresponding to the configured data source cannot be established, and the diagnosis result of the transmission type diagnosis is determined to be connection failure.

[0117] It can be seen that in the embodiment of the present application, by determining whether the communication connection between the platform and the target third-party database is normal and whether there is user data that has failed to be transmitted, three types of diagnostic results of transmission-related diagnosis can be obtained. Based on these three different diagnostic results, it is possible to accurately understand whether there are abnormalities in the communication connection between the platform and the target third-party database and the user data transmission.

[0118] As an implementation manner of an embodiment of the present application, the second dependency relationship is that the preset integrity diagnosis depends on the transmission diagnosis and the configuration diagnosis; when the diagnosis result of the transmission diagnosis satisfies the second dependency relationship, the step of performing integrity diagnosis on the user data transmitted between the platform and the target third-party database may include:

[0119] When the diagnosis result of the transmission diagnosis indicates that the data transmission status between the platform and the target third-party database is normal, the integrity of the user data transmitted between the platform and the target third-party database is diagnosed to ensure the integrity of the user data transmitted between the platform and the target third-party database.

[0120] Only when the data source corresponding to the target third-party database is configured on the platform can a communication connection between the platform and the target third-party database be established; only when the communication connection between the platform and the target third-party database is normal and there is no user data that fails to be transmitted, can an integrity diagnosis be performed on the user data transmitted between the platform and the target third-party database.

[0121] Therefore, when the platform has been configured with the data source corresponding to the target third-party database, and there is no abnormality in the data transmission status between the platform and the target third-party database corresponding to the configured data source, that is, when the diagnostic results of the configuration diagnosis and the transmission diagnosis are both normal, the integrity of the user data transmitted between the platform and the target third-party database can be diagnosed, thereby ensuring that there is no user data in the platform that has not been transmitted to the target third-party database.

[0122] It can be seen that in the embodiment of the present application, when the diagnosis result of the transmission diagnosis indicates that the data transmission status between the platform and the target third-party database is normal, the integrity of the user data transmitted between the platform and the target third-party database is diagnosed. In this way, it can be avoided that there is user data in the platform that has not been transmitted to the target third-party database, thereby effectively ensuring the integrity of the user data transmitted between the platform and the target third-party database.

[0123] As an implementation of an embodiment of the present application, the above-mentioned step of diagnosing the integrity of user data transmitted between the platform and the third-party database may include at least one of the following:

[0124] In response to the test data transmission instruction, based on the acquired database information of the target third-party database, the test data is sent to the target third-party database, and whether the database information of the target third-party database is correct is determined according to the transmission result, and if the database information of the target third-party database is correct, the database information of the target third-party database is saved;

[0125] The database information includes the database table name and field name.

[0126] In response to the transmission failure cause diagnosis instruction, based on the preset error code analysis file, the error code sent by the target third-party database is parsed to obtain the user data transmission failure cause, and the error code and the corresponding user data transmission failure cause are saved;

[0127] Among them, the error code is sent by the target third-party database to the platform when the platform fails to transmit user data to the target third-party database.

[0128] In response to the breakpoint resume instruction, the saved user data that failed to be transmitted is transmitted to the target third-party database according to the preset time point included in the breakpoint resume instruction.

[0129] In response to the data synchronization instruction, the user data to be synchronized within the time range indicated by the data synchronization instruction is obtained from the data source corresponding to the configured target third-party database, and the user data to be synchronized is transmitted to the target third-party database.

[0130] When obtaining the database information of the target third-party data set by the user, in order to ensure that the above database information is correct, the platform can respond to the test data transmission instruction, generate and send test data to the target third-party database indicated by the above database information. When the above target third-party database receives the test data, it is determined that the database information is correct, and the database information of the above target third-party database can be saved.

[0131] When the target third-party database does not receive the test data, it is determined that the database information is wrong, and the user is prompted to modify the database information. After the user makes the modification, the test data is sent again to the target third-party database indicated by the modified database information until it is determined that the database information set by the user is correct. The database information may include database table names and field names.

[0132] For example, when a user saves the target third-party database information, a page will pop up on the web page to remind the user whether to perform a test data transmission. When the user chooses to perform a test data transmission, the platform will generate a test data and transmit this test data to the target third-party database. When the target third-party database receives this test data, the platform determines that the target third-party database information set by the user is correct and prompts the user to save it. In this way, the platform can determine whether the database table name and field name in the database information set by the user are correct.

[0133] When the diagnosis result of the above-mentioned transmission diagnosis is transmission failure or connection failure, the target third-party database will return an error code for transmission failure to the platform. Since there are many categories of error codes and they are usually numbers that users do not understand the meaning of, in order to facilitate users to deal with the failure to transmit user data, the platform responds to the transmission failure cause diagnosis instruction, analyzes the above error code based on the pre-stored error code analysis file, obtains the cause of the user data transmission failure, and saves the error code and the corresponding cause of user data transmission failure, so as to subsequently display the error code and the corresponding cause of user data transmission failure to the user, so as to facilitate users to make modifications based on the cause of user data transmission failure.

[0134] When the diagnosis result of the transmission diagnosis is transmission failure, the cause of the user data transmission failure parsed by the platform from the error code may be that the communication connection between the platform and the target third-party database is disconnected, the length of the user data is too long, and the type of user data is incompatible, etc., which are all reasonable and are not specifically limited here.

[0135] When the diagnosis result of transmission diagnosis is connection failure, the platform may parse the error code to find that the cause of user data transmission failure may be failure to find the target third-party database, unstable network signal, and low platform version, which are all reasonable and are not specifically limited here.

[0136] When the diagnosis result of the above transmission diagnosis is transmission failure or connection failure, the target third-party database returns an error code to the platform and also returns the user data of the failed transmission to the platform for storage by the platform. Therefore, after the platform responds to the breakpoint resume instruction, when the preset time point included in the breakpoint resume instruction is reached, the platform can read the user data of the failed transmission stored in the platform database and retransmit it to the target third-party database.

[0137] Among them, in addition to the above-mentioned preset time point, the above-mentioned breakpoint resume instruction can also include the amount of user data retransmitted to the target third-party database, the identification of the user data, and the type of user data, etc., which are not specifically limited here.

[0138] Since the user may have forgotten to configure the data source corresponding to the target third-party database on the platform, and the platform transmits user data to the target third-party database in real time, the user data obtained by the platform cannot be transmitted to the target third-party database before the platform configures the corresponding data source, resulting in incomplete user data stored in the target third-party database.

[0139] Therefore, the user can choose the time range and data source for obtaining user data and issue a data synchronization instruction. The platform responds to the data synchronization instruction and obtains the user data to be synchronized within the time range indicated by the data synchronization instruction from the data source corresponding to the configured target third-party database, and transmits the user data to be synchronized to the target third-party database, thereby ensuring the integrity of the user data.

[0140] It can be seen that in the embodiment of the present application, the platform can respond to at least one of the test data transmission instructions, the transmission failure cause diagnosis instructions, the breakpoint resume instructions and the data synchronization instructions to diagnose whether the database information set by the user is correct, determine the reason why the platform failed to transmit user data to the target third-party database, retransmit the user data that failed to be transmitted and stored in the platform's database to the target third-party database, and synchronize the user data acquired before the data source is configured to the target third-party database, thereby ensuring the integrity of the user data transmitted between the platform and the target third-party database.

[0141] As an implementation of an embodiment of the present application, after the above step of saving the error code and the corresponding reason for the failure of user data transmission, the above method may further include:

[0142] In response to a query instruction issued by the user, based on the target error code corresponding to the user data whose transmission failed as indicated by the query instruction, the user data transmission failure cause corresponding to the target error code is searched from the saved error codes and the corresponding user data transmission failure causes.

[0143] The found reasons for the failure in transmitting user data are displayed, so that the user can view the reasons for the failure in transmitting user data corresponding to the failed transmission.

[0144] After the platform saves the error code returned by the target third-party database and the reason for the user data transmission failure obtained by the platform through parsing the error code, the user can query the user data that failed to be transmitted on the query page of the platform. In response to the query instruction issued by the user, the platform searches for the target error code and the reason for the user data transmission failure corresponding to the above query instruction in the saved error code and the corresponding reason for the user data transmission failure.

[0145] Since users do not necessarily understand the meaning of the target error code, the platform can display the reasons for the failure of user data transmission to users. In this way, users can accurately determine the reasons for the failure of each user data transmission and make modifications based on the above reasons, so that the user data that failed to be transmitted can be retransmitted to the target third-party database after modification.

[0146] For example, if the displayed reason for user data transmission failure is that the communication connection between the platform and the target third-party database is disconnected, the user can re-establish the communication connection between the platform and the target third-party database; if the displayed reason for user data transmission failure is that the length of the user data is too long, the user can adjust the length of the user data so that the modified user data can be transmitted to the target third-party database; if the platform version is lower and the communication connection cannot be established, the user can upgrade the platform to the latest version and then re-establish the communication connection between the platform and the target third-party database. This is all reasonable and is not specifically limited here.

[0147] It can be seen that in the embodiment of the present application, after the platform saves the error code and the corresponding user data transmission failure reason, the platform can search for the user data transmission failure reason corresponding to the target error code indicated by the query instruction according to the query instruction issued by the user, and display the found user data transmission failure reason to the user for viewing. In this way, it is convenient for the user to solve the corresponding problem according to the found user data transmission failure reason, so that the platform can subsequently retransmit the user data that failed to be transmitted to the target third-party database, ensuring the integrity of the user data transmission.

[0148] As an implementation method of the present application, Figure 4 As shown, before the step of performing configuration diagnosis on the target third-party database indicated by the diagnostic instruction in response to the diagnostic instruction, the method may further include:

[0149] S401, obtaining configuration information and database type of a third-party database.

[0150] In order to establish a communication connection between the platform and the data, the platform can obtain the configuration information and database type of the third-party database, where the third-party database can include the target third-party database; the configuration information may include the type, host address, port number, and security authentication of the third-party database.

[0151] The above-mentioned third-party databases may include at least one of postgresql (postgre structured query language, object-relational database server), mysql (my structured query language, relational database management system), sqlserver (structured query language server, relational database management system), oracle (Oracle database), etc., and are not specifically limited here.

[0152] S402: For each third-party database, create a corresponding database instance according to the configuration information and database type of the third-party database.

[0153] After obtaining the configuration information and database type of the third-party database, a database instance corresponding to each third-party database is created according to the obtained configuration information and database type of each third-party database, so as to facilitate the subsequent use of the database instance to mobilize different database drivers.

[0154] S403, calling a database driver corresponding to the database type through the database instance, and establishing a communication connection with the third-party database using the database driver.

[0155] After creating the database instance corresponding to each third-party database, the platform calls the database driver corresponding to the database type through each database instance, and then uses the database driver to establish a communication connection between the platform and the third-party database, thereby realizing the function of one platform being able to connect to multiple different third-party databases.

[0156] The above database driver may include a driver program, a driver component or a client, etc., which is not specifically limited here.

[0157] For example, when the third-party database type is postgresql, the corresponding database driver is libpq.dll (libpq dynamic link library); when the third-party database type is mysql, the corresponding database driver is mysql dynamic link library; when the third-party database type is sqlserver, the corresponding database driver is ado (activeX data objects) component; when the third-party database type is oracle, the corresponding database driver is odac (oracle data access components). These are all reasonable and are not specifically limited here.

[0158] In this way, after using the database driver to establish a communication connection between the platform and the corresponding third-party database, Figure 5 As shown, three types of diagnostic tools can be used to diagnose the target third-party database. Using the diagnostic tools on the platform, namely the above-mentioned three types of diagnosis, configuration diagnosis, transmission diagnosis and integrity diagnosis, different database instances are used to diagnose different third-party databases according to different types of third-party databases.

[0159] When the type of the third-party database is sqlserver (relational database management system), the platform calls the ado (activeX program object) component to establish a communication connection with the sqlserver database and perform diagnosis; when the type of the third-party database is mysql (relational database management system), the platform calls the mysql dynamic link library driver to establish a communication connection with the mysql database and perform diagnosis; when the type of the third-party database is oracle (oracle database), the platform calls the odac (oracle data access component) component to establish a communication connection with the oracle database and perform diagnosis; when the type of the third-party database is postgresql (object-relational database server), the platform calls the libpq.dll (libpq dynamic link library) driver to establish a communication connection with the postgresql database and perform diagnosis.

[0160] It can be seen that in the embodiment of the present application, before diagnosing the target third-party database, the platform can obtain the configuration information and database type of the third-party database, and for each third-party database, create a corresponding database instance according to the configuration information and database type of the third-party database, and then call the database driver corresponding to the database type through the database instance, and use the database driver to establish a communication connection with the third-party database. In this way, after establishing a communication connection between the platform and multiple different third-party databases, the diagnostic tool can implement diagnostic functions for different databases according to different database connections for different third-party database types.

[0161] As an implementation of the embodiment of the present application, the above method may also include:

[0162] If the diagnostic result of the configuration diagnosis indicates that the platform is not configured with the data source corresponding to the target third-party database, the diagnostic result of the configuration diagnosis and the first prompt information are returned, and the transmission diagnosis and integrity diagnosis are not performed, wherein the first prompt information is used to prompt the user that the platform is not configured with the data source corresponding to the target third-party database;

[0163] In the case where the diagnosis result of the transmission diagnosis is a transmission failure or a connection failure, the diagnosis result of the transmission diagnosis and the second prompt information are returned, and the integrity diagnosis is not performed, wherein the second prompt information is used to prompt the user to determine that the diagnosis result of the transmission diagnosis is the cause of the transmission failure or the connection failure;

[0164] When the diagnosis result of the integrity diagnosis is that the user data transmitted between the platform and the target third-party database is incomplete, the diagnosis result of the integrity diagnosis and the third prompt information are returned, wherein the third prompt information is used to prompt that the user data transmitted between the platform and the target third-party database is incomplete.

[0165] In the case where the diagnosis result of the configuration diagnosis indicates that the platform is not configured with the data source corresponding to the target third-party database, the first prompt information returned may include: prompting the user that the platform is not configured with the data source, prompting the user that the data source configured by the platform does not correspond to the target third-party database, indicating the user to enter the configuration page path for configuring the data source corresponding to the target third-party database for the platform or the configuration window for configuring the data source corresponding to the target third-party database for the platform, etc. And in the case that the platform is not configured with the data source corresponding to the target third-party database, it is impossible to transmit user data to the target third-party database, so there is no need to perform transmission diagnosis and integrity diagnosis, which are all reasonable and are not specifically limited here.

[0166] In the case where the diagnosis result of the transmission diagnosis is transmission failure or connection failure, the second prompt information returned may include: suggesting that the user confirm with the equipment manufacturer of the target third-party database whether the server to which the target third-party database belongs is working properly, and prompting to store the user data that failed to be transmitted in the platform to prevent the loss of user data that failed to be transmitted, etc. In addition, in the case where the diagnosis result of the transmission diagnosis is transmission failure or connection failure, there may be user data that failed to be transmitted, so there is no need to perform integrity diagnosis, which is reasonable and is not specifically limited here.

[0167] When the diagnosis result of the integrity diagnosis is that the user data transmitted between the platform and the target third-party database is incomplete, the third prompt information returned above may include: prompting the user to send test data to the target third-party database, prompting the user to check the reason for the transmission failure, prompting the administrator to set a preset time point included in the breakpoint resume instruction so that the platform can transmit the saved user data that failed to be transmitted to the target third-party database at the preset time point, and prompting the user to issue a data synchronization instruction to synchronize the user data to be synchronized in the data source corresponding to the target third-party database, etc., which are not specifically limited here.

[0168] It can be seen that in the embodiment of the present application, when the diagnostic results of the configuration diagnosis, transmission diagnosis and integrity diagnosis of the target third-party database are reported as errors, the platform can return the corresponding first prompt information, second prompt information or third prompt information, so that managers and users can determine the cause of the diagnostic result error as soon as possible according to the prompt information and make corresponding adjustments.

[0169] As an implementation of an embodiment of the present application, the first prompt information may include: an entry path to a configuration page for configuring a data source corresponding to a target third-party database for the platform or a configuration window for configuring a data source corresponding to a target third-party database for the platform; and / or,

[0170] The second prompt information may include at least one of: suggesting that the user confirm with the device manufacturer of the target third-party database whether the server to which the target third-party database belongs is working normally, and prompting the user to store the user data that failed to be transmitted in the platform; and / or,

[0171] The third prompt information may include: prompting the user to send test data to the target third-party database, prompting the user to check the reason for the transmission failure, prompting the administrator to set a preset time point included in the breakpoint resume instruction so that the platform can transfer the saved user data that failed to be transmitted to the target third-party database at the preset time point, and prompting the user to start the data synchronization instruction so that the platform can synchronize the user data to be synchronized in the data source corresponding to the target third-party database.

[0172] After returning to the first prompt information, the user can click on the entry path of the configuration page for configuring the data source corresponding to the target third-party database for the platform included in the first prompt information, thereby entering the configuration window for configuring the data source corresponding to the target third-party database for the platform, and configure the corresponding data source for the platform in the configuration window; alternatively, the user can also directly configure the data source corresponding to the target third-party database for the platform in the configuration window that pops up when the platform returns the first prompt information, and so on, which is not specifically limited here.

[0173] After the second prompt message is returned, the user can contact the equipment manufacturer of the target third-party database according to the suggestions in the second prompt message to confirm whether the server to which the target third-party database belongs is working normally, thereby determining whether the diagnosis result of the transmission-related diagnosis of transmission failure or connection failure is due to a failure of the server to which the target third-party database belongs; and the user can also store the user data of failed transmission in the platform according to the prompt of the second prompt message to prevent the loss of user data of failed transmission, etc., which are not specifically limited here.

[0174] After the third prompt information is returned, the user can perform test data transmission according to the prompt in the third prompt information, and a test data is generated in the platform and sent to the target third-party database to determine that the target third-party database information set by the user is correct; or the user clicks the analysis button in the page according to the prompt in the third prompt information, and the platform analyzes the error code returned when the transmission fails, so that the user can obtain the reason for the failure of user data transmission and make corresponding modifications based on the reason; or the administrator is prompted to set a preset time point included in the breakpoint resume instruction, so that the platform can transfer the saved user data with failed transmission to the target third-party database at the preset time point to ensure the integrity of the target third-party database; in addition, the user can also select the time range and data source of the user data according to the prompt in the third prompt information and issue a data synchronization instruction, so that the platform responds to the data synchronization instruction and transfers the user data to be synchronized in the corresponding time range and data source to the target third-party database, etc., which are not specifically limited here.

[0175] It can be seen that in the embodiment of the present application, when the diagnosis result is wrong, the prompt information returned by the platform can guide users and managers in the direction of troubleshooting the problem, so that users and managers can basically understand the reasons that caused the attendance platform to be disconnected from the target third-party database. There is no need for manual aimless troubleshooting, and the problem that caused the diagnosis result to be wrong can be solved more quickly, saving human resources.

[0176] As an implementation of the embodiment of the present application, the above method may also include:

[0177] The platform responds to the user data transmission instruction, and when the diagnosis result indicates that the configuration diagnosis, transmission diagnosis and integrity diagnosis of the target third-party database have all passed, sends the user data indicated by the user data transmission instruction to the target third-party database.

[0178] When the diagnostic results of the configuration type diagnosis indicate that the platform is configured with the data source corresponding to the target third-party database, the diagnostic results of the transmission type diagnosis indicate that the data transmission status is normal, and at least one type of integrity diagnosis is performed on the user data transmitted between the platform and the target third-party database, after receiving the user data transmission instruction, the user data indicated by the user data transmission instruction is sent to the target third-party database.

[0179] In one embodiment, after the platform responds to the user data transmission instruction, it can immediately perform configuration diagnosis and transmission diagnosis on the target third-party database, as well as integrity diagnosis on the user data transmitted between the platform and the target third-party database. When the diagnostic results of the above three types of diagnosis are all passed, the user data indicated by the user data transmission instruction is sent to the target third-party database.

[0180] In one embodiment, after the platform responds to the user data transmission instruction, it can obtain the most recent diagnostic result stored in the platform. When the diagnostic results of the above three types of diagnoses are all passed, the user data indicated by the user data transmission instruction is sent to the target third-party database.

[0181] Specifically, the process of transferring user data from the platform to the target third-party database can be as follows: Figure 6 As shown, after the user clocks in or swipes a card on the device, the device sends a user data reporting instruction to the task manager, and the task manager starts the user data transmission task and sends the user data transmission instruction to the platform. The platform responds to the user data transmission instruction and determines whether it has configured the data source. The platform can obtain the diagnosis result of the most recent configuration diagnosis or immediately perform configuration diagnosis on the target third-party database to obtain the current configuration diagnosis result.

[0182] If the above diagnostic results are abnormal, indicating that the platform is not configured, the above user data is filtered; if the above diagnostic results are normal, indicating that the platform is configured with the data source, further transmission diagnosis is performed to verify the communication connection. Among them, the platform can obtain the diagnosis result of the most recent transmission diagnosis or immediately perform transmission diagnosis on the target third-party database to obtain the diagnosis result of the current transmission diagnosis.

[0183] If the above diagnosis result is that the communication connection is abnormal, indicating that the communication connection between the platform and the target third-party database is disconnected, the user data is saved in the platform database; if the above diagnosis result is that the communication connection is normal, indicating that the communication connection between the platform and the target third-party database is normal, the platform transmits the user data to the target third-party database, and further diagnoses whether the user data transmission is successful. If the above diagnosis result is that there is user data that failed to be transmitted, indicating that the user data transmission is unsuccessful, it is saved in the platform database; if the above diagnosis result is that there is no user data that failed to be transmitted, indicating that the user data transmission is successful.

[0184] It can be seen that in the embodiment of the present application, when the diagnostic results indicate that the configuration diagnosis, transmission diagnosis and integrity diagnosis of the target third-party database have all passed, the user data indicated by the user data transmission instruction is sent to the target third-party database, which can effectively ensure the integrity and stability of the user data transmission.

[0185] In one embodiment, when the platform responds to the user data transmission instruction and chooses to immediately diagnose the target third-party database, or when the preset diagnosis cycle is reached, the platform diagnoses the target third-party database as follows: Figure 7 As shown, the user configures the third-party database information on the web page, and after the configuration is completed, the third-party database information is sent to the platform. The platform establishes a communication connection with the target third-party database information specified by the third-party database information based on the acquired third-party database information. If the communication connection is successfully established, the target third-party database sends a success signal to the platform, and the platform then sends the success signal to the web page to display to the user, wherein the above-mentioned third-party database information may include the configuration information and database type of the third-party database.

[0186] After the platform successfully establishes a communication connection with the target third-party database, the event source reports the acquired user data to the platform. For example, the event source in the attendance device reports the acquired employee clock-in data to the platform. After the user confirms to start the diagnosis on the web page, the web page sends a diagnostic instruction to the platform. In response to the diagnostic instruction, the platform first performs a configuration diagnosis on the target third-party database indicated by the diagnostic instruction to diagnose whether the platform is configured with a data source, where the data source corresponds to the target third-party database; after determining that the platform is configured with a data source corresponding to the target third-party database, the platform performs a transmission diagnosis on the target third-party database to determine whether the communication connection between the platform and the target third-party database is normal, and whether there is any user data that has failed to be transmitted.

[0187] When the communication connection is normal and there is no user data that fails to be transmitted, the integrity diagnosis of the user data transmitted between the platform and the target third-party database is further performed, where the integrity diagnosis may include at least one of the following:

[0188] The platform transmits the test data to the target third-party database in response to the test data transmission instruction;

[0189] The platform responds to the transmission failure cause diagnosis instruction and performs transmission failure cause diagnosis;

[0190] The platform responds to the breakpoint resume instruction and transmits the saved user data that failed to be transmitted to the target third-party database according to the preset time point included in the breakpoint resume instruction;

[0191] Since the user may have forgotten to configure the data source corresponding to the target third-party database on the platform, and the platform transmits user data to the target third-party database in real time, the user data obtained by the platform cannot be transmitted to the target third-party database before the platform configures the corresponding data source, resulting in incomplete user data stored in the target third-party database. After the user selects the time range and data source for obtaining user data and turns on data synchronization, the platform can actively request user data synchronization from the event source in response to the data synchronization instruction, query and obtain the user data to be synchronized within the time range; or obtain the user data to be synchronized from the data source corresponding to the configured target third-party database, and then transmit the obtained user data to be synchronized to the target third-party database to achieve user data synchronization.

[0192] It can be seen that in the embodiment of the present application, the diagnostic tools designed on the platform: configuration diagnosis, transmission diagnosis, and integrity diagnosis can be used to diagnose the correctness of the communication connection between the platform and different third-party databases, the accuracy of user data transmission, and the integrity of transmitted user data. By using the three different diagnostic functions of the diagnostic tool, the integrity of user data transmission between the platform and the target third-party database is guaranteed. In addition, the diagnostic tool has established communication connections with many different types of databases, has a certain compatibility, can diagnose different databases, and is convenient for managers and users to operate and manage third-party databases, increasing the ease of use of the platform.

[0193] Corresponding to the above-mentioned diagnostic method for a three-party database, an embodiment of the present application also provides a diagnostic device for a three-party database. The following introduces a diagnostic device for a three-party database provided in an embodiment of the present application.

[0194] like Figure 8 As shown, a diagnostic device for a third-party database is applied to a platform, and the platform is used to send user data to the third-party database. The device includes:

[0195] A configuration diagnosis module 801 is used to perform configuration diagnosis on a target third-party database indicated by the diagnosis instruction in response to the diagnosis instruction;

[0196] The configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database.

[0197] A transmission diagnosis module 802, configured to perform transmission diagnosis on the target third-party database when the diagnosis result of the configuration diagnosis satisfies the first dependency relationship;

[0198] The first dependency relationship is a preset dependency relationship between the transmission-type diagnosis and the configuration-type diagnosis, and the transmission-type diagnosis is used to determine the data transmission status between the platform and the target third-party database.

[0199] The integrity diagnosis module 803 is used to perform integrity diagnosis on the user data transmitted between the platform and the target third-party database when the diagnosis result of the transmission diagnosis satisfies the second dependency relationship, and obtain the diagnosis result of the target third-party database;

[0200] The second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission diagnosis and the configuration diagnosis.

[0201] It can be seen that in the scheme provided by the embodiment of the present application, the platform can respond to the diagnostic instruction and perform configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with the data source corresponding to the target third-party database, and then, if the diagnostic result of the configuration diagnosis satisfies the first dependency, the target third-party database is subjected to transmission diagnosis, wherein the first dependency is the dependency between the preset transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database, and then, if the diagnostic result of the transmission diagnosis satisfies the second dependency, the user data transmitted by the platform and the target third-party database is subjected to integrity diagnosis to obtain the diagnostic result of the target third-party database, wherein the second dependency is the dependency between the preset integrity diagnosis and the transmission diagnosis and the configuration diagnosis. In this way, the platform diagnoses the target third-party database based on the dependency between the configuration diagnosis, the transmission diagnosis and the integrity diagnosis, and determines whether the communication connection and data transmission between the platform and the target third-party database are normal, thereby ensuring the integrity and stability of the user data transmission. Moreover, the diagnostic result can guide the direction of troubleshooting, without the need for manual aimless troubleshooting, saving human resources.

[0202] As an implementation of an embodiment of the present application, the first dependency relationship is that the transmission diagnosis is preset to depend on the configuration diagnosis; the transmission diagnosis module 802 may include:

[0203] The data transmission status determination submodule determines the data transmission status between the above-mentioned platform and the above-mentioned target third-party database corresponding to the configured data source based on the communication connection between the above-mentioned platform and the above-mentioned target third-party database, when the diagnostic result of the above-mentioned configuration-type diagnosis indicates that the above-mentioned platform has been configured with the data source corresponding to the above-mentioned target third-party database, and obtains the diagnostic result of the above-mentioned transmission-type diagnosis.

[0204] As an implementation of an embodiment of the present application, the above-mentioned data transmission status determination submodule may include:

[0205] The communication connection unit is used to determine whether the communication connection between the above platform and the above target third-party database is normal, and to determine whether there is any user data that fails to be transmitted among the user data sent by the above platform to the above target third-party database corresponding to the configured data source.

[0206] The first diagnosis result determination unit is used to determine that the diagnosis result of the transmission type diagnosis is normal transmission when the communication connection is normal and there is no user data with transmission failure.

[0207] The second diagnosis result determination unit is used to determine that the diagnosis result of the transmission type diagnosis is a transmission failure when the communication connection is normal and there is user data that fails to be transmitted.

[0208] The third diagnosis result determination unit is used to determine that the diagnosis result of the above-mentioned transmission type diagnosis is a connection failure when the above-mentioned communication connection is abnormal.

[0209] As an implementation of an embodiment of the present application, the second dependency relationship is that the preset integrity diagnosis depends on the transmission diagnosis and the configuration diagnosis; the integrity diagnosis module 803 may include:

[0210] The data integrity determination submodule diagnoses the integrity of the user data transmitted between the above-mentioned platform and the above-mentioned target third-party database when the diagnosis result of the above-mentioned transmission-type diagnosis indicates that the data transmission status between the above-mentioned platform and the above-mentioned target third-party database is normal transmission, so as to ensure the integrity of the user data transmitted between the above-mentioned platform and the above-mentioned target third-party database.

[0211] As an implementation of an embodiment of the present application, the above-mentioned data integrity determination submodule may include at least one of the following:

[0212] a test data transmission unit, configured to respond to the test data transmission instruction, send test data to the target third-party database based on the acquired database information of the target third-party database, and determine whether the database information of the target third-party database is correct according to the transmission result, and save the database information of the target third-party database if the database information of the target third-party database is correct;

[0213] The above database information includes database table names and field names.

[0214] A failure cause diagnosis unit, which is used to respond to the transmission failure cause diagnosis instruction, analyze the error code sent by the target third-party database based on a preset error code analysis file, obtain the user data transmission failure cause, and save the error code and the corresponding user data transmission failure cause;

[0215] Among them, the above error code is sent by the above target third-party database to the above platform when the above platform fails to transmit user data to the above target third-party database.

[0216] A breakpoint resume execution unit, configured to respond to a breakpoint resume instruction and transmit the saved user data that failed to be transmitted to the target third-party database according to a preset time point included in the breakpoint resume instruction;

[0217] The user data synchronization unit is used to respond to the data synchronization instruction, obtain the user data to be synchronized within the time range indicated by the above data synchronization instruction from the data source corresponding to the above configured target third-party database, and transmit the above user data to be synchronized to the above target third-party database.

[0218] As an implementation of the embodiment of the present application, the above-mentioned data integrity determination submodule may also include:

[0219] A failure cause search unit is used to respond to a query instruction issued by a user, based on a target error code corresponding to the user data whose transmission failed as indicated by the query instruction, to search for the user data transmission failure cause corresponding to the target error code from the saved error codes and the corresponding user data transmission failure causes.

[0220] The failure reason display unit is used to display the found user data transmission failure reason, so that the user can view the user data transmission failure reason corresponding to the user data that failed to be transmitted.

[0221] As an implementation of the embodiment of the present application, the above device may further include:

[0222] The database information acquisition module is used to acquire the configuration information and database type of the third-party database, wherein the third-party database includes the target third-party database.

[0223] The database instance creation module is used to create a corresponding database instance for each third-party database according to the configuration information and database type of the third-party database.

[0224] The communication connection establishing module is used to call the database driver corresponding to the database type through the above database instance, and use the above database driver to establish a communication connection with the third-party database.

[0225] As an implementation of the embodiment of the present application, the above device may further include:

[0226] A first prompt information returning module is used to return the diagnostic result of the configuration diagnosis and the first prompt information when the diagnostic result of the configuration diagnosis indicates that the platform is not configured with the data source corresponding to the target third-party database, and not to perform the transmission diagnosis and integrity diagnosis, wherein the first prompt information is used to prompt the user that the platform is not configured with the data source corresponding to the target third-party database;

[0227] A second prompt information returning module is used to return the diagnosis result of the transmission diagnosis and the second prompt information when the diagnosis result of the transmission diagnosis is a transmission failure or a connection failure, and not to perform integrity diagnosis, wherein the second prompt information is used to prompt the user to determine the cause of the diagnosis result of the transmission diagnosis being the transmission failure or the connection failure;

[0228] The third prompt information returning module is used to return the diagnosis result of the integrity diagnosis and the third prompt information when the diagnosis result of the integrity diagnosis is that the user data transmitted by the platform and the target third-party database is incomplete, wherein the third prompt information is used to prompt that the user data transmitted by the platform and the target third-party database is incomplete.

[0229] As an implementation of an embodiment of the present application, the first prompt information may include: an entry path to a configuration page for configuring a data source corresponding to a target third-party database for the platform or a configuration window for configuring a data source corresponding to a target third-party database for the platform; and / or,

[0230] The second prompt information may include at least one of: suggesting that the user confirm with the device manufacturer of the target third-party database whether the server to which the target third-party database belongs is working normally, and prompting the user to store the user data that failed to be transmitted in the platform; and / or,

[0231] The third prompt information may include: prompting the user to send test data to the target third-party database, prompting the user to check the reason for the transmission failure, prompting the administrator to set a preset time point included in the breakpoint resume instruction so that the platform can transfer the saved user data that failed to be transmitted to the target third-party database at the preset time point, and prompting the user to start the data synchronization instruction so that the platform can synchronize the user data to be synchronized in the data source corresponding to the target third-party database.

[0232] The present application also provides an electronic device, such as Fig. 9 As shown, including:

[0233] Memory 901, used for storing computer programs;

[0234] The processor 902 is used to implement the diagnosis method of the third-party database described in any of the above embodiments when executing the program stored in the memory 901.

[0235] It can be seen that in the scheme provided by the embodiment of the present application, the platform can respond to the diagnostic instruction and perform configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with the data source corresponding to the target third-party database, and then, if the diagnostic result of the configuration diagnosis satisfies the first dependency, the target third-party database is subjected to transmission diagnosis, wherein the first dependency is the dependency between the preset transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database, and then, if the diagnostic result of the transmission diagnosis satisfies the second dependency, the user data transmitted by the platform and the target third-party database is subjected to integrity diagnosis to obtain the diagnostic result of the target third-party database, wherein the second dependency is the dependency between the preset integrity diagnosis and the transmission diagnosis and the configuration diagnosis. In this way, the platform diagnoses the target third-party database based on the dependency between the configuration diagnosis, the transmission diagnosis and the integrity diagnosis, and determines whether the communication connection and data transmission between the platform and the target third-party database are normal, thereby ensuring the integrity and stability of the user data transmission. Moreover, the diagnostic result can guide the direction of troubleshooting, without the need for manual aimless troubleshooting, saving human resources.

[0236] Furthermore, the electronic device may further include a communication bus and / or a communication interface, and the processor 902, the communication interface, and the memory 901 communicate with each other via the communication bus.

[0237] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0238] The communication interface is used for communication between the above electronic device and other devices.

[0239] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0240] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0241] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of the diagnostic method of any of the above-mentioned three-party databases are implemented.

[0242] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute the diagnostic method of any three-party database in the above embodiments.

[0243] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a solid-state hard disk (SSD), etc.

[0244] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0245] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, electronic device, computer-readable storage medium, and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0246] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A diagnostic method for a tripartite database, characterized in that: Applied to a platform, the platform is used to send user data to a third-party database, the method comprising: In response to the diagnostic instruction, performing configuration diagnosis on the target third-party database indicated by the diagnostic instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database; In the case where the diagnosis result of the configuration diagnosis satisfies the first dependency relationship, performing a transmission diagnosis on the target third-party database, wherein the first dependency relationship is a preset dependency relationship between the transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database; When the diagnostic result of the transmission type diagnosis satisfies the second dependency relationship, an integrity diagnosis is performed on the user data transmitted between the platform and the target third-party database to obtain the diagnostic result of the target third-party database, wherein the second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission type diagnosis and the configuration type diagnosis.

2. The method according to claim 1, characterized in that: The first dependency relationship is that the preset transmission-related diagnosis depends on the configuration-related diagnosis; The step of performing transmission diagnosis on the target third-party database when the diagnosis result of the configuration diagnosis satisfies the first dependency relationship includes: When the diagnostic result of the configuration-type diagnosis indicates that the platform has been configured with the data source corresponding to the target third-party database, the data transmission status between the platform and the target third-party database corresponding to the configured data source is determined based on the communication connection between the platform and the target third-party database to obtain the diagnostic result of the transmission-type diagnosis.

3. The method according to claim 2, characterized in that The step of determining the data transmission status between the platform and the target third-party database corresponding to the configured data source based on the communication connection between the platform and the target third-party database, and obtaining the diagnosis result of the transmission diagnosis includes: Determine whether the communication connection between the platform and the target third-party database is normal, and determine whether there is user data that fails to be transmitted among the user data sent by the platform to the target third-party database corresponding to the configured data source; In a case where the communication connection is normal and there is no user data that fails to be transmitted, determining that the diagnosis result of the transmission type diagnosis is normal transmission; In a case where the communication connection is normal and there is user data that fails to be transmitted, determining that the diagnosis result of the transmission type diagnosis is a transmission failure; In the case where the communication connection is abnormal, it is determined that the diagnosis result of the transmission type diagnosis is a connection failure.

4. The method according to claim 1, characterized in that: The second dependency relationship is that the preset integrity diagnosis depends on the transmission diagnosis and the configuration diagnosis; The step of performing integrity diagnosis on the user data transmitted between the platform and the target third-party database when the diagnosis result of the transmission-related diagnosis satisfies the second dependency relationship includes: When the diagnosis result of the transmission type diagnosis indicates that the data transmission status between the platform and the target third-party database is normal, the integrity of the user data transmitted between the platform and the target third-party database is diagnosed to ensure the integrity of the user data transmitted between the platform and the target third-party database.

5. The method according to claim 4, characterized in that The step of diagnosing the integrity of the user data transmitted between the platform and the target third-party database includes at least one of the following: In response to the test data transmission instruction, based on the acquired database information of the target third-party database, the test data is sent to the target third-party database, and whether the database information of the target third-party database is correct is determined according to the transmission result. If the database information of the target third-party database is correct, the database information of the target third-party database is saved, wherein the database information includes a database table name and a field name; In response to the transmission failure cause diagnosis instruction, based on the preset error code analysis file, the error code sent by the target third-party database is parsed to obtain the user data transmission failure cause, and the error code and the corresponding user data transmission failure cause are saved, wherein the error code is sent by the target third-party database to the platform when the platform fails to transmit user data to the target third-party database; In response to the breakpoint resume instruction, the saved user data that failed to be transmitted is transmitted to the target third-party database according to the preset time point included in the breakpoint resume instruction; In response to the data synchronization instruction, the user data to be synchronized within the time range indicated by the data synchronization instruction is obtained from the data source corresponding to the configured target third-party database, and the user data to be synchronized is transmitted to the target third-party database.

6. The method according to claim 5, characterized in that After the step of saving the error code and the corresponding reason for the failure of user data transmission, the method further includes: In response to a query instruction issued by a user, based on a target error code corresponding to the user data whose transmission fails as indicated by the query instruction, searching for a user data transmission failure cause corresponding to the target error code from the saved error codes and the corresponding user data transmission failure causes; The found reasons for the failure in transmitting the user data are displayed, so that the user can view the reasons for the failure in transmitting the user data corresponding to the failed transmission.

7. The method according to any one of claims 1 to 6, characterized in that: Before the step of performing configuration diagnosis on the target third-party database indicated by the diagnostic instruction in response to the diagnostic instruction, the method further includes: Acquire configuration information and database type of a third-party database, wherein the third-party database includes the target third-party database; For each third-party database, create a corresponding database instance according to the configuration information and database type of the third-party database; The database driver corresponding to the database type is called through the database instance, and a communication connection is established with the third-party database using the database driver.

8. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: In the case where the diagnosis result of the configuration diagnosis indicates that the platform is not configured with the data source corresponding to the target third-party database, the diagnosis result of the configuration diagnosis and the first prompt information are returned, and the transmission diagnosis and the integrity diagnosis are not performed, wherein the first prompt information is used to prompt the user that the platform is not configured with the data source corresponding to the target third-party database; In the case where the diagnosis result of the transmission diagnosis is a transmission failure or a connection failure, the diagnosis result of the transmission diagnosis and the second prompt information are returned, and the integrity diagnosis is not performed, wherein the second prompt information is used to prompt the user to determine that the diagnosis result of the transmission diagnosis is the cause of the transmission failure or the connection failure; When the diagnosis result of the integrity diagnosis is that the user data transmitted between the platform and the target third-party database is incomplete, the diagnosis result of the integrity diagnosis and a third prompt message are returned, wherein the third prompt message is used to prompt that the user data transmitted between the platform and the target third-party database is incomplete.

9. The method according to claim 8, characterized in that The first prompt information includes: an entry path to a configuration page for configuring a data source corresponding to a target third-party database for the platform or a configuration window for configuring a data source corresponding to a target third-party database for the platform; and / or, The second prompt information includes at least one of: suggesting that the user confirm with the device manufacturer of the target third-party database whether the server to which the target third-party database belongs is working normally, and prompting the user to store the user data that failed to be transmitted in the platform; and / or, The third prompt information includes: prompting the user to send the test data to the target third-party database, prompting the user to check the reason for the transmission failure, prompting the administrator to set a preset time point included in the breakpoint resume instruction so that the platform can transfer the saved user data that failed to be transmitted to the target third-party database at the preset time point, and prompting the user to start the data synchronization instruction so that the platform can synchronize the user data to be synchronized in the data source corresponding to the target third-party database.

10. A diagnostic device for a third-party database, characterized in that: Applied to a platform, the platform is used to send user data to a third-party database, the device includes: A configuration diagnosis module, configured to perform configuration diagnosis on a target third-party database indicated by the diagnosis instruction in response to the diagnosis instruction, wherein the configuration diagnosis is used to determine whether the platform is configured with a data source corresponding to the target third-party database; A transmission diagnosis module, configured to perform transmission diagnosis on the target third-party database if the diagnosis result of the configuration diagnosis satisfies a first dependency relationship, wherein the first dependency relationship is a preset dependency relationship between the transmission diagnosis and the configuration diagnosis, and the transmission diagnosis is used to determine the data transmission status between the platform and the target third-party database; An integrity diagnosis module is used to perform integrity diagnosis on the user data transmitted between the platform and the target third-party database to obtain the diagnosis result of the target third-party database when the diagnosis result of the transmission type diagnosis satisfies the second dependency relationship, wherein the second dependency relationship is a preset dependency relationship between the integrity diagnosis and the transmission type diagnosis and the configuration type diagnosis.

11. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-9 when executing a program stored in a memory.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Citation Information

Patent Citations

  • A method and apparatus for outputting information

    CN109308239A

  • Fault processing method and device for database server

    CN115686951A

  • Database exception monitoring method and device, storage medium and computer equipment

    CN116244152A

  • Method and device for transmitting data between databases, equipment and storage medium

    CN118012956A