12C ORA-错误汇总16 ORA-40001 to ORA-40556

分享一下我老师大神的人工智能教程！零基础，通俗易懂！http://blog.csdn.net/jiangjunshow

也欢迎大家转载本篇文章。分享知识，造福人民，实现我们中华民族伟大复兴！

                ORA-40001: value for string must be greater than zero
Cause: The input parameter in question has a value of zero or less.
Action: Provide a value greater than zero for the relevant parameter.
ORA-40002: wordsize must be string or greater
Cause: The input wordsize is less than the prescribed limit for the BLAST Match
or Align algorithm.
Action: Provide a wordsize greater than or equal to the prescribed value.
ORA-40003: wordsize must be in the range string - string for BLAST-P
Cause: The input wordsize has a value out of the prescribed range.
Action: Provide a wordsize value within the prescribed range for BLAST-P.
ORA-40004: penalty must be negative for BLAST-N
Cause: The input value provided for penalty is zero or greater.
Action: Provide a negative penalty value.
ORA-40021: no column named string in training table string
Cause: The training table does not contain the specified column
Action: Provide a case-id/target column that exists in the training table
ORA-40022: null case ID column - cannot provide row diagnostics in string
Cause: A row diagnostics table name was provided, but without a corresponding
case or row identifier column in the build data.
Action: Provide a non-null case identifier column in the build data to identify
rows in the row diagnostics table.
ORA-40023: sufficient memory could not be allocated given the number of
attributes
Cause: Unable to allocate sufficient memory to create a model capable of
producing confidence bounds on predictions because there were too many
attributes or there were high cardinality categorical attributes, or both, in the build
data.
Action: Reduce the number of attributes, especially high cardinality categoricals,
or enable ridge regression.
ORA-40024: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular.
22-2 Oracle Database Error Messages
Action: Enable ridge regression or remove exact multicollinearities from the build
data.
ORA-40025: reference class name not found in build data
Cause: The provided reference class name was not found in the build data.
Action: Provide an existing target value as the reference class name.
ORA-40026: reference class name not found in the weights table
Cause: The provided reference class name did not correspond to any of the entries
in the weights table.
Action: Provide consistent specification for reference class name and weights
table.
ORA-40027: Target attribute has more than two distinct values
Cause: Generalized Linear Models only support binary classification.
Action: Consolidate target values into two distinct categories.
ORA-40028: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor build data were not properly
scaled.
Action: Standardize the predictor build data by enabling auto prep.
ORA-40029: Specified diagnostics table name already exists
Cause: A diagnostics table name matching an existing table was specified.
Action: Choose a table name that does not match any existing user table.
ORA-40030: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular for the forced-in features.
Action: If there are forced-in features, remove them. If GLMS_FTR_
ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_STRICT, reset it to GLMS_
FTR_ACCEPTANCE_RELAXED and rebuild the model.
ORA-40031: insufficient memory for model build given the number of forced-in
features (maximum allowable for this data: string)
Cause: Unable to allocate sufficient memory to create a feature-selection model
because there were too many forced-in features or the forced-in features were high
cardinality categorical attributes, or both.
Action: Reduce the number of forced-in attributes, especially high cardinality
categoricals.
ORA-40032: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular for the selected features.
Action: If GLMS_FTR_ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_
STRICT, reset it to GLMS_FTR_ACCEPTANCE_RELAXED and rebuild the model.
ORA-40101: Data Mining System Error string-string-string
Cause: An internal system error occured during a data mining operation.
Action: Contact Oracle Support Services.
ORA-40102: invalid input string for data mining operation string
ORA-40001 to ORA-40556 22-3
Cause: The input parameter is either null or invalid for the given operation.
Action: Provide a valid value. Check range for NUMBER parameters.
ORA-40103: invalid case-id column: string
Cause: The case-id column was invalid. If a case-id column is specified, it must be
present in the input data source. The case-id column cannot be the same as the
target column, and the column's data type is restricted to NUMBER, CHAR, and
VARCHAR2 when building a GLM model with a diagnostics table.
Action: Change the schema of your input data to supply a case-id column of
appropriate data type.
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/schema as appropriate.
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-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-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-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-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-40110: Duplicate model tables found for table type string
Cause: Operation would result in duplicate model table types which is not
supported.
Action: Remove the duplicate entry.
ORA-40111: no mining attributes found in build data
Cause: Could not build a model when only special or empty columns were
present. Special columns include target, row weight, and case ID columns.
Action: Provide mining attribute data.
ORA-40112: insufficient number of valid data rows
22-4 Oracle Database Error Messages
Cause: Fewer than two valid data rows were found in the build data.
Action: Provide at least two valid build data rows. If the model is either a
classification or regression model, then valid rows must have non-NULL targets. If
a weight column was provided, then valid rows must have positive row weights.
In addition, if DELETE_ROW missing value treatment was used, consider
disabling it.
ORA-40113: insufficient number of distinct target values
Cause: Less than two distinct target values were found in the build data.
Action: Provide the classification build data with valid rows containing at least
two distinct target values. Valid rows must have non-NULL targets. If a weight
column was provided, then valid rows must have positive row weights. In
addition, if DELETE_ROW missing value treatment was used, consider disabling
it.
ORA-40114: weights table target values mismatched with build data
Cause: The entries in the weights table did not correspond to the target values in
the build data.
Action: Verify the entries in the weights table.
ORA-40115: weights table schema is incorrect
Cause: The weights table did not have the required schema.
Action: Provide a weights table with schema: (target_value, weight), where the
type of the first column corresponds to the type of the target column (CHAR,
VARCHAR2 or NUMBER) and the type of the second column is NUMBER.
ORA-40116: NULL values found in weights table
Cause: The weights table had NULL entries.
Action: Replace or eliminate all NULL entries in the weights table.
ORA-40117: repeated target values found in weights table
Cause: The weights table had repeated target values.
Action: Remove the repeated target values from the weights table.
ORA-40118: insufficient number of target values in weights table
Cause: The weights table had less that 2 target values.
Action: Provide at least two target values in the weights table.
ORA-40119: nested columns incompatible with missing value treatment
Cause: delete_row missing value treatment is not supported for nested columns.
Action: Use 2D (non-nested) data representation or manually delete the rows with
NULL values and disable the delete_row missing value treatment.
ORA-40120: invalid weight value in the weights table
Cause: Negative or zero weight values were found in the weights table.
Action: Ensure that weight values in the weights table are positive.
ORA-40121: force option not allowed for drop model in different schema
Cause: The force option was specified, but the model is in a different schema.
Action: If the force option is necessary, run the drop model from the owning
schema. If the force option is not necessary, set the force parameter to FALSE.
ORA-40001 to ORA-40556 22-5
ORA-40122: invalid data type for row weights column string.
Cause: Row weights column was not assigned one of the allowed data types.
Action: Choose a row weight column of type NUMBER or FLOAT.
ORA-40123: invalid row weights column string
Cause: Row weights column was the same as the target column.
Action: Choose a new row weights column.
ORA-40181: invalid transformation definition for column string
Cause: Transformation definition has duplicate or NULL columns.
Action: Provide a valid transformation definition specification.
ORA-40182: invalid column reference
Cause: Transformation expression has no column references or more than one
reference or the reference is qualified.
Action: Provide a valid expression.
ORA-40183: invalid stack definition for attribute string
Cause: Stack definition expression or reverse expression has syntax errors or it
does not match the transformation definition.
Action: Provide a valid expression.
ORA-40184: transformation definition does not match the data
Cause: Transformation definition specifies nested transformation for non-nested
data or it removes all of the columns.
Action: Provide a valid data.
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-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 provide the correct column name.
ORA-40203: model string does not exist
Cause: The model did not exist.
Action: Supply a valid model name.
ORA-40204: model string already exists
Cause: A model by the same name exists.
Action: Provide a different, unique name for the model.
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-40206: invalid setting value for setting name string
Cause: The input value for the given setting name was invalid.
22-6 Oracle Database Error Messages
Action: Consult the documentation for the settings table and provide a valid
setting value.
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-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-40209: setting string is invalid for string function
Cause: The specified setting was not supported for the mining function supplied.
Action: Provide appropriate combination of function and algorithm settings.
ORA-40210: invalid score criterion type when cost matrix is specified
Cause: The score criterion type may not be 'PROBABILITY' when a cost matrix is
specified.
Action: Set score criterion type to 'COST' or don't specify a cost matrix.
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-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-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-40214: duplicate setting: string
Cause: Duplicate setting in the settings table.
Action: Remove the duplicate setting from the settings table.
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-40216: feature not supported
Cause: The feature was not supported in the API.
Action: Modify the code to avoid usage of the feature.
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.
ORA-40001 to ORA-40556 22-7
Action: Verify the entries in the priors table.
ORA-40218: Both priors table and weights table are specified
Cause: Both a priors table and a weights table are specified for SVM model build.
Action: Priors table is the old (pre 11g) mechanism for specifying class weights,
and class weights table is the new (and correct) way to specify class weights.
Remove the priors table entry from the settings table (after transferring class
weight settings, if appropriate). Going forward, priors table will be valid only for
NB models. Use class weights for SVM.
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-40220: maximum number of attributes exceeded
Cause: The data had too many attributes.
Action: Reduce the dimensionality of the data.
ORA-40221: maximum target cardinality exceeded
Cause: The target cardinality of the training data was too high.
Action: Reduce the target cardinality.
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-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-40224: transactional input - no matching id for value column string
Cause: The training data is transactional - and a value column is specified without
a matching id specification.
Action: Specify a valid id column name as input
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-40226: model upgrade/downgrade must be performed by SYS
Cause: Upgrade/Downgrade routines are being invoked by a user with
insufficient privilieges.
Action: Run the routines as SYS during migration.
ORA-40227: invalid transformation attribute
Cause: Transformation list provided to CREATE_MODEL has duplicate or NULL
attributes. Case ID or target attribute has attribute_subname that is not NULL.
Attribute provided to ALTER_REVERSE_EXPRESSION does not exist in the
model.
Action: Remove NULLs and duplicates and fix case ID and target attributes or
provide a valid attribute for a given model.
22-8 Oracle Database Error Messages
ORA-40228: scoring cost matrix already exists
Cause: The model already has a scoring cost matrix.
Action: To add a new scoring cost matrix the existing one should be removed
first.
ORA-40229: scoring cost matrix not found
Cause: The model does not have a scoring cost matrix.
Action: To remove a scoring cost matrix the model should have one.
ORA-40230: invalid transformation expression
Cause: Expression has syntax or semantic errors.
Action: Provide a valid expression.
ORA-40231: transactional input incompatible with specified algorithm
Cause: Training data in transactional format is not accepted for model creation
using the specified mining algorithm.
Action: Pivot the data into 2D tabular format, or provide the transactional input
through a nested table column.
ORA-40232: transactional input - incompatible datatype for column string
Cause: The data type of the column in the input training data is not supported.
Action: Cast or change the type of the column to one of CHAR, VARCHAR,
NUMBER or FLOAT
ORA-40233: transactional input - case id should be provided with id string
Cause: The training data is transactional by virtue of presence of a and item id -
but does not have a case id specification.
Action: Specify a valid case id column name as input
ORA-40234: reverse expression incompatible with model cost matrix
Cause: A cost matrix existed for this model with actual and predicted values
which were inconsistent with the values resulting from the specified reverse
transformation.
Action: Either remove the cost matrix table and re-add it with the new actual and
predicted values, or respecify the reverse transformation to be consistent with the
existing cost matrix.
ORA-40251: no support vectors were found
Cause: The input data is non-predictive in nature, or one of the input settings is
incorrect/incompatible with respect to the input data.
Action: Provide additional data or change model setting value.
ORA-40252: no target values were found
Cause: No target values were identified during load.
Action: Validate that the target is correctly spec