Last updated on AUGUST 29, 2014
Applies to:Exadata Database Machine X2-2 Hardware - Version All Versions and later
Information in this document applies to any platform.
The process being followed is:
1. calling dbnodeupdate - which is kicking off the yum update
2. the yum update process causes the node to reboot
3. reboot not happening due to a bug. This bug could be encountered on any reboot, regardless of whether dbnodeupdate.sh was called.
Running dbnodeupdate.sh is hanging while attempting to upgrade Exadata software on a database node.
The hanging step is likely from the reboot step of the patching process.
It can occur during rebooting / shutting down, an action which may not be affiliated with a patching activity.
The console window returns a stack which often looks like the following:
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
 rds_ib_remove_one+0xf0/0x110 [rds_rdma]
 ? autoremove_wake_function+0x0/0x3d
 ? _cond_resched+0xe/0x22
 ib_unregister_device+0x36/0x103 [ib_core]
 mlx4_ib_remove+0x3f/0xfa [mlx4_ib]
 mlx4_remove_device+0x78/0xa0 [mlx4_core]
 mlx4_unregister_interface+0x2f/0x99 [mlx4_core]
 mlx4_ib_cleanup+0x15/0x23 [mlx4_ib]
 ? audit_syscall_entry+0x103/0x12f
Applying a new version of the Exadata software (upgrade)
This can occur even when simply rebooting / shutting down, as a process unrelated to patching activities.
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