-
ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array
-
Cause: The value of index1 was greater than the value for index2 in the call to bind_array. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2.
-
Action: Correct the value of the two indexes and try the call to again bind_array.
-
ORA-29252: collection does not contain elements at index locations in call to dbms_sql.bind_array
-
Cause: The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true.
-
Action: Either modify the two indexes or the contents of the table and try the call again.
-
ORA-29253: Invalid count argument passed to procedure dbms_sql.define_array
-
Cause: The count argument specified in the call to procedure define_array of package dbms_sql had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer.
-
Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again.
-
ORA-29254: Invalid lower_bound argument passed to procedure dbms_sql.define_array
-
Cause: The lower_bound argument specified in the call to procedure define_array had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal.
-
Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again.
-
ORA-29255: Cursor contains both bind and define arrays which is not permissible
-
Cause: Both define_array and bind_array have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries.
-
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand.
-
ORA-29256: Cursor contains both regular and array defines which is illegal
-
Cause: Both define_array and define_column have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables.
-
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the situation at hand.
-
ORA-29275: partial multibyte character
-
Cause: The requested read operation could not complete because a partial multibyte character was found at the end of the input.
-
Action: Ensure that the complete multibyte character is sent from the remote server and retry the operation. Or read the partial multibyte character as RAW.
-
ORA-29290: invalid offset specified for seek
-
Cause: An attempt was made to seek past the end of the file, or both the absolute and relative offsets were NULL, or absolute offset was less than zero.
-
Action: If specifying an absolute offset, ensure it is in the range [0, <total number of bytes in the file>], or if specifying a relative offset, ensure it is no greater than the current byte position plus the number of bytes remaining in the file.
-
ORA-29292: file rename operation failed
-
Cause: A file rename attempt was refused by the operating system either because the source or destination directory does not exist or is inaccessible, or the source file isn't accessible, or the destination file exists.
-
Action: Verify that the source file, source directory, and destination directory exist and are accessible, and that the destination file does not already exist.
-
ORA-29293: A stream error occurred during compression or uncompression.
-
Cause: The stream state was discovered to be invalid during compression or uncompression, or an invalid compression quality was requested or a NULL or invalid compression parameter was detected.
-
Action: Verify that quality is within the range [0,9] and that valid input source data exists.
-
ORA-29312: changes by release string cannot be used by release string, type: string
-
Cause: A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace.
-
Action: Choose a point-in-time and retry the operation.
-
ORA-29319: datafile string is not correct
-
Cause: An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database.
-
Action: Copy the datafile from the clone database to the production database.
-
ORA-29338: datafile string is in an undesired state (string, string)
-
Cause: The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE.
-
Action: Put the datafile into the desired state.
-
ORA-29339: tablespace block size string does not match configured block sizes
-
Cause: The block size of the tablespace to be plugged in or created does not match the block sizes configured in the database.
-
Action: Configure the appropriate cache for the block size of this tablespace using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.
-
ORA-29342: user string does not exist in the database
-
Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.
-
Action: Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options.
-
ORA-29344: Owner validation failed - failed to match owner 'string'
-
Cause: The system failed to match the referred owner. There are two cases that this may occur. (1) This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified. (2) This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set.
-
Action: Retry import with a different OWNER list.
-
ORA-29347: Tablespace name validation failed - failed to match tablespace 'string'
-
Cause: The system failed to match the referred tablespace. There are 2 cases that this may happen. (1) This tablespace is in the transportable set, but it is not specified in the TABLESPACES list of the import command line option, assuming that TABLESPACES is specified. (2) This tablespace is in the TABLESPACES list, but it is not in the transportable set.
-
Action: Retry the operation with the correct TABLESPACES list.
-
ORA-29356: These parameters can be specified only for directives that refer to consumer groups
-
Cause: The below parameters were specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.where the GROUP_OR_SUBPLAN argument is a resource plan. "ACTIVE_SESS_POOL_P1", "QUEUEING_P1", "PARALLEL_DEGREE_LIMIT_P1", "SWITCH_P1", "SWITCH_P2", "SWITCH_P3", "MAX_EST_EXEC_TIME", "UNDO_POOL"
-
Action: Specify these parameters only for consumer group directives.
-
ORA-29377: consumer group string is not part of top-plan string
-
Cause: OTHER_GROUPS was not included as part of the specified top-plan. Each top plan must include the built-in consumer group OTHER_GROUPS.
-
Action: Create a plan directive with the argument GROUP_OR_SUBPLAN being OTHER_GROUPS somewhere in the top-plan.
-
ORA-29381: plan/consumer_group string referred to by another plan and cannot be deleted
-
Cause: An attempt was made to delete a plan or consumer group that is referred to by another plan.
-
Action: Remove all plan directives that have the plan or consumer group as GROUP_OR_SUBPLAN; then delete the plan or consumer group.
-
ORA-29383: all leaves of top-plan string must be consumer groups
-
Cause: An attempt was made to create or modify the specified top-plan but it has some plans as leaves.
-
Action: To identify which plans and/or plan directives need to be modified, look at all plans that have no plan directives. Then, alter the top-plan so that all its leaves are consumer groups.
-
ORA-29387: no top-plans found in the pending area
-
Cause: The VALIDATE_PENDING_AREA procedure found that either the intended top-plan(s) are involved in a loop or there are no top-plans.
-
Action: Check all edges going from a subplan to the intended top-plan. Make sure the top plan does not have any plan referring to it.
-
ORA-29388: plan/consumer_group string is part of more than one top-plan
-
Cause: An attempt was made to delete a subtree that includes a plan or consumer group that is part of more than one top-plan as part of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. Such a plan or consumer group cannot be deleted.
-
Action: Check the ancestors of the plan or consumer group and make sure it is only part of the top-plan that includes the subtree being deleted.
-
ORA-29392: cpu parameters for level string for plan string must be zero
-
Cause: The cpu parameters for the specified level had a non-zero value, which is not a valid value for the plan's current cpu policy.
-
Action: Change the cpu level parameters for the specified level to zero or change the plan cpu policy.
-
ORA-29393: user string does not exist or is not logged on
-
Cause: An invalid user name was specified as argument to procedure SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or the specified user was not logged on.
-
Action: Specify a valid user name.
-
ORA-29399: user string does not have privilege to switch to consumer group string
-
Cause: An attempt was made to set the initial consumer group of the specified user but the user does not have the privilege to switch to that group.
-
Action: Grant the privilege to switch to the consumer group to the user and then set the initial group.
-
ORA-29400: data cartridge error string
-
Cause: An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error.
-
Action: See the data cartridge documentation for an explanation of the second error message.
-
ORA-29514: class name contains illegal character
-
Cause: An attempt was made to import a .class file containing a character that cannot be converted to the server character set. The .class file could not be imported because of the illegal character.
-
Action: Correct the illegal character in the .class file.
-
ORA-29537: class or resource cannot be created or dropped directly
-
Cause: An attempt was made to create or drop a Java class or resource that is known to result from compilation of an existing Java source object.
-
Action: Act on the class or resource by acting on the source, or change the source so that it no longer defines the class or resource.
-
ORA-29545: badly formed class: string
-
Cause: An attempt was made to create a Java class object with bytecodes that were rejected by the Java verifier.
-
Action: It is possible that an attempt was made to create the Java class from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver.
-
ORA-29552: verification warning: string
-
Cause: An attempt was made to create a Java class object with bytecodes that caused the Java verifier to issue a warning.
-
Action: It is possible that the Java class was created from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver.
-
ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
-
Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release.
-
Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT parameter. Or, upgrade all instances to Oracle 8.1.6 or later release and then specify the parameter.
-
ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
-
Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same in all Oracle cluster database instances.
-
Action: Check your initialization parameter files in all instances and ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value. Then restart the instance.
-
ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT
-
Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two node cluster database configuration or unspecified if a secondary instance is not needed.
-
Action: Check your initialization parameter files and correct the value of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a two node primary/secondary cluster database, set this value to 1. Otherwise, do not specify any value for the parameter.
-
ORA-29707: inconsistent value string for initialization parameter string with other instances
-
Cause: The value of the initialization parameter in error must be identical on all Oracle cluster database instances and was not.
-
Action: Check your INIT.ORA files on all instances and ensure that the initialization parameters in error have the same value.
-
ORA-29740: evicted by member string, group incarnation string
-
Cause: This member was evicted from the group by another member of the cluster database for one of several reasons, which may include a communications error in the cluster, failure to issue a heartbeat to the control file, etc.
-
Action: Check the trace files of other active instances in the cluster group for indications of errors that caused a reconfiguration.
-
ORA-29746: Cluster Synchronization Service is being shut down.
-
Cause: The administrator has shut down the Cluster Synchronization Service daemon. This error message is intended to be informative to users on the status of the service.
-
Action: Check the log file of the Cluster Synchronization Service daemon to verify the state of the service.
-
ORA-29760: instance_number parameter not specified
-
Cause: The init.ora file did not contain a value for the instance_number which is required to identify this instance to other instances of the database running on the same cluster
-
Action: Assign a value to the instance_number parameter in the init.ora parameter file
-
ORA-29835: ODCIGETINTERFACES routine does not return required interface(s)
-
Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the interface(s) required by the current usage.
-
Action: Ensure that the ODCIGetInterfaces routine returns the name(s) of the required interface(s).
-
ORA-29842: option not supported with the version string of the indextype interface
-
Cause: User specified an option which is not supported with the version of the indextype interface provided
-
Action: User should either not request for this option or should provide an implementation type that implements the correct version of the indextype interface.
-
ORA-29845: indextype does not support local domain index on string partitioned table
-
Cause: User specified a create local domain index statement using an indextype that does not support local domain indexes on tables partitioned with the given method
-
Action: Use a different indextype or build a global domain index
-
ORA-29857: domain indexes and/or secondary objects exist in the tablespace
-
Cause: An attempt was made to drop a tablespace which contains secondary objects and/or domain indexes.
-
Action: Drop the domain indexes in his tablespace. Also, find the domain indexes which created secondary objects in this tablespace and drop them. Then try dropping the tablespace.
-
ORA-29860: cannot truncate a table with domain indexes marked LOADING
-
Cause: The table has domain indexes defined on it that are marked LOADING.
-
Action: Wait to see if the ongoing index DDL ends and the index state changes from LOADING state. Else ,drop the domain indexes marked as LOADING with the FORCE option.
-
ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE
-
Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.
-
Action: Wait if the specified index is marked LOADING Drop the specified index if it is marked FAILED Drop or rebuild the specified index if it is marked UNUSABLE.
-
ORA-29864: analyzing domain indexes marked LOADING/FAILED not supported
-
Cause: Tried to analyze a domain index which was marked as LOADING or FAILED.
-
Action: If the index was marked LOADING, wait till it is marked valid before retrying the analyze. If index was marked FAILED, drop it OR rebuild it and retry the analyze.
-
ORA-29879: cannot create multiple domain indexes on a column list using same indextype
-
Cause: An attempt was made to define multiple domain indexes on the same column list using identical indextypes.
-
Action: Check to see if a different indextype can be used or if the index can be defined on another column list.
-
ORA-29880: such column list already indexed using another domain index and indextype
-
Cause: An attempt was made to create multiple domain indexes on a column list using indextypes which do not have disjoint operators.
-
Action: Check to see if the operator sets for the indextypes can be made disjoint.
-
ORA-29933: object being disassociated has some user defined statistics stored
-
Cause: There are some user defined statistics collected for the object being disassociated.
-
Action: First delete the user defined statistics and then reissue the DISASSOCIATE command or specify the FORCE option with DISASSOCIATE.
-
ORA-29952: cannot issue DDL on a domain index partition marked as LOADING
-
Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition in a LOADING state.
-
Action: Wait till the index partition operation completes OR issue a DROP INDEX FORCE to drop the index OR issue a ALTER TABLE DROP PARTITION to drop the partition.
-
ORA-29954: domain index partition is marked LOADING/FAILED/UNUSABLE
-
Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.
-
Action: Wait if the specified index partition is marked LOADING Rebuild the specified index partition if it is marked FAILED or UNUSABLE.
-
ORA-29959: error in the execution of the string routine for one or more of the index partitions
-
Cause: An error occurred during execution of the routine for one or more of the index partitions
-
Action: Check the *_IND_PARTITIONS view to see which partitions are marked FAILED. Rebuild or Truncate the FAILED index partitions
-
ORA-29967: Cannot drop an operator binding with dependent objects
-
Cause: The operator binding that is being dropped has dependent objects.
-
Action: Either drop the dependent objects first and then issue the ALTER OPERATOR DROP BINDING command or specify the FORCE option with ALTER OPERATOR DROP BINDING.
-
ORA-29968: No primary operator bindings found for ancillary binding #string
-
Cause: At least one ancillary binding of the specified operator could not be validated because all of its associated primary operator bindings have been dropped.
-
Action: Either drop the ancillary binding whose primary operators are missing, or drop the entire operator, if this is the only binding. This binding cannot be re-validated.
-
ORA-30000: missing either trim specification or char expression in TRIM
-
Cause: Since FROM is specified in TRIM function, either trim specification (TRAILING, HEADING, BOTH) or trim character or both must be specified.
-
Action: Add either trim specification (TRAILING, HEADING, BOTH) or trim character or both.
-
ORA-30015: previously offlined undo tablespace 'string' is still pending
-
Cause: the current operation is not allowed because an undo tablespace containing active transactions is pending from a previous SWITCH UNDO operation. The operation will be allowed again after all transactions in the previous undo tablespace are committed.
-
Action: Wait for all previous transactions to commit before reissuing the current statement.
-
ORA-30078: partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
-
Cause: An attempt was made to use a time/timestamp expression whose format does not explicitly have time zone on a TIME/TIMESTAMP or TIME/TIMESTAMP WITH TIME ZONE column.
-
Action: Explicitly use TIME/TIMESTAMP WITH TIME ZONE literal.
-
ORA-30079: cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
-
Cause: An attempt was made to alter database timezone with TIMESTAMP WITH LOCAL TIME ZONE column in the database.
-
Action: Either do not alter database timezone or first drop all the TIMESTAMP WITH LOCAL TIME ZONE columns.
-
ORA-30082: datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
-
Cause: datetime/interval column with existing data is being modified to decrease fractional second or leading field precisions.
-
Action: Such columns are only allowed to increase the precisions.
-
ORA-30086: interval year-month result not allowed for datetime subtraction
-
Cause: An attempt was made to specify interval year to month as the result of datetime subtraction.
-
Action: This is not allowed currently due to unclear specification in SQL Standards for this interval type. Change the interval type to interval day to second and resubmit statement.
-
ORA-30150: Invalid argument passed to OCIFile function
-
Cause: An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected.
-
Action: Make sure that the values passed as arguments are valid. Esp check for NULL pointers.
-
ORA-30159: OCIFileOpen: Cannot create the file or cannot open in the requested mode
-
Cause: The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it doesn't allow the file to be opened in in the requested open mode
-
Action: Check whether the user has permissions to create the specified file or if the file exists whether the permissions on it allow the requested open mode.
-
ORA-30335: JOIN KEY clause references a level not in this hierarchy
-
Cause: The level name specified with the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not reference a level in the hierarchy that contains the JOIN KEY clause. *Acction: Check the spelling of the level name.
-
Action: none
-
ORA-30336: no child for specified JOIN KEY
-
Cause: The level specified in the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not have a child level.
-
Action: Check the spelling of the level name referenced in the JOIN KEY clause. If the referenced level is the first level in the hierarchy, you need not and must not specify a JOIN KEY clause.
-
ORA-30337: multiple JOIN KEY clauses specified for the same parent level
-
Cause: More than one JOIN KEY clause was specified for a given parent level in a dimension hierarchy.
-
Action: Match up each JOIN KEY clause with the level it references in the hierarchy. Eliminate the redundant JOIN KEY clause.
-
ORA-30338: illegal dimension hierachy name
-
Cause: An illegal dimension hierarchy name was specified in a dimension DDL statement.
-
Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system.
-
ORA-30339: illegal dimension attribute name
-
Cause: An illegal dimension attribute name was specified in a dimension DDL statement.
-
Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system.
-
ORA-30340: illegal dimension name
-
Cause: An illegal dimension name was specified in a dimension DDL statement.
-
Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system.
-
ORA-30341: dropped level has references
-
Cause: An attempt was made to drop a level using the default or RESTRICT option in a dimension while references to that level remain in the dimension. References can occur in hierarchies and attributes within the dimension.
-
Action: First remove any referenes to the level prior to dropping it, or specify the CASCADE option with the DROP LEVEL clause.
-
ORA-30344: number of child cols different from number of parent level cols
-
Cause: The number of child columns specified in a JOIN KEY clause is not the same as the number of columns in the specified parent level.
-
Action: Check the child columns and the columns in the definition of the referenced parent level and correct the discrepency.
-
ORA-30352: inconsistent numeric precision or string length
-
Cause: The SELECT expression was of a different numeric precision or string length than the corresponding container column. Therefore, query rewrite cannot guarantee results that are identical to the results obtained with the un-rewritten query.
-
Action: Correct the precision or string length difference, specify the WITH REDUCED PRECISION option, or disable the REWRITE option on the materialized view.
-
ORA-30353: expression not supported for query rewrite
-
Cause: The select clause referenced UID, USER, ROWNUM, SYSDATE, CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable, correlation variable, a set result,a trigger return variable, a parallel table queue column, collection iterator, etc.
-
Action: Remove the offending expression or disable the REWRITE option on the materialized view.
-
ORA-30355: materialized view container does not exist
-
Cause: A DROP TABLE command was issued directly against the materialized view container table.
-
Action: Use the DROP MATERIALIZED VIEW command to clean up the residual meta data for the materialized view. Then use the CREATE MATERIALIZED VIEW statement to recreate the materialized view. Thereafter, use the DROP MATERIALIZED VIEW command rather than the DROP TABLE command to drop a materialized view.
-
ORA-30357: this PL/SQL function cannot be supported for query rewrite
-
Cause: The statement referenced a PL/SQL function that is not marked DETERMINISTIC.
-
Action: Perform one of the following actions:
- Remove the use of the PL/SQL function.
- Mark the PL/SQL function as DETERMINISTIC.
- Disable the REWRITE option on the materialized view. The function should be marked DETERMINISTIC only if it always returns the same result value for any given set of input argument values, regardless of any database state or session state. Do not mark the function as DETERMINISTIC if it has any meaningful side-effects.
-
ORA-30360: REF not supported with query rewrite
-
Cause: The statement contained a REF operator. Repeatable behavior cannot be guaranteed with the REF operator. Therefore, query rewrite cannot support the REF operator.
-
Action: Remove the reference to the REF operator or disable the REWRITE option on the materialized view.
-
ORA-30365: left relation in the JOIN KEY clause cannot be same as right
-
Cause: The relation of the child columns on the left side of the JOIN KEY clause was the same as that of the parent level on the right side.
-
Action: Remove the JOIN KEY clause. It is not required or allowed when the child and the parent are in the same relation.
-
ORA-30367: a JOIN KEY clause is required
-
Cause: A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY clause is required when the child level and the parent level are not in the same relation.
-
Action: Specify a JOIN KEY clause to indicate how the relation of the child level joins to the relation of the parent level.
-
ORA-30368: ATTRIBUTE cannot determine column in a different relation
-
Cause: An ATTRIBUTE clause in a dimension statement specified a determined column on the right that is in a different relation than that of the level on the left.
-
Action: Specify attibutes only for those dimension levels that functionally determine other columns within the same relation.
-
ORA-30371: column cannot define a level in more than one dimension
-
Cause: A column was used in the definition of a level after it had already been used to define a level in a different dimension.
-
Action: Reorganize dimension levels and hierarchies into a single dimension such that no column is used to define levels in different dimensions. There is no limit on the number of levels or hierarchies you can place in a dimension. A column can be used to define any number of levels provided all such levels are in the same dimension and provided no two levels contain identical sets of columns.
-
ORA-30372: fine grain access policy conflicts with materialized view
-
Cause: A fine grain access control procedure has applied a non-null policy to the query for the materialized view.
-
Action: In order for the materialized view to work correctly, any fine grain access control procedure in effect for the query must return a null policy when the materialized view is being created or refreshed. This may be done by ensuring that the usernames for the creator, owner, and invoker of refresh procedures for the materialized view all receive a null policy by the user-written fine grain access control procedures.
-
ORA-30378: MV_CAPABILITIES_TABLE is not compatible with Oracle version
-
Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is either missing or incompatible with the current Oracle version.
-
Action: Connect to the appropriate schema, DROP TABLE MV_CAPABILITIES_TABLE and recreate it by invoking the admin/utlxmv.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_MVIEW() API.
-
ORA-30381: REWRITE_TABLE is not compatible with Oracle version
-
Cause: One or more column definitions in the REWRITE_TABLE is either missing or incompatible with the current Oracle version.
-
Action: Connect to the appropriate schema, DROP TABLE REWRITE_TABLE and recreate it by invoking the admin/utlxrw.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_REWRITE() API.
-
ORA-30389: the source statement is not compatible with the destination statement
-
Cause: The SELECT clause of the source statement is not compatible with the SELECT clause of the destination statement
-
Action: Verify both SELECT clauses are compatible with each other such as numbers of SELECT list items are the same and the datatype for each SELECT list item is compatible
-
ORA-30395: dimension options require the COMPATIBLE parameter to be string or greater
-
Cause: The following materialized view options require 10.1 or higher compatibility setting:
o dimension attribute extended level syntax ATTRIBUTE <attribute name> LEVEL <level name> DETERMINES <column name>
-
Action: Shut down and restart with an appropriate compatibility setting.
-
ORA-30396: rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
-
Cause: Query rewrite equivalence APIs require 10.1 or higher compatibility setting:
o DBMS_ADVANCED_REWRITE.DECLARE_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.ALTER_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.DROP_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.VALIDATE_REWRITE_EQUIVALENCE
-
Action: Shut down and restart with an appropriate compatibility setting.
-
ORA-30438: unable to access named pipe 'string'
-
Cause: The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition.
-
Action: This is an internal error. Notify ORACLE technical support
-
ORA-30440: can't fast refresh;refresh complete or set event 30441 for partial refresh
-
Cause: Both DML and direct-load are performed against detail tables. Fast refresh can only process direct-load inserts.
-
Action: Refresh complete or set event 30441 to enable partial refresh with only direct-load inserts
-
ORA-30443: definition for filter string's item string is invalid
-
Cause: The specified filter is invalid. It contains at least one invalid filter item. If a filter item has a string list, it becomes illegal when the string list cannot be successfully parsed. If the filter item contains a range definition, and the lower bound of the range is greater than the higher bound, the item also becomes invalid.
-
Action: Remove the illegal filter with the purge_filter sub-program and redefine a correct filter
-
ORA-30446: valid workload queries not found
-
Cause: None of the specified queries can be successfully parsed. The error may come from many sources: SQL syntax error, the owner specified by the load_workload subprograms do not match the real user who generates the SQL statement
-
Action: Only load valid SQL statements into the advisor repository. Make sure the statements can be parsed with privilege of the owner as specified in the owner parameter of the load_workload() subprogram.
-
ORA-30447: internal data for run number string is inconsistent
-
Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.
-
Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove the inconsistent data from summary advisor's internal tables
-
ORA-30448: internal data of the advisor repository is inconsistent
-
Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.
-
Action: This is an internal error. Notify ORACLE technical support
-
ORA-30450: refresh_after_errors was TRUE; The following MVs could not be refreshed: string
-
Cause: One or more errors occurred during a refresh of multiple summaries.
-
Action: The number_of_failures parameter returns the count of how many failures occurred. The trace logs for each refresh operation describe the each individual failure in more detail
-
ORA-30452: cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
-
Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to in refresh STDDEV(X) or VARIANCE(X)
-
Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.
-
ORA-30453: summary contains AVG without corresponding COUNT
-
Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column to be included in the summary definition
-
Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.
-
ORA-30454: summary contains STDDEV without corresponding SUM & COUNT
-
Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition
-
Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.
-
ORA-30455: summary contains VARIANCE without corresponding SUM & COUNT
-
Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition
-
Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.
-
ORA-30457: 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
-
Cause: The container object for the summary contains one or more unmanaged columns do not allow nulls, and which do not specify a default valur for those columns.
-
Action: Make sure that default values are specified for all NOT NULL columns that are not part of the summary definition.
-
ORA-30459: 'string.string' cannot be refreshed because the refresh method is NONE
-
Cause: An attempt was made to refresh a summary whose refresh method is NONE
-
Action: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed. Alter the summary to change the default refresh method from NONE to some other value.
-
ORA-30463: 'string' is not a detail table of any summary
-
Cause: The list of tables passed to refresh_dependent contains at least one invalid table name. That table is not a detail table of any summary and is therefore an invalid input to refresh_dependent
-
Action: Verify the correct name of all tables in the list
-
ORA-30467: internal data for filter number string is inconsistent
-
Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.
-
Action: Users can call the DBMS_OLAP.PURGE_FILTER subprogram to remove the inconsistent data from summary advisor's internal tables
-
ORA-30476: PLAN_TABLE does not exist in the user's schema
-
Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user's schema. For more information refer to the SQL Reference Manual.
-
Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script utlxplan.sql will create this table.
-
ORA-30486: invalid window aggregation group in the window specification
-
Cause: If the window specification is specified using RANGE option and there are multiple ORDER BY expressions, then the aggregation group cannot contain any expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the first end point is CURRENT ROW, then second end point can only be CURRENT ROW or <expr> /UNBOUNDED FOLLOWING. If the first end point is <expr> FOLLOWING, then second end point can only be <expr>/UNBOUNDED FOLLOWING.
-
Action: none
-
ORA-30500: database open triggers and server error triggers cannot have BEFORE type
-
Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported.
-
Action: Do not attempt to create a trigger that fires before the database is open or before server errors.
-
ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
-
Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table.
-
Action: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events.
-
ORA-30505: system triggers should not reference a column in a WHEN clause
-
Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table.
-
Action: Change the WHEN clause to an appropriate clause.
-
ORA-30511: invalid DDL operation in system triggers
-
Cause: An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations and ALTER?COMPILE operations.
-
Action: Remove invalid DDL operations in system triggers.
-
ORA-30512: cannot modify string.string more than once in a transaction
-
Cause: An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations.
-
Action: Do not create system triggers that might modify an already modified object. Also, do not specify more than one DDL operation on a queue table in the same transaction.
-
ORA-30514: system trigger cannot modify tablespace being made read only
-
Cause: A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration
-
Action: Modify the trigger to avoid modifications to the objects in the same tablespace as the one which is being made read only, or use autonomous transactions to commit modifications
-
ORA-30554: function-based index string.string is disabled
-
Cause: An attempt was made to access a function-based index that has been marked disabled because the function on which the index depends has been changed.
-
Action: Perform one of the following actions: -- drop the specified index using the DROP INDEX command -- rebuild the specified index using the ALTER INDEX REBUILD command -- enable the specified index using the ALTER INDEX ENABLE command -- make the specified index usable using the ALTER INDEX UNUSABLE command
-
ORA-30564: Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
-
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD partition to a HASH partitioned table or ADD subpartition to a composite partitioned table.
-
Action: Remove clause and reissue operation
-
ORA-30569: data type of given column is not supported in a log group
-
Cause: An attempt was made to include a column with one of these unsupported data types: LONG, VARRAY, nested table, object, LOB, FILE, or REF in a log group.
-
Action: Change the column data type or remove the log group. Then retry the operation.
-
ORA-30572: AUTO segment space management not valid with DICTIONARY extent management
-
Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used with a DICTIONARY extent management clause.
-
Action: Either specify LOCAL extent management or remove the AUTO SEGMENT SPACE MANAGEMENT specification.
-
ORA-30645: reject limit out of range
-
Cause: Reject limit specifies the number of records rejected before terminating a table scan. The range is a either a number between 1..100000 or UNLIMITED if no limit is intended.
-
Action: Change the token representing the reject limit to either a number in the range of 0 and 100000 or the keyword UNLIMITED.
-
ORA-30659: too many locations specified for external table
-
Cause: An attempt was made to create an External Organized table with more than the maximum allowable (32767) locations specified.
-
Action: Don't do that, use fewer location clauses. Either consider concatenating the input files, or, creating two external tables with the input files split between them.
-
ORA-30676: socket read or write failed
-
Cause: A problem kept a socket from reading or writing the expected amount of data. More specific information is not available.
-
Action: Try re-establishing a connection. You may need to restart whatever program is at the other end of the socket that failed, or you may need to have some problem on your network fixed.
-
ORA-30678: too many open connections
-
Cause: An attempt to open a connection failed because too many are already open by this session. The number of allowed connections varies as some may be in use through other components which share the same pool of allowed connections.
-
Action: Retry after closing some other connection. The number of connections supported is currently not adjustable.
-
ORA-30679: JDWP-based debugging not supported in this configuration
-
Cause: An attempt to open a debugging connection failed because this server configuration cannot support the required asynchronous socket traffic detection.
-
Action: This feature will not work under this server configuration. Either the feature is not supported on this platform at all, or is available only through use of a protocol=tcp dispatcher in shared-server configurations. Please consult the platform-specific documentation and "readme" material.
-
ORA-30680: debugger connection handshake failed
-
Cause: A problem occurred when trying to establish a debugger connection. This might indicate that the port specified as the location of the debugger is actually being used by some other type of application.
-
Action: Correct the host or port specifications if they are incorrect, and verify that the debugger is properly waiting for a connection.
-
ORA-30683: failure establishing connection to debugger
-
Cause: An error was indicated when trying to establish a connection to a debugger. Usually a TNS error will display along with this message to further explain the problem, although this TNS error will likely be hidden if you choose to trap the error.
-
Action: Correct the indicated parameter value and try again.
-
ORA-30686: no dispatcher accepted TCP/IP connection request
-
Cause: A connection had to be routed through a local socket rather than a dispatcher. When this occurs, shared servers are less beneficial because the session that owns the socket cannot relinquish the process until the socket is closed. The most likely cause is that no dispatcher is configured for protocol=tcp.
-
Action: To improve the scalability of your configuration, configure a dispatcher for protocol=tcp. To route these particular connections through a particular set of dispatchers, you can specify presentation=kgas. However, if you haven't done so, any protocol=tcp dispatcher will be used.
-
ORA-30687: session terminated by debugger
-
Cause: Your program's execution has been stopped by the debugger. This can occur because of an explicit request to do so sent by the debugger, or because the debugger disconnected without first telling Oracle to let your program continue to run after the disconnection. To stop your program completely, Oracle needs to fully terminate the process.
-
Action: This is in response to a debugger request; it is not an error. No action required.
-
ORA-30688: maximum program calling depth exceeded
-
Cause: Your program contains a set of calls that are too deep to be handled. Only transitions between the different execution engines (SQL, PL/SQL, and Java) count in reaching this limit; calls within the same engine don't count.
-
Action: Restructure your program so as to not call so deeply. Perhaps some recursion can be replaced with iteration.
-
ORA-30731: scope constraint not allowed on nested table column when the nested table is being created
-
Cause: An attempt was made to define a scope constraint on a nested table column when the nested table is being created.
-
Action: Do not specify a scope constraint on a nested table column when creating it. Instead, specify it using the ALTER TABLE statement.
-
ORA-30737: cannot create subtable of a type which is not a subtype of the type of the supertable
-
Cause: An attempt was made to create a subtable(subview) of a type which is not a subtype of the type of the super object.
-
Action: Change the type of the subtable to be a subtype of the superobject's type and then retry the operation.
-
ORA-30740: cannot grant UNDER privilege on this object
-
Cause: The user tried to grant UNDER privilege on an object that is not one of the following : non final object type, object table of non final type, object view of non final type.
-
Action: Ensure that the UNDER privilege is granted on a valid object.
-
ORA-30742: cannot grant SELECT privilege WITH HIERARCHY OPTION on this object
-
Cause: The user tried to grant SELECT privilege WITH HIERARCHY OPTION on an object that is not one of the following : object table of non final type, object view of non final type.
-
Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is granted on a valid object.
-
ORA-30751: cannot disable column string from storing objects of type string.string
-
Cause: The user is trying to drop a type from being stored in a substitutable column or table. This error is raised due to one of the following reasons :
- the column is enabled to store instances of some subtype of the type being dropped.
- the column is enabled to store instances of only one type
-
Action: Fix the cause of the error and retry the operation.
-
ORA-30756: cannot create column or table of type that contains a supertype attribute
-
Cause: The user tried to create a column or table of an object type that contains a supertype attribute. This is not supported because it leads to infinite recursion in our current storage model. Note that creating a column of a type implies that we create columns corresponding to all subtype attributes as well.
-
Action: Change the type definition to contain a supertype REF attribute instead of the supertype object attribute.
-
ORA-30757: cannot access type information
-
Cause: Either a subtype was created and operations performed with this new type while the session was in progress, or the type information was unpinned from the object cache.
-
Action: Commit necessary changes, end the user session, reconnect again and re-try the object operations. If problem persists, contact your Oracle Support representative.
-
ORA-30772: opaque types do not have default constructors
-
Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors.
-
Action: Add user-defined constructors to opaque type, or specify a member or static method for the opaque type.
-
ORA-30934: 'string' (string node) cannot be inserted in parent 'string' (string node)
-
Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document
-
Action: Insert only child nodes that make sense for this node type
-
ORA-30937: No schema definition for 'string' (namespace 'string') in parent 'string'
-
Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used.
-
Action: Only insert elements and attributes declared in the schema. Check to make sure that xsi:type (if used) is specified first.
-
ORA-30938: No prefix defined for namespace 'string' (particle string)
-
Cause: An XML namespace mapping (xmlns:<prefix>=<namespace URL>) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document.
-
Action: Add an xmlns attribute definition (attribute name="xmlns:prefix" and value="namespace URL") to the current XMLType document. The safest place to add this attribute is in the root node of the document to ensure that the mapping will be in scope.
-
ORA-30939: Order violation: Element 'string' may not follow element 'string'
-
Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information
-
Action: Insert elements only in the order specified in the schema
-
ORA-30942: XML Schema Evolution error for schema 'string' table string column 'string'
-
Cause: The given XMLType table/column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one
-
Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action
-
ORA-30943: XML Schema 'string' is dependent on XML schema 'string'
-
Cause: Not all dependent schemas were specified and/or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1.
-
Action: Include the previously unspecified schema in the list of schemas and/or correct the order in which the schemas are specified. Then retry the operation.
-
ORA-30944: Error during rollback for XML schema 'string' table string column 'string'
-
Cause: The given XMLType table/column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one
-
Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action
-
ORA-30946: XML Schema Evolution warning: temporary tables not cleaned up
-
Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful
-
Action: If the user needs to remove the temporary tables, use the mapping table to get the temporary table names and drop them.
-
ORA-30990: insufficient privileges to change owner of resource string
-
Cause: An attempt was made to change the <Owner> field of an XML DB resource without sufficient privileges to do so.
-
Action: Switch to SYS before performing the ownership change, or have the intended recipient of the resource perform the transfer.
-
ORA-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string
-
Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.
-
Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to run at its fastest, set db_block_size to 8K.
-
ORA-31040: Property string: XML type (string) not compatible with internal memory type (string)
-
Cause: The XML datatype given is inconsistent with the database datatype, and a conversion cannot be made.
-
Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support.
-
ORA-31041: Property string: Memory type (string) not compatible with database type (string)
-
Cause: The memory type associated with this property is mapped to an incompatible database type, and a conversion cannot be made.
-
Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support.
-
ORA-31043: Element 'string' not globally defined in schema 'string'
-
Cause: The specified element name has not been defined at the top level of the XML schema (i.e. globally). Elements must be defined globally to be the root of an XMLType object.
-
Action: Check the XML schema definition to make sure the specified element name has been defined at the top level.
-
ORA-31045: Cannot store more than string extras outside the root XML node
-
Cause: An attempt was made to store more than the maximum number of XML extras (e.g. comments and processing instructions) either before or after the document's root node.
-
Action: Keep the number of extras outside the root node below the maximum.
-
ORA-31050: Access denied
-
Cause: The requested access privileges have not been granted to the current user. User must be granted privileges prior to resource access.
-
Action: Check the set of requested access privileges to make sure that they are included in the set of access privilges granted to the user.
-
ORA-31068: updateXML expected data format [string] instead of [string]
-
Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data.
-
Action: Use CREATEXML or getStringVal to coerce the new data to the proper format.
-
ORA-31089: schema "string" does not target namespace "string"
-
Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.
-
Action: Make sure that all schemas referenced via include definitions target the same namespace as the parent schema. Further make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema.
-
ORA-31091: empty string specified as a SQL name
-
Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
-
Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again.
-
ORA-31092: invalid SQL name "string"
-
Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
-
Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied.
-
ORA-31094: incompatible SQL type "string" for attribute or element "string"
-
Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.
-
Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.
-
ORA-31095: cannot generate string : "string.string" already exists
-
Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used.
-
Action: Use different names for types/tables or use the NOGEN mode so that schema compiler does not generate new types/tables.
-
ORA-31158: schema "string" currently being referenced
-
Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.
-
Action: Ensure all references to this schema in this session are released and try the operation again.
-
ORA-31160: max substitution group size string exceeded by "string" (string) for head element "string" (string)
-
Cause: The maximum limit on nested substitution groups has been exceeded by an element.
-
Action: Delete specified schema and re-register it after removing the offending substitution element.
-
ORA-31163: element or attribute "string" has invalid attribute value "string" (should be "string")
-
Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type
-
Action: Remove the mismatched attribute values from the offending element or attribute
-
ORA-31164: cannot load object-relational XML attribute using direct path
-
Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path.
-
Action: Perform the load with conventional path mode.
-
ORA-31165: cannot load object-relational XML attribute using direct path
-
Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path.
-
Action: Perform the load with conventional path mode.
-
ORA-31180: DOM Type mismatch in invalid PL/SQL DOM handle
-
Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl/sql handle was reused, or the original document is no longer available.
-
Action: Ensure that the pl/sql handle for the target node is valid and try the operation again.
-
ORA-31190: Resource string is not a version-controlled resource
-
Cause: Either one of the following is the cause:
- Checkout is requested for a resource that isn't under version control". Only version-controlled resource can be checked out.
- Checkout is requested for a row of a non-versioned table.
-
Action: put the resource under version-control before checking out.
-
ORA-31195: XML node 'string' (type=string) does not support this operation
-
Cause: The given node's type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
-
Action: Use a valid node type for the operation.
-
ORA-31196: XML nodes over string in size cannot be printed
-
Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
-
Action: Use getClobVal() or getStringVal() to print the Document.
-
ORA-31197: Error in processing file string
-
Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack
-
Action: Ensure that the specified file is correct. Look at the next error on the stack and take appropriate action.
-
ORA-31219: DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
-
Cause: There has been an error in the DBMS_LDAP explode_dn or explode_rdn operation.
-
Action: Please check the LDAP notypes value that you use for LDAP explode_dn or explode_rdn operation, or report the error number and description to Oracle Support.
-
ORA-31404: all input parameters are null
-
Cause: All input parameters are null. At least one property must be altered.
-
Action: Call the procedure again, making sure that all the required parameters have been specified. Ensure that at least one parameter is not null. Refer to user documentation for the correct way of calling this procedure.
-
ORA-31405: cannot make changes while change set string is advancing
-
Cause: The change set is currently advancing. Change sources related to an advancing change set cannot be altered. Change tables related to the advancing change set cannot be created, altered or dropped. Some or all the parameters of the change set cannot be altered while the set is advancing.
-
Action: Wait until the change set has finished advancing, then reissue the command. If altering the change set, only the advance_enable parameter can be altered during an advance.
-
ORA-31406: change source string is referenced by a change set
-
Cause: The operation cannot complete because this change source is referenced by one or more change sets.
-
Action: Drop the change sets first, then re-issue the command. May have to drop some change tables before the change sets are dropped.
-
ORA-31407: end_date must be greater than the begin_date
-
Cause: The end data of the change set is earlier than the begin date. The end date must always be later in time than the begin date, so that the duration between the begin and end dates is a positive amount of time.
-
Action: Change the begin date and/or the end date, so that the end date is later than the begin date.
-
ORA-31408: invalid value specified for begin_scn or end_scn
-
Cause: The begin_scn was not greater than zero. The end_scn was less than zero. The end_scn was less than the begin_scn.
-
Action: Check the values of both begin_scn and end_scn. Correct them to make sure that they form a legal SCN range. An end_scn value of zero indicates an infinite scn range.
-
ORA-31412: change set string is disabled and cannot be advanced
-
Cause: The specified change set is disabled. The change set needs to be enabled for the operation to succeed.
-
Action: Determine why the change set is disabled and correct this condition. Alter the change set specifying 'y' for advance_enable then retry the operation.
-
ORA-31413: change set string is currently being advanced
-
Cause: An advance operation is in progress for this change set and we only allow one at a time.
-
Action: Since the change set is currently being advanced, the best action is to wait for it to finish advancing. Only one caller at a time can advance the change set. Check for the cause of long running advance operations.
-
ORA-31415: change set string does not exist
-
Cause: Specified change set does not exist or the user does not have access to the publications in that change set. The name specified did not match the name of any existing change set. Certain privileges are required to access the publications within that change set.
-
Action: Check the name and call the procedure again, with the name of an existing change set. Contact the publisher or database administrator if user privileges are required to access the publications in the change set.
-
ORA-31417: column list contains control column string
-
Cause: Reserved column name was specified in a column list or column type parameter.
-
Action: Control columns are selected with separate parameters. If you did not want a control column, then change the name of the specified column so that it does not conflict with a reserved column name.
-
ORA-31420: unable to submit the purge job
-
Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed.
-
Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, contact Oracle.
-
ORA-31424: change table has active subscriptions
-
Cause: The change table is subscribed to, so it cannot be dropped.
-
Action: Do not drop a change table while there are active subscribers. If this is an emergency, use the FORCE parameter. This will forcibly drop the change table out from under all subscribers.
-
ORA-31427: publication string already subscribed
-
Cause: The subscription already contained this publication.
-
Action: Check the values of subscription_name and publication_id. Check any other subscribe calls to see if they subscribe to columns that are shared among more than one publication on the same source table. Do not attempt to subscribe to the same publication more than once in the same subscription. Use the publication_id variant of the SUBSCRIBE call if needed to specify precise publications.
-
ORA-31428: no publication contains all the specified columns
-
Cause: One or more of the specifed columns cannot be found in a single publication.
-
Action: Change the subscription request to select only columns that are in the same publication. Consult the USER_PUBLISHED_COLUMNS view to see current publications.
-
ORA-31441: table is not a change table
-
Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a table that is not a CHANGE table. This can also occur when a CHANGE table object has been orphaned. CHANGE tables can become orphaned after a CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE.
-
Action: Check spelling. If error was due to an incorrect name, then retry the procedure using the correct name. To drop a table that is not a CHANGE table, or an orphaned CHANGE table, use the DROP TABLE DDL command instead.
-
ORA-31456: error executing a procedure in the DBMS_CDC_UTILITY package
-
Cause: An internal attempt to invoke a procedure within the DBMS_CDC_UTILITY package failed.
-
Action: Check the trace logs for more information. Ensure that the package has been installed successfully. Try issuing a DESCRIBE command from SQL on the package. If it fails, then try reinstalling the package. If it succeeds then try invoking one of the procedures from SQL.
-
ORA-31459: system triggers for DBMS_CDC_PUBLISH package are not installed
-
Cause: One or more required system triggers are not installed. These triggers are required for the proper operation of Change Data Capture. Operations on Change tables cannot continue.
-
Action: Install or reenable the triggers, or reinstall the package.
-
ORA-31460: logfile location string is not an existing directory
-
Cause: The directory specification for logfile location for the change source, does not correspond with an existing directory, or the directory was not accessible.
-
Action: 1. Create the directory if it does not exist. If the directory does exist, change the file system permissions so the directory can be accessed. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles
-
ORA-31461: logfile location string contains no files that match pattern string
-
Cause: The directory specification for logfile location for the change source, does not contain any files whose names pattern-match the logfile_suffix.
-
Action: 1. Make sure that the logfile location contains logfiles whose names match the logfile_suffix pattern for the change set. OR 2. perform ALTER CHANGE SOURCE and change the logfile_suffix such that it matches the names of existing logfiles in the directory
-
ORA-31463: logfile location string is an empty directory
-
Cause: The directory specification for logfile location for the change source, is an empty directory
-
Action: 1. Make sure it is the correct location of the logfiles. If it is, make sure the directory contains logfiles. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles
-
ORA-31465: cannot obtain a lock on the subscription
-
Cause: A timeout occurred while trying to place a lock on the subscription. Another session had already acquired the lock on the subscription.
-
Action: Ensure the subscription name is correct and correct it if necessary. If it is already correct, try the operation again after the session holding the lock has released it.
-
ORA-31466: no publications found
-
Cause: Did not find any publications that matched the input parameters or the user does not have the privileges to access the specified publication.
-
Action: Check the input parameters on the call to SUBSCRIBE. Validate that the proposed source table has been published by checking the USER_PUBLICATIONS view for that source table. Contact the publisher if user privileges are required to access the publication. Retry the command with correct security or publication information.
-
ORA-31467: no column found in the source table
-
Cause: The OBJECT_ID flag was set to 'Y' on the call to CREATE_CHANGE_TABLE and change table belongs to the synchronous change set. The corresponding object column was not detected in the source table.
-
Action: Create the change table with the OBJECT_ID flag set to 'N' or investigate why the object column is not in the source table and add it to the source table.
-
ORA-31468: cannot process DDL change record
-
Cause: The change set has stop_on_ddl enabled and was trying to process a DDL change record.
-
Action: Check the alert log to find out what the DDL record contained. Make any necessary changes to the change tables. Call ALTER_CHANGE_SET with recover_after_error and remove_ddl set to 'Y'.
-
ORA-31469: cannot enable Change Data Capture for change set string
-
Cause: The change set has reached the specified limit that was set up by the CREATE_CHANGE_SET command.
-
Action: Check the alert log to find out whether capture, apply or both reached the limit. Once apply reaches its limit, the change set is permanently disabled. Create a new change set with new limits to continue capturing data.
-
ORA-31470: asynchronous change tables must contain the RSID$ column
-
Cause: If creating an asynchronous change table, the RSID was set to 'N'. If altering an asynchronous change table with an operation parameter of 'DROP' RSID was set to 'Y'.
-
Action: When creating asynchronous change tables, always specify 'Y' for the RSID parameter. When altering asynchronous change tables always specify 'N' for RSID.
-
ORA-31472: Importing Change Data Capture version string.string is too new
-
Cause: An attempt was made to Import a file that was exported by a newer version of Oracle than the target instance.
-
Action: If possible, re-export the file using a version of export that matches the import target. Objects can not be imported into previous versions of Oracle that did not support them.
-
ORA-31475: redo log catalog contains no metadata for the source table
-
Cause: While advancing a change set, an CDC attempted to query the LogMiner dictionary system tables to obtain the columns from the source table. The query returned no rows. This may be because none of the redo logs contains a catalog, or it may be an internal error.
-
Action: First, verify that the source system contains the source table. execute dbms_logmnr_d.build procedure to populate the redos log with logminer dictionary information. If this has been done and the problem persists, then contact Oracle Corporation
-
ORA-31476: a change table data column is missing from the source table
-
Cause: While advancing a change set, an CDC determined that at least one of the data columns in a change table does not match the name of any of the columns in the source table. The source table column listis stored in dictionary table SYSTEM.LOGMNR_OBJ$
-
Action: Make sure that all of the data columns of the change table have the same names as the corresponding columns in the source table, and that all the columns exist in the source table.
-
ORA-31477: could not detach LogMiner session during cleanup
-
Cause: Failure during detach from a LogMiner session during advance of an asynchronous change set. This is an internal error. This exception is raised when a previous exception occurred during the internal protocol with LogMiner, after which Change Data Capture attempted to detach the LogMiner session as part of recovery. The detach session also failed
-
Action: Contact Oracle Corporation
-
ORA-31478: could not detach LogMiner session after change set advance
-
Cause: Failure during detach from a LogMiner session after successful advance of an asynchronous change set. This is an internal error. This exception is raised when an asynchronous change set has been successfully advanced but CDC was unable to detach from the LogMiner session
-
Action: Contact Oracle Corporation
-
ORA-31495: error in synchronous change table on "string"."string"
-
Cause: There was an error originating from this synchronous change table. One possible cause is that schema redefinition has occurred on the source table and one or more columns in the change table are now a different type than corresponding source columns. Another possible cause is that there is a problem accessing the synchronous change table.
-
Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop and recreate the synchronous change table.
-
ORA-31496: must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
-
Cause: An attempt was made to use the SQL command DROP TABLE for change tables, but DROP TABLE is not supported for change tables.
-
Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead of the DROP TABLE command.
-
ORA-31497: invalid value specified for first_scn
-
Cause: The first_scn was not greater than zero or was less than the previous value of first_scn.
-
Action: Check the value of first_scn. Correct it to make sure it is an integer greater than zero and greater than any previous value for this change source.
-
ORA-31504: cannot alter or drop predefined change source
-
Cause: The caller attempted to alter or drop one of the predefined change sources HOTLOG_SOURCE or SYNC_SOURCE.
-
Action: Do not attempt to alter or drop a predefined change source or correct call to supply the name of a user-created change source.
-
ORA-31508: invalid parameter value for synchronous change set
-
Cause: A parameter value was specified that is not supported for synchronous change sets.
-
Action: Correct the call to supply only valid parameter values for a synchronous change set. Synchronous change sets only support the default values for the following parameters: begin_scn, end_scn, begin_date, end_date, stop_on_ddl, supplemental_processes.
-
ORA-31509: publication does not exist
-
Cause: The specified publication did not exist or it subscribed to a publication that no longer exists.
-
Action: Recheck the publication or subscription specified. Either call the procedure again with an existing publication or create a new subscription that only subscribes to existing publications.
-
ORA-31513: unsupported column type specified in change table
-
Cause: A source column of an unsupported type was specified for inclusion in a change table. Columns types of LOB or LONG are not currently supported for change capture.
-
Action: Change the column list so that it does not include columns of LOB or LONG types.
-
ORA-31514: change set string disabled due to capture error
-
Cause: This change set has encountered a capture error and was disabled.
-
Action: Contact the change set's publisher to request that the capture error be resolved. Subscriptions using this change set cannot be activated or have their subscription windows extended or purged until the capture error is resolved.
-
ORA-31518: change column string already exists in CDC change table string.string
-
Cause: A column in a Change Data Capture change table intended for import was already present in the change table.
-
Action: Either verify that the change table contains the desired columns or drop the change table and perform the import again.
-
ORA-31520: CDC subscription string already subscribes to publication ID string
-
Cause: A Change Data Capture subscription intended for import already subscribed to a publication.
-
Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again.
-
ORA-31521: CDC subscription string already subscribes to publication ID string column string
-
Cause: A Change Data Capture subscription intended for import already subscribed to a published column.
-
Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again.
-
ORA-31522: could not find Streams object string for CDC change set string
-
Cause: An underlying Streams capture, apply, or queue was missing for an imported Change Data Capture change set.
-
Action: Drop the imported change set because it is invalid. Retry the import, ensuring that STREAMS_CONFIGURATION=y is specified.
-
ORA-31523: could not find change source string for CDC change set string
-
Cause: The change source was missing for an imported Change Data Capture change set.
-
Action: Drop the imported change set because it is invalid. Verify that the schema containing the missing change source was included in the original export. If needed, perform the export again, including the schema of the missing change source.
-
ORA-31524: could not find change set string for CDC change table string.string
-
Cause: The change set was missing for an imported Change Data Capture change table.
-
Action: Drop the imported change table because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set.
-
ORA-31525: could not find column string in CDC change table string.string
-
Cause: A column was missing for an imported Change Data Capture change table.
-
Action: It is likely that this table existed before the import operation and import did not overwrite it. Determine whether the imported change table should supercede the original table. If so, drop the original table and retry the import. If not, the change table must have a different name in order to be imported.
-
ORA-31526: could not find source table string.string for CDC change table string.string
-
Cause: The source table was missing or was not set up correctly for an imported Change Data Capture change table. A synchronous change table requires the source table to exist and have the Change Data Capture trigger defined on it. An asynchronous change table requires table rules to be defined for the source table.
-
Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the source table. If change table is asynchronous, ensure that STREAMS_CONFIGURATION=y is specified for the import.
-
ORA-31527: could not find source column string for CDC change table string.string
-
Cause: A source column was missing for an imported Change Data Capture change table.
-
Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the missing source table.
-
ORA-31528: could not find change set string for CDC subscription string
-
Cause: The change set was missing for an imported Change Data Capture subscription.
-
Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set.
-
ORA-31529: could not find publication for CDC subscriber view string.string
-
Cause: A publication was missing for an imported Change Data Capture subscription.
-
Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing publication was included in the original export. If needed, perform the export again, including the schema of the missing publication.
-
ORA-31530: could not find published column string for CDC subscriber view string.string
-
Cause: A published column was missing for an imported Change Data Capture subscription.
-
Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing published column was included in the original export. If needed, perform the export again, including the schema of the missing published column.
-
ORA-31531: could not find column string in CDC subscriber view string.string
-
Cause: A column was missing in a subscriber view for an imported Change Data Capture subscription.
-
Action: It is likely that this view existed before the import operation and import did not overwrite it. Determine whether the imported subscriber view should supercede the original view. If so, drop the original view and retry the import. If not, the subscriber view must have a different name in order to be imported.
-
ORA-31602: parameter string value "string" in function string inconsistent with string
-
Cause: The parameter value is inconsistent with another value specified by the program. It may be inconsistent with the object type associated with the OPEN context, or it may be of the wrong datatype (a boolean rather than a text string or vice versa).
-
Action: Correct the program
-
ORA-31605: the following was returned from string in routine string: LPX-number: string
-
Cause: An LPX routine (XML/XSL processing) returned an internal error number to its PL/SQL wrapper routine in facility KUX which provides the implementation for package UTL_XML.
-
Action: Look up the LPX error number and follow its corrective action.
-
ORA-31610: cannot call this function from a non-master process
-
Cause: Called a Data Pump process model function from a process which is not a master process.
-
Action: Create a master process first. Then call the function from the master process. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31613: Master process string failed during startup.
-
Cause: The master process whose name is listed failed during startup.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31625: error changing username from string to string
-
Cause: An error occurred when attempting to change the username.
-
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31626: job does not exist
-
Cause: An invalid reference to a job which is no longer executing, is not executing on the instance where the operation was attempted, or that does not have a valid Master Table. Refer to any following error messages for clarification.
-
Action: Start a new job, or attach to an existing job that has a valid Master Table.
-
ORA-31628: error getting worker process exception
-
Cause: Attempt to get a worker process exception failed.
-
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31631: privileges are required
-
Cause: The necessary privileges are not available for operations such as: restarting a job on behalf of another owner, using a device as a member of the dump file set, or ommiting a directory object associated with any of the various output files. Refer to any following error messages for additional information.
-
Action: Select a different job to restart, try a different operation, or contact a database administrator to acquire the needed privileges.
-
ORA-31632: master table "string.string" not found, invalid, or inaccessible
-
Cause: A Master Table is required but no such table exists, or the content is not consistent with that of a valid Master Table, or the table is not accessible. Refer to any following error messages for clarification.
-
Action: Make sure a valid Master Table exists, and eliminate any problems indicated by the following error messages.
-
ORA-31633: unable to create master table "string.string"
-
Cause: Job creation failed because a Master Table and its indexes could not be created, most commonly due to the pre-existance of a table with the same name (job name) in the user schema. Refer to any following error messages for clarification.
-
Action: Select a different job name, DROP the existing table, or eliminate any problems indicated by the following error messages.
-
ORA-31634: job already exists
-
Cause: Job creation or restart failed because a job having the selected name is currently executing. This also generally indicates that a Master Table with that job name exists in the user schema. Refer to any following error messages for clarification.
-
Action: Select a different job name, or stop the currently executing job and re-try the operation (may require a DROP on the Master Table).
-
ORA-31635: unable to establish job resource synchronization
-
Cause: A lock used in synchronizing Data Pump resources during job creation and deletion could not be obtained during job creation. This indicates that a process for some other Data Pump job has not released the lock due to an internal error.
-
Action: Eliminate the processes for any failed Data Pump job and try to create the new job again. If the error continues to occur, contact Oracle Customer Support and report the error.
-
ORA-31639: unexpected data found
-
Cause: The Master Table or Data Pump file contents appear invalid. The table or file may not have been produced by a Data Pump job, or they may have been corrupted.
-
Action: Select a different job name (Master Table) or replace the table or file with one produced by Data Pump.
-
ORA-31644: unable to position to block number string in dump file "string"
-
Cause: Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system.
-
Action: Take appropriate action based on the device messages.
-
ORA-31648: Timeout before master process string finished initialization.
-
Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31649: Master process string violated startup protocol.
-
Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31650: timeout waiting for master process response
-
Cause: After creating the job infrastructure and sending the initial message to the master process, it failed to respond in the allotted time and most likely aborted during startup.
-
Action: Retry the open or attach request. Contact Oracle Customer Support if the problem persists.
-
ORA-31653: unable to determine job operation for privilege check
-
Cause: Failure trying to determine the operation of the current job in order to test for appropriate privileges.
-
Action: Retry in case it's an intermittent failure. If it still fails, detach, reattach, and retry the call. Contact Oracle Customer Support if the problem persists.
-
ORA-31655: no data or metadata objects selected for job
-
Cause: After the job parameters and filters were applied, the job specified by the user did not reference any objects.
-
Action: Verify that the mode of the job specified objects to be moved. For command line clients, verify that the INCLUDE, EXCLUDE and CONTENT parameters were correctly set. For DBMS_DATAPUMP API users, verify that the metadata filters, data filters, and parameters that were supplied on the job were correctly set.
-
ORA-31664: unable to construct unique job name when defaulted
-
Cause: The job name was defaulted, and the name creation algorithm was unable to find a unique job name for this schema where the table name (for the master table) didn't already exist.
-
Action: Specify a job name to use or delete some of the existing tables causing the name conflicts.
-
ORA-31666: Master process string had an unhandled exception.
-
Cause: A Data Pump process model master process had an unhandled exception condition.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31668: Timeout before worker process string finished initialization.
-
Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31669: Worker process string violated startup protocol.
-
Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31670: Username argument must be specified and non-null.
-
Cause: Called change user with a NULL username or a null string.
-
Action: Specify a valid username argument. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31671: Worker process string had an unhandled exception.
-
Cause: A Data Pump process model worker process had an unhandled exception condition.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31672: Worker process string died unexpectedly.
-
Cause: A Data Pump process model worker process died unexpectedly, so PMON is cleaning up the process.
-
Action: Check your system for problems. Check the trace file for the process, if one was created, for any additional information. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31673: worker process interrupt for normal exit by master process
-
Cause: A worker process was requested to clean up and exit because the master process is doing a normal exit.
-
Action: If this error occurs from a Data Pump client (e.g. expdp or impdp). it means that the master process for the operation exited prematurely. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31674: worker process interrupt for unhandled exception in master process
-
Cause: A worker process was requested to clean up and exit because an unhandled exception occurred in the master process.
-
Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation had an unhandled exception. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31675: worker process interrupt for unexpected death of master process
-
Cause: A worker process was requested to clean up and exit (signaled by PMON, doing cleanup because the master process died unexpectedly).
-
Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation died unexpectedly. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31676: illegal value for number of workers, string
-
Cause: Called create worker processes with an illegal number of workers specified.
-
Action: Make sure that the number of workers value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp) and you specified the parallel parameter, try the operation again with a smaller value for the parallel parameter. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31686: error creating worker processes
-
Cause: Setup to create worker processes failed.
-
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31687: error creating worker process string with worker id string
-
Cause: Attempt to create the listed worker process failed.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31688: Worker process string failed during startup.
-
Cause: The worker process whose name is listed failed during startup.
-
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31689: illegal value for base worker id, string
-
Cause: Called create worker processes with an illegal base worker id value specified.
-
Action: Make sure that the base worker id value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31690: Process name buffer size must be specified and must be greater than 0.
-
Cause: Called get worker exception and either specified NULL or 0 for the buffer size argument.
-
Action: Be sure to specify a buffer size that is big enough to hold the worker process name (e.g. 30 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-31698: Error stack buffer size must be specified and must be greater than 0.
-
Cause: Called get worker exception and either specified NULL or 0 for the error stack size argument.
-
Action: Be sure to specify am error stack buffer size that is big enough to hold the error stack string (e.g. 4096 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
-
ORA-32004: obsolete and/or deprecated parameter(s) specified
-
Cause: One or more obsolete and/or parameters were specified in the SPFILE or the PFILE on the server side.
-
Action: See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE.
-
ORA-32019: The parameter SPFILE cannot be updated in the server parameter file.
-
Cause: An attempt was made to update the parameter SPFILE in the server parameter file.
-
Action: Convert the server parameter file into a parameter file and then add the parameters needed and recreate the server parameter file.
-
ORA-32021: parameter value longer than string characters
-
Cause: An attempt was made to alter a parameter value but the number of characters in the parameter value was longer than the allowed maximum. For a list parameter, one of the values in the list was longer than the allowed maximum.
-
Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length.
-
ORA-32022: parameter value longer than string characters
-
Cause: An attempt was made to alter a parameter value but the combined length of all the parameter values was more than the allowed maximum.
-
Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length.
-
ORA-32027: There is no string column with the matching type in string.string.
-
Cause: An attempt was made to set the audit table to a table or view object that does not have a column with the same name and type as the one in the audit table.
-
Action: Specify a valid table or view object for the audit table option.
-
ORA-32034: unsupported use of WITH clause
-
Cause: Inproper use of WITH clause because one of the following two reasons:
1. nesting of WITH clause within WITH clause not supported yet
2. For a set query, WITH clause can't be specified for a branch.
3. WITH clause can't sepecified within parentheses.
-
Action: correct query and retry
-
ORA-32106: array fetch not allowed without setBuffer on all columns
-
Cause: The setBuffer method was not called for all column postions and the next method was called to fetch more than one row.
-
Action: Call the setBuffer method for all column positions if next is to to be called to fetch more than one row.
-
ORA-32131: bind data type cannot be changed
-
Cause: The setXXX method is called again with a different data type than originally specified, or the setXXX method is called for a subsequent iteration without being called before the first iteration.
-
Action: Call the setXXX method with the same data type as done before the first iteration. If no setXXX method was called for this parameter postion the first iteration, then make sure that a setXXX method is called before the first addIteration method is called.
-
ORA-32300: cannot drop a secondary materialized view "string"."string"
-
Cause: An attempt was made to drop a materialized view of a nested table column's storage table.
-
Action: Drop the materialized view that contains the nested table column. This will implicitly drop all secondary materialized views.
-
ORA-32303: mviews with user-defined types cannot reference multiple master sites
-
Cause: For materialized views with user-defined types, the definition query cannot reference tables from different master sites.
-
Action: Do not create materialized views with user-defined types referencing multiple master sites.
-
ORA-32306: updatable materialized views with user-defined types must use SELECT *
-
Cause: An attempt was made to create an updatable materialized view with user-defined types where the definition query did not use SELECT * at the topmost level.
-
Action: Rewrite the definition query so that SELECT * is used at the topmost level.
-
ORA-32307: must use FROM ONLY clause when referencing an object table
-
Cause: An attempt was made to create a materialized view whose definition query references object tables without the FROM ONLY clause.
-
Action: Rewrite the definition query to use the FROM ONLY clause for all the object tables in the query.
-
ORA-32311: materialized view definition query selects an unsupported user-defined type
-
Cause: An attempt was made in the definition query to select an embedded user-defined type, function returning a user-defined type, or a function whose arguments are user-defined types.
-
Action: Rewrite the definition query to exclude these unsupported user-defined types.
-
ORA-32312: cannot refresh a secondary materialized view "string"."string"
-
Cause: An attempt was made to refresh a materialized view of a nested table column's storage table.
-
Action: Refresh the materialized view that contains the nested table column. This will implicitly refresh all secondary materialized views.
-
ORA-32313: REFRESH FAST of "string"."string" unsupported after PMOPs
-
Cause: A Partition Maintenance Operation (PMOP) has been performed on a detail table, and the specified materialized view does not support fast refersh after PMOPs.
-
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
-
ORA-32314: REFRESH FAST of "string"."string" unsupported after deletes/updates
-
Cause: One or more deletes or updates has been performed on one or more of the detail tables referenced by the specified materialized view. This materialized view does not support fast refresh after deletes or updates.
-
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after deletes or updates using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
-
ORA-32315: REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
-
Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletes or updates and direct path insert.
-
Action: Use REFRESH COMPLETE. Note: you can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option.
-
ORA-32316: REFRESH FAST of "string"."string" unsupported after mixed DML
-
Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletes or updates have been performed on multiple detail tables.
-
Action: Use REFRESH COMPLETE. Note: you can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option.
-
ORA-32320: REFRESH FAST of "string"."string" unsupported after container table PMOPs
-
Cause: A Partition Maintenance Operation (PMOP) has been performed on the materialized view, and no materialized view supports fast refersh after container table PMOPs.
-
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
-
ORA-32321: REFRESH FAST of "string"."string" unsupported after detail table TRUNCATE
-
Cause: A detail table has been truncated and no materialized view supports fast refersh after a detail table has been truncated
-
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after TRUNCATE using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
-
ORA-32331: type "string"."string" is incompatible with the master site
-
Cause: A type used by the materialized view was found to be incompatible with its coressponding type on the master site. This could be because the type does not exist on the master site or has been evolved to a different version from that on the materialzied view site.
-
Action: Make sure that the types used by the materialized view are the same on both the materialized view and master sites.
-
ORA-32332: cannot refresh materialized view "string"."string" as type evolution has occured
-
Cause: The types used by the materialized view or its master tables have been evolved.e29250.msg@@/main/308e29250.msg@@/main/308
-
Action: Ensure that the types used by the materialized view have been evolved to the same version at both the master and materialized sites. Then, before refreshing the materialized view, evolve the materialized view using ALTER MATERIALIZED VIEW.
-
ORA-32336: cannot use USING NO INDEX to create materialized view "string"."string"
-
Cause: The USING NO INDEX option was specified to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view.
-
Action: Do not use the USING NO INDEX option to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view.
-
ORA-32337: cannot alter materialized view with pending changes refresh on commit
-
Cause: There are some pending changes in the detail tables
-
Action: Execute an on-demand refresh on the materialized view to synchronize the data between the materialized view and the detail tables and then issue an ALTER MATERIALIZED VIEW statement.
-
ORA-32339: cannot alter materialized view with the PMOP
-
Cause: the materialized view is not allowed to have destructive PMOPS such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag of i_am_a_refresh should be set first.
-
Action: execute set_i_am_a_refresh first before alter materialized view with the PMOP.
-
ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
-
Cause: The dependent object(s) of the materialized view may have changed. The materialized view may no longer be valid.
-
Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of the materialized view in catalog views.
-
ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement
-
Cause: An error exists in the materialized view definition. As a result, the materialized view statement could not be explained.
-
Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED VIEW statement, then also check the PARAMETERs specified for the materialized view.
-
ORA-32400: cannot use object id columns from materialized view log on "string"."string"
-
Cause: The materialized view log either does not have object id columns logged, or the timestamp associated with the object id columns is more recent than the last refresh time.
-
Action: A complete refresh is required before the next fast refresh. Add object id columns to the materialized view log, if required.
-
ORA-32403: cannot use new values from mv log on "string"."string"
-
Cause: The materialized view log either does not have new values logged, or the timestamp associated with the new values columns is more recent than the last refresh time.
-
Action: Perform a complete refresh is required before the next fast refresh.
-
ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database
-
Cause: A snapshot log that utilizes Change Data Capture is being imported to a database where Change Data Capture has not been enabled.
-
Action: First enable Change Data Capture on the database then retry the import.
-
ORA-32577: username must be SYS or SYSTEM
-
Cause: A user name of SYS or SYSTEM was not specified when providing a password in the CREATE DATABASE statement.
-
Action: Only passwords for the SYS and SYSTEM users can be provided in the CREATE DATABASE statement. Re-issue the statement with passwords for users SYS or SYSTEM.
-
ORA-32580: both SYS and SYSTEM passwords must be provided
-
Cause: Passwords for both the SYS and SYSTEM users were not provided in the CREATE DATABASE statement. If one of the passwords was provided, then both should be provided.
-
Action: Re-issue the CREATE DATABASE statement with a password for both the SYS and SYSTEM users.
-
ORA-32582: table function with left correlation to a table cannot also be left outer-joined to the table
-
Cause: A table function T2 contains a reference to a table T1. T2 is also left outer-joined to T1. This is not allowed.
-
Action: Remove the reference to T1 from T2 or remove the left outer-join specification (+).
-
ORA-32583: query passed to table function has wrong number of elements in select list
-
Cause: The query used as an input to a table function which takes a a ref cursor as argument has wrong number of elements in the select list which does not correspond to the elements in ref cursor. The ref cursor mentioned here refers to the one referenced in order by parition clauses. This is not allowed.
-
Action: Make sure that the select list of the query matches the ref cursor columns as defined in the function.
-
ORA-32586: multiple specification of a supplemental logging attribute
-
Cause: The primary key, unique index, foreign key or all column supplemental logging attribute can be specified at most once in a create/alter ddl.
-
Action: Rewrite the Create/Alter DDL with single occurence of the offending supplemental logging attribute.
-
ORA-32589: unable to drop minimal supplemental logging
-
Cause: Minimal supplemental logging could not be dropped as one of primary key, foreign key, unique or all column supplemental logging is enabled at the database level.
-
Action: Use V$DATABASE to determine the databasewide supplemental logging directives. Minimal supplemental logging could be dropped if and only if no other databasewide supplemental logging directives are enabled.
-
ORA-32630: multiple assignment in automatic order MODEL
-
Cause: A MODEL cell was updated on the same measure in multiple MODEL rules. Multiple assignment is not allowed in automatic order MODELs as it causes in ambiguity and nondeterminism.
-
Action: Use sequential order MODEL or rewrite the rule to avoid this.
-
ORA-32635: not a single cell reference predicate
-
Cause: A predicate that is not a single cell reference predicate was specified where a single cell reference predicate was expected. A single cell reference predicate is either a constant expression or a predicate of the form <dimension_key = constant_expr>
-
Action: Make sure that the predicate is a proper single cell reference. In some cases, you might have to put explicit type conversion operators (or casts) on the constant expression.
-
ORA-32637: Self cyclic rule in sequential order MODEL
-
Cause: A self-cyclic rule was detected in the sequential order MODEL. Sequential order MODELs cannot have self cyclic rules to guarantee that the results do not depend on the order of evaluation of the cells that are updated or upserted.
-
Action: Use ordered rule evaluation for this rule.
-
ORA-32766: instr with negative offset: use varchar semantics on LOBs
-
Cause: The current varchar behavior is different. e.g. instr('abcd', 'cd', -2, 1) returns 3, whereas instr(to_clob('abcd'), 'cd', -2, 1) returns 0, (i.e. no match), because the reverse search starts from offset -2, which points to 'c' and moving backward, i.e. 'd' is ignored. This is symmetric to instr('dcba','dc',2,1), which returns 0.
-
Action: ORACLE uses the same varchar semantics on LOBs (instr). Using the same example, instr(to_clob('abcd'), 'cd', -2, 1) will return 3 as in the varchar case.
-
ORA-32772: BIGFILE is invalid option for this type of tablespace
-
Cause: An attempt was made to create a bigfile tablespace that is dictionary managed or locally managed with manual segment-space management.
-
Action: Either change the tablespace type to locally managed with automatic segment-space management, or create a SMALLFILE tablespace instead.
扫一扫
1730
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
