Exadata Fleet Update

Exadata Fleet Update 概要、設定方法日本オラクル株式会社テクノロジー事業戦略統括部データベースソリューション部 2026/2/13 Takeshi Maruyama

Oracle Exadata Database Serviceの保守 Copyright © 2026, Oracle and/or its
affiliates

Oracle Exadata Database Service オンプレミスおよびパブリッククラウドで利用可能 3 Copyright © 2026, Oracle
and/or its affiliates お客様データセンターパブリック・クラウド

メンテナンスの課題 4 Copyright © 2026, Oracle and/or its affiliates 大規模なフリート環境では画面からメンテナンス作業
を実行する場合、数十から数百のステップが必要スクリプトを指定する必要があるスクリプト化されていない場合、一度に1つのターゲットにしか実行できないスケジュール機能が無い

Exadata Fleet Update お客様のフリートを維持する最も簡単な方法

• OCI上のExadata Database Service on Dedicated Infrastructure、 Exadata Database Service
on Cloud@Customerだけでなく、 ExaDB-D@Azure、ExaDB-D@GCP、ExaDB-D@AWSにおける大規模データベース・デプロイメント環境におけるメンテナンス作業を自動化（ExaDB-XSは今後対応予定） • データベースとグリッド・インフラストラクチャのグループに対して、単一のメンテナンス・スケジュールとメンテナンス・サイクルで更新可能 • ネイティブOCIサービス • Exadata Database Service on Dedicated Infrastructure、 Exadata Database Service on Cloud@Customer に含まれるサービス Exadata Fleet Update とは？ Copyright © 2026, Oracle and/or its affiliates 6

Exadata Fleet Update のメリット • 画面遷移やクリック数を大幅に削減：例：100個のデータベースターゲットの場合、 • 従来の方法では800回の画面遷移が必要 •
Exadata Fleet Updateを使用すると 4回の画面遷移で完了 • パッチ適用状況をフリートレベルで可視化し、注意が必要な失敗をハイライト • フリートレベルでの完全な再開およびロールバック機能 • 高度なローリングオプション Copyright © 2026, Oracle and/or its affiliates 7

Exadata Fleet Update で解決できる問題メンテナンスの簡素化管理にかかる時間の短縮化 8 Copyright © 2026,
Oracle and/or its affiliates

Maintenance Cycle を定義 (パッチ適用サイクル毎) 2 Exadata Fleet Update の仕組み ExaDB-D@Azure
ExaDB-D Grid Infrastructure Collection Database Collection 1 ExaDB-D@GCP ExaDB-D@AWS Grid Infrastructure Collection Database Collection 1 ExaDB-D in DRCC ExaDB-C@C Grid Infrastructure Collection Database Collection 1 ＊CollectionはExadataサービス種別、リージョン、ターゲット種別に紐づけられる Collection を作成 (設定は一度) 1 2 3 Maintenance Actions の実施 3 ExaDB Stack Collection ExaDB Stack Collection ExaDB Stack Collection Copyright © 2026, Oracle and/or its affiliates 9

Grid Infrastructure Oracle Database Guest OS ExaDB Stack Collection の作成方法
10 Copyright © 2026, Oracle and/or its affiliates Major version コンパートメント RU Version/ Custom Image DB Name/ DB Unique name Oracle Home VM Cluster Exadata Infrastructure

Virtual Machine Exadata OS Image Updated Grid Infrastructure Updated Virtual
Machine Exadata OS Image Updated Grid Infrastructure Updated ポイント毎の運用 vs ExaDB Stack Virtual Machine Exadata OS Image Database Instance Grid Infrastructure GuestOS Update GI Update Virtual Machine Exadata OS Image Database Instance Grid Infrastructure Guest OS + GI Update 1回のオペレーションポイント毎の運用 ExaDB Stack Copyright © 2026, Oracle and/or its affiliates データベースインスタンスは2回再起動されるデータベースインスタンスの再起動は1回のみ 11

ターゲットの Collections へのグループ化 Copyright © 2026, Oracle and/or its affiliates
12 ① ターゲット • Exadata Database Service • ExaDB-D • ExaDB-C@C ② ターゲット • 同一Exadata Cloud Serviceタイプで、複数のインフラストラクチャにまたがることが可能 ③ 同じタイプのターゲットを Collection でグループ化可能 • Oracle Databases • Oracle Grid Infrastructure • Guest OS • ExaDB Stack (Guest OS + GI) ④ Collectionは1つのリージョンで定義される複数のコンパートメントにまたがることが可能 ExaDB-C@C ExaDB-D 1 2 3 4 Region 2

Maintenance Cycle とは 13 Copyright © 2026, Oracle and/or its
affiliates 以下を定義ターゲット・バージョン Standard RU または Custom Image ローリングまたは非ローリング・メンテナンス Drain Timeout 無視可能なパッチその他のオプション

Maintenance Cycle が実行される仕組み 14 Copyright © 2026, Oracle and/or its
affiliates 必須ステップオプションステップ Maintenance Actions Stage Software Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Apply Updates Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ)

Exadata Fleet Update インタフェース希望の方法を利用可能 OCIコンソール OCIコマンドライン OCI API 15
Copyright © 2026, Oracle and/or its affiliates

Exadata Fleet Update Features ネイティブ・フリート・ワイド・パッチ適用/アップグレードメンテナンス・アクションは、個々のターゲットではなく、グループに対して実行される拡張(ローリング)パッチ・
オプション • 一度に1つのノードへ適用（ローリング、デフォルト） • 50/50 （ローリングで半分づつに適用） • スマート・バッチ • 非ローリング • ドレイン・タイムアウトの指定（デフォルト600秒）スケジュール機能メンテナンス処理をスケジュール可能アウトオブプレースのパッチ適用 Standard Software Images またはカスタム・データベース・ソフトウェア・イメージに基づいて新しいホームがインストールされる Copyright © 2026, Oracle and/or its affiliates ExaDB Stack グリッドインフラストラクチャとゲストOSのアップデートを 1つのフローにまとめることで、セッションドレインを削減 16

Exadata Fleet Update • Exadata Cloud Services全体のフリートでメンテナンス作業をオーケストレーション • ExaDB-D（パートナークラウドを含む）
• ExaDB C@C • 大規模なフリートのメンテナンス作業を自動化 • 複数のデータベースおよびグリッドインフラストラクチャを単一のメンテナンススケジュールで更新・アップグレード • ゲストOSやゲストOS+グリッドインフラストラクチャのグループを ExaDB Stack Collectionでまとめて更新 • ターゲットのCollectionを1つのエンティティとして操作することで、効率的なフリート管理を実現 • （カスタム）ゴールドイメージをアウト・オブ・プレースで適用し、フリート全体でアップデートを標準化 18 Copyright © 2026, Oracle and/or its affiliates https://blogs.oracle.com/oracle4engineer/announcing-exadata-fleet-update-jp

• Exadata Database Service の更新の簡素化、標準化、および強化 • インターフェースの選択 • OCI
コンソール • OCI API • OCI コマンドライン • 完全なネイティブOCIサービス • 無料 OCIリージョン ExaDB-D ExaDB-D まとめ ExaDB-D データベース Collection Grid Infrastructure Collection Copyright © 2026, Oracle and/or its affiliates 19

リソース • ブログ • Exadata Fleet Updateの発表 • Exadata Fleet
Update 概要 • Exadata Fleet UpdateがExadata Database Serviceのアップグレードをサポート！ • Exadata Fleet UpdateのGuest OSとExaDB Stackコレクションのご紹介 • マニュアル • Exadata Fleet Update Administrator's Guide - https://docs.oracle.com/en/engineered-systems/exadata-cloud-service/edsfu/index.html - https://docs.oracle.com/en-us/iaas/edsfu/index.html • Exadataフリート更新管理者ガイド - https://docs.oracle.com/cd/F56555_01/edsfu/index.html • API リファレンス • https://docs.oracle.com/en-us/iaas/api/#/en/edsfu/ • デモビデオ • https://www.youtube.com/playlist?list=PLdtXkK5KBY56u9bIE2PkAtE5eYdA_82WK 20 Copyright © 2026, Oracle and/or its affiliates

Fleet Patching & Provisioning

Gold Image Repository Fleet Patching & Provisioning Oracleソフトウェア管理の自動化 • すべてのOracleデプロイメントをサポート
• Oracle Database、Grid Infrastructure、フルスタックExadataパッチ適用 • Oracle RAC（One）またはDatabase Lifecycle Management Packにライセンス付与 • 容易で再現性のある標準化されたアウト・オブ・プレースパッチ適用とプロビジョニングの自動化を提供 • ダウンタイムの短縮、簡単なロールバック • 「一度構築して多数に展開」 • 以下のような高度な機能を含む： • ゴールドイメージ・ドリフト検出 • Oracle Data Guardの完全自動化パッチ適用 • 高度なジョブスケジューリング • 拡張性のためのカスタムユーザーアクション • 包括的なExadataパッチ適用 • Oracle MAAベストプラクティスの適用 • Oracle Update Advisorとの統合 23 Copyright © 2026, Oracle and/or its affiliates 11.2.0.4 12.1.0.2 12.2.0.1 19.22.0 23.26.0

Fleet Patching & Provisioning (FPP)はアウトオブプレース・パッチ適用を使用標準化とローリング・パッチ適用への道のり 24 Copyright © 2026,
Oracle and/or its affiliates インプレース・パッチ適用: • ロールバックは簡単で無い • ダウンタイム長い • プロセス複雑 • エラー発生 • 標準化は適用されないアウトオブプレース・パッチ適用 • ロールバックが簡単 • ダウンタイムが短縮 • SWバイナリを1回構築したらあらゆる場所で使用可能 • 計画が容易 • 組み込まれた標準化 ORACLE 推奨 UP UP UP UP DOWN DOWN DOWN DOWN UP UP UP UP STOP ALL SERVICES UP PATCH BINARIES PATCH DBs UP UP UP UP DOWN DOWN DOWN DOWN UP UP UP UP INSTALL NEW BINARIES STOP, MOVE, PATCH ONE BY ONE

dbca autoupgrade srvctl Fleet Patching and Provisioning patchmgr 複雑さの解消既存ツールを単一のフローで活用
25 Copyright © 2025, Oracle and/or its affiliates datapatch opatch gridSetup runInstaller dbua lsinventory 単一の入口（エントリポイント） rhpctl add / move / import パッチの問合せに使用 FPPで使用

Exadata Fleet Update 新機能一覧

Guest VMのOS更新をサポートし、OSとGIを一緒に更新可能に • Collection・タイプとしてGuest OS Exadata System Software とExaDB Stackが追加
• Guest OS Exadata System Software: 従来のGrid Infrastructureの更新、Databaseへの更新と同様に、Guest VM OSの更新をサポート • ExaDB Stack : Guest OSとGIを一緒に更新可能に。同一フローで適用することにより、DBインスタンスの停止回数を削減、メンテナンスによる影響・停止時間を短縮 Blog : Exadata Fleet UpdateのGuest OSとExaDB StackCollectionのご紹介 https://blogs.oracle.com/oracle4engineer/post/ja-update-guestos-and-exadb-stack-with-exadata-fleet-update 27 Copyright © 2026, Oracle and/or its affiliates Enhanced ExaDB Stack Updates for Exadata Infrastructure 2025/10

Guest VMのOS更新をサポートし、OSとGIを一緒に更新可能に Enhanced ExaDB Stack Updates for Exadata Infrastructure 28
Copyright © 2026, Oracle and/or its affiliates Virtual Machine Exadata OS Image Updated Grid Infrastructure Updated Virtual Machine Exadata OS Image データベース・インスタンス Grid Infrastructure Guest OS アップデート GIアップデート ExaDB Stack Guest OS + GIアップデート Component update ExaDB Stack update Grid Infrastructure アップデート仮想マシン Exadata OSイメージのアップデート Guest OS + GI = ExaDB Stack アップデートの統合 • データベースの中断を最小限に抑え、運用リスクを低減 • Guest OSとGIの更新が一緒に適用 • Guest OSとGIの両方の更新が適用されると、データベース・インスタンスを再起動 DBアップデート 2025/10

Exadata Fleet Updateを利用してDBやGIを19cから26aiにアップグレードすることが可能 • 制限事項 • データベースのアップグレード - 常にデータベースに対してノンローリングで実施 •
GIアップグレード機能 - 24時間以内にExadataインフラストラクチャのメンテナンス操作がスケジュールされている場合利用不可能 • バージョン制限： - Collectionですでに使用しているのと同じメジャーバージョンへのアップグレードは不可能 - Oracle Databaseを19cから26aiへアップグレードする場合 • Exadata System Softwareが推奨される最小バージョン以降で稼働している必要がある。 - 推奨されるExadataソフトウェアの最低バージョンは24.1.0.0.0 最新の推奨バージョンはMy Oracle Support (MOS) Note 888828.1を参照 • Supplemental READMEで推奨されるExadataソフトウェアバージョンを確認し、 Oracle Grid InfrastructureおよびOracle Databaseの最小必要バージョン詳細を確認すること • 最初にOracle Grid Infrastructureを26aiへアップグレードする必要がある • これらのガイドラインに従うことで、ダウンタイムが伴うものの影響を最小限に抑えつつ Oracle DatabaseおよびGrid Infrastructureターゲットを26aiへアップグレードできる (Blog:英) Exadata Fleet Update Now Supports Exadata Database Service Upgrades! (Blog:日) Exadata Fleet UpdateがExadata Database Serviceのアップグレードをサポート！ 29 Copyright © 2026, Oracle and/or its affiliates Upgrade a Collection of Oracle Database and Oracle Grid Infrastructure Targets to 26ai 2025/07

Exadata Fleet Updateを利用してDBやGIを19cから26aiにアップグレードすることが可能 • 適用アップグレードアクションで失敗したターゲットのロールバックと削除 • Apply Upgrade Action中に1つ以上のターゲットで失敗が発生した場合、Rollback and
Remove Actionを実施することで復旧可能。このアクションでは： - - 失敗したターゲットをFsuCollectionから削除 - - アップグレードサイクル開始前のバージョンに戻す • クリーンなロールバックが保証され、安定した状態で再度アップグレードを試行可能に • アップグレードが成功した後のロールバックは自動化されていない - データベースを以前のリリースに手動でダウングレードする場合は「Downgrading Oracle Database to an Earlier Release」を参照 30 Copyright © 2026, Oracle and/or its affiliates Upgrade a Collection of Oracle Database and Oracle Grid Infrastructure Targets to 26ai 2025/07

ターゲットに適用したアップデートのロールバック Rollback Updates Applied to the Targets • ロールバックは、サイクルが正常に完了しており、クリーンアップアクションが実行済みでない、または進行中でない場合にのみ可能 •
ロールバック実施後は、ロールバック対象パッチに対するクリーンアップ操作は手動で行う必要がある • 例：パッチアップデートのロールバック • アップデートの適用（19.21→19.23）： - アップデートサイクルを開始すると、現環境はPatch 19.21からPatch 19.23に移行。 - Apply Updateが正常完了すると、Cleanupアクションの実行が可能になる - 問題がなければシステムは19.23で稼働し、Cleanup実行により19.21関連の残データを削除可能になる • ロールバックサイクルの開始： - 19.23で問題や非互換が生じた場合、Rollback Cycle（RC）を開始して元のPatch 19.21へ戻すことが可能 - ロールバック処理中は元バージョン（19.21）関連の全データ保持が必須となるため、Cleanupは無効（グレーアウト）となり、必要なデータの早期削除が防止される • ロールバックサイクル完了後： - ロールバックが完了するとシステムはPatch 19.21へ戻り、Cleanupアクションは引き続き利用不可になる • Cleanupは新規適用時（19.21→19.23）にのみ有効になる - ロールバックで戻ったアップデート（19.23）に関するデータは自動管理されないため、不要な依存やリソース消費を避けるには19.23に関連するデータや環境は手動でクリーンアップが必要 31 Copyright © 2026, Oracle and/or its affiliates 2024/11

Collection type毎の Apply Upgrade、Rollbackの可否 Rollback Updates Applied to the Targets
Collection type 例 Apply Upgrade Rollback 補足 Database Update DBRU適用 ◦ ◦ DBHOMEをmove Grid Infrastructure Update GIRU適用 ◦ ◦ GIHOMEをmove Database Upgrade 19c→26ai ◦ アップグレード失敗時のみ実行可能アップグレード成功時は非対応 ESS 24以降 GI26ai以降 Grid Infrastructure Upgrade 19c→26ai ◦ アップグレード失敗時のみ実行可能アップグレード成功時は非対応 ESS 24以降 Guest VM OS system ESS 23.1 → ESS 25.1 ◦ 非対応 FPPではrollback対応しているので今後のロールバック対応に期待 ExaDB Stack ESS 23.1 → ESS 25.1 と GI RU 適用 ◦ 非対応 32 Copyright © 2026, Oracle and/or its affiliates

Oracle DatabaseおよびGrid Infrastructureバージョン26aiにおけるターゲットのCollectionを作成、パッチ適用 Create or Patch a Collection of
Targets with Oracle Database and Grid Infrastructure Version 26ai • Oracle Database 26aiに対してすべてのライフサイクル操作が実行可能に 33 Copyright © 2026, Oracle and/or its affiliates 2024/09

Patch a Fleet of Clusters with a Custom Grid Infrastructure
Image • 事前に作成したGrid InfrastructureのCustomイメージをターゲット・イメージとして選択できるようになりました [Blog] Introducing Incident and trace collection and, custom Grid Infrastructure images in Exadata Fleet Update https://blogs.oracle.com/maa/post/exadata-fleet-update-new-features-opt-in-custom-gi Grid Infrastructureへのパッチ適用時にカスタム・イメージを利用可能に Copyright © 2026, Oracle and/or its affiliates 34 2024/07

Enable Incident Logs and Trace Collection • メンテナンス・サイクルの作成、編集画面から、自動診断収集の有効化が可能に •
デフォルトは自動診断収集有効化 • メンテナンス・サイクル時だけ有効化も可能 [Blog] Introducing Incident and trace collection and, custom Grid Infrastructure images in Exadata Fleet Update https://blogs.oracle.com/maa/post/exadata-fleet- update-new-features-opt-in-custom-gi 自動診断収集(ログやトレース)の有効化 Copyright © 2026, Oracle and/or its affiliates 35 2024/07

Copyright © 2026, Oracle and/or its affiliates 36 Exadata Fleet
Update • 利用開始の前提条件 • Collections の管理（DB） • Maintenance Cycles の管理（DB） • Grid Infrastructure の場合の Collections、Maintenance Cycle の管理 • Database Upgrade • Grid Infrastructure Upgrade • Guest OS Exadata system • ExaDB Stack • Topics、Rulesの設定

Exadata Fleet Update 利用開始時の前提条件 • ネットワーク設定 • Collection（コレクション）の管理に必要なIAMポリシー • Maintenance
Cycle（メンテナンス・サイクル）の管理に必要なIAMポリシー 38 Copyright © 2026, Oracle and/or its affiliates

利用開始時の前提条件 Collection の管理必要なネットワーク設定 Exadata Fleet Update Copyright © 2026,
Oracle and/or its affiliates 39 Security List > Ingress Rules Add Ingress Rules 利用しているVCN

Oracle and/or its affiliates 40 Stateless: No (all rules must be stateful) Source Type: CIDR Source CIDR: Client subnet's CIDR IP Protocol: TCP Source Port Range: All Destination Port Range: 7085

Oracle and/or its affiliates 41 作成された Security List

利用開始時の前提条件 Collection の管理 IAM Policies の設定 Resource-Types • 集約リソース・タイプ •
fleet-software-update-family • 個々のリソース・タイプ • fleet-software-update-discoveries • fleet-software-update-collections • fleet-software-update-cycles • fleet-software-update-actions • fleet-software-update-jobs • fleet-software-update-work-requests • fleet-software-update-images • fleet-software-update-homes Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 42

利用開始時の前提条件 Collection の管理 IAM Policies の設定 Dynamic Groups Exadata Fleet
Update Copyright © 2026, Oracle and/or its affiliates 43 作成済みの Dynamic Group を利用

利用開始時の前提条件 Collection の管理 IAM Policies の設定 Exadata Fleet Update Collection
の管理に必要なポリシー allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-discoveries in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-collections in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to read fleet-software-update-work-requests in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to inspect database-software-images in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to inspect db-homes in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to inspect databases in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to inspect cloud-exadata-infrastructures in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to inspect db-nodes in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use cloud-vmclusters in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use vcns in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use subnets in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use vnics in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use private-ips in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use network-security-groups in compartment exadatacloud Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 44

利用開始時の前提条件 Maintenance Cycle の管理 IAM Policies の設定 Maintenance Cycle の管理に必要なポリシー
allow dynamic-group project-exadatacloud_dynamic_group to read db-nodes in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use database-software-images in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage db-homes in compartment exadatacloud where any {request.permission='DB_HOME_CREATE', request.permission='DB_HOME_UPDATE', request.permission='DB_HOME_INSPECT'} allow dynamic-group project-exadatacloud_dynamic_group to manage databases in compartment exadatacloud where any {request.permission='DATABASE_CREATE', request.permission='DATABASE_UPDATE', request.permission='DATABASE_INSPECT'} allow dynamic-group project-exadatacloud_dynamic_group to use cloud-vmclusters in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use vcns in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use subnets in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use vnics in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to use private-ips in compartment exadatacloud allow service fppcsprod to use cloud-vmclusters in compartment exadatacloud Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 48

利用開始時の前提条件 Maintenance Cycle の管理 IAM Policies の設定 Maintenance Cycle のCleanupに必要なポリシー
allow dynamic-group project-exadatacloud_dynamic_group to manage db-homes in compartment exadatacloud where request.permission='DB_HOME_DELETE' allow dynamic-group project-exadatacloud_dynamic_group to manage databases in compartment exadatacloud where request.permission='DATABASE_DELETE' マニュアルを読み飛ばしがちなので注意！ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 51

利用開始時の前提条件 Maintenance Cycle の管理 IAM Policies の設定 Maintenance Cycle、アクションリソース管理の付与 allow
dynamic-group project-exadatacloud_dynamic_group to use fleet-software-update-collections in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-cycles in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-actions in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-jobs in compartment exadatacloud allow dynamic-group project-exadatacloud_dynamic_group to manage fleet-software-update-work-requests in compartment exadatacloud allow group project-exadatacloud_dynamic_group to use database-software-images in compartment exadatacloud allow group project-exadatacloud_dynamic_group to manage db-homes in compartment exadatacloud allow group project-exadatacloud_dynamic_group to use cloud-vmclusters in compartment exadatacloud allow group project-exadatacloud_dynamic_group to manage databases in compartment exadatacloud where any {request.permission='DATABASE_CREATE', request.permission='DATABASE_UPDATE', request.permission='DATABASE_INSPECT'} allow group project-exadatacloud_dynamic_group to use vmclusters in compartment exadatacloud allow group project-exadatacloud_dynamic_group to inspect exadata-infrastructures in compartment exadatacloud Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 54

利用開始時の前提条件 Maintenance Cycle の管理 IAM Policies の設定 Maintenance Cycle、アクションリソース管理の付与 Exadata
Fleet Update Copyright © 2026, Oracle and/or its affiliates 55 Create Policy Policy

利用開始時の前提条件 Maintenance Cycle の管理 IAM Policies の設定 Maintenance Cycle、アクションリソース管理の付与 Exadata
Fleet Update Copyright © 2026, Oracle and/or its affiliates 56 Policy

Collection の管理 Collection の作成 Exadata Fleet Update Copyright © 2026,
Oracle and/or its affiliates 58 Oracle AI Database Exadata Fleet Update

Oracle and/or its affiliates 59 Collections Create collection

Oracle and/or its affiliates 60 Collection type: • Database software update • Grid Infrastructure software update • Guest OS Exadata system software update • ExaDB Stack (Guest OS Exadata system and Grid Infrastructure) software update （赤字が新機能）

Oracle and/or its affiliates 61 Collection type: 前ページ Cloud service: Oracle Exadata Database Service on Cloud@Customer (ExaDB- C@C) Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D) どちらか選択 Current major version: Collection内のターゲットは同じバージョンである必要があるが、異なるパッチ・レベルにすることが可能） (DB, GI の時のみ表示される。Guest OS、ExaDB Stack の際は表示されない

Oracle and/or its affiliates 62 Edit search criteria 対象のデータベースの検索基準この例では VMCluster5上の DB19.26を検索 Include targets already in an active maintenance cycle in another collection: 別のCollectionにすでにアクティブなメンテナンス・サイクルにあるターゲットを追加する場合は、このチェック・ボックスを選択各ターゲットは、一度に1つのアクティブなメンテナンス・サイクルにのみ属することができる。別のCollectionでアクティブなメンテナンス・サイクルにすでに存在するターゲットを追加しても、他のメンテナンス・サイクルが完了するか、またはこれらのターゲットがCollectionから削除されるまで、メンテナンス・サイクルは作成できない Apply Edit search criteria

Oracle and/or its affiliates 63 検索結果の候補 DB0408 現在 19.26.0.0 が対象 Create

Oracle and/or its affiliates 64 Collection 作成された

Oracle and/or its affiliates 65 Collection Information

Oracle and/or its affiliates 66 Collection Targets ターゲットに登録された対象 DB0408を確認出来る

Maintenance Cycle の管理 Maintenance Cycle の作成 Exadata Fleet Update Copyright
© 2026, Oracle and/or its affiliates 68 Maintenance cycle Collections Create Maintenance cycle

© 2026, Oracle and/or its affiliates 71 Update適用するバージョン 19.27.0.0 が選択された Database Home Create new home 新しいDBHOMEを作成 Use existing home 選択したイメージの既存のホームがターゲット・データベースの VMクラスタに見つからない場合は、新しいDBHOMEが作成される。選択したイメージの複数の既存のDBホームが見つかった場合は、データベース数が最も少ない DBHOMEが使用される。複数のホームにデータベース数が最も少ない場合、DBHOME はランダムに選択される。

© 2026, Oracle and/or its affiliates 72 Maintenance Method 適用方式 • One node at a time (rolling): • (Default) • 50/50 (rolling): • VMの半分にあるデータベース・インスタンスは、1つのバッチで更新され、残りの半分は別のバッチで更新される。 2つのバッチは、データベース・サービスの構成によって決まります。これにより、すべてのサービスが使用可能になる • Enable one batch at a time: • 一度に1つのバッチに更新を適用するには、このチェック・ボックスを選択します。適用アクションでは、 1つ目のバッチの更新を適用すると、2つ目のバッチを開始する前に、続行が待機される • Non-rolling: • Smart batch (rolling): • データベース・インスタンスは、一度に 1つ以上のVMで更新されます。 VMは、構成されたデータベース・サービスに基づいてバッチされる。これにより、必要なバッチの合計数を最小限に抑えながら、複数のノードにすべてのサービスを構成しているかぎり、すべてのサービスが使用可能になる Incident Logs and Trace Collection: 障害診断および問題解決を可能にするためにOracleがインシデント・ログおよびトレースを収集この構成に対する変更は、メンテナンス・サイクルのすべてのアクションがスケジュール済状態の場合にのみサポート。メンテナンス・サイクルのアクションが開始されると、この設定を変更することは不可能。推奨事項:この設定を有効

© 2026, Oracle and/or its affiliates 73 Database start/stop options: Maximum drain timeout (in seconds): ノード間のドレイン・タイムアウトを秒単位で指定。これは、ローリング更新中に使用され、データベース接続の再配置の時間を提供する。使用されるドレイン・タイムアウトは、この値の最大値、または特定のインスタンスで実行されているサービスの最大構成ドレイン・タイムアウトになる。デフォルトは600。 Keep service placement: 有効にすると、データベース・サービスは、更新を適用アクションの前に配置にリストアされる Software update options: Ignore missing bug fixes ソース・ホームに存在するバグ修正のパッチがターゲット・ホームにない場合でも、ソフトウェア更新の一環として移動が実行 Force rolling patch 非ローリング・パッチであっても、パッチ操作が強制的にローリング方式で実行される

Maintenance Cycle の管理アクションの実行 Precheck Exadata Fleet Update Copyright ©
2026, Oracle and/or its affiliates 75 Maintenance Cycle Precheck Stage Software Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Apply Updates Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1つ)

Maintenance Cycle の管理アクションの実行 Precheck Exadata Fleet Update Copyright ©
2026, Oracle and/or its affiliates 76 Precheck prior to staging software

Maintenance Cycle の管理アクションの実行 Precheck(stage) Exadata Fleet Update Copyright ©
2026, Oracle and/or its affiliates 77 Precheck prior to staging software Run precheck now

2026, Oracle and/or its affiliates 78 Actions Precheck (stage) Succeeded クリックするとjobの詳細を確認可能

2026, Oracle and/or its affiliates 79 Precheck(stage) Precheck Succeeded した job の内容

2026, Oracle and/or its affiliates 80 ログを見たいとき View log Precheck Succeeded した job の内容

2026, Oracle and/or its affiliates 81 下にスクロール次ページに続く

2026, Oracle and/or its affiliates 82 次ページ次ページ

Maintenance Cycle の管理アクションの実行 Precheck(stage) precheck成功時のログ ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client:
fppcsdp-ad1-prod-1 Scheduled job command: "rhpctl add workingcopy -eval -targetnode goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com -skipclone -user oracle -image db-DscQDDB8EVvKKdvz16UTMoGULZUL2wlq-20251029015034 -schedule 2025- 10-29T01:53:45Z -workingcopy wc_z5zURucfvLnHF2wJDfVbxRDvNOL5Lozj_20251029015035 -direct -skipcopy -checkwcpatches -auth restauth -oraclebase /u02/app/oracle -groups OSDBA=dba,OSOPER=racoper,OSBACKUP=dba,OSDG=dba,OSKM=dba,OSRAC=dba -json -sourcehome /u02/app/oracle/product/19.0.0.0/dbhome_1 -path /u02/app/oracle/product/ -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137805 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137804 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137803" Job execution start time: 2025-10-29 01:53:51 Job execution end time: 2025-10-29 01:56:06 Job execution elapsed time: 2 minutes 15 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= 2025-10-29 01:54:40.048 UTC : Evaluation in progress for "add workingcopy" ... 2025-10-29 01:55:59.842 UTC : Warning: Image "db-DscQDDB8EVvKKdvz16UTMoGULZUL2wlq-20251029015034" is missing the patches for bug numbers "34672698,34697081,37213431,37102264,37497089,37260974", which are present in the source Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1". 2025-10-29 01:55:59.842 UTC : Option storagetype is set to the following default value: LOCAL. 2025-10-29 01:56:06.735 UTC : Evaluation finished successfully for "add workingcopy". Job has completed with warnings. Review the output messages before continuing with the next action. Fleet Patching and Provisioning の rhpctl コマンドが実行されているのが分かる Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 83

Stage Software Jobs (one each Target) Jobs (one each Target)
Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Apply Updates Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Maintenance Cycle の管理アクションの実行 Stage software Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 84 Maintenance Cycle Stage software

Maintenance Cycle の管理アクションの実行 Stage software Exadata Fleet Update Copyright
© 2026, Oracle and/or its affiliates 85 Stage software Stage now

Maintenance Cycle の管理アクションの実行 Apply update 実行前の環境 ORACLE_HOME [oracle@goro-sx2zy2 ~]$
env | grep ORA ORACLE_UNQNAME=DB0408_qg7_kix ORACLE_SID=DB04082 ORACLE_BASE=/u02/app/oracle ORACLE_HOME=/u02/app/oracle/product/19.0.0.0/dbhome_1 ORACLE_HOSTNAME=goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com [oracle@goro-sx2zy2 ~]$ [oracle@goro-sx2zy2 ~]$ cat /etc/oratab #Backup file is /u01/app/grid/crsdata/goro-sx2zy2/output/oratab.bak.goro-sx2zy2.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0408_qg7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM2:/u02/app/23.0.0.0/gridhome_1:Y [oracle@goro-sx2zy2 ~]$ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 93

Maintenance Cycle の管理アクションの実行 Apply update Exadata Fleet Update Copyright
© 2026, Oracle and/or its affiliates 94 Apply update Stage Software Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Apply Updates Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ) Precheck Jobs (one each Target) Jobs (one each Target) Jobs (one each Target) ジョブ(ターゲットごとに1 つ)

Maintenance Cycle の管理アクションの実行 Apply update ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client:
clu5 Scheduled job command: "rhpctl move database -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -patchedwc wc_rDTpN1mgkwZmTyaFzdV9wrhOHSXsDYpi_20251029023923 -auth restauth -dbname DB0408_qg7_kix -drain_timeout 600 -json -sourcewc wc_nBp3xVRxU6gb7Ufxl2wvn74fQwDXWFYf_20251029023939 -schedule 2025-10-29T03:12:54Z -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137819 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 766137818 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137817" Job execution start time: 2025-10-29 03:13:21 Job execution end time: 2025-10-29 03:42:32 Job execution elapsed time: 29 minutes 11 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= Fleet Patching and Provisioning の rhpctl コマンドが実行されているのが分かる Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 98

Maintenance Cycle の管理アクションの実行 Apply update ORACLE_HOMEのMOVE 2025-10-29 03:20:58.665 UTC
: starting to move the following databases: "DB0408_qg7_kix" 2025-10-29 03:20:58.666 UTC : starting to move the following databases: "DB0408_qg7_kix" 2025-10-29 03:20:58.731 UTC : moving databases: "DB0408_qg7_kix" on nodes: "goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com" 2025-10-29 03:21:01.927 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 03:21:25.930 UTC : copying database configuration files from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" ... 2025-10-29 03:22:38.063 UTC : retrieving status of services of databases "DB0408_qg7_kix" ... 2025-10-29 03:22:44.428 UTC : relocating services of databases "DB0408_qg7_kix" ... 2025-10-29 03:22:50.740 UTC : stopping services of databases "DB0408_qg7_kix" ... 2025-10-29 03:23:00.396 UTC : stopping instances of databases "DB0408_qg7_kix" ... 2025-10-29 03:23:54.413 UTC : starting instances of databases "DB0408_qg7_kix" ... 2025-10-29 03:24:43.134 UTC : moving databases: "DB0408_qg7_kix" on nodes: "goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com" 2025-10-29 03:24:43.137 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 03:24:57.125 UTC : copying database configuration files from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" ... 2025-10-29 03:26:10.743 UTC : relocating services of databases "DB0408_qg7_kix" ... 2025-10-29 03:26:18.389 UTC : stopping services of databases "DB0408_qg7_kix" ... 2025-10-29 03:26:28.041 UTC : stopping instances of databases "DB0408_qg7_kix" ... 2025-10-29 03:27:13.932 UTC : starting instances of databases "DB0408_qg7_kix" ... 2025-10-29 03:27:58.468 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 03:28:17.615 UTC : Checking datapatch execution requirement for database 'DB0408_qg7_kix' ... 2025-10-29 03:34:22.406 UTC : Datapatch executed succesfully for DB 'DB0408_qg7_kix' ... 2025-10-29 03:34:22.425 UTC : Checking datapatch execution requirement for database 'DB0408_qg7_kix' ... 2025-10-29 03:40:27.136 UTC : Datapatch executed succesfully for DB 'DB0408_qg7_kix' ... 2025-10-29 03:40:27.196 UTC : Executing "mcpostpatch" script on nodes "goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com"... 2025-10-29 03:42:03.478 UTC : Done executing "mcpostpatch" script... Databases moved from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" : "DB0408_qg7_kix" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 99

Maintenance Cycle の管理アクションの実行 Apply update後のORACLE_HOME [oracle@goro-sx2zy2 ~]$ env |
grep ORA ORACLE_UNQNAME=DB0408_qg7_kix ORACLE_SID=DB04082 ORACLE_BASE=/u02/app/oracle ORACLE_HOME=/u02/app/oracle/product/19.0.0.0/dbhome_4 ORACLE_HOSTNAME=goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com [oracle@goro-sx2zy2 ~]$ cat /etc/oratab #Backup file is /u02/app/oracle/product/19.0.0.0/dbhome_4/srvm/admin/oratab.bak.goro-sx2zy2 line added by RHP #Backup file is /u01/app/grid/crsdata/goro-sx2zy2/output/oratab.bak.goro-sx2zy2.oracle line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # +ASM2:/u02/app/23.0.0.0/gridhome_1:Y DB0408_qg7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_4:Y [oracle@goro-sx2zy2 ~]$ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 100

Maintenance Cycle の管理アクションの実行 Rollback Exadata Fleet Update Copyright ©
2026, Oracle and/or its affiliates 104 Cleanup Apply update アクションが成功すると、メンテナンス・サイクルは「Succeeded」状態に移行し、 Cleanup アクションが使用可能になる。Cleanup 処理は、メンテナンス・サイクルでのオプションの処理。メンテナンス・サイクルが正常に完了した後、Cleanup アクションを実行して、メンテナンス・サイクルのソースの DBHOME およびGrid Infrastructure HOMEを削除。すぐにクリーンアップを実行またはクリーンアップをスケジュール可能。 Rollback

2026, Oracle and/or its affiliates 105 当該Collection名を入力してRollback update

2026, Oracle and/or its affiliates 106 Rollback update

2026, Oracle and/or its affiliates 107 Rollback update Succeeded

2026, Oracle and/or its affiliates 108 Rollback完了後は Actionsメニューから Rollbackは消える。 Cleanupは選択できなくなる

2026, Oracle and/or its affiliates 109 Rollback update Action information

2026, Oracle and/or its affiliates 110 Rollback update Jobs

2026, Oracle and/or its affiliates 111 Rollback update Jobs view logs

Maintenance Cycle の管理アクションの実行 Rollback ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: clu5
Scheduled job command: "rhpctl move database -targetnode goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com -dbname DB0408_qg7_kix -sourcewc wc_rDTpN1mgkwZmTyaFzdV9wrhOHSXsDYpi_20251029023923 -schedule 2025-10- 29T04:16:24Z -direct -patchedwc wc_nBp3xVRxU6gb7Ufxl2wvn74fQwDXWFYf_20251029023939 -auth restauth -ignorewcpatches -drain_timeout 600 -json -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137822 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137821 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137820" Job execution start time: 2025-10-29 04:16:52 Job execution end time: 2025-10-29 04:45:54 Job execution elapsed time: 29 minutes 1 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= 2025-10-29 04:25:39.716 UTC : starting to move the following databases: "DB0408_qg7_kix" 2025-10-29 04:25:39.716 UTC : starting to move the following databases: "DB0408_qg7_kix" 2025-10-29 04:25:39.761 UTC : moving databases: "DB0408_qg7_kix" on nodes: "goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com" 2025-10-29 04:25:42.953 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 04:26:13.369 UTC : copying database configuration files from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" ... 2025-10-29 04:26:49.478 UTC : retrieving status of services of databases "DB0408_qg7_kix" ... 2025-10-29 04:26:57.148 UTC : relocating services of databases "DB0408_qg7_kix" ... 2025-10-29 04:27:05.048 UTC : stopping services of databases "DB0408_qg7_kix" ... 2025-10-29 04:27:15.454 UTC : stopping instances of databases "DB0408_qg7_kix" ... 2025-10-29 04:28:08.965 UTC : starting instances of databases "DB0408_qg7_kix" ... 2025-10-29 04:28:50.542 UTC : moving databases: "DB0408_qg7_kix" on nodes: "goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com" 2025-10-29 04:28:50.546 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 04:29:04.667 UTC : copying database configuration files from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" ... 2025-10-29 04:29:40.803 UTC : relocating services of databases "DB0408_qg7_kix" ... 2025-10-29 04:29:46.916 UTC : stopping services of databases "DB0408_qg7_kix" ... 2025-10-29 04:29:53.187 UTC : stopping instances of databases "DB0408_qg7_kix" ... 2025-10-29 04:30:36.996 UTC : starting instances of databases "DB0408_qg7_kix" ... 2025-10-29 04:31:15.301 UTC : retrieving status of databases "DB0408_qg7_kix"... 2025-10-29 04:31:37.648 UTC : Checking datapatch execution requirement for database 'DB0408_qg7_kix' ... 2025-10-29 04:37:42.087 UTC : Datapatch executed succesfully for DB 'DB0408_qg7_kix' ... 2025-10-29 04:37:42.097 UTC : Checking datapatch execution requirement for database 'DB0408_qg7_kix' ... 2025-10-29 04:43:46.742 UTC : Datapatch executed succesfully for DB 'DB0408_qg7_kix' ... 2025-10-29 04:43:46.795 UTC : Executing "mcpostpatch" script on nodes "goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com"... 2025-10-29 04:45:24.993 UTC : Done executing "mcpostpatch" script... Databases moved from Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_4" to Oracle home "/u02/app/oracle/product/19.0.0.0/dbhome_1" : "DB0408_qg7_kix" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 112

Maintenance Cycle の管理アクションの実行 Rollback dbhome_1 に戻っていることを確認 [oracle@goro-sx2zy2 ~]$ .
DB0408.env [oracle@goro-sx2zy2 ~]$ env | grep ORA ORACLE_UNQNAME=DB0408_qg7_kix ORACLE_SID=DB04082 ORACLE_BASE=/u02/app/oracle ORACLE_HOME=/u02/app/oracle/product/19.0.0.0/dbhome_1 ORACLE_HOSTNAME=goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com [oracle@goro-sx2zy2 ~]$ cat /etc/oratab #Backup file is /u02/app/oracle/product/19.0.0.0/dbhome_1/srvm/admin/oratab.bak.goro-sx2zy2 line added by RHP #Backup file is /u01/app/grid/crsdata/goro-sx2zy2/output/oratab.bak.goro-sx2zy2.oracle line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # +ASM2:/u02/app/23.0.0.0/gridhome_1:Y DB0408_qg7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y [oracle@goro-sx2zy2 ~]$ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 113

Grid Infrastructureの場合のCollections, Maintenance Cycle Exadata Fleet Update Copyright © 2026,
Oracle and/or its affiliates 129 Create collection

Oracle and/or its affiliates 130 Collection type Grid Infrastructure software update を選択 Edit search criteria

Oracle and/or its affiliates 131 Edit search criteria Grid infrastructure release update に表記が変わる

Oracle and/or its affiliates 132 VMCluster-3が選択されている

Oracle and/or its affiliates 133 Maintenance Cycle 作成された Collection

Oracle and/or its affiliates 134 Maintenance Cycle Create Maintenance Cycle 作成された Collection

Oracle and/or its affiliates 135 Create maintenance cycle Change grid infrastructure image

Oracle and/or its affiliates 136 Target Grid Infrastructure Image 23.9（Exadata Fleet Update でサポートされているバージョン。マニュアルには記載ないので注意）

Oracle and/or its affiliates 137 Target Grid Infrastructure Image 23.9（Exadata Fleet Update でサポートされているバージョン。マニュアルには記載ないので注意）

Oracle and/or its affiliates 138 Target Grid Infrastructure version: 23.9 Precheck

Oracle and/or its affiliates 139 Precheck prior to staging software Run precheck now Run

Oracle and/or its affiliates 140 Precheck(stage) Succeeded View log

Oracle and/or its affiliates 141 View log rhpctl add workingcopyコマンド

Oracle and/or its affiliates 142 Precheck(stage) Succeeded Stage software

Oracle and/or its affiliates 143 Stage software

Oracle and/or its affiliates 144 Stage software Succeeded Jobs

Oracle and/or its affiliates 145 View Log

Oracle and/or its affiliates 151 Precheck(apply) Succeeded Apply update

Oracle and/or its affiliates 152 Apply software updates

Grid Infrastructureの場合のCollections, Maintenance Cycle Update前 [grid@jiro-1koqp1 ~]$ cat /etc/oratab #Backup
file is /u01/app/grid/crsdata/jiro-1koqp1/output/oratab.bak.jiro-1koqp1.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0411_7d7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y EMTEST_2ts_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y DB1014_fx4_kix:/u02/app/oracle/product/19.0.0.0/dbhome_5:Y nocd1030:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM1:/u02/app/23.0.0.0/gridhome_2:N # line added by Agent [grid@jiro-1koqp1 ~]$ [grid@jiro-1koqp1 ~]$ ls -al /etc/oratab -rw-rw-r-- 1 grid oinstall 1133 Nov 4 11:35 /etc/oratab [grid@jiro-1koqp1 ~]$ date Tue Nov 4 11:36:25 JST 2025 Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 153

Oracle and/or its affiliates 155 Apply update: Succeeded

Grid Infrastructureの場合のCollections, Maintenance Cycle GIRU適用時はGIの再起動のみ、OS再起動無し、 [root@jiro-1koqp1 ~]# less /u01/app/grid/diag/crs/jiro-1koqp1/crs/trace/alert.log 2025-11-04
11:34:41.687 [OHASD(31825)] CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'jiro-1koqp1' 2025-11-04 11:35:08.657 [OHASD(31825)] CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'jiro-1koqp1' has completed [grid@jiro-1koqp1 ~]$ last reboot wtmp begins Sat Nov 1 10:16:45 2025 [grid@jiro-1koqp1 ~]$ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 156

Grid Infrastructureの場合のCollections, Maintenance Cycle GI_HOME は /u02 以下にmove [root@jiro-1koqp1 ~]#
cat /etc/oratab #Backup file is /u01/app/grid/crsdata/jiro-1koqp1/output/oratab.bak.jiro-1koqp1.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0411_7d7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y EMTEST_2ts_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y DB1014_fx4_kix:/u02/app/oracle/product/19.0.0.0/dbhome_5:Y nocd1030:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM1:/u02/app/23.0.0.0/gridhome_2:Y [root@jiro-1koqp1 ~]# [grid@jiro-1koqp1 ~]$ env | grep ORA ORACLE_SID=+ASM1 ORACLE_HOME=/u02/app/23.0.0.0/gridhome_2 ORACLE_HOSTNAME=jiro-1koqp1 Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 157

Grid Infrastructureの場合のCollections, Maintenance Cycle Grid の diagnostic_dest 変更無し [grid@jiro-1koqp1 ~]$
sqlplus / as sysasm SQL*Plus: Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems on Tue Nov 4 14:31:11 2025 Version 23.9.0.25.07 Copyright (c) 1982, 2025, Oracle. All rights reserved. Connected to: Oracle Database 23ai Enterprise Edition Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems Version 23.9.0.25.07 SQL> show parameter diag NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ diagnostic_dest string /u01/app/grid diagnostics_control string IGNORE SQL> Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 158

Oracle and/or its affiliates 159 Apply update: Log

Grid Infrastructureの場合のCollections, Maintenance Cycle ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: clu3 Scheduled
job command: "rhpctl move gihome -targetnode jiro-1koqp2.sub04210756190.exavcn.oraclevcn.com -auth restauth -destwc wc_k4nB87PyYeWYVxOKZkJ9xJs9L13fCHkh_20251031070029 -drain_timeout 600 -json -sourcewc wc_3gkaTIDceOWnRT1STQWwKndhskZTf44e_20251031035841 -schedule 2025-11- 04T02:27:15Z -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888517 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888516 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq- 1285888515" Job execution start time: 2025-11-04 02:27:42 Job execution end time: 2025-11-04 02:48:38 Job execution elapsed time: 20 minutes 56 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 160

Grid Infrastructureの場合のCollections, Maintenance Cycle、Rollback Exadata Fleet Update Copyright © 2026,
Oracle and/or its affiliates 161 Rollback のテストのため、 Gi 23.9 に 23.10 を適用

Grid Infrastructureの場合のCollections, Maintenance Cycle、Rollback 適用後、gridhome_2 が gridhome_3 に [grid@jiro-1koqp1 ~]$
env | grep ORA ORACLE_SID=+ASM1 ORACLE_HOME=/u02/app/23.0.0.0/gridhome_3 ORACLE_HOSTNAME=jiro-1koqp1 [grid@jiro-1koqp1 ~]$ cat /etc/oratab #Backup file is /u01/app/grid/crsdata/jiro-1koqp1/output/oratab.bak.jiro-1koqp1.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0411_7d7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y EMTEST_2ts_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y DB1014_fx4_kix:/u02/app/oracle/product/19.0.0.0/dbhome_5:Y nocd1030:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM1:/u02/app/23.0.0.0/gridhome_3:Y [grid@jiro-1koqp1 ~]$ ls -al /etc/oratab -rw-rw-r-- 1 grid oinstall 1110 Nov 5 11:02 /etc/oratab Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 162

Grid Infrastructureの場合のCollections, Maintenance Cycle、Rollback Exadata Fleet Update Copyright © 2026,
Oracle and/or its affiliates 163 Rollback

Oracle and/or its affiliates 164 Rollback Succeeded

Grid Infrastructureの場合のCollections, Maintenance Cycle、Rollback ロールバックでgridhome_2に戻る [grid@jiro-1koqp1 ~]$ env | grep
ORA ORACLE_SID=+ASM1 ORACLE_HOME=/u02/app/23.0.0.0/gridhome_2 ORACLE_HOSTNAME=jiro-1koqp1 [grid@jiro-1koqp1 ~]$ cat /etc/oratab #Backup file is /u01/app/grid/crsdata/jiro-1koqp1/output/oratab.bak.jiro-1koqp1.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0411_7d7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y EMTEST_2ts_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y DB1014_fx4_kix:/u02/app/oracle/product/19.0.0.0/dbhome_5:Y nocd1030:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM1:/u02/app/23.0.0.0/gridhome_2:Y [grid@jiro-1koqp1 ~]$ ls -al /etc/oratab -rw-rw-r-- 1 grid oinstall 1110 Nov 5 11:54 /etc/oratab Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 165

Oracle and/or its affiliates 166 RollbackするとCleanup は選べなくなる

Oracle and/or its affiliates 167 Rollbackのjob 30分くらい

Oracle and/or its affiliates 168 View Log

Grid Infrastructureの場合のCollections, Maintenance Cycle、Rollback rollbackもmoveしている ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: clu3
Scheduled job command: "rhpctl move gihome -targetnode jiro-1koqp1.sub04210756190.exavcn.oraclevcn.com -auth restauth -ignorewcpatches -destwc wc_k4nB87PyYeWYVxOKZkJ9xJs9L13fCHkh_20251031070029 -drain_timeout 600 -json -sourcewc wc_UwoBJzoHN4rGNGYOcUlk4BAfzf2kPRtm_20251105010711 -schedule 2025-11- 05T02:33:55Z -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888538 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888537 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq- 1285888536" Job execution start time: 2025-11-05 02:34:22 Current status: EXECUTING =======================JOB_EXECUTION_DETAILS_END======================= Job ID: 390 Job ID: 390 Job ID: 390 ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: clu3 Scheduled job command: "rhpctl move gihome -targetnode jiro-1koqp1.sub04210756190.exavcn.oraclevcn.com -auth restauth -ignorewcpatches -destwc wc_k4nB87PyYeWYVxOKZkJ9xJs9L13fCHkh_20251031070029 -drain_timeout 600 -json -sourcewc wc_UwoBJzoHN4rGNGYOcUlk4BAfzf2kPRtm_20251105010711 -schedule 2025-11- 05T02:33:55Z -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888538 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888537 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq- 1285888536" Job execution start time: 2025-11-05 02:34:22 Job execution end time: 2025-11-05 02:54:56 Job execution elapsed time: 20 minutes 33 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 169

Grid Infrastructureの場合のCollections, Maintenance Cycle エラー例 GI 23.7適用 Exadata Fleet Update
Copyright © 2026, Oracle and/or its affiliates 178 GI 23.7 を適用する Maintenance Cycle Stage software Succeeded

Grid Infrastructureの場合のCollections, Maintenance Cycle エラー例 GI 23.7適用 Exadata Fleet Update
Copyright © 2026, Oracle and/or its affiliates 179 Grid Infrastructure 23.7 の Apply update で Failed Jobs のページで該当job の View log

Grid Infrastructureの場合のCollections, Maintenance Cycle エラー例 GI 23.7適用 com.oracle.bmc.model.BmcException: Error returned
by Unknown operation operation in Unknown service service.(400, InvalidParameter, false) Update operation failed. Only the following patchSet versions are supported : [19.29.0.0.0, 23.26.0.0.0, 23.9.0.25.07, 19.28.0.0.0]. (opc-request-id: ADC5FEF3CAA64FAF9342D51615010CC8/26071A97F557874351ED080200D6141D/527273D53177A6176689732E34962361) Timestamp: 2025-10-31T04:59:30.896Z Client version: Oracle-JavaSDK/2.81.1-preview1-SNAPSHOT Request Endpoint: Unknown request endpoint Troubleshooting Tips: See https://docs.oracle.com/en-us/iaas/Content/API/References/apierrors.htm#apierrors_400__400_invalidparameter for more information about resolving this error Also see Unknown API reference link for details on this operation's requirements. To get more info on the failing request, you can enable debug level logs as mentioned in `Using SLF4J for Logging section` in https://docs.oracle.com/en- us/iaas/Content/API/SDKDocs/javasdkconfig.htm. If you are unable to resolve this Unknown service issue, please contact Oracle support and provide them this full error message. GIRUのMaintenance Cycleサポート対象が 23.9 以降、23.7 は対象外。。 Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 180

Grid Infrastructureの場合のCollections, Maintenance Cycle エラー例 GI23.9→GI23.7へのロールバック Exadata Fleet Update Copyright
© 2026, Oracle and/or its affiliates 181 Rollback

Grid Infrastructureの場合のCollections, Maintenance Cycle エラー例 GI23.9→GI23.7へのロールバックロールバック時も対象バージョンの制限がある com.oracle.bmc.model.BmcException: Error returned
by Unknown operation operation in Unknown service service.(400, InvalidParameter, false) Update operation failed. Only the following patchSet versions are supported : [19.29.0.0.0, 23.26.0.0.0, 23.9.0.25.07, 19.28.0.0.0]. (opc-request-id: 728CD1E6527E49A384BF6EC796238B53/7C25780B97AF5DE0ABF98B0149F8C73A/2058C56F4309A9F1A26F8E741C9A249E) Timestamp: 2025-11-04T05:40:47.454Z Client version: Oracle- JavaSDK/2.81.1-preview1-SNAPSHOT Request Endpoint: Unknown request endpoint Troubleshooting Tips: See https://docs.oracle.com/en- us/iaas/Content/API/References/apierrors.htm#apierrors_400__400_invalidparameter for more information about resolving this error Also see Unknown API reference link for details on this operation's requirements. To get more info on the failing request, you can enable debug level logs as mentioned in `Using SLF4J for Logging section` in https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/javasdkconfig.htm. If you are unable to resolve this Unknown service issue, please contact Oracle support and provide them this full error message. Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 185

Database Upgrade Exadata Fleet Update Copyright © 2026, Oracle and/or
its affiliates 187 Create collection Collection type は Database software updateと同じ Database release update

its affiliates 188 Targets

its affiliates 189 Collection

its affiliates 190 Collectionに登録されたターゲットDB0408

its affiliates 191 Create maintenance cycle

its affiliates 192 Target database image Change database software image

its affiliates 193 ここでターゲットを 26ai を選択するとDatabase upgradeになる DB 23.9を選択

its affiliates 194 Target database image 23.9

its affiliates 195 Advanced options: Recompilation of invalid objects: データベースのアップグレード中に無効なオブジェクトの再コンパイルを有効または無効に（GI upgradeの再は Advanced options無し（No upgrade options are supported for Grid Infrastructure (GI) collection upgrades.） Time zone upgrade: Enables or disables the time zone upgrade. タイム・ゾーン・アップグレードでは、アップグレード中に停止時間が長くなる可能性あり

its affiliates 196 Upgradeのcollection

its affiliates 200 Precheck Succeeded

its affiliates 201 View log

Database Upgrade ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: fppcsdp-ad1-prod-1 Scheduled job command:
"rhpctl add workingcopy -eval -targetnode goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com -skipclone -user oracle -image db- U5ReO1Rf0enN9ql5A9oXJYmpCLEYX16P-20251029074712 -schedule 2025-10-29T07:50:16Z -workingcopy wc_ckkVcD1hzOsHTiI5j4iV6hrhMl6XIkOX_20251029074713 -direct -skipcopy -checkwcpatches -auth restauth -oraclebase /u02/app/oracle -groups OSDBA=dba,OSOPER=racoper,OSBACKUP=dba,OSDG=dba,OSKM=dba,OSRAC=dba -json -sourcehome /u02/app/oracle/product/19.0.0.0/dbhome_1 -path /u02/app/oracle/product/ -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap- osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137825 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137824 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 766137823" Job execution start time: 2025-10-29 07:50:23 Job execution end time: 2025-10-29 07:52:07 Job execution elapsed time: 1 minutes 44 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 202

its affiliates 203 Stage software

its affiliates 204 Stage now

its affiliates 205 Stage software Succeeded

Database Upgrade ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: fppcsdp-ad1-prod-1 Scheduled job command:
"rhpctl add workingcopy -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -skipclone -user oracle -image db- U5ReO1Rf0enN9ql5A9oXJYmpCLEYX16P-20251029074712 -schedule 2025-10-29T08:20:56Z -workingcopy wc_anQTaEroB6RZT12maLDbLQnayfGh9pLo_20251029081905 -direct -skipcopy -auth restauth -oraclebase /u02/app/oracle -groups OSDBA=dba,OSOPER=racoper,OSBACKUP=dba,OSDG=dba,OSKM=dba,OSRAC=dba -json -path /u02/app/oracle/product/23.0.0.0/dbhome_3 -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137828 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137827 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 766137826" Job execution start time: 2025-10-29 08:21:23 Job execution end time: 2025-10-29 08:23:16 Job execution elapsed time: 1 minutes 52 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 207

its affiliates 208 Apply upgrade

its affiliates 209 Apply upgrade now

its affiliates 210 Apply upgrade Succeeded

its affiliates 211 Apply upgrade Succeeded

Database Upgrade ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: clu5 Scheduled job command:
"rhpctl upgrade database -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -upgtimezone NO -auth restauth -dbname DB0408_qg7_kix -destwc wc_anQTaEroB6RZT12maLDbLQnayfGh9pLo_20251029081905 -json -sourcewc wc_nBp3xVRxU6gb7Ufxl2wvn74fQwDXWFYf_20251029023939 -schedule 2025-10- 30T01:23:02Z -direct -runutlrp YES -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137834 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-766137833 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 766137832" Job execution start time: 2025-10-30 01:23:29 Job execution end time: 2025-10-30 03:42:18 Job execution elapsed time: 2 hours 18 minutes 48 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= 略 2025-10-30 01:27:31.194 UTC : Starting autoupgrade prerequisites verification on node goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com ... 2025-10-30 01:27:33.343 UTC : Starting autoupgrade tool on node goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com ... Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 213

Database Upgrade Upgrade前 [oracle@goro-sx2zy2 ~]$ . DB0408.env [oracle@goro-sx2zy2 ~]$ cat
/etc/oratab #Backup file is /u02/app/oracle/product/19.0.0.0/dbhome_1/srvm/admin/oratab.bak.goro-sx2zy2 line added by RHP #Backup file is /u01/app/grid/crsdata/goro-sx2zy2/output/oratab.bak.goro-sx2zy2.oracle line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # +ASM2:/u02/app/23.0.0.0/gridhome_1:Y DB0408_qg7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y [oracle@goro-sx2zy2 ~]$ env | grep ORA ORACLE_UNQNAME=DB0408_qg7_kix ORACLE_SID=DB04082 ORACLE_BASE=/u02/app/oracle ORACLE_HOME=/u02/app/oracle/product/19.0.0.0/dbhome_1 ORACLE_HOSTNAME=goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 214

Database Upgrade Upgrade後 [oracle@goro-sx2zy2 ~]$ ls -lart total 32 -rw-r--r--
1 oracle oinstall 172 Apr 12 2024 .kshrc -rw-r--r-- 1 oracle oinstall 376 May 22 2024 .bashrc -rw-r--r-- 1 oracle oinstall 18 May 22 2024 .bash_logout drwxr-xr-x 8 root root 91 Apr 3 2025 .. -rw-r--r-- 1 oracle oinstall 155 Apr 3 2025 .bash_profile drwx------ 2 oracle oinstall 108 Apr 3 2025 .ssh -rwxrwx--- 1 oracle oinstall 649 Jul 24 03:14 tjk1925.env -rwxrwx--- 1 oracle oinstall 653 Aug 26 07:37 MNMNDB.env lrwxrwxrwx 1 oracle oinstall 23 Oct 29 03:41 DB0408_qg7_kix.env -> /home/oracle/DB0408.env -rwxrwx--- 1 oracle oinstall 692 Oct 30 03:41 DB0408.env drwx------ 3 oracle oinstall 190 Oct 30 03:41 . -rw------- 1 oracle oinstall 478 Oct 30 04:33 .bash_history [oracle@goro-sx2zy2 ~]$ date Thu Oct 30 04:34:01 UTC 2025 [oracle@goro-sx2zy2 ~]$ . DB0408.env [oracle@goro-sx2zy2 ~]$ env | grep ORA ORACLE_UNQNAME=DB0408_qg7_kix ORACLE_SID=DB04082 ORACLE_BASE=/u02/app/oracle ORACLE_HOME=/u02/app/oracle/product/23.0.0.0/dbhome_3 ORACLE_HOSTNAME=goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com [oracle@goro-sx2zy2 ~]$ Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 215

its affiliates 216 Database 23.9 新しいDBHOME

its affiliates 217 Database Upgrade 成功時は Rollback 出来ない

its affiliates 218 Cleanup

DB Database Upgrade Exadata Fleet Update Copyright © 2026, Oracle
and/or its affiliates 219 need attention

its affiliates 220 View log Starting Cleanup workflow for action ocid1.fsuaction.oc1.ap- osaka- 1.amaaaaaassl65iqargrde spwmuzy76p6idskuxot24 eb3bxjmezy63y6cvga The database home ocid1.dbhome.oc1.ap- osaka- 1.anvwsljrkrdj45ia46g4tc gk4uwpo4sbriup6g7ouqxd xy7brfdmdbyki7ma was not deleted because it is still in use by one or more databases. 他のDBでDBHOMEが利用中のためcleanup出来ない

Grid Infrastructure Upgrade Exadata Fleet Update Copyright © 2026, Oracle
and/or its affiliates 222 テスト対象 VMCluster1 Version Exadata image version 24.1.5.0.0.241016 Grid Infrastructure version 19.24.0.0.0

and/or its affiliates 223 Create collection

and/or its affiliates 224 Collection type Grid Infrastructure Grid Infrastructure release update

and/or its affiliates 225 Search criteria VMCluster1 を対象

and/or its affiliates 226 Collection

and/or its affiliates 227 Targets VMCluster1 19.24.0.0

and/or its affiliates 228 Maintenance cycles Create maintenance cycle

and/or its affiliates 229 Select a Grid Infrastructure image GI 23.9

and/or its affiliates 230 GI 23.9

and/or its affiliates 231 Maintenance cycle Target 23.9

and/or its affiliates 232 Precheck

and/or its affiliates 233 Run precheck now

and/or its affiliates 234 Precheck Succeeded

and/or its affiliates 235 Precheck Succeeded

and/or its affiliates 236 View log

Grid Infrastructure Upgrade 2025-12-15T02:30:00Z: Scheduled job command: "rhpctl register workingcopy
-targetnode vmc1-v4hra1.sub04210756190.exavcn.oraclevcn.com -auth restauth -json - image gi-T5x84lvFMr0hpfHC9n1XhAJs7yOXKQnr-20251215022451 -schedule 2025-12-15T02:27:57Z -workingcopy wc_K4jl0W5U20SdeGNkS8WuI6kRknZzhTva_20251215022450 -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q- 1495906973 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906974 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906978" 2025-12-15T02:30:01Z: Scheduled job command: "rhpctl add workingcopy -eval -targetnode vmc1-v4hra1.sub04210756190.exavcn.oraclevcn.com -auth restauth - softwareonly -json -image gi-o2NCRdGZEz2MZPFZUXVbzSGkaM7HrUnj-20251215022433 -sourcehome /u02/app/grid -schedule 2025-12-15T02:27:57Z -workingcopy wc_s0FjRJwYItNf2mS61Z9ClWUNvMa9A1KC_20251215022434 -direct -skipcopy -checkwcpatches -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906975 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q- 1495906976 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906977" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 237

and/or its affiliates 238 Stage software

and/or its affiliates 239 Stage now

and/or its affiliates 240 Stage software Succeeded

Grid Infrastructure Upgrade 2025-12-15T02:57:56Z: Scheduled job command: "rhpctl add workingcopy
-targetnode vmc1-v4hra2.sub04210756190.exavcn.oraclevcn.com -auth restauth -softwareonly - json -image gi-o2NCRdGZEz2MZPFZUXVbzSGkaM7HrUnj-20251215022433 -schedule 2025-12-15T02:51:37Z -workingcopy wc_i03f7wMLaV3MZSuTzrhKVcqyx3Ks8GW1_20251215024946 - direct -skipcopy -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906970 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906971 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q- 1495906972" 2025-12-15 02:57:49.901 UTC : Oracle home "/u02/app/23.0.0.0/gridhome_1" of version "23.9.0.25.07" created as working copy "wc_i03f7wMLaV3MZSuTzrhKVcqyx3Ks8GW1_20251215024946" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 242

and/or its affiliates 243 Apply upgrade

and/or its affiliates 244 Apply upgrade now

Grid Infrastructure Upgrade Failedの例一般的な GI 19c → 26ai のアップグレード要件である
Diskgroup の compatible.rdbmsパラメーターを 19.0.0.0 に事前に変更が必要 2025-12-15 04:34:21.979 UTC : PRGO-1774 : The evaluation revealed potential failure for command "upgrade gihome". 2025-12-15T04:34:45Z: PRGO-1707 : Failure occurred while executing Cluster Verification Utility. 2025-12-15T04:34:45Z: PRGT-510 : Pre-upgrade verification through Configuration Verification Utility reported one or more errors. 2025-12-15T04:34:45Z: PRVE-3180 : RDBMS compatibility for ASM disk group "RECOC1" is set to "11.2.0.4.0", which is less than the minimum supported value "19.0.0.0.0". 2025-12-15T04:34:45Z: PRVE-3180 : RDBMS compatibility for ASM disk group "DATAC1" is set to "11.2.0.4.0", which is less than the minimum supported value "19.0.0.0.0". 2025-12-15T04:35:31Z: Finishing apply eval for action ocid1.fsuaction.oc1.ap-osaka-1.amaaaaaassl65iqajvfe3rrsfpzduep4jgziarpuj53r2egrhifnfgbnnzfa 2025-12-15T04:35:31Z: Job failed due to Internal error during execution of apply eval for another one or more targets associated with action ocid1.fsuaction.oc1.ap-osaka-1.amaaaaaassl65iqajvfe3rrsfpzduep4jgziarpuj53r2egrhifnfgbnnzfa. Review failure in the Action logs or in the Job logs and retry by creating a new Apply Action. Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 247

Grid Infrastructure Upgrade compatible.rdbms の確認 [grid@vmc1-v4hra1 ~]$ asmcmd lsattr -l
-G DATAC1 Name Value access_control.enabled FALSE access_control.umask 066 appliance._partnering_type EXADATA FIXED appliance.mode TRUE ate_conversion_done true au_size 4194304 cell.smart_scan_capable TRUE cell.sparse_dg allnonsparse compatible.advm 19.0.0.0 compatible.asm 19.0.0.0.0 compatible.rdbms 11.2.0.4 content.check TRUE content.type data content_hardcheck.enabled FALSE disk_repair_time 12.0h failgroup_repair_time 24.0h idp.boundary auto idp.type dynamic logical_sector_size 512 maxblkdump_content.check 3 maxdump_content.check 32 maxerr_content.check 1048576 phys_meta_replicated true preferred_read.enabled FALSE scrub_async_limit 1 scrub_content_check_in_repair FALSE scrub_metadata.enabled TRUE sector_size 512 thin_provisioned FALSE Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 248

Grid Infrastructure Upgrade [grid@vmc1-v4hra1 ~]$ sqlplus / as sysasm SQL>
select group_number,name,value from v$asm_attribute where name like '%compatible.rdbms%'; GROUP_NUMBER ------------ NAME -------------------------------------------------------------------------------- VALUE -------------------------------------------------------------------------------- 1 compatible.rdbms 11.2.0.4 2 compatible.rdbms 11.2.0.4.0 GROUP_NUMBER ------------ NAME -------------------------------------------------------------------------------- VALUE -------------------------------------------------------------------------------- SQL> ALTER DISKGROUP DATAC1 SET ATTRIBUTE 'compatible.rdbms' = '19.0'; Diskgroup altered. SQL> ALTER DISKGROUP RECOC1 SET ATTRIBUTE 'compatible.rdbms' = '19.0'; Diskgroup altered. Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 249

Grid Infrastructure Upgrade SQL> select group_number,name,value from v$asm_attribute where name
like '%compatible.rdbms%'; GROUP_NUMBER ------------ NAME -------------------------------------------------------------------------------- VALUE -------------------------------------------------------------------------------- 1 compatible.rdbms 19.0 2 compatible.rdbms 19.0 GROUP_NUMBER ------------ NAME -------------------------------------------------------------------------------- VALUE -------------------------------------------------------------------------------- SQL> Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 250

and/or its affiliates 251 Retry failed targets （Faileした場合に出てくるメニュー）

and/or its affiliates 252 Apply upgrade(retry) Succeeded

Grid Infrastructure Upgrade 2025-12-15T06:50:16Z: ======================JOB_EXECUTION_DETAILS_START====================== 2025-12-15T06:50:16Z: User: opc 2025-12-15T06:50:16Z: Client:
cl-tgmfvq5q 2025-12-15T06:50:16Z: Scheduled job command: "rhpctl upgrade gihome -targetnode vmc1-v4hra1.sub04210756190.exavcn.oraclevcn.com -auth restauth -destwc wc_i03f7wMLaV3MZSuTzrhKVcqyx3Ks8GW1_20251215024946 -json -sourcewc wc_K4jl0W5U20SdeGNkS8WuI6kRknZzhTva_20251215022450 -schedule 2025-12-15T06:19:38Z -direct - arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q- 1495906961 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906962 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqajkmymifj22mxmmiqva5nkwn2rp4xc7iwabkatgmfvq5q-1495906963" 2025-12-15T06:50:16Z: Job execution start time: 2025-12-15 06:20:06 2025-12-15T06:50:16Z: Job execution end time: 2025-12-15 06:49:47 2025-12-15T06:50:16Z: Job execution elapsed time: 29 minutes 41 seconds 2025-12-15T06:50:16Z: Current status: SUCCEEDED 2025-12-15T06:50:16Z: =======================JOB_EXECUTION_DETAILS_END======================= Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 254

Grid Infrastructure Upgrade アップグレード後、/u02/app/23.0.0.0/gridhome_1 に GIHOME が移動 [root@vmc1-v4hra1 23.0.0.0]# cat
/etc/oratab #Backup file is /u01/app/grid/crsdata/vmc1-v4hra1/output/oratab.bak.vmc1-v4hra1.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB1206_nhb_kix:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y DB0409_vf6_kix:/u02/app/oracle/product/19.0.0.0/dbhome_3:Y restdb_phr_kix:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y tmp_rqf_kix:/u02/app/oracle/product/19.0.0.0/dbhome_4:Y DB1209_qr2_kix:/u02/app/oracle/product/19.0.0.0/dbhome_5:Y +ASM1:/u02/app/23.0.0.0/gridhome_1:Y [root@vmc1-v4hra1 23.0.0.0]# Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 255

and/or its affiliates 256 GI Upgrade 成功後の rollback は非対応

Oracle and/or its affiliates 259 Create maintenance cycle Select a Exadata image 25.2.2.0.0

Oracle and/or its affiliates 260 Oracle Exadata image 25.2.2

Oracle and/or its affiliates 261 Advanced options Database start/stop options: Keep service placement: Software update options:

Oracle and/or its affiliates 262 Maintenance cycle Target Exadata image version

Oracle and/or its affiliates 263 Precheck

Oracle and/or its affiliates 264 Precheck Succeeded

Guest OS Exadata system Scheduled job command: "rhpctl register image
-imagetype EXAPATCHSOFTWARE -getfromOSS /fpp/base/crsdata/fppcsdp-ad1-prod-1/rhp/examap-guestos- 0ygTvVVoJ8KXQUan4CFNVvSafIh28CQp-20251111091554 -json -image guestos-0ygTvVVoJ8KXQUan4CFNVvSafIh28CQp-20251111091554 -schedule 2025-11-11T09:17:00Z" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 266

Oracle and/or its affiliates 267 Stage software

Oracle and/or its affiliates 268 Stage now

Oracle and/or its affiliates 269 Stage software Succeeded

Oracle and/or its affiliates 270 Scheduled job command: "rhpctl stageCollection"

Oracle and/or its affiliates 271 Apply update

Oracle and/or its affiliates 272 Apply update now

Oracle and/or its affiliates 273 Apply update Succeeded

Guest OS Exadata system rhpctl コマンドで Exadata Image の更新を実施 Scheduled
job command: "rhpctl update exadata -iso_repo guestos-0ygTvVVoJ8KXQUan4CFNVvSafIh28CQp-20251111091554 -targetnode jiro- 1koqp2.sub04210756190.exavcn.oraclevcn.com -racks kix1-d2-cl3-e95e0f2e-888b-4210-80e4-c91969b5674d-clu03 -auth restauth -dbnodes -drain_timeout 600 -json -image guestos-0ygTvVVoJ8KXQUan4CFNVvSafIh28CQp-20251111091554 -schedule 2025-11-12T07:51:42Z -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888556 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq- 1285888555 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaanpaavrsfzpzqvu755emgokt3ghrwwdnt7na72fr52iq-1285888554" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 275

