CN116414848A - Database master-slave copy consistency verification method and device and computer equipment - Google Patents

Database master-slave copy consistency verification method and device and computer equipment Download PDF

Info

Publication number
CN116414848A
CN116414848A CN202310246262.5A CN202310246262A CN116414848A CN 116414848 A CN116414848 A CN 116414848A CN 202310246262 A CN202310246262 A CN 202310246262A CN 116414848 A CN116414848 A CN 116414848A
Authority
CN
China
Prior art keywords
data
data table
database
source
standby
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.)
Pending
Application number
CN202310246262.5A
Other languages
Chinese (zh)
Inventor
闫美阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202310246262.5A priority Critical patent/CN116414848A/en
Publication of CN116414848A publication Critical patent/CN116414848A/en
Pending legal-status Critical Current

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
    • 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/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275—Synchronous replication
    • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/278—Data partitioning, e.g. horizontal or vertical partitioning
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a database master-slave copy consistency verification method, a database master-slave copy consistency verification device, a database slave copy consistency verification computer device, a database master-slave copy consistency verification storage medium and a database master-slave copy consistency verification computer program product, and relates to the technical field of computers, and can be used in the technical field of finance and science or other related fields. The method comprises the following steps: confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database; confirming a source end data table and a destination end data table in the main data table and the standby data table according to the replication direction information between the main site database and the standby site database; creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; and verifying the source end data table and the destination end data table after the data processing operation by referring to the data to obtain a copy consistency verification result between the main data table and the standby data table. By adopting the method, the verification accuracy of the database master-slave copy consistency can be improved.

Description

