Database Recovery Progress Reporting via Object-Level Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database recovery progress tracking methods, such as those using DVM, are limited to the database level and do not effectively monitor the recovery status of database objects like tablespace partitions, making it difficult to provide comprehensive recovery progress reports.

Innovation Solution

A computer program product and method that receives a start time, selects database objects for a recovery progress report, and outputs a report identifying the number or percentage of recovered objects based on an object recovery table generated by the database recovery utility, providing detailed recovery status for tablespaces and index partitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If database recovery tracking is performed at the database level using existing methods, then the tracking process is simple, but the measurement precision of recovery progress is insufficient because it cannot track individual database objects

Engineering Contradiction:
Improverecovery progress tracking precisionVSAvoidtracking system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the database recovery tracking into two levels: database-level tracking (using existing DVM mechanisms) and object-level tracking (using new object recovery tables). This segmentation allows precise tracking of individual database objects while maintaining the simplicity of database-level monitoring, resolving the contradiction between measurement precision and system complexity.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If comprehensive recovery status of all database objects is monitored, then the information completeness is improved, but the loss of time for data collection and processing increases

Engineering Contradiction:
Improverecovery status information completenessVSAvoiddata collection and processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the database recovery utility automatically populate object recovery tables with recovery status information as recovery operations occur. This pre-collection of data eliminates the need for time-consuming queries during reporting, providing comprehensive recovery status information without significant time loss.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If detailed recovery status of individual database objects is provided, then the usefulness of recovery reports is improved, but the device complexity for generating and maintaining recovery data increases

Engineering Contradiction:
Improverecovery report usefulnessVSAvoidrecovery data management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces object recovery tables as intermediary structures between the database recovery utility and the reporting system. These tables store detailed recovery status information for individual database objects, serving as a mediator that provides comprehensive data for useful reports without requiring the reporting system to directly manage complex recovery data collection and processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2610749B1Database recovery progress report
Publication Date: 2018.02.28 BMC SOFTWARE INC
  • EP2610749B1 patent drawingFigure 1
  • EP2610749B1 patent drawingFigure 2
  • EP2610749B1 patent drawingFigure 3

AI summary

The present description refers to a computer implemented method, computer program product, and computer system for receiving (510) a start time, selecting (520) one or more database objects for which a database recovery progress report is to be provided, determining (530), based on an object recovery table generated by the database recovery utility, which of the selected database objects have been recovered since the start time, and outputting (540) a database recovery progress report that identifies at least a number or percentage of the selected database objects that have been recovered by the database recovery utility since the start time.