Single Node Database Server Online Patching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for patching a database in a single node cluster require shutting down the database instance, making it completely unavailable, as there is no existing method for online patching in this configuration.
Innovation Solution
Implementing a local rolling online patching solution where a new instance of the database is started from the newly patched home before shutting down the old instance, allowing for minimal disruption and maintaining availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a database instance is patched using traditional methods, then the database can be updated to the latest version, but the database becomes completely unavailable during the patching process
Solution Approach 1:
The patent applies preliminary action by creating a new database instance with the patched version before shutting down the old instance. This ensures that the updated database is ready and waiting to take over immediately, minimizing downtime. The new instance is prepared in advance with all necessary patches applied, so when the switch occurs, the database is already at the latest version without requiring any additional patching time.
Solution Approach 2:
The patent uses an intermediary approach by introducing a new database instance as a mediator between the old instance and the patched version. This new instance serves as a temporary bridge that allows the database to remain accessible during the transition. The new instance handles all database operations while the old instance is being shut down, ensuring continuous availability without direct interruption to users.
2Adaptability or versatility
If a single node database server is patched, then the database can be updated, but the entire database service must be shut down making it unavailable
Solution Approach 1:
The patent applies segmentation by dividing the database service into two separate instances: an old instance and a new instance with patched version. This segmentation allows each instance to operate independently, enabling the new instance to be updated without affecting the old instance's operation. The database service is split into multiple segments that can be managed separately, providing online patching capability while maintaining service continuity.
Solution Approach 2:
The patent uses parameter changes by transitioning from a single-instance model to a multi-instance model with different version parameters. The new instance runs with updated software version parameters while the old instance continues with the previous version. This parameter differentiation enables the system to support multiple versions simultaneously, facilitating online patching operations without disrupting service continuity.
Data Source
AI summary
Described are improved systems, computer program products, and methods for a new local rolling online patching solution to a database server with minimized disruption to other instances during patching. For a one-node database server, it achieves single rolling online patching by starting a new instance of the same database from the newly patched home before shutting down the collocated instance running out of the old home.