|Oracle® Data Mining Concepts
11g Release 2 (11.2)
Part Number E16808-03
This section describes new features in Oracle Data Mining. It includes the following sections:
In Oracle Data Mining 11g Release 2 (220.127.116.11), you can import externally-created data mining models when they are presented as valid PMML documents. PMML is an XML-based standard for representing data mining models.
IMPORT_MODEL procedure in the
DBMS_DATA_MINING package is overloaded with syntax that supports PMML import. When invoked with this syntax, the
IMPORT_MODEL procedure will accept a PMML document and translate the information into an Oracle Data Mining model. This includes creating and populating model tables as well as
SYS model metadata.
Oracle Database PL/SQL Packages and Types Reference for details about
Mining Model schema objects
In Oracle 11g, Data Mining models are implemented as data dictionary objects in the
SYS schema. A set of new data dictionary views present mining models and their properties. New system and object privileges control access to mining model objects.
In previous releases, Data Mining models were implemented as a collection of tables and metadata within the
DMSYS schema. In Oracle 11g, the
DMSYS schema no longer exists.
Automatic Data Preparation (ADP)
In most cases, data must be transformed using techniques such as binning, normalization, or missing value treatment before it can be mined. Data for build, test, and apply must undergo the exact same transformations.
In previous releases, data transformation was the responsibility of the user. In Oracle Database 11g, the data preparation process can be automated. Algorithm-appropriate transformation instructions are embedded in the model and automatically applied to the build data and scoring data. The automatic transformations can be complemented by or replaced with user-specified transformations.
Because they contain the instructions for their own data preparation, mining models are known as supermodels.
Chapter 19 for information on automatic and custom data transformation for Data Mining
Oracle Database PL/SQL Packages and Types Reference for information on
Scoping of Nested Data and Enhanced Handling of Sparse Data
Oracle Data Mining supports nested data types for both categorical and numerical data. Multi-record case data must be transformed to nested columns for mining.
In Oracle Data Mining 10gR2, nested columns were processed as top-level attributes; the user was burdened with the task of ensuring that two nested columns did not contain an attribute with the same name. In Oracle Data Mining 11g, nested attributes are scoped with the column name, which relieves the user of this burden.
Handling of sparse data and missing values has been standardized across algorithms in Oracle Data Mining 11g. Data is sparse when a high percentage of the cells are empty but all the values are assumed to be known. This is the case in market basket data. When some cells are empty, and their values are not known, they are assumed to be missing at random. Oracle Data Mining assumes that missing data in a nested column is a sparse representation, and missing data in a non-nested column is assumed to be missing at random.
In Oracle Data Mining 11g, Decision Tree and O-Cluster algorithms do not support nested data.
Generalized Linear Models
A new algorithm, Generalized Linear Models, is introduced in Oracle 11g. It supports two mining functions: classification (logistic regression) and regression (linear regression).
See Also:Chapter 12, "Generalized Linear Models"
New SQL Data Mining Function
A new SQL Data Mining function,
PREDICTION_BOUNDS, has been introduced for use with Generalized Linear Models.
PREDICTION_BOUNDS returns the confidence bounds on predicted values (regression models) or predicted probabilities (classification).
Enhanced Support for Cost-Sensitive Decision Making
Cost matrix support is significantly enhanced in Oracle 11g. A cost matrix can be added or removed from any classification model using the new procedures,
The SQL Data Mining functions support new syntax for specifying an in-line cost matrix. With this new feature, cost-sensitive model results can be returned within a SQL statement even if the model does not have an associated cost matrix for scoring.
Only Decision Tree models can be built with a cost matrix.
Features Not Available in This Release
Oracle Data Mining Scoring Engine
In Oracle 10.2, you could use Database Configuration Assistant (DBCA) to configure the Data Mining option. In Oracle 11g, you do not need to use DBCA to configure the Data Mining option.
Basic Local Alignment Search Tool (BLAST)
Adaptive Bayes Network classification algorithm (replaced with Decision Tree)
DM_USER_MODELS view and functions that provide information about models, model signature, and model settings (for example,
GET_MODEL_SIGNATURE) are replaced by data dictionary views. See Oracle Data Mining Application Developer's Guide.
The Oracle Data Mining Java API (OJDM) fully supports the new features in Oracle Data Mining 11g Release 2 (11.2). This section provides a summary of the new features in the Java API. For details, see Oracle Data Mining Java API Reference (Javadoc).
As described in "Mining Model schema objects", mining models in 11g Release 2 (11.2) are data dictionary objects in the
SYS schema. System and object privileges control access to mining models.
In the Oracle Data Mining Java API, a new extension method
OraConnection.getObjectNames is added to support listing of mining objects that can be accessed by a user. This method provides various object filtering options that applications can use as needed.
As described in "Automatic Data Preparation (ADP)", Oracle Data Mining 11g Release 2 (11.2) supports automatic and embedded data preparation (supermodels).
In the Oracle Data Mining Java API, a new build setting extension method,
OraBuildSettings.useAutomatedDataPreparations, is added to enable ADP. Using the new
OraBuildTask.setTransformationSequenceName, applications can embed the transformations with the model.
Two new GLM packages are introduced:
oracle.dmt.jdm.modeldetail.glm. These packages have GLM algorithm settings and model details interfaces respectively.
New apply content enumeration values,
probabilityUpperBound, are added to specify probability bounds for classification apply output. The enumeration
oracle.dmt.jdm.supervised.classification.OraClassificationApplyContent specifies these enumerations. Similarly apply contents enumeration values
predictionUpperBound are added to specify prediction bounds for regression model apply output. In this release only GLM models support this feature.
New static methods
removeCostMatrix are added to
OraClassificationModel to support associating a cost matrix with the model. This will greatly ease the deployment of costs along with the model.
Mining task features are enhanced to support the building of mining process workflows. Applications can specify dependent tasks using the new
OraTask.addDependency method. Another notable new task feature is
overwriteOutput, which can be enabled by calling the new
With these new features, applications can easily develop mining process workflows and deploy them to the database server. These task workflows can be monitored from the client side. For usage of these methods refer to the demo programs shipped with the product (See Oracle Data Mining Administrator's Guide for information about the demo programs.)
A new mining object,
oracle.dmt.jdm.transform.OraTransformationSequence supports the specification of user-defined transformation sequences. These can either be embedded in the mining model or managed externally. In addition, the new
OraExpressionTransform object can be used to specify SQL expressions to be included with the model.
oracle.dmt.jdm.OraProfileTask is added to support the new predictive analytics profile functionality.
The Oracle Data Mining Java API can be used with Oracle Database 11g Release 2 (11.2) and with Oracle Database 10.2. When used with a 10.2 database, only the 10.2 features are available.