One thing that changes as you move to versions 19.11 & beyond of the Oracle Data Appliance (ODA) is the move of the Oracle Base, as well as Oracle Homes for the RDBMS Software to their own dedicated ACFS Mountpoints, which are carved from the +DATA diskgroup.
This is quite extensively documented, and the steps you would typically need to follow for a Bare Metal system are below. Assuming you are patching from a pre-19.11, you must first complete your system and storage patching successfully. But, before moving on to the database patching step, you need to configure the storage for the new Oracle Home and Oracle Base.
# odacli configure-dbhome-storage -dg DATA
This assigns a default of 10 GB to the Oracle Base and 80 GB to the Oracle Home for your RDBMS. The storage allocated can be altered at any point using the command.
# odacli modify-dbhome-storage .
However, starting 19.12, there is yet another ACFS filesystem that comes out of the box, or you can see it on your ODA after you have completed your upgrade. It is the /opt/…/orapkgs/clones directory.
Oracle creates this directory to store the Oracle Database and Oracle Grid Infrastructure clone files used during the patching process. This is not something that we define or can control, but happens automatically during the patching process.
/opt/oracle/oak/pkgrepos/orapkgs/clones -- sized at 150 GB
Now, REMEMBER that this is yet another chunk of 150 GB carved out from your +DATA Diskgroup.
So be mindful!!! When you patch from a pre-19.11 ODA (say 19.8) to 19.12, you will typically find yourself a good 250 GB short on +DATA
- 100 GB for the default Oracle home & Base for your RDBMS
- 150 GB for the clone Filesystem.
Also, another thing to review post the move of ORACLE_BASE to ACFS is the appropriate diagnostic destination for your databases. Depending on the number of databases, you might want to adjust things. So review v$diag_info for the locations and size your directories accordingly