Database System with Segmented Tablespaces for Simultaneous Write Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database architectures, such as Oracle Data Guard, only allow one database to be open for read/write operations while the other is read-only, leading to delayed access to data in standby databases and limited flexibility in data storage.

Innovation Solution

The system divides data into multiple tablespaces across multiple databases, with each database acting as both primary and standby for different data sets, enabling simultaneous read and write operations while maintaining redundancy through journaling, allowing for instantaneous transition between primary and standby roles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If one database is designated as primary and another as standby, then data redundancy is maintained, but the standby database is limited to read-only access and cannot perform write operations

Engineering Contradiction:
Improvedata redundancyVSAvoiddata access flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the database system into multiple independent database instances, each capable of functioning as both primary and standby for different data sets. This segmentation allows each database to have specialized roles for specific tablespaces while maintaining overall system flexibility and redundancy.

Inventive Principle:
Principle #1Segmentation

2Stability of the object's composition

If changes are made to the primary database and journaling is used, then data consistency is maintained, but access to the standby database is delayed

Engineering Contradiction:
Improvedata consistencyVSAvoiddata access delay
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements preliminary replication of data and journal entries to standby databases before they are needed. By proactively maintaining synchronized copies and pre-positioning data in standby databases, the system reduces access delays when failover or read operations are required.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the standby database is converted to primary database, then data availability is improved, but the transition requires delay dependent on data volume and network performance

Engineering Contradiction:
Improvedata availabilityVSAvoidtransition delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements dynamic role assignment where databases can flexibly switch between primary and standby roles for different tablespaces. This dynamic configuration allows the system to optimize data availability by enabling multiple databases to simultaneously serve as primary for different data sets, eliminating the need for lengthy role transition delays.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10963484B2Systems and methods for use in data access
Publication Date: 2021.03.30 MASTERCARD INT INC
  • US10963484B2 patent drawing
  • US10963484B2 patent drawing
  • US10963484B2 patent drawing

AI summary

Systems and methods are provided for use in accessing data stored in multiple databases. One exemplary system includes first and second databases. The first database includes a first primary tablespace having first data, a first standby tablespace having first standby data, and a first journal. The first database is configured, in response to a request including a change instruction for the first data, to alter the first data consistent with the change instruction, append a change description indicative of the alteration to the journal, and transmit the journal to the second database. The second database is configured to then receive the journal from the first database and to alter second standby data included in a second standby tablespace of the second database consistent with the change description, thereby maintaining the second standby data in the second standby tablespace as a replicate of the first data in the first primary tablespace.