Last updated on DECEMBER 05, 2016
Applies to:Oracle Exadata Storage Server Software - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Several customers have found that the dbnodeupdate.sh script has been unable to re-start the CRS stack on Exadata Compute Node after using dbnodeupdate.sh to update the Compute Node Linux OS:
After Patching of the Compute Node 1 of an Exadata Machine, the final step in the patching process is to run the following command:
This job does the following ....
(*) 2016-03-23 16:11:00: Verifying GI and DB's are shutdown
(*) 2016-03-23 16:11:02: Verifying firmware updates/validations. Maximum wait time: 60 minutes.
(*) 2016-03-23 16:11:02: If the node reboots during this firmware update/validation, re-run './dbnodeupdate.sh -c' after the node restarts..
(*) 2016-03-23 16:11:03: Collecting console history for diag purposes
(*) 2016-03-23 16:11:35: No rpms to remove
(*) 2016-03-23 16:11:36: Relinking all homes
(*) 2016-03-23 16:11:36: Unlocking /u01/app/188.8.131.52/grid
(*) 2016-03-23 16:11:39: CRS_LIMIT_NPROC successfully set to 65535 in /u01/app/184.108.40.206/grid/crs/install/s_crsconfig_smcct2-dm-1-co01_env.txt as workaround for Bug 19680763
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