Idling Specified Database Objects During Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database replication systems face challenges in idling specific database objects during replication, requiring the entire replication process to stop and restart, leading to errors and inefficiencies, especially when high latency occurs or when only a subset of tables needs to be updated.
Innovation Solution
Implementing a method to suspend replication of a specified database object by terminating the transfer of target operations and monitoring for no operations on the target database, allowing for immediate idling without affecting other tables, and notifying the user or application of the idling status.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire replication process is stopped to idle a specified database object, then the specified object can be idled without errors, but the replication productivity decreases and latency increases
Solution Approach 1:
The patent segments the replication process by introducing per-object replication state tracking. Each database object can be independently idled or resumed without affecting other objects. The system maintains a replication state for each object (IDLE, ACTIVE, SUSPENDED) and processes operations based on individual object states rather than requiring global replication state changes. This allows selective idling of specific objects while maintaining replication for others.
Solution Approach 2:
The patent implements partial action by allowing replication to continue for objects that do not require idling. When a specified object needs to be idled, only that particular object's replication is suspended while other objects continue to receive replication operations. This partial suspension approach maintains overall system productivity while achieving the specific idling requirement.
2Stability of the object's composition
If the entire replication process is stopped to idle a specified database object, then replication consistency is maintained, but the time required for idling increases
Solution Approach 1:
The patent implements preliminary action by pre-establishing per-object replication state tracking mechanisms before idling is requested. The system maintains readiness to suspend or resume replication for individual objects by having separate state tracking and operation routing infrastructure in place. When an idling request arrives, the system can immediately transition the specific object's state without requiring preliminary global replication suspension.
3Productivity
If replication operations continue on an idled database object, then replication productivity is maintained, but errors occur in the target database
Solution Approach 1:
The patent implements feedback mechanisms by continuously monitoring the replication state of each database object and adjusting operation routing accordingly. When an object is marked as IDLE, the system detects this state and prevents replication operations from being applied to that object. The system provides feedback loops where the replication state is tracked, operations are routed based on current state, and state transitions are monitored to maintain consistency and prevent errors.
4Reliability
If the entire replication process is stopped to idle a specified database object, then operational safety is ensured, but the device complexity increases due to restart requirements
Solution Approach 1:
The patent applies local quality by implementing differentiated replication control at the object level rather than using a uniform global control mechanism. Each database object can have its own replication state (ACTIVE, IDLE, SUSPENDED) and operation routing rules. This allows the system to apply appropriate replication behavior locally to each object based on its specific requirements, reducing the need for complex global restart procedures while maintaining operational safety through targeted control.
Data Source
AI summary
According to one embodiment of the present invention, during database replication from a source database to a target database, operations applied to the source database are transferred as target operations and applied to the target database. A request from a requestor to idle a specified database object is received during the database replication. In response to receiving the request, transference of the target operations for the specified database object from the source database to the target database is terminated and target operations for the specified database object on the target database are monitored. In response to no target operations being applied to the specified database object on the target database, replication of the specified database object is suspended and the requestor is notified when the idling of the specified database object has completed.