updated, or customized. However, the Oracle Database Appliance update may not
carry newer version dependencies of customized components. Therefore, you might
be required to remove and subsequently reapply site-specific changes to successfully
update Oracle Database Appliance in the future.
Caution:
For database nodes, do not update the following:
•
Oracle Linux Kernel (kernel*)
•
Oracle Optimal Flexible Architecture (ofa*)
•
Oracle InfiniBand-related packages (ofed*)
For storage, do not apply any RPM updates.
About Using a Different Version of Java Development Kit (JDK)
Oracle Database Appliance depends on a specific version of JDK. If you want to use a
different version of JDK for a specific application, then install it in a different directory
and only point to it for that application.
About Migrating Oracle Database Appliance to the DCS
Stack
When you apply the patches for this release, your bare metal deployments of Oracle
Database Appliance are migrated from the OAK stack to the DCS stack.
No additional configuration steps are required. You migrate the Oracle Database
Appliance bare metal system to the DCS stack when you apply the latest patches.
Note:
When you migrate Oracle Database Appliance bare metal system to the
DCS stack, the Database Class is set to Online Transaction Processing
(OLTP) and the Database Shape is set to
odb1
, by default.
See ODACLI Command Reference for OAKCLI Migration for the equivalent ODACLI
and OAKCLI commands.
About Update Pre-Checks
Update pre-checks are designed to detect problems that might be encountered during
patching and flag those issues.
The pre-checks view the state of the appliance, including the version and hardware
specific upgrades, verify that the necessary conditions and checks are complete
before attempting an upgrade, and identify conditions that might cause an upgrade to
Chapter 7
About Migrating Oracle Database Appliance to the DCS Stack
7-3
Summary of Contents for Database Appliance X6-2-HA
Page 15: ...Index xv...
