Exadata Patching - Compute Node

In earlier posts we have seen how to patch infiniband switch and Cell Server. 

Well, now let's continue with Database Server patching which is pending since long time.

Patching on Database server can be performed serially or in parallel using DCLI utility.

dbnodeupdate.sh utility is used to perform the database server patching

What dbnodeupdate.sh utility does?

  • Stop/unlock/disable CRS for host restart
  • Perform LVM snapshot backup of / filesystem
  • Mount yum ISO image and configure yum
  • Apply OS updates via yum
  • Relink all Oracle homes for RDS protocol
  • Lock GI home and enable CRS upon host restart


Step 1: Go to the database server patch directory

#cd /19625719/Infrastructure/ExadataDBNodeUpdate/3.60

Step 2:  Download latest dbnodeupdate.sh script and replace it with new one

You can go through the MOS ID 1553103.1 for latest dbnodeupdate.sh utility.

Step 3: Execute pre-requisites check on DB Server

#./dbnodeupdate.sh -u -l /19625719/Infrastructure/ -v

If pre-requisites check fails than fix the problem first and re-execute it again.

Step 4: Start patching on DB node post completion of successful pre-requisites check

#./dbnodeupdate.sh -u -l  /19625719/Infrastructure/

Step 5: Closely monitor the log file for any error and do the next steps based on the given instruction by dbnodeupdate.sh utility.

Log file location /var/log/cellos/dbnodeupdate.log

Step 6: After reboot execute below command to continue as instucted by dbnodeupdate.sh utility

#./dbnodeupdate.sh -c

How it works?

-----Pre steps starts
  • Collecting configuration details
  • Validating system details. It will check best practice and know issues
  • Check free space in /u01
  • Backup yum configuration files
  • Cleaning up the yum cache
  • Preparing update
  • Performing yum package dependency
  • It will give the overview of pre-requisites check before starting the upgrade including existing and upgrading to image version
-----Pre steps completes

  • Acceptance to continue upgrade procedure

-----Start upgrade
  • Verifying GI and DB's are shut down
  • Un-mount and mount /boot
  • Performing file system backup
  • Verifying and updating yum.conf
  • Stop OSwatcher
  • Cleaning up the yum cache
  • Preparing for update 
  • Performing yum update. Node is expected to reboot when finished
  • Finish all the post steps
  • Reboot system automatically
  • After reboot run "./dbnodeupdate.sh -c" to complete the upgrade
-----Finish upgrade

-----Post Steps Starts
  • Collect system configuration details
  • Verifying GI and DB's are shutdown
  • Verifying firmware updates/validations
  • If the node reboots during this execution, re-run './dbnodeupdate.sh -c' after the node restarts
  • Start ExaWatcher
  • Re-linking all homes
  • Unlocking /u01/app/
  • Re-linking /u01/app/ 
  • Re-linking /u01/app/oracle/product/ 
  • Executing /u01/app/ -patch
  • Starts stack
  • Enabling stack to start at reboot
-----Finished post steps

After completing on first node we can carry on same tasks on second node if patching is executing serially.


There are only two steps need to perform to rollback the patch to the previous version on database server.

Step 1 Execute #./dbnodeupdate.sh -r

Step 2 #./dbnodeupdate.sh -c

No comments:

Post a Comment