external vSphere and vUM databases update planning advice sought

our vCenter 4.1 uses external Oracle databases. We have Linux operating system and Oracle Critical Patch Updates to apply to them, which will require databases quiesce and database server reboot.  This will break commujications with vCenter. In the past we have had issues with the vCenter Services not restarting.  We would like to better plan this time around so that vCenter Server operations will come back.

Would someone with experience please commenton the following plan:

1. From the vCenter server's Server Manager: Services console
   1. Stop the VMware VirtualCenter Management Webservices service
   2. Stop the VMware vCenter Update Manager service
   3. Stop the VMware VirtualCenter Server service
2. On the external database server:
   1. Apply needed Linux updates
   2. Reboot the server (will be required)
   3. Quiesce the databases
   4. Apply the Critial Patches
   5. Restart the databases
3. From the vCenter server's Server Manager: Services console
   1. Start the VMware vCenter Update Manager service
   2. Start the VMware Virtual Center Server service
   3. Start the VMware VirtualCenter Management Webservices service

Is there a place where I should specifically stop and restart VMware vCenter Converter server and worker? VMware Tools service and VMware Upgrade Helper services show no dependencies. Do these need to be manually stopped/restarted as well? If so, is the order important?

Thanks in advance for all insights.