International Business Machines Corporation

Globalfoundries Inc.

Einar Lueck

Utz Bacher

Felix O Beier

Thomas Spatzier

Sabine Perathoner-Tschaffler

Stefan Raspl

Dennis Butterstein

Daniel Martin

Angel Nunez Mencias

Reinhard Theodor Buendgen

Dinesh C Verma

Matthias Klein

Sambit Sahu

Christoph Raisch

Namik Hrle

Andreas Brodt

Dinakaran B Joseph

Gerd Breiter

Lap Thiet Huynh

Debanjan Saha

Michael E Baskey

Christian Borntraeger

Dominik Dingel

Nicole Finnie

Sivaram Gottimukkala

Heiko Carstens

Mandis S Beigi

Steffen Rost

Ruediger Maass

Frank Blaschka

Knut Stolze

Michael Man Behrendt

Christian Bolik

Dietmar Noll

Viktor Mihajlovski

Jens Müller

Joachim Hagmeier

Nile Haustein

The present disclosure relates to a computer implemented method for data synchronization in a data analysis system. The data analysis system comprises a source and target database system. The method comprises: receiving a change record describing an operation performed on a data record in the source database system. The change record may be read for determining a value of a distribution key of the data record. The value of the distribution key may be used for selecting a target database node of the target database system where the operation is to be performed. A direct connection may be established to the selected target database node and the change record may be provided to the selected target database node through the direct connection.

Data distribution in data analysis systems

A computer-implemented method for a crash recovery for linked databases may be provided. The linked databases comprise a source and related target database. Selected queries of the source database are transferred to the target database. The method comprises synchronizing selected portions of the source database with tables of an in-memory portion of target database and, storing persistently applied changes to the in-memory target database portion asynchronously and persistently. Upon a database crash of the target database system, the method also comprises restoring, the in-memory target database portion with the latest snapshot available, and applying, changes from the source database recovery log file that have a later timestamp than the latest snapshot available in the persistent target database storage of the in-memory target database portion.

Asynchronous persistency of replicated data changes in a database accelerator

A computer implemented method comprises receiving at least one log record. A type of operation performed in a source database system may be determined based on the log record. Based on the type of operation, an update strategy may be selected from a set of pre-defined update strategies, wherein the update strategy specifies a sequence of replication operations to be performed in order to apply changes described in the at least one log record to a target database system.

Data synchronization in a data analysis system

In an approach to improve online database replication by automating the upgrading of a database replications system online. Additionally, embodiments of the present invention stop an upgrade using a first incremental update strategy on data of a source database, identify an earliest open transaction from a first database to a second database, and identify a last committed log record identifier. Further, embodiments of the present invention execute an adaptive apply strategy on transactions including the earliest open transaction until the last committed log record identifier is reached by the adaptive apply strategy, and resume, by upgrade controller, the upgrade with a second incremental update strategy.

Automated online upgrade of database replication

A computer-implemented method for a crash recovery for linked databases may be provided. The linked databases comprise a source database and a related target database, and selected portions of content of tables of the source database are synchronized with respective portions of the content of the tables of the target database. Thereby, selected queries against a database management system comprising the source database are transferred to a database management system comprising the target database for processing. And the method also comprises synchronizing the portions of the content of the selected tables in the target database with the portions of the content of the selected tables in the source database by reading entries of a recovery log file relating to the source database and applying the read entries to the target database.

Volatile database caching in a database accelerator

The present disclosure relates to a method for data replication in a data analysis system (). A source database system () of the data analysis system () comprises a transaction log () storing log records generated by database transactions. The method comprises in response to determining () that a received log record is generated by a database transaction that rolls back a change of another database transaction whose log records are buffered in at least one record buffer, data indicative of a log record generated by the other database transaction buffering () in the compensation buffer tag data. The tag data may be used () for replicating to a target database system of the data analysis system buffered log records of the record buffer which are not marked as compensation records.

Data replication in a data analysis system

