1. Maintenance Guide
  2. Updating Exadata Software
  3. Planning for Software Maintenance
  4. Configuration and Operational Best Practices for Software Maintenance
  5. Version Compatibility and Mixed Version Support

8.2.2.5 Version Compatibility and Mixed Version Support

It is recommended that software for all components be updated regularly to stay in step with the recommended minimum release in order to maintain the most stable and secure system.

However, it is supported to update only a subset of components during a software maintenance window while the remaining components remain at an earlier version. For example, the following scenarios are supported:

  • Update a subset of Oracle Exadata storage servers to a higher version of the Oracle Exadata System Software while the remaining storage servers remain at the earlier Oracle Exadata System Software version.

  • Update Oracle Exadata storage servers to a higher version of the Oracle Exadata System Software while the database servers remain at the earlier Oracle Exadata System Software version.

  • Update Oracle Exadata database servers to a higher version of the Oracle Exadata System Software while the storage servers remain at the earlier Oracle Exadata System Software version.

  • Update Oracle Exadata storage servers to a higher version of the Oracle Exadata System Software while RDMA Network Fabric switches remain at the earlier Oracle Exadata System Software version.

  • Update RDMA Network Fabric switches to a higher version of the Oracle Exadata System Software while Oracle Exadata storage servers remain at the earlier Oracle Exadata System Software version.

  • Update Oracle Exadata storage servers to a higher version of the Oracle Exadata System Software while Oracle Grid Infrastructure or Oracle Database software remains at an earlier release and update level.

While mixed versions are supported (within the same component or across different components), it is highly recommended that this be only a temporary configuration that exists for the purpose and duration of rolling upgrade.

If mixing versions the following rules and considerations must be observed:

  • A specific generation of Oracle Exadata hardware will have a minimum required Oracle Exadata System Software version. For example, Oracle Exadata X6 hardware requires Oracle Exadata System Software release 12.1.2.3.1 or higher.

  • A specific Oracle Database release requires a minimum Oracle Exadata System Software release to fully support Oracle Exadata features. For example, Oracle Database 12c Release 2 (12.2) requires Oracle Exadata System Software release 12.2.1.1.0 or higher on storage servers to support all Oracle Exadata offload features.

  • Features supplied with a new Oracle Exadata System Software release may require a minimum Oracle Grid Infrastructure or Oracle Database software release or release update. For example, the Oracle Exadata feature Smart Scan Offload for Compressed Index Scan requires Oracle Database 12.2 and Oracle Exadata System Software 12.2 on storage servers.

  • Oracle Grid Infrastructure supports mixed versions only during a rolling update (for example, while updating from release 12.1.0.2 to 12.2.0.1, or updating from release 12.1.0.2.161018 to 12.1.0.2.170117). Some Oracle Clusterware functionality is restricted while the cluster is in rolling upgrade mode.

  • Oracle Database supports mixed versions only during a rolling update (for example, while updating from release 12.1.0.2.161018 to 12.1.0.2.170117).

Related Topics

Parent topic: Configuration and Operational Best Practices for Software Maintenance