Exadata upgrade using patchmgr or dbnodeupdate fails with message "Bios boot order is incorrect"
Last updated on JULY 14, 2015
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Exadata Storage Server Software - Version 184.108.40.206.1 to 220.127.116.11.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.
- 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_18.104.22.168.1.140712/patchmgr.stdout, /u01/patches/STORAGE/patch_22.214.171.124.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:
restore_status: Restore pending >>>
- Compute nodes running dbnodeupdate -c
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms