Service outage time reduction for a planned event in a system

Patent metadata

Field	Value
Publication number	US-10599636-B2
Application number	US-201715825731-A
Country	US
Kind code	B2
Filing date	Nov 29, 2017
Priority date	May 23, 2017
Publication date	Mar 24, 2020
Grant date	Mar 24, 2020

Abstract

A method, computer program product, and a computer system, to store information related to changed data in response to a transaction with a first database of the on-line system requested during a planned period and data in the first database changed by the transaction. In response to a planned event a back-up system with a second database is switched to set up a new connection and a new transaction with the second database, wherein the second database is backup of the first database. The on-line system prevents setting up a new connection to the on-line system and prevents conducting a new transaction with the first database, sends information related to the changed data from the on-line system to the back-up system, and switches to the back-up system for a new connection and for a new transaction. The on-line system synchronizes data between the first database and the second database.

First claim

What is claimed is:

1. A computer system comprising:
one or more computer processors, one or more computer-readable storage media, and program instructions stored on the one or more computer-readable storage media for execution by at least one of the one or more processors, the program instructions comprising:
program instructions to store, by an on-line system, information related to changed data in response to an existing transaction with a first database of the on-line system being conducted during a planned period, and data in the first database being changed by the transaction, wherein information related to the changed data comprises an identification code of the transaction with the first database, wherein the planned period is a time period before a planned event, wherein the time period comprises an average time for data synchronization between the first database and a second database of a back-up system plus an additional length of time;
in response to program instructions to execute the planned event occurring in which program instructions to switch on a back-up system with the second database for program instructions to set up a new connection and a new transaction, wherein the second database is a backup of the first database,
program instructions to prevent, by the on-line system, a new connection to the on-line system and program instructions to cancel an existing transaction with the first database during the planned period, and
program instructions to send, by the on-line system, the information related to the changed data to the back-up system;

program instructions to commit, by the back-up system, the new transaction with the second database in the back-up system, in response to the new transaction being not related to addresses of the changed data according to the information related to the changed data;
program instructions to route to the back-up system a new connection and a new transaction with the second database; and
program instructions to synchronize, by the on-line system, data between the first database and the second database.

2. The computer system according to claim 1 , wherein the planned event occurs at time T, and program instructions to synchronize data between the first database and the second database costs maximum time period t, the planned period is time period between time T-t and time T.

3. The computer system according to claim 1 , further comprising:
program instructions to reject, by the back-up system, the new transaction with the second database in the back-up system, in response to the new transaction being related to the changed data according to the information related to the changed data and the data synchronization between the first database and the second database not being complete.

4. The computer system according to claim 1 , further comprising:
program instructions to hold, by the back-up system, the new transaction with the second database until the program instructions to synchronize data between the first database and the second database is completed, in response to the new transaction being related to the changed data according to the information related to the changed data and data size of the data synchronization between the first database and the second database being below a threshold; and
program instructions to reject, by the back-up system, the new transaction with the second database, in response to the new transaction being related to the changed data according to the information related to the changed data and the data size of the data synchronization between the first database and the second database being greater than the threshold.

5. The computer system according to claim 1 , further comprising:
program instructions to commit, by the back-up system, the new transaction with the second database in the back-up system in response to the program instructions to synchronize data between the first database and the second database being complete.

6. The computer system according to claim 1 , wherein the information related to the changed data comprises at least one table name and at least one row number of the changed data location in the first database.

7. A computer program product comprising:
one or more computer-readable storage media and program instructions stored on the one or more computer-readable storage media, the program instructions comprising:
program instructions to store, by an on-line system, information related to changed data in response to an existing transaction with a first database of the on-line system being conducted during a planned period, and data in the first database being changed by the transaction, wherein information related to the changed data comprises an identification code of the transaction with the first database, wherein the planned period is a time period before a planned event, wherein the time period comprises an average time for data synchronization between the first database and a second database of a back-up system plus an additional length of time;
in response program instructions to execute the planned event occurring in which program instructions to switch on the back-up system with a second database for program instructions to set up a new connection and a new transaction, wherein the second database is a backup of the first database,
program instructions to prevent, by the on-line system, a new connection to the on-line system and program instructions to cancel an existing transaction with the first database during the planned period, and
program instructions to send, by the on-line system, the information related to the changed data to the back-up system;

program instructions to commit, by the back-up system, the new transaction with the second database in the back-up system, in response to the new transaction being not related to addresses of the changed data according to the information related to the changed data;
program instructions to route to the back-up system a new connection and a new transaction with the second database; and
program instructions to synchronize, by the on-line system, data between the first database and the second database.

8. The computer program product according to claim 7 , wherein the planned event occurs at time T, and program instructions to synchronize data between the first database and the second database costs maximum time period t, the planned period is time period between time T-t and time T.

9. The computer program product according to claim 7 , further comprising:
program instructions to reject, by the back-up system, the new transaction with the second database in the back-up system, in response to the new transaction being related to the changed data according to the information related to the changed data and the data synchronization between the first database and the second database not being complete.

10. The computer program product according to claim 7 , further comprising:
program instructions to hold, by the back-up system, the new transaction with the second database until the program instructions to synchronize data between the first database and the second database is completed, in response to the new transaction being related to the changed data according to the information related to the changed data and data size of the data synchronization between the first database and the second database being below a threshold; and
program instructions to reject, by the back-up system, the new transaction with the second database, in response to the new transaction being related to the changed data according to the information related to the changed data and the data size of the data synchronization between the first database and the se

Assignees

• IBM

Inventors

• Lu E Feng
• Fang Yu
• Mao Ying
• Liu Ning Ll
• Yu Lu

Classifications

• G06F11/2038

  with a single idle spare processing component · CPC title

• G06F16/214

  Database migration support · CPC title

• G06F11/2048

  where the redundant components share neither address space nor persistent storage · CPC title

• G06F11/2097

  maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title

• G06F16/2379 Primary

  Updates performed during online database operations; commit processing · CPC title