Not all the steps suggested by Oracle are executed in this walkthrough. It's because this installation creates an environment for testing/development. Security is not the primary concern, patching is at the minimum level that it makes the system good enough to work well. The major differences are:
All Patches are applied in hot patch mode.
No fs_clone. Only the RUN file system is available to use.
Database 19c is single-tenant
With the timespan of 12 years to move from release 12.2.0 to 12.2.15, each release was tested thoroughly at that release time. So the best, error-free, exhausted-tested configuration is the one that is matched at that time of software environment. So the whole process is broken down into 4 phases -- from the time it just released in 2013, and progressively to R12.2.15 in 2025, sailing from Windows Server 2008 to Windows Server 2019.
Another reason of this break down is that a lot of companies do not upgrade the instance to the latest version. For development or troubleshooting, you need to match the same version, or as close as possible, as your company is using. So if your company is using 12.2.6, then you can take the 12.2.5 version and upgrade it to 12.2.6.
The ISO images of Windows Server 2008 R2, 2012, 2016, and 2019.
Know how to do the activation of Windows Server (by any mean...).
Microsoft Visual Studio 2008, 2016, and 2019. Community Edition is good enough.
GNU Cygwin 64bit. Use the older version, as specified in the steps. No need to use MKS Toolkit because the GNU stuff just works well.
An Oracle support account which can download patches.
adop=fs_clone to copy the files to fs2 folder?This configuration is intended for development / demo / quick testing. All files are executed in RUN file system fs1, and we don't care about downtime. So we don't need anything from fs2. Similar to 12.1 or 11i, the single file system is good enough. It is reduced the overall file footprint that we can do a quicker backup/restore and minimize the storage needs.
In this walkthrough, I only apply necessary patches to make the instance work well enough to do the development or other simple demo. So you could apply as many patches you like, but just make sure you have a backup plan in case the patch fails because patch can be applied in hotpatch mode only.
Yes, these steps have been tested for Vision demo installation. The only difference is that in the RapidWiz, in the Database Node Configuration screen you select Vision Demo instead of Fresh Database.
After successfully log on tosupport.oracle.com, change the URL to https://support.oracle.com/support/?patchId=[Patch ID]
####
© 2026 by Christopher Ho. All Rights Reserved