DB node post upgrade kernel panic during boot preceded by unexpected operator errors
Last updated on JUNE 01, 2016
Applies to:Oracle Exadata Storage Server Software - Version 184.108.40.206.0 to 220.127.116.11.1 [Release 12.1]
Information in this document applies to any platform.
Some time after dbnodeupdate.sh is executed, the DB node gets rebooted, but is stuck in a reboot loop due to a kernel panic encountered during the early boot sequence. Monitoring the ILOM's /SP/console reveals the following entries prior to the kernel panic, a key symptom to the issue described in this note:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms