Abstract: A computing system performs real-time replication of database management system transactions. The computing system includes a source DBMS, a replication service and a data lakehouse. The source DBMS stores at least one source transaction table recording at least one source transaction and generates at least one recovery log indicating at least one modification in the at least one source transaction table. The replication service replicates the at least one source transaction recorded in the at least one source transaction table by generating at least one data file having a first data format. The data lakehouse stores at least one lakehouse table corresponding to the at least one source transaction table and having a second data format different from the first data format, and to modify the at least one lakehouse table based on the at least one data file.

Abstract: A computing system performs real-time replication of database management system transactions. The computing system includes a source DBMS, a replication service and a data lakehouse. The source DBMS stores at least one source transaction table recording at least one source transaction and generates at least one recovery log indicating at least one modification in the at least one source transaction table. The replication service replicates the at least one source transaction recorded in the at least one source transaction table by generating at least one data file having a first data format. The data lakehouse stores at least one lakehouse table corresponding to the at least one source transaction table and having a second data format different from the first data format, and to modify the at least one lakehouse table based on the at least one data file.

Abstract: A method, system and computer program product is provided. The method includes identifying a large statement, writing rows that are changed by the large statement into a set of files outside a database management system recovery log, and writing log records for the set of files to the database management system recovery log, such that the log records provide ordering of row changes made by the large statement. The log records include a log sequence number corresponding to a first row changed and a format and encoding used for the row changes. The method further includes streaming, by the one or more processors of the computer system, the set of files out-of-band by a replication capture process to a target database management system.

Abstract: Transaction consistency query support is available for replicated data from recovery log to external data stores. An external data store is populated with records using entries of a change data table. The change data table has entries for each transaction that has committed and is to be replicated, and each of the entries stores information for each log entry in a recovery log from a database management system. Each log entry identifies a transactional change of data and a transaction completion indicator of one of commit and abort. In response to receiving a query about a transaction of the transactions, a set of records are retrieved from the external data store for the transaction. From the set of records, records whose sequence identifier values are larger than a maximum transaction commit sequence identifier are removed. From the set of records, remaining records having transaction consistency are returned.

Abstract: Transaction consistency query support is available for replicated data from recovery log to external data stores. An external data store is populated with records using entries of a change data table. The change data table has entries for each transaction that has committed and is to be replicated, and each of the entries stores information for each log entry in a recovery log from a database management system. Each log entry identifies a transactional change of data and a transaction completion indicator of one of commit and abort. In response to receiving a query about a transaction of the transactions, a set of records are retrieved from the external data store for the transaction. From the set of records, records whose sequence identifier values are larger than a maximum transaction commit sequence identifier are removed. From the set of records, remaining records having transaction consistency are returned.

Abstract: A method, system and computer program product is provided. The method includes identifying a large statement, writing rows that are changed by the large statement into a set of files outside a database management system recovery log, and writing log records for the set of files to the database management system recovery log, such that the log records provide ordering of row changes made by the large statement. The log records include a log sequence number corresponding to a first row changed and a format and encoding used for the row changes. The method further includes streaming, by the one or more processors of the computer system, the set of files out-of-band by a replication capture process to a target database management system.

Abstract: A method, system and computer program product is provided. The method includes identifying a large statement, writing the rows that are changed by the large statement into a set of files outside a database management system recovery log, and writing log records for the set of files to the database management system recovery log, such that the log records provide ordering of row changes made by the large statement. The log records include a log sequence number corresponding to a first row changed and a format and encoding used for the row changes. The method further includes streaming, by the one or more processors of the computer system, the set of files out-of-band by a replication capture process to a target database management system.

Abstract: A system for maintaining a two-site configuration for continuous availability over long distances may include a first computing site configured to execute a first instance associated with a priority workload, the first instance being designated as an active instance; a second computing site configured to execute a second instance of the priority workload, the second instance being designated as a standby instance; a software replication module configured to replicate a unit of work data associated with the priority workload from a first data object associated with the active instance to a second data object associated with the standby instance, and a hardware replication module configured to replicate an image from a first storage volume to a copy on a second storage volume, wherein the first storage volume is associated with the first computing site, and the second storage volume is associated with a third computing site.

Abstract: Systems for replication group partitioning include a workload profiling module configured to analyze historical workload data for a plurality of data elements to identify and categorize one or more transaction patterns; and a recommendation module configured to generate a recommended partitioning of the plurality of data elements into one or more replication groups, based on the one or more transaction patterns, that are optimized toward a partitioning goal.

Abstract: Methods and systems for replication group partitioning include analyzing historical workload data for a plurality of data elements to generate one or more transaction patterns and generating a recommended partitioning of the plurality of data elements into one or more replication groups, based on the one or more transaction patterns, that are optimized toward a partitioning goal.

Abstract: A method includes reading, by a capture engine, log data. The log data can be synchronously hardware-replicated. The log data reflects that an update was started for a database of a first site. The capture engine corresponds to a capture engine of a second site. The method also includes identifying, by the capture engine, the update. The method also includes determining whether the update was committed to the database of the first site. The method also includes replicating, by an apply engine, the update to a database of the second site based on the determining. The update is replicated to the database of the second site based on a determination that the update was committed to the database of the first site. The committed update corresponds to a consistent replication of updates across two or more databases that reside in multiple database management systems.

Abstract: Aspects of the invention include a continuous availability for workload and site switches with no data loss at unlimited distances in an active-active sites configuration. A non-limiting example computer-implemented method includes synchronously replicating commit records of changed workload data, by a processor, from an active site to a bunker site upon a workload data commit. The method asynchronously replicates committed transactions on changed workload data, by the processor, from the bunker site to a recovery site.

Abstract: A method for verifying data consistency between update-in-place data structures and append-only data structures containing change histories associated with the update-in-place data structures is provided. The method includes loading data from an update-in-place data structure to a first set of hash buckets in a processing platform, loading data from append-only data structures to a second set of hash buckets in the processing platform, performing a bucket-level comparison between the data in the first set of hash buckets and the data in the second set of has buckets, and generating a report based on the bucket-level comparison.

Abstract: Several replication subscriptions are defined for a table in a database management system. The table is divided into partitions. Each replication subscription replicates transactions to a range of partitions. Subscriptions are assignable to different consistency groups. Transaction consistency is preserved at the consistency group level. A persistent delay table is created for each of several apply functions. Each apply function processes replication subscriptions for one consistency group, to replicate the table to a target table in parallel. Transactions for a given range of a partition are executed in parallel. When an apply function upon a row of the target table results in an error, the row is stored in the delay table. Application of each row in the delay table is repeatedly retried, and if successful, the row is removed from the delay table.

Abstract: A method, system and computer program product is provided. The method includes identifying a large statement, writing the rows that are changed by the large statement into a set of files outside a database management system recovery log, and writing log records for the set of files to the database management system recovery log, such that the log records provide ordering of row changes made by the large statement. The log records include a log sequence number corresponding to a first row changed and a format and encoding used for the row changes. The method further includes streaming, by the one or more processors of the computer system, the set of files out-of-band by a replication capture process to a target database management system.

Abstract: A system for maintaining a two-site configuration for continuous availability over long distances may include a first computing site configured to execute a first instance associated with a priority workload, the first instance being designated as an active instance; a second computing site configured to execute a second instance of the priority workload, the second instance being designated as a standby instance; a software replication module configured to replicate a unit of work data associated with the priority workload from a first data object associated with the active instance to a second data object associated with the standby instance, and a hardware replication module configured to replicate an image from a first storage volume to a copy on a second storage volume, wherein the first storage volume is associated with the first computing site, and the second storage volume is associated with a third computing site.

Abstract: A method for resynchronizing at least one batch job is provided. The method may include detecting a type of region switch request. The method may further include stopping execution workloads on a primary system based on the switch request. The method may further include suspending software and hardware data replication from the primary system to the secondary system. The method may further utilizing proxy replication engine to determine a point-in-time (PIT) at which the execution is stopped and the suspension. The method may also include switching the replication of the software and hardware data to occur the secondary system to the primary system. The method may further include synchronizing the software and hardware data up to the determined point-in-time (PIT). The method may also include activating the execution of the plurality of workloads on the secondary system based on the determined point-in-time (PIT), switching, and synchronizing.

Abstract: A system for providing continuous availability comprises a second computing site that is geographically remote from a first computing site. The second computing site comprises a storage unit configured to store units of work data and data synchronously replicated from the first computing site. The second computing site further comprises a group of workloads configured to process the units of work data asynchronously replicated from the first computing site. The second computing site further comprises a software replication module configured not to replicate any data while the first computing site is available.

Abstract: A system for providing continuous availability comprises a second computing site that is geographically remote from a first computing site. The second computing site comprises a storage unit configured to store units of work data and data synchronously replicated from the first computing site. The second computing site further comprises a group of workloads configured to process the units of work data asynchronously replicated from the first computing site. The second computing site further comprises a software replication module configured not to replicate any data while the first computing site is available.

Abstract: A method includes reading, by a capture engine, log data. The log data can be synchronously hardware-replicated. The log data reflects that an update was started for a database of a first site. The capture engine corresponds to a capture engine of a second site. The method also includes identifying, by the capture engine, the update. The method also includes determining whether the update was committed to the database of the first site. The method also includes replicating, by an apply engine, the update to a database of the second site based on the determining. The update is replicated to the database of the second site based on a determination that the update was committed to the database of the first site. The committed update corresponds to a consistent replication of updates across two or more databases that reside in multiple database management systems.