The error OPATCHAUTO-72030 typically indicates that opatchauto cannot execute a patch in rolling mode because the Grid Infrastructure (GI) home is shared across nodes.
Update OPatch First: Always ensure you are using the latest OPatch utility version (e.g., 12.2.0.1.30+ for Oracle 19c) before starting. opatchauto72030 execute in nonrolling mode high quality
High quality is demonstrated by a thorough audit of the opatch lsinventory output to confirm that patch 72030 is listed correctly on all nodes. It also involves validating that all database services, listeners, and cluster resources have restarted without errors. A cluster that comes online with degraded resources—such as a failed ASM instance or a missing listener—indicates a low-quality patching process, even if the patch binary application succeeded. True quality is achieved only when the system is returned to full operational status, indistinguishable from its pre-patch performance but for the updated software version. It also involves validating that all database services,
Node Availability: If any cluster nodes are down or the ASM instance is not running on remote nodes, opatchauto cannot initiate a rolling session. Node Availability: If any cluster nodes are down