Database master-slave copy consistency verification method and device and computer equipment
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a database active/standby replication consistency verification method, apparatus, computer device, storage medium, and computer program product.
Background
To meet the business continuity requirements of enterprises and the risk resistance requirements of databases, enterprises generally employ a dual-activity architecture of a primary and a backup site database. In the application process of the primary site database and the backup site database, the situation that the software versions of the primary site database and the backup site database are inconsistent often occurs, so that whether the replication consistency can be ensured between the primary site database and the backup site database needs to be verified.
In general, verification of the primary and backup replication consistency of the primary and backup site databases is achieved by operation and maintenance personnel comparing database reports of the primary site database and the backup site database in the same time period. However, in the application scenario of a large host database, the database involves a large amount of data and is complex in data type; therefore, the conventional verification method based on manual comparison can make the accuracy of the verification result of the database master-slave copy consistency lower.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a database master-slave replication consistency verification method, apparatus, computer device, computer readable storage medium, and computer program product that can improve the accuracy of the verification result.
In a first aspect, the application provides a database master-slave replication consistency verification method. The method comprises the following steps:
confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database;
confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site data database and the standby site data database;
creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and verifying the source data table and the destination data table after data processing operation through the reference data to obtain a replication consistency verification result between the main data table and the standby data table.
In one embodiment, the performing a data processing operation on the data in the source data table according to the reference data in the verification table includes:
identifying data associated with the reference data from the source data table;
Deleting the data associated with the reference data in the source data table to obtain a source data table after data deletion.
In one embodiment, the verifying, by using the reference data, the source data table and the destination data table after the data processing operation to obtain a copy consistency verification result between the primary data table and the backup data table includes:
inquiring the source end data table and the destination end data table after deleting the data according to the data identification of the reference data;
and confirming that the copy consistency verification result between the main data table and the standby data table passes the deletion consistency verification under the condition that the data with the same corresponding data identification as the data identification of the reference data does not exist in the source data table and the destination data table after the data deletion.
In one embodiment, deleting the data associated with the reference data in the source data table, and after obtaining the source data table after deleting the data, further includes:
adding the reference data into the source data table after the data deletion to obtain a source data table after the data addition;
And verifying the source end data table and the destination end data table after the data processing operation through the reference data to obtain a copy consistency verification result between the main data table and the standby data table, and further comprising:
inquiring a source end data table and a destination end data table after the data addition according to the data identification of the reference data;
and confirming that the copy consistency verification result between the main data table and the standby data table passes the addition consistency verification under the condition that the data with the same corresponding data identification as the data identification of the reference data exists in the source data table and the destination data table after the data addition.
In one embodiment, the creating the verification table according to the source data table includes:
obtaining the table structure information of the source data table;
creating an initial verification table according to the table structure information;
and randomly selecting one line of data from the source data table as reference data, and adding the reference data into the initial verification table to obtain the verification table.
In one embodiment, before validating the master data table to be validated in the master site database and validating the backup data table to be validated in the backup site database, the method further comprises:
Confirming a master site database to be verified and a standby site database to be verified according to site information in the consistency verification instruction;
the step of confirming the main data table to be verified in the main site database and the standby data table to be verified in the standby site database comprises the following steps:
confirming a main database partition to be verified in the master site database and a standby database partition to be verified in the standby site database according to the database partition information in the consistency verification instruction;
and according to the data table copying relation information in the consistency verification instruction, confirming the main data table to be verified in the main database partition, and confirming the standby data table to be verified in the standby database partition.
In one embodiment, the identifying, according to the replication direction information between the primary site database and the backup site database, the source data table and the destination data table in the primary data table and the backup data table includes:
under the condition that the copying direction is that the main site database copies to the standby site database, the main data table is confirmed to be the source data table, and the standby data table is confirmed to be the destination data table;
And under the condition that the copying direction is that the backup site database copies to the master site database, the backup data table is confirmed to be the source data table, and the master data table is confirmed to be the destination data table.
In a second aspect, the application also provides a database master-slave copy consistency verification device. The device comprises:
the first confirmation module is used for confirming the main data table to be verified in the main station data database and confirming the standby data table to be verified in the standby station data database;
the second confirming module is used for confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main station data database and the standby station data database;
the data processing module is used for creating a verification table according to the source data table and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and the copy verification module is used for verifying the source data table and the destination data table after the data processing operation through the reference data to obtain a copy consistency verification result between the main data table and the standby data table.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:
confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database;
confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site data database and the standby site data database;
creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and verifying the source data table and the destination data table after data processing operation through the reference data to obtain a replication consistency verification result between the main data table and the standby data table.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
Confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database;
confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site data database and the standby site data database;
creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and verifying the source data table and the destination data table after data processing operation through the reference data to obtain a replication consistency verification result between the main data table and the standby data table.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:
confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database;
confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site data database and the standby site data database;
Creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and verifying the source data table and the destination data table after data processing operation through the reference data to obtain a replication consistency verification result between the main data table and the standby data table.
The database master-slave copy consistency verification method, the device, the computer equipment, the storage medium and the computer program product comprise the steps of firstly, confirming a master data table to be verified in a master site database and confirming a slave data table to be verified in a slave site database; then, according to the copying direction information between the main site database and the standby site database, confirming a source end data table and a destination end data table in the main data table and the standby data table; then, a verification table is established according to the source data table, and data processing operation is carried out on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table; and finally, verifying the source end data table and the destination end data table after the data processing operation by referring to the data, and obtaining a copy consistency verification result between the main data table and the standby data table. According to the verification method based on the process, the data operation is carried out on the source data table through the reference data in the verification table, and then the data consistency verification of the source data table and the destination data table after the data operation is realized. Therefore, on one hand, the data structure and the data content of the data table can be ensured not to be changed in the whole verification process; on the other hand, the whole verification process can be realized based on the uniquely determined reference data, so that the accuracy of the database master-slave copy consistency verification result is improved.
Drawings
FIG. 1 is a flow chart of a method for verifying replication consistency of a database master and slave in one embodiment;
FIG. 2 is a flow chart illustrating the steps for validating a primary data table and a backup data table in one embodiment;
FIG. 3 is a flowchart of a method for verifying replication consistency of a database master and slave in another embodiment;
FIG. 4 is a block diagram illustrating a method and apparatus for verifying master-slave replication consistency of a database in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
It should be noted that, in the present application, the database active-standby replication consistency test refers to a verification process of whether the destination data table can perform synchronous replication when the source data table performs data operation after verification and upgrade in a scenario that the large-scale host performs database software upgrade; for example, after an IBM (International Business Machines Corporation ) mainframe using z/OS as an operating system performs DB2 (relational database management system developed by IBM corporation) software upgrade, it is verified whether the data of the source data table can be synchronized normally with the destination data table.
In an exemplary embodiment, as shown in fig. 1, a database active-standby replication consistency verification method is provided, and the embodiment is illustrated by applying the method to a server; it will be appreciated that the method may also be applied to a terminal, and may also be applied to a system comprising a server and a terminal, and implemented by interaction between the server and the terminal. The server can be realized by an independent server or a server cluster formed by a plurality of servers; the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, etc. In this embodiment, the method includes the steps of:
step S102, confirming a main data table to be verified in a main site database and confirming a standby data table to be verified in a standby site database.
The master site database refers to a local database in the process of the replication consistency test, and the backup site database refers to a remote database in the process of the replication consistency test.
The master site database and the backup site database have a replication relationship, and specifically, the backup site database may perform synchronous replication according to the data change of the master site database, or the master site database may perform synchronous replication according to the data change of the backup site database.
The main data table and the standby data table have an association relationship, for example, the main data table and the standby data table store data of the same client.
The server may be a background server where the master site database is located, or may be a background server independent of the master site database and the slave site database.
Specifically, the server confirms a main data table to be verified corresponding to the consistency verification instruction in the master station data database and confirms a standby data table to be verified corresponding to the consistency verification instruction in the standby station data database according to information carried by the consistency verification instruction.
For example, assume that the information carried in the consistency verification instruction is "master data table 1; the backup data table 10", the server confirms the data table 1 as a master data table to be verified in the master site data database according to the master data table 1, and confirms the data table 10 as a backup data table to be verified in the backup site data database according to the backup data table 10.
Step S104, confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site database and the standby site database.
In practical application, when the master site database takes over the service, the copying direction is copying from the master site database to the slave site database, but when the master site database is abnormal, the slave site database takes over the service, and at the moment, the copying direction is changed to copying from the slave site database to the master site database; that is, the source data table may be in the primary site database or the backup site database, and the destination data table may be in the secondary site database. Therefore, the server needs to confirm the source data table and the destination data table in the main data table and the standby data table according to the copy direction information.
Specifically, the server acquires a data replication record between the main site database and the standby site database in the last period, confirms replication direction information between the main site database and the standby site database according to the data replication record, and confirms which one is the source data table and which is the destination data table in the main data table and the standby data table according to the replication direction information.
Step S106, a verification table is created according to the source data table, and data processing operation is carried out on the data in the source data table according to the reference data in the verification table.
The reference data is any row of data in the source data table.
The data processing operation at least comprises a data deleting operation and a data adding operation.
Specifically, the server creates and obtains a verification table according to the table structure of the source data table, and randomly selects one row of data from the source data table as reference data and adds the reference data into the verification table; and then the server respectively performs data deletion operation and data addition operation on the data in the source data table according to the reference data in the verification table.
And step S108, verifying the source end data table and the destination end data table after the data processing operation by referring to the data to obtain a copy consistency verification result between the main data table and the standby data table.
The server firstly verifies the source data table after the data processing operation, checks whether the data in the source data table is successfully operated, then verifies the destination data table, and checks whether the data in the destination data table is successfully operated synchronously, so that a copy consistency verification result between the main data table and the standby data table is obtained.
For example, the server firstly verifies the source data table after the data deleting operation, checks whether the data in the source data table is successfully deleted, then verifies the destination data table, and checks whether the data in the destination data table is successfully deleted synchronously, thereby obtaining a deleting consistency verification result; then verifying the source end data table after the data adding operation, verifying whether the data in the source end data table is successfully added, then verifying the destination end data table, and checking whether the data in the destination end data table is successfully added synchronously, thereby obtaining an added consistency verification result; and under the condition that the deleting consistency verification result and the adding consistency verification result are both passed, the copy consistency between the main data table and the standby data table is ensured.
In the database master-slave copy consistency verification method, a server firstly confirms a master data table to be verified in a master site database and confirms a slave data table to be verified in a slave site database; then, according to the copying direction information between the main site database and the standby site database, confirming a source end data table and a destination end data table in the main data table and the standby data table; then, a verification table is established according to the source data table, and data processing operation is carried out on the data in the source data table according to the reference data in the verification table; and finally, verifying the source end data table and the destination end data table after the data processing operation by the server through reference data to obtain a replication consistency verification result between the main data table and the standby data table. Based on the verification method in the process, the server performs data operation on the source data table through the reference data in the verification table obtained by the source data table, so that the data consistency in the source data table and the destination data table after the data operation is verified. Therefore, on one hand, the server can ensure that the data structure and the data content of the data table are not changed in the whole verification process; on the other hand, the server can also ensure that the whole verification process is realized based on the uniquely determined reference data, thereby improving the accuracy of the database master-slave copy consistency verification result.
In an exemplary embodiment, the step S106 performs a data processing operation on the data in the source data table according to the reference data in the verification table, and specifically includes the following steps: identifying data associated with the reference data from the source data table; deleting the data associated with the reference data in the source data table to obtain the source data table after the data deletion.
The data associated with the reference data refers to data that matches the data content (i.e., attribute value) of the reference data in the source data table.
Specifically, the server identifies data consistent with the content of the reference data from the source data table as target data; and deleting the target data in the source data table to obtain the source data table after data deletion.
For example, assume that the source data table is used to store student information of a class, and the attribute of the source data table is { number, name, gender, age }; the reference data in the verification table is the data of student Zhang San, and the attribute value thereof is {20180001, zhang San, man, 18}; then the server needs to identify a row of data whose attribute value is {20180001, zhang three, men, 18} from the source data table and delete the row of data from the source data table when performing the data deletion operation.
According to knowledge of the database, the primary key in the data table can be used for uniquely determining the data of each row, so that the server can also confirm the data corresponding to the reference data in the source data table according to the primary key value (i.e. the learning number) of Zhang san as a screening condition, taking the source data table and Zhang san as examples, which store student information.
In this embodiment, by referring to the related information (attribute value or primary key value) of the data, the target data that needs to be deleted can be identified from the source data table, so as to implement accurate deletion of the data in the source data table, and further provide a verification object for subsequent replication consistency verification.
In an exemplary embodiment, step S108 is performed to verify the source data table and the destination data table after the data processing operation by referring to the data, so as to obtain a copy consistency verification result between the primary data table and the backup data table, and specifically includes the following steps: inquiring the source end data table and the destination end data table after deleting the data according to the data identification of the reference data; and under the condition that the data with the same corresponding data identification as the data identification of the reference data does not exist in the source data table and the destination data table after the data is deleted, confirming that the copy consistency verification result between the main data table and the standby data table passes the deletion consistency verification.
The data identifier refers to information capable of uniquely determining a specific row of data in a data table, such as a primary key value or an attribute value of a row of data.
Specifically, taking a primary key value as an example of a data identifier, the server queries the source end data table and the destination end data table after deleting the data according to the primary key value of the reference data; if the data of the source data table and the destination data table after the data deletion do not have the same data as the corresponding primary key value of the reference data, then in step S106, it is stated that the server successfully deletes the data associated with the reference data in the source data table, and the destination data table synchronously completes the deletion operation of the data associated with the reference data according to the data deletion operation, that is, the primary data table and the standby data table can realize the synchronous copy for the data deletion operation, and the server confirms the copy consistency verification result between the primary data table and the standby data table as the verification of the deletion consistency passing.
For example, with the data of the third page as the reference data, the server queries whether the data with the primary key value of 20180001 exists in the source data table and the destination data table after the data deletion, and if the data does not exist, it is stated that the server successfully deletes the data of the third page in the source data table in step S106, and the destination data table successfully synchronizes the data deletion operation.
In this embodiment, the server can ensure the uniqueness of the query results of the source data table and the destination data table after data deletion through the data identifier (the primary key value or the attribute value) of the reference information, so as to realize accurate verification on whether the source data table successfully deletes the data and whether the destination data table successfully deletes the data synchronously.
In an exemplary embodiment, the foregoing step deletes the data associated with the reference data in the source data table, and after obtaining the source data table after the data deletion, specifically further includes the following: and adding the reference data into the source data table after the data deletion to obtain the source data table after the data addition.
Step S108, by referring to the data, verifies the source data table and the destination data table after the data processing operation to obtain a copy consistency verification result between the main data table and the standby data table, and specifically further includes the following contents: inquiring a source end data table and a destination end data table after data addition according to the data identification of the reference data; and under the condition that the data with the same corresponding data identification as the data identification of the reference data exists in the source data table and the destination data table after the data addition, confirming the copy consistency verification result between the main data table and the standby data table as the passing of the addition consistency verification.
Specifically, the server adds the reference data in the verification table into the source data table after data deletion to obtain the source data table after data addition; then, inquiring the source end data table and the destination end data table after the data are added according to the primary key value of the reference data; if the source data table and the destination data table after the data addition have the same data as the corresponding primary key value of the reference data, then in step S106, it is explained that the server successfully adds the reference data into the source data table after the data deletion, and the destination data table synchronously completes the addition operation for the reference data according to the data addition operation, that is, the primary data table and the standby data table can realize the synchronous replication for the data addition operation, and the server confirms the replication consistency verification result between the primary data table and the standby data table as the pass of the addition consistency verification.
For example, taking data of three sheets as reference data, the server queries whether data with a primary key value of 20180001 exists in the source data table after the data addition, if so, it is explained that the server successfully adds data of three sheets into the source data table in step S106, and the destination data table successfully synchronizes the data addition operation.
In this embodiment, the server can ensure the uniqueness of the query results of the source data table and the destination data table after data addition by referring to the data identifier (the primary key value or the attribute value) of the information, so as to realize accurate verification on whether the source data table is successfully added and whether the destination data table is successfully and synchronously added. In addition, in the whole data processing and verification process, the server executes corresponding steps according to the sequence of deletion, verification, addition and verification, so that the data table after verification is completed can be ensured to be consistent with the data table before verification, namely the data of the data table is not changed in the whole process.
In an exemplary embodiment, the step S106 creates a verification table according to the source data table, which specifically includes the following contents: obtaining table structure information of a source data table; creating an initial verification table according to the table structure information; and randomly selecting one line of data from the source data table as reference data, and adding the reference data into the initial verification table to obtain the verification table.
The table structure information of the source data table at least comprises attribute, attribute type, constraint condition, primary key, foreign key, index and other information of the source data table.
Specifically, the server acquires table structure information such as attributes, attribute types, constraint conditions, primary keys, foreign keys, indexes and the like of the source data table, and creates an empty initial verification table according to the table structure information of the source data table; and then the server randomly selects one row of data from the source data table as reference data, and adds the reference data into the initial verification table to obtain the verification table.
For example, assume that the attributes of the source data table include { number, name, gender, age }, and each attribute has its own type, and a primary key of the source data table is defined as the number; the server creates and obtains an initial verification table according to the attribute, the attribute type and the primary key value of the source data table; and then the server randomly selects one row of data from the source data table, and adds the data into the initial verification table to obtain the verification table. At this time, only one piece of data is unique in the verification table, and the data is the reference data.
It should be understood that, since the field type of the database file is different from the field type of the server file, if the data in the database is directly written into the server, the server will default to convert the field types of the fields of the database into character strings, so as to change the structure and content of the data, and then when the data corresponding to the data is queried in the source data table and the destination data table, the situations of false query, missed query, etc. may occur. Therefore, in this embodiment, the server creates the verification table through the table structure information of the source data table and any row of data in the source data table, so that the data structure and the data content of the data table can be ensured not to change in the process of data processing operation; meanwhile, the reference data is selected from the source data table, so that the validity and the accuracy of replication consistency verification are further ensured.
As shown in fig. 2, in an exemplary embodiment, the primary and backup data tables are validated by:
step S202, confirming a master site database to be verified and a backup site database to be verified according to site information in the consistency verification instruction.
Step S204, confirming the main database partition to be verified in the main site database and the standby database partition to be verified in the standby site database according to the database partition information in the consistency verification instruction.
Step S206, according to the data table copying relation information in the consistency verification instruction, confirming the main data table to be verified in the main database partition, and confirming the standby data table to be verified in the standby database partition.
The site information is used for representing the object database for copy consistency verification at the time. The site information at least comprises two site parameters, when the site parameters are empty, the local database is defaulted, and when the site parameters are not zero, the corresponding remote database is confirmed according to the site parameters.
The database partition information is used for representing the service partition to which the object data table for copy consistency verification belongs; in the database, according to the service type corresponding to the data stored in the data table, the database is subjected to partition management, namely, the data in different partitions aim at different types of services; the database partition information may be an identification of each partition. When the database partition information is not empty, the replication consistency verification is performed in the range corresponding to the value, and when the database partition information is empty, the replication consistency verification is performed in all the ranges by default.
The data table is used for representing the characteristics of the data table, such as the table name and the field name of the data table. When the data table copy relation information is not empty, copy consistency verification is performed in the range corresponding to the value, and when the data table copy relation information bit is empty, copy consistency verification is performed in all the ranges by default.
Specifically, the server firstly receives a consistency verification instruction, and identifies site information, database partition information and data table copy relation information from the consistency verification instruction; then, according to site information, confirming a master site database to be verified and a standby site database to be verified from a plurality of databases associated with a server, and carrying out communication connection with the master site database and the standby site database; then, according to the database partition information, confirming a main database partition to be verified in a master site database, and confirming a standby database partition to be verified in a standby site database; then, according to the data table copying relation information, confirming a main data table to be verified in the main database partition, and confirming a standby data table to be verified in the standby database partition; and finally, the server reads the data of the main data table and the standby data table, and performs copy consistency verification on the main data table and the standby data table.
For example, assume that the site information, database partition information, and data table replication relationship information identified by the server from the consistency verification instruction are "{ NULL, location_10}," "174", and "2018-level care professional student information table { number, name, gender, age }"; the server first confirms the local database as the main site database, confirms the remote database 10 as the backup site database, then respectively identifies the corresponding database partition mark as the database partition of 174 in the main site database and the backup site database, finally confirms the data table with the copy relation of '2018-level nursing professional student information table { academic number, name, sex, age }' as the main data table in the main database partition 174 area, and confirms the data table with the copy relation of '2018-level nursing professional student information table { academic number, name, sex, age }' as the backup data table in the backup database partition 174 area.
In this embodiment, the server divides the process of confirming the primary data table and the backup data table into three layers through three information of site information, database partition information and data table copy relationship information, thereby realizing the process of confirming the data tables layer by layer according to the consistency verification instruction.
In an exemplary embodiment, the step S104 includes confirming the source data table and the destination data table in the primary data table and the backup data table according to the replication direction information between the primary site database and the backup site database, and specifically includes the following contents: under the condition that the copying direction is that the master site database copies to the slave site database, the master data table is confirmed to be a source data table, and the slave data table is confirmed to be a target data table; and under the condition that the replication direction is that the backup site database replicates to the master site database, the backup data table is confirmed to be a source data table, and the master data table is confirmed to be a destination data table.
Specifically, the server confirms the replication direction information according to the data replication record between the main site database and the standby site database in the last period, and confirms the source end data table and the destination end data table according to the replication direction information; for example, if the backup site database is synchronized according to the data update of the primary site database in the last period of time, the replication direction is that the primary site database replicates to the backup site database, so that the server confirms the primary data table as the source data table and the backup data table as the destination data table; if the master site database is synchronized according to the data updating of the backup site database in the last period, the replication direction is that the backup site database replicates to the master site database, so that the server confirms the backup data table as a source end data table and confirms the master data table as a destination end data table.
It can be understood that if the replication direction is that the master site database replicates to the backup site database, but the server performs the data processing operation on the data in the backup data table, the master data table cannot be synchronized based on the data processing operation, so that the server is invalid for the verification result of the master data table and the backup data table.
In this embodiment, the server can accurately confirm the source end data table and the destination end data table in the main data table and the standby data table by copying the direction information, thereby ensuring the validity of the subsequent data table verification.
In an exemplary embodiment, the consistency verification instruction is a loop instruction; updating the data table copy relation information in the consistency verification instruction by the server after the completion of the copy consistency verification of the table level through the database information recorded in the server, and verifying the next data table; updating the database partition information in the consistency verification instruction after the replication consistency verification of the partition level is completed, and verifying a data table in the next database partition; after the replication consistency verification of the library level is completed, updating site information in a consistency verification instruction, and verifying a data table in the next database.
It can be appreciated that each time the server completes copy consistency verification of one table, the verification table created during the verification process is deleted, and then the verification table is re-created during the verification process of the next table.
In this embodiment, on the one hand. The server realizes the copy consistency verification of the full data table in the database through the circulating instruction; on the other hand, based on the non-multiplexing of the verification table, the server can realize verification of the data tables with different table structures.
In an exemplary embodiment, as shown in fig. 3, another database master-slave replication consistency verification method is provided, and the method is applied to a server for illustration, and includes the following steps:
step S301, confirming a master site database to be verified and a backup site database to be verified according to site information in the consistency verification instruction.
Step S302, confirming a main database partition to be verified in a main site database and a standby database partition to be verified in a standby site database according to the database partition information in the consistency verification instruction.
Step S303, according to the data table copying relation information in the consistency verification instruction, confirming the main data table to be verified in the main database partition, and confirming the standby data table to be verified in the standby database partition.
Step S304, confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site database and the standby site database.
Step S305, an initial verification table is created according to the table structure information of the source data table, one row of data is arbitrarily selected from the source data table as reference data, and the reference data is added into the initial verification table to obtain the verification table.
In step S306, data associated with the reference data is identified from the source data table.
Step S307, deleting the data associated with the reference data in the source data table to obtain a source data table after data deletion.
Step S308, the source end data table and the destination end data table after deleting the data are queried according to the data identification of the reference data.
Step S309, when there is no data with the same data identification as the data identification of the reference data in the source data table and the destination data table after the data deletion, confirming that the copy consistency verification result between the main data table and the standby data table is the passing of the deletion consistency verification.
Step S310, adding the reference data into the source data table after data deletion to obtain the source data table after data addition.
Step S311, according to the data identification of the reference data, the source data table and the destination data table after the data addition are queried.
In step S312, when the data with the same data identifier as the data identifier of the reference data exists in the source data table and the destination data table after the data addition, the copy consistency verification result between the main data table and the standby data table is confirmed to pass the addition consistency verification.
In this embodiment, on the one hand, the server can ensure the uniqueness of the query results of the source end data table and the destination end data table after data addition through the data identification of the reference information, so as to realize accurate verification on whether the source end data table is successfully added and whether the destination end data table is successfully and synchronously added; on the other hand, in the whole data processing and verifying process, the server executes corresponding steps according to the sequence of deleting, verifying, adding and verifying, so that the data table after the verification is completed can be ensured to be consistent with the data table before the verification, namely the data in the data table cannot be changed in the whole process. In addition, the server creates a verification table through the table structure information of the source data table and any row of data in the source data table, so that the structure and the content of the database data can be ensured not to change in the process of data processing operation; meanwhile, the reference data is selected from the source data table, so that the validity and the accuracy of replication consistency verification are further ensured. It should be noted that the server divides the process of confirming the primary data table and the backup data table into three layers through three information of site information, database partition information and data table replication relation information, so that the process of confirming the data tables layer by layer according to the consistency verification instruction is realized.
In order to more clearly illustrate the database master-slave copy consistency verification method provided by the embodiment of the present application, a specific embodiment is used to specifically describe the database master-slave copy consistency verification method. In an exemplary embodiment, the present application further provides a method for verifying master-slave replication integrity of a mainframe database, which specifically includes the following steps:
step 1: the server acquires a consistency verification instruction and connects the main site database and the standby site database according to the site parameters in the consistency verification instruction.
Step 2: and the server confirms the main database partition verified at the time in the master site database and confirms the standby database partition verified at the time in the standby site database according to the service range in the consistency verification instruction.
Step 3: the server confirms the main data table in the main database partition and confirms the standby data table in the standby database partition according to the replication relation in the consistency verification instruction; and identifying a source end data table and a destination end data table from the main data table and the standby data table, and reading the corresponding source end data table and destination end data table.
Step 4: and the server creates a verification table according to the table structure of the source data table, and randomly takes out one row of data from the source data table and inserts the data into the verification table.
Step 5: and the server takes the primary key value of the verification table as a screening condition, and deletes one row of data meeting the condition in the source data table.
Step 6: the server takes the main key value of the verification table as a screening condition, checks whether the row of data exists in the source data table, and if so, indicates that the source data table fails to delete the data; if the data is not present, checking whether the line of data is present in the data table of the destination end by taking the primary key value of the verification table as a screening condition, if the data is present, indicating that the synchronous deleting operation of the data table of the destination end fails, and if the data is not present, indicating that the synchronous deleting operation of the data table of the destination end succeeds.
Step 7: after the deleting operation is successful in synchronization, the server grabs the data in the verification table and inserts the data into the source data table.
Step 8: the server takes the main key value of the verification table as a screening condition, checks whether the row of data exists in the source data table, and if the row of data does not exist, the deletion and insertion failure of the source data table is indicated; if so, checking whether the line of data exists in the destination data table by taking the primary key value of the verification table as a screening condition, if not, indicating that the synchronous inserting operation of the destination data table fails, and if so, indicating that the synchronous inserting operation of the destination data table is successful.
Step 9: the server deletes the temporary table, updates the information in the consistency verification instruction, and repeats steps 1-9.
In the embodiment, the server uses the verification table as a data deleting and inserting operation bridge, so that on one hand, the resource consumption is reduced; on the other hand, the field types of the original table are completely reserved, so that the data table can be conveniently and efficiently and simply validated. In addition, the verification table is used as a verification medium and is also a backup table, when the consistency of deleting operation is verified, the source table data can be backed up, but if an intermediate medium is not adopted, the line of data in the source data table is lost; in addition, when the insertion operation is performed, the data in the verification table can be directly used as the insertion content. Therefore, based on the steps, effective and accurate master-slave copy consistency verification can be realized on the premise of not damaging the data table structure, the field types and the data content of the source data table.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a database master-slave copy consistency verification device for realizing the above related database master-slave copy consistency verification method. The implementation scheme of the solution to the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitation in the embodiments of the database master-slave copy consistency verification device or devices provided below may refer to the limitation of the database master-slave copy consistency verification method hereinabove, and will not be repeated herein.
In an exemplary embodiment, as shown in fig. 4, there is provided a database master-slave replication consistency verification apparatus, including: a first validation module 402, a second validation module 404, a data processing module 406, and a replication verification module 408, wherein:
the first confirmation module 402 is configured to confirm the master data table to be verified in the master site database, and confirm the backup data table to be verified in the backup site database.
And the second confirmation module 404 is configured to confirm the source data table and the destination data table in the primary data table and the backup data table according to the replication direction information between the primary site database and the backup site database.
The data processing module 406 is configured to create a verification table according to the source data table, and perform a data processing operation on data in the source data table according to reference data in the verification table; the reference data is any row of data in the source data table.
The copy verification module 408 is configured to verify the source data table and the destination data table after the data processing operation by referring to the data, so as to obtain a copy consistency verification result between the main data table and the standby data table.
In an exemplary embodiment, the data processing module 406 is further configured to identify data associated with the reference data from the source data table; deleting the data associated with the reference data in the source data table to obtain the source data table after the data deletion.
In an exemplary embodiment, the copy verification module 408 is further configured to query the source data table and the destination data table after deleting the data according to the data identifier of the reference data; and under the condition that the data with the same corresponding data identification as the data identification of the reference data does not exist in the source data table and the destination data table after the data is deleted, confirming that the copy consistency verification result between the main data table and the standby data table passes the deletion consistency verification.
In an exemplary embodiment, the data processing module 406 is further configured to add the reference data to the source data table after the data deletion, to obtain the source data table after the data addition.
The copy verification module 408 is further configured to query the source data table and the destination data table after the data addition according to the data identifier of the reference data; and under the condition that the data with the same corresponding data identification as the data identification of the reference data exists in the source data table and the destination data table after the data addition, confirming the copy consistency verification result between the main data table and the standby data table as the passing of the addition consistency verification.
In an exemplary embodiment, the data processing module 406 is further configured to obtain table structure information of the source data table; creating an initial verification table according to the table structure information; and randomly selecting one line of data from the source data table as reference data, and adding the reference data into the initial verification table to obtain the verification table.
In an exemplary embodiment, the first confirmation module 402 is further configured to confirm the master site database to be verified and the backup site database to be verified according to the site information in the consistency verification instruction; confirming a main database partition to be verified in a master site database and a standby database partition to be verified in a standby site database according to the database partition information in the consistency verification instruction; and according to the data table copying relation information in the consistency verification instruction, confirming the main data table to be verified in the main database partition, and confirming the standby data table to be verified in the standby database partition.
In an exemplary embodiment, the second confirmation module 404 is further configured to confirm the primary data table as a source data table and the backup data table as a destination data table when the replication direction is that the primary site database replicates to the backup site database; and under the condition that the replication direction is that the backup site database replicates to the master site database, the backup data table is confirmed to be a source data table, and the master data table is confirmed to be a destination data table.
All or part of each module in the database master-slave copy consistency verification device can be realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In an exemplary embodiment, a computer device is provided, which may be a server, and an internal structure thereof may be as shown in fig. 5. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a database master-slave replication consistency verification method.
It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In an exemplary embodiment, a computer device is also provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.
In an exemplary embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method embodiments described above.
In an exemplary embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims (11)

