To resolve the 72030 error, you must explicitly tell the utility to use the non-rolling method by adding the -nonrolling flag to your command. Standard Syntax:
Download the latest OPatch utility and your target patch from My Oracle Support . Back up your Oracle Homes before proceeding. opatchauto72030 execute in nonrolling mode
Run the opatchauto apply command with the -nonrolling flag. To resolve the 72030 error, you must explicitly
Once completed, use ./opatch lsinventory to confirm the patch is successfully applied across the homes. Key Differences: Rolling vs. Non-Rolling Non-Rolling upgrade in RAC using opatchauto - Oracle Forums Run the opatchauto apply command with the -nonrolling flag
The primary reason for this specific error code is a configuration. In a shared home, multiple nodes use the same physical installation binaries. Since a rolling patch updates binaries while they are still in use by other nodes, it would cause immediate system instability or failure. To protect the environment, opatchauto throws error 72030 to force a full maintenance window. Other triggers for non-rolling mode include:
Some patches contain metadata explicitly stating they cannot be applied in a rolling fashion due to significant binary or architectural changes.