Pluggable Database Archive File for Zero-Downtime Relocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing technologies for relocating pluggable databases between container databases are time-consuming, costly, and disruptive, especially for large databases, due to the complexity of managing and moving loose files, and compatibility issues between different patch levels of container databases.
Innovation Solution
The creation and use of an archive file that includes data files, a manifest file, rollback scripts, and a patch list, allowing for the creation of a target pluggable database that is backward compatible with the target container database by executing rollback scripts to align with the target's patch level, facilitating efficient and compatible database relocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If pluggable databases are moved between container databases using existing technologies, then database relocation is achieved, but the process is time-consuming and causes significant downtime
Solution Approach 1:
The system creates archive files containing database metadata and configuration information before the actual relocation process. This preliminary packaging of database components allows for faster restoration at the destination, significantly reducing the overall downtime during database migration between container databases.
Solution Approach 2:
Instead of moving physical database files directly, the system creates archive copies of database metadata and configuration. These archive files can be rapidly transferred and restored at the destination container database, enabling quick relocation without the time-consuming process of copying large binary database files.
2Adaptability or versatility
If pluggable databases are relocated between container databases, then database mobility is improved, but compatibility issues arise due to different patch levels
Solution Approach 1:
The system stores patch level information and compatibility metadata in the archive files. During relocation, the target container database can read this metadata to verify compatibility or automatically adjust parameters to ensure the relocated database works correctly with the target patch level, enabling cross-patch-level migration while maintaining reliability.
Solution Approach 2:
The archive file acts as an intermediary that carries database metadata and compatibility information between source and target container databases. This intermediary structure allows the system to resolve compatibility issues by providing the necessary information about the source database's patch level and requirements, enabling safe relocation across different patch levels.
3Ease of operation
If loose database files are managed and moved manually, then database relocation is possible, but the process is complex and error-prone
Solution Approach 1:
The system merges multiple loose database files, metadata, and configuration information into a single archive file structure. This consolidation simplifies the relocation process by transforming a complex multi-file management task into a simple single-file copy and restore operation, dramatically reducing operational complexity and potential for errors.
Solution Approach 2:
The archive file structure includes self-describing metadata that automatically identifies database components, their relationships, and restoration requirements. This self-service capability eliminates the need for complex manual file management and tracking, as the archive structure itself provides all necessary information for accurate restoration at the destination.
Data Source
AI summary
Techniques herein make and use a pluggable database archive file (AF). In an embodiment, a source database server of a source container database (SCD) inserts contents into an AF from a source pluggable database (SPD). The contents include data files from the SPD, a listing of the data files, rollback scripts, and a list of patches applied to the SPD. A target database server (TDS) of a target container database (TCD) creates a target pluggable database (TPD) based on the AF. If a patch on the list of patches does not exist in the TCD, the TDS executes the rollback scripts to adjust the TPD. In an embodiment, the TDS receives a request to access a block of a particular data file. The TDS detects, based on the listing of the data files, a position of the block within the AF. The TDS retrieves the block based on the position.