1. A database master-slave replication consistency verification method, the method comprising:
confirming a main data table to be verified in a main site database, and confirming a standby data table to be verified in a standby site database;
confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main site data database and the standby site data database;
Creating a verification table according to the source data table, and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and verifying the source data table and the destination data table after data processing operation through the reference data to obtain a replication consistency verification result between the main data table and the standby data table.
2. The method of claim 1, wherein the performing a data processing operation on the data in the source data table according to the reference data in the verification table comprises:
identifying data associated with the reference data from the source data table;
deleting the data associated with the reference data in the source data table to obtain a source data table after data deletion.
3. The method according to claim 2, wherein verifying the source data table and the destination data table after the data processing operation by the reference data, to obtain a copy consistency verification result between the primary data table and the backup data table, includes:
Inquiring the source end data table and the destination end data table after deleting the data according to the data identification of the reference data;
and confirming that the copy consistency verification result between the main data table and the standby data table passes the deletion consistency verification under the condition that the data with the same corresponding data identification as the data identification of the reference data does not exist in the source data table and the destination data table after the data deletion.
4. The method of claim 2, wherein deleting the data associated with the reference data in the source data table, after obtaining the source data table with the deleted data, further comprises:
adding the reference data into the source data table after the data deletion to obtain a source data table after the data addition;
and verifying the source end data table and the destination end data table after the data processing operation through the reference data to obtain a copy consistency verification result between the main data table and the standby data table, and further comprising:
inquiring a source end data table and a destination end data table after the data addition according to the data identification of the reference data;
And confirming that the copy consistency verification result between the main data table and the standby data table passes the addition consistency verification under the condition that the data with the same corresponding data identification as the data identification of the reference data exists in the source data table and the destination data table after the data addition.
5. The method of claim 1, wherein said creating a validation table from said source data table comprises:
obtaining the table structure information of the source data table;
creating an initial verification table according to the table structure information;
and randomly selecting one line of data from the source data table as reference data, and adding the reference data into the initial verification table to obtain the verification table.
6. The method of claim 1, wherein validating the master data table to be validated in the master site database and validating the backup data table to be validated in the backup site database further comprises:
confirming a master site database to be verified and a standby site database to be verified according to site information in the consistency verification instruction;
the step of confirming the main data table to be verified in the main site database and the standby data table to be verified in the standby site database comprises the following steps:
Confirming a main database partition to be verified in the master site database and a standby database partition to be verified in the standby site database according to the database partition information in the consistency verification instruction;
and according to the data table copying relation information in the consistency verification instruction, confirming the main data table to be verified in the main database partition, and confirming the standby data table to be verified in the standby database partition.
7. The method according to any one of claims 1 to 6, wherein said identifying a source data table and a destination data table in the primary data table and the backup data table according to the replication direction information between the primary site database and the backup site database comprises:
under the condition that the copying direction is that the main site database copies to the standby site database, the main data table is confirmed to be the source data table, and the standby data table is confirmed to be the destination data table;
and under the condition that the copying direction is that the backup site database copies to the master site database, the backup data table is confirmed to be the source data table, and the master data table is confirmed to be the destination data table.
8. A database master-slave replication consistency verification apparatus, the apparatus comprising:
the first confirmation module is used for confirming the main data table to be verified in the main station data database and confirming the standby data table to be verified in the standby station data database;
the second confirming module is used for confirming a source end data table and a destination end data table in the main data table and the standby data table according to the copying direction information between the main station data database and the standby station data database;
the data processing module is used for creating a verification table according to the source data table and performing data processing operation on the data in the source data table according to the reference data in the verification table; the reference data is any row of data in the source data table;
and the copy verification module is used for verifying the source data table and the destination data table after the data processing operation through the reference data to obtain a copy consistency verification result between the main data table and the standby data table.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
CN202310246262.5A 2023-03-06 2023-03-06 Database master-slave copy consistency verification method and device and computer equipment Pending CN116414848A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310246262.5A CN116414848A (en) 2023-03-06 2023-03-06 Database master-slave copy consistency verification method and device and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310246262.5A CN116414848A (en) 2023-03-06 2023-03-06 Database master-slave copy consistency verification method and device and computer equipment

