Problems with Patching and Rollback

The following information applies to problems with patching and rollback operations on Oracle Big Data Cloud.

I can’t apply a patch

The most common reason a patch can’t be applied is a failure in the precheck step. To apply a patch the entire cluster must be in a healthy state, with all services up and running. Log in to Ambari to verify that all services are running and start any services that aren’t. If you can’t start all services, verify that ambari-agent is running on all cluster nodes. See I need to control the Ambari-agent service.

Patching fails due to disk space

Patching will fail if there isn't enough disk space on specific volumes of each node of the instance. Disk space requirements:

  • Root volume (/): 5 GB

  • Tools root (/u01/app/oracle/tools): 4 GB

  • Install root (/u01/bdcsce): 25 GB

  • Data volume (/data): 10%