Oracle international corporation (20240126785). FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE simplified abstract
Contents
- 1 FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE
Organization Name
oracle international corporation
Inventor(s)
Carol Lyndall Colrain of Kansas City KS (US)
Xiaoli Qi of Palo Alto CA (US)
Kevin S. Neel of San Mateo CA (US)
Stephen J. Vivian of Londonderry NH (US)
Michael Cusson of Woburn MA (US)
Yunrui Li of Los Altos CA (US)
Jonathan Giloni of Foster City CA (US)
FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE - A simplified explanation of the abstract
This abstract first appeared for US patent application 20240126785 titled 'FAILOVER OF DATABASE SESSIONS TO A LOGICAL REPLICA DATABASE
Simplified Explanation
The patent application describes techniques for preserving inflight sessions during failover from a primary database to a replicated logical database.
- Prior to failover, the primary database server stores a commit indication for each transaction that has been committed by executing a corresponding SQL command. This commit indication is replicated to the logical replica database, allowing the standby database server in the failover session to request the outcome of the transaction.
- Client-side LOB references are preserved when failing over to the logical replica database, as well as AS OF queries and versioning of checksums, signatures, and structures across logical replicas.
Potential Applications
This technology could be applied in disaster recovery scenarios where seamless failover from a primary database to a replicated logical database is crucial for maintaining business continuity.
Problems Solved
This technology solves the problem of preserving inflight sessions and client-side references during failover, ensuring that transactions are not lost and that data integrity is maintained.
Benefits
The benefits of this technology include improved reliability and availability of database systems, reduced downtime in the event of a primary database failure, and enhanced data protection during failover processes.
Potential Commercial Applications
One potential commercial application of this technology could be in the financial industry, where real-time transaction processing is critical and any downtime can result in significant financial losses.
Possible Prior Art
One possible prior art for this technology could be techniques for database replication and failover in high availability systems, such as those used in large-scale enterprise environments.
Unanswered Questions
How does this technology compare to existing failover solutions in terms of performance and reliability?
This article does not provide a direct comparison with existing failover solutions, so it is unclear how this technology stacks up against other options in terms of performance and reliability.
What are the potential limitations or drawbacks of implementing this technology in a production environment?
The article does not address any potential limitations or drawbacks of implementing this technology, leaving open the question of whether there are any challenges or trade-offs that need to be considered before adoption.
Original Abstract Submitted
techniques are described for preserving the inflight sessions failing over from a primary database to the replicated logical database of the primary database. in an implementation, prior to failover, when the primary database server receives a commit for a transaction, the process stores a commit indication that the transaction has been committed by performing a corresponding sql command. the commit indication is replicated to the logical replica database by virtue of the replication of the sql command and its execution on the logical replica database. accordingly, the standby database server in the failover session may successfully request for the outcome of the transaction. techniques are also described for the client-side lob references to be preserved when failing over to the logical replica database, for as of queries preserved, and for versioning of checksums, signatures and structures across logical replicas.
- Oracle international corporation
- Carol Lyndall Colrain of Kansas City KS (US)
- Xiaoli Qi of Palo Alto CA (US)
- Kevin S. Neel of San Mateo CA (US)
- Stephen J. Vivian of Londonderry NH (US)
- Michael Cusson of Woburn MA (US)
- Yunrui Li of Los Altos CA (US)
- Jonathan Giloni of Foster City CA (US)
- G06F16/27
- G06F11/20
- G06F16/23