A method comprises receiving a stream of change log records from a source database system; generating change statistics based on a number of pending changes per table partition according to the change log records; estimating, based on performance statistics, a first amount of time for applying the pending changes to a target database system using an incremental update path; estimating, based on the performance statistics, a second amount of time for applying the pending changes to the target database using a bulk update path; dynamically selecting, based on comparison of the first amount of time with the second amount of time, one of the incremental update path and the bulk update path for applying the pending changes to the target database system; and applying the pending changes to the target database system using the selected update path.

Dynamic selection of synchronization update path

Approaches presented herein enable replicating data records between a source database and a target database. More specifically, for a batch of change records in a table received from the source database, a first estimated replication duration needed to apply the batch as a bulk change to the target is determined. For the same batch, a second estimated replication duration needed to apply a set of changes in a single row of the table to the target is determined based on time penalties for each column in the row. A threshold quantity of rows at which the first duration equals a summed total of second durations for the quantity is calculated. The bulk change is selected if a number of rows in the batch exceeds the threshold. Applying change records singly is selected if the number of rows in the batch is less than the threshold.

Dynamic selection of data apply strategy during database replication

A source IT-infrastructure hosts a composite application including multiple functional modules connected to each other via communication links. An abstract pattern includes first nodes and first links representing the functional modules and communication links and lacks resource-related data enabling a deployment engine to instantiate a resource for providing a runtime environment. A target IT-infrastructure has assigned a resource catalog including, for each resource available in the target IT-infrastructure, a specification of the resource's capabilities, and includes second nodes and links, each second node being a representation of one or more of the resources of the target IT-infrastructure and including an indication of the capabilities of one or more resources represented by the second node. The first nodes and links of the abstract pattern are iteratively supplemented by the second nodes and second links.

Deployment management of composite applications

A computer-implemented method for controlling a system is provided. The system includes a source database and a target database. The system can asynchronously replicate data changes of at least one part of the source database to the target database. This asynchronous replication includes evaluating, by a capture engine, a log of the source database for identifying any un-replicated data changes of the at least one part of the source database, transferring the identified data changes to an apply engine, and applying, by the apply engine, the transferred data changes to the target database.

Controlling a multi-database system

The invention relates to computer-implemented method for updating a target table with changes introduced into a source table. New data records are stored into partitions of the source table. An incremental update module copies the new data records from the source table into the target table, thereby assigning a new target partition ID contained within a first value domain to each copied data record. A view specifies a set of visible partition IDs as a union of the first value domain and of a current target partition ID set and allows the execution of database queries selectively on target table partitions having assigned a target partition ID that is element of the visible partition ID set. A batch update module performs an atomic batch update operation that comprises copying partitions of the source table into a respective new partition in the target table.

Updating a table using incremental and batch updates

Operating a node cluster system with a plurality of nodes in a network, wherein the cluster system appears to be a single node with only one specific network address to its network environment. Providing a shared socket database for linking network connection port identifications of a common set of network connection port identifications to the individual nodes, assigning a master function to one of the nodes, sending incoming traffic to all nodes of the cluster system wherein each node verifies its responsibility for this traffic individually, exclusive assignment of a network connection port to the responsible node for the duration of a connection of the corresponding application process by means of the corresponding network connection port identification and the link established by the shared socket database and processing of the traffic by the responsible node or otherwise by the node having the master function.

Method for operating a node cluster system in a network and node cluster system

The present disclosure relates to a method for processing data in a database engine. The method includes storing a first instance of a first table in the database engine in plaintext. Encryption information about encryption methods and encryption keys of at least one predefined column of the first table may be maintained. In response to data changes in the column, first log entries for the data changes may be written in plaintext. The data changes may be encrypted by an encryption component using the encryption information. This results in encrypted data changes. Second log entries for the encrypted data changes may be written and applied to a second instance of the first table. The second instance of the first table is stored at a further database engine.

Data coherency between trusted DBMS and untrusted DBMS

Growing community of inventors

Stuttgart, Germany

Einar Lueck