Database Re-Instantiation with Redo Logs for Failover Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face challenges in maintaining synchronization between primary and replication databases during failover, leading to inefficiencies in data recovery and dualization processes.
Innovation Solution
A method involving the use of redo logs and control files to identify and synchronize data blocks and control file changes, allowing for efficient re-instantiation of databases by applying reference data from a secondary database to a primary database post-failover, without the need for additional logging mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If traditional database failover is performed without additional logging mechanisms, then system complexity is reduced, but data synchronization between primary and replication databases deteriorates
Solution Approach 1:
The patent applies preliminary action by capturing and storing data block addresses and control file change information in redo logs before failover occurs. This pre-capturing of critical information ensures that when failover happens, the synchronization data is already available, eliminating the need for complex additional logging mechanisms during the failover process itself.
Solution Approach 2:
The patent introduces redo logs as an intermediary mechanism that mediates between the primary database operations and the replication database. The redo logs store the necessary synchronization information (data block addresses and control file changes) and facilitate the transfer of this information to the replication database during failover, without requiring direct complex communication protocols between the databases.
2Reliability
If comprehensive data synchronization is performed during failover, then data integrity is improved, but failover time increases
Solution Approach 1:
The patent extracts only the critical synchronization information (data block addresses and control file change information) from the complete database state and stores it in redo logs. During failover, only this extracted essential information needs to be transferred and applied, rather than synchronizing the entire database state, which significantly reduces failover time while maintaining data integrity.
Solution Approach 2:
By pre-capturing and storing the essential synchronization information in redo logs before failover, the patent eliminates the need for time-consuming data collection and verification processes during the actual failover event. The synchronization data is already prepared and ready for rapid application to the replication database.
3Measurement precision
If redo logs are used to track data changes, then synchronization precision is improved, but system overhead increases
Solution Approach 1:
The patent applies local quality by storing only the specific local information needed for synchronization (data block addresses and control file change information) in the redo logs, rather than tracking all database operations in detail. This selective local tracking achieves sufficient synchronization precision for failover purposes while minimizing the overhead of logging every change.
Data Source
AI summary
Disclosed is a method for implementing re-instantiation for a database, which is performed by a computing device, which may include: acquiring at least one redo log; acquiring an address of a data block based on the at least one redo log; acquiring information on changed matters included in a control file based on the at least one redo log; and modifying a first database based on the address of the data block and the information on the changed matters.