4.5 Verifying the Oracle R Enterprise Server Installation

The Oracle R Enterprise server installation script creates log files in the server subdirectory of the installation directory. Examine the log files to verify the success of the installation process.

The following commands on a Linux or UNIX system list the log files:

cd ./oreserver_install_dir/server
ls *.log
outcdb.log  rqconfig.log  rqdrop.log  rqgrant.log  rqinst.log  rqpdrp.log  rqproc.log  rquser.log

If there are problems with the installation and you are unable to resolve them, you can request help from My Oracle Support or from the Oracle R Enterprise Forum.

4.5.1 Validating Basic Oracle R Enterprise Functionality

After connecting to the database, test the basic functionality of Oracle R Enterprise with these commands.

First execute these commands from an R instance directly on the database server and then execute them from the Oracle R Enterprise client.

## Is the ORE client connected to the ORE server?
## The output of this command should be TRUE.
ore.is.connected()

## List the available database tables 
ore.ls()

## Push an R dataframe to a database table
CARS <- ore.push(cars)
head(CARS)

## Run embedded R
ore.doEval(function(){library(ORE)})

4.5.2 Running the Oracle R Enterprise Example Scripts

To fully validate the success of the installation, run the suite of Oracle R Enterprise demo scripts.

In a successful installation, all demo scripts run to completion without errors.

The example scripts are located in $ORACLE_HOME/R/library/ORE/demo.

This R command provides a list of available examples:

demo(package="ORE")

These commands run two of the examples. The aggregate script tests the use of an R function on data that is resident in database memory; the row_apply script tests embedded R execution.

demo("aggregate", package="ORE")
demo("row_apply", package="ORE")

This command exits from R.

q()