Proxy Pluggable Database for Transparent Location Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems face challenges in maintaining locational transparency and efficient management of pluggable databases (PDBs) across container databases, leading to the need for constant application code rewriting and inefficient data transfer when PDBs are moved or scaled.

Innovation Solution

The implementation of proxy pluggable databases and application root replicas, which allow for transparent location management and data partitioning using container maps, enabling commands to be forwarded to new locations without rewriting application code and optimizing data transfer by pruning irrelevant data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If pluggable databases are moved or scaled across container databases, then database availability and scalability are improved, but application code must be constantly rewritten and data transfer efficiency deteriorates

Engineering Contradiction:
Improvedatabase scalabilityVSAvoidapplication code maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a container map as an intermediary data structure that stores the mapping relationship between pluggable database names and their physical locations across container databases. This intermediary layer allows applications to access PDBs without needing to know their actual locations, thereby improving scalability while eliminating the need to rewrite application code when PDBs are moved or scaled.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If all data is transferred between query coordinator and slave processes, then query execution is simplified, but data transfer overhead increases

Engineering Contradiction:
Improvequery execution simplicityVSAvoiddata transfer overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary data from slave processes and transfers it to the query coordinator process, rather than transferring all data. The query coordinator sends query plans to slave processes, which execute the queries locally and return only the required results. This extraction approach simplifies query execution while significantly reducing data transfer overhead by eliminating unnecessary data movement.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10360269B2Proxy databases
Publication Date: 2019.07.23 ORACLE INT CORP
  • US10360269B2 patent drawing
  • US10360269B2 patent drawing
  • US10360269B2 patent drawing

AI summary

In an approach, when a pluggable database within a container database is transported to a new container database, the pluggable database is replaced with a proxy pluggable database storing forwarding information for the pluggable database. When a command is received that is to be executed on the proxy pluggable database, the database server handling the command uses the forwarding information stored within the proxy pluggable database to forward the command to a second database receiver responsible for the new container database for execution on the pluggable database. The result of executing the command is then returned to the first database server. Thus, application code which references the pluggable database within the original container database does not have to be rewritten to reference the new location and can remain agnostic as to the actual location of the pluggable database.