Hierarchical Rollback System for Non-Transactional Data Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems, particularly Enterprise Information Systems, face challenges in rolling back non-transactional operations due to the absence of predefined execution sequences, leading to extraneous or incorrectly linked data that can corrupt the data store, as existing communication interfaces are unable to effectively remove such data.
Innovation Solution
A hierarchical rollback system comprising modules for generating and executing rollback procedures for business objects with parent-child relationships, allowing for cascade execution of rollback procedures in a non-linear order, and utilizing an activity log to record both modification and rollback operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-transactional operations are executed without predefined sequences, then operational flexibility is improved, but data integrity deteriorates due to inability to rollback failed operations
Solution Approach 1:
The system performs preliminary actions by creating rollback procedures before executing non-transactional operations. The rollback module generates undo commands in advance, storing them in the activity log, so that if an operation fails, the pre-prepared rollback procedures can be executed to restore data integrity.
Solution Approach 2:
The activity log serves as an intermediary between the update module and the rollback module. It records all modification requests and their corresponding rollback procedures, enabling the system to track and revert non-transactional operations even without predefined execution sequences.
2Reliability
If hierarchical rollback procedures are implemented for non-transactional operations, then data integrity is improved, but system complexity increases
Solution Approach 1:
The rollback system is segmented into distinct modules: the update module that executes operations, the rollback module that generates rollback procedures, and the activity log that records operations. Each module has a specific function, making the complex rollback mechanism more manageable and maintainable through functional decomposition.
Solution Approach 2:
The rollback procedures are nested within the activity log structure, with each modification request containing its corresponding rollback commands. This nested organization allows the system to manage complex hierarchical rollbacks by embedding rollback logic within the operation records themselves.
3Manufacturing precision
If rollback procedures are generated for each data element, then rollback precision is improved, but processing time increases
Solution Approach 1:
Rollback procedures are generated in advance when modification requests are received, rather than being created at the moment of failure. The rollback module prepares undo commands for each data element change and stores them in the activity log, so that during a rollback operation, pre-computed procedures can be executed quickly without recalculation delays.
Data Source
AI summary
An apparatus, system, computer program product and method are disclosed for the hierarchical rollback of business objects on a datastore. The hierarchical rollback method utilizes a non-linear process designed to restore data to a previous point in the case of a data modification failure in order to prevent incorrect linking and data corruption. The hierarchical rollback methods are generated by retrieving existing data and creating commands in an order that will prevent orphan data in a datastore.