This chapter describes administrative tasks for maintaining and optimizing Oracle R Enterprise. This chapter contains these topics:
An Oracle wallet is a password-protected container for storing security credentials in Oracle Database. Wallets provide a secure mechanism for specifying connection details in embedded R scripts.
To create a wallet for an Oracle R Enterprise connection:
Start Oracle Wallet Manager:
(Linux and UNIX) At the command line, enter
(Windows) Select Start, Programs, Oracle-HOME_NAME, Integrated Management Tools, Wallet Manager.
Follow the instructions in your Oracle Database documentation to create the wallet:
For Oracle Database 11.2, see: "Using Oracle Wallet Manager" in Oracle Database Advanced Security Administrator's Guide
For Oracle Database 12.1, see: "Using Oracle Wallet Manager" in Oracle Database Enterprise User Security Administrator's Guide.
Locate the connection string for the Oracle R Enterprise database in
tnsnames.ora. For example:
mydb_test = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = server23) (PORT = 1521) ) (CONNECT_DATA = (sid=ORCL)) )
Specify the connection information in the wallet. Follow the instructions in the Oracle Database security documentation referenced in step 2.
After you configure the wallet, you can connect to the Oracle R Enterprise server database by simply specifying the connection identifier. For example:
ore.connect(conn_string = "mydb_test", all = TRUE)
See Also:R help for
You can control the memory used by embedded R execution by limiting the heap memory (vector and cons in R terminology) that is automatically managed by the R
gc mechanism. To limit the size of heap memory in the database, use the
sys.rqconfigset utility. The keyword arguments for
sys.rqconfigset are described in Table 7-1.
Minimum R vector heap memory
Maximum R vector heap memory
Minimum number of R cons cells
Maximum number of R cons cells
-- Set the minimum R vector heap memory to 20MB SQL> EXEC sys.rqconfigset('MIN_VSIZE', '20MB'); -- Set the maximum R vector heap memory to 100MB SQL> EXEC sys.rqconfigset('MAX_VSIZE', '100MB') -- Set the minimum number of R cons cells to 500x1024 SQL> EXEC sys.rqconfigset('MIN_NSIZE', '500K'); -- Set the maximum number of R cons cells to 10x10x1024 SQL> EXEC sys.rqconfigset('MAX_NSIZE', '10MB'); -- Set maximum vector heap memory and maximum cons cells to unlimited SQL> EXEC sys.rqconfigset('MAX_VSIZE', NULL); SQL> EXEC sys.rqconfigset('MAX_NSIZE', NULL);
sys.rqconfigsetprocedure does not control the C type memory that may be allocated by Calloc, Realloc, calloc, or malloc. Such C type memory is mainly created to hold temporary values used by R functions that are implemented in C. Under normal circumstances, C type memory is limited in size and does not significantly affect the memory usage of R.
Note on IBM AIX:Upgrade from Oracle R Enterprise 1.1 is not supported on IBM AIX. To upgrade Oracle R Enterprise 1.1 on IBM AIX, first uninstall Oracle R Enterprise 1.1 (including R) and then download and install the later version.
To upgrade Oracle R Enterprise:
Ensure that you have the version of R that is required for the new version of Oracle R Enterprise. See Oracle R Enterprise Release Notes for the latest requirements.
To install R, follow the instructions in Chapter 3, "Installing R".
To upgrade Oracle R Enterprise Server, follow the installation procedures. When the installation script detects an earlier version of Oracle R Enterprise, it asks if you want to upgrade. Answering
No aborts the process; answering
Yes starts the upgrade.
See Chapter 4 for the Oracle R Enterprise Server installation instructions.
To upgrade Oracle R Enterprise Client, re-install the client packages and client supporting Packages. You do not have to uninstall the current packages before installing the new packages.
See Chapter 5 for the Oracle R Enterprise Client installation instructions.
An uninstall script is included with the Oracle R Enterprise Server files in the
server directory. The script removes the libraries that were installed in
$ORACLE_HOME/lib and drops all the database objects that were created by the Oracle R Enterprise Server installation.
The user that runs the uninstall script must satisfy the requirements specified in Section 4.2.3, "User Requirements".
On a Linux system, you could uninstall Oracle R Enterprise Server as follows:
% cd download_path/server/ % ./uninstall.sh
R> remove.packages("ORE") R> remove.packages("ORExml") R> remove.packages("OREeda") R> remove.packages("OREgraphics") R> remove.packages("OREstats") R> remove.packages("OREbase") R> remove.packages("ROracle") R> remove.packages("DBI") R> remove.packages("png") R> remove.packages("OREdm") R> remove.packages("OREpredict")
Uninstall Open Source R just as you would uninstall any other Windows program. using Add or Remove Programs from the Windows Control Panel.
To uninstall Oracle R Distribution on Linux, log in as root and execute these commands in this order. To uninstall a different version of R, replace
2.15.3 with the version number.
# rpm -e R-2.15.3 # rpm -e R-devel # rpm -e R-core # rpm -e libRmath-devel # rpm -e libRmath
To uninstall Oracle R Distribution on Oracle Solaris, follow the instructions in the readme on the Oracle R Distribution download page on the Oracle Technology Network:
The Oracle R Distribution installation directory on Oracle Solaris includes an uninstall script. Log in as root and run the script as follows:
To uninstall Oracle R Distribution on IBM AIX, follow the instructions in the readme on the Oracle R Distribution download page on the Oracle Technology Network:
To uninstall all filesets execute the following command as root:
# installp -u ORD
You can also uninstall independent filesets. For example, the following commands uninstall only
# installp -u ORD.devel # installp -u ORD.core