Database Failover Configuration via Observer Process

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for configuring automatic failover in database management systems are error-prone, time-consuming, and require manual manipulation using SQL*Plus or programmatic interfaces, making it difficult to set up database systems with replicated data for seamless failover without data loss.

Innovation Solution

A graphical user interface (GUI) server is used to input and store automatic failover configuration information, which is accessed by an observer that initiates failover independently of the primary and standby database systems, enabling automatic failover through a network and persistent storage, with features like ping detection for failover requirements and automatic restart capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration methods using SQL*Plus or programmatic interfaces are used, then database failover capability can be implemented, but the configuration process becomes error-prone and time-consuming

Engineering Contradiction:
Improvefailover capabilityVSAvoidconfiguration process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an observer process as an intermediary component that automatically monitors the primary database system and initiates failover to standby systems when failures are detected. This mediator eliminates the need for manual configuration and monitoring, reducing errors while maintaining reliable failover capability through automated detection and response mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service failover through the observer process that autonomously monitors database health, detects failures, and triggers failover operations without human intervention. The configuration is stored in persistent storage and automatically retrieved by the observer, enabling the system to manage its own failover processes and reducing operational complexity.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If automatic failover configuration is implemented, then failover can be initiated automatically, but the system complexity increases with multiple components like observer processes and persistent storage

Engineering Contradiction:
Improveautomatic failover initiationVSAvoidsystem architecture
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent segments the failover system into distinct functional components: an observer process for monitoring, persistent storage for configuration, and the database systems (primary and standby). This segmentation allows each component to perform its specific function independently, simplifying the overall system architecture while enabling automatic failover through coordinated operation of these modular elements.

Inventive Principle:
Principle #1Segmentation

3Device complexity

If manual configuration methods are used, then system complexity can be reduced, but the time required for setup and configuration increases significantly

Engineering Contradiction:
Improveconfiguration systemVSAvoidsetup time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by storing the failover configuration in persistent storage before any failure occurs. The observer process retrieves this pre-configured information automatically when needed, eliminating the time-consuming manual configuration steps during actual failover events. The configuration is prepared in advance and readily available for immediate execution.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7549079B2System and method of configuring a database system with replicated data and automatic failover and recovery
Publication Date: 2009.06.16 ORACLE INT CORP
  • US7549079B2 patent drawing
  • US7549079B2 patent drawing
  • US7549079B2 patent drawing

AI summary

A graphical user interface based method of configuring automatic failover from a primary database system to a standby database system that is coupled to the primary database system by a network. Also coupled to the network is an observer process that is independent of the database systems and that initiates the failover process. The observer periodically pings the database systems to determine whether a failover is necessary. The graphical user interface permits a user to specify the primary and secondary database systems, configure the observer, and specify conditions under which a failover may occur and to enable automatic failover. A failover context is created from the inputs to the GUI and stored in persistent storage belonging to the database systems. If the Observer's context is stale, the Observer fetches the database system's context.