Oracle Database Appliance X7, X8 and X9 will require the use of Data Preserving Reprovisioning (DPR) to apply the patch coming from 19.20 and previous releases.
Unlike traditional patching, DPR erases the system disks but keeps data on ASM/ACFS disks.
Dbvisit Standby is a smart solution for those needing a Disaster Recovery solution without the need for buying Enterprise Edition.
Best practice to prevent the erasing of configuration files when using DPR is to set up Dbvisit Standby in a dedicated ACFS filesystem.
DPR will require a longer downtime of your ODA, several hours at least, meaning that you will need to switchover your databases to another ODA with Data Guard or Dbvisit Standby.
Classic patching does not require any additional operation when using Dbvisit Standby compared to Data Guard.
The first failure in Dbvisit Standby when using DPR is easy to fix, just remove the service associated with the database before DPR is activated.
If metadata in OCR is inconsistent while using DPR, it should be related to metadata in the ODA registry.
Using DPR on an ODA running Dbvisit Standby works fine, but it is important to check and fix the role of the database in the ODA registry if stuck at the preupgradereport.
DPR aims to make upgrading easier, but patching is not always a trivial task. Dbvisit is a powerful tool that can simplify the patching process.