myblog

This summary is not available. Please click here to view the post.

Performing an OS upgrade on an ExaCS environment is a critical maintenance task. Recently, we performed a DomU patch on our Exadata X9M-2 cluster to migrate from Oracle Linux 7.9 to Oracle Linux 8.10 . While the process is generally automated, specific environmental variables can introduce challenges.     This post walks through the failure we encountered, root cause analysis, and how we manually recovered the patching process. Cluster Details Component    Current Version Target Version     Cluster Image      22.1.25.0.0.240710      24.1.16.0.0.250905    OS      OL 7.9      OL 8.10    Infra Version      25.1.4.0.0.250612      25.1.4.0.0.250612    Storage Version      25.1.4.0.0.250612      25.1.4.0.0.250612 1. Pre-Check Failures — Custom Packages The initial patchmgr pre-check fail...

Introduction: A Major OS Migration (OL7 to OL8) Upgrading an Oracle Database Appliance (ODA) Bare Metal system to version 19.24 is a significant process that goes far beyond simple patching. It involves a massive operating system migration, specifically transitioning the appliance from Oracle Linux 7 (OL7) to Oracle Linux 8 (OL8) . This mandates the Data Preserving Reprovisioning (DPR) process, which essentially rebuilds the server's OS while keeping the Grid Infrastructure (GI) and user data intact on the ASM disk groups. During a recent production upgrade, we encountered a critical hard stop failure right at the beginning of the post-reprovisioning configuration, specifically during the node restore phase. The root cause was not a bug in the new software, but a subtle "configuration drift" involving DNS, magnified by separated team responsibilities. Phase 1: The Initial Crisis — Diagnosing DNS Metadata Drift The failure occurred immediately after the OS re-image when ...