Target Database Recovery Bookmark for Fault-Resilient Transactions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face inefficiencies in handling complex analytical queries and data processing tasks, particularly in environments where multi-table transactions are not supported, leading to costly and time-consuming reloads of database tables during fault conditions.

Innovation Solution

Implementing a single recovery bookmark that includes an earliest open entry, latest commit entry, and transactional identifier to manage database transactions, allowing for efficient recovery and resumption of transactions without reloading tables, even in environments lacking multi-table transaction support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database tables are reloaded during fault conditions in environments without multi-table transaction support, then data consistency can be restored, but system downtime increases and productivity decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating recovery bookmarks before executing batch transactions. These bookmarks capture the state of database tables prior to batch processing, enabling rapid recovery without full table reloads when faults occur, thus maintaining both data consistency and system availability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention segments the database recovery process into individual table-level operations rather than requiring complete system-wide table reloads. By tracking which specific tables were affected by each batch transaction through recovery bookmarks, the system can selectively recover only the necessary tables, minimizing downtime and maintaining productivity

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If multiple recovery bookmarks are maintained for each batch transaction, then recovery precision improves, but device complexity increases

Engineering Contradiction:
Improverecovery precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system merges multiple recovery bookmark data structures into a single consolidated recovery bookmark that tracks the state across all tables affected by a batch transaction. This unified approach maintains precise recovery information while reducing the complexity of managing multiple separate bookmark structures

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The recovery bookmark structure is designed as a universal data structure that can track the state of any number of database tables within a single batch transaction. This multi-functional bookmark eliminates the need for separate tracking mechanisms for each table, reducing overall system complexity while maintaining comprehensive recovery precision

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12405865B1Recovery of a target database system
Publication Date: 2025.09.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12405865B1 patent drawing
  • US12405865B1 patent drawing
  • US12405865B1 patent drawing

AI summary

Aspects of the present disclosure relate to recovery of a target database system. The method comprises receiving multiple batches of database transactions to form the target database system. The method further comprises generating a single recovery bookmark before beginning processing of a current batch, wherein the single recover bookmark comprises: an earliest open entry for a previous batch, a latest commit entry for the previous batch, an earliest open entry for the current batch, a latest commit entry for the current batch, a transactional identifier, and list of tables to be processed; performing the sequence of database transactions; replacing the list of tables from the single recovery bookmark with a flag value upon completion; detecting a fault condition during the performance of the sequence of database transactions; recovering the target database system using the single recovery bookmark; and resuming the sequence of database transactions.