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

ORA-40001: value for string must be greater than zero
Cause: The input parameter in question has a value of zero or less.
Action: Provide a value greater than zero for the relevant parameter.
ORA-40002: wordsize must be string or greater
Cause: The input wordsize is less than the prescribed limit for the BLAST Match
or Align algorithm.
Action: Provide a wordsize greater than or equal to the prescribed value.
ORA-40003: wordsize must be in the range string - string for BLAST-P
Cause: The input wordsize has a value out of the prescribed range.
Action: Provide a wordsize value within the prescribed range for BLAST-P.
ORA-40004: penalty must be negative for BLAST-N
Cause: The input value provided for penalty is zero or greater.
Action: Provide a negative penalty value.
ORA-40021: no column named string in training table string
Cause: The training table does not contain the specified column
Action: Provide a case-id/target column that exists in the training table
ORA-40022: null case ID column - cannot provide row diagnostics in string
Cause: A row diagnostics table name was provided, but without a corresponding
case or row identifier column in the build data.
Action: Provide a non-null case identifier column in the build data to identify
rows in the row diagnostics table.
ORA-40023: sufficient memory could not be allocated given the number of
attributes
Cause: Unable to allocate sufficient memory to create a model capable of
producing confidence bounds on predictions because there were too many
attributes or there were high cardinality categorical attributes, or both, in the build
data.
Action: Reduce the number of attributes, especially high cardinality categoricals,
or enable ridge regression.
ORA-40024: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular.
22-2 Oracle Database Error Messages
Action: Enable ridge regression or remove exact multicollinearities from the build
data.
ORA-40025: reference class name not found in build data
Cause: The provided reference class name was not found in the build data.
Action: Provide an existing target value as the reference class name.
ORA-40026: reference class name not found in the weights table
Cause: The provided reference class name did not correspond to any of the entries
in the weights table.
Action: Provide consistent specification for reference class name and weights
table.
ORA-40027: Target attribute has more than two distinct values
Cause: Generalized Linear Models only support binary classification.
Action: Consolidate target values into two distinct categories.
ORA-40028: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor build data were not properly
scaled.
Action: Standardize the predictor build data by enabling auto prep.
ORA-40029: Specified diagnostics table name already exists
Cause: A diagnostics table name matching an existing table was specified.
Action: Choose a table name that does not match any existing user table.
ORA-40030: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular for the forced-in features.
Action: If there are forced-in features, remove them. If GLMS_FTR_
ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_STRICT, reset it to GLMS_
FTR_ACCEPTANCE_RELAXED and rebuild the model.
ORA-40031: insufficient memory for model build given the number of forced-in
features (maximum allowable for this data: string)
Cause: Unable to allocate sufficient memory to create a feature-selection model
because there were too many forced-in features or the forced-in features were high
cardinality categorical attributes, or both.
Action: Reduce the number of forced-in attributes, especially high cardinality
categoricals.
ORA-40032: solution to least squares problem could not be found
Cause: Unable to find solution because the predictor covariance matrix was
singular for the selected features.
Action: If GLMS_FTR_ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_
STRICT, reset it to GLMS_FTR_ACCEPTANCE_RELAXED and rebuild the model.
ORA-40101: Data Mining System Error string-string-string
Cause: An internal system error occured during a data mining operation.
Action: Contact Oracle Support Services.
ORA-40102: invalid input string for data mining operation string
ORA-40001 to ORA-40556 22-3
Cause: The input parameter is either null or invalid for the given operation.
Action: Provide a valid value. Check range for NUMBER parameters.
ORA-40103: invalid case-id column: string
Cause: The case-id column was invalid. If a case-id column is specified, it must be
present in the input data source. The case-id column cannot be the same as the
target column, and the column's data type is restricted to NUMBER, CHAR, and
VARCHAR2 when building a GLM model with a diagnostics table.
Action: Change the schema of your input data to supply a case-id column of
appropriate data type.
ORA-40104: invalid training data for model build
Cause: The training data provided in the reported table is unsuitable for build,
either because it is empty, has unsuitable data, or the schema of the table does not
match the input specifications.
Action: Inspect the training data and correct the contents/schema as appropriate.
ORA-40105: input data incompatible with model signature
Cause: The data provided for this post-build operation is in format different from
that used for model build.
Action: Provide data whose attribute data types match the build data. Input data
attributes must have the same data types as those described in the model signature
for the model.
ORA-40106: positive target value not specified for computing Lift
Cause: Positive target value has not been specified for Lift.
Action: Provide a positive target value for the Lift operation.
ORA-40107: operation requires string option to be installed
Cause: The specified option has not been installed with the RDBMS.
Action: Install the reported option and retry the operation.
ORA-40108: input data contains too few distinct target (string) values
Cause: At least two distinct target values are required for Build.
Action: Provide counter-example target values in the input data.
ORA-40109: inconsistent logical data record
Cause: Repeated instances of a record identifier or repeated attribute(s) in a
nested column.
Action: Remove or re-label repeated instances to resolve inconsistencies.
ORA-40110: Duplicate model tables found for table type string
Cause: Operation would result in duplicate model table types which is not
supported.
Action: Remove the duplicate entry.
ORA-40111: no mining attributes found in build data
Cause: Could not build a model when only special or empty columns were
present. Special columns include target, row weight, and case ID columns.
Action: Provide mining attribute data.
ORA-40112: insufficient number of valid data rows
22-4 Oracle Database Error Messages
Cause: Fewer than two valid data rows were found in the build data.
Action: Provide at least two valid build data rows. If the model is either a
classification or regression model, then valid rows must have non-NULL targets. If
a weight column was provided, then valid rows must have positive row weights.
In addition, if DELETE_ROW missing value treatment was used, consider
disabling it.
ORA-40113: insufficient number of distinct target values
Cause: Less than two distinct target values were found in the build data.
Action: Provide the classification build data with valid rows containing at least
two distinct target values. Valid rows must have non-NULL targets. If a weight
column was provided, then valid rows must have positive row weights. In
addition, if DELETE_ROW missing value treatment was used, consider disabling
it.
ORA-40114: weights table target values mismatched with build data
Cause: The entries in the weights table did not correspond to the target values in
the build data.
Action: Verify the entries in the weights table.
ORA-40115: weights table schema is incorrect
Cause: The weights table did not have the required schema.
Action: Provide a weights table with schema: (target_value, weight), where the
type of the first column corresponds to the type of the target column (CHAR,
VARCHAR2 or NUMBER) and the type of the second column is NUMBER.
ORA-40116: NULL values found in weights table
Cause: The weights table had NULL entries.
Action: Replace or eliminate all NULL entries in the weights table.
ORA-40117: repeated target values found in weights table
Cause: The weights table had repeated target values.
Action: Remove the repeated target values from the weights table.
ORA-40118: insufficient number of target values in weights table
Cause: The weights table had less that 2 target values.
Action: Provide at least two target values in the weights table.
ORA-40119: nested columns incompatible with missing value treatment
Cause: delete_row missing value treatment is not supported for nested columns.
Action: Use 2D (non-nested) data representation or manually delete the rows with
NULL values and disable the delete_row missing value treatment.
ORA-40120: invalid weight value in the weights table
Cause: Negative or zero weight values were found in the weights table.
Action: Ensure that weight values in the weights table are positive.
ORA-40121: force option not allowed for drop model in different schema
Cause: The force option was specified, but the model is in a different schema.
Action: If the force option is necessary, run the drop model from the owning
schema. If the force option is not necessary, set the force parameter to FALSE.
ORA-40001 to ORA-40556 22-5
ORA-40122: invalid data type for row weights column string.
Cause: Row weights column was not assigned one of the allowed data types.
Action: Choose a row weight column of type NUMBER or FLOAT.
ORA-40123: invalid row weights column string
Cause: Row weights column was the same as the target column.
Action: Choose a new row weights column.
ORA-40181: invalid transformation definition for column string
Cause: Transformation definition has duplicate or NULL columns.
Action: Provide a valid transformation definition specification.
ORA-40182: invalid column reference
Cause: Transformation expression has no column references or more than one
reference or the reference is qualified.
Action: Provide a valid expression.
ORA-40183: invalid stack definition for attribute string
Cause: Stack definition expression or reverse expression has syntax errors or it
does not match the transformation definition.
Action: Provide a valid expression.
ORA-40184: transformation definition does not match the data
Cause: Transformation definition specifies nested transformation for non-nested
data or it removes all of the columns.
Action: Provide a valid data.
ORA-40201: invalid input parameter string
Cause: The input parameter was either null or invalid.
Action: Provide a valid value for the input parameter.
ORA-40202: column string does not exist in the input table string
Cause: The column was missing from the table.
Action: Correct the table schema and/or provide the correct column name.
ORA-40203: model string does not exist
Cause: The model did not exist.
Action: Supply a valid model name.
ORA-40204: model string already exists
Cause: A model by the same name exists.
Action: Provide a different, unique name for the model.
ORA-40205: invalid setting name string
Cause: The input setting name was invalid.
Action: Consult the documentation for the settings table and provide a valid
setting name.
ORA-40206: invalid setting value for setting name string
Cause: The input value for the given setting name was invalid.
22-6 Oracle Database Error Messages
Action: Consult the documentation for the settings table and provide a valid
setting value.
ORA-40207: duplicate or multiple function settings
Cause: The input settings table contained settings for multiple mining functions.
Action: Provide setting(s) for a single function in the settings table.
ORA-40208: duplicate or multiple algorithm settings for function string
Cause: The input settings table had duplicate or multiple algorithm settings for a
mining function.
Action: Provide only one appropriate algorithm setting for the mining function.
ORA-40209: setting string is invalid for string function
Cause: The specified setting was not supported for the mining function supplied.
Action: Provide appropriate combination of function and algorithm settings.
ORA-40210: invalid score criterion type when cost matrix is specified
Cause: The score criterion type may not be 'PROBABILITY' when a cost matrix is
specified.
Action: Set score criterion type to 'COST' or don't specify a cost matrix.
ORA-40211: algorithm name string is invalid
Cause: Algorithm name for the model was invalid or the operation was not valid
for the algorithm.
Action: Check the algorithm name for the model and verify that the operation is
valid.
ORA-40212: invalid target data type in input data for string function
Cause: Target data type was invalid.
Action: Classification function accepts CHAR,VARCHAR2, and NUMBER targets.
Regression function accepts NUMBER targets only.
ORA-40213: contradictory values for settings: string, string
Cause: The settings values were not compatible.
Action: Check the documentation and change the setting value(s).
ORA-40214: duplicate setting: string
Cause: Duplicate setting in the settings table.
Action: Remove the duplicate setting from the settings table.
ORA-40215: model string is incompatible with current operation
Cause: The current operation was not supported for the mining function the
model corresponds to.
Action: Provide the model name suitable for current operation.
ORA-40216: feature not supported
Cause: The feature was not supported in the API.
Action: Modify the code to avoid usage of the feature.
ORA-40217: priors table mismatched with training data
Cause: The entries in the priors table do not correspond to the targets in the
training data.
ORA-40001 to ORA-40556 22-7
Action: Verify the entries in the priors table.
ORA-40218: Both priors table and weights table are specified
Cause: Both a priors table and a weights table are specified for SVM model build.
Action: Priors table is the old (pre 11g) mechanism for specifying class weights,
and class weights table is the new (and correct) way to specify class weights.
Remove the priors table entry from the settings table (after transferring class
weight settings, if appropriate). Going forward, priors table will be valid only for
NB models. Use class weights for SVM.
ORA-40219: apply result table string is incompatible with current operation
Cause: The current operation was not allowed for the apply result table supplied.
Action: Make sure the operation being performed is valid for the mining function
used to build the model (using which the apply result table was created).
ORA-40220: maximum number of attributes exceeded
Cause: The data had too many attributes.
Action: Reduce the dimensionality of the data.
ORA-40221: maximum target cardinality exceeded
Cause: The target cardinality of the training data was too high.
Action: Reduce the target cardinality.
ORA-40222: data mining model export failed, job name=string, error=string
Cause: The model export job failed.
Action: Check export job settings as required by DataPump.
ORA-40223: data mining model import failed, job name=string, error=string
Cause: The model import job failed.
Action: Check import job settings as required by DataPump.
ORA-40224: transactional input - no matching id for value column string
Cause: The training data is transactional - and a value column is specified without
a matching id specification.
Action: Specify a valid id column name as input
ORA-40225: model is currently in use by another process
Cause: The model is currently in use by another process.
Action: Retry if necessary.
ORA-40226: model upgrade/downgrade must be performed by SYS
Cause: Upgrade/Downgrade routines are being invoked by a user with
insufficient privilieges.
Action: Run the routines as SYS during migration.
ORA-40227: invalid transformation attribute
Cause: Transformation list provided to CREATE_MODEL has duplicate or NULL
attributes. Case ID or target attribute has attribute_subname that is not NULL.
Attribute provided to ALTER_REVERSE_EXPRESSION does not exist in the
model.
Action: Remove NULLs and duplicates and fix case ID and target attributes or
provide a valid attribute for a given model.
22-8 Oracle Database Error Messages
ORA-40228: scoring cost matrix already exists
Cause: The model already has a scoring cost matrix.
Action: To add a new scoring cost matrix the existing one should be removed
first.
ORA-40229: scoring cost matrix not found
Cause: The model does not have a scoring cost matrix.
Action: To remove a scoring cost matrix the model should have one.
ORA-40230: invalid transformation expression
Cause: Expression has syntax or semantic errors.
Action: Provide a valid expression.
ORA-40231: transactional input incompatible with specified algorithm
Cause: Training data in transactional format is not accepted for model creation
using the specified mining algorithm.
Action: Pivot the data into 2D tabular format, or provide the transactional input
through a nested table column.
ORA-40232: transactional input - incompatible datatype for column string
Cause: The data type of the column in the input training data is not supported.
Action: Cast or change the type of the column to one of CHAR, VARCHAR,
NUMBER or FLOAT
ORA-40233: transactional input - case id should be provided with id string
Cause: The training data is transactional by virtue of presence of a and item id -
but does not have a case id specification.
Action: Specify a valid case id column name as input
ORA-40234: reverse expression incompatible with model cost matrix
Cause: A cost matrix existed for this model with actual and predicted values
which were inconsistent with the values resulting from the specified reverse
transformation.
Action: Either remove the cost matrix table and re-add it with the new actual and
predicted values, or respecify the reverse transformation to be consistent with the
existing cost matrix.
ORA-40251: no support vectors were found
Cause: The input data is non-predictive in nature, or one of the input settings is
incorrect/incompatible with respect to the input data.
Action: Provide additional data or change model setting value.
ORA-40252: no target values were found
Cause: No target values were identified during load.
Action: Validate that the target is correctly specified.
ORA-40253: no target counter examples were found
Cause: One or more of the target classes have only positive examples.
Action: Provide counter examples or remove that target class.
ORA-40254: priors cannot be specified for one-class models
Cause: Priors were specified.
ORA-40001 to ORA-40556 22-9
Action: Do NOT provide priors for one-class models.
ORA-40255: specified priors or weights table has an incorrect schema
Cause: The priors or class weights table whose name is specified in in the settings
does not have the prescribed schema. A priors table should have the schema
(target_value, prior_probability) and a class weights table should have the schema
(target_value, class_weight)
Action: Modify the schema of the input priors or class weights table to match the
ones provided above (also in the documentation).
ORA-40261: input data for model build contains negative values
Cause: The input data contains negative values, which is not acceptable for a
Non-negative Matrix Factorization model.
Action: Provide clean data for build without any negative values.
ORA-40262: NMF: number of features not between [1, string]
Cause: The number of requested features must be greater than 1, and less than the
smaller of the number of attributes and the number of cases in the dataset.
Action: Specify the desired number of features within the acceptable range.
ORA-40263: no meaningful matrix factorization found
Cause: Input data was not significantly different from 0.
Action: Check your data for problems or add a positive constant to all the
numeric attributes.
ORA-40264: number of mining attributes (string) exceeds maximum (string)
Cause: Input data was found to contain a number of mining attributes exeeding
the maximum allowed.
Action: Check the input data for categorical fields with high cardinality.
ORA-40271: no statistically significant features were found
Cause: Input data inadequate in volume and/or quality to derive statistically
significant predictors for building a data mining model.
Action: Provide a well-prepared training data set.
ORA-40272: apply rules prohibited for this model mode
Cause: Adaptive Bayes Network rules are only generated for SingleFeature ABN
models
Action: Rebuild model in SingleFeature mode and then apply with rules.
ORA-40273: invalid model type string for Adaptive Bayes Network algorithm
Cause: The valid values for the abns_model_type settings are: abns_multi_
feature, abns_single_feature, abns_naive_bayes.
Action: Use a valid value for the abns_model_type setting.
ORA-40274: the Adaptive Bayes Network algorithm is desupported
Cause: An attempt was made to score an Adaptive Bayes Network model.
Action: Drop the existing model and build a new model using a supported
classification algorithm.
ORA-40281: invalid model name
Cause: A model name is invalid or does not exist.
22-10 Oracle Database Error Messages
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.
ORA-40001 to ORA-40556 22-11
Action: Provide a model name that corresponds to a model that was built with an
appropriate cost matrix specification.
ORA-40292: confidence level must be greater than 0 and less than 1
Cause: The specified value for confidence level is out of range.
Action: Specify a value for confidence level in the range 0 < level < 1
ORA-40293: input class is invalid for the specified predictive model
Cause: The specified model is either not a classification model, or does not have
the input class label as one of its target values.
Action: Provide the correct target value (class label) or provide the appropriate
classification model with the target attribute that has the specified class label as
one of its values.
ORA-40301: invalid cost matrix specification
Cause: A valid cost matrix is not specified.
Action: Consult documentation for valid cost matrix specification.
ORA-40302: invalid classname string in cost matrix specification
Cause: Actual or predicted classname specified is not present in training data
Action: Provide valid classname(s) in cost matrix specification
ORA-40303: invalid prior probability specification
Cause: Valid prior probabilities not specified. Valid probabilities should be
between 0 and 1.
Action: Consult documentation for valid prior probability specification.
ORA-40304: invalid classname string in prior probability specification
Cause: Actual or predicted classname specified is not present in training data.
Action: Provide valid classname(s) in prior probability specification.
ORA-40305: invalid impurity metric specified
Cause: Impurity metric specified is not valid. Examples of valid metrics are
TREE_IMPURITY_GINI, TREE_IMPURITY_ENTROPY.
Action: Consult documentation for valid impurity metrics and specification.
ORA-40306: dm_nested types not supported by this algorithm
Cause: The training input to the CREATE_MODEL routine contained one or more
columns of DM_NESTED type (DM_NESTED_NUMERICALS or DM_NESTED_
CATEGORICALS). These columns are currently not supported by Orthogonal
Partitioning Clustering (O-Cluster).
Action: Remove columns of these data types from the input data source.
ORA-40307: nested attribute combined name and value too long
Cause: The data that was presented to the decision tree algorithm was too long.
The length is computed from the sum of the length of the nested attribute name
and the length of the attribute value.
Action: Reduce the length of the attribute name or reduce the length of the
categorical value (perhaps by recoding).
ORA-40321: invalid bin number, is zero or negative value
Cause: Input bin number has zero or negative values.
22-12 Oracle Database Error Messages
Action: Provide positive bin numbers starting from 1.
ORA-40322: bin number too large
Cause: Bin number is too large.
Action: Reprocess build data by choosing smaller bin numbers.
ORA-40323: Attribute string has too many distinct values (string)
Cause: Exceeded maximum number of distinct values allowed in an attribute.
Action: Bin numerical data with fewer than 1024 bins or recode categorical data
with fewer than 1024 unique values.
ORA-40324: All rows contain the same data
Cause: All rows contained the same data and could not be clustered using
k-Means with cosine distance metric.
Action: Use Euclidean distance metric.
ORA-40341: access violation on model storage object
Cause: An attempt was made to directly access/modify a schema object that
stores model metadata and content.
Action: Perform all mining operations (create,drop,alter, and select using data
mining functions) against named model objects. Contact your DBA or Oracle
Support if you suspect that an orphaned schema object.
ORA-40342: model was not correctly upgraded
Cause: An attempt was made to use a model, but the model was not correctly
upgraded to the current release. This is most likely caused by importing a model
from an old release without upgrading it, but could also be caused by a failed
database upgrade.
Action: Invoke the SYS.DMP_SYS.UPGRADE_MODELS() procedure.
ORA-40343: invalid version specified in UPGRADE_MODELS
Cause: An invalid version was specified when invoking the UPGRADE_MODELS
procedure. Valid values for the version are 10.2.0, 11.0.0, 12.0.0, and NULL.
Action: Specify a valid version for UPGRADE_MODELS.
ORA-40350: One or more models exist that cannot be downgraded
Cause: There are data mining models in the database that were created in a
release beyond the selected release for downgrade.
Action: Prior to downgrade, drop data mining models that cannot be
downgraded to the selected release.
ORA-40361: only SELECT and ALTER are valid for mining models
Cause: An attempt was made to grant or revoke an invalid privilege on a mining
model.
Action: Do not attempt to grant or revoke any privilege besides SELECT or
ALTER on mining models.
ORA-40362: invalid object string.string specified in the statement
Cause: An attempt was made to grant a privilege on an invalid object.
Action: Make sure the dependents of the object are valid before attempting // to
grant the privilege on the object.
ORA-40001 to ORA-40556 22-13
ORA-40381: Invalid field specification for: string
Cause: The derived field was incorrectly defined.
Action: Make sure the field is correctly defined in the PMML document.
ORA-40382: More than one linear regression equation in the model
Cause: More than one linear regression equation was in the model.
Action: Make sure there is only one linear regression equation in the model.
ORA-40383: No model found in PMML document
Cause: There was no model found in the PMML document.
Action: Make sure the PMML document contains a model section.
ORA-40384: Only one model allowed in PMML document
Cause: More than one model existed in the PMML document.
Action: PMML model import only supports one model per PMML document.
Make sure only one model exists in the PMML document.
ORA-40385: Target has more than two categories
Cause: The target contained more than two categories.
Action: PMML model import supports only binary logistic regression. Make sure
the target contains no more than two categories.
ORA-40386: NormContinuous must include at least two LinearNorm elements
Cause: NormContinuous included less than two LinearNorm elements.
Action: NormContinuous must include at least two LinearNorm elements. Make
sure at least two LinearNorm elements are included.
ORA-40387: Invalid interval for Discretize field: string
Cause: The intervals were incorrect.
Action: Make sure that both margins are not missing.
ORA-40388: Unsupported feature in PMML document: string
Cause: The feature was not supported by PMML model import.
Action: Please make sure to use supported features.
ORA-40389: Unsupported PMML transformation: string
Cause: The transformation was not supported.
Action: Make sure to use supported transformations.
ORA-40390: PMML DerivedField must have a unique name specified: string
Cause: A DerivedField did not reference another defined field.
Action: A DerivedField did not have a unique name specified. Make sure to
specify a unique name for each DerivedField.
ORA-40391: PMML DerivedField depends on a undefined field: string
Cause: A DerivedField may only reference other defined fields.
Action: Make sure DerivedFields reference other defined fields.
ORA-40392: PMML regression equation references an undefined field: string
Cause: Regression equation did not reference defined fields.
22-14 Oracle Database Error Messages
Action: Regression equation may only reference defined fields. Make sure all
fields are defined.
ORA-40401: categorical attributes are not supported by this algorithm
Cause: The build data provided to the CREATE_MODEL routine contained one or
more categorical attributes of types CHAR, VARCHAR2, or DM_NESTED_
CATEGORICAL. These attributes are currently not supported for the SVD
algorithm.
Action: Remove the categorical attributes from the build data.
ORA-40402: cannot output U matrix without a valid case identifier column
Cause: A U matrix was requested, but there was no case identifier column in the
build data.
Action: Provide a non-null case identifier column in the build data.
ORA-40403: model does not have any valid features
Cause: All singular values in the SVD model were equal to zero. This can occur if
the build data contains only zeros or all build columns have constant values and
automatic data preparation is turned on.
Action: Inspect and modify the build data.
ORA-40404: approximate computation cannot be disabled for the build data
Cause: The build data had a very high number of attributes. An SVD model can
be built only by enabling approximate computation.
Action: Enable approximate computation.
ORA-40421: missing text policy name
Cause: Text policy name was missing.
Action: Provide a valid text policy name created using CTX_DDL.CREATE_
POLICY().
ORA-40422: TEXT attribute types not supported by this algorithm
Cause: The training input to the CREATE_MODEL routine contained one or more
attributes of TEXT type. These attributes are currently not supported by
Orthogonal Partitioning Clustering (O-Cluster).
Action: Remove attributes of these types from the input data source.
ORA-40441: JSON syntax error
Cause: The provided JavaScript Object Notation (JSON) data had invalid syntax
and could not be parsed.
Action: Provide JSON data with the correct syntax.
ORA-40442: JSON path expression syntax error
Cause: The provided JavaScript Object Notation (JSON) path expression had an
invalid syntax and could not be parsed.
Action: Provide JSON path expression with the correct syntax.
ORA-40443: unsupported JSON path expression
Cause: The provided JavaScript Object Notation (JSON) path expression
contained unsupported features.
Action: Remove unsupported features from JSON path expression.
ORA-40001 to ORA-40556 22-15
ORA-40444: JSON processing error
Cause: The requested JavaScript Object Notation (JSON) operation failed.
Action: Make sure the JSON operation is invoked correctly.
ORA-40445: unsupported JSON operation
Cause: The requested JavaScript Object Notation (JSON) operation is not
supported.
Action: None
ORA-40446: expecting keyword STREAM
Cause: The JavaScript Object Notation (JSON) operator expected the keyword
STREAM.
Action: Add the keyword STREAM to the JSON operator.
ORA-40447: expecting PASSING clause
Cause: The JavaScript Object Notation (JSON) operator expected a PASSING
clause.
Action: Add a PASSING caluse to the JSON operator.
ORA-40448: expecting RETURNING clause
Cause: The JavaScript Object Notation (JSON) operator expected a RETURNING
clause.
Action: Add a RETURNING clause to the JSON operator.
ORA-40449: invalid data type for return value
Cause: The provided data type for the return value was invalid or unsupported.
Action: Provide a supported return value.
ORA-40450: invalid ON ERROR clause
Cause: The provided ON ERROR clause was invalid.
Action: Provide a valid ON ERROR clause.
ORA-40451: invalid default value provided
Cause: The provided default value was not allowed here.
Action: Provide a valid default value.
ORA-40452: default value not matching type defined in RETURNING clause
Cause: The provided default value did not match the type defined in
RETURNING clause.
Action: Make sure that the default value and RETURNING clause are of the same
type.
ORA-40453: JSON operator syntax error
Cause: The provided JavaScript Object Notation (JSON) operator had invalid
syntax.
Action: Provide JSON operator with correct syntax.
ORA-40454: path expression not a literal
Cause: The provided path expression was not a literal (a constant).
Action: Provide a constant path expression.
ORA-40455: default value not a literal
22-16 Oracle Database Error Messages
Cause: The provided default value was not a literal (a constant).
Action: Provide a constant default value.
ORA-40456: JSON_VALUE evaluated to non-scalar value
Cause: The provided JavaScript Object Notation (JSON) path expression selected
a non-scalar value.
Action: Correct the JSON path expression or use JSON_QUERY.
ORA-40457: JSON path expression contained an invalid array index
Cause: The provided JavaScript Object Notation (JSON) path expression
contained an invalid array index.
Action: Provide array index greater 0. The first element in the array has the index
1.
ORA-40458: JSON_EXISTS used outside predicate
Cause: The operator JSON_EXISTS was used outside a predicate.
Action: Use JSON_EXISTS inside a preciate, for instance by embedding it inside a
CASE expression.
ORA-40459: output value too large (actual: string, maximum: string)
Cause: The provided JavaScript Object Notation (JSON) operator generated a
result which exceeds the maximum length specified in the RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or
use a CLOB/BLOB in the RETURNING clause.
ORA-40460: default value too large
Cause: The provided default value exceed the maximum length specified in the
RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or
reduce the length of the default value.
ORA-40461: Unsupported character set
Cause: The provided JavaScript Object Notation (JSON) operator does not
supported the current database character set.
Action: Chose a different database character set, for instance AL32UTF8,
AL16UTF16, or a single byte character set.
ORA-40462: JSON_VALUE evaluated to no value
Cause: The provided JavaScript Object Notation (JSON) path expression did not
select a value.
Action: Correct the JSON path expression.
ORA-40463: JSON path expression contained an invalid variable name
Cause: The provided JavaScript Object Notation (JSON) path expression
contained a variable name that is not used in the PASSING clause.
Action: Make sure that the variable names in the path expression and PASSING
clause match.
ORA-40464: JSON PASSING clause contained duplicate variable names
Cause: The provided JavaScript Object Notation (JSON) PASSING clause
contained non-unique variable names.
Action: Rename the variables in the PASSING clause.
ORA-40001 to ORA-40556 22-17
ORA-40465: JSON PASSING clause contained too many unnamed parameters
Cause: The provided JavaScript Object Notation (JSON) PASSING clause
contained too many unnamed parameters.
Action: Assign names to the parameters provided in the PASSING clause.
ORA-40466: Invalid parameter in IS [NOT] JSON predicate
Cause: The IS [NOT] JSON predicate containes an invalid parameter.
Action: Remove or correct the parameter.
ORA-40467: JSON_TEXTCONTAINS() cannot be evaluated without JavaScript
Object Notation (JSON) index
Cause: There was no JSON-enabled context index available.
Action: Create a JSON-enabled context index.
ORA-40468: first input parameter to JSON_TEXTCONTAINS() must be a column
Cause: The first input parameter to JSON_TEXTCONTAINS() was not a column.
Action: Pass a column to the first input parameter to JSON_TEXTCONTAINS().
ORA-40469: JSON path expression in JSON_TEXTCONTAINS() is invalid
Cause: A predicate or array position was used in JavaScript Object
Notation(JSON) path expression.
Action: Do not use a predicate or array position in a JSON path expression.
ORA-40470: JSON_VALUE evaluated to multiple values
Cause: The provided JavaScript Object Notation (JSON) path expression selected
more than one value.
Action: Correct the JSON path expression or use JSON_QUERY.
ORA-40471: selected value not JSON array or object
Cause: The selected value was not a JavaScript Object Notation (JSON) value.
(object or array)
Action: Use CAST AS ARRAY to return this value.
ORA-40472: invalid escape in JSON data
Cause: The provided JavaScript Object Notation (JSON) data had an invalid
escape sequence.
Action: Provide JSON data with corrected escape sequence.
ORA-40473: duplicate key names in JSON object
Cause: The provided JavaScript Object Notation (JSON) data had duplicate key
names in one object.
Action: Provide JSON data with unique key names in each JSON object.
ORA-40474: invalid UTF-8 byte sequence in JSON data
Cause: The provided JavaScript Object Notation (JSON) data had an invalid
UTF-8 byte sequence.
Action: Provide JSON data with corrected UTF-8 byte sequence or escape the
characters.
ORA-40475: JSON data nested too many levels
Cause: The provided JavaScript Object Notation (JSON) data had too many levels
of nesting.
22-18 Oracle Database Error Messages
Action: Provide JSON data with fewer levels of nesting.
ORA-40476: JSON key too long
Cause: The provided JavaScript Object Notation (JSON) data had a key which
exceeds the maximum length.
Action: Provide JSON data with shorter key names.
ORA-40477: internal JSON error
Cause: There was an internal error in the JavaScript Object Notation (JSON)
processing layer.
Action: None
ORA-40478: output value too large (maximum: string)
Cause: The provided JavaScript Object Notation (JSON) operator generated a
result which exceeds the maximum length specified in the RETURN clause.
Action: Increase the maximum size of the data type in the RETURNING clause or
use a CLOB or BLOB in the RETURNING clause.
ORA-40479: internal JSON serializer error
Cause: There was an internal error in the JavaScript Object Notation (JSON)
serializer).
Action: None
ORA-40480: result cannot be returned without array wrapper
Cause: The JavaScript Object Notation (JSON) path expressions selected a value
that can only be returned inside an array.
Action: Add WITH ARRAY WRAPPER to the JSON function.
ORA-40481: ASCII or PRETTY not supported for non-textual return data type
Cause: An attempt was made to pretty print or escape non-ASCII characters for a
non-textual output of a JSON operation.
Action: Change return data type to VARCHAR2 or CLOB or remove the PRETTY
or ASCII serialization option.
ORA-40482: JSON_TEXTCONTAINS() used outside predicate of WHERE clause
Cause: JSON_TEXTCONTAINS() was used outside of the predicate of a WHERE
clause.
Action: Use JSON_TEXTCONTAINS() inside a preciate of a WHERE clause.
ORA-40483: incorrect search string to JSON_TEXTCONTAINS()
Cause: An incorrect search string to JSON_TEXTCONTAINS() was used.
Action: The search string to JSON_TEXTCONTAINS() needs to be a non-zero
length compile time constant.
ORA-40484: invalid data type for JSON_TABLE column
Cause: A column in the provided JSON_TABLE had an unsupported data type.
Action: Provide a supported data type.
ORA-40485: keyword PRETTY not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty
printed.
ORA-40001 to ORA-40556 22-19
Action: Change column semantics to JSON_QUERY or remove the keyword
PRETTY.
ORA-40486: array wrapper not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not have an
array wrapper.
Action: Change column semantics to JSON_QUERY or remove the array wrapper.
ORA-40487: invalid usage of keyword EXISTS
Cause: A JSON_TABLE column with JSON_EXISTS semantics had invalid
parameters.
Action: Remove the invalid keywords.
ORA-40488: invalid ON ERROR clause for column semantics
Cause: An ON ERROR clause was provided that was not valid for the selected
column semantics.
Action: Change or remove the ON ERROR clause or change the column
semantics.
ORA-40489: keyword ASCII not valid for this column
Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty
printed.
Action: Change column semantics to JSON_QUERY or remove keyword ASCII.
ORA-40490: COLUMNS clause required
Cause: The provided JSON_TABLE row source requires a COLUMNS clause.
Action: Provide a COLUMNS clause.
ORA-40491: invalid input data type for JSON_TABLE
Cause: The provided input to JSON_TABLE has an unsupported data type.
Action: Provide a (N)VARCHAR2, (N)CLOB, RAW, BLOB or BFILE input.
ORA-40492: invalid column definition in JSON_TABLE
Cause: A column definition inside JSON_TABLE was invalid.
Action: Correct the column definition.
ORA-40493: invalid option or parameter in JSON_TABLE
Cause: The provided JSON_TABLE definition contained one or more invalid
options or parameters.
Action: Correct the JSON_TABLE definition.
ORA-40494: error during execution of JSON_TABLE
Cause: The provided JSON_TABLE definition could not be evaluated.
Action: Correct the JSON_TABLE definition.
ORA-40495: internal error in JSON_TABLE
Cause: The provided JSON_TABLE definition could not be evaluated.
Action: Contact Oracle Support Services.
ORA-40497: only one ordinality column permitted
Cause: The provided JSON_TABLE definition contained more than one ordinality
column.
22-20 Oracle Database Error Messages
Action: Remove the ordinality column or columns from the JSON_TABLE
definition.
ORA-40498: binary format requested for non-binary data type
Cause: The provided JSON format was binary but the input data type was not
binary.
Action: Either change the format clause or use an input of binary data type.
ORA-40499: no format defined for binary data type
Cause: The provided JSON input was of binary type but a format was not
defined.
Action: Define a format for binary input.
ORA-40501: cannot open an encrypted log file
Cause: An attempt was made to open a log file that has been encrypted for
storage and management by the Recovery Appliance. Only the processes involved
in shipping such a log to or from the Recovery Appliance can open the log.
Action: Allow the Recovery Appliance to manage the log file.
ORA-40551: internal BSON/JSON conversion error [string]
Cause: BSON/JSON conversion failed with internal error.
Action: Contact Oracle Support Services.
ORA-40552: invalid data type
Cause: The BSON/JSON converter was invoked with an invalid data type.
Action: Ensure that both the input and output is of data type BLOB.
ORA-40553: path expression with predicates not supported in this operation
Cause: A path expression with predicates was specified in a JavaScript Object
Notation (JSON) operation that does not support predicates.
Action: Only JSON_EXISTS supports predicates.
ORA-40554: invalid input data type in PASSING clause
Cause: The specified PASSING clause had an unsupported data type.
Action: Use a supported data type in the PASSING clause.
ORA-40555: incorrect PASSING clause
Cause: The specified PASSING clause was invalid.
Action: Specify a valid passing clause.
ORA-40556: unsupported chaining of JSON_TABLE
Cause: The specified JSON_TABLES were chained.
Action: Use the NESTED PATH syntax for JSON_TABLE.
ORA-41001: session id list not specified
Cause: An attempt to migrate was made, which failed because the session id list
specified was null.
Action: Check the session id list, and try again with a valid value.
ORA-41002: destination instance not specified
Cause: An attempt to migrate was made, which failed because the destination
instance specified was null.
Action: Check the destination instance , and try again with a valid value.
ORA-41003: client id not specified
Cause: An attempt to migrate was made, which failed because the client id
specified was null.
Action: Check the client id, and try again with a valid value.
ORA-41004: percentage not specified
Cause: An attempt to migrate was made, which failed because the percentage
specified was null.
Action: Check the percentage, and try again with a valid value.
ORA-41005: session id list not specified
Cause: An attempt to cancel migration was made, which failed because the
session id list specified was null.
Action: Check the session id list, and try again with a valid value.
ORA-41006: session id not specified
Cause: An attempt to get migration status was made, which failed because the
session id specified was null.
Action: Check the session id, and try again with a valid value.
ORA-41007: sid field is null
Cause: A session id instance passed into a dbms_tsm procedure or function had a
null sid field.
Action: Check the session id, and try again with a valid value.
ORA-41008: serial# field is null
Cause: A session id instance passed into a dbms_tsm procedure or function had a
null serial# field.
Action: Check the session id, and try again with a valid value.
23-2 Oracle Database Error Messages
ORA-41009: Session with session number string, serial number string does not exist
Cause: An attempt to migrate was made, which failed because of invalid session
number and/or serial number.
Action: Check the session number and serial number and try again.
ORA-41010: No more memory to hold connection state information
Cause: An attempt to reference more connections than configured
Action: Check the connection information and try again.
ORA-41011: Operation failed for session id string, serial number string
Cause: An migration related operation failed because of contention between
sessions.
Action: Check the additional error codes for more information, and retry
operation later.
ORA-41012: Migration not allowed for session number string, serial number string
Cause: An attempt to migrate was made, which failed because the session
specified cannot be migrated.
Action: Check the session number and serial number and try again.
ORA-41013: instance name not specified
Cause: An attempt to migrate was made, which failed because the instance name
specified was null.
Action: Check the instance name, and try again with a valid value.
ORA-41014: Session number string, serial number string currently being migrated
Cause: An attempt to migrate was made, which failed because the session
specified is currently being migrated.
Action: Check the session number and serial number and try again.
ORA-41015: destination connect string not specified
Cause: A migration attempt was made, which failed because the connect string
specified was null.
Action: Check the connect string and try again.
ORA-41016: Session recreation failed
Cause: Session recreation failed at the destination instance.
Action: Check session state and try migration again
ORA-41017: Session prepare failed for session number string, serial number string
Cause: A migration attempt was made, which failed because session prepare
failed.
Action: Retry migration again after checking all arguments.
ORA-41019: Session begin at the destination instance failed
Cause: Session begin failed at the destination instance because the shadow
connection could not be established.
Action: Check the connect string and try beginning the session again.
ORA-41020: invalid value "string" specified for parameter "string"
Cause: An invalid value was specified for the the given parameter.
ORA-41001 to ORA-42804 23-3
Action: Correct the value being specified for the parameter.
ORA-41021: OCI error during transparent session migration
Cause: An OCI operation failed during transparent session migration.
Action: Check the OCI error signalled, and take corrective action.
ORA-41022: instance name not specified
Cause: An attempt to recover after instance death was made, which failed because
the instance name specified was null.
Action: Check the instance name, and try again with a valid value.
ORA-41023: death time not specified
Cause: An attempt to recover after instance death was made, which failed because
the death time specified was null.
Action: Check the death time, and try again with a valid value.
ORA-41024: Cursor needs to be parsed again
Cause: An SQL operation failed because the cursor state was lost.
Action: Reissue all operations starting from parse.
ORA-41025: sid field string is invalid
Cause: A session id instance passed into a dbms_tsm procedure or function had
an invalid sid field.
Action: Check the session id, and try again with a valid value.
ORA-41026: serial# field string is invalid
Cause: A session id instance passed into a dbms_tsm procedure or function had
an invalid serial# field.
Action: Check the serial#, and try again with a valid value.
ORA-41027: Error status string during OCI operation at string
Cause: An OCI operation failed during transparent session migration.
Action: Check the OCI error signalled, and take corrective action.
ORA-41028: Session id not specified
Cause: An attempt to migrate was made, which failed during migration because
the session id specified by the client was null.
Action: Check the session id, and try again with a valid value.
ORA-41029: Destination session id not specified for sid string serial# string
Cause: An attempt to migrate was made, which failed during migration because
the destination session id specified by the client was null.
Action: Check the session id, and try again with a valid value.
ORA-41030: Session id not specified
Cause: An attempt to migrate was made, which failed during migration because
the session id specified by the client was null.
Action: Check the session id, and try again with a valid value.
ORA-41031: Destination session key not specified for sid string serial# string
Cause: An attempt to migrate was made, which failed during migration because
the destination session key specified by the client was null.
23-4 Oracle Database Error Messages
Action: Check the session id, and try again with a valid value.
ORA-41100: Oracle Cluster Registry operation failed with event string.
Cause: The Portable Clusterware/Oracle Cluster Registry stack returned an error.
Action: Check if the Portable Clusterware stack is properly brought up.
ORA-41101: The database: string has already been designated as Cluster Director.
Cause: An attempt was made to designate multiple databases as the Cluster
Director.
Action: Undesignate the existing Cluster Director before Designating a new one.
ORA-41102: No database has currently been designated as Cluster Director.
Cause: An attempt was made to query/undesignate a Cluster Director when no
database has been designated as Cluster Director.
Action: None
ORA-41103: Only the designated Cluster Director: string can undesignate itself.
Cause: An attempt was made to undesignate the current Cluster Director by a
database that is not the Cluster Director.
Action: Login to the currently designated Cluster Director to perform the
undesignation.
ORA-41104: The database: string is the Cluster Director.
Cause: An attempt was made to control the Cluster Director on a database that is
not the Cluster Director.
Action: Log in to the currently designated Cluster Director to perform the control
operation.
ORA-41105: The Cluster Director is not stopped.
Cause: An attempt was made to control the Cluster Director before the Cluster
Director was stopped.
Action: Use dbms_cluster_director.stop to stop the Cluster Director and retry the
control operation.
ORA-41106: invalid argument string: value is null
Cause: An attempt to read the scan hostname or port failed
Action: Verify pcw is running and scan is configured. Run grdcscan read_config
to verify or grdcscan set_config host:port to set scan name and port.
ORA-41107: invalid argument: service string cannot be found
Cause: The program attempted to access a nonexistent or deleted service.
Action: Check to make sure the service has been properly created.
ORA-41108: Posting system alert with reason_id string failed with code [string]
[string]
Cause: Internal Error: An attempt to post a system alert failed.
Action: If this condition repeats, please contact Oracle Support.
ORA-41109: Updating system alert with reason_id string failed; previous alert not
found
Cause: System Error: An attempt to update a system alert failed. The alert was
improperly cleared from WRI$_ALERT_OUTSTANDING.
ORA-41001 to ORA-42804 23-5
Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition
repeats, please contact Oracle Support.
ORA-41110: The Director has blocked this instance. Cannot start [string]
Cause: An attempt to start services on an instance that will be shutdown
Action: Start the services on another available instance
ORA-41201: Session state not capturable due to reason (string, string)
Cause: Session state capture was initiated when session state could not be
captured.
Action: Check session state status and make sure session state can be captured.
ORA-41202: Session state capture or restore failed
Cause: Capture or restore operation failed.
Action: Check session state status and failure reason for details.
ORA-41203: Invalid session state operation
Cause: Invalid session state operation was issued.
Action: Check if session status was valid for the current operation.
ORA-41204: Session capture in progress
Cause: Session state capture was initiated and could not perform the requested
operation.
Action: Wait for the current capture to complete or abort it.
ORA-41205: Invalid parameter for session state capture or restore
Cause: Invalid parameter was passed to session state capture or restore interface.
Action: Correct the invalid parameter(s).
ORA-41206: Session capture or restore internal error KPCSFR-string
Cause: Internal operation error was encountered.
Action: Turn on related trace for details and report it as a bug.
ORA-41207: Cannot restore session state due to reason (string, string)
Cause: Session state restore was initiated when session was not ready for state
restore.
Action: Restore session state immediately after logging into a session or perform
necessary operations to make the session ready for restore; for example, commit
current transaction, or close BFiles.
ORA-41208: OCI error during session state capture and restore
Cause: An OCI operation failed during an internal operation of session state
capture and restore.
Action: Check the OCI error signaled and take corrective action.
ORA-41209: OCI operation failed at string due to ORA-string
Cause: An OCI operation failed during an internal operation of session state
capture and restore.
Action: Check the OCI error signaled and take corrective action.
ORA-41210: Failed to resolve session state directory object
Cause: Session state directory object passed to capture or restore was incorrect.
23-6 Oracle Database Error Messages
Action: Verify session state directory object and retry.
ORA-41211: Failed to insert capture or restore record
Cause: An error occurred while capture or restore record was being stored into
the database.
Action: Check the error signaled and take corrective action.
ORA-41251: Failed to restore session state from a file (error code number)
Cause: Session state file may be corrupted.
Action: Ensure that the file is a session state file.
ORA-41252: Failed to switch to new session in SSCR
Cause: This is the generic internal error number for the SSCR exceptions. This
indicates that the SSCR has encountered an exceptional condition.
Action: Report as a bug.
ORA-41253: Failed to access session state file
Cause: An error was encountered while reading from or writing to session state
capture file.
Action: Check the error stack for the actual error number and turn on tracing if
necessary.
ORA-41254: Invalid session state file: string
Cause: An invalid session state file was used in session state restore operation.
Action: Check if the session state file is a valid file created by session capture.
ORA-41255: Package not supported: string
Cause: The specified package is not supported.
Action: Do not call the package functions and procedures.
ORA-41300: File driver is not initialized
Cause: An attempt was made to operate on the uninitialized file driver.
Action: Initialize the file driver using the OCIServerAttach function.
ORA-41301: failed to write data to file
Cause: You may not have sufficient privileges or quotas for this action.
Action: Ensure that you have sufficient privileges and quotas for this action.
ORA-41302: failed to read data from file
Cause: The file may not exist or you do not have privileges for this action.
Action: Ensure that the file exists and that you have sufficient privileges for this
action.
ORA-41303: Received partial data from file
Cause: This is the generic internal error number for file driver exceptions. This
indicated that file driver encountered an exception condition.
Action: Report as a bug.
ORA-41304: Failed to connect to file driver
Cause: The connect string may be incorrect.
Action: Ensure that the connect string is correct.
ORA-41001 to ORA-42804 23-7
ORA-41305: Failed to open file
Cause: You may not have sufficient privileges for this action.
Action: Ensure that the file exists and that you have sufficient privileges for this
action.
ORA-41400: Bind character set (string) does not match database character set (string)
Cause: In this recursive OCI call, the bind character set was different from the
current database character set. This is usually caused by database character set
change.
Action: Be sure to obtain bind data in database character set and do rebind in the
current environment.
ORA-41401: Define character set (string) does not match database character set
(string)
Cause: In this recursive OCI call, the define character set was different from the
current database character set. This is usually caused by database character set
change.
Action: Be sure to do redefine in the current environment.
ORA-41402: SCNs not valid after failover; failover cannot continue
Cause: The Oracle server process failed and replay was initiated.
Action: Resubmit the request.
ORA-41403: failed over to older server; failover cannot continue (string, string,
string)
Cause: Failover replay was enabled for a service in which some standby databases
were older than the original server and could not replay work from the original
server.
Action: Disable replay on the service, or upgrade your databases to compatible
versions.
ORA-41404: invalid replay context
Cause: Application continuity protocol was violated.
Action: Contact Oracle Support Services.
ORA-41405: Failed over to older server; failover cannot continue (string, string).
Cause: Failover replay was enabled for a service in which some standby databases
were older than the original server and could not replay work from the original
server.
Action: Disable replay on the service, or upgrade your databases to compatible
versions.
ORA-41407: SQL command not supported for replay; replay disabled
Cause: Application replay encountered a command that was not supported for
replay, and so replay was disabled.
Action: Use a service without replay for this operation.
ORA-41408: embedded COMMIT in last call; failover cannot continue
Cause: The Oracle server process failed after committing a transaction but
COMMIT was embedded in a stored procedure and it cannot be guaranteed that
the stored procedure finished. Failover cannot continue.
Action: User may resubmit request.
23-8 Oracle Database Error Messages
ORA-41409: cannot replay committed transaction; failover cannot continue
Cause: The Oracle server process failed after committing a transaction in the
current request. The transaction cannot be replayed, so the current request cannot
be replayed and session state cannot be restored. Failover cannot continue.
Action: User may resubmit request.
ORA-41410: call committed a transaction and started a new transaction; failover
cannot continue
Cause: The Oracle server process failed after committing a transaction in the
current request. One call that committed a transaction, and thus cannot be
replayed, also started a new transaction. Since that call cannot be replayed, the
new transaction cannot be restored. Failover cannot continue.
Action: Resubmit, and consider restructuring application to not start a transaction
in the same call after committing a transaction.
ORA-41411: too many round trips in request; replay disabled
Cause: The Oracle server process failed after executing a request with more than
65535 round trips, so replay of the request is not possible.
Action: Resubmit, and consider partitioning application calls into more requests
with fewer round trips.
ORA-41412: results changed during replay; failover cannot continue
Cause: The Oracle server process failed and replay was initiated. However, results
of the replay differed from the original execution. Failover cannot continue.
Action: User may resubmit request.
ORA-41413: too much data in call capture; replay disabled
Cause: The Oracle server process failed after executing a request with a
complicated call whose capture had too much data, therefore, replaying of the
request was not possible.
Action: Resubmit and partition the application calls into more requests with
fewer round trips.
ORA-41414: could not allocate memory for call capture; replay disabled
Cause: The Oracle server process failed after executing a request with a memory
allocation failure during capture, therefore, replaying of the request was not
possible.
Action: Resubmit and partition the application calls into more requests with
fewer round trips.
ORA-41415: duplicate or conflicting KEEP or NOKEEP specifications
Cause: Duplicate KEEP or NOKEEP was specified, or both KEEP and NOKEEP
were specified.
Action: Remove the duplicate or conflicting specification.
ORA-41417: invalid use of DBMS_APP_CONT_PRVT: [string] [string]
[mode=string] [string] [string] [string] [string] [string]
Cause: Application continuity protocol was violated.
Action: Contact Oracle Support Services.
ORA-41418: Replay context is corrupt. Reason: [string], [string], [string], [string]
Cause: The replay context was not valid.
ORA-41001 to ORA-42804 23-9
Action: Check your network configuration and hardware.
ORA-41601: invalid property for the rule class
Cause: An invalid property was specified for the rule class.
Action: Correct the rule class properties and try again.
ORA-41602: insufficient privileges
Cause: The user does not have required privileges on the object.
Action: Obtain the required privileges and try again.
ORA-41603: invalid privilege type
Cause: An attempt was made to grant an invalid privilege on a rule class.
Action: Correct the privilege name and try again.
ORA-41604: cannot revoke a privilege that was not granted
Cause: An attempt was made to revoke a privilege that was never granted.
Action: None
ORA-41605: schema extended name not allowed: string
Cause: An attempt was made to specify a schema extended name for an event
structure, a rule class, or an action call-back procedure.
Action: Specify the object name with out a schema extension.
ORA-41606: rule class name already used by an existing object
Cause: An attempt was made to create a rule class with a name that is already
used by an existing object.
Action: Specify a different name for the rule class and try again.
ORA-41607: rule class creation failed with string
Cause: rule class creation failed with a recursive error.
Action: Correct the rule class specification and try again.
ORA-41608: rule class does not exist
Cause: An attempt was made to access a rule class that does not exist or is not
accessible.
Action: Correct the rule class name and try again.
ORA-41609: invalid name for the rule class
Cause: An invalid name was specified for the rule class.
Action: Correct the rule class name and try again.
ORA-41610: callback procedure name already used for an existing object
Cause: An attempt was made to create a callback procedure with a name that is
already used for an existing object.
Action: Choose another name for the callback procedure.
ORA-41611: rule identifier "string" not unique in the rule class
Cause: An attempt was made to use a duplicate rule identifier.
Action: Choose a unique identifier for the rule and try again.
ORA-41612: scalar values expected for action preferences
Cause: Incorrect values were specified for the action preferences.
23-10 Oracle Database Error Messages
Action: Correct the action preferences values and try again.
ORA-41613: invalid action preference for rule class: string
Cause: An attempt was made to use an invalid action preference.
Action: Correct the input and try again.
ORA-41614: missing action preference value
Cause: Values for one or more action preferences were not specified.
Action: Specify values for all relevant action preferences.
ORA-41615: too many values in action preference list
Cause: Too many entries were specified in the action preference values list. The
action preference values list should not have more entries than the action
preference names list.
Action: Correct the input and try again.
ORA-41616: rule class's action callback procedure may have errors
Cause: The operation failed because the action callback procedure associated with
the rule class has compilation errors.
Action: Recompile the action callback procedure and try the operation again.
ORA-41617: action preference name "string" collides with an event attribute name
Cause: An attempt was made to create an action preference with the same name
as an attribute in the event structure.
Action: Choose a different name for action preference and try again.
ORA-41618: specified rule does not exist
Cause: Invalid rule identifier was used to operate on a rule definition.
Action: Use a valid rule identifier.
ORA-41619: rule manager feature currently not supported
Cause: An attempt was made to use a rule manager feature that is currently not
supported.
Action: No action necessary. This is an informational message only.
ORA-41620: invalid ordering property for the rule class
Cause: An attempt was made to specify an invalid ordering property for the rule
class.
Action: Make sure that the attributes listed in the ordering property are all part of
the rule class/event structure definition with appropriate extended names.
ORA-41621: error in ordering property :string
Cause: An attempt was made to specify an invalid ordering property for the rule
class.
Action: Make sure that the attributes listed in the ordering property are all part of
the rule class/event structure definition with appropriate extended names.
ORA-41622: invalid primitive event object in rule class properties : string
Cause: In the rule class properties, the name used for one or the primitive event
objects was not found in the corresponding composite event structure.
Action: Correct the name of the primitive event object in the rule class properties
and try again.
ORA-41001 to ORA-42804 23-11
ORA-41623: conflicting values for autocommit and duration properties
Cause: An attempt was made to create a rule class with autocommit enabled
when the duration of events is set to TRANSACTION.
Action: Turn autocommit off or choose a different duration policy.
ORA-41624: invalid duration policy for primitive object in a composite event
Cause: An attempt was made to specify a SESSION or TRANSACTION duration
policy for the primitive objects.
Action: Correct the rule class properties and try again.
ORA-41625: event structure string does not exist
Cause: The object type that represents the event structure was not created in the
user's schema.
Action: Create the object type with the event structure's name and try again.
ORA-41626: invalid XML element "string" in rule class properties
Cause: An invalid XML element was used in the properties specification for the
rule class.
Action: Use the correct (case-sensitive) tags in the properties.
ORA-41627: event structure object type in inconsistent state
Cause: The object type specified for the event structure was in an inconsistent
state.
Action: Fix the object type and try again.
ORA-41628: invalid usage of "string" attribute in "string" element
Cause: An invalid or unsupported XML attribute was used in the rule class
properties.
Action: Use the correct (case-sensitive) tags in the properties.
ORA-41629: event structure for simple events cannot be reused for composite
events
Cause: An attempt was made to reuse an object type (event structure) for
composite events when it is already configured for simple events.
Action: Drop the attribute set associated with the object and try again.
ORA-41630: invalid value for "string" attribute in the rule class properties
Cause: An invalid value was specified for an attribute in the rule class properties.
Action: Correct the value and try again.
ORA-41631: invalid text node or child element for "string" element in properties
Cause: An attempt was made to specify a child element or a text node in invalid
position in the rule class properties specification.
Action: Correct the rule class properties and try again.
ORA-41632: invalid value for the "string" attribute
Cause: An attempt was made to assign an invalid value for an attribute in the rule
class properties.
Action: See the documentation.
ORA-41633: specified rule class configuration not supported: "string"
23-12 Oracle Database Error Messages
Cause: An attempt was made to use an unsupported configuration for the rule
class.
Action: Remove the specified tag in the properties and try again.
ORA-41634: invalid duration specification in rule properties: "string"
Cause: Invalid value was specified for the duration attribute in the rule class
properties.
Action: Correct the value and try again.
ORA-41635: invalid unit of time used in duration specification
Cause: An attempt was made to use an invalid unit of time for the rule class's
duration specification. Valid units are : minutes, hours, and days.
Action: Correct the duration specification and try again.
ORA-41636: invalid duration specification at the primitive event level
Cause: An attempt was made to specify a duration policy for the primitive events
when the composite event was configured with TRANSACTION or SESSION
duration policy.
Action: Correct the rule class properties and try again.
ORA-41637: missing primitive event name
Cause: The name attribute of the object element in the rule class properties was
not specified. This is a required value.
Action: Specify the name of the primitive event and try again.
ORA-41638: invalid attribute for "string" element in rule condition
Cause: An attempt was made to specify an invalid attribute for an XML element
in the rule condition.
Action: Correct the rule condition and try again.
ORA-41639: invalid child node in "string" element
Cause: An attempt was made to specify an invalid child element or text node for
an XML element in the rule condition.
Action: Correct the rule condition and try again.
ORA-41640: invalid element "string" in the rule condition
Cause: An attempt was made to use an invalid element or a valid element in
invalid position in the rule condition.
Action: Correct the rule condition and try again.
ORA-41641: invalid or empty rule condition
Cause: An attempt was made to specify an invalid or empty rule condition.
Action: Correct the input and try again.
ORA-41642: Missing "string" element in the rule condition
Cause: The rule condition was specified without a required element.
Action: Correct the rule condition and try again.
ORA-41643: invalid attribute for the "string" element in the rule condition
Cause: An attempt was made to specify an invalid attribute for an element in the
rule condition.
Action: Correct the rule condition and try again.
ORA-41001 to ORA-42804 23-13
ORA-41644: invalid use of "string" attribute in rule condition
Cause: An attempt was made to specify an invalid attribute for an element in the
rule condition.
Action: Correct the rule condition and try again.
ORA-41645: duplicate tag "string" in rule condition
Cause: An attempt was made to specify the same XML tag in more than one
positions within a single rule condition.
Action: Remove the duplicate reference to the tag and try again.
ORA-41646: missing "string" attribute for "string" element in the rule condition
Cause: One of the required attributes was not specified in the rule condition.
Action: Correct the rule condition and try again.
ORA-41647: negation not allowed in rule conditions with "any" semantics
Cause: An attempt was made to specify a "not" element within an "any" element
in the rule condition.
Action: Correct the rule condition and try again.
ORA-41648: invalid sequence of child elements in "string" element
Cause: An attempt was made to specify an invalid sequence of elements within a
parent element.
Action: Correct the rule condition and try again.
ORA-41649: invalid rule condition for a rule class involving composite events
Cause: An attempt was made to add an invalid rule condition to a rule set defined
for composite events.
Action: Correct the input and try again.
ORA-41650: invalid composite event structure
Cause: A composite event structure may only have attributes that are either table
aliases or of an object type that is defined in the owner's schema.
Action: Ensure that the event structure has no scalar attributes and all the
embedded types in it are defined in the owner's schema.
ORA-41651: Event structure object type has one or more dependent objects
Cause: An attempt was made to configure an object type that has one or more
dependents as a event structure. The object type cannot be modified due to the
dependent objects.
Action: Create a new object type for the event structure and try again.
ORA-41652: invalid value for the equal attribute in the rule condition
Cause: An invalid value is assigned to the equal attribute in the rule condition.
Action: Correct the input and try again.
ORA-41653: inconsistent value for the "count" attribute of the "any" element
Cause: The value specified for the "count" attribute of the "any" element is greater
than or equal to the the number of primitive events appearing in the rule
condition.
Action: Specify a smaller value for the "any" element's "count" attribute.
ORA-41654: insufficient number of primitive events for the use of "sequence"
23-14 Oracle Database Error Messages
Cause: An attempt was made to use "sequence" attribute when there is an
insufficient number of primitive events in the rule conditions.
Action: Remove the sequence specification.
ORA-41655: rule condition construct not supported: string
Cause: An attempt was made to use a rule condition construct that is not
supported in the current release.
Action: Modify the rule condition.
ORA-41656: insufficient number of child elements in "string" element.
Cause: An attempt was made to use fewer than two elements within an "and" or
"notany" element.
Action: Specify at least two elements within the parent element.
ORA-41657: rule class internal objects cannot be dropped
Cause: An attempt was made to drop an internal object that is required for a rule
class.
Action: Drop the rule class associated with this object.
ORA-41658: invalid value for the "count" attribute in the "any" element
Cause: An invalid value is assigned to the count attribute in the rule condition.
The values should be a positive integer that is smaller than the number of object
elements within the "any" element.
Action: Correct the input and try again.
ORA-41659: invalid primitive event "string" for the rule class
Cause: An attempt was made to use an invalid primitive event in a rule condition.
Action: Correct the input and try again.
ORA-41660: ordering property for the rule class is too long
Cause: An attempt was made to configure the rule class with an ordering
property that is longer than 240 characters.
Action: Correct the input and try again.
ORA-41661: the system generated rule class package has errors
Cause: An attempt was made to use a rule class configuration that was not
supported.
Action: File a bug.
ORA-41662: number of primitive events in the composite event exceeds maximum
limit
Cause: An attempt was made to create a composite event structure with more
than 32 primitive events.
Action: Use a composite event that consists of fewer primitive events.
ORA-41663: invalid use of "equal" or "sequence" attribute with a single event
Cause: An attempt was made to use "equal" or "sequence" attribute when the
"count". attribute in a rule condition with "any" semantics is set to 1.
Action: Remove the "equal" and "sequence" specifications.
ORA-41664: invalid consumption policy for the primitive event
ORA-41001 to ORA-42804 23-15
Cause: An attempt was made to use EXCLUSIVE consumption policy for a
primitive event when the composite event is configured for RULE consumption
policy.
Action: Correct the rule class properties and try again.
ORA-41665: conflicting values for duration, consumption, and autocommit policies
Cause: An attempt was made to use an EXCLUSIVE consumption policy with no
autocommit and a duration other than TRANSACTION or SESSION.
Action: Modify the rule class properties and try again. Autocommit should be set
to YES when the consumption policy is EXCLUSIVE.
ORA-41666: XML schema validation failed when validating against string
Cause: The user input has undefined element or attribute according to the
provided XML schema definition.
Action: Correct the user inputs and try again.
ORA-41667: rule class results view name already used for an existing object
Cause: An attempt was made to use a duplicate name for the rule class results
view.
Action: Use a different name for the rule class results view.
ORA-41668: invalid operation for the rule class
Cause: An attempt was made to use an invalid operation for the rule class.
Action: No action necessary. This is an informational message only.
ORA-41669: invalid list of primitive event identifiers
Cause: An attempt was made to pass an empty list of primitive event identifiers
to the CONSUME_PRIM_EVENTS API.
Action: Correct the input and try again.
ORA-41670: duplicate or invalid event name in equal specification
Cause: An attempt was made to specify a duplicate or invalid primitive event for
the rule class's equal property.
Action: Correct the input and try again.
ORA-41671: duplicate table names in the event structure with table aliases
Cause: The table used for an event structure has the same name as another table
or a primitive event type in the event structure.
Action: Use an event structure with distinct table names for table aliases.
ORA-41672: invalid rowid passed in for "string" table
Cause: An attempt was made to pass a NULL or invalid rowid for a table in the
event structure.
Action: Correct the input and try again.
ORA-41673: sequence attribute not allowed in rule conditions using table aliases
Cause: An attempt was made to use sequence attribute in a rule condition that is
defined using table aliases. Sequence usage is not permitted for the lack of
timestamp attribute.
Action: Correct the input and try again.
ORA-41674: dmlevents policy allowed only for event structures with table aliases
23-16 Oracle Database Error Messages
Cause: An attempt was made to use the dmlevents policy for an event structure
with no table alias constructs.
Action: Correct the rule class properties and try again.
ORA-41675: schema for data tables does not match that of the rule class
Cause: An attempt was made to use the dmlevents policy for a rule class that
refers to table residing in different schema. To use the dmlevents policy, the table
associated with table aliases in the event structure and the rule class should exist
in the same schema.
Action: Remove dmlevents specification from rule class properties.
ORA-41676: invalid use of dmlevents policy for primitive event
Cause: An attempt was made to use the dmlevents policy for a primitive event
defined with more than one table alias attribute.
Action: Remove the dmlevents specification from the rule class properties.
ORA-41677: DML event trigger creation failed with string
Cause: Triggers could not be created on the data table to track DML events.
Action: Remove the dmlevents specification from the rule class properties.
ORA-41678: conflicting values for the autocommit and dmlevents policies
Cause: An attempt was made to use dmlevents policy in combination with
autocommit set to YES. This combination is not allowed.
Action: Set autocommit to NO and try again.
ORA-41679: dmlevents specification only allowed with table alias attributes
Cause: An attempt was made to use the dmlevents policy for an event structure
not containing any table alias attributes.
Action: Remove the dmlevents specification from the rule class properties.
ORA-41680: Rules Manager background process string does not exist
Cause: An attempt was made to use a Scheduler process that does not exist.
Action: Execute EXFSYS.RLM$CREATE_SCHEDULER_JOBS procedure as a
privileged user.
ORA-41681: clean up of expired events failed
Cause: The background process that cleans up the expired events failed for a rule
class.
Action: Invoke EXFSYS.DBMS_RLMGR_UTL.CLEANUP_EVENTS API for the
exact nature of the problem.
ORA-41682: invalid rule class package
Cause: An attempt was made to use a rule class package with invalid signature or
permissions.
Action: Drop the rule class and recreate it.
ORA-41683: unable to lock a rule in the rule class
Cause: A rule matching the current event is locked by another session.
Action: Reissue the command after committing the other sessions.
ORA-41684: invalid value for the RLM$ENABLED column
ORA-41001 to ORA-42804 23-17
Cause: An attempt was made to insert or update a value other than 'Y' or 'N' into
the RLM$ENABLED column of a rule class table.
Action: Retry the DML statement with a value of 'Y' or 'N' for the
RLM$ENABLED column.
ORA-41685: invalid window specification for the collection element
Cause: An invalid attribute value was specified for the "windowlen" or the
"windowsize" attribute. The value specified for the "windowlen" attribute should
be a number indicating the number of days or a fraction of a day. The value
specified for the "windowsize" attribute should be an integer which indicates
number of items in the collection. The maximum value allowed for the window
specification is 64000.
Action: Correct the input and try again.
ORA-41686: use of "collection" invalid for the primitive event
Cause: An attempt was made to define a rule condition with "collection" element
when the corresponding event was not configured for collections of events.
Action: Correct the rule condition and try again.
ORA-41687: attribute "string" not allowed in the "groupby" specification
Cause: The attributes listed in the "groupby" specification in a rule condition were
not a subset of the attributes specified in the rule class properties.
Action: Correct the "groupby" specification for the rule condition and try again.
ORA-41688: invalid value for the "groupby" attribute
Cause: An invalid value was specified for the "groupby" attribute.
Action: Correct the input and try again.
ORA-41689: invalid collection specification in the rule condition
Cause: An attempt was made to insert a rule condition with invalid collection
element specification.
Action: Correct the input and try again.
ORA-41690: maximum number of grouping expressions for a rule class exceeded
Cause: An attempt was made to specify more than 32 expressions for the
"groupby" clause in rule class properties.
Action: Use fewer than 32 expressions for the "groupby" clause.
ORA-41691: invalid aggregate specification: string
Cause: The aggregate operation specified in the rule condition was invalid.
Action: Correct the input and try again.
ORA-41692: unsupported aggregate operator in the having/compute clause: string
Cause: An attempt was made to use an unsupported aggregate operator in the
having or the compute clause in the rule condition.
Action: Correct the input and try again.
ORA-41693: invalid attribute or data type for an aggregate operator: string
Cause: An attempt was made to apply an aggregate operator on an invalid
attribute or an attribute with invalid or unsupported data type in the aggregate
operator. Only NUMBER and DATE attributes are allowed in the aggregate
operators.
23-18 Oracle Database Error Messages
Action: Correct the input and try again.
ORA-41694: invalid equal specification around: string
Cause: An attempt was made to specify an invalid equal clause for a rule
condition or the rule class properties.
Action: Correct the input and try again.
ORA-41695: equal specification should have a minimum of two elements
Cause: An attempt was made to specify fewer than two elements in the equal
clause for a rule condition or the rule class properties.
Action: Correct the input and try again.
ORA-41696: invalid operator in the having clause: string
Cause: An attempt was made to use an invalid relational operator in the having
clause of the rule condition.
Action: Correct the input and try again.
ORA-41697: attribute prefix missing in aggregate specification: string
Cause: An attempt was made to specify an aggregate predicate across multiple
primitive event types with no attribute prefix.
Action: Correct the input and try again.
ORA-41698: invalid use of "string" attribute in aggregate predicate
Cause: An attempt was made to use an attribute where a literal is expected in the
aggregate predicate in the rule condition.
Action: Correct the input and try again.
ORA-41699: maximum number of aggregate operations per rule condition exceeded
Cause: An attempt was made to specify more than 5 aggregate operations in a
rule condition.
Action: Correct the input an try again.
ORA-41700: a conditions table already exists for the event structure
Cause: A table storing the primitive rule conditions was already assigned to the
event structure.
Action: No action necessary. This is an informational message only.
ORA-41701: conditions table with a rule class association cannot be truncated or
dropped
Cause: An attempt was made to truncate or drop a conditions table when one or
more rule classes are associated to it through the event structure.
Action: Drop the rule class before truncating or dropping the conditions table.
ORA-41702: invalid conditions table
Cause: An attempt was made to use an invalid conditions table.
Action: Correct the input and try again.
ORA-41703: invalid child node in "object" element with "ref" attribute
Cause: An attempt was made to use both a condition and a "ref" attribute in the
"object" element.
Action: Remove the "ref" attribute.
ORA-41001 to ORA-42804 23-19
ORA-41704: invalid condition reference: "string"
Cause: An attempt was made to use a reference to a nonexistent conditions table
or a condition.
Action: Ensure that the conditions table exists for the primitive event and the
value specified for the "ref" attribute of the "object" element is valid.
ORA-41705: conditions table cannot be dropped with DROP TABLE command
Cause: An attempt was made to drop a conditions table with a DROP TABLE
command.
Action: Use DBMS_RLMGR.DROP_CONDITIONS_TABLE instead.
ORA-41706: a condition referenced in rule conditions may not be deleted
Cause: An attempt was made to delete a condition when one or more rule
conditions refer to it.
Action: Delete the rules before deleting the conditions.
ORA-41707: unsupported construct with collection events: "string"
Cause: An attempt was made to define a collection rule condition with
unsupported constructs.
Action: Correct the input and try again.
ORA-41708: the identifier for the shared condition may not be modified
Cause: An attempt was made to update the identifier of a row stored in the
conditions table.
Action: Insert a row with the new identifier instead.
ORA-41710: invalid use of aggregate operator for a noncollection event
Cause: An attempt was made to specify an aggregate operator on an event that is
not identified as collection.
Action: Correct the input and try again.
ORA-41711: invalid attribute in the rule condition's having clause
Cause: An invalid attribute is used in the specification for the having clause of the
rule condition.
Action: Correct the input and try again.
ORA-41712: missing groupby specification for the collection "string"
Cause: An attempt was made to use a collection element with no groupby
specification in the rule condition.
Action: Correct the input and try again.
ORA-41713: invalid use of "windowlen" and "windowsize" attributes
Cause: An attempt was made to use the windowlen and windowsize attributes
within the same collection element.
Action: Correct the input and try again.
ORA-41714: invalid use of window specification with SESSION/TRANSACTION
duration
Cause: An attempt was made to use the windowlen or windowsize attributes
when the events are configured for SESSION or TRANSACTION duration.
Action: Remove the window specification and try again.
23-20 Oracle Database Error Messages
ORA-41721: invalid use of DMLEVENTS and CNFEVENTS in rule class properties
Cause: An attempt was made to specify both the DMLEVENTS and CNFEVENTS
for the same rule class.
Action: Remove either the DMLEVENTS or the CNFEVENTS specification.
ORA-41722: insufficient privileges for database change notification
Cause: An attempt was made to use CNFEVENTS property with insufficient
privileges.
Action: Grant CHANGE NOTIFICATION privilege and EXECUTE privilege on
DBMS_CHANGE_NOTIFICATION to the user and try again.
ORA-42000: invalid online redefinition column mapping for table "string"."string"
Cause: An attempt was made to change the logical structure of a materialized
view log, queue table, or a partition by specifying a non-NULL column mapping
during online redefinition.
Action: Pass a NULL column mapping parameter.
ORA-42002: partition "string" of table "string"."string" not being redefined
Cause: An attempt was made to redefine a partition which is not involved in this
redefinition.
Action: Pass a valid partition name.
ORA-42003: partition must be specified for this redefinition
Cause: A partition was involved in this redefinition but was not specified.
Action: Specify the partition involved in this redefinition.
ORA-42004: redefinition not instantiated
Cause: An attempt was made to complete an instantiation-deferred redefinition
without invoking dbms_redefinition.sync_interim_table.
Action: Invoke dbms_redefinition.sync_interm_table to instantiate this
redefinition.
ORA-42005: invalid type of redefinition method
Cause: An unknown redefinition method was used.
Action: Use one of the supported redefinition methods: o dbms_
redefinition.cons_use_pk o dbms_redefinition.cons_use_rowid
ORA-42006: dependent object registration not supported during a partition
redefinition
Cause: An attempt was made to register dependent objects when redefining a
partition.
Action: Do not invoke dbms_redefinition.register_dependent_object during a
partition redefinition.
ORA-42007: dependent object unregistration not supported during a partition
redefinition
Cause: An attempt was made to unregister dependent objects when redefining a
partition.
Action: Do not invoke dbms_redefinition.unregister_dependent_object during a
partition redefinition.
ORA-42008: error occurred while instantiating the redefinition
ORA-41001 to ORA-42804 23-21
Cause: An error occurred while instantiating the online redefinition which
requires aborting the redefinition.
Action: Correct the error, abort, and restart the online redefinition.
ORA-42009: error occurred while synchronizing the redefinition
Cause: An error occurred while synchronizing the online redefinition.
Action: Correct the error and continue the online redefinition.
ORA-42010: error occurred while synchronizing the redefinition
Cause: An error occurred while synchronizing the online redefinition which
requires aborting the redefinition.
Action: Correct the error, abort, and restart the online redefinition.
ORA-42011: error occurred while completing the redefinition
Cause: An error occurred while completing the online redefinition.
Action: Correct the error and continue the online redefinition.
ORA-42012: error occurred while completing the redefinition
Cause: An error occurred while completing the online redefinition which requires
aborting the redefinition.
Action: Correct the error, abort, and restart the online redefinition.
ORA-42013: interim table of an AQ IOT table should be an IOT table
Cause: An attempt was made to create a table that is not an index-organized table
(IOT) as the interim table of an AQ IOT table (history, time management, or
dequeue).
Action: Ensure that the interim table is created as an IOT table.
ORA-42014: online redefinition unable to lock AQ objects
Cause: An online redefinition of an AQ table was unable to lock all related AQ
objects.
Action: Abort and retry the redefinition.
ORA-42015: online redefinition unable to log changes made to AQ tables
Cause: An online redefinition of an AQ table was unable to log changes made to
AQ tables during the redefinition.
Action: Abort and retry the redefinition.
ORA-42016: shape of interim table does not match specified column mapping
Cause: The number of columns, or the type or the length semantics of a column,
in the interim table did not match the specified column mapping.
Action: Ensure that the interim table matches the column mapping by either
modifying the column mapping string or altering the interim table's column
definition(s).
ORA-42017: interim table of an AQ table should not be an AQ table
Cause: An attempt was made to create an AQ table as an interim table of an
online redefined AQ table.
Action: Ensure that the interim table is not created as an AQ table.
ORA-42018: partition cannot be redefined online because of index organization
incompatibility
23-22 Oracle Database Error Messages
Cause: interim table is incompatible with partition being redefined because one or
more of the following apply:
- one is index-organized and the other is not
- one has IOT overflow segment and the other does not
- one has IOT mapping table and the other does not
Action: Ensure that the interim table is compatible with the partition being
redefined.
ORA-42019: partition cannot be redefined online because of incompatible
partitioning of interim table
Cause: both original and interim tables are partitioned, or original table is
composite-partitioned but interim table is non-partitioned.
Action: Ensure that the interim table has compatible partitioning with the original
table. For example, if the original table is partitioned, the interim table should be
non-partitioned. If the original table is composite-partitioned, the interim table
should be partitioned.
ORA-42020: partition cannot be redefined online because of unsupported type of
interim table
Cause: An unsupported type of interim table was provided during the partition
redefinition. Currently the following types of interim tables are not supported:
- a nested table or has nested-table columns
- an external table
- part of cluster
- contains LOB shared segments
Action: Do not use unsupported types of interim tables.
ORA-42021: partition cannot be redefined online because of incompatible row
dependencies
Cause: original/interim table was created with row dependency and
interim/original table was not.
Action: Ensure that both tables are created with same row dependency properties.
ORA-42022: partition cannot be redefined online because of presence of nested
columns
Cause: An attempt was made to online redefine a partition with nested table
columns.
Action: Do not attempt to online redefine a partition with nested table columns.
ORA-42023: compatibility of AQ table must be release 8.1.x or later
Cause: An attempt was made to perform online redefinition on an AQ table that
was created with compatibility prior to release 8.1.x.
Action: Ensure that the AQ table is created with the COMPATIBLE parameter set
to release 8.1.x or later before attempting online redefinition.
ORA-42024: interim table of an AQ table can not be a partitioned table
Cause: An attempt was made to use a partitioned table as an interim table.
Action: Ensure that the interim table is not a partitioned table.
ORA-41001 to ORA-42804 23-23
ORA-42025: redefinition of CONS_USE_ROWID method cannot be used to
redefine an AQ IOT table
Cause: An attempt was made to use method of DBMS_REDEFINITION.CONS_
USE_ROWID to redefine an AQ IOT table.
Action: Ensure that method of DBMS_REDEFINITION.CONS_USE_PK is used to
redefine an AQ IOT table.
ORA-42026: duplicated rows detected while instantiating the redefinition
Cause: Duplicated rows are detected during instantiation of the redefinition.
Action: Abort the redefinition, turn off the optimistic ascending SCN
optimization, and restart the redefinition.
ORA-42027: cannot redefine an object online that is not a table
Cause: An attempt was made to redefine an object online that is not a table.
Action: Ensure that the object being redefined online is a table.
ORA-42028: materialized view log "string"."string" does not exist
Cause: An attempt was made to register a nonexistent materialized view log as a
dependent object.
Action: Invoke DBMS_REDEFINITION.REGISTER_DEPENDENT_OBJECT on a
valid materialized view log.
ORA-42029: cannot online redefine table "string"."string" at this time
Cause: An attempt was made to redefine a table which is incompatible with
another ongoing redefinition.
Action: Do not perform the redefinition operation on this table or wait until the
incompatible ongoing redefinition has completed.
ORA-42030: cannot online redefine table "string"."string" with commit SCN-based
MV log
Cause: An attempt was made to redefine a table which had a commit SCN-based
materialzed view log defined on it.
Action: Do not attempt to online redefine a table that has a commit SCN-based
materialzed view log defined on it.
ORA-42031: interim table cannot have a commit SCN-based MV log defined on it
Cause: An attempt was made to use an interim table which had a commit
SCN-based materialzed view log defined on it.
Action: Ensure that the interim table does not have a commit SCN-based
materialzed view log defined on it.
ORA-42032: cannot online redefine table "string"."string" with Flashback Data
Archive enabled
Cause: An attempt was made to redefine a table which had Flashback Data
Archive enabled.
Action: Do not attempt to online redefine a table that has Flashback Data Archive
enabled.
ORA-42033: interim table "string"."string" cannot have Flashback Data Archive
enabled
Cause: An attempt was made to redefine a table with an interim table which had
Flashback Data Archive enabled.
23-24 Oracle Database Error Messages
Action: Do not attempt to online redefine a table with an interim table which has
Flashback Data Archive enabled.
ORA-42034: cannot online redefine table "string"."string" which is a CDC table
Cause: An attempt was made to redefine a table which is a CDC table.
Action: Do not attempt to online redefine a table that is a CDC table.
ORA-42035: cannot online redefine IOT table "string"."string" with CONS_USE_
ROWID
Cause: An attempt was made to redefine an IOT table with CONS_USE_ROWID.
Action: Do not attempt to online redefine an IOT table with CONS_USE_ROWID.
ORA-42036: cannot online redefine temporary table "string"."string"
Cause: An attempt was made to redefine a temporary table.
Action: Do not attempt to online redefine a temporary table.
ORA-42037: cannot online redefine table "string"."string" with IOT overflow
segment
Cause: An attempt was made to redefine a table with IOT overflow segment.
Action: Do not attempt to online redefine a table with IOT overflow segment.
ORA-42038: cannot online redefine table "string"."string" with a CDC log defined
on it
Cause: An attempt was made to redefine a table with a CDC log defined on it.
Action: Do not attempt to online redefine a table with a CDC log defined on it.
ORA-42039: cannot online redefine table "string"."string" with FGA enabled
Cause: An attempt was made to redefine a table with Fine Grained Auditing
(FGA) or Row Level Security (RLS) enabled.
Action: Do not attempt to online redefine a table with Fine Grained Auditing
(FGA) or Row Level Security (RLS) enabled.
ORA-42040: cannot online redefine table "string"."string" with column of binary
XML type
Cause: An attempt was made to redefine a table with a column of binary XML
type.
Action: Do not attempt to online redefine a table with a column of binary XML
type.
ORA-42041: cannot online redefine table "string"."string" with nested table columns
Cause: An attempt was made to redefine a table with nested table columns.
Action: Do not attempt to online redefine a table with nested table columns.
ORA-42042: time out in acquiring DML lock during online redefinition
Cause: During FINISH_REDEF_TABLE procedure, the elapsed time waiting to
acquire a table or partition DML lock on the original table exceeds the timeout the
user specified.
Action: Rerun FINISH_REDEF_TABLE procedure to continue the process.
ORA-42043: CONS_VPD_AUTO is only applicable to null column mapping
ORA-41001 to ORA-42804 23-25
Cause: An attempt was made to specify CONS_VPD_AUTO for non-null column
mapping other than null column mapping. CONS_VPD_AUTO can only be
specified for null column mapping.
Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
ORA-42044: cannot redefine table with non-null VPD policy predicate against the
table owner or redefinition invoker
Cause: Virtual Private Database (VPD) policies with non-null predicate against
the table owner or redefinition invoker existed on the original table.
Action: Drop the VPD policies with non-null predicate against the table owner or
redefinition invoker. Restart online redefinition.
ORA-42045: COPY_VPD_OPT cannot be set to CONS_VPD_NONE with VPD
policies on table "string"."string".
Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_
NONE. COPY_VPD_OPT cannot be set to CONS_VPD_NONE with Virtual
Private Database (VPD) policies on the original table.
Action: Set COPY_VPD_OPT to CONS_VPD_AUTO or CONS_VPD_MANUAL.
ORA-42046: COPY_VPD_OPT cannot be set to string with VPD policies on interim
table "string"."string".
Cause: An attempt was made to set the COPY_VPD_OPT value to either CONS_
VPD_NONE or CONS_VPD_AUTO. Cannot set the COPY_VPD_OPT value to
CONS_VPD_NONE or CONS_VPD_AUTO with Virtual Private Database (VPD)
policies on the interim table.
Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
ORA-42047: The specified value for COPY_VPD_OPT is invalid.
Cause: An unknown COPY_VPD_OPT value was used.
Action: Use one of the supported COPY_VPD_OPT values: o DBMS_
REDEFINITION.CONS_VPD_NONE o DBMS_REDEFINITION.CONS_VPD_
AUTO o DBMS_REDEFINITION.CONS_VPD_MANUAL
ORA-42048: Automatic copying of VPD policies with application context is not
supported in online redefinition.
Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_
AUTO for Virtual Private Database (VPD) policies with application context.
Automatic copying of VPD policies with application context is not supported in
online redefinition.
Action: Drop VPD policies with application context or set the COPY_VPD_OPT
value to CONS_VPD_MANUAL.
ORA-42049: cannot online redefine multiple tables and multiple partitions
Cause: An online redefinition procedure was passed multiple original tables and
multiple partitions to redefine.
Action: Do not attempt to online redefine multiple tables at the same time as
multiple partitions.
ORA-42050: COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when
redefining a partition.
Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_
MANUAL. COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when
redefining a partition.
23-26 Oracle Database Error Messages
Action: Set COPY_VPD_OPT to CONS_VPD_NONE or CONS_VPD_AUTO.
ORA-42051: duplicate partition names in partition name list
Cause: An online redefinition procedure was passed a partition name list
containing duplicates.
Action: Ensure that all names in the partition name list are unique.
ORA-42052: interim table cannot have materialized view or zonemap defined on it
Cause: An attempt was made to redefine a table with an interim table on which a
materialized view or zonemap was defined.
Action: Remove all materialized views and zonemaps defined on the interim
table and retry online redefinition, or do not attempt online redefinition.
ORA-42053: cannot online redefine table "string"."string" with OLS/XDS enabled
Cause: An attempt was made to redefine a table with Oracle Label Security (OLS)
or Extensible Data Security (XDS) enabled.
Action: Do not attempt to online redefine a table with Oracle Label Security (OLS)
or Extensible Data Security (XDS) enabled.
ORA-42054: cannot online redefine table "string"."string" with UXI XML index
Cause: An attempt was made to redefine a table with XML indexes having an
Unstructured XMLIndex (UXI) component.
Action: Do not attempt to online redefine a table with XML indexes having an
Unstructured XMLIndex (UXI) component.
ORA-42287: cannot rename user on whose type a table depends
Cause: An attempt was made to rename a user whose schema contained a type on
which some table depends. The operation may not proceed as it would render the
table invalid causing loss of data.
Action: Drop table(s) dependent on types belonging to the schema of the user
being renamed.
ORA-42288: may not create a schema synonym for the specified schema
Cause: An attempt was made to create a schema synonym for one of the reserved
schemas (such as SYS or SYSTEM.)
Action: Schema synonyms for this schema may not be created.
ORA-42289: may not rename specified user
Cause: An attempt was made to rename one of the following:
- reserved user (such as SYS or SYSTEM)
- an administrative user
- a common user
- a locked user account
Action: This user may not be renamed.
ORA-42290: specified schema does not exist
Cause: An attempt was made to create a schema synonym for a schema which did
not exist.
Action: Correct the input and try again.
ORA-42291: schema synonym 'string' does not exist
ORA-41001 to ORA-42804 23-27
Cause: The named schema synonym did not exist.
Action: Verify you are using the correct schema synonym name.
ORA-42292: RENAME TO already specified
Cause: The RENAME TO clause was specified twice.
Action: Use only one RENAME TO clause.
ORA-42293: user name conflicts with another user, role or schema synonym name
Cause: There was already a user, role or schema synonym with that name.
Action: Specify a different user name.
ORA-42294: role name conflicts with another user, role or schema synonym name
Cause: There was already a user, role or schema synonym with that name.
Action: Specify a different role name.
ORA-42295: schema synonym name conflicts with another user, role or schema
synonym name
Cause: There was already a user, role or schema synonym with that name.
Action: Specify a different schema synonym name or use CREATE OR REPLACE
SCHEMA SYNONYM.
ORA-42296: user, role or schema synonym 'string' does not exist
Cause: There was no user, role, or schema synonym by that name.
Action: Respecify the name.
ORA-42297: cannot drop a schema synonym for a schema of a user who is currently
connected
Cause: An attempt was made to drop a schema synonym for a schema of a user
who was logged on.
Action: Make sure user is logged off, then repeat command.
ORA-42298: cannot rename a user that is currently connected
Cause: An attempt was made to rename a user that was logged on.
Action: Make sure user is logged off, then repeat command.
ORA-42300: an Editioning view is already defined on this table
Cause: An attempt was made to create an Editioning view on a table on which
another Editioning view is already defined in the same Edition. This violates a
restriction that at most one Editioning view may be associated with any base table
in a given Edition.
Action: Create the new view as a regular view or, if the view being created is
really intended to be an Editioning view associated with this table, drop the
existing Editioning view before creating the new one.
ORA-42301: definition of an Editioning view may not refer to a synonym
Cause: An attempt was made to create an Editioning view referring to a synonym,
which is not supported.
Action: Do not create an Editioning view if you want the view to refer to a
synonym.
ORA-42302: definition of an Editioning view may not refer to remote tables
23-28 Oracle Database Error Messages
Cause: An attempt was made to create an Editioning view referring to remote
tables, which is not supported.
Action: Do not create an Editioning view if you want the view to refer to a remote
table.
ORA-42303: duplicate column reference in a definition of an Editioning view
Cause: An attempt was made create an Editioning view referencing the same
column of a base table more than once, which is not supported.
Action: Do not create an Editioning view if you have multiple columns referring
to the same column of the base table.
ORA-42304: base table and the Editioning view must belong to the same schema
Cause: An attempt was made to create an Editioning view in a schema different
from that of the base table.
Action: Create an Editioning view in the same schema as the base table.
ORA-42305: only an Editioning view may replace an Editioning view
Cause: An attempt was made to replace an Editioning view with a view which is
not an Editioning view or vice versa.
Action: Ensure that either both or neither of the views involved are Editioning
views.
ORA-42306: a CrossEdition trigger may not be created on an Editioning view
Cause: An attempt was made to create a CrossEdition trigger on an Editioning
view, which is not supported.
Action: Instead of creating a CrossEdition trigger on an Editioning view, create it
on the Editioning view's underlying table.
ORA-42307: columns of an Editioning view may only refer to base table columns
Cause: An attempt was made to define an Editioning view containing a column
referring to an entity other than a base table column (for example, a PL/SQL
function without a parameter), which is not supported.
Action: Ensure that every column of an Editioning view refers to a column of a
base table.
ORA-42308: view string.string is already in read-only mode
Cause: An attempt was made to set a read-only table in read-only mode.
Action: This DDL can only be executed on a read/write view.
ORA-42309: view string.string is already in read/write mode
Cause: An attempt was made to set a read/write view in read/write mode.
Action: This DDL can only be executed on a read-only view.
ORA-42310: Implementation restriction: this operation is only permitted on
Editioning views
Cause: The view being altered was not an Editioning view. In this release, an
ALTER VIEW READ ONLY, or ALTER VIEW READ WRITE operation is only
permitted on Editioning views.
Action: Ensure that the view is an Editioning view.
ORA-42311: This operation is not permitted on Editioning views with compilation
errors
ORA-41001 to ORA-42804 23-29
Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not
permitted on Editioning views which have compilation errors.
Action: Resolve the compilation errors.
ORA-42313: This operation is not supported on Editioning views marked invalid
Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not
permitted on Editioning views which are marked invalid.
Action: Recompile the Editioning view to ensure that it is valid.
ORA-42314: editioning view cannot be owned by a non-editioned user
Cause: An attempt was made to create an editioning view in a schema where
views were not editionable.
Action: Enable editions for the user for views and then create the editioning view.
ORA-42399: cannot perform a DML operation on a read-only view
Cause: An attempt was made to insert, delete, or update row(s) of a view created
with read-only option. DML operations on such views are explicitly prohibited.
Action: Perform the desired DML operation on the view's underlying base table
or issue ALTER VIEW ... READ WRITE command to make the view updatable.
ORA-42800: The specified attribute association ("string", "string") is already
attached to existing shared context-sensitive policies with the specified policy
function string.string.
Cause: An attempt was made to add an attribute association which was already
attached to shared context-sensitive policies with the specified policy function. All
shared context-sensitive policies with a common policy function need to have the
same set of attribute associations. Attribute associations of an existing shared
context-sensitive policy which is using the specified policy function will be
automatically added to the new policy.
Action: Retry the operation without specifying the attribute association.
ORA-42801: Value is not set for context attribute ("string", "string") which is
associated with the Row Level Security (RLS) policy "string".
Cause: The value was not set for every attribute association of the shared
context-sensitive policy. The value must be set for every attribute association of the
shared context-sensitive policy.
Action: Set the value for the context attribute and retry the operation.
ORA-42802: Could not read attribute associations from an existing shared
context-sensitive policy which is using the specified policy function.
Cause: An existing shared context-sensitive policy using the specified policy
function was dropped from another session.
Action: Re-issue the command.
ORA-42803: Cannot use bind variable in VERSIONS clause when the object has a
Row-Level Security (RLS) policy defined on it.
Cause: The object being accessed had a Row-Level Security (RLS) policy defined
on it and the VERSIONS clause contained a bind variable.
Action: Rewrite the query without the use of bind variable in the VERSIONS
clause.
ORA-42804: The query could disclose rows protected by select VPD policy.
23-30 Oracle Database Error Messages
Cause: The object being accessed had a select Virtual Private Database (VPD)
policy defined on it and the DML which is executed could disclose rows protected
by the select VPD policy.
Action: Define VPD policy with the specific statement type.