Installing Oracle Data Miner

The scripts described in this document are available to manage the Oracle Data Miner Repository. These scripts are also integrated with Oracle SQL Developer  to allow users to manage the repository through SQL Developer as well.

It is not necessary to install SQL Developer to run the installation scripts for Oracle Data Miner.

Download the scripts directly from the Oracle Data Miner page at Oracle Technology Network.

Download the file and unzip it.

Using SQL*Plus, log in as SYS, and run the appropriate script.

Installing the Oracle Data Miner Repository

installodmr.sql installs the Oracle Data Miner Repository; use it as follows:

set serveroutput on
@installodmr.sql <default_tablespace> <temp_tablespace>

Example: @installodmr.sql USER TEMP

The initial space requirement for the Data Miner Repository can range from 200MB to 700MB depending on the tablespace setting; however, the repository will grow as metadata is added.

The script will take approximately 10 minutes to run for remote database installation and 2 minutes for local database installation.

See Loading and Dropping Sample Tables to load sample data.

Granting a User the Rights to Access the Repository

usergrants.sql user account grants the specified user account the rights required by Oracle Data Miner to use the Oracle Data Miner Repository. For example,

@usergrants.sql MININGACCT

dropusergrants.sql user account revokes all of these grants. For example,

@dropusergrants.sql MININGACCT

See Loading and Dropping Sample Tables to load sample data.

Dropping the Oracle Data Miner Repository

dropRepositoryAndUserObjects.sql drops the Repository and the user objects. 

@dropRepositoryAndUserObjects.sql <session_disconnect>

For example:

@dropRepositoryAndUserObjects.sql DR
 

To avoid session locks that can block the drop repository process, the drop repository script has an option to disconnect sessions connected that have the ODMRUSER role privilege.  The session_disconnect parameter allows the user to disconnect such sessions automatically or to just report on any instances of such sessions. If any sessions are detected but not automatically disconnected, the drop repository process is aborted.

The session_disconnect parameter has the following options:

R = report only, do not disconnect any sessions
D = disconnect only, displays disconnect  only
DR or RD = disconnect and report

All workflows and internal tables will be dropped. Models created by Oracle Data Miner will not be dropped. Tables created by the Create Table node will not be dropped.

See Loading and Dropping Sample Tables to drop sample data.

Migrating the Oracle Data Miner Repository

migrateodmr.sql migrates the Data Miner Repository from an earlier version to the current version. All workflows created by users are preserved; only the repository software is updated.  

@migrateodmr.sql <session_disconnect>

For example:

@migrateodmr.sql DR
To avoid session locks that can block the migrate repository process, the migrate repository script has an option to disconnect sessions connected that have the ODMRUSER role privilege.  The session_disconnect parameter allows the user to disconnect such sessions automatically or to just report on any instances of such sessions. If any sessions are detected but not automatically disconnected, the drop repository process is aborted.

The session_disconnect parameter has the following options:

R = report only, do not disconnect any sessions
D = disconnect only, displays disconnect  only
DR or RD = disconnect and report


Loading and Dropping Sample Tables

These scripts load and remove the sample data used in the Cue Cards and in the Oracle by Example (OBE) for Oracle Data Miner: