Skip Headers
Oracle® Data Mining Administrator's Guide
11g Release 1 (11.1)

Part Number B28130-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Users and Privileges for Data Mining

This chapter explains how to create data mining users and control their mining activities through the use of database privileges.

See Also:

Oracle Database Security Guide for comprehensive information on Oracle Database security.

This chapter contains the following topics:

Creating Data Mining Users

Data Mining should be performed by a user that is specifically configured for data mining activities.

The following SQL statement creates a user named dmuser with the password dmuser_password. The user will use a tablespace called default_tablespace by default; its temporary tablespace is called temp_tablespace. Tablespaces for Data Mining users should be assigned according to standard DBA practices, depending on system load and system resources.

SQL>CREATE USER dmuser IDENTIFIED BY dmuser_password
       DEFAULT TABLESPACE default_tablespace
       TEMPORARY TABLESPACE temp_tablespace
       QUOTA UNLIMITED on default_tablespace;

You must be logged on as a system administrator to create users and grant privileges.

Note:

To create a user that can use the Data Mining sample programs, you need to run two configuration scripts as described in "Create a Data Mining Demo User".

Privileges Required for Data Mining

Oracle Corporation recommends a set of basic privileges for data mining. The following GRANT statements grant these privileges to a user named dmuser.

GRANT create mining model TO dmuser;
GRANT create procedure TO dmuser;
GRANT create session TO dmuser;
GRANT create table TO dmuser;
GRANT create sequence TO dmuser;
GRANT create view TO dmuser;
GRANT create job TO dmuser;
GRANT create type TO dmuser;
GRANT create synonym TO dmuser;

The CREATE MINING MODEL privilege is required for creating models. The other privileges may not be required for some mining activities, however it is prudent to grant them all as a group.

SELECT access to the data being mined is always required. The following example allows dmuser to mine data in the CUSTOMERS table in the SH schema.

GRANT SELECT ON customers TO dmuser;

EXECUTE access to the Oracle Text package ctxsys.ctx_ddl is required for text mining.

GRANT EXECUTE ON ctxsys.ctx_ddl TO dmuser;
 

Additional access rights are required for exporting and importing mining models, as described in "Exporting and Importing Mining Models".

Additional system and object privileges described in the following sections can be used to enable or restrict particular mining activities.

System Privileges for Mining Models

A system privilege confers the right to perform a particular action in the database or to perform an action on a type of schema objects. For example, the privileges to create tablespaces and to delete the rows of any table in a database are system privileges.

To grant a system privilege, you must either have been granted the system privilege with the ADMIN OPTION or have been granted the GRANT ANY PRIVILEGE system privilege.

The system privileges listed in Table 4-1 are required for performing specific operations on mining models.

Table 4-1 System Privileges for Mining Model

System Privilege Allows you to ....

CREATE MINING MODEL

Create mining models in your own schema.

CREATE ANY MINING MODEL

Create mining models in any schema.

ALTER ANY MINING MODEL

Change the name or cost matrix of any mining model in any schema.

DROP ANY MINING MODEL

Drop any mining model in any schema.

SELECT ANY MINING MODEL

Apply a mining model in any schema, also view model details in any schema.

COMMENT ANY MINING MODEL

Add a comment to any mining model in any schema.

AUDIT ANY

Generate an audit trail for any mining model (or any object) in any schema.


Object Privileges on Mining Models

An object privilege confers the right to perform a particular action on a specific schema object. For example, the privilege to delete rows from the SH.PRODUCTS table is an example of an object privilege.

A user automatically has all object privileges for schema objects contained in his or her schema. A user can grant any object privilege on any schema object he or she owns to any other user or role.

Table 4-2 Object Privileges for Data Mining

Object Privilege Allows you to ....

ALTER MINING MODEL

Change the name or cost matrix of the specified mining model object.

SELECT MINING MODEL

Apply or view the specified mining model object.