Installing ORE – Part B
This is the second part of a two part blog post on installing ORE.
In reality there are 3 blog posts on installing ORE. The third and next blog post will be on a particular issue you might encounter on a Windows server and how you can over come the issue.
In the previous blog post I outlined the steps needed to install ORE on the database server and on the client machine. Click here to go to this post.
In this blog post I will show you how to setup a schema for ORE and how to get connected to the schema using ORE.
Step 3 : Setting up your Schema to use ORE / Tasks for your DBA
On the server when you unzipped the ORE download, you will find a demo_user.bat script (something similar like demo_user.sh on Linux).
After the script has performed some checks, you will be asked do you want to create a demo schema. Enter yes for this task to be completed and the RQUSER schema will be created in your schema. Then enter the password for the RQUSER.
The RQUSER can as a small set of system privileges that allow it to connect to and perform some functions on the database. This include:
GRANT CREATE TABLE TO RQUSER;
GRANT CREATE PROCEDURE TO RQUSER;
GRANT CREATE VIEW TO RQUSER;
GRANT CREATE MINING MODEL TO RQUSER;
NOTE: If you cannot connect to the database using the RQUSER and the password you set, then you might need to also grant CONNECT and RESOURCE to it too.
For every schema that you want to access using ORE you will need to grant the above to them.
In addition to these grants, if you want a schema to be able to create and drop R scripts in the database then you will need to grant them the addition role of RQADMIN.
sqlplus / AS SYSDBA
GRANT RQADMIN to RQUSER;
NB: You will need to grant RQADMIN to an schema where you want to use the embedded ORE in the database.
Step 4 : Connecting to the Database
If you have complete all of the above steps you are now ready to use ORE to connect to your database. The following is an example of the ore.connect command that you can use. It is assuming the RQUSER has the password RQUSER, and the the host is on the local machine (localhost). Replace localhost with the host name of your database server and also change the SID to that of your database.
ore.connect(user=”rquser”, sid=”orcl”, host=”localhost”, password=”rquser”, port=1521, all=TRUE);
If you get no errors and you get the R prompt back then you are connected to the RQUSER schema in your database.
To test that the connection was made you can run the following ORE command and then list the tables in the schema.
The output of the last line above tells us that we do not have any tables in our RQUSER schema. I will have more blog posts on how you can use ORE and perform various ORE analytics in future posts.
There are a series of demonstrations that come with ORE. To access these type in the following command which will list the available ORE demos.
The following command illustrates how you can run the ORE demo called basic.
> demo(basic, package=”ORE”)
Also check out the Part C blog post on how to resolve a potential install issue on a Windows server.
One thought on “Installing ORE – Part B”
September 14, 2014 at 5:24 pm
Thank you for this post.
LikeLiked by 1 person