Table Formats

Oracle Data Mining supports one basic format for data tables:

For association models only, Oracle Data Miner supports the following format:

Transactional format is typically used for market basket data.

Algorithms and Table Format

Association models created using Oracle Data Miner require data in transactional format.

All other models require a non-transactional case table. Transactional data can be added by joining it to the case table.

All models except for Association models can have either pure single-record case format input or input consisting of transactional data joined to a non-transactional case table. Oracle Data Mining Tutorial contains an example showing how to create a case table and then join transactional data to it.

Restriction: Attribute Name in transactional format should be no longer than 30 characters. Oracle Data Mining does not support longer attribute names (that is, attribute names having datatype VARCHAR2(n) with n>30) in operations such as model building.

Nested Tables

A nested table type models an unordered set of elements. The elements may be built-in types or user-defined types. You can view a nested table as a single-column table or, if the nested table is an object type, as a multicolumn table, with a column for each attribute of the object type.

Oracle Data Miner has limited support for nested tables, as follows: