Container Database Pluggable Isolation Transport

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database consolidation methods face challenges in achieving effective isolation, transportability, and fast provisioning of databases across hardware platforms, often resulting in inefficiencies and prolonged metadata updates during database transport.

Innovation Solution

A container database management system (DBMS) is introduced, which manages multiple pluggable databases with separate dictionaries, allowing for isolated access and efficient transport by using a container DBMS that includes a root database for global management and pluggable databases with their own dictionaries, facilitating quick provisioning and resource sharing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional database consolidation methods are used, then databases can be distributed across hardware platforms, but isolation between databases is insufficient and namespace conflicts occur

Engineering Contradiction:
Improvedatabase transportabilityVSAvoiddatabase isolation
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the database system into separate pluggable databases, each with its own namespace and dictionary. This segmentation allows each database to be isolated from others while maintaining the ability to transport them independently across platforms, resolving the contradiction between transportability and isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a container database as an intermediary that manages multiple pluggable databases. The container provides a unified namespace that mediates between individual database namespaces, enabling both isolation of individual databases and coordinated transport across platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If databases are consolidated on a single host, then resource sharing is improved, but provisioning time increases due to metadata updates

Engineering Contradiction:
Improveresource sharing efficiencyVSAvoidprovisioning time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements fast provisioning by copying entire pluggable databases as transportable packages between hosts. This copying mechanism avoids time-consuming metadata updates by preserving the database structure and relationships intact during the provisioning process.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs preliminary organization of databases into transportable packages with complete metadata and structural information. This preliminary action enables rapid provisioning when databases need to be deployed or moved, as the packaging work is done in advance rather than during provisioning.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2901325B1Container database
Publication Date: 2022.01.26 ORACLE INT CORP
  • EP2901325B1 patent drawingFigure 1
  • EP2901325B1 patent drawingFigure 2
  • EP2901325B1 patent drawingFigure 3

AI summary

A container database may contain multiple database dictionaries, each database dictionary defining a pluggable database. When database sessions are established on a container DBMS, each database session is given access to a pluggable database by establishing the respective database dictionary of the pluggable database as the database dictionary for that database session. Database commands issued through database session can only access the database objects defined in the database dictionary established for the database session.