Skip Headers
Oracle® Database Error Messages
12c Release 1 (12.1)

E49325-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

22 ORA-40001 to ORA-40556

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.
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
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
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-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.
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.
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.
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 specified.
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-40254: priors cannot be specified for one-class models
Cause: Priors were specified.
Action: Do NOT provide priors for one-class models.
ORA-40255: specified priors or weights table has an incorrect schema
Cause: The priors or class weights table whose name is specified in in the settings does not have the prescribed schema. A priors table should have the schema (target_value, prior_probability) and a class weights table should have the schema (target_value, class_weight)
Action: Modify the schema of the input priors or class weights table to match the ones provided above (also in the documentation).
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-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-40263: no meaningful matrix factorization found
Cause: Input data was not significantly different from 0.
Action: Check your data for problems or add a positive constant to all the numeric attributes.
ORA-40264: number of mining attributes (string) exceeds maximum (string)
Cause: Input data was found to contain a number of mining attributes exeeding the maximum allowed.
Action: Check the input data for categorical fields with high cardinality.
ORA-40271: no statistically significant features were found
Cause: Input data inadequate in volume and/or quality to derive statistically significant predictors for building a data mining model.
Action: Provide a well-prepared training data set.
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-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-40274: the Adaptive Bayes Network algorithm is desupported
Cause: An attempt was made to score an Adaptive Bayes Network model.
Action: Drop the existing model and build a new model using a supported classification algorithm.
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-40282: invalid cost matrix
Cause: Cost matrix specification is invalid.
Action: Provide valid cost matrix specification. Check syntax for data mining functions.
ORA-40283: missing cost matrix
Cause: Cost matrix specification is missing.
Action: Provide valid cost matrix specification. Check syntax for data mining functions.
ORA-40284: model does not exist
Cause: The model entered does not exist.
Action: Check spelling.
ORA-40285: label not in the model
Cause: The user-specified label was not present in the model.
Action: Provide a valid label. The set of valid labels can be retrieved from a classification model by invoking PREDICTION_SET, from a clustering model by invoking CLUSTER_SET, and from a feature extraction model by invoking FEATURE_SET.
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-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-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-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 based on an algorithm that is incompatible with function.
Action: Provide the name of the model suitable for the function.
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-40292: confidence level must be greater than 0 and less than 1
Cause: The specified value for confidence level is out of range.
Action: Specify a value for confidence level in the range 0 < level < 1
ORA-40293: input class is invalid for the specified predictive model
Cause: The specified model is either not a classification model, or does not have the input class label as one of its target values.
Action: Provide the correct target value (class label) or provide the appropriate classification model with the target attribute that has the specified class label as one of its values.
ORA-40301: invalid cost matrix specification
Cause: A valid cost matrix is not specified.
Action: Consult documentation for valid 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-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-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-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 contained one or more columns of DM_NESTED type (DM_NESTED_NUMERICALS or DM_NESTED_CATEGORICALS). These columns are currently not supported by Orthogonal Partitioning Clustering (O-Cluster).
Action: Remove columns of these data types from the input data source.
ORA-40307: nested attribute combined name and value too long
Cause: The data that was presented to the decision tree algorithm was too long. The length is computed from the sum of the length of the nested attribute name and the length of the attribute value.
Action: Reduce the length of the attribute name or reduce the length of the categorical value (perhaps by recoding).
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-40324: All rows contain the same data
Cause: All rows contained the same data and could not be clustered using k-Means with cosine distance metric.
Action: Use Euclidean distance metric.
ORA-40341: access violation on model storage object
Cause: An attempt was made to directly access/modify a schema object that stores model metadata and content.
Action: Perform all mining operations (create,drop,alter, and select using data mining functions) against named model objects. Contact your DBA or Oracle Support if you suspect that an orphaned schema object.
ORA-40342: model was not correctly upgraded
Cause: An attempt was made to use a model, but the model was not correctly upgraded to the current release. This is most likely caused by importing a model from an old release without upgrading it, but could also be caused by a failed database upgrade.
Action: Invoke the SYS.DMP_SYS.UPGRADE_MODELS() procedure.
ORA-40343: invalid version specified in UPGRADE_MODELS
Cause: An invalid version was specified when invoking the UPGRADE_MODELS procedure. Valid values for the version are 10.2.0, 11.0.0, 12.0.0, and NULL.
Action: Specify a valid version for UPGRADE_MODELS.
ORA-40350: One or more models exist that cannot be downgraded
Cause: There are data mining models in the database that were created in a release beyond the selected release for downgrade.
Action: Prior to downgrade, drop data mining models that cannot be downgraded to the selected release.
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-40362: invalid object string.string specified in the statement
Cause: An attempt was made to grant a privilege on an invalid object.
Action: Make sure the dependents of the object are valid before attempting // to grant the privilege on the object.
ORA-40381: Invalid field specification for: string
Cause: The derived field was incorrectly defined.
Action: Make sure the field is correctly defined in the PMML document.
ORA-40382: More than one linear regression equation in the model
Cause: More than one linear regression equation was in the model.
Action: Make sure there is only one linear regression equation in the model.
ORA-40383: No model found in PMML document
Cause: There was no model found in the PMML document.
Action: Make sure the PMML document contains a model section.
ORA-40384: Only one model allowed in PMML document
Cause: More than one model existed in the PMML document.
Action: PMML model import only supports one model per PMML document. Make sure only one model exists in the PMML document.
ORA-40385: Target has more than two categories
Cause: The target contained more than two categories.
Action: PMML model import supports only binary logistic regression. Make sure the target contains no more than two categories.
ORA-40386: NormContinuous must include at least two LinearNorm elements
Cause: NormContinuous included less than two LinearNorm elements.
Action: NormContinuous must include at least two LinearNorm elements. Make sure at least two LinearNorm elements are included.
ORA-40387: Invalid interval for Discretize field: string
Cause: The intervals were incorrect.
Action: Make sure that both margins are not missing.
ORA-40388: Unsupported feature in PMML document: string
Cause: The feature was not supported by PMML model import.
Action: Please make sure to use supported features.
ORA-40389: Unsupported PMML transformation: string
Cause: The transformation was not supported.
Action: Make sure to use supported transformations.
ORA-40390: PMML DerivedField must have a unique name specified: string
Cause: A DerivedField did not reference another defined field.
Action: A DerivedField did not have a unique name specified. Make sure to specify a unique name for each DerivedField.
ORA-40391: PMML DerivedField depends on a undefined field: string
Cause: A DerivedField may only reference other defined fields.
Action: Make sure DerivedFields reference other defined fields.
ORA-40392: PMML regression equation references an undefined field: string
Cause: Regression equation did not reference defined fields.
Action: Regression equation may only reference defined fields. Make sure all fields are defined.
ORA-40401: categorical attributes are not supported by this algorithm
Cause: The build data provided to the CREATE_MODEL routine contained one or more categorical attributes of types CHAR, VARCHAR2, or DM_NESTED_CATEGORICAL. These attributes are currently not supported for the SVD algorithm.
Action: Remove the categorical attributes from the build data.
ORA-40402: cannot output U matrix without a valid case identifier column
Cause: A U matrix was requested, but there was no case identifier column in the build data.
Action: Provide a non-null case identifier column in the build data.
ORA-40403: model does not have any valid features
Cause: All singular values in the SVD model were equal to zero. This can occur if the build data contains only zeros or all build columns have constant values and automatic data preparation is turned on.
Action: Inspect and modify the build data.
ORA-40404: approximate computation cannot be disabled for the build data
Cause: The build data had a very high number of attributes. An SVD model can be built only by enabling approximate computation.
Action: Enable approximate computation.
ORA-40421: missing text policy name
Cause: Text policy name was missing.
Action: Provide a valid text policy name created using CTX_DDL.CREATE_POLICY().
ORA-40422: TEXT attribute types not supported by this algorithm
Cause: The training input to the CREATE_MODEL routine contained one or more attributes of TEXT type. These attributes are currently not supported by Orthogonal Partitioning Clustering (O-Cluster).
Action: Remove attributes of these types from the input data source.
ORA-40441: JSON syntax error
Cause: The provided JavaScript Object Notation (JSON) data had invalid syntax and could not be parsed.
Action: Provide JSON data with the correct syntax.
ORA-40442: JSON path expression syntax error
Cause: The provided JavaScript Object Notation (JSON) path expression had an invalid syntax and could not be parsed.
Action: Provide JSON path expression with the correct syntax.
ORA-40443: unsupported JSON path expression
Cause: The provided JavaScript Object Notation (JSON) path expression contained unsupported features.
Action: Remove unsupported features from JSON path expression.
ORA-40444: JSON processing error
Cause: The requested JavaScript Object Notation (JSON) operation failed.
Action: Make sure the JSON operation is invoked correctly.
ORA-40445: unsupported JSON operation
Cause: The requested JavaScript Object Notation (JSON) operation is not supported.
Action: None
ORA-40446: expecting keyword STREAM
Cause: The JavaScript Object Notation (JSON) operator expected the keyword STREAM.
Action: Add the keyword STREAM to the JSON operator.
ORA-40447: expecting PASSING clause
Cause: The JavaScript Object Notation (JSON) operator expected a PASSING clause.
Action: Add a PASSING caluse to the JSON operator.
ORA-40448: expecting RETURNING clause
Cause: The JavaScript Object Notation (JSON) operator expected a RETURNING clause.
Action: Add a RETURNING clause to the JSON operator.
ORA-40449: invalid data type for return value
Cause: The provided data type for the return value was invalid or unsupported.
Action: Provide a supported return value.
ORA-40450: invalid ON ERROR clause
Cause: The provided ON ERROR clause was invalid.
Action: Provide a valid ON ERROR clause.
ORA-40451: invalid default value provided
Cause: The provided default value was not allowed here.
Action: Provide a valid default value.
ORA-40452: default value not matching type defined in RETURNING clause
Cause: The provided default value did not match the type defined in RETURNING clause.
Action: Make sure that the default value and RETURNING clause are of the same type.
ORA-40453: JSON operator syntax error
Cause: The provided JavaScript Object Notation (JSON) operator had invalid syntax.
Action: Provide JSON operator with correct syntax.
ORA-40454: path expression not a literal
Cause: The provided path expression was not a literal (a constant).
Action: Provide a constant path expression.
ORA-40455: default value not a literal
Cause: The provided default value was not a literal (a constant).
Action: Provide a constant default value.
ORA-40456: JSON_VALUE evaluated to non-scalar value
Cause: The provided JavaScript Object Notation (JSON) path expression selected a non-scalar value.
Action: Correct the JSON path expression or use JSON_QUERY.
ORA-40457: JSON path expression contained an invalid array index
Cause: The provided JavaScript Object Notation (JSON) path expression contained an invalid array index.
Action: Provide array index greater 0. The first element in the array has the index 1.
ORA-40458: JSON_EXISTS used outside predicate
Cause: The operator JSON_EXISTS was used outside a predicate.
Action: Use JSON_EXISTS inside a preciate, for instance by embedding it inside a CASE expression.
ORA-40459: output value too large (actual: string, maximum: string)
Cause: The provided JavaScript Object Notation (JSON) operator generated a result which exceeds the maximum length specified in the RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or use a CLOB/BLOB in the RETURNING clause.
ORA-40460: default value too large
Cause: The provided default value exceed the maximum length specified in the RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or reduce the length of the default value.
ORA-40461: Unsupported character set
Cause: The provided JavaScript Object Notation (JSON) operator does not supported the current database character set.
Action: Chose a different database character set, for instance AL32UTF8, AL16UTF16, or a single byte character set.
ORA-40462: JSON_VALUE evaluated to no value
Cause: The provided JavaScript Object Notation (JSON) path expression did not select a value.
Action: Correct the JSON path expression.
ORA-40463: JSON path expression contained an invalid variable name
Cause: The provided JavaScript Object Notation (JSON) path expression contained a variable name that is not used in the PASSING clause.
Action: Make sure that the variable names in the path expression and PASSING clause match.
ORA-40464: JSON PASSING clause contained duplicate variable names
Cause: The provided JavaScript Object Notation (JSON) PASSING clause contained non-unique variable names.
Action: Rename the variables in the PASSING clause.
ORA-40465: JSON PASSING clause contained too many unnamed parameters
Cause: The provided JavaScript Object Notation (JSON) PASSING clause contained too many unnamed parameters.
Action: Assign names to the parameters provided in the PASSING clause.
ORA-40466: Invalid parameter in IS [NOT] JSON predicate
Cause: The IS [NOT] JSON predicate containes an invalid parameter.
Action: Remove or correct the parameter.
ORA-40467: JSON_TEXTCONTAINS() cannot be evaluated without JavaScript Object Notation (JSON) index
Cause: There was no JSON-enabled context index available.
Action: Create a JSON-enabled context index.
ORA-40468: first input parameter to JSON_TEXTCONTAINS() must be a column
Cause: The first input parameter to JSON_TEXTCONTAINS() was not a column.
Action: Pass a column to the first input parameter to JSON_TEXTCONTAINS().
ORA-40469: JSON path expression in JSON_TEXTCONTAINS() is invalid
Cause: A predicate or array position was used in JavaScript Object Notation(JSON) path expression.
Action: Do not use a predicate or array position in a JSON path expression.
ORA-40470: JSON_VALUE evaluated to multiple values
Cause: The provided JavaScript Object Notation (JSON) path expression selected more than one value.
Action: Correct the JSON path expression or use JSON_QUERY.
ORA-40471: selected value not JSON array or object
Cause: The selected value was not a JavaScript Object Notation (JSON) value. (object or array)
Action: Use CAST AS ARRAY to return this value.
ORA-40472: invalid escape in JSON data
Cause: The provided JavaScript Object Notation (JSON) data had an invalid escape sequence.
Action: Provide JSON data with corrected escape sequence.
ORA-40473: duplicate key names in JSON object
Cause: The provided JavaScript Object Notation (JSON) data had duplicate key names in one object.
Action: Provide JSON data with unique key names in each JSON object.
ORA-40474: invalid UTF-8 byte sequence in JSON data
Cause: The provided JavaScript Object Notation (JSON) data had an invalid UTF-8 byte sequence.
Action: Provide JSON data with corrected UTF-8 byte sequence or escape the characters.
ORA-40475: JSON data nested too many levels
Cause: The provided JavaScript Object Notation (JSON) data had too many levels of nesting.
Action: Provide JSON data with fewer levels of nesting.
ORA-40476: JSON key too long
Cause: The provided JavaScript Object Notation (JSON) data had a key which exceeds the maximum length.
Action: Provide JSON data with shorter key names.
ORA-40477: internal JSON error
Cause: There was an internal error in the JavaScript Object Notation (JSON) processing layer.
Action: None
ORA-40478: output value too large (maximum: string)
Cause: The provided JavaScript Object Notation (JSON) operator generated a result which exceeds the maximum length specified in the RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or use a CLOB or BLOB in the RETURNING clause.
ORA-40479: internal JSON serializer error
Cause: There was an internal error in the JavaScript Object Notation (JSON) serializer).
Action: None
ORA-40480: result cannot be returned without array wrapper
Cause: The JavaScript Object Notation (JSON) path expressions selected a value that can only be returned inside an array.
Action: Add WITH ARRAY WRAPPER to the JSON function.
ORA-40481: ASCII or PRETTY not supported for non-textual return data type
Cause: An attempt was made to pretty print or escape non-ASCII characters for a non-textual output of a JSON operation.
Action: Change return data type to VARCHAR2 or CLOB or remove the PRETTY or ASCII serialization option.
ORA-40482: JSON_TEXTCONTAINS() used outside predicate of WHERE clause
Cause: JSON_TEXTCONTAINS() was used outside of the predicate of a WHERE clause.
Action: Use JSON_TEXTCONTAINS() inside a preciate of a WHERE clause.
ORA-40483: incorrect search string to JSON_TEXTCONTAINS()
Cause: An incorrect search string to JSON_TEXTCONTAINS() was used.
Action: The search string to JSON_TEXTCONTAINS() needs to be a non-zero length compile time constant.
ORA-40484: invalid data type for JSON_TABLE column
Cause: A column in the provided JSON_TABLE had an unsupported data type.
Action: Provide a supported data type.
ORA-40485: keyword PRETTY not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty printed.
Action: Change column semantics to JSON_QUERY or remove the keyword PRETTY.
ORA-40486: array wrapper not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not have an array wrapper.
Action: Change column semantics to JSON_QUERY or remove the array wrapper.
ORA-40487: invalid usage of keyword EXISTS
Cause: A JSON_TABLE column with JSON_EXISTS semantics had invalid parameters.
Action: Remove the invalid keywords.
ORA-40488: invalid ON ERROR clause for column semantics
Cause: An ON ERROR clause was provided that was not valid for the selected column semantics.
Action: Change or remove the ON ERROR clause or change the column semantics.
ORA-40489: keyword ASCII not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty printed.
Action: Change column semantics to JSON_QUERY or remove keyword ASCII.
ORA-40490: COLUMNS clause required
Cause: The provided JSON_TABLE row source requires a COLUMNS clause.
Action: Provide a COLUMNS clause.
ORA-40491: invalid input data type for JSON_TABLE
Cause: The provided input to JSON_TABLE has an unsupported data type.
Action: Provide a (N)VARCHAR2, (N)CLOB, RAW, BLOB or BFILE input.
ORA-40492: invalid column definition in JSON_TABLE
Cause: A column definition inside JSON_TABLE was invalid.
Action: Correct the column definition.
ORA-40493: invalid option or parameter in JSON_TABLE
Cause: The provided JSON_TABLE definition contained one or more invalid options or parameters.
Action: Correct the JSON_TABLE definition.
ORA-40494: error during execution of JSON_TABLE
Cause: The provided JSON_TABLE definition could not be evaluated.
Action: Correct the JSON_TABLE definition.
ORA-40495: internal error in JSON_TABLE
Cause: The provided JSON_TABLE definition could not be evaluated.
Action: Contact Oracle Support Services.
ORA-40497: only one ordinality column permitted
Cause: The provided JSON_TABLE definition contained more than one ordinality column.
Action: Remove the ordinality column or columns from the JSON_TABLE definition.
ORA-40498: binary format requested for non-binary data type
Cause: The provided JSON format was binary but the input data type was not binary.
Action: Either change the format clause or use an input of binary data type.
ORA-40499: no format defined for binary data type
Cause: The provided JSON input was of binary type but a format was not defined.
Action: Define a format for binary input.
ORA-40501: cannot open an encrypted log file
Cause: An attempt was made to open a log file that has been encrypted for storage and management by the Oracle Availability Machine. Only the processes involved in shipping such a log to or from the Oracle Availability Machine can open the log.
Action: Allow the Oracle Availability Machine to manage the log file.
ORA-40551: internal BSON/JSON conversion error [string]
Cause: BSON/JSON conversion failed with internal error.
Action: Contact Oracle Support Services.
ORA-40552: invalid data type
Cause: The BSON/JSON converter was invoked with an invalid data type.
Action: Ensure that both the input and output is of data type BLOB.
ORA-40553: path expression with predicates not supported in this operation
Cause: A path expression with predicates was specified in a JavaScript Object Notation (JSON) operation that does not support predicates.
Action: Only JSON_EXISTS supports predicates.
ORA-40554: invalid input data type in PASSING clause
Cause: The specified PASSING clause had an unsupported data type.
Action: Use a supported data type in the PASSING clause.
ORA-40555: incorrect PASSING clause
Cause: The specified PASSING clause was invalid.
Action: Specify a valid passing clause.
ORA-40556: unsupported chaining of JSON_TABLE
Cause: The specified JSON_TABLES were chained.
Action: Use the NESTED PATH syntax for JSON_TABLE.