Cause: The input parameter in question has a value of zero or less.

Cause: The input wordsize is less than the prescribed limit for the BLAST Match or Align algorithm.

Cause: The input wordsize has a value out of the prescribed range.

Cause: The input value provided for penalty is zero or greater.

Cause: The training table does not contain the specified column

Cause: The row diagnostics were enabled, but without a corresponding case or row identifier column in the build data.

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.

Cause: Unable to find solution because the predictor covariance matrix was singular.

Cause: The provided reference class name was not found in the build data.

Cause: The provided reference class name did not correspond to any of the entries in the weights table.

Cause: Generalized Linear Models only support binary classification.

Cause: Unable to find solution because the predictor build data were not properly scaled.

Cause: A diagnostics table name matching an existing table was specified.

Cause: Unable to find solution because the predictor covariance matrix was singular for the forced-in features.

Cause: Too many forced-in features were specified or the features were high cardinality attributes, or both.

Cause: Unable to find solution because the predictor covariance matrix was singular for the selected features.

Cause: This was caused by one or more of the following: - Data rows were too few in number. - Mining attributes were too many. - Ridge regression was on.

Cause: The setting GLMS_FTR_SELECTION which was disabled was incompatible with the specified FORCE_IN transformation.

Cause: The time series had fewer rows than the number of parameters in the model.

Cause: The time series contained numbers greater than 1 million.

Cause: The time series was not strictly positive.

Cause: The time series was constant.

Cause: The time series had too few rows to obtain an initial trend estimate.

Cause: A valid value was not specified for the EXSM_INTERVAL setting. If the case ID column type is datetime, a valid EXSM_INTERVAL setting must be provided.

Cause: The case ID column was required to provide time labels, but a valid case ID column was not provided.

Cause: There was no consecutive one year period containing all existing seasons.

Cause: An internal system error occured during a data mining operation.

Cause: The input parameter is either null or invalid for the given operation.

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.

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.

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

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

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

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

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

Cause: Operation would result in duplicate model table types which is not supported.

Cause: Could not build a model when only special or empty columns were present. Special columns include target, row weight, and case ID columns.

Cause: Fewer than two valid data rows were found in the build data.

Cause: Less than two distinct target values were found in the build data.

Cause: The entries in the weights table did not correspond to the target values in the build data.

Cause: The weights table did not have the required schema.

Cause: The weights table had NULL entries.

Cause: The weights table had repeated target values.

Cause: The weights table had less that 2 target values.

Cause: delete_row missing value treatment is not supported for nested columns.

Cause: Negative or zero weight values were found in the weights table.

Cause: The force option was specified, but the model is in a different schema.

Cause: Row weights column was not assigned one of the allowed data types.

Cause: Row weights column was the same as the target column.

Cause: A partitioned model was referenced in the query, but the partition key column was not found in the input.

Cause: The partition entered did not exist.

Cause: The model specified was not a partitioned model.

Cause: The number of partition keys specified did not match the model.

Cause: A partition already existed for the partition keys specified.

Cause: The partition name specified was not unique for this model.

Cause: The partition name specified was not valid.

Cause: The partition column did not have a supported data type.

Cause: A model partition was not specified. This function requires the specification of a model partition.

Cause: The partition columns in the operation did not match those in the existing model.

Cause: The specified partitioned model contained a single partition. An empty model is not supported.

Cause: The maximum number of 16 partition columns was exceeded.

Cause: The maximum number of partitions per model was exceeded.

Cause: There were no partitions found in the training data.

Cause: The training data did not allow the building of a meaningful model.

Cause: All training data rows had zero norm.

Cause: The partition key column values did not match for one or more scored rows.

Cause: The required R function was not specified.

Cause: The R SCORE, WEIGHT, or DETAILS function did not return the result in a data.frame containing either R numeric values for SCORE and WEIGHT function or R numeric or string values for DETAILS function.

Cause: The R SCORE or WEIGHT function returned a different number of rows than that of the input data.frame.

Cause: The specified attribute was not a scalar numeric value or a single string.

Cause: The R parameter was not a scalar numeric value or a single string.

Cause: The specified script was not found in the R script repository.

Cause: The R DETAILS function output format specfication did not use numeric or string value, or did not match the actual output from the R DETAILS function.

Cause: The R_HOME was not set to the location where R was installed.

Cause: The R memory control settings did not use positive values.

Cause: The expected setting was not on the model setting table.

Cause: The generated R model did not have the required attribute.

Cause: Conflict attributes were specified for the R model object.

Cause: The R regression model prediction did not return an R data.frame with a single column of numerics for predicted value, or two additional columns containing the standard error of model fit and the degree of freedom were missing from the output when SQL function prediction_bounds was invoked.

Cause: The R classification, clustering, or feature extraction model SCORE function did not return the prediction for each class, cluster, or feature respectively in the output R data.frame.

Cause: The R model WEIGHT function did not return the contribution weight for each attribute of the data.

Cause: The R classification model prediction did not have correct target class names assigned as the column names for the return data.frame.

Cause: The input data.frame column names contained special characters that are not supported by R.

Cause: The specified input table contained no valid data to build R model.

Cause: The R function execution failed.

Cause: An attempt was made to drop models built on this algorithm.

Cause: An attempt was made to register an algorithm that did not follow the predefined JavaScript Object Notation (JSON) schema.

Cause: An attempt was made to register an algorithm with the same name, mining function and type combination.

Cause: The specified algorithm did not exist.

Cause: An attempt was made to use both registered algorithm name and R scripts definition.

Cause: The privileges to register or drop an algorithm were not granted.

Cause: Transformation definition has duplicate or NULL columns.

Cause: Transformation expression has no column references or more than one reference or the reference is qualified.

Cause: Stack definition expression or reverse expression has syntax errors or it does not match the transformation definition.

Cause: Transformation definition specifies nested transformation for non-nested data or it removes all of the columns.

Cause: The input parameter was either null or invalid.

Cause: The column was missing from the table.

Cause: The model did not exist.

Cause: A model by the same name exists.

Cause: The input setting name was invalid.

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

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

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

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

Cause: The score criterion type may not be 'PROBABILITY' when a cost matrix is specified.

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

Cause: Target data type was invalid.

Cause: The settings values were not compatible.

Cause: Duplicate setting in the settings table.

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

Cause: The feature was not supported in the API.

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

Cause: Both a priors table and a weights table are specified for SVM model build.

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

Cause: The data had too many attributes.

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

Cause: The model export job failed.

Cause: The model import job failed.

Cause: The training data is transactional. A valid ID column must be specified.

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

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

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.

Cause: The model already has a scoring cost matrix.

Cause: The model does not have a scoring cost matrix.

Cause: Expression has syntax or semantic errors.

Cause: Training data in transactional format is not accepted for model creation using the specified mining algorithm.

Cause: The data type of the column in the input training data is not supported.

Cause: The training data is transactional by virtue of presence of a and item id - but does not have a case id specification.

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.

Cause: The setting ASSO_AGGREGATES was not valid.

Cause: The setting ASSO_AGGREGATES specified too many aggregates.

Cause: The same value occurred more than once in the case ID column of the training table.

Cause: The shared library containing platform-optimized linear algebra routines was not loaded.

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

Cause: No target values were identified during load.

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

Cause: Priors or weights were specified.

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)

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

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.

Cause: Input data was not significantly different from 0.

Cause: Input data was found to contain a number of mining attributes exeeding the maximum allowed.

Cause: Input data inadequate in volume and/or quality to derive statistically significant predictors for building a data mining model.

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

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

Cause: An attempt was made to score an Adaptive Bayes Network model.

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

Cause: Cost matrix specification is invalid.

Cause: Cost matrix specification is missing.

Cause: The model entered does not exist.

Cause: The user-specified label was not present in the model.

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

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

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.

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.

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

Cause: The specified value for confidence level is out of range.

Cause: The specified model is either not a classification model, or does not have the input class label as one of its target values.

Cause: A valid cost matrix is not specified.

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

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

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

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

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).

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.

Cause: The setting for RFOR_MTRY was either 0 or >= number of attributes. The default behavior in this scenario is to use all of the attributes for the model build.

Cause: The sample did not fit into available memory.

Cause: Input bin number has zero or negative values.

Cause: Bin number is too large.

Cause: Exceeded maximum number of distinct values allowed in an attribute.

Cause: All rows contained the same data and could not be clustered using k-Means with cosine distance metric.

Cause: The maximum number of clusters was exceeded.

Cause: All mining attributes were filtered out.

Cause: An attempt was made to directly access/modify a schema object that stores model metadata and content.

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.

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.

Cause: There are data mining models in the database that were created in a release beyond the selected release for downgrade.

Cause: An attempt was made to grant or revoke an invalid privilege on a mining model.

Cause: An attempt was made to grant a privilege on an invalid object.

Cause: An attempt was made to grant SYSOPER or SYSDBA privileges to SYS user. These administrative privileges cannot be granted to SYS, since SYS always has SYSOPER and SYSDBA privileges.

Cause: This is an internal error message.

Cause: An attempt was made to lock the SYS user account by executing the DDL statement ALTER USER SYS ACCOUNT LOCK while the password file was created in LEGACY or 12 format.

Cause: An attempt was made to grant administrative privilege to a user who has been created with NONE as its authentication type. Such grants are not allowed.

Cause: An attempt was made to alter an administrative user to have no authentication type.

Cause: The derived field was incorrectly defined.

Cause: More than one linear regression equation was in the model.

Cause: There was no model found in the PMML document.

Cause: More than one model existed in the PMML document.

Cause: The target contained more than two categories.

Cause: NormContinuous included less than two LinearNorm elements.

Cause: The intervals were incorrect.

Cause: The feature was not supported by Predictive Model Markup Language (PMML) model import.

Cause: The transformation was not supported.

Cause: "The Predictive Model Markup Language (PMML) DerivedField did not reference another defined field and did not have a unique name."

Cause: A DerivedField referenced an undefined field.

Cause: The Predictive Model Markup Language (PMML) Regression equation did not reference defined fields. PMML Regression equation may only reference defined fields.

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.

Cause: A U matrix was requested, but there was no case identifier column in the build data.

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.

Cause: The build data had a very high number of attributes. An SVD model can be built only by enabling approximate computation.

Cause: The build data had a very high number of attributes. A Singular Value Decomposition (SVD) model cannot be built using full SVD solvers.

Cause: Text policy name was missing.

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).

Cause: Extraction of tokens from an attribute of TEXT type failed.

Cause: The provided JavaScript Object Notation (JSON) data had invalid syntax and could not be parsed.

Cause: The provided JavaScript Object Notation (JSON) path expression had an invalid syntax and could not be parsed.

Cause: The provided JavaScript Object Notation (JSON) path expression contained unsupported features.

Cause: The requested JavaScript Object Notation (JSON) operation failed.

Cause: The requested JavaScript Object Notation (JSON) operation is not supported.

Cause: The JavaScript Object Notation (JSON) operator expected the keyword STREAM.

Cause: The JavaScript Object Notation (JSON) operator expected a PASSING clause.

Cause: The JavaScript Object Notation (JSON) operator expected a RETURNING clause.

Cause: The provided data type for the return value was invalid or unsupported.

Cause: The provided ON ERROR clause was invalid.

Cause: The provided default value was not allowed here.

Cause: The provided default value did not match the type defined in the RETURNING clause.

Cause: The provided JavaScript Object Notation (JSON) operator had invalid syntax.

Cause: The provided path expression was not a literal (a constant).

Cause: The provided default value was not a literal (a constant).

Cause: The provided JavaScript Object Notation (JSON) path expression selected a non-scalar value.

Cause: The provided JavaScript Object Notation (JSON) path expression contained an invalid array index.

Cause: The operator JSON_EXISTS was used outside of a predicate.

Cause: The provided JavaScript Object Notation (JSON) operator generated a result which exceeds the maximum length specified in the RETURN clause.

Cause: The provided default value exceed the maximum length specified in the RETURN clause.

Cause: The provided JavaScript Object Notation (JSON) operator does not supported the current database character set.

Cause: The provided JavaScript Object Notation (JSON) path expression did not select a value.

Cause: The provided JavaScript Object Notation (JSON) path expression contained a variable name that was not used in the PASSING clause.

Cause: The provided JavaScript Object Notation (JSON) PASSING clause contained non-unique variable names.

Cause: The provided JavaScript Object Notation (JSON) PASSING clause contained too many unnamed parameters.

Cause: The IS [NOT] JSON predicate containes an invalid parameter.

Cause: There was no JavaScript Object Notation (JSON)-enabled context index available.

Cause: The first input parameter to JSON_TEXTCONTAINS() was not a column.

Cause: A predicate or array position was used in JavaScript Object Notation (JSON) path expression, or the length of a JSON field name in the path expression exceeded the JSON search index token length limit.

Cause: The provided JavaScript Object Notation (JSON) path expression selected more than one value.

Cause: The selected value was not a JavaScript Object Notation (JSON) value. (object or array)

Cause: The provided JavaScript Object Notation (JSON) data had an invalid escape sequence.

Cause: The provided JavaScript Object Notation (JSON) data had duplicate key names in one object.

Cause: The provided JavaScript Object Notation (JSON) data had an invalid UTF-8 byte sequence.

Cause: The provided JavaScript Object Notation (JSON) data had too many levels of nesting.

Cause: The provided JavaScript Object Notation (JSON) data had a key which exceeds the maximum length.

Cause: There was an internal error in the JavaScript Object Notation (JSON) processing layer.

Cause: The provided JavaScript Object Notation (JSON) operator generated a result which exceeds the maximum length specified in the RETURN clause.

Cause: There was an internal error in the JavaScript Object Notation (JSON) serializer).

Cause: The JavaScript Object Notation (JSON) path expressions selected a value that can only be returned inside an array.

Cause: An attempt was made to pretty print or escape non-ASCII characters for a non-textual output of a JavaScript Object Notation (JSON) operation.

Cause: JSON_TEXTCONTAINS() was used outside of the predicate of a WHERE clause.

Cause: An incorrect search string to JSON_TEXTCONTAINS() was used.

Cause: A column in the provided JSON_TABLE had an unsupported data type.

Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty printed.

Cause: A JSON_TABLE column with JSON_VALUE semantics could not have an array wrapper.

Cause: A JSON_TABLE column with JSON_EXISTS semantics had invalid parameters.

Cause: An ON ERROR clause was provided that was not valid for the selected column semantics.

Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty printed.

Cause: The provided JSON_TABLE row source requires a COLUMNS clause.

Cause: The provided input to JSON_TABLE has an unsupported data type.

Cause: A column definition inside JSON_TABLE was invalid.

Cause: The provided JSON_TABLE definition contained one or more invalid options or parameters.

Cause: The provided JSON_TABLE definition could not be evaluated.

Cause: The provided JSON_TABLE definition could not be evaluated.

Cause: The number of rows in a JSON_OBJECTAGG aggregation group exceeded the maximum number of keys for a JSON Object.

Cause: The provided JSON_TABLE definition contained more than one ordinality column.

Cause: The provided JSON format was binary but the input data type was not binary.

Cause: The provided JavaScript Object Notation (JSON) input was of binary type but a format was not defined.

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.

Cause: An attempt at media recovery found that the data file already existed before the last CREATE CONTROLFILE statement was executed. The information needed for doing the media recovery was lost with the control file that existed when the data file was added to the database.

Cause: An attempt was made on the physical standby database to access the tablespace that was being dropped by Redo Apply. Note that the target tablespace was dropped on the primary database and the physical standby database was applying the redo that was generated at the primary database for the target tablespace drop.

Cause: A corrupt data file header was encountered during a checkpoint.

Cause: Cursor compilation failed. Check the alert log for more details.

Cause: An attempt was made to rename a file for which renaming is not supported.

Cause: The data transfer cache was sent and rejected blocks for a file that was not accessible to the recovery. Either the file had not yet been added by the recovery or the file was offline.

Cause: BSON/JSON conversion failed with internal error.

Cause: The BSON/JSON converter was invoked with an invalid data type.

Cause: A path expression with predicates was specified in a JavaScript Object Notation (JSON) operation that does not support predicates.

Cause: The specified PASSING clause had an unsupported data type.

Cause: The specified PASSING clause was invalid.

Cause: The specified JSON_TABLES were chained.

Cause: An attempt was made to update a JavaScript Object Notation (JSON) value.

Cause: DBMS_SODA_ADMIN package was used when the database was operating at a compatible setting lower than 12.0.0.0.0.

Cause: There were JavaScript Object Notation (JSON) objects in the database that were created in a release beyond the selected release for downgrade.

Cause: The JSON_TABLE expression contained two or more nested path expressions that (partially or fully) selected the same fields.

Cause: The JSON_TABLE expression contained a nested path clause with an invalid path expression.

Cause: The selected value could not be converted to a SDO_GEOMETRY object.

Cause: The error handler specified a default value and the returned data type was an object type. These cannot be combined.

Cause: The provided specification was invalid.

Cause: The JavaScript Object Notation (JSON) path expression did not select a value.

Cause: The JavaScript Object Notation (JSON) path expression selected a data type value different than the requested data type.

Cause: The JavaScript Object Notation (JSON) patch operation failed.

Cause: An attempt to modify a JavaScript Object Notation (JSON) structure failed because the structure cannot be modified.

Cause: An attempt was made to execute an unimplemented JavaScript Object Notation (JSON) feature.

Cause: A conversion between a JavaScript Object Notation (JSON) value and another type failed.

Cause: A key with the specified name was not found in the JavaScript Object Notation (JSON) data.

Cause: An attempt was made to access an item inside a JavaScript Object Notation (JSON) array with a position that is either out of bounds or invalid.

Cause: An attempt was made to use a PL/SQL JavaScript Object Notation (JSON) object type in an invalid context.

Cause: An attempt was made to use a JavaScript Object Notation (JSON) operation on a column which has a redaction policy.

Cause: An attempt was made to bind a non-runtime constant to a bind variable in SQL/JSON path.

Cause: The provided key name was not valid.

Cause: The provided array position was not valid or non-existant.

Cause: Either t.* or * was used in a context where it is not allowed.

Cause: The package was used with a database that was operating at a compatible setting lower than expected.

Cause: A data guide-enabled context index for the specified column in the specified table was not found.

Cause: The view name or table name or JSON column name was null.

Cause: The given table did not have a JavaScript Object Notation (JSON) column with the given name.

Cause: The specified frequency was invalid.

Cause: A internal error occurred.

Cause: The specified JavaScript Object Notation (JSON) type was invalid.

Cause: The specified estimate percentage was invalid.

Cause: The specified path was not found.

Cause: The specified format was invalid.

Cause: No data has been inserted to the json column.

Cause: An attempt was made to create virtual columns using an annotated Javascript Object Notation (JSON) data guide with the name of a column that already exists.

Cause: An attempt was made to create a view using an annotated Javascript Object Notation (JSON) data guide with the name of a column that already exists.

Cause: The specified data guide was invalid.

Cause: The name input given to the Javascript Object Notation (JSON) generation function was null.

Cause: An error occurred when evaluating the JavaScript Object Notation (JSON) operator.

Cause: The specified JavaScript Object Notation (JSON) path expression had invalid syntax and could not be parsed.

Cause: The specified JavaScript Object Notation (JSON) path expression contained an invalid array index.

Cause: IS JSON check constraint could not be dropped when there was a JSON search index created on the column.

Cause: The operator JSON_EQUAL was used outside of a predicate.

Cause: The input JavaScript Object Notation (JSON) data was missing data to match all of the attributes in the specified object type.

Cause: The input JavaScript Object Notation (JSON) data had extra fields that did not match any attribute in the specified object type.

Cause: The input JavaScript Object Notation (JSON) data had fields that nominally matched an attribute in the specified object type, but had an incompatible data type.

Cause: The maximum size permitted for a JavaScript Object Notation (JSON) data type object was exceeded.

