ORA-40001 to ORA-40701

86 ORA-40001 to ORA-40701

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: Cause: The row diagnostics were enabled, 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.
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: too many forced-in features (maximum allowable 1000): Cause: Too many forced-in features were specified or the features were high cardinality attributes, or both.; Action: Reduce the number of forced-in attributes.
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-40033: invalid covariance matrix: 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.; Action: Modify the data or disable ridge regression to get a valid covariance matrix and full diagnostic statistics.
ORA-40034: FORCE_IN incompatible with the setting GLMS_FTR_SELECTION disabled: Cause: The setting GLMS_FTR_SELECTION which was disabled was incompatible with the specified FORCE_IN transformation.; Action: Either enable the setting GLMS_FTR_SELECTION, or respecify the FORCED_IN transformation to be compatible with the disabled GLMS_FTR_SELECTION setting.
ORA-40051: too few rows to estimate the specified model: Cause: The time series had fewer rows than the number of parameters in the model.; Action: Choose a simpler model type with fewer parameters.
ORA-40052: series contains large numbers; possible numerical instability: Cause: The time series contained numbers greater than 1 million.; Action: Scale the data.
ORA-40053: inappropriate data for multiplicative model: Cause: The time series was not strictly positive.; Action: Choose a model type that does not contain a multiplicative trend or seasonality.
ORA-40054: time series is constant: Cause: The time series was constant.; Action: Choose a model type that does not contain a multiplicative trend or seasonality.
ORA-40055: too few rows to estimate trend: Cause: The time series had too few rows to obtain an initial trend estimate.; Action: Choose a simple exponential model type.
ORA-40056: must provide a valid EXSM_INTERVAL setting: 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.; Action: Specify a valid EXSM_INTERVAL setting.
ORA-40057: must provide a valid case ID column: Cause: The case ID column was required to provide time labels, but a valid case ID column was not provided.; Action: Specify a valid case ID column name as input.
ORA-40058: seasonal effect not estimable for irregular time series: Cause: There was no consecutive one year period containing all existing seasons.; Action: Choose a model type with no seasonal effect.
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-40124: partition key column string missing from input: Cause: A partitioned model was referenced in the query, but the partition key column was not found in the input.; Action: Provide an input dataset containing the partition key column.
ORA-40125: partition string does not exist: Cause: The partition entered did not exist.; Action: Check the spelling of the partition and try again.
ORA-40126: model string is not partitioned: Cause: The model specified was not a partitioned model.; Action: Specify a model that is partitioned.
ORA-40127: invalid number of partition keys specified: Cause: The number of partition keys specified did not match the model.; Action: Specify key values for each partition.
ORA-40128: partition string exists for partition keys specified: Cause: A partition already existed for the partition keys specified.; Action: Specify unique key values for each partition.
ORA-40129: partition name string exists for this model: Cause: The partition name specified was not unique for this model.; Action: Specify a unique partition name.
ORA-40130: invalid partition name string: Cause: The partition name specified was not valid.; Action: Check the spelling of the partition name and try again.
ORA-40131: invalid data type for partition column string: Cause: The partition column did not have a supported data type.; Action: Choose a partition column of type NUMBER, CHAR, or VARCHAR2.
ORA-40132: partition not specified: Cause: A model partition was not specified. This function requires the specification of a model partition.; Action: Specify a model partition.
ORA-40133: invalid partition columns: Cause: The partition columns in the operation did not match those in the existing model.; Action: Specify the correct partitioning keys.
ORA-40135: cannot drop the only partition of a partitioned model: Cause: The specified partitioned model contained a single partition. An empty model is not supported.; Action: Drop the model, or add additional partition(s) then drop the desired partition.
ORA-40136: maximum number of partition columns exceeded: Cause: The maximum number of 16 partition columns was exceeded.; Action: Reduce the number of partition columns.
ORA-40137: maximum number of partitions exceeded: Cause: The maximum number of partitions per model was exceeded.; Action: Reduce the number of partitions.
ORA-40139: no partitions found in training data: Cause: There were no partitions found in the training data.; Action: Specify partitioning keys that have one or more distinct values in the training data.
ORA-40140: model could not be built: Cause: The training data did not allow the building of a meaningful model.; Action: Modify the training data to ensure that there are valid data rows, columns, or targets. If there is solver choice, ensure that the selected solver is appropriate for the training data.
ORA-40141: only zero norm rows were provided in the training data: Cause: All training data rows had zero norm.; Action: Modify the training data or enable automatic data preparation.
ORA-40142: partition mismatch for feature comparison: Cause: The partition key column values did not match for one or more scored rows.; Action: Modify the query to ensure that each scored row contains matching partition key column values.
ORA-40150: Model string function is not specified.: Cause: The required R function was not specified.; Action: Specify the required R function in the model setting table and build the R model.
ORA-40151: invalid output type from R SCORE, WEIGHT, or DETAILS function: 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.; Action: Modify the R function to return the result in a data.frame that contains values of valid types.
ORA-40152: Output data.frame mismatches the input for R SCORE or WEIGHT function.: Cause: The R SCORE or WEIGHT function returned a different number of rows than that of the input data.frame.; Action: Modify the R function to output the result for each row of the input data.frame.
ORA-40153: invalid value on attribute string for R model: Cause: The specified attribute was not a scalar numeric value or a single string.; Action: Set the specified attribute of the R model with a valid value.
ORA-40154: invalid type or value for R parameter specification: Cause: The R parameter was not a scalar numeric value or a single string.; Action: Modify the parameter specification to use either a scalar numeric value or a single string.
ORA-40155: R script string is not found.: Cause: The specified script was not found in the R script repository.; Action: Verify that the script exists in the R script repository or create it using the rqScriptCreate PL/SQL function.
ORA-40156: invalid or mismatched output specification for R model view: 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.; Action: Use scalar numeric and string to specify the R DETAILS function output format and match the actual output of the R function.
ORA-40157: R_HOME is not set on string.: Cause: The R_HOME was not set to the location where R was installed.; Action: Use sys.rqConfigSet to set the R_HOME to the correct value.
ORA-40158: invalid values on R memory control settings: Cause: The R memory control settings did not use positive values.; Action: Use sys.rqConfigSet to set R memory control with valid values.
ORA-40159: Parameter setting string is not specified for R model.: Cause: The expected setting was not on the model setting table.; Action: Set the expected setting on the model setting table.
ORA-40160: Mining function string requires attribute string on the R model.: Cause: The generated R model did not have the required attribute.; Action: Set the required attribute for the R model in the R BUILD function.
ORA-40161: Either attribute string or string, but not both, is required.: Cause: Conflict attributes were specified for the R model object.; Action: Set the required attribute only for the return R model object.
ORA-40162: mismatched results from string output data.frame: 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.; Action: Modify the specified R function to return the results in the right format.
ORA-40163: some prediction results missing from string output: 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.; Action: Modify the R model SCORE function to return all predicted values in the output data.frame.
ORA-40164: contribution weights of some attributes missing from string output: Cause: The R model WEIGHT function did not return the contribution weight for each attribute of the data.; Action: Modify the R model WEIGHT function to return the contribution weights for all attributes.
ORA-40165: mismatched target class name from R model prediction string: Cause: The R classification model prediction did not have correct target class names assigned as the column names for the return data.frame.; Action: Modify the R classification model SCORE function to set the correct target class names on the return data.frame.
ORA-40166: invalid R name for input data.frame columns: Cause: The input data.frame column names contained special characters that are not supported by R.; Action: Modify the input data.frame column names and remove the unsupported characters from the column names.
ORA-40167: no valid data in input table: Cause: The specified input table contained no valid data to build R model.; Action: Insert valid data into the input table to build R model.
ORA-40170: Error out in R: string: Cause: The R function execution failed.; Action: Verify the specified R model function script.
ORA-40171: The algorithm cannot be dropped because there are models built on it.: Cause: An attempt was made to drop models built on this algorithm.; Action: Drop the model first.
ORA-40172: The algorithm registration does not follow the predefined JSON schema.: Cause: An attempt was made to register an algorithm that did not follow the predefined JavaScript Object Notation (JSON) schema.; Action: Check the predefined JSON schema and revise the algorithm format.
ORA-40173: The same algorithm name, mining function, and algorithm type combination already exits.: Cause: An attempt was made to register an algorithm with the same name, mining function and type combination.; Action: Use a different algorithm name for the same mining function and algorithm type.
ORA-40174: The algorithm that is used is not registered yet.: Cause: The specified algorithm did not exist.; Action: Register the algorithm first.
ORA-40175: Registered algorithm name and R script definition cannot be used simultaneously.: Cause: An attempt was made to use both registered algorithm name and R scripts definition.; Action: Keep either registered algorithm name or R script definition, but not both.
ORA-40176: The current user does not have privilege to register or drop an algorithm.: Cause: The privileges to register or drop an algorithm were not granted.; Action: Obtain the proper privileges before attempting to register or drop an algorithm.
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 and attribute importance functions accept CHAR, VARCHAR2, and NUMBER data type targets. VARCHAR2 data type targets longer than 4000 bytes are not supported. Regression and time series functions accept NUMBER, BINARY_DOUBLE, and BINARY_FLOAT data type 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: Ensure that the operation being performed is valid for the mining function used to build the model (using for 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: must specify a valid ID column name when setting string is provided: Cause: The training data is transactional. A valid ID column must be specified.; 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-40235: invalid setting value for setting ASSO_AGGREGATES: string: Cause: The setting ASSO_AGGREGATES was not valid.; Action: Specify valid aggregates column names.
ORA-40236: maximum number of aggregates exceeded: Cause: The setting ASSO_AGGREGATES specified too many aggregates.; Action: Reduce the number of aggregates.
ORA-40237: duplicate case IDs in training table: Cause: The same value occurred more than once in the case ID column of the training table.; Action: Eliminate the duplicate case IDs in the training table.
ORA-40238: invalid linear algebra shared library string: Cause: The shared library containing platform-optimized linear algebra routines was not loaded.; Action: Verify that the shared library is correctly installed.
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 or weights cannot be specified for one-class models: Cause: Priors or weights were specified.; Action: Do not specify priors or weights 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-40308: RFOR_MTRY is greater than attribute count or negative or 0: 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.; Action: Consider a different value for RFOR_MTRY.
ORA-40309: The Random Forest sample size exceeds available memory.: Cause: The sample did not fit into available memory.; Action: No action needed. The sample size was adjusted automatically to fit into memory.
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-40325: maximum number of clusters exceeded: Cause: The maximum number of clusters was exceeded.; Action: Reduce the number of clusters.
ORA-40326: no mining attributes after filtering: Cause: All mining attributes were filtered out.; Action: Disable attribute filtering.
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: Ensure that the dependents of the object are valid before attempting to grant the privilege on the object.
ORA-40363: GRANT failed: user SYS always has SYSOPER and SYSDBA: 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.; Action: Try granting administrative privilege to users other than SYS.
ORA-40364: Use of BECOME USER functionality is restricted.: Cause: This is an internal error message.; Action: Contact Oracle Support Services.
ORA-40365: The SYS user cannot be locked while the password file is in its current format.: 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.; Action: The password file must be created in the 12.2 format to provide support for maintaining the ACCOUNT_STATUS of all administrative users including SYS.
ORA-40366: Administrative privilege cannot be granted to this user.: 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.; Action: Do not grant administrative privilege to user with NONE as its AUTHENTICATION_TYPE in DBA_USERS view.
ORA-40367: An Administrative user cannot be altered to have no authentication type.: Cause: An attempt was made to alter an administrative user to have no authentication type.; Action: Revoke administrative privilege from the user before attempting to alter the user.
ORA-40381: Invalid field specification for: string: Cause: The derived field was incorrectly defined.; Action: Ensure that 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: Ensure that 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: Ensure that 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. Ensure that 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. Ensure that 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. Ensure that at least two LinearNorm elements are included.
ORA-40387: Invalid interval for Discretize field: string: Cause: The intervals were incorrect.; Action: Ensure that that both margins are not missing.
ORA-40388: Unsupported feature in PMML document: string: Cause: The feature was not supported by Predictive Model Markup Language (PMML) model import.; Action: Ensure that you use the supported features.
ORA-40389: Unsupported PMML transformation: string: Cause: The transformation was not supported.; Action: Ensure that you use the supported transformations.
ORA-40390: PMML DerivedField must have a unique name specified: string: Cause: "The Predictive Model Markup Language (PMML) DerivedField did not reference another defined field and did not have a unique name."; Action: "Specify a unique name for each DerivedField."
ORA-40391: PMML DerivedField depends on a undefined field: string: Cause: A DerivedField referenced an undefined field.; Action: Ensure that the DerivedField references other defined fields.
ORA-40392: PMML regression equation references an undefined field: string: Cause: The Predictive Model Markup Language (PMML) Regression equation did not reference defined fields. PMML Regression equation may only reference defined fields.; Action: Ensure that 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-40405: Full SVD solvers cannot be used for the build data.: Cause: The build data had a very high number of attributes. A Singular Value Decomposition (SVD) model cannot be built using full SVD solvers.; Action: Select a truncated SVD solver.
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-40423: Extraction of tokens from text failed: Cause: Extraction of tokens from an attribute of TEXT type failed.; Action: Check text policy, policy owner, other settings for TEXT type, and computer resources.
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 ('string')string: 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: Ensure that 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 the RETURNING clause.; Action: Ensure 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 ('string')string: Cause: The provided JavaScript Object Notation (JSON) path expression contained an invalid array index.; Action: Provide a valid array index. The first element in the array has the index 0.
ORA-40458: JSON_EXISTS used outside predicate: Cause: The operator JSON_EXISTS was used outside of a predicate.; Action: Use JSON_EXISTS inside a predicate, 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 was not used in the PASSING clause.; Action: Ensure 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 a JSON-enabled context index: Cause: There was no JavaScript Object Notation (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, or the length of a JSON field name in the path expression exceeded the JSON search index token length limit.; Action: Neither use a predicate or array position in a JSON path expression nor a step with length longer than the JSON search index token length limit.
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 JavaScript Object Notation (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-40496: too many keys for JSON_OBJECTAGG: Cause: The number of rows in a JSON_OBJECTAGG aggregation group exceeded the maximum number of keys for a JSON Object.; Action: Reduce the number of rows in each group, or remove the WITH UNIQUE KEYS check.
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 JavaScript Object Notation (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-40504: file string created before last CREATE CONTROLFILE, could not proceed with recovery: 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.; Action: Restore a more recent backup of the data file and retry the recovery.
ORA-40505: tablespace #string has been dropped: 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.; Action: None
ORA-40507: The file header of data file string is corrupt. Automatic block repair is trying to fix the file header.: Cause: A corrupt data file header was encountered during a checkpoint.; Action: Run the query after the data file header is fixed by the automatic block repair.
ORA-40509: cursor compilation failed because string: Cause: Cursor compilation failed. Check the alert log for more details.; Action: Run the query again after fixing the condition that failed cursor compilation.
ORA-40510: This type of file cannot be renamed.: Cause: An attempt was made to rename a file for which renaming is not supported.; Action: Do not attempt to rename files of this type.
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.
ORA-40557: cannot update a JSON value: Cause: An attempt was made to update a JavaScript Object Notation (JSON) value.; Action: Update the entire JSON object instead.
ORA-40558: package functions are unsupported below compatible 12.0.0.0.0: Cause: DBMS_SODA_ADMIN was used when the database was operating at a compatible setting lower than 12.0.0.0.0.; Action: Upgrade the database compatible setting to 12.0.0.0.0 or higher to enable the desired new features.
ORA-40559: one or more JSON objects exist that cannot be downgraded.: Cause: There were JavaScript Object Notation (JSON) objects in the database that were created in a release beyond the selected release for downgrade.; Action: Prior to downgrade, drop the JSON objects that cannot be downgraded to the selected release.
ORA-40560: JSON_TABLE nested path expressions not disjunct: Cause: The JSON_TABLE expression contained two or more nested path expressions that (partially or fully) selected the same fields.; Action: Correct or combine the nested path expressions so that they become disjunct.
ORA-40561: invalid path in JSON_TABLE nested path clause: Cause: The JSON_TABLE expression contained a nested path clause with an invalid path expression.; Action: Correct or remove the nested path expression.
ORA-40562: Conversion from GeoJSON to SDO_GEOMETRY failed.: Cause: The selected value could not be converted to a SDO_GEOMETRY object.; Action: Ensure that the path expression selects one valid GeoJSON value.
ORA-40563: default value not allowed for object types.: Cause: The error handler specified a default value and the returned data type was an object type. These cannot be combined.; Action: Change either the return type or choose 'NULL ON ERROR' or 'ERROR ON ERROR' as error handler.
ORA-40564: Invalid JSON specification.: Cause: The provided specification was invalid.; Action: Correct the specification parameter.
ORA-40565: JSON path expression did not select a value.: Cause: The JavaScript Object Notation (JSON) path expression did not select a value.; Action: Correct the JSON path expression.
ORA-40566: JSON path expression selected a value of different data type.: Cause: The JavaScript Object Notation (JSON) path expression selected a data type value different than the requested data type.; Action: Use another 'get-method' to retrieve the value selected by the JSON path expression.
ORA-40567: JSON patch operation failed.: Cause: The JavaScript Object Notation (JSON) patch operation failed.; Action: Correct the specification parameter.
ORA-40568: Cannot modify read-only target.: Cause: An attempt to modify a JavaScript Object Notation (JSON) structure failed because the structure cannot be modified.; Action: None
ORA-40569: Unimplemented JSON feature.: Cause: An attempt was made to execute an unimplemented JavaScript Object Notation (JSON) feature.; Action: None
ORA-40570: JSON conversion failed.: Cause: A conversion between a JavaScript Object Notation (JSON) value and another type failed.; Action: Check the type definition or the selected JSON value.
ORA-40571: JSON key name not found.: Cause: A key with the specified name was not found in the JavaScript Object Notation (JSON) data.; Action: Correct the key name.
ORA-40572: Invalid JSON array position.: 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.; Action: Correct the position value.
ORA-40573: Invalid use of PL/SQL JSON object type.: Cause: An attempt was made to use a PL/SQL JavaScript Object Notation (JSON) object type in an invalid context.; Action: Use PL/SQL JSON object types only inside PL/SQL.
ORA-40574: JSON operation on redacted column string not allowed.: Cause: An attempt was made to use a JavaScript Object Notation (JSON) operation on a column which has a redaction policy.; Action: Drop the redaction policy. Re-create redaction policy on a new view over the column if needed.
ORA-40576: Invalid use of bind variable in SQL/JSON path.: Cause: An attempt was made to bind a non-runtime constant to a bind variable in SQL/JSON path.; Action: Bind either compile time constant or runtime SQL bind variable value to a bind variable for SQL/JSON path.
ORA-40577: invalid key name: Cause: The provided key name was not valid.; Action: Provide a valid key name.
ORA-40578: invalid or non-existent array position: Cause: The provided array position was not valid or non-existant.; Action: Provide a valid array position or use the 'append' function to add new items to the array.
ORA-40581: package functions are unsupported below compatible string: Cause: The package was used with a database that was operating at a compatible setting lower than expected.; Action: Upgrade the database to a compatible setting that is the expected release or higher to enable the desired new features.
ORA-40582: cannot find a data guide-enabled context index: Cause: A data guide-enabled context index for the specified column in the specified table was not found.; Action: Ensure that the table and column exist, the column is a JavaScript Object Notation (JSON) column, and a data guide-enabled context index exists on the JSON column before invoking the procedure or function.
ORA-40583: view name or table name or JSON column name cannot be null: Cause: The view name or table name or JSON column name was null.; Action: Pass in a valid view name or table name or JavaScript Object Notation (JSON) column name to the function or procedure.
ORA-40584: JSON column string does not exist: Cause: The given table did not have a JavaScript Object Notation (JSON) column with the given name.; Action: Ensure that the table name and JSON column name are specified correctly.
ORA-40585: invalid frequency: Cause: The specified frequency was invalid.; Action: The range of frequency has to be 0 to 100.
ORA-40586: error occurred in the execution of string: Cause: A internal error occurred.; Action: This is an internal error. Contact Oracle Support Services.
ORA-40587: invalid JSON type: Cause: The specified JavaScript Object Notation (JSON) type was invalid.; Action: Ensure that the JSON type is specified correctly.
ORA-40588: invalid estimate percentage: Cause: The specified estimate percentage was invalid.; Action: The range of estimate percentage has to be 0.000001 to 100.
ORA-40589: path string does not exist: Cause: The specified path was not found.; Action: Ensure that the specified path exists.
ORA-40590: invalid format: Cause: The specified format was invalid.; Action: Ensure that the format is specified correctly.
ORA-40591: empty data guide on json column: Cause: No data has been inserted to the json column.; Action: Insert data or commit.
ORA-40592: name conflicts were found during execution of DBMS_JSON.ADDVC: string: 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.; Action: Change the preferred name of the virtual column in the annotated Javascript Object Notation (JSON) data guide.
ORA-40593: name conflicts were found during execution of DBMS_JSON.CREATEVIEW: string: 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.; Action: Change the preferred name of the column in the annotated Javascript Object Notation (JSON) data guide.
ORA-40594: invalid data guide: Cause: The specified data guide was invalid.; Action: Ensure that the specified data guide follows data guide rules.
ORA-40595: Name input to JSON generation function cannot be null.: Cause: The name input given to the Javascript Object Notation (JSON) generation function was null.; Action: Ensure that the input has a valid value.
ORA-40596: error occurred in JSON processing string: Cause: An error occurred when evaluating the JavaScript Object Notation (JSON) operator.; Action: None
ORA-40597: JSON path expression syntax error ('string')string\nat position string: Cause: The specified JavaScript Object Notation (JSON) path expression had invalid syntax and could not be parsed.; Action: Specify JSON path expression with the correct syntax.
ORA-40598: JSON path expression contained an invalid array index ('string')string\nat position string: Cause: The specified JavaScript Object Notation (JSON) path expression contained an invalid array index.; Action: Specify a valid array index. The first element in the array has the index 0.
ORA-40599: IS JSON check constraint cannot be dropped.: Cause: IS JSON check constraint could not be dropped when there was a JSON search index created on the column.; Action: Drop the JSON search index first before dropping the IS JSON check constraint.
ORA-40600: JSON_EQUAL used outside predicate: Cause: The operator JSON_EQUAL was used outside of a predicate.; Action: Use JSON_EQUAL inside a predicate, for instance by embedding it inside a CASE expression.
ORA-40620: total length of key names in JSON object too long: Cause: The length of all the key names combined exceeded the maximum length permitted for a JavaScript Object Notation (JSON) object.; Action: Use fewer keys or shorter key names.
ORA-40621: Collection create mode string is not supported.: Cause: An invalid collection create mode was specified.; Action: Use a valid collection create mode.
ORA-40622: Creating a collection backed by view or package in ''NEW'' mode is not allowed.: Cause: Creating a collection backed by view or package in NEW mode was not allowed.; Action: Do not specify a view or package when creating the collection in NEW create mode, or specify a create mode that supports view or package-based collections.
ORA-40623: The table intended to back the collection does not exist.: Cause: The table intended to back the collection did not exist.; Action: Ensure that the table intended to back the collection exists.
ORA-40624: Columns of the mapped table backing the collection do not match collection metadata.: Cause: The columns of mapped table backing the collection did not match the collection metadata.; Action: Ensure that the columns of the table backing the collection match their description in collection metadata.
ORA-40625: The view intended to back the collection does not exist.: Cause: The view intended to back the collection did not exist.; Action: Ensure that the view intended to back the collection exists.
ORA-40626: The table or view underlying the collection cannot be dropped.: Cause: The table or the view underlying the collection could not be dropped. There could be uncommitted writes to the collection.; Action: Ensure that all writes to the collection are committed.
ORA-40627: Columns of the mapped view backing the collection do not match collection metadata.: Cause: The columns of mapped view backing the collection did not match the collection metadata.; Action: Ensure that the columns of the view backing the collection match their description in collection metadata.
ORA-40628: Projection specification is not valid JSON: Cause: Projection specification was not expressed in valid JSON.; Action: Ensure that projection specification is expressed in valid JSON.
ORA-40629: Patch specification is not valid JSON: Cause: Patch specification was not expressed in valid JSON.; Action: Ensure that patch specification is expressed in valid JSON.
ORA-40630: Versioning method 'string' is not valid.: Cause: The specified versioning method was not valid.; Action: Specify a valid versioning method.
ORA-40631: The last-modified column index can only be set when the last-modified column name is set.: Cause: The last-modified column index was specified without setting the last-modified column name.; Action: Specify the last-modified column name if the last-modified column index is required.
ORA-40632: Key column length value cannot be less than 0.: Cause: The specified key column length value was less than 0.; Action: If the key column length value is specified, then ensure that it is greater than 0.
ORA-40633: When using GUID or UUID to assign character type key values, the key column length must be 32 bytes or greater.: Cause: The specified key column length for a GUID or UUID character type key value was less than 32 bytes.; Action: Ensure that the specified key column length for a GUID or UUID character type key value is 32 bytes or greater.'
ORA-40634: Key assignment method 'string' is not valid.: Cause: The specified key assignment method was not valid.; Action: Specify a valid key assignment method.
ORA-40635: If the key assignment method is 'SEQUENCE', a key column sequence name must be specified.: Cause: The key assignment method 'SEQUENCE' was specified, but the key column sequence name was not set.; Action: If the key assignment method is 'SEQUENCE', ensure that the key column sequence name is set.
ORA-40636: Content column type 'string' is not valid.: Cause: The specified content column type was not valid.; Action: Specify a valid content column type.
ORA-40637: Content column maximum length value cannot be less than 0.: Cause: The specified content column maximum length value was less than 0.; Action: Specify a content column maximum length value greater than 0.
ORA-40638: Content column validation mode 'string' is not valid.: Cause: The specified content column validation mode was not valid.; Action: Specify a valid content column validation mode.
ORA-40639: Content column compress setting 'string' is not valid.: Cause: The specified content column compress setting was not valid.; Action: Specify a valid content column compress setting.
ORA-40640: Content column LOB cache setting 'string' is not valid (must be 'true' or 'false').: Cause: The specified content column LOB cache setting was not valid.; Action: 'Specify a valid content column LOB cache setting.
ORA-40641: Content column LOB encrypt setting 'string' is not valid.: Cause: The specified content column LOB encrypt setting was not valid.; Action: Specify a valid content column LOB encrypt setting.
ORA-40642: The collection cannot have a media type column unless the content column type is BLOB.: Cause: The content column type was set to a type other than Binary Large Object (BLOB), and the media type column was requested.; Action: If the media type column is requested, set the content column type to BLOB.
ORA-40643: INITIAL storage clause parameter value cannot be less than 0.: Cause: The specified INITIAL storage clause parameter value was not valid.; Action: Specify a valid INITIAL storage clause parameter value.
ORA-40644: PCTINCREASE storage clause parameter value cannot be less than 0.: Cause: The specified PCTINCREASE storage clause parameter value was not valid.; Action: Specify a valid PCTINCREASE storage clause parameter value.
ORA-40645: If the key column sequence name was specified, the key column assignment method must be set to 'SEQUENCE'.: Cause: The key column sequence name was specified, but the key column assignment method was not 'SEQUENCE'.; Action: If the key column sequence name is specified, ensure that the key column assignment method is 'SEQUENCE'.
ORA-40646: SecureFile LOB settings cannot be used when the content column type is 'string'.: Cause: SecureFile LOB settings were specified, but the content column was not of LOB type.; Action: If SecureFile LOB settings are specified, ensure that the content column is of LOB type.
ORA-40647: A non-zero content column maximum length cannot be set for LOB content types.: Cause: A non-zero content column maximum length was specified, but the content column was of a LOB type.; Action: If non-zero content column maximum length is specified, ensure that the content column is not of a LOB type.
ORA-40648: Versioning method other than 'NONE' can only be specified if version column name is specified.: Cause: Versioning method other than 'NONE' was specified, but the version column name was not specified.; Action: If a versioning method other than 'NONE' is specified, ensure that the version column name is set.
ORA-40649: Key column maximum length cannot be greater than 255 bytes.: Cause: A key column maximum length value greater than 255 bytes was specified.; Action: Ensure that the key column maximum length value is not greater than 255 bytes.
ORA-40650: The specified key column type cannot be used with a maximum length.: Cause: A key column type that does not support maximum length was specified.; Action: Ensure that if a key column maximum length is set, the key column type supports a maximum length setting.
ORA-40651: Key column type 'string' is not valid.: Cause: The specified key column type was not valid.; Action: Specify a valid key column type.
ORA-40652: Read-only setting is not valid (must be 'true' or 'false').: Cause: The specified read-only setting was not valid.; Action: Specify a valid read-only setting.
ORA-40653: Spatial data type MDSYS.SDO_GEOMETRY not found.: Cause: The spatial data type MDSYS.SDO_GEOMETRY could not be found.; Action: Create data type MDSYS.SDO_GEOMETRY by installing Oracle Spatial and Graph or Oracle Locator.
ORA-40654: Input to JSON generation function has unsupported data type.: Cause: An input parameter to the JavaScript Object Notation (JSON) generation function had a data type that is not supported.; Action: Use the correct input or a conversion function to convert the input to a supported data type.
ORA-40655: no PASSING clause specified: Cause: The PASSING clause was not specified for the bind variables in the query.; Action: Add a PASSING clause to specify the values for bind variables.
ORA-40656: Variable in JSON path expression has no value in PASSING clause.: Cause: The JavaScript Object Notation (JSON) path expression contained a variable name that had no corresponding value in the external PASSING clause.; Action: Add a variable to the external PASSING clause and ensure that the names match.
ORA-40657: Variable in PASSING clause has no name.: Cause: The expression provided in the PASSING clause had no name.; Action: Name the expression in the PASSING clause.
ORA-40658: Collection name cannot be null for this operation.: Cause: An attempt was made to perform the operation without a name.; Action: Specify the collection name for the operation.
ORA-40659: Data type does not match the specification in the collection metadata.: Cause: An attempt was made to use an invalid data type.; Action: Use the data type that is specified in the collection descriptor.
ORA-40660: Content value cannot be null for instantiating a document.: Cause: An attempt was made to instantiate a document with a null content.; Action: Specify non-null content for instantiating the document.
ORA-40661: Key value cannot be null for this operation.: Cause: An attempt was made to perform an operation with a null key.; Action: Specify non-null key for the operation.
ORA-40662: Document cannot be null for this operation.: Cause: An attempt was made to perform an operation with a null document.; Action: Instantiate a document using the constructor before this operation.
ORA-40663: cannot modify a read-only collection: Cause: An attempt was made to modify a read-only collection.; Action: None
ORA-40664: cannot add additional IS JSON check constraint: Cause: An attempt was made to add an IS JSON check constraint to a column that already had an IS JSON check constraint.; Action: None
ORA-40665: A client-assigned key cannot be used for this operation.: Cause: An attempt was made to use a client-assigned key for this collection.; Action: Remove the client-assigned key from the document.
ORA-40666: Internal error 'string' received from JSON processor: Cause: An internal error was received during a JSON operation.; Action: This is an internal error. Contact Oracle Support Services.
ORA-40667: Patch operation cannot destroy JSON_ELEMENT_T type.: Cause: An operation in the patch specification attempted to remove the top-most container (object or array) from the JSON_ELEMENT_T type.; Action: Modify the patch specification by either removing the operation that deletes the top-most container or by adding an operation that adds a new top-most container.
ORA-40668: collection metadata too long: Cause: The collection metadata which was passed was too long.; Action: Reduce the size of the collection metadata.
ORA-40669: Collection create failed: collection with same name but different metadata exists.: Cause: Creation of the collection failed because there was an existing collection with same name but different metadata.; Action: None
ORA-40670: Unable to complete collection create due to an interfering collection DDL operation.: Cause: Existing collection with the same name was encountered, but dropped from another process before its metadata could be checked.; Action: Retry creating the collection.
ORA-40671: Collection not found.: Cause: Collection was not found.; Action: None
ORA-40672: Specified key column max length of string bytes exceeds maximum allowed 255 bytes.: Cause: Key column max length specified in the supplied metadata exceeded maximum allowed length of 255 bytes.; Action: Ensure key column max length specified in the supplied metadata does not exceed 255 bytes.
ORA-40673: string argument cannot be NULL.: Cause: Supplied argument was NULL.; Action: Provide a valid argument.
ORA-40674: Length of string metadata value cannot exceed string bytes.: Cause: Length of the supplied metadata value exceeded allowed limit.; Action: Provide a valid metadata value.
ORA-40675: Metadata descriptor must be specified using valid JSON.: Cause: JSON supplied for the metadata descriptor was not valid.; Action: Supply valid JSON for the metadata descriptor.
ORA-40676: invalid filter condition: Cause: The Query-By-Example (QBE) filter condition was invalid.; Action: Correct the filter condition.
ORA-40677: internal SODA error: Cause: There was an internal error in the Simple Oracle Document Access (SODA) processing layer.; Action: None
ORA-40678: exceeded maximum number of keys in filter condition: Cause: The number of keys exceeded allowed limit.; Action: Reduce the number of keys to below 1000.
ORA-40679: Lob length of string bytes exceed maximum supported length of string bytes: Cause: The large object (LOB) content that was fetched exceeded the maximum supported length; Action: None
ORA-40680: invalid identifier used for path expression in JSON_TABLE: Cause: A double-quoted identifier used a path expression that was invalid.; Action: Use single quotes to specify the path expression.
ORA-40681: OCI_SODA_AS_STORED cannot be used if the content column type is CLOB or VARCHAR2: Cause: An attempt was made to use OCI_SODA_AS_STORED on a collection whose content column type is not BLOB.; Action: Use OCI_DEFAULT or OCI_SODA_AS_AL32UTF8.
ORA-40682: invalid combination of flags used: Cause: An attempt was made to use an invalid combination of flags.; Action: Use only one of the flags. (OCI_DEFAULT, OCI_AS_STORED or OCI_SODA_AS_AL32UTF8)
ORA-40683: Value 'string' is not valid for field 'string' (must be 'true' or 'false').: Cause: The specified setting was not valid.; Action: Specify a valid setting ('true' or 'false').
ORA-40684: maximum number of key names exceeded: Cause: An attempt was made to return a list of keys names for a JSON object that had more than 32767 keys.; Action: Reduce the number of keys in the JSON object to 32767 or less.
ORA-40685: UTF-32 encoding is not supported for JSON documents.: Cause: UTF-32 encoded content was specified for a document of type "applicaton/json".; Action: Use UTF-8 or UTF-16 encoding with JavaScript Object Notation (JSON) documents.
ORA-40686: For a JSON-only collection, media type of the input document must be 'application/json'.: Cause: An attempt was made to write a document with media type other than 'application/json' to a JSON-only collection.; Action: Provide a document with media type 'application/json'.
ORA-40687: CREATE_MODE parameter of CREATE_COLLECTION function is invalid.: Cause: Invalid value was supplied as CREATE_MODE parameter of CREATE_COLLECTION function.; Action: Supply MAP or DDL constant for the CREATE_MODE parameter of CREATE_COLLECTION function.
ORA-40701: null case ID column - cannot provide row importance: Cause: The row importance was enabled, 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.