Oracle and/or its affiliates 276 Rollback

Oracle and/or its affiliates 277 メッセージが不正確だが、 Rollbackは未サポートの機能とのこと

Oracle and/or its affiliates 310 Cleanup

Oracle and/or its affiliates 311 Warning Cleaning up the GI Home will remove the ability to perform a rollback. （メッセージが正しくない）

Oracle and/or its affiliates 312 Cleanup Succeeded

Oracle and/or its affiliates 313 Cleanup後はメニュー選択できなくなる

ExaDB Stack (Guest OS Exadata system and Grid Infrastructure) software
update: Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 315 Create collection ExaDB Stack (Guest OS Exadata system and Grid Infrastructure) software update: Edit search criteria Compartment Apply

update: Scheduled job command: "rhpctl register image -imagetype EXAPATCHSOFTWARE -getfromOSS /fpp/base/crsdata/fppcsdp-ad1-prod-1/rhp/examap-guestos- OXaqoeCK8lm2gmJEDvWgMly8p4je4XpY-20251016022733 -json -image guestos-OXaqoeCK8lm2gmJEDvWgMly8p4je4XpY-20251016022733 -schedule 2025-10-16T02:29:32Z" Job execution start time: 2025-10-16 02:29:32 Job execution end time: 2025-10-16 02:29:34 Job execution elapsed time: 2 seconds Scheduled job command: "rhpctl register workingcopy -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -auth restauth -json -image gi- gnXKAXxtW5DVB9pv4Yzx9nEfCE7ewkvz-20251016022801 -schedule 2025-10-16T02:30:55Z -workingcopy wc_iqLAMN5KclSjkzCEUsdXu28Vp0RUpv3n_20251016022758 -direct -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335068 - arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 512335069 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335073" Job execution end time: 2025-10-16 02:32:24 Job execution elapsed time: 1 minutes 22 seconds Scheduled job command: "rhpctl add workingcopy -eval -targetnode goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com -auth restauth -softwareonly -json -image gi- btw7kOQkplsCMPt2l2U2DKrLv3CpGI8L-20251016022740 -sourcehome /u02/app/grid -schedule 2025-10-16T02:30:55Z -workingcopy wc_izdy7xUpHh0h3k1fnGUxayxuuCpixlMi_20251016022742 -direct -skipcopy -checkwcpatches -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335070 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 512335071 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335072" Job execution start time: 2025-10-16 02:31:02 Job execution end time: 2025-10-16 02:32:49 Job execution elapsed time: 1 minutes 47 seconds 2025-10-16 02:32:03.191 UTC : Warning: Image "gi-btw7kOQkplsCMPt2l2U2DKrLv3CpGI8L-20251016022740" is missing the patches for bug numbers "35221462,37537949,37711404,37701427,37701418,37701424,37701421", which are present in the source Oracle home "/u01/app/23.0.0.0/grid". Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 335

rhpctl コマンドオプション • rhpctl register image • イメージのメタデータをOracle FPPリポジトリに登録 -
-imagetype EXAPATCHSOFTWARE • for Oracle Exadata software • rhpctl register workingcopy • 作業用コピーのメタデータをOracle FPPリポジトリに登録 • rhpctl add workingcopy • クライアント・クラスタ上に作業用コピーを作成 336 Copyright © 2026, Oracle and/or its affiliates

update: ======================JOB_EXECUTION_DETAILS_START====================== User: opc Client: fppcsdp-ad1-prod-1 Scheduled job command: "rhpctl add workingcopy -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -auth restauth -softwareonly -json -image gi- btw7kOQkplsCMPt2l2U2DKrLv3CpGI8L-20251016022740 -schedule 2025-10-16T02:55:04Z -workingcopy wc_UL2uEaNtzehnZVNJobpX83gIz48E4aCk_20251016025300 -direct -skipcopy -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 512335065 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335066 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335067" Job execution start time: 2025-10-16 02:55:32 Job execution end time: 2025-10-16 03:00:57 Job execution elapsed time: 5 minutes 24 seconds Current status: SUCCEEDED =======================JOB_EXECUTION_DETAILS_END======================= 2025-10-16 02:57:05.415 UTC : Storing metadata in repository for working copy "wc_UL2uEaNtzehnZVNJobpX83gIz48E4aCk_20251016025300" ... 2025-10-16 02:57:05.455 UTC : Changing the home ownership to user grid... 2025-10-16 03:00:54.685 UTC : Oracle Grid Infrastructure home "/u02/app/23.0.0.0/gridhome_1" staged successfully 2025-10-16 03:00:54.768 UTC : Executing root script on nodes [goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com, goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com]. 2025-10-16 03:00:56.990 UTC : Successfully executed root script on nodes [goro-sx2zy1.sub04210756190.exavcn.oraclevcn.com, goro- sx2zy2.sub04210756190.exavcn.oraclevcn.com]. 2025-10-16 03:00:57.054 UTC : Oracle home provisioned. 2025-10-16 03:00:57.054 UTC : Oracle home "/u02/app/23.0.0.0/gridhome_1" of version "23.26.0.0.0" created as working copy "wc_UL2uEaNtzehnZVNJobpX83gIz48E4aCk_20251016025300" 2025-10-16 03:00:57.062 UTC : Working copy creation completed. Successfully provisioned new GI goal working copy wc_UL2uEaNtzehnZVNJobpX83gIz48E4aCk_20251016025300 on cluster ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 342

update: stage 前 [root@goro-sx2zy1 ~]# df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/VGExaDbDisk.u02_extra.img-LVDBDisk ext4 303G 60G 228G 21% /u02 stage後 [root@goro-sx2zy1 ~]# df -Th /u02 Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/VGExaDbDisk.u02_extra.img-LVDBDisk ext4 303G 63G 225G 22% /u02 [root@goro-sx2zy1 ~]# Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 343

update: Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 346 Apply update 2:20くらい Guest OS Exadata systemのApply update は2:05くらい、 Grid Infrastructureの Apply updateは1:10くらいだったので、それぞれ実施するより一度で実行することで1時間弱短縮化

update: [root@goro-sx2zy2 ~]# imageinfo Kernel version: 5.15.0-308.179.6.14.el8uek.x86_64 #2 SMP Sun Jul 27 21:02:28 PDT 2025 x86_64 Uptrack kernel version: 5.15.0-310.184.5.2.el8uek.x86_64 #2 SMP Wed Jul 9 16:08:33 PDT 2025 x86_64 Image kernel version: 5.15.0-308.179.6.14.el8uek Image version: 25.1.8.0.0.250828 Image activated: 2025-10-16 10:14:12 +0000 Image status: success Exadata software version: 25.1.8.0.0.250828 Node type: GUEST System partition on device: /dev/mapper/VGExaDb-LVDbSys1 [root@goro-sx2zy2 ~]# imagehistory Version : 24.1.9.0.0.250213 Exadata Live Update Version : n/a Image activation date : 2025-04-03 07:18:37 +0000 Imaging mode : fresh Imaging status : success Version : 25.1.2.0.0.250213.1 Exadata Live Update Version : n/a Image activation date : 2025-04-10 03:04:40 +0000 Imaging mode : patch Imaging status : success Version : 25.1.8.0.0.250828 Exadata Live Update Version : n/a Image activation date : 2025-10-16 10:14:12 +0000 Imaging mode : patch Imaging status : success Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 347

update: [root@goro-sx2zy2 ~]# cat /etc/oratab #Backup file is /u01/app/grid/crsdata/goro-sx2zy2/output/oratab.bak.goro-sx2zy2.grid line added by Agent # # This file is used by ORACLE utilities. It is created by root.sh # and updated by either Database Configuration Assistant while creating # a database or ASM Configuration Assistant while creating ASM instance. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third field indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # DB0408_qg7_kix:/u02/app/oracle/product/19.0.0.0/dbhome_1:Y +ASM2:/u02/app/23.0.0.0/gridhome_1:Y [root@goro-sx2zy2 ~]# Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 348

update: Scheduled job command: "rhpctl move gihome -targetnode goro-sx2zy2.sub04210756190.exavcn.oraclevcn.com -sourcewc wc_iqLAMN5KclSjkzCEUsdXu28Vp0RUpv3n_20251016022758 -image guestos-OXaqoeCK8lm2gmJEDvWgMly8p4je4XpY-20251016022733 -schedule 2025-10-16T08:49:07Z -direct - iso_repo guestos-OXaqoeCK8lm2gmJEDvWgMly8p4je4XpY-20251016022733 -racks kix1-d2-cl3-e95e0f2e-888b-4210-80e4-c91969b5674d-clu05 -auth restauth -destwc wc_UL2uEaNtzehnZVNJobpX83gIz48E4aCk_20251016025300 -drain_timeout 600 -json -arg5 tlskeystore:/fpp/base/chkbase/scheduled/jksKeyStore- ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335059 -arg4 tlstruststore:/fpp/base/chkbase/scheduled/jksTrustStore-ocid1.cloudvmcluster.oc1.ap-osaka-1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa- 512335060 -arg1 restendpointfile:/fpp/base/chkbase/scheduled/restaddrfile-ocid1.cloudvmcluster.oc1.ap-osaka- 1.anvwsljrssl65iqaakxd76z6dshzptnrha677kp5hszbalfy3ins7ryg5nqa-512335061" Exadata Fleet Update Copyright © 2026, Oracle and/or its affiliates 350

affiliates 355 Create Subscriptions Topic: FSU

affiliates 356 Configure Subscription Create

affiliates 357 Observability & Management ➢ Events Service ➢ Rules Create Rule

affiliates 358 Service Name: FSU To create rules, see Creating an Events Rule. Note that you must select FSU to filter Exadata Fleet Update service events. Event Type: Table 5-3 Exadata Fleet Update Event Types が一覧

affiliates 359 com.oraclecloud.fsu.createfsu action.begin com.oraclecloud.fsu.createac tion.end com.oraclecloud.fsu.deletefs uaction.begin com.oraclecloud.fsu.deleteac tion.end 等々 Table 5-3 Exadata Fleet Update Event Types 下へスクロール

affiliates 360 Create Rule Actions Action Type: Notifications Notifications Compartment: コンパートメント名 Topic: 作成したトピック名

affiliates 361 Event Matching Event Types

affiliates 362 Actions Action Type: Notifications Details: Topic=FSU

affiliates 363 Topic: FSU Subscriptions: State: Pending

affiliates 364 Subscribe to the topic: FSU Confirm subscription

affiliates 365 Subscription confirmed

affiliates 366 Topic: FSU State: Active

Exadata Fleet Update

Exadata Fleet Update

More Decks by oracle4engineer

Other Decks in Technology

Featured

Transcript