Exadata upgrade using patchmgr or dbnodeupdate fails with message "Bios boot order is incorrect"
(Doc ID 1946042.1)
Last updated on MARCH 04, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Exadata Storage Server Software - Version 11.2.3.3.1 to 12.1.2.1.1 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- While preparing to upgrade Oracle EXADATA storage software, the patch manager pre-req failed (patchmgr -patch_check_prereq ):
2014-11-13 10:57:22 -0600 :FAILED: Details in files <cell_name>.log /u01/patches/STORAGE/patch_12.1.1.1.1.140712/patchmgr.stdout, /u01/patches/STORAGE/patch_12.1.1.1.1.140712/patchmgr.stderr
2014-11-13 10:57:22 -0600 :FAILED: DONE: Execute plugin check for Patch Check Prereq.
[ERROR] Patch prerequisite checks failed. Please run cleanup before retrying.
The referenced file <cell_name>.log further shows:
[WARNING] ubiosconfig statuses are not in Ok states
[WARNING] BIOS is not ready for export/import operations
[WARNING] Restore status: Restore pending
[WARNING] Config sync status: Ok
Additional details reported on file /var/log/cellos/validations/biosbootorder.log, which is the result of running command ubiosconfig list status:
system_bios_version: 17100400
restore_status: Restore pending >>>
config_sync_status: Ok
reset_to_defaults: Off
- Compute nodes running dbnodeupdate -c
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |