MANAGING REPLICATION CONFIGURATION AVAILABILITY

• US 20160267161A1
• Filed: 06/06/2016
• Published: 09/15/2016
• Est. Priority Date: 03/11/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cadarette, Paul M., Spyker, James D.
• Granted Patent: US 9,665,635 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

A computer program product for managing replication configurations includes program instructions to receive a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database. The program instructions initialize a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration. The program instructions utilize the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view. The program instructions to, responsive to determining the replication of data is in spec, utilize the target table in the target database to satisfy requesting applications.

Claims

1. A computer program product for managing replication configurations, the computer program product comprising:

one or more non-transitory computer readable tangible storage media and program instructions stored on at least one of the one or more storage media, the program instructions comprising;

program instructions to receive a first replication configuration for replicating data, wherein the first replication configuration defines at least a target table in a target database based on a source table in a source database;

program instructions to determine a latency value, wherein the latency value represents a latency of replicating data from the source database to the target database;

program instructions to, responsive to determining the latency value exceeds a threshold latency value and a portion of the target table in the target database is damaged, determine to utilize a first federated view to satisfy requesting applications;

program instructions to initialize the first federated view, wherein the first federated view is based on at least the source table in the source database as defined in the first replication configuration;

program instructions to utilize the first federated view to satisfy requesting applications, wherein requesting applications obtain data from the first federated view;

program instructions to, responsive to determining the source table matches the target table, utilize the target table in the target database to satisfy requesting applications;

program instructions to, responsive to determining the source table does not match the target table, initialize a second federated view, wherein the second federated view is based on at least the target table in the target database in the first replication configuration;

program instructions to utilize the second federated view to satisfy requesting applications, where requesting applications obtain data from the second federated view;

program instructions to receive a second replication configuration for replicating data, wherein the second replication configuration defines at least a new target table based on the source table;

program instructions to, responsive to determining the target table matches the new target table, utilize the new target table in the target database to satisfy requesting applications;

program instructions to, responsive to determining the target table does not match the new target table, initialize a third federated view, wherein the third federated view is based on at least the new target table in the target database in the second replication configuration; and

program instructions to utilize the third federated view to satisfy requesting applications, where requesting applications obtain data from the third federated view.