Decoupling RPM Dependencies, running Oracle R Distribution (ORD) on Exadata Database Nodes in Docker
Last updated on MAY 10, 2017
Applies to:Oracle Exadata Storage Server Software - Version 184.108.40.206.0 and later
Oracle R Distribution (ORD) is Oracle's distribution of the open source R environment. It is a prerequisite for Oracle R Enterprise (ORE), a set of R packages designed for running R against large volumes of data residing in the Oracle Database. On Linux, ORD is delivered as a set of RPMs that are commonly installed on Exadata Database Nodes. The ORD RPMs bring in Operating System (OS) dependencies that are non-native to the Exadata Operating System. Because of this Exadata Database Node Updating requires the ORD RPMs and dependencies be removed prior updating to a new Exadata release. The goal is decoupling the ORD RPMs and their dependencies from the Exadata Database Operating System. The decoupling is accomplished by the use of Docker and will result in being able to:
• Update Exadata Database nodes without affecting the ORD runtime configuration
• Update the ORD runtime configuration without making changes to the Exadata Database node host Operating System.
This will ease life-cycle management for both Exadata database hosts as well as ORD. Also it will stretch supportability as ORD can now run define it's own runtime.
There will be multiple (evolving) scenario's for running ORD on Exadata. Below you find the manual approach which can be used for any 12.2 Exadata Database Node image. In a next phase a separate, ready to go Docker image will be made available and automate the manual steps using a Docker deployment script that gets executed automatically when the Docker image is downloaded.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms