Oracle Database Errors or Warnings from Error ORA-40305 to ORA-41003

SQLServerF1

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-40306: dm_nested types not supported by this algorithm
Cause: The training input to the CREATE_MODEL routine contains one or more columns of dm_nested type (DM_NESTED_NUMERICALS and/or DM_NESTED_CATEGORICALS). These columns are currently not supported for Decision Tree, O-Cluster, and Adaptive Bayes Network algorithms.
Action: Remove columns of these data types from the input data source.
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-40322: bin number too large
Cause: Bin number is too large.
Action: Reprocess build data by choosing smaller bin numbers.
ORA-40323: Attribute string has too many distinct values (string)
Cause: Exceeded maximum number of distinct values allowed in an attribute.
Action: Bin numerical data with fewer than 1024 bins or recode categorical data with fewer than 1024 unique values.
ORA-40350: 11g model existed.
Cause: There are 11g data mining models existed in the database.
Action: Drop 11g data mining models prior to downgrade to 10g.

ORA-40361: only SELECT and ALTER are valid for mining models
Cause: An attempt was made to grant or revoke an invalid privilege on a mining model.
Action: Do not attempt to grant or revoke any privilege besides SELECT or ALTER on mining models.
ORA-41001: session id list not specified
Cause: An attempt to migrate was made, which failed because the session id list specified was null.
Action: Check the session id list, and try again with a valid value.
ORA-41002: destination instance not specified
Cause: An attempt to migrate was made, which failed because the destination instance specified was null.
Action: Check the destination instance , and try again with a valid value.
ORA-41003: client id not specified
Cause: An attempt to migrate was made, which failed because the client id specified was null.
Action: Check the client id, and try again with a valid value.

Above are list of Oracle Database Errors or Warnings from Error ORA-40305 to ORA-41003 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *