Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
ORA-29250 Invalid index specifed in call to dbms_sql.bind_array
Cause: An invalid index was specified in a call to BIND_ARRAY of DBMS_SQL. The index may have been null or of an improper value.
Action: Correct the index value by modifying your PL/SQL program and try the BIND_ARRAY call again.
ORA-29251 Index1 is greater than Index2 in call to dbms_sql.bind_array
Cause: The value of index1 was greater than the value for index2 in the call to BIND_ARRAY. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2.
Action: Correct the value of the two indexes and try the call to again BIND_ARRAY.
ORA-29252 collection does not contain elements at index locations in call to dbms_sql.bind_array
Cause: The bound table does not contain elements at both index locations in call to BIND_ARRAY of DBMS_SQL. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true.
Action: Either modify the two indexes or the contents of the table and try the call again.
ORA-29253 Invalid count argument passed to procedure dbms_sql.define_array
Cause: The count argument specified in the call to procedure DEFINE_ARRAY of package DBMS_SQL had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer.
Action: Correct your PL/SQL program so that only valid arguments are passed to DEFINE_ARRAY and try again.
ORA-29254 Invalid lower_bound argument passed to procedure dbms_sql.define_array
Cause: The LOWER_BOUND argument specified in the call to procedure DEFINE_ARRAY had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal.
Action: Correct your PL/SQL program so that only valid arguments are passed to DEFINE_ARRAY and try again.
ORA-29255 Cursor contains both bind and define arrays which is not permissible
Cause: Both DEFINE_ARRAY and BIND_ARRAY have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries.
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand.
ORA-29256 Cursor contains both regular and array defines which is illegal
Cause: Both DEFINE_ARRAY and DEFINE_COLUMN have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables.
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the situation at hand.
ORA-29300 ORACLE error, tablespace point-in-time recovery
Cause: Another Oracle error occurred in the DBMS_PITR package.
Action: See the text of the error message for a description of the error.
ORA-29301 wrong DBMS_PITR package function/procedure order
Cause: The DBMS_PITR package function/procedure was called in an incorrect order.
Action: Restart tablespace point-in-time recovery with a correct procedure.
ORA-29302 database is not open clone
Cause: The database was not opened as a clone database.
Action: Mount the database clone and open the database.
ORA-29303 user does not login as SYS
Cause: The user did not log in as SYS to perform tablespace point-in-time recovery in a clone database.
Action: Log in as SYS and restart tablespace point-in-time recovery.
ORA-29304 tablespace 'string' does not exist
Cause: The selected tablespace does not exist in the database.
Action: Check the list of tablespaces in V$TABLESPACE and select a valid tablespace.
ORA-29305 cannot point-in-time recover tablespace 'string'
Cause: An attempt was made to ALTER the tablespace to be read only.
Action: Check if the tablespace is SYSTEM or with online rollback segment.
ORA-29306 datafile string is not online
Cause: The selected datafile was not online.
Action: Bring the datafile online and rename it if necessary.
ORA-29307 datafile string error, string
Cause: The datafile is not ready for tablespace point-in-time recovery.
Action: Check the correct tablespace point-in-time recovery procedure.
ORA-29308 view TS_PITR_CHECK failure
Cause: Some objects which crossed the boundary of the recovery set were not allowed in the tablespace point-in-time recovery.
Action: Query TS_PITR_CHECK and resolve the boundary crossing objects.
ORA-29309 export dump file was generated by different version of DBMS_PITR package
Cause: The version of DBMS_PITR is different from the version of the cloned database.
Action: Load the version of DBMS_PITR which matches the version of the cloned database.
ORA-29310 database is not open, or opened as a clone
Cause: Either the database was not open, or an attempt was made to open it as a cloned database.
Action: Open the production database instead.
ORA-29311 export dump file was not generated by this database, string does not match
Cause: The export dump files were imported to an incorrect database.
Action: Open the correct production database and try the import again.
ORA-29312 database not compatible, string string
Cause: A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace.
Action: Choose a point-in-time and retry the operation.
ORA-29313 tablespace 'string' cannot be imported twice
Cause: This is an internal error.
Action: Contact your database administrator.
ORA-29314 tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
Cause: Tablespace clean SCN is either 0 or invalid.
Action: ALTER the tablespace OFFLINE FOR RECOVER.
ORA-29315 tablespace 'string' has been recreated
Cause: An attempt was made to recover a tablespace to a point-in-time before it was re-created.
Action: Choose a different point in time for recovery.
ORA-29316 datafile string been imported twice
Cause: This is an internal error.
Action: Contact your database administrator.
ORA-29317 datafile string does not exist
Cause: The specified datafile could not be found in the production database.
Action: Copy the datafile from the clone database.
ORA-29318 datafile string is online
Cause: The datafile is online.
Action: Take the datafile offline.
ORA-29319 datafile string is not correct
Cause: An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database.
Action: Copy the datafile from the clone database to the production database.
ORA-29320 datafile header error
Cause: An error occurred during reading datafile header.
Action: Copy the correct datafile from the clone database to the production database, then retry the operation.
ORA-29321 too many datafiles added since the point-in-time
Cause: Too many datafiles were added to the recovery set since the point-in-time recovery. It is assumed that no more than 100 datafiles were added since the point-in-time.
Action: Divide the recovery set into smaller subsets and retry.
ORA-29322 SCN string size too long -- maximum size 58 bytes/characters
Cause: Too many characters in specifying the SCN string
Action: Remove all unnecessary characters. Only 15 characters are required for both the hex and decimal representation of the 48 bit SCN.
ORA-29323 SET COMPATIBILITY command cannot be used for releases before 8.0.0
Cause: The rolling release feature was first implemented in 8.0.3.
Action: Try 8.0.3 or later.
ORA-29324 SET COMPATIBILITY release string format is wrong
Cause: It should be of the form 8.x.x.
Action: Use the correct format.
ORA-29325 SET COMPATIBILITY release number mismatches compatibility release number
Cause: In 8.0.3, it should be the same as compatibility release number.
Action: Specify the same as the COMPATIBLE initialization parameter. Note that this cannot be a release number less than 8.0.0.
ORA-29326 specified SET COMPATIBILITY release number reduced to string.string.string.string.string
Cause: One or more instances had a lower release number.
Action: To roll the release to the specified number, all instances will need to migrate to the same release number or higher.
ORA-29335 tablespace 'string' is not read only
Cause: The tablespace is not read only.
Action: Make the tablespace read only and retry the operation.
ORA-29336 Internal error [string] [string] from DBMS_PLUGTS
Cause: Internal error from package DBMS_PLUGTS.
Action: Call Oracle Customer Support.
ORA-29337 Failed to validate the file header of datafile string
Cause: The system failed to validate the file header of the referred datafile. The datafile maybe missing. The content in the datafile header may be inconsistent with that in the control file.
Action: Make sure the referred datafile exists. Make sure it is in a valid state.
ORA-29338 datafile string is in an undesired state (string, string)
Cause: The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE.
Action: Put the datafile into the desired state.
ORA-29339 tablespace block size string does not match database block size string
Cause: The block size of the tablespace to be plugged in does not match the block size of the database. Plugging a tablespace into a database with a different block size is not supported.
Action: Use a different way to move data.
ORA-29340 export file appears to be corrupted: [string] [string] [string]
Cause: This is caused either by a corrupted export file or by an Oracle internal error.
Action: Make sure the export file used for transportable tablespace is not corrupted. If the error still occurs, call Oracle Customer Support.
ORA-29341 The transportable set is not self-contained
Cause: The set of objects in the set of tablespaces selected are not self-contained.
Action: Consider using different export options, or removing some of the pointers that caused the violation, or selecting a different set of tablespaces.
ORA-29342 user string does not exist in the database
Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.
Action: Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options.
ORA-29343 user string (mapped from user string) does not exist in the database
Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.
Action: Consider either creating the user or map the original user to a different user.
ORA-29344 Owner validation failed - failed to match owner 'string'
Cause: The system failed to match the referenced owner. There are two cases in which this may occur:
Action: Retry the import with a different OWNER list.
ORA-29345 can not plug a tablespace into a database using a different character set
Cause: Oracle does not support plugging a tablespace into a database using a different character set.
Action: Use import/export or unload/load to move data instead.
ORA-29346 invalid tablespace list
Cause: The tablespace list supplied to DBMS_TTS.TRANSPORT_SET_CHECK. PL/SQL routine is in an incorrect format.
Action: Check PL/SQL User's Guide and Reference and use the correct format.
ORA-29347 Tablespace name validation failed - failed to match tablespace 'string'
Cause: The system failed to match the referenced tablespace. There are two case in which this may happen:
Action: Retry the operation with the correct TABLESPACES list.
ORA-29348 You must specify the datafiles to be plugged in
Cause: The datafiles to be plugged in are not specified.
Action: Specify the datafiles via the import DATAFILES command line option.
ORA-29349 tablespace 'string' already exists
Cause: An attempt was made to plug-in a tablespace which already exists.
Action: Drop the offending tablespace if possible. Otherwise use a different method (for example, import/export) to move data.
ORA-29350 server version string incompatible with package string version string
ORA-29351 can not transport system or temporary tablespace 'string'
Cause: The referenced tablespace is either the system tablespace or a temporary tablespace.
Action: Do not include this tablespace in the transportable set.
ORA-29355 NULL or invalid string argument specified
Cause: The named argument was either invalid or specified as a NULL.
Action: Specify non-null, valid arguments.
ORA-29356 MAX_ACTIVE_SESS_TARGET_P1 and PARALLEL_DEGREE_LIMIT_P1 can be specified only for directives that refer to consumer groups
Cause: The above parameters were specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER where the GROUP_OR_SUBPLAN argument is a resource plan.
Action: Specify these parameters only for consumer group directives.
ORA-29357 object string already exists
Cause: The name specified as argument to procedure CREATE_PLAN, CREATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER was already in use.
Action: Specify an unused name.
ORA-29358 resource plan string does not exist
Cause: An invalid plan name was specified as an argument to procedure UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan name.
ORA-29359 invalid method name string specified for resource plan string
Cause: An invalid method was specified as an argument to procedure CREATE_PLAN or UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid method name.
ORA-29360 retry operation. Too much concurrent activity
Cause: An attempt was made to revoke the switch consumer group privilege from a user for his/her initial consumer group but someone is modifying the user in another session.
Action: Retry the operation later.
ORA-29361 percentage string is outside valid range of 0 to 100
Cause: An invalid percentage value was specified.
Action: Specify a percentage value between 0 and 100 inclusive.
ORA-29362 plan directive string, string does not exist
Cause: A non-existent plan directive was specified for procedure UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan directive for update.
ORA-29363 plan directive string, string is mandatory and cannot be modified or deleted
Cause: An attempt was made to modify a mandatory plan directive.
Action: Do not attempt to modify mandatory plan directives because they are required by the Resource Manager and cannot be modified.
ORA-29364 plan directive string, string already exists
Cause: An attempt was made to create a plan directive that already exists.
Action: Retry the create operation using different values.
ORA-29365 NULL or invalid GROUP_OR_SUBPLAN argument specified
Cause: A NULL or invalid GROUP_OR_SUBPLAN was specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify a non-NULL, valid argument.
ORA-29366 invalid CONSUMER_GROUP argument specified
Cause: An invalid consumer group name was specified.
Action: Specify a non-NULL, valid consumer group name.
ORA-29367 object string does not exist
Cause: A non-existent object name was specified as an argument to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid plan or consumer group name.
ORA-29368 consumer group string does not exist
Cause: An non-existent consumer group was specified.
Action: Specify an existing consumer group.
ORA-29369 invalid method name string specified for consumer group string
Cause: An invalid method name was specified as an argument to procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid method name.
ORA-29370 pending area is already active
Cause: An attempt was made to activate a pending area that is already active.
Action: Wait until the pending area is no longer active; then, retry the operation.
ORA-29371 pending area is not active
Cause: An attempt was made to make changes without creating a pending area.
Action: Invoke procedure CREATE_PENDING_AREA before making any changes.
ORA-29372 identifier string is too long; it must be less than string characters
Cause: An attempt was made to specify an identifier that is more than 30 characters long.
Action: Use an identifier that is 30 characters or less in length.
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 Oracle8i 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 Customer Support.
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 compiling string.string
Cause: The output of a SQLJ compilation conflicted with an existing object.
Action: Remove existing object, or modify JSQL 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-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 DLM operation
Cause: An unexpected error occurred while performing a DLM operation.
Action: Check Oracle trace files for errors.
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 for the indextype
Cause: Implementation type for the index type cannot be compiled.
Action: Try to compile the implementation type which is specified for this index 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-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 ODCIIndexCreate 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: An attempt was made to ALTER a domain index in FAILED state.
Action: Truncate the table to mark the index as valid and then issue a ALTER INDEX 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-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-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-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-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:
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-30074 invalid datetime/interval value
Cause: The value specified is not a valid datetime or interval.
Action: Specify a valid datetime/internal value.
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-30080 evaluation of NUMTOYMINTERVAL or NUMTODSINTERVAL failed
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-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 Customer Support 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 Oracle8i 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 Oracle8i 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 Oracle8i SQL Reference for allowable Oracle number values.
ORA-30121 invalid function argument received
Cause: A function received an invalid argument
Action: Check function calls, make sure correct arguments are being passed.
ORA-30122 invalid parameter key type received
Cause: A function received an invalid parameter key type.
Action: Check parameter key types in function calls.
ORA-30123 number of keys being set exceeds allocation
Cause: Number of parameter keys being set exceeds allocation.
Action: Reduce the number of keys being set or increase allocation.
ORA-30124 invalid key index supplied
Cause: The key index specified was not within bounds.
Action: Change key index to ensure it lies within bounds.
ORA-30125 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.
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, contact Oracle Customer Support.
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 Customer Support.
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 reserved for future use
Cause: This message is reserved for future use.
Action: No action required.
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-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 snapshot 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:
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 Customer Support.
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 Customer Support.
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, such as in a materialized view definition.
Action: Re-specify the expression to avoid the use of objects.
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 Customer Support.
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 Customer Support.
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 Customer Support.
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-30450 refresh_after_errors was TRUE, and one or more errors occurred
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 Customer Support.
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.
ORA-30464 no summaries exist
Cause: A call was made to REFRESH_ALL_MVIEWS, but no summaries exist. At least one summary must exist before calling REFRESH_ALL_MVIEWS.
Action: Create one or more summaries.
ORA-30475 feature not enabled: string
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
ORA-30476 PLAN_TABLE does not exist in the user's schema
Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user's schema. For more information, refer to Oracle8i SQL Reference.
Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script UTLXPLAN.SQL will create this table.
ORA-30477 The input select_clause is incorrectly specified
Cause: The input select-clause parameter to Estimate_Summary_Size is incorrectly specified and cannot be compiled.
Action: Check the syntax of the select-clause.
ORA-30478 Specified dimension does not exist
Cause: The specified dimension to be verified does not exist.
Action: Check the spelling of the dimension name.
ORA-30479 Summary Advisor errorstring
Cause: An error has occurred in the Summary Advisor package. This message will be followed by a second message giving more details about the nature of the error.
Action: See the Summary Advisor documentation for an explanation of the second error message.
ORA-30480 DISTINCT option not allowed with GROUP BY CUBE or ROLLUP
ORA-30481 GROUPING function only supported with GROUP BY CUBE or ROLLUP
ORA-30500 database open triggers and server error triggers cannot have BEFORE type
Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported.
Action: Do not attempt to create a trigger that fires before the database is open or before server errors.
ORA-30501 instance shutdown triggers cannot have AFTER type
Cause: An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported.
Action: Do not attempt to create a trigger that fires after an instance shutdown.
ORA-30502 system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table.
Action: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events.
ORA-30503 system triggers cannot have a REFERENCING clause
Cause: An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.
Action: Do not use a REFERENCING clause with a system trigger.
ORA-30504 system triggers cannot have a FOR EACH ROW clause
Cause: An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.
Action: Do not use a FOR EACH ROW clause with a system trigger.
ORA-30505 system triggers should not reference a column in a WHEN clause
Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table.
Action: Change the WHEN clause to an appropriate clause.
ORA-30506 system triggers cannot be based on tables or views
Cause: An attempt was made to base a system trigger on a table or a view.
Action: Make sure the type of the trigger is compatible with the base object.
ORA-30507 normal triggers cannot be based on a schema or a database
Cause: An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views.
Action: Make sure the type of the trigger is compatible with the base object.
ORA-30508 client logon triggers cannot have BEFORE type
Cause: An attempt was made to create a trigger that fires before logon. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires before logon.
ORA-30509 client logoff triggers cannot have AFTER type
Cause: An attempt was made to create a trigger that fires after logoff. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires after logoff.
ORA-30510 system triggers cannot be defined on the schema of SYS user
Cause: An attempt was made to define a system trigger on the schema of SYS user. This type of trigger is not supported currently.
Action: Do not attempt to create a system trigger defined on the schema of SYS user.
ORA-30511 invalid DDL operation in system triggers
Cause: An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations and ALTER?COMPILE operations.
Action: Remove invalid DDL operations in system triggers.
ORA-30512 cannot modify string.string more than once in a transaction
Cause: An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations.
Action: Do not create system triggers that might modify an already modified object. Also, do not specify more than one DDL operation on a queue table in the same transaction.
ORA-30550 index depends on a package/function spec/body which is not valid
Cause: The functional indexes depend on some invalid/non-existent package/function specification/body.
Action: Verify that all the package/functions which the index depends on exist and are valid.
ORA-30551 The index depends on a package/type body which does not exist
Cause: The functional indexes depend on a package/type body which does not exist.
Action: Create the package/type body.
ORA-30552 The package/procedure/function cannot be changed
Cause: The package/procedure/function is deterministic and some object depends on it.
Action: Drop the other object which depends on the package/function/procedure you are trying to change.
ORA-30553 The function is not deterministic
Cause: The function on which the index is defined is not deterministic.
Action: Mark the function deterministic.
ORA-30554 function-based index string.string is disabled
Cause: An attempt was made to access a function-based index that has been marked disabled because the function on which the index depends has been changed.
Action: Perform one of the following actions:
ORA-30555 global index partitioning key is an expression
Cause: An attempt was made to use an expression as a partitioning key in an index.
Action: Do not attempt to use an expression as index partitioning key.
ORA-30560 SAMPLE option not allowed with index-organized tables
ORA-30561 SAMPLE option not allowed in statement with multiple table references
ORA-30562 SAMPLE percentage must be in the range [0.000001,100)
ORA-30575 ConText Option not installed
Cause: Oracle executable does not have ConText Option linked in.
Action: Get the correct version of Oracle.
ORA-30576 ConText Option dictionary loading error
Cause: ConText dictionary tables may be corrupted. This is an internal error.
Action: Contact Oracle Customer Support.
ORA-30625 method dispatch on NULL SELF argument is disallowed
Cause: A member method of a type is being invoked with a NULL SELF argument.
Action: Change the method invocation to pass in a valid self argument.
ORA-30726 cannot specify referenced column list here
Cause: An attempt was made to specify a referenced column list for a referential constraint involving a REF column.
Action: Remove the referenced column list specification.
ORA-30727 duplicate referential constraint for a REF column
Cause: Multiple referential constraints were specified for a single REF column.
Action: Remove the duplicate referential constraint and retry the operation.
ORA-30728 maximum number of columns exceeded
Cause: Adding referential constraint on a REF column requires the creation of an additional column.
Action: Drop some columns and retry the operation.
ORA-30729 maximum number of columns exceeded
Cause: Adding scope or referential constraint on a REF column requires the creation of additional columns if the target table's object identifier is primary key based.
Action: Drop some columns and retry the operation.
ORA-30730 referential constraint not allowed on nested table column
Cause: An attempt was made to define a referential constraint on a nested table column.
Action: Do not specify referential constraints on nested table columns.
ORA-30731 scope constraint not allowed on nested table column when the nested table is being created
Cause: An attempt was made to define a scope constraint on a nested table column when the nested table is being created.
Action: Do not specify a scope constraint on a nested table column when creating it. Instead, specify it using the ALTER TABLE statement.
ORA-30732 table contains no user-visible columns
Cause: An attempt was made to query on a system table which has no user-visible columns.
Action: Do not query on a system table that has no user-visible columns.
ORA-30733 cannot specify rowid constraint on scoped ref column
Cause: An attempt was made to specify ROWID constraint on a scoped REF column.
Action: Remove the ROWID constraint and then retry the operation.
ORA-30734 cannot specify scope constraint on ref column with rowid
Cause: An attempt was made to specify scope constraint on a REF column with the ROWID constraint.
Action: Remove the scope constraint and then retry the operation.
