Very important :
This fix introduces a notable change in behaviour in that from 18.104.22.168 onwards an I/O write error to a datafile will now crash the instance. Before this fix I/O errors to datafiles not in the system tablespace offline the respective datafiles when the database is in archivelog mode. This behavior is not always desirable. Some customers would prefer that the instance crash due to a datafile write error. This fix introduces a new hidden parameter to control if the instance should crash on a write error or not: _datafile_write_errors_crash_instance With this fix: If _datafile_write_errors_crash_instance = TRUE (default) then any write to a datafile which fails due to an IO error causes an instance crash. If _datafile_write_errors_crash_instance = FALSE then the behaviour reverts to the previous behaviour (before this fix) such that a write error to a datafile offlines the file (provided the DB is in archivelog mode and the file is not in SYSTEM tablespace in which case the instance is aborted)
11.2 Patch Sets 22.214.171.124 and higher are supplied as full releases.
Starting with the first patch set for Oracle Database 11g Release 2 (126.96.36.199), Oracle Database patch sets are full installations of the Oracle Database software. In past releases, Oracle Database patch sets consisted of a set of files that replaced files in an existing Oracle home. Beginning with Oracle Database 11g Release 2, patch sets are full installations that replace existing installations.
Upgrade process: Beginning with the release 188.8.131.52 patch set, you have two ways to apply a patch set:
- Out-of-place upgrade – This is Oracle's recommended way to apply a patch set. You install the patch set into a new, separate Oracle home location. After you install the patch upgrade, you then migrate the Oracle Database from the older Oracle home. The patch set upgrade is now the same process to upgrade from one version to another. Oracle recommends that you perform an out-of-place patch set upgrade, because this patch set application option requires much less downtime, and is safer because it does not require patching an ORACLE_HOME that is already being used in production. However, you must ensure that you have sufficient free disk space to accommodate two Oracle home directories at the same time.
- In-place upgrade – You install the patch set into an existing Oracle home location. Oracle recommends that you select this option only if you do not have sufficient free disk space to perform an out-of-place upgrade, as the upgrade removes the existing Oracle installation. This patch option requires less disk space, but requires more time, and is riskier, because if you encounter an installation failure, then you must recover the entire existing Oracle home from a backup. If you choose this more risky option, then before you begin the patch installation, complete the following tasks:
- Make a complete backup of your existing Oracle home
- Read through the entire Upgrade Guide section dealing with in-place upgrades
Direct upgrade from previous releases: You can upgrade from a previous Oracle Database release directly to the latest patch set, without having to install the base release. For example, if you want to upgrade from Oracle Database 10g Release 2, or Oracle Database 11g Release 1, then you can upgrade directly to Oracle Database 11g Release 2, patch set 2 (184.108.40.206) using an out-of-place upgrade. Oracle now supports direct upgrades to the release 220.127.116.11 patch set from any release where direct upgrade to the base release (18.104.22.168) is supported, as well as direct upgrades from 22.214.171.124 to 126.96.36.199.
In addition to the usual set of fixes, the release 188.8.131.52 patch set contains a small number of features that complete the Database 11g Release 2 feature set. The new features fall into the following five categories:
- General improvements
- Oracle Automatic Storage Management Cluster File System (ACFS) improvements
- Quality of Service Management
- Database Replay