The other day, Oracle has released another patchset for its database with version 126.96.36.199. This patch also marked an important change in the release form of the patchsets. This translation in brief will be devoted to this translation of the article on the My Oracle Support website - 188.8.131.52 [ID 1189783.1].
Starting with patch 184.108.40.206 - all Oracle Database packs will be complete product installations. (And now they weigh accordingly - a comment of the translator). Prior to this version, patchsets were a specific set of files that replaced the files of an existing installation.
In connection with the innovation, the patchset will be divided into several packages, as before the basic issues:
* Oracle Database Server
* Oracle Grid Infrastructure
* Oracle Database Client
* Companion / examples
* Oracle GatewaysSimplified primary installation.
You no longer need to install the basic version, and then roll up the patchset on it. You can immediately download and install the latest patchset.
There are two ways to apply a patchset to an existing installation.
- This is the recommended way to use the patchset by Orakl. You install the patchset in a new Oracle home. After installation, you are migrating from the old home. Now it is more like an upgrade from one version to another. This method allows you to reduce database downtime and is safer because it does not require changing the existing ORACLE_HOME that you have in your work. However, it requires sufficient disk space to expand another Oracle directory.
- You install the patchset in an existing Oracle home. Oracle recommends using this option only if you do not have free disk space to implement the previous method. This method requires more time and is more risky. If you do decide to use this method, Orakl strongly advises to make a full backup of the existing Oracle_home and carefully read the entire Upgrade Guide section concerning the in-place installation.
Note: All Oracle Grid Infrastructure patchsets should be installed using the out-of-place method only. The second method is not supported.Direct upgrade from previous releases.
Now you can upgrade directly to the latest version of the patchset without upgrading to the base version. For example, you can upgrade your Oracle Database 10g Release 2 or Oracle Database 11g Release 1 immediately to version 220.127.116.11, bypassing the upgrade to base 18.104.22.168.How to get the patchset.
As before, you can get patchsets on My Oracle Support as well as on edelivery.oracle.comFAQQ.
Is this really a patchset?A.
Yes, this is really a patchset, containing mainly fixes to the basic version 22.214.171.124. Just now they are packaged differently. Although this version includes several new features (new features) - their number is very small and we have no plans to add new functionality to the future 11.2 patchsets.Q.
Why did Oracle make these changes?A.
In response to customer feedback, Oracle did this for the following reasons:
An out-of-place upgrade has proven to be the best practice for many clients when installing patchsets. This method reduces the cost of time, because you can completely install and configure the new home, until the time when you extinguish the old. This method is easier, faster and safer. If there are any problems during the installation process, you will simply return to the working Oracle_home.
If the client has several instances (instances) of the database - this method allows you to transfer them one by one, instead of transferring all instances simultaneously. It also reduces downtime.
Oracle noted that using a full installation with upgrades is generally more convenient for customers and allows for an easier and safer upgrade, which significantly reduces downtime.
Full installation will allow customers to go directly to the latest release 126.96.36.199, bypassing the previous basic releases.