Cause: The length of all the key names combined exceeded the maximum length permitted for a JavaScript Object Notation (JSON) object.

Cause: An invalid collection create mode was specified.

Cause: Creating a collection backed by view or package in NEW mode was not allowed.

Cause: The table intended to back the collection did not exist.

Cause: The columns of mapped table backing the collection did not match the collection metadata.

Cause: The view intended to back the collection did not exist.

Cause: The table or the view underlying the collection could not be dropped. There could be uncommitted writes to the collection.

Cause: The columns of mapped view backing the collection did not match the collection metadata.

Cause: Projection specification was not expressed in valid JSON.

Cause: Patch specification was not expressed in valid JSON.

Cause: The specified versioning method was not valid.

Cause: The last-modified column index was specified without setting the last-modified column name.

Cause: The specified key column length value was less than 0.

Cause: The specified key column length for a GUID or UUID character type key value was less than 32 bytes.

Cause: The specified key assignment method was not valid.

Cause: The key assignment method 'SEQUENCE' was specified, but the key column sequence name was not set.

Cause: The specified content column type was not valid.

Cause: The specified content column maximum length value was less than 0.

Cause: The specified content column validation mode was not valid.

Cause: The specified content column compress setting was not valid.

Cause: The specified content column LOB cache setting was not valid.

Cause: The specified content column LOB encrypt setting was not valid.

Cause: The content column type was set to a type other than Binary Large Object (BLOB), and the media type column was requested.

Cause: The specified INITIAL storage clause parameter value was not valid.

Cause: The specified PCTINCREASE storage clause parameter value was not valid.

Cause: The key column sequence name was specified, but the key column assignment method was not 'SEQUENCE'.

Cause: SecureFile LOB settings were specified, but the content column was not of LOB type.

Cause: A non-zero content column maximum length was specified, but the content column was of a LOB type.

Cause: Versioning method other than 'NONE' was specified, but the version column name was not specified.

Cause: A key column maximum length value greater than 255 bytes was specified.

Cause: A key column type that does not support maximum length was specified.

Cause: The specified key column type was not valid.

Cause: The specified read-only setting was not valid.

Cause: The spatial data type MDSYS.SDO_GEOMETRY could not be found.

Cause: An input parameter to the JavaScript Object Notation (JSON) generation function had a data type that is not supported.

Cause: The PASSING clause was not specified for the bind variables in the query.

Cause: The JavaScript Object Notation (JSON) path expression contained a variable name that had no corresponding value in the external PASSING clause.

Cause: The expression provided in the PASSING clause had no name.

Cause: An attempt was made to perform the operation without a name.

Cause: An attempt was made to use an invalid data type.

Cause: An attempt was made to instantiate a document with a null content.

Cause: An attempt was made to perform an operation with a null key.

Cause: An attempt was made to perform an operation with a null document.

Cause: An attempt was made to modify a read-only collection.

Cause: An attempt was made to add an IS JSON check constraint to a column that already had an IS JSON check constraint.

Cause: An attempt was made to use a client-assigned key for this collection.

Cause: An internal error was received during a JSON operation.

Cause: An operation in the patch specification attempted to remove the top-most container (object or array) from the JSON_ELEMENT_T type.

Cause: The collection metadata which was passed was too long.

Cause: Creation of the collection failed because there was an existing collection with same name but different metadata.

Cause: Existing collection with the same name was encountered, but dropped from another process before its metadata could be checked.

Cause: Collection was not found.

Cause: Key column max length specified in the supplied metadata exceeded maximum allowed length of 255 bytes.

Cause: Supplied argument was NULL.

Cause: Length of the supplied metadata value exceeded allowed limit.

Cause: JSON supplied for the metadata descriptor was not valid.

Cause: The Query-By-Example (QBE) filter specification was invalid.

Cause: There was an internal error in the Simple Oracle Document Access (SODA) processing layer.

Cause: The number of keys exceeded allowed limit.

Cause: The large object (LOB) content that was fetched exceeded the maximum supported length

Cause: A double-quoted identifier used a path expression that was invalid.

Cause: An attempt was made to use OCI_SODA_AS_STORED on a collection whose content column type is not BLOB.

Cause: An attempt was made to use an invalid combination of flags.

Cause: The specified setting was not valid.

Cause: An attempt was made to return a list of keys names for a JSON object that had more than 32767 keys.

Cause: UTF-32 encoded content was specified for a document of type "applicaton/json".

Cause: An attempt was made to write a document with media type other than 'application/json' to a JSON-only collection.

Cause: Invalid value was supplied as CREATE_MODE parameter of CREATE_COLLECTION function.

Cause: An attempt was made to convert the date or time stamp string value that did not conform to ISO 8601 format.

Cause: An attempt was made to set a null value for skip.

Cause: An attempt was made to set a null value for limit.

Cause: An attempt was made to use a cursor that has already been closed.

Cause: An attempt was made to set a null value for version.

Cause: An attempt was made to set a null value for filter.

Cause: An attempt was made use QBE on a heterogeneous collection.

Cause: An attempt was made to use version in the operation on a collection with no version column.

Cause: An invalid index property type was specified.

Cause: An invalid value for the index property 'dataguide' was specified.

Cause: An invalid value for the index property 'search_on' was specified.

Cause: An invalid value for the index property 'order' was specified.

Cause: A mandatory index property was missing.

Cause: The row importance was enabled, but without a corresponding case or row identifier column in the build data.

Cause: Incompatible index field properties were specified.

Cause: An index property was specified without specifying the 'fields' property.

Cause: Index properties 'lax' and 'scalarRequired' were both specified.

Cause: An invalid data type property was used.

Cause: Index property 'maxLength' was specified with a non-string data type.

Cause: An attempt was made to create a text index on a heterogeneous collection.

Cause: An attempt was made to create a functional index on a heterogeneous collection.

Cause: An attempt was made to create a geospatial index on a heterogeneous collection.

Cause: An invalid index property was specified.

Cause: An attempt was made to create a text index on a collection with a key column of NVARCHAR2 data type.

Cause: An attempt was made to create a text index on a collection with a content column of NVARCHAR2 or NCLOB data type.

Cause: An attempt was made to create a text index on a collection with an encrypted content column.

Cause: An attempt was made to specify a null index specification.

Cause: An attempt was made to use array steps in fields path.

Cause: An attempt was made to specify a null value for the field's path in the index specification.

Cause: An attempt was made to specify an invalid path in the index specification.

Cause: Number of paths with string data type exceeds the maximum permissible limit of 16.

Cause: A dot separator was missing in the path expression.

Cause: A quote that was not closed was detected at the end of the path.

Cause: An attempt was made to use a path containing invalid charcters in the escape string.

Cause: An attempt was made to use an invalid quoted step in the path.

Cause: An attempt was made to use an incomplete escape sequence in the path.

Cause: An attempt was made to create an index with the same name as another index in the schema.

Cause: An attempt was made to replace a document without setting the key attribute.

Cause: An attempt was made to use an invalid data type in the RETURNING clause.

Cause: QBE filter was not expressed in valid JSON.

Cause: partitionColumn.name was specified, but partitionColumn.path was missing.

Cause: One or a combination of partitionColumn.path, partitionColumn.maxLength, or partitionColumn.sqlType was specified, but partitionColumn.name was missing.

Cause: The specified partition column type was not valid.

Cause: An invalid combination of content column settings was specified.

Cause: An invalid combination of heterogeneous collection settings was specified.

Cause: An invalid JSON format was specified for the content column.

Cause: The specified partition column length value was less than 0.

Cause: Partition column max length specified in the supplied metadata exceeded the maximum allowed length.

Cause: A partition column type that does not support maximum length was specified.

Cause: keyColumn.path was not set with the specified EXTRACT or INSERT key assignment method.

Cause: The key value was not of a valid type.

Cause: An attempt was made to use SKIP and LIMIT attributes in a count operation.

Cause: An index property was specified without specifying the fields or spatial properties.

Cause: The specified sort condition included a LOB column.

Cause: The document flags were not the same in all the input documents supplied to the insert operation.

Cause: The supplied input document array length was less than or equal to 0.

Cause: The current user was not the owner of the index. Only the owner of the index can perform the operation.

Cause: Collection name was null for the operation.

Cause: Index name was null for the operation.

Cause: The specified path contained a descendant step.

Cause: A dot (.) was used as the first or last character of the path.

Cause: Special characters such as $, @ cannot be used as a path step by itself unless backquoted.

Cause: The specified path contained a wildcard step.

Cause: Index with the specified name did not exist on the collection.

Cause: An attempt was made to use OCI_SODA_AS_STORED on a Binary Large Object (BLOB) collection whose content column format was not textual JavaScript Object Notation (JSON).

Cause: An attempt was made to work with a value in JSON_TRANSFORM that was missing.

Cause: An attempt was made to work with a value in JSON_TRANSFORM that already existed.

Cause: An option for the ON EXISTING clause was provided thatwas not legal for the given JSON_TRANSFORM operation.

Cause: An option for the ON MISSING clause was provided that was not legal for the given JSON_TRANSFORM operation.

Cause: An operation was performed that raised this internal error.

Cause: A RENAME operation was attempted to rename a field to a name that already existed in the same Javascript Object Notation (JSON) object.

Cause: A RENAME operation attempted to rename a field that did not exist.

Cause: An attempt was made to execute a JSON_TRANSFORM array operation on a value that was not an array.

Cause: An attempt was made to remove the topmost object, array or scalar value in the JavaScript Object Notation (JSON) data.

Cause: An attempt was made to use the JavaScript Object Notation (JSON) array subscript 'last' with an operator that does not support 'last'.

Cause: An attempt was made to truncate a collection that was not table based.

Cause: Encoding of JSON content in all input documents was not the same.

Cause: An attempt was made to use unsupported collection metadata value.

Cause: An attempt was made to create a collection not backed by a table.

Cause: An attempt was made to set a null value for system change number (SCN).

Cause: An attempt was made to set a null value for the timestamp value.

Cause: An attempt was made to use system change number (SCN) and timestamp attributes in an 'as of' operation that was not SELECT or COUNT.

Cause: An attempt was made to use the TRUNCATE keyword with a non-textual data type in the RETURNING clause.

Cause: The provided JavaScript Object Notation (JSON) data had invalid syntax and could not be parsed.

Cause: The operation on the OCIJson descriptor resulted in an underflow error.

Cause: The operation on the OCIJson descriptor resulted in an error due to invalid input.

Cause: The provided binary JavaScript Object Notation (JSON) data was invalid.

Cause: An error occurred while reading from the input stream due to incorrect initialization.

Cause: An error occurred while writing to the output stream due to incorrect initialization.

Cause: The provided JavaScript Object Notation (JSON) path expression selected a non-Boolean value.

Cause: The specified input to JSON_TRANSFORM has an unsupported data type.

Cause: An attempt was made to insert a value into a JSON object or array using a JavaScript Object Notation (JSON) path expression that can potentially select multiple positions inside the same array or multiple keys in the same object.

Cause: An attempt was made to invoke JSON_TRANSFORM with an unsupported operation or parameter.

Cause: The specified input to JSON_TRANSFORM had a SQL null value.

Cause: An invalid JavaScript Object Notation (JSON) descriptor was detected.

Cause: The operation processed a NULL input.

Cause: An attempt was made to perform a write operation on a JavaScript Object Notation (JSON) descriptor passed as an IN argument to a C callout.

Cause: An attempt was made to perform a comparison against a JavaScript Object Notation (JSON) type value.

Cause: An error occurred during conversion of OCIJson descriptor to textual JSON.

Cause: An attempt was made to use the Boolean number conversion with a data type that was not NUMBER.

Cause: An attempt was made to convert a Boolean value that was selected by a JavaScript Object Notation (JSON path) expression having a number() or numberOnly() function to a number.

Cause: An attempt was made to create a JSON_VALUE functional index with predicates in the path expression.

Cause: An attempt was made to specify a null metadata descriptor.

Cause: An invalid collection create mode was specified.