Publications (1)

Publication Number Publication Date
CN116414848A true CN116414848A (en) 2023-07-11

Family

ID=87052413

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310246262.5A Pending CN116414848A (en) 2023-03-06 2023-03-06 Database master-slave copy consistency verification method and device and computer equipment

Country Status (1)

Country Link
CN (1) CN116414848A (en)

Similar Documents

Publication Publication Date Title
US11429641B2 (en) Copying data changes to a target database
CN109906448B (en) Method, apparatus, and medium for facilitating operations on pluggable databases
CN108369601B (en) Promoting attributes in relational structured data
US10754854B2 (en) Consistent query of local indexes
US8762337B2 (en) Storage replication systems and methods
US9020916B2 (en) Database server apparatus, method for updating database, and recording medium for database update program
CN105574187B (en) A kind of Heterogeneous Database Replication transaction consistency support method and system
US20120203745A1 (en) System and method for range search over distributive storage systems
CN107209704A (en) Detect the write-in lost
US11314717B1 (en) Scalable architecture for propagating updates to replicated data
CN108431807B (en) Replication of structured data records in partitioned data storage spaces
US20180276269A1 (en) Transaction processing in distributed database management system
CN102323930B (en) Mirroring data changes in a database system
CN105550306A (en) Multi-copy data reading/writing method and system
CN109902127B (en) Historical state data processing method and device, computer equipment and storage medium
US20160139980A1 (en) Erasure-coding extents in an append-only storage system
CN111930850A (en) Data verification method and device, computer equipment and storage medium
CN116134420A (en) Using multiple blockchains to apply transactions to a set of persistent data objects in a persistent storage system
US20230267103A1 (en) Database Schema Branching Workflow, with Support for Data, Keyspaces and VSchemas
CN116303789A (en) Parallel synchronization method and device for multi-fragment multi-copy database and readable medium
JP2011522337A (en) Method of synchronizing software modules of computer system distributed to server cluster, application to synchronization system and data storage
CN114661818B (en) Method, system, and medium for real-time synchronization of data between clusters in a graph database
CN116414848A (en) Database master-slave copy consistency verification method and device and computer equipment
CN115495620A (en) Data management method based on graph structure and related equipment
US10628399B2 (en) Storing data in a dispersed storage network with consistency

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