Database Cluster Synchronization for Pluggable Database Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multi-node database management systems face limitations in scaling the number of pluggable databases within a container database, leading to inefficiencies when accessing and managing PDBs distributed across multiple CDBs, as administrators must manually update scripts to account for PDB movements, causing maintenance costs and complexity.

Innovation Solution

A multi-node DBMS with a cluster synchronization server that maintains mapping information and metadata across CDBs, allowing database clients to interact with PDBs as if they are part of a single CDB, ensuring locational transparency and eliminating the need for script updates by forwarding commands to the correct CDBs based on current PDB locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If pluggable databases are distributed across multiple container databases to overcome scaling limitations, then the number of PDBs that can be managed is improved, but the complexity of accessing and managing these PDBs worsens due to the need for administrators to manually update scripts to account for PDB movements

Engineering Contradiction:
Improvenumber of pluggable databasesVSAvoidmanagement complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the database management system with mapping information) that sits between the administrator and the distributed PDBs. This intermediary automatically resolves the physical location of PDBs across multiple CDBs and redirects access appropriately, eliminating the need for administrators to manually track and update script locations while maintaining transparent access to all PDBs

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If pluggable databases are distributed across multiple container databases, then scalability is improved, but the time required to maintain and update access scripts worsens

Engineering Contradiction:
Improvenumber of pluggable databasesVSAvoidmaintenance time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system implements self-service through automatic location tracking and redirection. The database management system continuously maintains mapping information about PDB locations across CDBs and automatically redirects access requests without requiring administrator intervention. This self-updating mechanism eliminates manual script maintenance while supporting arbitrary numbers of distributed PDBs

Inventive Principle:
Principle #25Self-service

3Quantity of substance

If multiple container databases are used to hold pluggable databases, then the scaling capability is improved, but the operational efficiency worsens due to the need to manually track PDB locations

Engineering Contradiction:
Improvenumber of container databasesVSAvoidoperational efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism where the database management system continuously monitors and maintains mapping information about PDB locations across multiple CDBs. This feedback loop automatically updates location information and redirects access requests, enabling efficient operations across distributed databases without manual tracking while supporting unlimited scaling

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10803078B2Ability to group multiple container databases as a single container database cluster
Publication Date: 2020.10.13 ORACLE INT CORP
  • US10803078B2 patent drawing
  • US10803078B2 patent drawing
  • US10803078B2 patent drawing

AI summary

In an approach, a database management system is configured in a manner that allows all pluggable databases within a cluster to be treated, from the perspective of a user, as though stored on a single container database, even when the pluggable databases are distributed across a plurality of container databases. When a command is received by a database server that is to be executed on all or a subset of the pluggable databases within the cluster, the database inspects mapping information replicated on all container databases within the cluster by a cluster synchronization server to determine which container databases store pluggable databases implicated by the command. The command is then forwarded to the database servers responsible for the determined container databases for execution. As a result, the commands issued by the user can be agnostic in regard to the actual location of the pluggable databases within the cluster.