CN114510495A - Database service data consistency processing method and system - Google Patents
Database service data consistency processing method and system Download PDFInfo
- Publication number
- CN114510495A CN114510495A CN202210418267.7A CN202210418267A CN114510495A CN 114510495 A CN114510495 A CN 114510495A CN 202210418267 A CN202210418267 A CN 202210418267A CN 114510495 A CN114510495 A CN 114510495A
- Authority
- CN
- China
- Prior art keywords
- service request
- database
- service
- transaction
- database operation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
Abstract
The application discloses a method and a system for processing consistency of database service data, wherein the method comprises the following steps: receiving a service request for operating a database, wherein the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target; running the service request; in the process of operating the service request, judging whether the service request is operated in one transaction; and if the service request is determined to be in one transaction, the data consistency can be maintained if an abnormal condition occurs in the execution process of the service request. The method and the device solve the problem that whether the condition that the data are inconsistent is not monitored due to the fact that whether the service request of the database can cause the data to be inconsistent or not in the prior art, so that whether the database operation corresponding to one service request is in one transaction or not can be monitored, and the data consistency can be kept after the abnormal condition occurs.
Description
Technical Field
The application relates to the field of databases, in particular to a method and a system for processing consistency of database service data.
Background
In the process of operating the database, a database operation service needs to be able to rollback, for example, a database is modified multiple times continuously in a database operation service, and when a modification is problematic, the database needs to be rolled back to a state before the modification is performed.
In actual work, the condition that rollback cannot be performed sometimes occurs. The inventor has found that, for the case of non-rollback, the database operation business is generally distributed in different transactions, which results in failure of rollback, and inconsistency of data occurs. However, the prior art does not monitor this situation.
Disclosure of Invention
The embodiment of the application provides a method and a system for processing the running continuity of a database service, so as to solve at least the problem that whether the condition of data inconsistency is caused by the service request of the database is not monitored in the prior art.
According to one aspect of the application, a database service data consistency processing method is provided, which includes: receiving a service request for operating a database, wherein the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target; running the service request; in the process of running the service request, judging whether the service request runs in a transaction, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or not executed and are inseparable working units; and if the service request is determined to be in one transaction, the data consistency can be maintained if an abnormal condition occurs in the execution process of the service request.
Further, still include: if the service request is not in one transaction, judging whether the database operation corresponding to the service request meets a preset triggering condition, and if the database operation corresponding to the service request meets the triggering condition, sending alarm information, wherein the alarm information is used for indicating that data is inconsistent under the condition that the service request is abnormal.
Further, the trigger condition includes: and judging whether the database operation corresponding to the service request is in one session, and if the database operation is not in one session and comprises data change operation, triggering and sending the alarm information.
Further, the trigger condition includes: if automatic submission is set in the connection and a plurality of data change operations exist, triggering and sending the alarm information, wherein the automatic submission is executed once every time, and the database operation corresponding to the automatic submission is completed in one transaction; and triggering and sending the alarm information if the automatic submission is forbidden in the connection, multiple explicit submission COMMIT requests exist in the same service, and at least one COMMIT request contains change operation.
Further, the trigger condition includes: and the database operation corresponding to the service request comprises a change operation, and after the change operation fails, if no rollback operation is initiated, the alarm information is triggered and sent.
According to another aspect of the present application, there is also provided a database service data consistency processing system, including: the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a service request for operating a database, the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target; the operation module is used for operating the service request; the judging module is used for judging whether the service request is operated in a transaction in the process of operating the service request, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or all not executed and are an inseparable working unit; the determining module is used for determining that the business request can keep data consistency if an abnormal condition occurs in the execution process under the condition that the business request is in one transaction.
Further, still include: and the sending module is used for judging whether the database operation corresponding to the service request meets a preset triggering condition or not if the service request is not in one transaction, and sending alarm information if the triggering condition is met, wherein the alarm information is used for indicating that the data is inconsistent under the condition that the service request is abnormal.
Further, the trigger condition includes: and judging whether the database operation corresponding to the service request is in one session, and if the database operation is not in one session and comprises data change operation, triggering and sending the alarm information.
Further, the trigger condition includes: if automatic submission is set in the connection and a plurality of data change operations exist, triggering and sending the alarm information, wherein the automatic submission is executed once every time, and the database operation corresponding to the automatic submission is completed in one transaction; and triggering and sending the alarm information if the automatic submission is forbidden in the connection, multiple explicit submission COMMIT requests exist in the same service, and at least one COMMIT request contains change operation.
Further, the trigger condition includes: and the database operation corresponding to the service request comprises a change operation, and after the change operation fails, if no rollback operation is initiated, the alarm information is triggered and sent.
In the embodiment of the application, a service request for operating a database is received, wherein the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target; running the service request; in the process of running the service request, judging whether the service request runs in a transaction, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or not executed and are inseparable working units; and if the service request is determined to be in one transaction, the data consistency can be maintained if an abnormal condition occurs in the execution process of the service request. The method and the device solve the problem that whether the condition that the data are inconsistent is not monitored due to the fact that whether the service request of the database can cause the data to be inconsistent or not in the prior art, so that whether the database operation corresponding to one service request is in one transaction or not can be monitored, and the data consistency can be kept after the abnormal condition occurs.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the application and, together with the description, serve to explain the application and are not intended to limit the application. In the drawings:
fig. 1 is a flowchart of a database service data consistency processing method according to an embodiment of the present application.
Detailed Description
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
In this embodiment, a method for processing consistency of database service data is provided, and fig. 1 is a flowchart of a method for processing consistency of database service data according to an embodiment of the present application, and as shown in fig. 1, the flowchart includes the following steps:
step S102, receiving a service request for operating a database, wherein the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target;
step S104, operating the service request;
step S106, in the process of operating the service request, judging whether the service request is operated in a transaction, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or all not executed and are an inseparable working unit;
step S108, determining that if an abnormal condition occurs in the execution process of the service request under the condition that the service request is in one transaction, the consistency of data can be maintained.
The method solves the problem caused by the fact that whether the data inconsistency is caused by the service request of the database is not monitored in the prior art, so that whether the database operation corresponding to one service request is in one transaction or not can be monitored, and the data consistency can be kept after the abnormal condition occurs.
Optionally, if the service request is not in one transaction, determining whether a database operation corresponding to the service request meets a pre-configured trigger condition, and if the database operation meets the trigger condition, sending alarm information, where the alarm information is used to indicate that data is inconsistent when the service request is abnormal.
As an optional implementation manner, if the database operations corresponding to the service requests are all query operations, the steps in the above method are not executed, because the query operations do not cause data inconsistency. And if the change operation is included, judging whether the database operation is in one session or not, or judging whether the database operation is in one transaction or not, and if the database operation is not in one session or one transaction, triggering and sending the alarm information.
The trigger condition is exemplified below.
Example 1, the trigger condition may include: and judging whether the database operation corresponding to the service request is in one session, and if the database operation is not in one session and comprises data change operation, triggering and sending the alarm information.
Example 2, the trigger condition may include: if automatic submission is set in the connection and a plurality of data change operations exist, triggering and sending the alarm information, wherein the automatic submission is executed once every time, and the database operation corresponding to the automatic submission is completed in one transaction; and triggering and sending the alarm information if the automatic submission is forbidden in the connection, multiple explicit submission COMMIT requests exist in the same service, and at least one COMMIT request contains change operation.
Example 3, the trigger conditions include: and the database operation corresponding to the service request comprises a change operation, and after the change operation fails, if no rollback operation is initiated, the alarm information is triggered and sent.
As an optional implementation manner, it may also be determined whether the service request is in a preconfigured white list, and if the service request is in the preconfigured white list, the method described above is not performed. In the embodiment, the service in the white list does not need to judge whether the problem of data inconsistency occurs, so that the computing resource is saved.
As an optional implementation manner, the foregoing steps may be applied to a code debugging process, in a code debugging stage, if the service request is not in a transaction, determining whether a database operation corresponding to the service request meets a pre-configured trigger condition, and if the service request meets the trigger condition, generating an interrupt, where the interrupt is used to stop debugging of the code and send an alarm message; or not interrupting the debugging of the code, but recording the position of the running code when the interruption is generated and generating an alarm message.
In this embodiment, an electronic device is provided, comprising a memory in which a computer program is stored and a processor configured to run the computer program to perform the method in the above embodiments.
The programs described above may be run on a processor or stored in memory (or referred to as computer-readable media), which includes both non-transitory and non-transitory, removable and non-removable media, that enable storage of information by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
These computer programs may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks, and corresponding steps may be implemented by different modules.
Such an apparatus or system is provided in this embodiment. The system is called a database business data consistency processing system and comprises: the system comprises a receiving module, a processing module and a sending module, wherein the receiving module is used for receiving a service request for operating a database, the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target; the operation module is used for operating the service request; the judging module is used for judging whether the service request is operated in a transaction in the process of operating the service request, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or all not executed and are an inseparable working unit; the determining module is used for determining that the business request can keep data consistency if an abnormal condition occurs in the execution process under the condition that the business request is in one transaction.
The system or the apparatus is used for implementing the functions of the method in the foregoing embodiments, and each module in the system or the apparatus corresponds to each step in the method, which has been described in the method and is not described herein again.
For example, it also includes: and the sending module is used for judging whether the database operation corresponding to the service request meets the preset triggering condition or not if the service request is not in one transaction, and sending alarm information if the triggering condition is met, wherein the alarm information is used for indicating that the data are inconsistent under the condition that the service request is abnormal.
The embodiment solves the problem caused by the fact that whether the data inconsistency is caused by the service request of the database is not monitored in the prior art, so that whether the database operation corresponding to one service request is in one transaction or not can be monitored, and the data consistency can be kept after the abnormal condition occurs.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for processing consistency of database service data is characterized by comprising the following steps:
receiving a service request for operating a database, wherein the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target;
running the service request;
in the process of running the service request, judging whether the service request runs in a transaction, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or not executed and are inseparable working units;
and if the service request is determined to be in one transaction, the data consistency can be maintained if an abnormal condition occurs in the execution process of the service request.
2. The method of claim 1, further comprising:
if the service request is not in one transaction, judging whether the database operation corresponding to the service request meets a preset triggering condition, and if the database operation corresponding to the service request meets the triggering condition, sending alarm information, wherein the alarm information is used for indicating that data is inconsistent under the condition that the service request is abnormal.
3. The method of claim 2, wherein the trigger condition comprises:
and judging whether the database operation corresponding to the service request is in one session, and if the database operation is not in one session and comprises data change operation, triggering and sending the alarm information.
4. The method of claim 2, wherein the trigger condition comprises:
if automatic submission is set in the connection and a plurality of data change operations exist, triggering and sending the alarm information, wherein the automatic submission is executed once every time, and the database operation corresponding to the automatic submission is completed in one transaction;
and triggering and sending the alarm information if the automatic submission is forbidden in the connection, multiple explicit submission COMMIT requests exist in the same service, and at least one COMMIT request contains change operation.
5. The method of claim 2, wherein the trigger condition comprises:
and the database operation corresponding to the service request comprises a change operation, and after the change operation fails, if no rollback operation is initiated, the alarm information is triggered and sent.
6. A database service data consistency handling system, comprising:
the system comprises a receiving module, a processing module and a sending module, wherein the receiving module is used for receiving a service request for operating a database, the service request corresponds to a database operation service, and the database operation service is used for operating the database to complete a preset operation target;
the operation module is used for operating the service request;
the judging module is used for judging whether the service request is operated in a transaction in the process of operating the service request, wherein the transaction is a database operation sequence for accessing and operating various data items, and the operations in the database operation sequence are either all executed or all not executed and are an inseparable working unit;
the determining module is used for determining that the business request can keep data consistency if an abnormal condition occurs in the execution process under the condition that the business request is in one transaction.
7. The system of claim 6, further comprising:
and the sending module is used for judging whether the database operation corresponding to the service request meets a preset triggering condition or not if the service request is not in one transaction, and sending alarm information if the triggering condition is met, wherein the alarm information is used for indicating that the data is inconsistent under the condition that the service request is abnormal.
8. The system of claim 7, wherein the trigger condition comprises:
and judging whether the database operation corresponding to the service request is in one session, and if the database operation is not in one session and comprises data change operation, triggering and sending the alarm information.
9. The system of claim 7, wherein the trigger condition comprises:
if automatic submission is set in the connection and a plurality of data change operations exist, triggering and sending the alarm information, wherein the automatic submission is executed once every time, and the database operation corresponding to the automatic submission is completed in one transaction;
and triggering and sending the alarm information if the automatic submission is forbidden in the connection, multiple explicit submission COMMIT requests exist in the same service, and at least one COMMIT request contains change operation.
10. The system of claim 7, wherein the trigger condition comprises:
and the database operation corresponding to the service request comprises a change operation, and after the change operation fails, if no rollback operation is initiated, the alarm information is triggered and sent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210418267.7A CN114510495B (en) | 2022-04-21 | 2022-04-21 | Database service data consistency processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210418267.7A CN114510495B (en) | 2022-04-21 | 2022-04-21 | Database service data consistency processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114510495A true CN114510495A (en) | 2022-05-17 |
| CN114510495B CN114510495B (en) | 2022-07-08 |
Family
ID=81555260
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210418267.7A Active CN114510495B (en) | 2022-04-21 | 2022-04-21 | Database service data consistency processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114510495B (en) |
Citations (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040236763A1 (en) * | 2003-05-22 | 2004-11-25 | Microsoft Corporation | System and method for identifying and storing changes made to a table |
| CN101673275A (en) * | 2009-08-11 | 2010-03-17 | 东软集团股份有限公司 | Method and device for ensuring consistent affairs inside database |
| CN102289519A (en) * | 2011-09-14 | 2011-12-21 | 成都软智科技有限公司 | Application server and method for coordinating data of same and database |
| US20120030184A1 (en) * | 2010-07-27 | 2012-02-02 | Sap Ag | Distributed database system utilizing an extended two-phase-commit process |
| US20140046919A1 (en) * | 2007-09-14 | 2014-02-13 | Oracle International Corporation | Support for compensation aware data types in relational database systems |
| US20150149401A1 (en) * | 2013-11-26 | 2015-05-28 | Stephan Kottler | Lock-free generation of columns with minimal dictionaries after parallel aggregation |
| US20150199395A1 (en) * | 2014-01-15 | 2015-07-16 | International Business Machines Corporation | Enabling collaborative development of a database application across multiple database management systems |
| CN104793988A (en) * | 2014-01-20 | 2015-07-22 | 阿里巴巴集团控股有限公司 | Cross-database distributed transaction implementation method and device |
| CN104820698A (en) * | 2015-05-08 | 2015-08-05 | 中国人民解放军61600部队 | Realization method of distributed consistency of data screening rule system |
| CN104915756A (en) * | 2015-05-22 | 2015-09-16 | 电信科学技术第五研究所 | Data consistency cloud auditing system and implementation method |
| CN104933132A (en) * | 2015-06-12 | 2015-09-23 | 广州巨杉软件开发有限公司 | Distributed database weighted voting method based on operating sequence number |
| CN105512137A (en) * | 2014-09-26 | 2016-04-20 | 中国银联股份有限公司 | Method for operating database handle, and database handle management system |
| CN105589961A (en) * | 2015-12-21 | 2016-05-18 | 武汉达梦数据库有限公司 | Method and system for detecting data consistency of real-time synchronous system of database |
| CN105760762A (en) * | 2016-03-10 | 2016-07-13 | 华中科技大学 | Unknown malicious code detection method for embedded processor |
| CN106033439A (en) * | 2015-03-13 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Method and system for processing distributed transaction |
| US20160350357A1 (en) * | 2015-05-29 | 2016-12-01 | Nuodb, Inc. | Disconnected operation within distributed database systems |
| CN106682141A (en) * | 2016-12-20 | 2017-05-17 | 华北计算技术研究所（中国电子科技集团公司第十五研究所） | Data synchronization method based on business operation logs |
| CN107203560A (en) * | 2016-03-18 | 2017-09-26 | 中国移动通信集团宁夏有限公司 | Database, multiple database operation transaction consistency ensuring method and system |
| CN107436799A (en) * | 2016-05-26 | 2017-12-05 | 阿里巴巴集团控股有限公司 | Distributed transaction uniformity implementation method and device |
| CN107644077A (en) * | 2017-09-19 | 2018-01-30 | 杭州贝购科技有限公司 | Data consistency monitoring method, computer equipment and storage medium |
| CN108469987A (en) * | 2018-02-26 | 2018-08-31 | 华东师范大学 | It is a kind of that system is verified based on the interruption for interrupting controlling stream graph |
| CN109189608A (en) * | 2018-08-13 | 2019-01-11 | 武汉达梦数据库有限公司 | A kind of method guaranteeing duplication transaction consistency and corresponding reproducing unit |
| CN109213631A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | A kind of transaction methods, device, equipment and readable storage medium storing program for executing |
| CN109214180A (en) * | 2017-06-30 | 2019-01-15 | 武汉斗鱼网络科技有限公司 | A kind of method of calibration and device of internal storage code |
| CN109388481A (en) * | 2018-09-21 | 2019-02-26 | 网易（杭州）网络有限公司 | A kind of transmission method of transaction information, device, calculates equipment and medium at system |
| CN110032571A (en) * | 2019-04-18 | 2019-07-19 | 腾讯科技（深圳）有限公司 | Business flow processing method, apparatus, storage medium and calculating equipment |
| CN110196759A (en) * | 2018-06-20 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Distributed transaction processing method and device, storage medium and electronic device |
| CN110347576A (en) * | 2018-04-04 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Pseudocode adjustment method and device |
| CN110968448A (en) * | 2019-12-03 | 2020-04-07 | 积成电子股份有限公司 | Method for monitoring multitask running state |
| CN111400085A (en) * | 2020-02-18 | 2020-07-10 | 中国平安人寿保险股份有限公司 | Transaction rollback exception processing method and device, computer equipment and storage medium |
| CN111475583A (en) * | 2020-06-19 | 2020-07-31 | 阿里云计算有限公司 | Transaction processing method and device |
| CN111984388A (en) * | 2020-08-27 | 2020-11-24 | 深圳壹账通智能科技有限公司 | Method, device and medium for coordinating data consistency in distributed transactions of cloud environment |
| CN112162989A (en) * | 2020-09-24 | 2021-01-01 | 北京人大金仓信息技术股份有限公司 | Database data consistency detection method, device, medium and electronic equipment |
| CN112817787A (en) * | 2021-01-28 | 2021-05-18 | 南京大学 | Automatic detection method for data competition of interrupt-driven embedded system |
| CN112988883A (en) * | 2019-12-16 | 2021-06-18 | 中兴通讯股份有限公司 | Database data synchronization method and device and storage medium |
| CN113032176A (en) * | 2021-03-23 | 2021-06-25 | 中国邮政储蓄银行股份有限公司 | Distributed transaction double-compensation method and device based on daily account checking |
| CN113254425A (en) * | 2021-06-24 | 2021-08-13 | 阿里云计算有限公司 | Method, apparatus, system, program and storage medium for database transaction retention |
| CN114281603A (en) * | 2021-12-29 | 2022-04-05 | 中国邮政储蓄银行股份有限公司 | Method and device for sending message corresponding to transaction |
-
2022
- 2022-04-21 CN CN202210418267.7A patent/CN114510495B/en active Active
Patent Citations (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040236763A1 (en) * | 2003-05-22 | 2004-11-25 | Microsoft Corporation | System and method for identifying and storing changes made to a table |
| US20140046919A1 (en) * | 2007-09-14 | 2014-02-13 | Oracle International Corporation | Support for compensation aware data types in relational database systems |
| CN101673275A (en) * | 2009-08-11 | 2010-03-17 | 东软集团股份有限公司 | Method and device for ensuring consistent affairs inside database |
| US20120030184A1 (en) * | 2010-07-27 | 2012-02-02 | Sap Ag | Distributed database system utilizing an extended two-phase-commit process |
| CN102289519A (en) * | 2011-09-14 | 2011-12-21 | 成都软智科技有限公司 | Application server and method for coordinating data of same and database |
| US20150149401A1 (en) * | 2013-11-26 | 2015-05-28 | Stephan Kottler | Lock-free generation of columns with minimal dictionaries after parallel aggregation |
| US20150199395A1 (en) * | 2014-01-15 | 2015-07-16 | International Business Machines Corporation | Enabling collaborative development of a database application across multiple database management systems |
| CN104793988A (en) * | 2014-01-20 | 2015-07-22 | 阿里巴巴集团控股有限公司 | Cross-database distributed transaction implementation method and device |
| CN105512137A (en) * | 2014-09-26 | 2016-04-20 | 中国银联股份有限公司 | Method for operating database handle, and database handle management system |
| CN106033439A (en) * | 2015-03-13 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Method and system for processing distributed transaction |
| CN104820698A (en) * | 2015-05-08 | 2015-08-05 | 中国人民解放军61600部队 | Realization method of distributed consistency of data screening rule system |
| CN104915756A (en) * | 2015-05-22 | 2015-09-16 | 电信科学技术第五研究所 | Data consistency cloud auditing system and implementation method |
| US20160350357A1 (en) * | 2015-05-29 | 2016-12-01 | Nuodb, Inc. | Disconnected operation within distributed database systems |
| CN104933132A (en) * | 2015-06-12 | 2015-09-23 | 广州巨杉软件开发有限公司 | Distributed database weighted voting method based on operating sequence number |
| CN105589961A (en) * | 2015-12-21 | 2016-05-18 | 武汉达梦数据库有限公司 | Method and system for detecting data consistency of real-time synchronous system of database |
| CN105760762A (en) * | 2016-03-10 | 2016-07-13 | 华中科技大学 | Unknown malicious code detection method for embedded processor |
| CN107203560A (en) * | 2016-03-18 | 2017-09-26 | 中国移动通信集团宁夏有限公司 | Database, multiple database operation transaction consistency ensuring method and system |
| CN107436799A (en) * | 2016-05-26 | 2017-12-05 | 阿里巴巴集团控股有限公司 | Distributed transaction uniformity implementation method and device |
| CN106682141A (en) * | 2016-12-20 | 2017-05-17 | 华北计算技术研究所（中国电子科技集团公司第十五研究所） | Data synchronization method based on business operation logs |
| CN109214180A (en) * | 2017-06-30 | 2019-01-15 | 武汉斗鱼网络科技有限公司 | A kind of method of calibration and device of internal storage code |
| CN107644077A (en) * | 2017-09-19 | 2018-01-30 | 杭州贝购科技有限公司 | Data consistency monitoring method, computer equipment and storage medium |
| CN108469987A (en) * | 2018-02-26 | 2018-08-31 | 华东师范大学 | It is a kind of that system is verified based on the interruption for interrupting controlling stream graph |
| CN110347576A (en) * | 2018-04-04 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Pseudocode adjustment method and device |
| CN110196759A (en) * | 2018-06-20 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Distributed transaction processing method and device, storage medium and electronic device |
| CN109189608A (en) * | 2018-08-13 | 2019-01-11 | 武汉达梦数据库有限公司 | A kind of method guaranteeing duplication transaction consistency and corresponding reproducing unit |
| CN109213631A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | A kind of transaction methods, device, equipment and readable storage medium storing program for executing |
| CN109388481A (en) * | 2018-09-21 | 2019-02-26 | 网易（杭州）网络有限公司 | A kind of transmission method of transaction information, device, calculates equipment and medium at system |
| CN110032571A (en) * | 2019-04-18 | 2019-07-19 | 腾讯科技（深圳）有限公司 | Business flow processing method, apparatus, storage medium and calculating equipment |
| CN110968448A (en) * | 2019-12-03 | 2020-04-07 | 积成电子股份有限公司 | Method for monitoring multitask running state |
| CN112988883A (en) * | 2019-12-16 | 2021-06-18 | 中兴通讯股份有限公司 | Database data synchronization method and device and storage medium |
| CN111400085A (en) * | 2020-02-18 | 2020-07-10 | 中国平安人寿保险股份有限公司 | Transaction rollback exception processing method and device, computer equipment and storage medium |
| CN111475583A (en) * | 2020-06-19 | 2020-07-31 | 阿里云计算有限公司 | Transaction processing method and device |
| CN111984388A (en) * | 2020-08-27 | 2020-11-24 | 深圳壹账通智能科技有限公司 | Method, device and medium for coordinating data consistency in distributed transactions of cloud environment |
| CN112162989A (en) * | 2020-09-24 | 2021-01-01 | 北京人大金仓信息技术股份有限公司 | Database data consistency detection method, device, medium and electronic equipment |
| CN112817787A (en) * | 2021-01-28 | 2021-05-18 | 南京大学 | Automatic detection method for data competition of interrupt-driven embedded system |
| CN113032176A (en) * | 2021-03-23 | 2021-06-25 | 中国邮政储蓄银行股份有限公司 | Distributed transaction double-compensation method and device based on daily account checking |
| CN113254425A (en) * | 2021-06-24 | 2021-08-13 | 阿里云计算有限公司 | Method, apparatus, system, program and storage medium for database transaction retention |
| CN114281603A (en) * | 2021-12-29 | 2022-04-05 | 中国邮政储蓄银行股份有限公司 | Method and device for sending message corresponding to transaction |
Non-Patent Citations (1)
| Title |
|---|
| 熊守丽: ""关于异地数据库传输数据一致性检测仿真"", 《计算机仿真》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114510495B (en) | 2022-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10439937B2 (en) | Service addressing in distributed environment | |
| US10509585B2 (en) | Data synchronization method, apparatus, and system | |
| CN106933843B (en) | Database heartbeat detection method and device | |
| US9880897B2 (en) | Failure mode identification and reporting | |
| CN111245897B (en) | Data processing method, device, system, storage medium and processor | |
| CN114443768A (en) | Main/standby switching method and device of distributed database and readable storage medium | |
| CN114510495B (en) | Database service data consistency processing method and system | |
| CN110647463B (en) | Method and device for restoring test breakpoint and electronic equipment | |
| CN108845772B (en) | Hard disk fault processing method, system, equipment and computer storage medium | |
| CN109254880B (en) | Method and device for processing database downtime | |
| CN115729724A (en) | Fault injection method, fault test system, electronic device and readable storage medium | |
| CN108920563B (en) | Database switching method and device | |
| CN114900531B (en) | Data synchronization method, device and system | |
| CN113641424B (en) | Database operation processing method and system | |
| CN112860746B (en) | Cache reduction-based method, equipment and system | |
| CN113961968B (en) | Method and device for carrying out data desensitization interrupt post-processing on file | |
| CN115712685A (en) | Data writing method, device and equipment | |
| CN113703820A (en) | Method and device for hot loading source code, electronic equipment and storage medium | |
| CN116775359A (en) | Fault service alarming method and device, storage medium and electronic device | |
| CN116263725A (en) | Database log backup method and device | |
| CN114721811A (en) | Distributed processing method, system and device | |
| CN117290447A (en) | Inspection method and device of data synchronization system, storage medium and electronic equipment | |
| CN116089219A (en) | Fault monitoring method and device based on kernel, electronic equipment and storage medium | |
| CN116566910A (en) | Method and equipment for detecting state of node | |
| CN113961639A (en) | Distributed transaction processing method, terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |