Oracle Database Appliance X4-2
 
Oracle Database Appliance Software
 
Oracle Database Appliance
 
Oracle Database Appliance X3-2
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
 

Each release of the ODA comes with newest available Infra/GI/RDBMS versions. This note clarifies RDBMS version installation options on the ODA and ODAVP.

Applies to:

Goal

The ODA does not use generic RDBMS patchsets or PSUs.

The ODA uses unique patched RDBMS versions tested and released with the ODA patch bundle (Infra/GI/RDBMS), End User Bundle (EUB) or as an independent RDBMS CLONE.
Originally ODA 2.1.0.0.0 was released and supported 11.2.0.2.x and higher versions. However, ODA installations were limited to the default ODA RDBMS patched version provided and future patched versions which could be used as upgrades.
Any ODA provided RDBMS patched versions that pre-existed the originally ODA version used were not supported until 2.8.
From 2.8 to 2.10 any existing ODA patched RDBMS version could be installed on the ODA.

As of ODA 12.1.x there are two notable changes in RDBMS availability.

UPGRADES

For X4-2, X3-2 and V1 you can continue to use any existing and installed RDBMS versions that exist before upgrading to ODA 12.1.x.
However, once you are upgrading or re-installing (Bare metal) 12.1.x you must create any new databases using ACFS as the storage option.
Pre-existing databases below 11.2.0.4 will retain ASM storage. Pre-existing 11.2.0.4.x databases will allow migrating to ACFS or retaining ASM.
Any NEW databases as of 12.1.x ODA can only be created using ACFS storage. This is not optional. 

NEW INSTALLATIONS

As of ODA 12.1.x and higher the only allowed new RDBMS homes allowed are 11.2.0.4 and higher until you are on 12.1.2.4 and higher.
The reason is that all new databases created 12.1.x and higher default to using only ACFS on top of ASM. ASM only is not an option for new databases.
IF you are on 12.1.2.4 and higher you can now download and install 11.2.0.3.15 which is supported for ACFS. 11.2.0.4 and higher also supports ACFS. RDBMS versions for 11.2.0.2.x does _not_support ACFS.

However, if upgrading from 2.10 or lower any RDBMS versions installed prior to the 12.x upgrade would also be supported and continue to work.

X5-2 

The lowest version the X5-2 comes with is 12.1.2.2.0. Version 12.1.x GI on the ODA only supports ACFS.
ACFS is not supported on older versions of the RDBMS. The earliest version of RDBMS available on X5-2 is 11.2.0.4.x. unless you are on 12.1.2.4 and higher.

As of ODA version 12.1.2.4 and higher can use the provided ODA 11.2.0.3.15 RDBMS Clone file. This can be downloaded from My Oracle Support ( MOS ) or via links found in note 888888.1.

ODAVP 

One frequently asked question is installing RDBMS versions on a Virtualized image.
Although Virtualized RDBMS versions can be installed in ODAVP [ODA Virtualized Platform], performance will not be equivalent to ODA RDBMS versions installed on ODA_BASE.
 

Note to Support: the ODA does not backport Security patches to previously tested ODA RDBMS versions / clones.
We also do not support applying Security patches independently on ODA RDBMS Clones.

Solution

ODA 12.1.x and higher Only support creating 11.2.0.4 and higher databases using ACFS unless on ODA 12.1.2.4 and higher which also supports 11.2.0.3.15
        12.1.2.2 is the first and lowest ODA version available for the X5-2
ODA 2.8, 2.9, 2.10 support applying any of the following binaries into their own individual Oracle_home.
ODA 2.7 and earlier could only apply their base release RDBMS versions and Upgraded versions as new RDBMS patches became available.

--

STEPS

•   Identify and download the above patch for your specific RDBMS version depending on version used
•   Steps used to unpack the patch (below)

- EXAMPLE -

You may also receive a warning regarding version compatibility when unpacking older RDBMS versions 
- These can be ignored: If you have questions please visit the Oracle Database Appliance Community before creating a SR.

NOTE- Some READMEs will be based on using the original ODA version released at the same time as the RDBMS
             This is not longer required as 2.9 and 2.10 can go back to ANY supplied ODA RDBMS version 
i.e    Do not expect comments in the README to reference newer version patchsets or bundles which did not originally exist when the patch was first released  

Unpack this patch bundle p17770873_210000_Linux-x86-64.zip using the following oakcli command on first node as root user.

- Common practices are to unpack to the /tmp directory 

          # cd /opt/oracle/oak/bin
          # ./oakcli unpack -package <absolute_path_to_patch_file  p17770873_210000_Linux-x86-64.zip>

After that, you can 

          # cd /opt/oracle/oak/bin
          # ./oakcli create dbhome -version 11.2.0.4.2

Discussion:

There are a few sources for many ODA patched and tested RDBMS files:

1)  The Original RDBMS Release associated with a newly shipped ODA: These are usually identified as GI + RDBMS Patchset Bundles.
     The GI version of these Patchset Bundles has a matching Infra Version - These patches have a single matching ODA .ISO version

2) Patchset Updates: A newer version of the RDBMS patched for the ODA but released after the original shipped ODA patched version.
    These are also identified as GI + RDBMS Patchset Bundles but include a newer release than the original installed ODA release(s).
    However, these Bundles may also be paired with an OLDER GI version than the one you are currently using. IF no RDBMS Clone
    exists for only the RDBMS version you need you may have to find a GI + RDBMS bundle and extract only the RDBMS version you need.

3) RDBMS Clones: This is an ODA provided single-patched RDBMS version. Unlike the GI + RDBMS bundles these Clones are
    are updated patches of previously released ODA patched RDBMS versions. These ODA provided patches will be tied to the most current
    Security patch which was available at the time of the Clone release. While 2.9+ allows the use of older clones from 11.2.0.2; 11.2.0.3;
    11.2.0.4 it is important to consider dated security patches associated with older Clone releases.

References

This solution has no attachment