Secure Child Tables for Data Repair in Productive Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data corruption in productive systems is challenging to repair without causing further damage, as direct data repair in the storage system often requires system shutdowns and can be complicated by differences between production and test systems, leading to time-consuming and costly downtime.

Innovation Solution

A secure environment is established within the productive system to modify and repair corrupt data, using child tables that inherit from base tables, allowing for local testing and repair without affecting the productive environment, enabling access for reserved users to perform SQL operations and modifications without impacting active data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of repair

If data is repaired directly in the productive system storage, then data corruption is fixed, but system downtime occurs and further damage may be caused

Engineering Contradiction:
Improvedata repair capabilityVSAvoidsystem availability
Core Design Contradiction:
Ease of repairVSProductivity

Solution Approach 1:

The system divides data storage into separate environments: productive environment for active data and secure environment for repair operations. Child tables are segmented from base tables, allowing repair operations to be performed on isolated copies without affecting the productive system's availability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A secure environment acts as an intermediary between the productive system and repair operations. Reserved users access the productive system through this secure environment, which provides table inheritance functionality to create child tables for safe testing and repair without directly modifying productive data.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If backup restoration is performed to fix corrupt data, then data integrity is restored, but time-consuming downtime occurs

Engineering Contradiction:
Improvedata integrityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Child tables are created in advance from base tables in the productive environment. These child tables serve as pre-prepared copies that can be modified and tested without affecting the productive system, eliminating the need for time-consuming backup restoration operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates child tables that copy data from base tables. These copies can be freely modified, tested, and repaired without impacting the original productive data, providing a fast alternative to backup restoration while maintaining data integrity.

Inventive Principle:
Principle #26Copying

3Difficulty of detecting and measuring

If test system is used to reproduce corruption, then root cause can be identified, but system differences prevent accurate reproduction

Engineering Contradiction:
Improvecorruption detectionVSAvoidenvironment compatibility
Core Design Contradiction:
Difficulty of detecting and measuringVSAdaptability or versatility

Solution Approach 1:

The system merges the advantages of test environments with the productive environment by creating a secure environment within the productive system itself. Child tables inherit from base tables, ensuring environment compatibility while providing the isolation needed for safe testing and corruption reproduction.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The secure environment provides local quality differences from the productive environment, allowing reserved users to perform testing and repair operations in a controlled setting. The table inheritance mechanism ensures that child tables maintain the same structure as base tables while allowing modifications for testing purposes.

Inventive Principle:
Principle #3Local quality

4Reliability

If productive system is shut down for data repair, then safety is ensured, but productivity is significantly reduced

Engineering Contradiction:
Improvesystem safetyVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The productive system continues to operate without interruption while repair operations are performed on child tables in the secure environment. The table inheritance mechanism ensures that productive data remains accessible and operational throughout the repair process, maintaining continuous useful action.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The secure environment with table inheritance acts as an intermediary that enables repair operations without requiring system shutdown. Reserved users can safely modify child tables while the productive system continues to serve productive users, ensuring both safety and availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11238025B2Data repair within productive system
Publication Date: 2022.02.01 SAP SE
  • US11238025B2 patent drawing
  • US11238025B2 patent drawing
  • US11238025B2 patent drawing

AI summary

Provided are devices and methods for repairing corrupt data using a secure environment in a productive system. In one example, the method includes receiving a request to modify a base table stored in a productive environment, generating a child table corresponding to the base table within a secure environment of the productive system, modifying the one or more table entries from the base table and storing the modified table entries in the child table, executing one or more operations on the child table within the secure environment to determine if the one or more modified table entries repair the base table, and outputting a determined result of the one or more operations to a user interface. As a result, corrupt data can be modified locally via inheriting tables within a secured environment without any further damage being done to productive data in a productive environment.