Sap Se

Reiner Singer

Werner Thesing

Christoph Roterring

Markus Behrens

Michael Muehle

Juchang Lee

Chang Gyoo Park

Kyu Hwan Kim

Beomsoo Kim

Edward-Robert Tyercha

Thomas Theodor Koetter

Thomas Simenec

Omran Saleh

Yue Zhu

Dirk Thomsen

Christoph Weyerhaeuser

Boris Gruschko

Christian Mohr

Martin Strenge

Martin Heidel

Helmut Prestel

Christian Stork

John Smirnios

Kerstin Hoeft

Sebastian Seifert

Marcel Hermanns

Anant Agarwal

Rolf Hammer

Kai Baumgarten

Stefan Voss

Mahendra Chavan

Sigrid K Wortmann

Uwe Hahn

Yu Su

Michael Brombach

Philipp Grosse

Eduard Bartsch

Veit Spaegele

Marcel Birn

Johannes Haeussler

Andreas Gruenhagen

Timo Hochberger

Frank Huber

Christoph Rottering

Thomas Elvers

Junhui Liu

Juan Ge

Jianfeng Yan

Mitja Kleider

Timo Sulg

Mohamed Ali Chriki

Sascha Bastke

Tilman Giese

Various examples are directed to systems and methods for operating a primary database management system and a secondary database management system. The secondary database management system may receive a takeover request indicating that the secondary database management system is to assume a role of the primary database system. The secondary database management system may determine that a last valid commit of a first host of the secondary database system is an oldest last valid commit. The secondary database management system may revert to a first state of the primary database management system corresponding to the last valid commit of the first host. The secondary database management system may be configured to assume the role of the primary database management system.

Database replication with host replication at asynchronously replicated system

A scale-out computing cluster may include a large number of computing servers and storage devices. In order to provide high reliability, the computing cluster must be able to handle failures of individual devices. Reliability of the computing cluster may be improved by providing a standby server for each active server in the computing cluster. If any active server fails, the corresponding standby server is activated. The failed server may be brought back online or replaced, at which time the restored server becomes the standby server for the now-active original standby server. During the restoration period, if any other active server fails, the standby server for that active server is immediately activated. As a result, the recovery ability of the computing cluster is only challenged if both servers of an active/standby pair fail during the restoration period, substantially improving reliability.

Increased replication for managed volumes

A method, a system, and a computer program product for executing a takeover process. A takeover process of a primary computing system by a secondary computing system is triggered. The secondary computing system stores transaction data replicated from the primary computing system. Writing of a redo log of transaction data of one or more transactions into storage by the primary computing system is suspended. The redo log is written by the primary computing system prior to the suspending is transmitted to the secondary computing system. The takeover process of the primary computing system by the secondary computing system is executed upon receiving and persisting the redo log at the secondary computing system.

Replication system takeover with handshake

Disclosed herein are system, method, and computer program product embodiments for coordinated replication of heterogeneous database stores. An embodiment operates by determining a synchronization point based on a commit log of a primary data center. A current log position of each of a plurality of secondary slave servers associated with a secondary master server of a secondary data center is requested. It is determined that the current log position of at least one of the secondary slave servers does not correspond to the logged position of a corresponding primary slave server relative to the synchronization point. An update indicating that the current log position of each of the secondary slave servers corresponds to the logged position of each of the relative corresponding primary slave servers is received. A replay of each of the secondary slave servers up to the synchronization point is initiated.

Coordinated replication of heterogeneous database stores

A computer implemented method is provided comprising receiving a group of transaction logs from a first database, allocating transaction logs from the group of transaction logs to a first queue and to a second queue, generating an end-of-group transaction log indicative of an end of the group of transaction logs, allocating the end-of-group log to the first queue and the second queue; replaying transaction logs from the first queue including the end-of-group transaction log allocated to the first queue, replaying transaction logs from the second queue including the end-of-group transaction log allocated to the second queue; and changing visibility of one or more transactions in response to replaying the end-of-group transaction log allocated to the first queue and the end-of-group transaction log allocated to the second queue. Related apparatus, systems, techniques and articles are also described.

Delayed snapshot isolation for read service at a database

A computer implemented method for monitoring databases includes providing views for monitoring information associated with a first datacenter and proxy views for monitoring information associated with a second datacenter. The first datacenter receives a query for monitoring information and parses the query to identify filter information that identifies which of the first or second datacenter the requested services are running on. If the filter information indicates the service is running on the first datacenter, the first datacenter queries the views to request the monitoring information from the server on the first datacenter running the requested service. If the filter information indicates the service is running on the second datacenter, the first datacenter queries the proxy views to request the monitoring information from the server on the second datacenter running the requested service, and receives the monitoring information. Related apparatus, systems, techniques and articles are also described.

Proxy views for extended monitoring of database systems

A computer implemented method for replication includes registering a first database system with a second database system and performing a failback operation on the first database system. The failback operation includes opening a snapshot that includes data known to have existed on the first database system and the second database system at a first time. Transaction log information is requested from the second database system. The transaction log information corresponds to transactions performed on the second database system beginning with the first time. The transaction log information is applied to the snapshot data on the first database system. Related apparatus, systems, techniques and articles are also described.

Logical equivalent replication with snapshot based fallback of database systems

Testing a database replication system within a multi-container system architecture comprises receiving a first request for creating a database recovery system within a multi-container system architecture. The multi-container system architecture is configured to contain a plurality of tenant databases and a system database, and the database recovery system includes a primary system and a secondary system. The primary system is then identified from the information in the first request. Upon identification, a first tenant database included in the plurality of tenant databases is determined that corresponds to the identified primary system. Upon determining the first tenant database, a second tenant database of the plurality of tenant database is generated that corresponds to the secondary system, and which is enabled to test replicating information that would otherwise be associated with the first tenant database. Related apparatus, systems, techniques and articles are also described.

Testing database replication with multi-container system architecture

Replicating a tenant database includes receiving at a source system a first request from a target system for replicating a first tenant database of the source system, which includes one or more first servers. Characteristics of the one or more first servers are sent to the target system to generate at the target system a second tenant database including one or more second servers. Each second server corresponds to one first server and has the same characteristics as the corresponding first server. Information from each first server is replicated, in an asynchronous mode, to the corresponding second server through a communication channel that is established between each first server and the second server. Upon receiving a second request for stopping the replication, a synchronous mode of processing statements from client applications of the first tenant database is entered. Related apparatus, systems, techniques and articles are described.

Tenant database replication

Recovery of a database system can be initiated by taking the database system offline. Thereafter, recovery operations specified by a redo log of the database system are replayed. During the replaying, updates to pages implicated by the recovery operations are blocked. In parallel, modified pages are flushed to physical disk storage. The database is later brought online after all of the recovery operations are replayed.

Optimized savepoint during database recovery

A new query language can be embedded in a business application programming language (e.g., the ABAP language). A query language consistent with implementations of the current subject matter can be based on a graph data-model of connected business objects (BO) or other data objects and can be designed as an efficient query language embedded into the business application programming language runtime, thereby allowing expression of business logic in a declarative manner.

Advanced business query language

Methods and apparatus, including computer program products, are provided for implementing a cooperative model between an application and a database. In one aspect, there is provided a computer-implemented method. The method may include receiving from an application a command to perform an operation at a database; accessing metadata representative of the application; configuring, based on at least the metadata, a result of the operation; and sending the configured result to shared memory accessible by the application. Related apparatus, systems, methods, and articles are also described.

Cooperative model between an application server and a database

Growing community of inventors

Schriesheim, Germany

Reiner Singer