Gold Image as Service for Database Patch Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy database software installation and patching processes are error-prone and cumbersome due to manual steps, inconsistent mechanisms, and the need for users to maintain and apply one-off patch updates, which are not always incorporated into general releases, leading to time-consuming and inefficient database software upgrades.

Innovation Solution

The Gold Image as a Service (GIaaS) generates customized software images by applying customer-specific one-off patch updates to a generic software version, optimizing the image for deployment by removing unnecessary files and detecting conflicts, thereby streamlining the software upgrade process and reducing manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual installation and patching processes are used, then users can install database software and apply patches, but the process becomes error-prone and time-consuming

Engineering Contradiction:
Improveinstallation accuracyVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically detecting the database software version, identifying applicable patches, and applying them without requiring manual user intervention. The patch management system autonomously navigates the software repository, retrieves patches, and executes installation, eliminating human errors and reducing time consumption.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring automated patch management policies, defining software version criteria, and establishing patch application rules before actual patching operations. This preparatory configuration enables the system to automatically execute patching workflows without manual intervention during critical updates.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If users maintain inventory of one-off patch updates, then they can track custom patches, but the process becomes burdensome and time-consuming

Engineering Contradiction:
Improvepatch tracking accuracyVSAvoidpatch management efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring the database software environment, automatically detecting which patches have been applied, and providing real-time status information. This feedback loop eliminates the need for manual inventory tracking by automatically maintaining an accurate record of all applied patches and their current state.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces a patch management system as an intermediary between the database software and the patches. This intermediary automatically manages the relationship between software versions and applicable patches, eliminating the need for users to manually track and correlate patch information with specific software configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If DBAs manually create gold images, then they can ensure custom patches are included, but the process requires huge effort and inconsistency

Engineering Contradiction:
Improvegold image consistencyVSAvoidgold image creation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs self-service by automatically generating gold images with the correct configuration of database software and applied patches. The automated system ensures consistency by using standardized templates and verified patch combinations, eliminating the variability and errors associated with manual gold image creation by different DBAs.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring gold image templates with standard database software configurations and pre-tested patch combinations. These pre-prepared templates can be quickly instantiated and customized, dramatically reducing the time and effort required to create consistent gold images while maintaining reliability through standardized configurations.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If automated scripts are used for installation, then manual effort is reduced, but the scripts break due to changing naming conventions and requirements

Engineering Contradiction:
Improveinstallation automation levelVSAvoidscript stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements dynamics by making the automation scripts adaptive rather than static. The scripts automatically detect changes in software naming conventions, file structures, and installation requirements, and dynamically adjust their behavior accordingly. This dynamic adaptation prevents script breakage when vendor conventions change, maintaining both automation and reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback mechanisms where the automation scripts continuously monitor the software environment for changes in naming conventions, file locations, and installation requirements. When changes are detected, the scripts automatically update themselves or adjust their parameters, ensuring continued stability and functionality without manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10732960B2Systems and methods for implementing gold image as a service (GIaaS)
Publication Date: 2020.08.04 ORACLE INT CORP
  • US10732960B2 patent drawing
  • US10732960B2 patent drawing
  • US10732960B2 patent drawing

AI summary

A computer program product, system, and computer implemented method for generating a software image as a service for deployment by receiving a request for a software image, determining, via a conflict checker, whether conflicts arise between one-off patch updates, a release version of the software and/or RUs, retrieving the release version of the software, and RUs and one-off patch updates that do not have a conflict, installing the release version of the software, the RUs retrieved, and the one-off patch updates retrieved as a test image into a testing environment, testing the test image, upon successful completion of the testing of the test image, formatting the test image into the output format requested, the gold image indicating the test image has been successfully tested and is ready for deployment.