ORA-40321: invalid bin number, is zero or negative value

ORA-40321: invalid bin number, is zero or negative value

Cause: Input bin number has zero or negative values.

Action: Provide positive bin numbers starting from 1.

ORA-40306: wide data not supported for decision tree model create

ORA-40306: wide data not supported for decision tree model create

Cause: Wide data (DM_NESTED_NUMERICALS and or or DM_NESTED_ CATEGORICALES) is being passed to the decision tree model create routine. These datatypes are currently not supported for tree builds.

Action: Remove columns of these datatypes from the input.

ORA-40305: invalid impurity metric specified

ORA-40305: invalid impurity metric specified

Cause: Impurity metric specified is not valid. Examples of valid metrics are TREE_IMPURITY_GINI, TREE_IMPURITY_ENTROPY.

Action: Consult documentation for valid impurity metrics and specification.

ORA-40304: invalid classname string in prior probability specification

ORA-40304: invalid classname string in prior probability specification

Cause: Actual or predicted classname specified is not present in training data.

Action: Provide valid classname(s) in prior probability specification.

ORA-40303: invalid prior probability specification

ORA-40303: invalid prior probability specification

Cause: Valid prior probabilities not specified. Valid probabilities should be between 0 and 1.

Action: Consult documentation for valid prior probability specification.

ORA-40302: invalid classname string in cost matrix specification

ORA-40302: invalid classname string in cost matrix specification

Cause: Actual or predicted classname specified is not present in training data

Action: Provide valid classname(s) in cost matrix specification

ORA-40301: invalid cost matrix specification

ORA-40301: invalid cost matrix specification

Cause: A valid cost matrix is not specified.

Action: Consult documentation for valid cost matrix specification.

ORA-40291: model cost not available

ORA-40291: model cost not available

Cause: The supplied model was assumed to have been built with a cost matrix specification, when in reality, it was not.

Action: Provide a model name that corresponds to a model that was built with an appropriate cost matrix specification.

ORA-40290: model incompatible with data mining function

ORA-40290: model incompatible with data mining function

Cause: The supplied model cannot be operated upon by the data mining function because the model is built for a mining function and or or based on an algorithm that is incompatible with function.

Action: Provide the name of the model suitable for the function.

ORA-40289: duplicate attributes provided for data mining function

ORA-40289: duplicate attributes provided for data mining function

Cause: A duplicate, non-nested attribute was provided as input to the data mining function. A duplicate attribute is one which is present in the model signature, occurs more than once in the USING clause after tablename expansion, and is not a collection element in a nested table column.

Action: Eliminate the duplicate attribute(s).

ORA-40287: invalid data for model - cosine distance out of bounds

ORA-40287: invalid data for model - cosine distance out of bounds

Cause: The norm computed using attribute values from the incoming row for the cosine model is outside the range 0-1.

Action: Remove or correct the data in the offending row.

ORA-40286: remote operations not permitted on mining models

ORA-40286: remote operations not permitted on mining models

Cause: An attempt was made to perform queries or DML operations on remote tables using local mining models.

Action: Remove the reference to remote tables in the statement.

ORA-40285: label not in the model

ORA-40285: label not in the model

Cause: The model does not have the label.

Action: Provide valid label.

ORA-40284: model does not exist

ORA-40284: model does not exist

Cause: The model entered does not exist.

Action: Check spelling.

ORA-40283: missing cost matrix

ORA-40283: missing cost matrix

Cause: Cost matrix specification is missing.

Action: Provide valid cost matrix specification. Check syntax for data mining functions.

ORA-40282: invalid cost matrix

ORA-40282: invalid cost matrix

Cause: Cost matrix specification is invalid.

Action: Provide valid cost matrix specification. Check syntax for data mining functions.

ORA-40281: invalid model name

ORA-40281: invalid model name

Cause: A model name is invalid or does not exist.

Action: Check spelling. A valid model name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word.

ORA-40273: invalid model type string for Adaptive Bayes Network algorithm

ORA-40273: invalid model type string for Adaptive Bayes Network algorithm

Cause: The valid values for the abns_model_type settings are: abns_multi_ feature, abns_single_feature, abns_naive_bayes.

Action: Use a valid value for the abns_model_type setting.

ORA-40272: apply rules prohibited for this model mode

ORA-40272: apply rules prohibited for this model mode

Cause: Adaptive Bayes Network rules are only generated for SingleFeature ABN models

Action: Rebuild model in SingleFeature mode and then apply with rules.

ORA-40271: no statistically significant features were found

ORA-40271: no statistically significant features were found

Cause: Input data inadequate in volume and or or quality to derive statistically significant predictions for building a Adaptive Bayes Network model.

Action: Provide a well-prepared training data set.

ORA-40262: NMF: number of features not between (1, string(

ORA-40262: NMF: number of features not between (1, string(

Cause: The number of requested features must be greater than 1, and less than the smaller of the number of attributes and the number of cases in the dataset.

Action: Specify the desired number of features within the acceptable range.

ORA-40261: input data for model build contains negative values

ORA-40261: input data for model build contains negative values

Cause: The input data contains negative values, which is not acceptable for a Non-negative Matrix Factorization model.

Action: Provide clean data for build without any negative values.

ORA-40254: priors cannot be specified for one-class models

ORA-40254: priors cannot be specified for one-class models

Cause: Priors were specified.

Action: Do NOT provide priors for one-class models.

ORA-40253: no target counter examples were found

ORA-40253: no target counter examples were found

Cause: One or more of the target classes have only positive examples.

Action: Provide counter examples or remove that target class.

ORA-40252: no target values were found

ORA-40252: no target values were found

Cause: No target values were identified during load.

Action: Validate that the target is correctly specified.

ORA-40251: no support vectors were found

ORA-40251: no support vectors were found

Cause: The input data is non-predictive in nature, or one of the input settings is incorrect or incompatible with respect to the input data.

Action: Provide additional data or change model setting value.

ORA-40226: model upgrade or downgrade must be performed by SYS

ORA-40226: model upgrade or downgrade must be performed by SYS

Cause: Upgrade or Downgrade routines are being invoked by a user with insufficient privilieges.

Action: Run the routines as SYS during migration.

ORA-40225: model is currently in use by another process

ORA-40225: model is currently in use by another process

Cause: The model is currently in use by another process.

Action: Retry if necessary.

ORA-40223: data mining model import failed, job name=string, error=string

ORA-40223: data mining model import failed, job name=string, error=string

Cause: The model import job failed.

Action: Check import job settings as required by DataPump.

ORA-40222: data mining model export failed, job name=string, error=string

ORA-40222: data mining model export failed, job name=string, error=string

Cause: The model export job failed.

Action: Check export job settings as required by DataPump.

ORA-40221: maximum target cardinality exceeded

ORA-40221: maximum target cardinality exceeded

Cause: The target cardinality of the training data was too high.

Action: Reduce the target cardinality.

ORA-40220: maximum number of attributes exceeded

ORA-40220: maximum number of attributes exceeded

Cause: The data had too many attributes.

Action: Reduce the dimensionality of the data.

ORA-40219: apply result table string is incompatible with current operation

ORA-40219: apply result table string is incompatible with current operation

Cause: The current operation was not allowed for the apply result table supplied.

Action: Make sure the operation being performed is valid for the mining function used to build the model (using which the apply result table was created).

ORA-40217: priors table mismatched with training data

ORA-40217: priors table mismatched with training data

Cause: The entries in the priors table do not correspond to the targets in the training data.

Action: Verify the entries in the priors table.

ORA-40216: feature not supported

ORA-40216: feature not supported

Cause: The feature was not supported in the API.

Action: Modify the code to avoid usage of the feature.

ORA-40215: model string is incompatible with current operation

ORA-40215: model string is incompatible with current operation

Cause: The current operation was not supported for the mining function the model corresponds to.

Action: Provide the model name suitable for current operation.

ORA-40214: duplicate setting: string

ORA-40214: duplicate setting: string

Cause: Duplicate setting in the settings table.

Action: Remove the duplicate setting from the settings table.

ORA-40213: contradictory values for settings: string, string

ORA-40213: contradictory values for settings: string, string

Cause: The settings values were not compatible.

Action: Check the documentation and change the setting value(s).

ORA-40212: invalid target data type in input data for string function

ORA-40212: invalid target data type in input data for string function

Cause: Target data type was invalid.

Action: Classification function accepts CHAR,VARCHAR2, and NUMBER targets. Regression function accepts NUMBER targets only.

ORA-40211: algorithm name string is invalid

ORA-40211: algorithm name string is invalid

Cause: Algorithm name for the model was invalid or the operation was not valid for the algorithm.

Action: Check the algorithm name for the model and verify that the operation is valid.

ORA-40209: setting % is invalid for % function

ORA-40209: setting % is invalid for % function

Cause: The specified setting was not supported for the mining function supplied.

Action: Provide appropriate combination of function and algorithm settings.

ORA-40208: duplicate or multiple algorithm settings for function string

ORA-40208: duplicate or multiple algorithm settings for function string

Cause: The input settings table had duplicate or multiple algorithm settings for a mining function.

Action: Provide only one appropriate algorithm setting for the mining function.

ORA-40207: duplicate or multiple function settings

ORA-40207: duplicate or multiple function settings

Cause: The input settings table contained settings for multiple mining functions.

Action: Provide setting(s) for a single function in the settings table.

ORA-40206: invalid setting value for setting name string

ORA-40206: invalid setting value for setting name string

Cause: The input value for the given setting name was invalid.

Action: Consult the documentation for the settings table and provide a valid setting value.

ORA-40205: invalid setting name string

ORA-40205: invalid setting name string

Cause: The input setting name was invalid.

Action: Consult the documentation for the settings table and provide a valid setting name.

ORA-40204: model string already exists

ORA-40204: model string already exists

Cause: A model by the same name exists.

Action: Provide a different, unique name for the model.

ORA-40203: model string does not exist

ORA-40203: model string does not exist

Cause: The model did not exist.

Action: Supply a valid model name.

ORA-40202: column string does not exist in the input table string

ORA-40202: column string does not exist in the input table string

Cause: The column was missing from the table.

Action: Correct the table schema and or or provide the correct column name.

ORA-40201: invalid input parameter string

ORA-40201: invalid input parameter string

Cause: The input parameter was either null or invalid.

Action: Provide a valid value for the input parameter.

ORA-40109: inconsistent logical data record

ORA-40109: inconsistent logical data record

Cause: Repeated instances of a record identifier or repeated attribute(s) in a nested column.

Action: Remove or re-label repeated instances to resolve inconsistencies.

ORA-40108: input data contains too few distinct target (string) values

ORA-40108: input data contains too few distinct target (string) values

Cause: At least two distinct target values are required for Build.

Action: Provide counter-example target values in the input data.

ORA-40107: operation requires string option to be installed

ORA-40107: operation requires string option to be installed

Cause: The specified option has not been installed with the RDBMS.

Action: Install the reported option and retry the operation.

ORA-40106: positive target value not specified for computing Lift

ORA-40106: positive target value not specified for computing Lift

Cause: Positive target value has not been specified for Lift.

Action: Provide a positive target value for the Lift operation.

ORA-40105: input data incompatible with model signature

ORA-40105: input data incompatible with model signature

Cause: The data provided for this post-build operation is in format different from that used for model build.

Action: Provide data whose attribute data types match the build data. Input data attributes must have the same data types as those described in the model signature for the model.

ORA-40104: invalid training data for model build

ORA-40104: invalid training data for model build

Cause: The training data provided in the reported table is unsuitable for build, either because it is empty, has unsuitable data, or the schema of the table does not match the input specifications.

Action: Inspect the training data and correct the contents or schema as appropriate.