The patch README for bug 72030 may state: "This patch is not rolling installable. Use -nonrolling flag."

A. Run root scripts manually if not auto-executed:

# As root on each node:
/u01/app/19.0.0/grid/rootupgrade.sh   # or patch-specific root script

B. Start Clusterware on all nodes:

# As root on each node:
crsctl start cluster -all

C. Verify cluster status:

crsctl stat res -t

D. Start databases:

srvctl start database -d prod_db

E. Validate patch application:

$ORACLE_HOME/OPatch/opatch lsinventory -patch -id 72030

Some bug fixes require replacing shared libraries (libclntsh.so, libhasgen.so) used by every node. A rolling patch could leave nodes running mixed binaries, causing corruption.

Yes. If the patch modifies ASM binaries, all disk groups will be dismounted during the patch window.

No. Oracle’s utility is opatchauto. The number 72030 is a placeholder for a specific patch ID. The keyword you searched likely originated from a DBA’s notes or script alias.