Oracle Enterprise Linux / OEL support

Aspera products packaged in the Linux RPM format are compatible with Linux distributions built from Redhat Enterprise Linux (RHEL) source packages. These include but are not limited to: RHEL itself, CentOS, and Oracle Enterprise Linux (OEL).

OEL is largely built from Redhat Enterprise Linux source packages, and when booted using the "Redhat Compatible Kernel" is guaranteed by Oracle to be compatible with the equivalent release of RHEL. Aspera products packaged as RPMs are fully supported in this configuration.

OEL is however shipped with and defaults to use of Oracle's "Unbreakable Enterprise Kernel" (UEK) which is built from an Oracle maintained kernel source tree. The Oracle kernel uses a more recent kernel source version, and includes functionality not found in stock linux kernels (such as the ksplice "no downtime" patching feature and the dtrace tracing facility). The Oracle kernel is tuned for use in systems that run other Oracle technology (such as the Oracle database or Oracle java application servers.)

Aspera products packaged as RPMs should work without issues on the Oracle UEK, but are supported on a best effort basis only. Customers running the UEK who experience issues with Aspera functionality should reboot the system into the Redhat Compatible Kernel to verify whether the issue persists in the "stock supported" configuration. Details of product functionality for both kernels must be submitted in cases where the initial error is reported against the UEK.

To make testing with alternative kernels easier, the shell script attached to this KB article can be used to reboot a RHEL 6.X.x derived system with an alternative kernel on a one-time basis. (That is, the script allows the administrator to choose an alternetive kernel to boot the system with *at the next reboot only*. A subsequent reboot will return to the system default kernel. This is useful on systems where the system console is not easily avaiable).

Attachments

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk