Wednesday, May 27, 2015

ORacle Error Code form ORA-29373

ORA-29373 resource manager is not on
Cause: An attempt was made to execute an operation that cannot be executed with the resource manager being off.
Action: Turn on the resource manager and try again.

ORA-29374 resource plan string in top-plan string has no plan directives
Cause: A plan was created in the pending area that is an orphan or standalone.
Action: Create plan directives if needed. Otherwise, delete the plan.

ORA-29375 sum of percentages string for level string, plan string exceeds string
Cause: The sum of percentages for the specified plan, level exceeds 100.
Action: Alter the percentages for the level so that they sum to 100.

ORA-29376 number of consumer groups string in top-plan string exceeds string
Cause: The number of consumer groups in the specified top-plan is more than 32.
Action: Change the top-plan to have no more than 32 consumer groups.

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-29379 resource plan string is involved in a loop in top-plan string
Cause: A loop was discovered while validating a top-plan.
Action: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN, and remove the plan directive that causes the loop.

ORA-29380 resource plan string is currently active and cannot be deleted
Cause: An attempt was made to delete an active plan in the pending area. No changes can be made to active plans.
Action: Delete the plan when it is not in use.

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-29382 validation of pending area failed
Cause: Invalid changes were attempted in the pending area.
Action: See documentation and the error messages that follow this one.

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-29384 number of children for plan string exceeds string
Cause: An attempt was made to create or modify the specified plan, but the plan has more than 32 children.
Action: Make sure the specified plan points to no more than 32 distinct nodes.

ORA-29385 cannot create plan directive from string to string
Cause: An attempt was made to create a plan directive from a plan to itself.
Action: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are different.

ORA-29386 plan or consumer group string is mandatory and cannot be deleted or modified
Cause: An attempt was made to delete or modify the specified mandatory plan or consumer group.
Action: Do not attempt to delete or modify mandatory plans and 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-29389 too many errors during validation
Cause: The number of errors detected during validation is too high.
Action: Perform the necessary actions to remove some errors, and retry validation.

ORA-29390 some resource plans are not part of any top-plan
Cause: An attempt was made to create or modify some plans in the pending area that are not part of any top-plan.
Action: Remove these plans are try validation again.

ORA-29391 string and string must be mandatory to create a mandatory plan directive
Cause: An attempt was made to create a mandatory plan directive where either PLAN or GROUP_OR_SUBPLAN or both were not mandatory.
Action: Re-create these objects as mandatory and then create the plan directive.

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-29394 session id string and serial# string do not exist
Cause: Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM.
Action: Specify valid values from the view V$SESSION.

ORA-29395 cannot set the initial consumer group to string
Cause: An attempt was made to set the initial consumer group of a user to OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group.

ORA-29396 cannot switch group to string
Cause: An attempt was made to switch the consumer group of a user or a session to OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group.

ORA-29397 cannot grant/revoke switch privilege for string
Cause: An attempt was made to grant or revoke the privilege to switch to OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group.

ORA-29398 invalid privilege name specified
Cause: An invalid privilege name was specified as an argument to procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of package DBMS_RESOURCE_MANAGER_PRIVS.
Action: Specify a valid privilege 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 errorstring
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 Oracle9i Data Cartridge Developer's Guide for an explanation of the second error message.

ORA-29500 NAMED keyword is invalid in CREATE JAVA CLASS
Cause: A NAMED keyword was specified in the CREATE JAVA CLASS statement. NAMED keywords are valid only in CREATE JAVA SOURCE or RESOURCE statements.
Action: Remove the NAMED keyword from the CREATE JAVA CLASS statement.

ORA-29501 invalid or missing Java source, class, or resource name
Cause: The required name for a Java source, class, or resource was invalid or missing.
Action: Specify a valid name.

ORA-29502 NAMED keyword required in CREATE JAVA RESOURCE
Cause: The name for a Java resource was not specified. The name must be specified with the NAMED keyword.
Action: Specify a valid name with the NAMED keyword.

ORA-29503 SCHEMA keyword not valid with NAMED keyword
Cause: SCHEMA and NAMED keywords were used together in the same CREATE JAVA command, but only one may be used in a CREATE JAVA command.
Action: Remove either the NAMED or the SCHEMA keyword.

ORA-29504 invalid or missing schema name
Cause: The required schema name was invalid or missing.
Action: Specify a valid schema name.

ORA-29505 AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
Cause: The AS keyword was used in CREATE JAVA CLASS or RESOURCE. The AS keyword is valid only in CREATE JAVA SOURCE.
Action: Use the USING keyword in CREATE JAVA CLASS or RESOURCE.

ORA-29506 invalid query derived from USING clause
Cause: The USING clause did not form a valid query.
Action: Correct the USING clause.

ORA-29507 query derived from USING clause found zero or many rows
Cause: The USING clause defined a query that either did not return any values, or returned more than one value.
Action: Correct the USING clause.

ORA-29508 query derived from USING clause did not select a value of type string
Cause: The USING clause did not form a query that selects a value of the type specified by the term following the USING keyword.
Action: Correct the USING clause.

ORA-29509 incorrectly formed Java binary class definition
Cause: An attempt was made to create a Java class using data expected to be in binary (Java .class) format. The data was found not to be in this format, or to be incorrectly formed.
Action: Correct the definition data.

ORA-29510 name, string.string, already used by an existing object
Cause: A CREATE JAVA command attempted to create a source, class, or resource object with a name that is already in use.
Action: Drop the existing object that is using the desired name, or use a different name for the new object.

ORA-29511 could not resolve Java class
Cause: A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified definition data that could not be resolved, or resolution failed for some referenced class.
Action: Remove the NOFORCE option or remove impediments to resolution.

ORA-29512 incorrectly formed name resolver specification
Cause: A name resolver was not specified in the required form: (( name_pattern , schema_name) ...).
Action: Correct the specification.

ORA-29513 referenced class name too long
Cause: An attempt was made to import a .class file containing a class name of length greater than number. The .class file could not be imported because the referenced class name was too long.
Action: Shorten the referenced class name in the .class file.

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-29515 exit called from Java code with status string
Cause: Java code included a call to java.lang.Runtime.exitInternal.
Action: Do not include this call unless non-local exit is desired.

ORA-29516 Aurora assertion failure: string
Cause: An internal error occurred in the Aurora module.
Action: Contact Oracle Support Services.

ORA-29517 recursive resolution failed for a referenced class
Cause: An attempt to resolve a referenced class failed.
Action: Review the errors for referenced classes and complete the necessary actions to correct them.

ORA-29518 name string resolved to an object in schema string that is not a Java class
Cause: A referenced name was resolved to an object that is not a Java class.
Action: Adjust name resolver or add missing Java class.

ORA-29519 name string resolved via a synonym in schema string to a class with a different name
Cause: A referenced name was resolved to a synonym, which translated to a class whose name does not match the referenced name.
Action: Adjust name resolver or add missing Java class.

ORA-29520 name string resolved to a class in schema string that could not be accessed
Cause: An attempt to access a referenced class failed.
Action: Adjust authorizations or name resolution.

ORA-29521 referenced name string could not be found
Cause: Name resolution failed to find an object with the indicated name.
Action: Adjust name resolver or add missing Java class.

ORA-29522 authorization error for referenced name string.string
Cause: An attempt was made to resolve a class that is not authorized to use the indicated referenced class.
Action: Adjust authorizations or name resolution.

ORA-29523 authorization error for unknown referenced name
Cause: An attempt was made to resolve a class that is not authorized to use a referenced class. The name of the referenced class could not be determined.
Action: Adjust authorizations or name resolution.

ORA-29524 wrong types of arguments in call to 'string'
Cause: A method was called with argument(s) of incompatible type(s).
Action: Adjust caller.

ORA-29525 referenced name is too long: 'string'
Cause: An attempt was made to create a class that references a name longer than 4000 characters. The class could not be created because the name is too long.
Action: Adjust the definition.

ORA-29526 created Java class string"string"
Cause: An informational message, not an error.
Action: No action required.

ORA-29527 created Java source string"string"
Cause: An informational message, not an error.
Action: No action required.

ORA-29528 invalid Java call in trigger string
Cause: The Java method specified in trigger does not exist or cannot be called as used.
Action: Adjust trigger definition.

ORA-29529 invalid function or method call string in trigger string
Cause: The function or method specified in Java trigger call expression could not be resolved.
Action: Adjust trigger definition.

ORA-29530 could not create shortened name for string
Cause: Insert into shortened name translation table failed.
Action: Retry the insert.

ORA-29531 no method string in class string
Cause: An attempt was made to execute a non-existent method in a Java class.
Action: Adjust the call or create the specified method.

ORA-29532 Java call terminated by uncaught Java exception: string
Cause: A Java exception or error was signaled and could not be resolved by the Java code.
Action: Modify Java code, if this behavior is not intended.

ORA-29533 attempt to overwrite class or resource string while defining or compiling string.string
Cause: A class or resource defined by a SQLJ source conflicted with an existing object.
Action: Remove existing object, or modify SQLJ source.

ORA-29534 referenced object string.string could not be resolved
Cause: Name resolution determined that the indicated object is referenced but could not be resolved.
Action: Correct name resolver or address resolution problems in the referenced class, or correct compilation problems in its source.

ORA-29535 source requires recompilation
Cause: The reason the current class object was invalid is recorded with the source object from which it was compiled.
Action: Inspect errors in the source object and take the necessary corrective actions.

ORA-29536 badly formed source: string
Cause: An attempt was made to create a Java source object with text that could not be parsed adequately to determine the class(es) defined by it.
Action: Correct errors in source.

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-29538 Java not installed
Cause: An attempt was made to use a Java command when Java is not installed.
Action: Install Java, or do not use the command.

ORA-29539 Java system classes already installed
Cause: An attempt was made to use the CREATE JAVA SYSTEM command in a database where the Java system classes already are installed.
Action: Use CREATE OR REPLACE JAVA SYSTEM.

ORA-29540 class string does not exist
Cause: Java method execution failed to find a class with the indicated name.
Action: Correct the name or add the missing Java class.

ORA-29541 class string.string could not be resolved
Cause: An attempt was made to execute a method in a Java class that had not been previously and cannot now be compiled or resolved successfully.
Action: Adjust the call or make the class resolvable.

ORA-29542 class string already defined by source string
Cause: An attempt was made to create a Java source object that would define a class that is already defined by a different Java source object.
Action: Either drop the old source or modify the new source.

ORA-29543 Java command string not yet implemented
Cause: An attempt was made to use a Java command that is not yet implemented.
Action: Do not use the command.

ORA-29544 invalid type
Cause: The type argument in a call to a Java export or import command did not have a recognized value.
Action: Correct the value.

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-29546 badly formed resource: string
Cause: An attempt was made to create a Java resource object with data that was rejected by the Java verifier.
Action: Correct the data.

ORA-29547 Java system class not available: string
Cause: An attempt was made to use a command that requires a Java system class that was not yet present or was invalid.
Action: Load the system classes, or do not use the command.

ORA-29548 Java system class reported: string
Cause: A command that uses a Java system class was aborted due to an error reported by the Java system class.
Action: Correct the error that was reported.

ORA-29549 class string.string has changed, Java session state cleared
Cause: A class in use by the current session was redefined or dropped, invalidating the current Java session state and requiring that it be cleared.
Action: No action required.

ORA-29550 Java session state cleared
Cause: The Java state in the current session became inconsistent and was cleared.
Action: No action required.

ORA-29551 could not convert string to Unicode
Cause: A string in the database character set could not be converted to Unicode, as required for use by Java.
Action: Correct the string.

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-29553 class in use: string.string
Cause: An attempt was made to modify a Java class that is in use in the current call.
Action: Correct the code in use in this call.

ORA-29554 unhandled Java out of memory condition
Cause: The session encountered an out of memory condition in Java from which it could not recover. Java session state was cleared.
Action: No action required.

ORA-29555 Java source, class or resource is not allowed here
Cause: A Java source, class, or resource was specified in an inappropriate place in a statement.
Action: Make sure the name is correct or remove it.

ORA-29556 object type has changed
Cause: A database object name that named a Java source, class, or resource now names an object of a different type.
Action: No action required.

ORA-29557 Java system class string cannot be modified
Cause: A command was attempted that would have modified a Java system class.
Action: No action required.

ORA-29655 USING clause is incompatible with its supertype
Cause: The USING clause of a type has to be the same as its supertype or compatible with it.
Action: Make sure the USING clause is compatible with its supertype.

ORA-29656 Invalid option for USING
Cause: The class has to implement the required interface for the value of the option for USING.
Action: Make sure the USING clause is supported.

ORA-29657 class defined in EXTERNAL NAME clause is used in another subtype
Cause: The supertype has an existing type that has the same value for the EXTERNAL NAME.
Action: Make sure the EXTERNAL NAME clause is unique among subtypes.

ORA-29658 EXTERNAL NAME clause is not compatible with its supertype
Cause: The EXTERNAL NAME clause of the type is not a subclass of the supertype EXTERNAL NAME.
Action: Make sure the EXTERNAL NAME clause of the type is a subclass of the EXTERNAL NAME of its supertype.

ORA-29659 SQLJ Object Type validation failed to get default connection
Cause: Unable to connect using the JDBC default connection.
Action: No action required.

ORA-29660 Unable to find the class defined in the EXTERNAL NAME clause
Cause: The class is not loaded in the database.
Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the database.

ORA-29661 Unable to find the superclass of the defined in the EXTERNAL NAME
Cause: The class is not loaded in the database.
Action: Make sure the superclass of the EXTERNAL NAME is loaded in the database.

ORA-29662 Unable to find a field that matches one or more of the attributes
Cause: The EXTERNAL NAME option of one or more attributes do not match any fields in the defined class.
Action: Make sure the EXTERNAL NAME option of each attribute matches a field in the defined in the defined class.

ORA-29663 Unable to find a method that matches one or more of the functions
Cause: The EXTERNAL NAME option of one or more functions do not match any method in the defined class.
Action: Make sure the EXTERNAL NAME option of each function matches a method in the defined in the defined class.

ORA-29664 Unable to generate the helper class for the defined type
Cause: The helper class used for supporting SQLJ Object Type is not generated.
Action: No Action required.

ORA-29665 Java thread deadlock detected
Cause: The Java VM has detected a thread deadlock.
Action: Modify the Java program to avoid the deadlock condition.

ORA-29701 unable to connect to Cluster Manager
Cause: Connect to the Cluster Manager (CM) failed or timed out.
Action: Verify that the CM was started. If the CM was not started, start it and then retry the database startup. If the CM died or is not responding, check the Oracle and CM trace files for errors.

ORA-29702 error occurred in Cluster Group Service operation
Cause: An unexpected error occurred while performing a CGS operation.
Action: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors.

ORA-29703 error occurred in global enqueue service operation
Cause: An unexpected error occurred while performing a global enqueue service operation.
Action: Check Oracle trace files for errors.

ORA-29704 cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
Cause: The ACTIVE_INSTANCE_COUNT initialization 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 initialization 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 initialization 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 initialization parameter has the same value. Then restart the instance.

ORA-29706 incorrect value string for parameter ACTIVE_INSTANCE_COUNT
Cause: The ACTIVE_INSTANCE_COUNT initialization 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 initialization parameter. If you are configuring a two node primary/secondary cluster database, then set this value to 1. Otherwise, do not specify any value for the parameter.

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, and so on.
Action: Check the trace files of other active instances in the cluster group for indications of errors that caused a reconfiguration.

ORA-29741 IMR active for some, but not all members of cluster
Cause: The IMR feature is not active for this instance, but is active for another instance in the cluster database.
Action: Ensure that all instances have the same value for the _imr_active initialization parameter.

ORA-29760 instance_number parameter not specified
Cause: The initialization parameter file did not contain a value for the INSTANCE_NUMBER parameter 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 initialization parameter file.

ORA-29800 invalid name for operator
Cause: The name specified for the operator is incorrect.
Action: Specify a correct name for the operator.

ORA-29801 missing RETURN keyword
Cause: The RETURN keyword has not been specified.
Action: Specify the RETURN keyword or check the SQL statement.

ORA-29802 missing CONTEXT keyword
Cause: The CONTEXT keyword has not been specified.
Action: Specify the CONTEXT keyword or check the SQL statement.

ORA-29803 missing ANCILLARY keyword
Cause: The ANCILLARY keyword has not been specified.
Action: Specify the ANCILLARY keyword or check the SQL statement.

ORA-29804 missing DATA keyword
Cause: The DATA keyword has not been specified.
Action: Specify the DATA keyword or check the SQL statement.

ORA-29805 missing COLUMN keyword
Cause: Keyword COLUMN is expected.
Action: Either specify the COLUMN keyword or specify another option.

ORA-29806 specified binding does not exist
Cause: The operator binding which has been specified does not exist.
Action: Ensure that the operator binding that has been specified does exist.

ORA-29807 specified operator does not exist
Cause: The operator which has been specified does not exist.
Action: Ensure that the operator that has been specified does exist.

ORA-29808 specified primary operator binding does not exist
Cause: The specified binding for the primary operator does not exist.
Action: Ensure that the specified binding for the primary operator exists.

ORA-29809 cannot drop an operator with dependent objects
Cause: The operator which is being dropped has some dependent objects.
Action: Either drop the dependent objects first and then issue the DROP OPERATOR command or specify the FORCE option with DROP OPERATOR.

ORA-29810 inadequate operator privileges
Cause: The user does not have the appropriate privileges to perform the specified operation on the operator.
Action: Grant the appropriate privileges to the user and then reissue the statement.

ORA-29811 missing STATISTICS keyword
Cause: This is not a valid option with the ASSOCIATE command.
Action: Specify STATISTICS keyword after the ASSOCIATE command.

ORA-29812 incorrect object name specified
Cause: The specified name is not a valid name.
Action: Specify the correct name of the object with for which an association needs to be defined.

ORA-29813 non-supported object type with associate statement
Cause: The type of object specified is not supported with the associate statistics statement.
Action: Use a valid object type with the associate command.

ORA-29814 expecting USING or DEFAULT keyword
Cause: Expecting the USING or DEFAULT keyword after the names of object(s).
Action: Provide the USING or DEFAULT keyword.

ORA-29815 object being associated is not present
Cause: The object for which the association is being defined is not present.
Action: Ensure that all the objects for which the association is being defined are present.

ORA-29816 object being disassociated is not present
Cause: Object which is being disassociated is not present.
Action: Ensure that the object which needs to be disassociated is present.

ORA-29817 non-supported option with disassociate statement
Cause: The type of object specified is not supported with the disassociate statistics statement.
Action: Use a object type which is supported with the disassociate command.

ORA-29818 column name not properly specified
Cause: Name of the column should contain the table and the column name.
Action: Specify a valid column name.

ORA-29819 cannot associate default values with columns
Cause: An attempt was made to associate DEFAULT values with columns which is not a valid option.
Action: Specify a valid option.

ORA-29820 the statistics type is not present
Cause: The statistics type which is being associated with object(s) is not present.
Action: Ensure that the type which contains the statistics functions is present.

ORA-29821 specified primary operator does not exist
Cause: The specified primary operator does not exist.
Action: Check the primary operator and the signature specified.

ORA-29822 selectivity cannot be specified for the type of object
Cause: An attempt was made to associate selectivity with index or index types which is not allowed.
Action: Specify a valid option.

ORA-29823 object being analyzed is not a table
Cause: The object being analyzed is not a table and is not supported.
Action: Specify only a supported option.

ORA-29824 operator is invalid
Cause: The operator is invalid.
Action: Drop and re-create the operator.

ORA-29825 invalid name for indextype
Cause: Index type name or index type schema name has invalid characters.
Action: Verify that the name has valid characters and it is not a reserved word.

ORA-29826 keyword FOR is missing
Cause: FOR keyword must be provided with CREATE INDEXTYPE statement.
Action: Use FOR keyword and provide relevant operator information.

ORA-29827 keyword USING is missing
Cause: USING keyword and corresponding implementation details must be provided.
Action: Provide USING keyword and relevant implementation details with CREATE INDEXTYPE statement.

ORA-29828 invalid name for implementation type
Cause: Implementation type or Implementation schema name is invalid.
Action: Verify that the name has valid characters and it is not a reserved word.

ORA-29829 implementation type does not exist
Cause: The implementation type specified with USING clause could not be found.
Action: Check to see if the type exists and the user has EXECUTE privilege on this type.

ORA-29830 operator does not exist
Cause: The operator could not be found.
Action: Verify that the operator exists and the user has EXECUTE privilege for this operator.

ORA-29831 operator binding not found
Cause: The specified binding for the operator is not available from the operator schema object.
Action: Verify that the operator with the specified binding exists.

ORA-29832 cannot drop or replace an indextype with dependent indexes
Cause: One or more indexes are dependent upon the index type.
Action: Drop all the indexes which are dependent upon the index type before dropping the index type itself.

ORA-29833 indextype does not exist
Cause: There is no index type by the specified name.
Action: Use public views for the index types to see if an index type by the specified name has been created.

ORA-29834 REF datatype not supported with operators
Cause: The user specified a REF datatype which is not supported in CREATE OPERATOR.
Action: Reissue the CREATE OPERATOR statement without the REF datatype.

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-29836 failed to validate referenced operators
Cause: One of the operators referenced cannot be compiled.
Action: Try to recompile the operators which are referenced by this index type. Use USER_INDEXTYPE_OPERATORS view to find out the referenced operators.

ORA-29837 insufficient privileges to execute implementation type
Cause: User does not have privileges to execute the implementation type.
Action: The owner of the implementation type must grant appropriate privileges to the user.

ORA-29838 insufficient privileges to execute the operator(s)
Cause: User does not have privileges to execute one of the operators.
Action: The owner of the operators must grant appropriate privileges to the user.

ORA-29839 failed to validate implementation type
Cause: Implementation type cannot be compiled.
Action: Try to compile the implementation type.

ORA-29840 indextype and implementation type are not in same schema
Cause: Index type and implementation type are in different schema.
Action: Put the index type and implementation type in the same schema.

ORA-29841 invalid option for ALTER INDEXTYPE
Cause: The user specified an invalid option with the ALTER INDEXTYPE command.
Action: Choose a valid option with the ALTER INDEXTYPE command.

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-29843 indextype should support atleast one operator
Cause: User attempted to drop all the operators from the indextype.
Action: Do not drop all the operators from the indextype.

ORA-29844 duplicate operator name specified
Cause: User attempted to add an operator name to an indextype which is already supported by the indextype.
Action: Remove the duplicate operator and retry the command.

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-29846 cannot create a local domain index on a string partitioned table
Cause: User specified a create local domain index statement on a table partitioned using a method not supported by domain indexes.
Action: Build a global domain index on the partitioned table.

ORA-29847 cannot create a local domain index on a partitioned index-organized table
Cause: User specified a create local domain index statement on a partitioned index-organized table.
Action: Build a global domain index on the partitioned index-organized table.

ORA-29848 error occurred in the execution of ODCIINDEXMERGEPARTITION routine
Cause: Failed to successfully execute the ODCIIndexMergePartition routine.
Action: Check to see if the routine has been coded correctly.

ORA-29849 error occurred in the execution of ODCIINDEXSPLITPARTITION routine
Cause: Failed to successfully execute the ODCIIndexSplitPartition routine.
Action: Check to see if the routine has been coded correctly.

ORA-29850 invalid option for creation of domain indexes
Cause: The user specified an invalid option like ASC, DESC, SORT or a parallel clause, partitioning clause or physical attributes clause.
Action: Choose one of the valid clauses for creation of domain indexes.

ORA-29851 cannot build a domain index on more than one column
Cause: User attempted to build a domain index on more than one column.
Action: Build the domain index only on a single column.

ORA-29852 keyword IS is missing
Cause: IS keyword must be specified with Create Index statement for domain indexes.
Action: Use IS keyword and then specify the index type name.

ORA-29853 keyword UNIQUE may not be used in creating domain indexes
Cause: An attempt was made to create a domain index with the UNIQUE attribute.
Action: Remove UNIQUE from the CREATE INDEX statement.

ORA-29854 keyword BITMAP may not be used in creating domain indexes
Cause: An attempt was made to create a domain index with the BITMAP attribute.
Action: Remove BITMAP from the CREATE INDEX statement.

ORA-29855 error occurred in the execution of ODCIINDEXCREATE routine
Cause: Failed to successfully execute the ODCIIndexCreate routine.
Action: Check to see if the routine has been coded correctly.

ORA-29856 error occurred in the execution of ODCIINDEXDROP routine
Cause: Failed to successfully execute the ODCIIndexDrop routine.
Action: Check to see if the routine has been coded correctly.

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-29858 error occurred in the execution of ODCIINDEXALTER routine
Cause: Failed to successfully execute the ODCIIndexAlter routine.
Action: Check to see if the routine has been coded correctly.

ORA-29859 error occurred in the execution of ODCIINDEXTRUNCATE routine
Cause: Failed to successfully execute the ODCIIndexTruncate routine.
Action: Check to see if the routine has been coded correctly.

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-29862 cannot specify FORCE option for dropping non-domain index
Cause: A DROP INDEX FORCE was issued for a non-domain index.
Action: Reissue the command without the FORCE option.

ORA-29863 warning in the execution of ODCIINDEXCREATE routine
Cause: A warning was returned from the ODCIIndexCreate routine.
Action: Check to see if the routine has been coded correctly Check user specified log tables for greater detail.

ORA-29864 analyzing domain indexes marked LOADING/FAILED not supported
Cause: An attempt was made 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-29865 indextype is invalid
Cause: The index type is invalid.
Action: Drop and re-create the index type.

ORA-29866 cannot create domain index on a column of index-organized table
Cause: An attempt was made to create a domain index on a column of an index-organized table.
Action: Do not attempt to create a domain index on columns of an index-organized table.

ORA-29867 cannot create a domain index on a LONG column
Cause: The user attempted to create a domain index on a column of LONG datatype.
Action: Do not create a domain index on a LONG column.

ORA-29868 cannot issue DDL on a domain index marked as LOADING
Cause: An attempt was made to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state.
Action: Wait till the index operation completes OR issue a DROP INDEX FORCE to drop the index.

ORA-29869 cannot issue ALTER without REBUILD on a domain index marked FAILED
Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state.
Action: Truncate the table to mark the index as valid OR do ALTER INDEX REBUILD to rebuild the index.

ORA-29870 specified options are only valid for altering a domain index
Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index.
Action: Reissue the statement with the correct syntax for alter.

ORA-29871 invalid alter option for a domain index
Cause: The user specified an invalid option for altering a domain index.
Action: Reissue the alter statement with a valid option.

ORA-29872 parameters clause cannot be combined with the specified options
Cause: The user combined PARAMETERS clause with other alter index options.
Action: Reissue the statement with the correct syntax for alter.

ORA-29873 warning in the execution of ODCIINDEXDROP routine
Cause: A warning was returned from the ODCIIndexDrop routine.
Action: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details.

ORA-29874 warning in the execution of ODCIINDEXALTER routine
Cause: A warning was returned from the ODCIIndexAlter routine.
Action: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details.

ORA-29875 failed in the execution of the ODCIINDEXINSERT routine
Cause: Failed to successfully execute the ODCIIndexInsert routine.
Action: Check to see if the routine has been coded correctly.

ORA-29876 failed in the execution of the ODCIINDEXDELETE routine
Cause: Failed to successfully execute the ODCIIndexDelete routine.
Action: Check to see if the routine has been coded correctly.

ORA-29877 failed in the execution of the ODCIINDEXUPDATE routine
Cause: Failed to successfully execute the ODCIIndexUpdate routine.
Action: Check to see if the routine has been coded correctly.

ORA-29878 warning in the execution of ODCIINDEXTRUNCATE routine
Cause: A warning was returned from the ODCIIndexTruncate routine.
Action: Check to see if the routine has been coded correctly. Check the user defined warning log tables for greater details.

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-29881 failed to validate indextype
Cause: Index type cannot be compiled.
Action: Try to compile the index type which is referenced by the domain index.

ORA-29882 insufficient privileges to execute indextype
Cause: User does not have privileges to execute the index type.
Action: The owner of the index type must grant appropriate privileges to the user.

ORA-29883 cannot create a domain index on column expressions
Cause: User specified an expression in the column list.
Action: Specify only simple columns in the column list for domain index.

ORA-29884 domain index is defined on the column to be dropped
Cause: An ALTER TABLE DROP COLUMN was issued on a column on which a domain index exists.
Action: Drop the domain index before attempting to drop the column.

ORA-29885 domain index is defined on the column to be modified
Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which a domain index exists.
Action: Drop the domain index before attempting to modify the column.

ORA-29886 feature not supported for domain indexes
Cause: Feature is not supported for domain indexes.
Action: No action required.

ORA-29887 cannot support row movement if domain index defined on table
Cause: An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which has a domain index defined on it.
Action: Drop the domain index if you want to enable row movement and then reissue the command.

ORA-29888 cannot create domain index on a table with row movement enabled
Cause: A CREATE DOMAIN INDEX statement was issued on a table that has row movement enabled.
Action: Disable the row movement in the table and then reissue the create domain index statement.

ORA-29890 specified primary operator does not have an index context
Cause: The primary operator does not have an index and scan contexts.
Action: Create the primary operator with a context clause.

ORA-29900 operator binding does not exist
Cause: There is no binding for the current usage of the operator.
Action: Change the operator arguments to match any of the existing bindings or add a new binding to the operator.

ORA-29901 function underlying operator binding does not exist
Cause: The function underlying the operator binding does not exist.
Action: Ensure that the function corresponding to the operator invocation exists.

ORA-29902 error in executing ODCIIndexStart() routine
Cause: The execution of ODCIIndexStart routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.

ORA-29903 error in executing ODCIIndexFetch() routine
Cause: The execution of ODCIIndexFetch routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.

ORA-29904 error in executing ODCIIndexClose() routine
Cause: The execution of ODCIIndexClose routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.

ORA-29905 method string does not exist in type string.string
Cause: A required method with the required signature does not exist in the specified type.
Action: Add the required method to the type.

ORA-29906 indextype string.string does not exist
Cause: The index type does not exist.
Action: Create the index type.

ORA-29907 found duplicate labels in primary invocations
Cause: There are multiple primary invocations of operators with the same number as the label.
Action: Use distinct labels in primary invocations.

ORA-29908 missing primary invocation for ancillary operator
Cause: The primary invocation corresponding to an ancillary operator is missing.
Action: Add the primary invocation with the same label as the ancillary operator.

ORA-29909 label for the ancillary operator is not a literal number
Cause: The label used for invoking the ancillary operator is not a literal number.
Action: Use a literal number as the label.

ORA-29910 invalid callback operation
Cause: Encountered an invalid callback operation.
Action: Ensure that all the callbacks executed from callouts are valid in the statement context.

ORA-29911 null scan context returned by ODCIIndexStart() routine
Cause: The ODCIIndexStart() routine returned a null scan context.
Action: Ensure that the ODCIIndexStart() routine returns a non-null scan context.

ORA-29913 error in executing string callout
Cause: The execution of the specified callout caused an error.
Action: Examine the error messages take appropriate action.

ORA-29914 ODCIGETINTERFACES routine does not return required stream version
Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the required stream version for external tables.
Action: Ensure that the ODCIGetInterfaces routine returns the required stream version.

ORA-29915 cannot select FOR UPDATE from collection operand
Cause: Collection operands cannot be updated.
Action: Remove the FOR UPDATE clause.

ORA-29925 cannot execute string
Cause: The specified function does not exist or does not have an appropriate signature.
Action: Implement the function with the appropriate signature.

ORA-29926 association already defined for the object
Cause: The object for which the association is being defined, already has a statistics type associated with it.
Action: Disassociate the object and then associate the object.

ORA-29927 error in executing the ODCIStatsCollect / ODCIStatsDelete routine
Cause: The ODCIStatsCollect/ODCIStatsDelete function is causing an error.
Action: Check the ODCIStatsCollect/ODCIStatsDelete function.

ORA-29928 duplicate default selectivity specified
Cause: The keyword DEFAULT SELECTIVITY can only be specified once.
Action: Remove the duplicate keyword.

ORA-29929 missing SCAN Keyword
Cause: The scan context is not specified.
Action: Supply the SCAN keyword.

ORA-29930 COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
Cause: The COMPUTE ANCILLARY DATA option was specified without the WITH INDEX CONTEXT clause.
Action: Specify the WITH INDEX CONTEXT option.

ORA-29931 specified association does not exist
Cause: One or more of the object(s) that have been specified to be disassociated, do not have an association defined for them.
Action: Verify the objects which have an association defined and issue the disassociate command again.

ORA-29932 the type being dropped is a statistics type
Cause: Some objects have defined their statistics methods in the type being dropped.
Action: First drop the relevant associations using the DISASSOCIATE command and then retry the DROP command, or use the FORCE option with DROP TYPE command.

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-29934 index specified for association is not a domain index
Cause: The user issued an ASSOCIATE STATISTICS command with an index which is not a domain index.
Action: Issue an ASSOCIATE STATISTICS WITH INDEXES command on a domain index only.

ORA-29935 missing FROM keyword
Cause: The keyword FROM is missing.
Action: Specify the FROM keyword or check the SQL statement.

ORA-29936 NULL association is allowed only with a column or an index
Cause: User tried to use the ASSOCIATE command with a schema object other than a column or an index.
Action: Specify the NULL clause only with a column or an index.

ORA-29950 warning in the execution of ODCIINDEXMERGEPARTITION routine
Cause: A warning was returned from the ODCIIndexMergePartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.

ORA-29951 warning in the execution of ODCIINDEXSPLITPARTITION routine
Cause: A warning was returned from the ODCIIndexSplitPartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.

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 until the index partition operation completes, issue a DROP INDEX FORCE to drop the index, OR issue an ALTER TABLE DROP PARTITION to drop the partition.

ORA-29953 cannot issue DDL on a domain index partition marked as FAILED
Cause: Tried to issue a DROP/ALTER on a domain index partition in a FAILED state.
Action: do ALTER INDEX REBUILD PARTITION to rebuild the index partition OR ALTER TABLE TRUNCATE PARTITION to mark the index partition as valid.

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-29955 error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
Cause: Failed to successfully execute the ODCIIndexExchangePartition routine.
Action: Check to see if the routine has been coded correctly.

ORA-29956 warning in the execution of ODCIINDEXEXCHANGEPARTITION routine
Cause: A warning was returned from the ODCIIndexExchangePartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.

ORA-29957 cannot create a function-based domain index on a string table
Cause: User specified an unsupported create function-based domain index statement.
Action: Issue the create function-based domain index statement only on supported types of tables.

ORA-29958 fatal error occurred in the execution of ODCIINDEXCREATE routine
Cause: Failed to successfully execute the ODCIIndexCreate routine.
Action: Check to see if the routine has been coded correctly.

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-29960 line string, stringThe ODCIIndex DDL routine has put a warning message into table SYS.ODCI_WARNINGS$.
Action: Check the warning message.

ORA-29961 too many warnings occurred in the execution of ODCIIndex DDL routine
Cause: The number of warnings during the ODCIIndex DDL routine is too high.
Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages.

ORA-29962 fatal error occurred in the execution of ODCIINDEXALTER routine
Cause: Failed to successfully execute the ODCIIndexAlter routine.
Action: Check to see if the routine has been coded correctly.

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-30001 trim set should have only one character
Cause: Trim set contains more or less than 1 character. This is not allowed in TRIM function.
Action: Change trim set to have only 1 character.

ORA-30002 SYS_CONNECT_BY_PATH function is not allowed here
Cause: SYS_CONNECT_BY_PATH function is called at places other than select list.
Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than select list.

ORA-30003 illegal parameter in SYS_CONNECT_BY_PATH function
Action: use a non-empty constant string as the second argument and retry the operation.

ORA-30004 when using SYS_CONNECT_BY_PATH function, cannot have seperator as part of column value
Action: Use another seperator which does not occur in any column value and retry.

ORA-30005 missing or invalid WAIT interval
Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword.
Action: Correct the syntax and retry.

ORA-30006 resource busy; acquire with WAIT timeout expired
Cause: The requested resource is busy.
Action: Retry the operation later.

ORA-30012 undo tablespace 'string' does not exist or of wrong type
Cause: the specified undo tablespace either does not exist or is of the wrong type.
Action: Correct the tablespace name and reissue the statement.

ORA-30013 undo tablespace 'string' is currently in use
Cause: the specified undo tablespace is currently used by another instance.
Action: Wait for the undo tablespace to become available or change to another name and reissue the statement.

ORA-30014 operation only supported in Automatic Undo Management mode
Cause: the operation is only supported in automatic undo mode.
Action: restart the instance in Automatic Undo Management mode before retrying the operation.

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-30016 undo tablespace 'string' is already in use by this instance
Cause: the specified undo tablespace is currently used by this instance. The operation failed.
Action: If the specified undo tablespace name is incorrect, reissue the statement with the correct name.

ORA-30017 segment 'string' is not supported in string Undo Management mode
Cause: The type of the specified undo segment is incompatible with the current undo management mode of the instance.
Action: Check the undo segment name and the undo management mode and reissue the statement if necessary.

ORA-30018 Create Rollback Segment failed, USN string is out of range
Cause: the system runs out of undo segment number. Too many undo segments exist.
Action: drop some of the unused undo segments and retry the operation.

ORA-30019 Illegal rollback Segment operation in Automatic Undo mode
Cause: This operation is only allowed in Manual Undo mode.
Action: Restart the instance in Manual Undo_Management mode and retry the operation.

ORA-30020 UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
Cause: Auto undo management mode is not allowed in the specified compatibility release.
Action: restart the instance in correct compatibility release.

ORA-30021 Operation not allowed on undo tablespace
Cause: This operation is not allowed on undo tablespaces.
Action: Check the tablespace name and reissue the command if necessary.

ORA-30022 Cannot create segments in undo tablespace
Cause: Cannot create segments in undo tablespace.
Action: Check the tablespace name and reissue the command.

ORA-30023 Duplicate undo tablespace specification
Cause: Cannot create more than one undo tablespace during database creation.
Action: Modify the command to contain only one undo tablespace.

ORA-30024 Invalid specification for CREATE UNDO TABLESPACE
Cause: You have specified a clause that should not be used with CREATE UNDO TABLESPACE.
Action: Drop the clause from the command and reissue it.

ORA-30025 DROP segment 'string' (in undo tablespace) not allowed
Cause: Explicit DROP operation is not allowed on undo tablespace segments.
Action: Check the undo segment name and reissue the statement if necessary.

ORA-30026 Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
Cause: Tried to drop a tablespace that contains unexpired undo information.
Action: lower the setting of UNDO_RETENTION or wait a while before reissuing the command to drop undo tablespace.

ORA-30027 Undo quota violation - failed to get string (bytes)
Cause: the amount of undo assigned to the consumer group of this session has been exceeded.
Action: ask the database administrator to increase undo quota, or wait until other transactions commit.

ORA-30029 no active undo tablespace assigned to instance
Cause: the current instance does not have an active undo tablespace assigned to execute transactions.
Action: ask the database administrator to create an undo tablespace, online the undo tablespace and then retry the operation.

ORA-30031 the suspended (resumable) statement has been aborted
Cause: The database administrator or the user aborted the execution of the suspended statement in the resumable session.
Action: No action required.

ORA-30032 the suspended (resumable) statement has timed out
Cause: A correctable error was signaled in the resumable session and the error was not cleared within the timeout interval.
Action: Fix the correctable error within the timeout. The default is 2 hours. Alternatively, increase the (resumable) timeout.

ORA-30033 Undo tablespace cannot be specified as default user tablespace
Cause: It is incorrect to specify undo tablespace as default user tablespace.
Action: Check the tablespace name and reissue the command.

ORA-30034 Undo tablespace cannot be specified as temporary tablespace
Cause: Undo tablespace cannot be specified as default temporary tablespace for the user.
Action: Check the tablespace name and reissue the command.

ORA-30035 Undo tablespace cannot be specified as default temporary tablespace
Cause: Undo tablespace cannot be specified as default temporary tablespace for the database.
Action: Check the tablespace name and reissue the command.

ORA-30036 unable to extend segment by string in undo tablespace 'string'
Cause: the specified undo tablespace has no more space available.
Action: Add more space to the undo tablespace before retrying the operation. An alternative is to wait until active transactions to commit.

ORA-30037 Cannot perform parallel DML after a prior DML on the object
Cause: Attempt to perform parallel DML after another DML on the same object in the same transaction.
Action: Use bitmap segments to perform multiple (parallel) DML operations on the same object. Alternatively, commit before issueing the DML.

ORA-30038 Cannot perform parallel insert on non-partitioned object
Cause: Attempt to perform parallel insert on a non-partitioned object after a previous DML on the object in the same transaction.
Action: Commit before issueing the insert.

ORA-30039 Cannot drop the undo tablespace
Cause: Cannot drop an undo tablespace that is in use.
Action: Switch to a different undo tablespace and then try to drop.

ORA-30040 Undo tablespace is offline
Cause: Cannot operate on an offlined undo tablespace.
Action: Online the undo tablespace and redo the operation.

ORA-30041 Cannot grant quota on the tablespace
Cause: User tried to grant quota on an undo tablespace.
Action: Check the tablespace name and reissue the command.

ORA-30042 Cannot offline the undo tablespace
Cause: Cannot offline an undo tablespace that is in use.
Action: Switch to a different undo tablespace and then try to offline.

ORA-30043 Invalid value 'string' specified for parameter 'Undo_Management'
Cause: The specified undo management mode is invalid.
Action: Correct the parameter value in the initialization parameter file and retry the operation.

ORA-30045 No undo tablespace name specified
Cause: If Create Database has the datafile clause, then undo tablespace name has to be specified, unless using OMF.
Action: Specify the undo tablespace name.

ORA-30071 conversion between datetime/interval and string fail
Cause: An error occurred during a conversion between datetime/interval and string data type due to one of the following reasons:
  • The buffer is too short to hold the result.
  • The format string is bad.
Action: Correct the problem and try again.

ORA-30072 invalid time zone value
Cause: The value specified for the time zone string, which appears in ALTER SESSION statement, environment variable ORA_SDTZ, or a datetime factor, is not valid.
Action: Specify a valid time zone value.

ORA-30073 invalid adjustment value
Cause: The value is none of the followings: 'ADJUST', 'NO_ADJUST', 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value.
Action: Set it to one of the three values.

ORA-30074 GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
Cause: An attempt was made to GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE.
Action: Do not GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE.

ORA- 30075 TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
Cause: An attempt was made to create a constraint on a time or timestamp with or without time zone column without explicitly specifying the time zone.
Action: Use time or timestamp with time zone literals only.

ORA-30076 invalid extract field for extract source
Cause: The extract source does not contain the specified extract field.
Action: Specify a valid extract field for the extract source.

ORA-30077 illegal casting between specified datetime types
Cause: Cannot cast between the specified datetime types.
Action: No action required.

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 WITH TIME ZONE column.
Action: Explicitly use the TIME/TIMESTAMP WITH TIME ZONE literal.

ORA-30081 invalid data type for datetime/interval arithmetic
Cause: The data types of the operands are not valid for datetime/interval arithmetic.
Action: Specify valid data types for datetime/interval arithmetic.

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-30083 syntax error was found in interval value expression
Cause: A syntax error was found during parsing an interval value expression.
Action: Correct the syntax.

ORA-30084 invalid data type for datetime primary with time zone modifier
Cause: When a time zone modifier is specified, the data type of datetime primary must be one of the following: TIME, TIME WITH TIME ZONE, TIMESTAMP, TIMESTAMP WITH TIME ZONE.
Action: Specify a valid data type.

ORA-30085 syntax error was found in overlaps predicate
Cause: A syntax error was found during parsing an overlaps predicate.
Action: Correct the syntax.

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-30087 Adding two datetime values is not allowed
Cause: An attempt was made to add two datetime values.
Action: This addition is not allowed.

ORA-30088 datetime/interval precision is out of range
Cause: The specified datetime/interval precision was not between 0 and 9.
Action: Use a value between 0 and 9 for datetime/interval precision.

ORA-30089 missing or invalid datetime_field
Cause: A datetime_field (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is expected but not found, or a datetime_field specified the end_field in an interval_qualifier is more significant than its start_field.
Action: Specify a valid datetime field.

ORA-30100 internal error [number]
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.

ORA-30101 unknown parameter name 'string'
Cause: You have misspelled the parameter name.
Action: Spell the parameter name correctly.

ORA-30102 'string' is not in the legal range for 'string'
Cause: The value of the parameter is not within the legal range.
Action: Refer to the Oracle9i SQL Reference for the allowable values for this parameter.

ORA-30103 'string' contains an illegal integer radix for 'string'
Cause: An illegal integer radix specification was found.
Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.

ORA-30104 'string' is not a legal integer for 'string'
Cause: The value is not a valid integer.
Action: Specify only valid integers for this parameter.

ORA-30105 'string' is not a legal boolean for 'string'
Cause: The value is not a valid boolean.
Action: Refer to the Oracle9i SQL Reference for allowable boolean values.

ORA-30106 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30107 parameter name abbreviation 'string' is not unique
Cause: The abbreviation given was not unique.
Action: Use a longer abbreviation to make the parameter name unique.

ORA-30108 invalid positional parameter value 'string'
Cause: An invalid positional parameter value has been entered.
Action: Remove the invalid positional parameter.

ORA-30109 could not open parameter file 'string'
Cause: The parameter file does not exist.
Action: Create an appropriate parameter file.

ORA-30110 syntax error at 'string'
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.

ORA-30111 no closing quote for value 'string'
Cause: A quoted string was begun but not finished.
Action: Put a closing quote in the proper location.

ORA-30112 multiple values not allowed for parameter 'string'
Cause: An attempt was made to specify multiple values for a parameter which can take only one value.
Action: Do not specify more than one value for this parameter.

ORA-30113 error when processing file 'string'
Cause: A problem occurred when processing this file.
Action: Examine the additional error messages and correct the problem.

ORA-30114 error when processing from command line
Cause: A problem occurred when processing the command line.
Action: Examine the additional error messages and correct the problem.

ORA-30115 error when processing an environment variable
Cause: A problem occurred when processing an environment variable.
Action: Examine the additional error messages and correct the problem.

ORA-30116 syntax error at 'string' following 'string'
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.

ORA-30117 syntax error at 'string' at the start of input
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.

ORA-30118 syntax error at 'string' at the end of input
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.

ORA-30119 unable to obtain a valid value for 'string'
Cause: No valid value was obtained for this parameter.
Action: Rerun the application and enter a valid value.

ORA-30120 'string' is not a legal oracle number for 'string'
Cause: The value is not a valid Oracle number.
Action: Refer to the Oracle9i SQL Reference for allowable Oracle number values.

ORA-30121 'string' is not an allowable value for 'string'
Cause: The value is not a legal value for this parameter.
Action: Refer to the manual for allowable values.

ORA-30122 value 'string' for 'string' must be between 'number' and 'number'"
Cause: The value of the parameter is not within the legal range.
Action: Specify a value that is within the legal range.

ORA-30129 invalid function argument received
Cause: A function received an invalid argument.
Action: Check function calls and make sure correct arguments are being passed.

ORA-30130 invalid parameter key type received
Cause: A function received an invalid parameter key type.
Action: Check parameter key types in function calls.

ORA-30131 number of keys being set exceeds allocation
Cause: The number of parameter keys being set exceeds allocation.
Action: Reduce the number of keys being set or increase allocation.

ORA-30132 invalid key index supplied
Cause: The key index specified was not within bounds.
Action: Change key index to ensure it lies within bounds.

ORA-30135 OCI Thread operation fails
Cause: An OCI Thread function call has failed.
Action: Check the function call to make sure that the correct parameters are being passed and take the appropriate action.

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. Check for NULL pointers.

ORA-30151 File already exists
Cause: An attempt was made to open a file with OCI_FILE_EXCL flag and the file already exists.
Action: OCIFile is supposed throw this exception in this case.

ORA-30152 File does not exist
Cause: The OCIFile function requires the file to exist, but it does not.
Action: Make sure that the file exists.

ORA-30153 An invalid File Object is passed to the OCIFile function
Cause: An invalid File Object is passed to the OCIFile function.
Action: Make sure that the file object is a valid one. Create a new file object by calling OCIFileOpen if needed.

ORA-30154 The memory address given as buffer for OCIFileRead/Write is invalid
Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write.
Action: Make sure that the required memory is allocated and pass a valid memory address as buffer pointer.

ORA-30155 An I/O Error occured during an OCIFile function call
Cause: An I/O error occurred at the system level.
Action: This is a system error and the action will depend on the error.

ORA-30156 Out of disk space
Cause: The disks associated with the underlying file system are full.
Action: Create more disk space.

ORA-30157 An invalid argument was given to operating system call
Cause: The operating system call was called with an invalid argument.
Action: Check the values passed. If you are unable to solve the problem, then contact Oracle Support Services.

ORA-30158 The OCIFileWrite causes the file to exceed the maximum allowed size
Cause: There is no space to write to the file. Its size is at the maximum limit.
Action: If you can, increase the limit.

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 does not allow the file to be opened 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-30160 Unable to access the file
Cause: The function was unable to access the existing the file.
Action: Check if the user has the required permissions on the file.

ORA-30161 A system error occurred during the OCIFile function call
Cause: A system error occurred while executing the OCIFile function.
Action: Investigate and solve the system error.

ORA-30162 The OCIFile context is not initialzed
Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context.
Action: Call the function OCIFileInit need to be called before calling any other OCIFile function.

ORA-30163 The thread safety initialization failed
Cause: The call to SlgInit failed in OCIFileInit.
Action: Contact Oracle Support Services.

ORA-30175 invalid type given for an argument
Cause: There is an argument with an invalid type in the argument list.
Action: Use the correct type wrapper for the argument.

ORA-30176 invalid format code used in the format string
Cause: There is an invalid format code in the format string.
Action: Replace the invalid format code with a valid one.

ORA-30177 invalid flag used in a format specification
Cause: There is an invalid flag in a format specification.
Action: Replace the invalid flag with a valid one.

ORA-30178 duplicate flag used in a format specification
Cause: There is a duplicate flag in a format specification.
Action: Remove the duplicate flag.

ORA-30179 invalid argument index used in a format code
Cause: Zero or negative argument index or index not following (.
Action: Replace the invalid argument index with a valid one.

ORA-30180 argument index is too large
Cause: An argument index exceeds actual number of arguments supplied.
Action: Fix format string or pass additional arguments.

ORA-30181 integer in argument index is not immediately followed by )
Cause: Missing closing parenthesis in argument index.
Action: Fix the format specification.

ORA-30182 invalid precision specifier
Cause: Period in format specification not followed by valid format.
Action: Replace the invalid precision specifier with a valid one.

ORA-30183 invalid field width specifier
Cause: Invalid field width supplied.
Action: Replace the invalid field width with a valid one.

ORA-30184 argument type not compatible with a format code
Cause: Bad argument type given for a format code.
Action: Make format and arguments be compatible.

ORA-30185 output too large to fit in the buffer
Cause: The buffer is not large enough to hold the entire output string.
Action: Fix the buffer size and length passed in.

ORA-30186 '\' must be followed by four hexadecimal characters or another '\'
Cause: In the argument of SQL function UNISTR, a '\' must be followed by four hexadecimal characters or another '\'.
Action: Fix the string format.

ORA-30187 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30188 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30189 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30190 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30191 missing argument list
Cause: No argument list supplied.
Action: Modify the argument list to have at least OCIFormatEnd in it.

ORA-30192 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30193 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30194 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30195 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30196 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30197 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30198 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30199 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.

ORA-30200 Wrong NLS item was passed into OCINlsGetInfo()
Cause: The item is not supported NLS item.
Action: Correct the item number passed to OCINlsGetInfo().

ORA-30201 Unable to load NLS data object
Cause: It may be caused by invalid NLS environment setting.
Action: Check your NLS environment setting such as ORA_NLS33.

ORA-30202 NULL pointer to OCIMsgh was passed to OCIMsg function
Cause: The NULL pointer was passed.
Action: Check the value of the OCIMsgh pointer.

ORA-30203 Cannot open mesage file
Cause: The message may not exist in your system.
Action: Check the message for the given product and facility.

ORA-30204 buffer is not large enough
Cause: The destination buffer is not large enough for storing converted data.
Action: Check the size of the destination buffer.

ORA-30205 invalid Character set
Cause: The specified character set is invalid.
Action: Check if the character set ID is valid.

ORA-30331 summary does not exist
Cause: A non-existent summary name was specified.
Action: Check the spelling of the summary name.

ORA-30332 container table already in use by other summary
Cause: Another summary is already using this table as a container table.
Action: Select another table or materialized view as the container table for this summary.

ORA-30333 dimension does not exist
Cause: The dimension named in a dimension DDL statement does not exist.
Action: Check the spelling of the dimension name.

ORA-30334 illegal dimension level name
Cause: A level name in a dimension DDL statement did not conform to SQL identifier rules.
Action: Use a level name that begins with a letter, consists of only letters, digits, and underscores and contains no more than 30 characters.

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.
Action: Check the spelling of the level name.

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 references to the level prior to dropping it, or specify the CASCADE option with the DROP LEVEL clause.

ORA-30342 referenced level is not defined in this dimension
Cause: A reference to a level not defined within the dimension was found.
Action: Check the spelling of the level name.

ORA-30343 level name is not unique within this dimension
Cause: Two or more levels were defined with the same name.
Action: Check the spelling of the level names.

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

ORA-30345 circular dimension hierarchy
Cause: A circularity was found the dimension hierarchy.
Action: Check the hierarchy for a level name that occurs more than once.

ORA-30346 hierarchy name must be unique within a dimension
Cause: The same name was used for more than one hierarchy in a dimension.
Action: Check the spelling of the hierarchy name.

ORA-30347 a table name is required to qualify the column specification
Cause: A table name was omitted in a column specification where the column must be qualified by the table name.
Action: Qualify the column with the table name.

ORA-30348 ADD and DROP cannot both be specified
Cause: One or more ADD clauses were found in the same ALTER DIMENSION statement with one or more DROP clauses.
Action: Separate your ADD operations into one ALTER DIMENSION statement and your DROP operations into another.

ORA-30349 specified dimension hierarchy does not exist
Cause: A hierarchy name was encountered that is not defined within the dimension.
Action: Check the spelling of the hierarchy name.

ORA-30350 specified dimension attribute does not exist
Cause: An attribute name was encountered that is not defined within the dimension.
Action: Check the attribute name spelling.

ORA-30351 query rewrite does not currently support this expression
Cause: A complex expression was specified that is not currently supported by query rewrite.
Action: Reduce the complexity of the expression.

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, and so on.
Action: Remove the offending expression or disable the REWRITE option on the materialized view.

ORA-30354 Query rewrite not allowed on SYS relations
Cause: A SYS relation was referenced in the select clause for a materialized view with query rewrite enabled.
Action: Remove the reference to the SYS relation from the select clause 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 metadata for the materialized view. Then use the CREATE MATERIALIZED VIEW statement to re-create the materialized view. Thereafter, use the DROP MATERIALIZED VIEW command rather than the DROP TABLE command to drop a materialized view.

ORA-30356 the specified refresh method is not supported in this context
Cause: The refresh method that was specified is not currently supported.
Action: Specify a different refresh method or change the context to enable support of the chosen refresh method.

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-30358 summary and materialized view are not in same schema
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

ORA-30359 Query rewrite is not supported on SYS materialized views
Cause: An attempt was made to enable the REWRITE option on a materialized view in the SYS schema.
Action: Create the materialized view in a different schema or disable the REWRITE option.

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-30361 unrecognized string type
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

ORA-30362 dimension column cannot be a sequence
Cause: The dimension statement referenced a column that is a sequence.
Action: Remove the reference to the sequence.

ORA-30363 columns in a dimension column list must be in the same relation
Cause: The dimension statement contained a column list where the columns are not all from the same relation.
Action: Specify the list of columns using only columns from a single relation.

ORA-30364 this level has the same set of columns as another
Cause: The level definition contained the same set of columns as another level.
Action: Eliminate the redundant level definition.

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-30366 child JOIN KEY columns not in same relation as child level
Cause: The relation of the child columns on the left side of the JOIN KEY clause differed from that of that child level.
Action: Specify the correct child columns in the JOIN KEY clause.

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 attributes only for those dimension levels that functionally determine other columns within the same relation.

ORA-30369 maximum number of columns is 32
Cause: A list of columns was specified using more than 32 columns.
Action: Specify the list using no more than 32 columns.

ORA-30370 set operators are not supported in this context
Cause: A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was encountered in an unsupported context, such as in a materialized view definition.
Action: Re-specify the expression to avoid the use of set operators.

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-30373 object data types are not supported in this context
Cause: An object data type was encountered in an unsupported context.
Action: Re-specify the expression to avoid the use of objects.

ORA-30374 materialized view is already fresh
Cause: If the materialized view is fresh, ORACLE ignores the ALTER MATERIALIZED VIEW <mv> RELY FRESH command, and issues this error message.
Action: No action required.

ORA-30375 materialized view cannot be considered fresh
Cause: If the materialized view is invalid or unusable, it cannot be considered fresh with the ALTER MATERIALIZED VIEW <mv> CONSIDER FRESH command.
Action: No action required.

ORA-30376 prevent sharing of a parsed query of an explain rewrite session
Cause: Explain rewrite generates a shared cursor after parsing the user query. Raising this error will prevent the cursor from being shared.
Action: No action required.

ORA-30377 MV_CAPABILITIES_TABLE not found
Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() API before you have defined the MV_CAPABILITIES_TABLE.
Action: Invoke the ORACLE_HOME/rdbms/admin/utlxmv.sql script after connecting to the desired schema.

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 ORACLE_HOME/rdbms/admin/utlxmv.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_MVIEW() API.

ORA-30379 query txt not specified
Cause: You have attempted to use the DBMS_MVIEW.EXPLAIN_REWRITE() API with an empty query text argument.
Action: Input a valid SQL query.

ORA-30380 REWRITE_TABLE does not exist.
Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have created the REWRITE_TABLE.
Action: Create it using the ORACLE_HOME/rdbms/admin/utlxrw.sql script after connecting to the desired schema.

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 ORACLE_HOME/rdbms/admin/utlxrw.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_REWRITE() API.

ORA-30382 DROP MATERIALIZED VIEW string.string operation is not complete
Cause: The drop materialized view operation got an unexpected error while dropping a summary object.
Action: Re-issue the drop materialized view command.

ORA-30430 list does not contain any valid summaries
Cause: List is empty or does not contain the names of existing summaries.
Action: Verify that the list of names passed to refresh contains the name of at least one existing summary object

ORA-30431 refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
Cause: An invalid refresh method was specified.
Action: Verify that the refresh method is one of 'ANY' or 'INCREMENTAL' or 'FORCE_FULL'.

ORA-30432 summary 'string.string' is in INVALID state
Cause: The summary is in INVALID state and cannot be refreshed.

ORA-30433 'string.string' is not a summary
Cause: There is no such summary, therefore it cannot be refreshed.
Action: Verify the correct name of the summary.

ORA-30434 refresh method must be one of FC?AN, not 'string'
Cause: An invalid refresh method was specified.
Action: Verify that the refresh method is one of 'FC?AN'.

ORA-30435 job_queue_processes must be non-zero in order to refresh summaries
Cause: The server must be started with parameter JOB_QUEUE_PROCESSES greater than zero.
Action: Correct the value of JOB_QUEUE_PROCESSES and restart the server instance.

ORA-30436 unable to open named pipe 'string'
Cause: The refresh process was unable to open a named pipe to the job queue process usually because of insufficient system resources. This is an internal error.
Action: Contact Oracle Support Services.

ORA-30437 all job queue processes have stopped running
Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries. This is an internal error.
Action: Contact Oracle Support Services.

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. This is an internal error.
Action: Contact Oracle Support Services.

ORA-30439 refresh of 'string.string' failed because of string
Cause: The refresh job queue process encountered an error and is reporting it. The accompanying text of the message indicates cause of the error.
Action: Varies, depending upon the reported cause.

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-30442 can not find the definition for filter string
Cause: For the specified filterid parameter, there is no corresponding filter definition found in the advisor repository.
Action: Use a valid filterid generated by the create_filter function.

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-30445 workload queries not found
Cause: No workload queries in the advisor repository can satisfy the specified filter.
Action: Redefine a new filter or load additional workload queries that can satisfy the specified 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 or 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-30449 syntax error in parameter string
Cause: The syntax for the specified parameter is incorrect.
Action: Check ORACLE documentation for the correct syntax.

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-30451 internal error
Cause: An internal error was detected by the summary refresh subsystem, and aborted the refresh operation.
Action: Contact Oracle Support Services.

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-30456 'string.string' cannot be refreshed because of insufficient privilege
Cause: The user lacks one or more permissions that are required in order to refresh summaries.
Action: Make sure that the user is granted all required privileges.

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 value 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-30458 'string.string' cannot be refreshed because the refresh mask is string
Cause: An attempt was made to incrementally refresh a summary that is not incrementally refreshable.
Action: Do not attempt to incrementally refresh the summary; use full refresh instead.

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-30460 'string.string' cannot be refreshed because it is marked UNUSABLE
Cause: An attempt was made to refresh a summary which is UNUSABLE.
Action: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh.

ORA-30461 'string.string' cannot be refreshed because it is marked DISABLED
Cause: An attempt was made to refresh a summary which is DISABLED.
Action: Determine why the summary is DISABLED, re-enable it, and retry the refresh.

ORA-30462 unsupported operator: string
Cause: An attempt was made to refresh a summary containing an unsupported operator.
Action: Verify that all columns of the summary contain expressions that are refreshable.

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.

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)