Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
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.
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.
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.
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.
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.
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.
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.
Cause: The specified host name was unknown.
Action: Check the spelling of the host name or the IP address. Make sure that the host name or the IP address is valid.
Cause: The input or output buffer was too small for the operation.
Action: Increase the size of the buffer and retry the operation.
Cause: The end of the input was reached.
Action: If the end of the input is reached prematurely, check if the input source terminates prematurely. Otherwise, close the connection to the input.
Cause: A network error occurred.
Action: Fix the network error and retry the operation.
Cause: A bad argument was passed to the PL/SQL API.
Action: Check the arguments passed to the PL/SQL API and retry the call.
Cause: An improperly formed URL was passed to the PL/SQL API.
Action: Check the URL and retry the call.
Cause: An HTTP protocol error occurred during the HTTP operation.
Action: Check the HTTP server on which the HTTP operation was performed to make sure that it follows the HTTP protocol standard.
Cause: The URL scheme was unknown or unsupported.
Action: Check the URL to make sure that the scheme is valid and supported.
Cause: The requested HTTP header was not found.
Action: Check to make sure that the requested HTTP header is present.
Cause: The end of the HTTP response body was reached.
Action: If the end of the HTTP response is reached prematurely, check if the HTTP response terminates prematurely. Otherwise, end the HTTP response.
Cause: The call to the PL/SQL API was illegal at the current stage of the operation.
Action: Retry the call at a different stage of the operation.
Cause: The HTTP response indicated that the HTTP client error occurred.
Action: Fix the HTTP client error and retry the HTTP request.
Cause: The HTTP response indicated that the HTTP server error occurred.
Action: Fix the HTTP server error and retry the HTTP request. Contact the administrator of the HTTP server when necessary.
Cause: Too many HTTP requests were opened.
Action: End some HTTP requests and retry the HTTP request.
Cause: The network connection was not made while the network operation was attempted.
Action: Retry the network operation after the network connection is made successfully.
Cause: The UTL_HTTP package failed to initialize.
Action: Free up some memory or other system resources and retry the operation.
Cause: The UTL_HTTP package failed to execute the HTTP request.
Action: Use get_detailed_sqlerrm to check the detailed error message. Fix the error and retry the HTTP request.
Cause: The character set used as an encoding of the URL is a fixed-width multibyte character set and is not allowed for a URL.
Action: Use the corresponding variable-width multibyte character set for the URL instead.
Cause: The requested read operation could not complete because a partial multibyte character was found at the end of the input.
Action: Ensure that the complete multibyte character is sent from the remote server and retry the operation. Or read the partial multibyte character as RAW.
Cause: Timeout occurred while reading from or writing to a network connection.
Action: Check the remote server or the network to ensure that it responds within the timeout limit. Or increase the timeout value.
Cause: The SMTP operation was invalid at the current stage of the SMTP transaction.
Action: Retry the SMTP operation at the appropriate stage of the SMTP transaction.
Cause: An SMTP transient error occurred.
Action: Correct the error and retry the SMTP operation.
Cause: An SMTP permanent error occurred.
Action: Correct the error and retry the SMTP operation.
Cause: A corresponding directory object does not exist.
Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command.
Cause: An invalid value was specified for file open mode.
Action: Correct the mode to be one of the values: 'r', 'a', or 'w'.
Cause: A file ID handle was specified for which no corresponding open file exists.
Action: Verify that the file ID handle is a value returned from a call to UTL_FILE.FOPEN.
Cause: An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system.
Action: Verify file and directory access privileges on the file system, and if reading, verify that the file exists.
Cause: An attempt to read from a file failed.
Action: Verify that the file exists, and that it is accessible, and that it is open in read mode.
Cause: Failed to write to, flush, or close a file.
Action: Verify that the file exists, that it is accessible, and that it is open in write or append mode.
Cause: A fatal error occurred while allocating PL/SQL session memory.
Action: Verify that the PL/SQL session is connected and that adequate memory resources are available.
Cause: An invalid maximum line size value was specified.
Action: Correct the maximum line size to be in the range [1, 32767].
Cause: A NULL or zero length file name was specified.
Action: Correct the file name to be a nonzero length string.
Cause: A directory object was specified for which no access is granted.
Action: Grant access to the directory object by issuing the statement GRANT READ ON DIRECTORY [object] TO [username];.
Cause: An attempt was made to seek past the end of the file, both the absolute and relative offsets were NULL, or the absolute offset was less than zero.
Action: If specifying an absolute offset, then ensure it is in the range [0, <total number of bytes in the file>], or if specifying a relative offset, then ensure it is no greater than the current byte position plus the number of bytes remaining in the file.
Cause: A file deletion attempt was refused by the operating system.
Action: Verify that the file exists and delete privileges granted on the directory and the file.
Cause: A file rename attempt was refused by the operating system either because the source or destination directory does not exist or is inaccessible, the source file isn't accessible, or the destination file exists.
Action: Verify that the source file, source directory, and destination directory exist and are accessible, and that the destination file does not already exist.
Cause: Another Oracle error occurred in the DBMS_PITR package.
Action: See the text of the error message for a description of the error.
Cause: The DBMS_PITR package function/procedure was called in an incorrect order.
Action: Restart tablespace point-in-time recovery with a correct procedure.
Cause: The database was not opened as a clone database.
Action: Mount the database clone and open the database.
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.
Cause: The selected tablespace does not exist in the database.
Action: Check the list of tablespaces in V$TABLESPACE and select a valid tablespace.
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.
Cause: The selected datafile was not online.
Action: Bring the datafile online and rename it if necessary.
Cause: The datafile is not ready for tablespace point-in-time recovery.
Action: Check the correct tablespace point-in-time recovery procedure.
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.
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.
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.
Cause: The export dump files were imported to an incorrect database.
Action: Open the correct production database and try the import again.
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.
Cause: This is an internal error.
Action: Contact your database administrator.
Cause: Tablespace clean SCN is either 0 or invalid.
Action: ALTER the tablespace OFFLINE FOR RECOVER.
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.
Cause: This is an internal error.
Action: Contact your database administrator.
Cause: The specified datafile could not be found in the production database.
Action: Copy the datafile from the clone database.
Cause: The datafile is online.
Action: Take the datafile offline.
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.
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.
Cause: Too many datafiles were added to the recovery set since the point-in-time recovery.
Action: Divide the recovery set into smaller subsets and retry.
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.
Cause: The rolling release feature was first implemented in 8.0.3.
Action: Try 8.0.3 or later.
Cause: It should be of the form 8.x.x.
Action: Use the correct format.
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.
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.
Cause: The client compatibility mode is higher than the version of the server.
Action: Using SET COMPATIBILITY command, specify the same release number as the server.
Cause: Too many datafiles in this bitmap tablespace.
Action: Contact Oracle Support Services.
Cause: The tablespace is not read only.
Action: Make the tablespace read only and retry the operation.
Cause: Internal error from package DBMS_PLUGTS.
Action: Contact Oracle Support Services.
Cause: The tablespace has a non-standard block size and making such a tablespace read-write is not permitted.
Action: Use some other mechanism to import the data.
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.
Cause: The block size of the tablespace to be plugged in or created does not match the block sizes configured in the database.
Action: Configure the appropriate cache for the block size of this tablespace using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.
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, then contact Oracle Support Services.
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.
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.
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.
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.
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.
Cause: The tablespace list supplied to DBMS_TTS.TRANSPORT_SET_CHECK. PL/SQL routine is in an incorrect format.
Action: Check the PL/SQL User's Guide and Reference and use the correct format.
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.
Cause: The datafiles to be plugged in are not specified.
Action: Specify the datafiles via the import DATAFILES command line option.
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.
Cause: The referenced tablespace is either the system tablespace or a temporary tablespace.
Action: Do not include this tablespace in the transportable set.
Cause: The transportable list exceeds the buffer size of 32767.
Action: Reduce the list of tablespaces to transport.
Cause: The named argument was either invalid or specified as a NULL.
Action: Specify non-null, valid arguments.
Cause: The below parameters were specified as an argument to the procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER where the GROUP_OR_SUBPLAN argument is a resource plan. "ACTIVE_SESS_POOL_P1", "QUEUEING_P1", "PARALLEL_DEGREE_LIMIT_P1", "SWITCH_P1", "SWITCH_P2", "SWITCH_P3", "MAX_EST_EXEC_TIME", "UNDO_POOL"
Action: Specify these parameters only for consumer group directives.
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.
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.
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.
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.
Cause: An invalid percentage value was specified.
Action: Specify a percentage value between 0 and 100 inclusive.
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.
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.
Cause: An attempt was made to create a plan directive that already exists.
Action: Retry the create operation using different values.
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.
Cause: An invalid consumer group name was specified.
Action: Specify a non-NULL, valid consumer group name.
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.
Cause: An non-existent consumer group was specified.
Action: Specify an existing consumer group.
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.
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.
Cause: An attempt was made to make changes without creating a pending area.
Action: Invoke procedure CREATE_PENDING_AREA before making any changes.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Invalid changes were attempted in the pending area.
Action: See documentation and the error messages that follow this one.
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.
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.
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.
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.
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.
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.
Cause: The number of errors detected during validation is too high.
Action: Perform the necessary actions to remove some errors, and retry validation.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error.
Action: See the Oracle9i Data Cartridge Developer's Guide for an explanation of the second error message.
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.
Cause: The required name for a Java source, class, or resource was invalid or missing.
Action: Specify a valid name.
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.
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.
Cause: The required schema name was invalid or missing.
Action: Specify a valid schema name.
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.
Cause: The USING clause did not form a valid query.
Action: Correct the USING clause.
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.
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.
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.
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.
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.
Cause: A name resolver was not specified in the required form: (( name_pattern , schema_name) ...).
Action: Correct the specification.
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.
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.
Cause: Java code included a call to java.lang.Runtime.exitInternal.
Action: Do not include this call unless non-local exit is desired.
Cause: An internal error occurred in the Aurora module.
Action: Contact Oracle Support Services.
Cause: An attempt to resolve a referenced class failed.
Action: Review the errors for referenced classes and complete the necessary actions to correct them.
Cause: A referenced name was resolved to an object that is not a Java class.
Action: Adjust name resolver or add missing Java class.
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.
Cause: An attempt to access a referenced class failed.
Action: Adjust authorizations or name resolution.
Cause: Name resolution failed to find an object with the indicated name.
Action: Adjust name resolver or add missing Java class.
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.
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.
Cause: A method was called with argument(s) of incompatible type(s).
Action: Adjust caller.
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.
Cause: An informational message, not an error.
Action: No action required.
Cause: An informational message, not an error.
Action: No action required.
Cause: The Java method specified in trigger does not exist or cannot be called as used.
Action: Adjust trigger definition.
Cause: The function or method specified in Java trigger call expression could not be resolved.
Action: Adjust trigger definition.
Cause: Insert into shortened name translation table failed.
Action: Retry the insert.
Cause: An attempt was made to execute a non-existent method in a Java class.
Action: Adjust the call or create the specified method.
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.
Cause: A class or resource defined by a SQLJ source conflicted with an existing object.
Action: Remove existing object, or modify SQLJ source.
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.
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.
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.
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.
Cause: An attempt was made to use a Java command when Java is not installed.
Action: Install Java, or do not use the command.
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.
Cause: Java method execution failed to find a class with the indicated name.
Action: Correct the name or add the missing Java class.
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.
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.
Cause: An attempt was made to use a Java command that is not yet implemented.
Action: Do not use the command.
Cause: The type argument in a call to a Java export or import command did not have a recognized value.
Action: Correct the value.
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.
Cause: An attempt was made to create a Java resource object with data that was rejected by the Java verifier.
Action: Correct the data.
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.
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.
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.
Cause: The Java state in the current session became inconsistent and was cleared.
Action: No action required.
Cause: A string in the database character set could not be converted to Unicode, as required for use by Java.
Action: Correct the 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.
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.
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.
Cause: A Java source, class, or resource was specified in an inappropriate place in a statement.
Action: Make sure the name is correct or remove it.
Cause: A database object name that named a Java source, class, or resource now names an object of a different type.
Action: No action required.
Cause: A command was attempted that would have modified a Java system class.
Action: No action required.
Cause: The USING clause of a type has to be the same as its supertype or compatible with it.
Action: Make sure the USING clause is compatible with its supertype.
Cause: The class has to implement the required interface for the value of the option for USING.
Action: Make sure the USING clause is supported.
Cause: The supertype has an existing type that has the same value for the EXTERNAL NAME.
Action: Make sure the EXTERNAL NAME clause is unique among subtypes.
Cause: The EXTERNAL NAME clause of the type is not a subclass of the supertype EXTERNAL NAME.
Action: Make sure the EXTERNAL NAME clause of the type is a subclass of the EXTERNAL NAME of its supertype.
Cause: Unable to connect using the JDBC default connection.
Action: No action required.
Cause: The class is not loaded in the database.
Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the database.
Cause: The class is not loaded in the database.
Action: Make sure the superclass of the EXTERNAL NAME is loaded in the database.
Cause: The EXTERNAL NAME option of one or more attributes do not match any fields in the defined class.
Action: Make sure the EXTERNAL NAME option of each attribute matches a field in the defined in the defined class.
Cause: The EXTERNAL NAME option of one or more functions do not match any method in the defined class.
Action: Make sure the EXTERNAL NAME option of each function matches a method in the defined in the defined class.
Cause: The helper class used for supporting SQLJ Object Type is not generated.
Action: No Action required.
Cause: The Java VM has detected a thread deadlock.
Action: Modify the Java program to avoid the deadlock condition.
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.
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.
Cause: An unexpected error occurred while performing a global enqueue service operation.
Action: Check Oracle trace files for errors.
Cause: The ACTIVE_INSTANCE_COUNT initialization parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release.
Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT initialization parameter. Or, upgrade all instances to Oracle 8.1.6 or later release and then specify the parameter.
Cause: The value of the ACTIVE_INSTANCE_COUNT initialization parameter must be the same in all Oracle cluster database instances.
Action: Check your initialization parameter files in all instances and ensure that the ACTIVE_INSTANCE_COUNT initialization parameter has the same value. Then restart the instance.
Cause: The ACTIVE_INSTANCE_COUNT initialization parameter must be set to 1 in a two node cluster database configuration or unspecified if a secondary instance is not needed.
Action: Check your initialization parameter files and correct the value of the ACTIVE_INSTANCE_COUNT initialization parameter. If you are configuring a two node primary/secondary cluster database, then set this value to 1. Otherwise, do not specify any value for the parameter.
Cause: This member was evicted from the group by another member of the cluster database for one of several reasons, which may include a communications error in the cluster, failure to issue a heartbeat to the control file, and so on.
Action: Check the trace files of other active instances in the cluster group for indications of errors that caused a reconfiguration.
Cause: The IMR feature is not active for this instance, but is active for another instance in the cluster database.
Action: Ensure that all instances have the same value for the _imr_active initialization parameter.
Cause: The initialization parameter file did not contain a value for the INSTANCE_NUMBER parameter which is required to identify this instance to other instances of the database running on the same cluster.
Action: Assign a value to the INSTANCE_NUMBER parameter in the initialization parameter file.
Cause: The name specified for the operator is incorrect.
Action: Specify a correct name for the operator.
Cause: The RETURN keyword has not been specified.
Action: Specify the RETURN keyword or check the SQL statement.
Cause: The CONTEXT keyword has not been specified.
Action: Specify the CONTEXT keyword or check the SQL statement.
Cause: The ANCILLARY keyword has not been specified.
Action: Specify the ANCILLARY keyword or check the SQL statement.
Cause: The DATA keyword has not been specified.
Action: Specify the DATA keyword or check the SQL statement.
Cause: Keyword COLUMN is expected.
Action: Either specify the COLUMN keyword or specify another option.
Cause: The operator binding which has been specified does not exist.
Action: Ensure that the operator binding that has been specified does exist.
Cause: The operator which has been specified does not exist.
Action: Ensure that the operator that has been specified does exist.
Cause: The specified binding for the primary operator does not exist.
Action: Ensure that the specified binding for the primary operator exists.
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.
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.
Cause: This is not a valid option with the ASSOCIATE command.
Action: Specify STATISTICS keyword after the ASSOCIATE command.
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.
Cause: The type of object specified is not supported with the associate statistics statement.
Action: Use a valid object type with the associate command.
Cause: Expecting the USING or DEFAULT keyword after the names of object(s).
Action: Provide the USING or DEFAULT keyword.
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.
Cause: Object which is being disassociated is not present.
Action: Ensure that the object which needs to be disassociated is present.
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.
Cause: Name of the column should contain the table and the column name.
Action: Specify a valid column name.
Cause: An attempt was made to associate DEFAULT values with columns which is not a valid option.
Action: Specify a valid option.
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.
Cause: The specified primary operator does not exist.
Action: Check the primary operator and the signature specified.
Cause: An attempt was made to associate selectivity with index or index types which is not allowed.
Action: Specify a valid option.
Cause: The object being analyzed is not a table and is not supported.
Action: Specify only a supported option.
Cause: The operator is invalid.
Action: Drop and re-create the operator.
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.
Cause: FOR keyword must be provided with CREATE INDEXTYPE statement.
Action: Use FOR keyword and provide relevant operator information.
Cause: USING keyword and corresponding implementation details must be provided.
Action: Provide USING keyword and relevant implementation details with CREATE INDEXTYPE statement.
Cause: Implementation type or Implementation schema name is invalid.
Action: Verify that the name has valid characters and it is not a reserved word.
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.
Cause: The operator could not be found.
Action: Verify that the operator exists and the user has EXECUTE privilege for this operator.
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.
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.
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.
Cause: The user specified a REF datatype which is not supported in CREATE OPERATOR.
Action: Reissue the CREATE OPERATOR statement without the REF datatype.
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).
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.
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.
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.
Cause: Implementation type cannot be compiled.
Action: Try to compile the implementation type.
Cause: Index type and implementation type are in different schema.
Action: Put the index type and implementation type in the same schema.
Cause: The user specified an invalid option with the ALTER INDEXTYPE command.
Action: Choose a valid option with the ALTER INDEXTYPE command.
Cause: User specified an option which is not supported with the version of the indextype interface provided.
Action: User should either not request for this option or should provide an implementation type that implements the correct version of the indextype interface.
Cause: User attempted to drop all the operators from the indextype.
Action: Do not drop all the operators from the indextype.
Cause: User attempted to add an operator name to an indextype which is already supported by the indextype.
Action: Remove the duplicate operator and retry the command.
Cause: User specified a create local domain index statement using an indextype that does not support local domain indexes on tables partitioned with the given method.
Action: Use a different indextype or build a global domain index.
Cause: User specified a create local domain index statement on a table partitioned using a method not supported by domain indexes.
Action: Build a global domain index on the partitioned table.
Cause: User specified a create local domain index statement on a partitioned index-organized table.
Action: Build a global domain index on the partitioned index-organized table.
Cause: Failed to successfully execute the ODCIIndexMergePartition routine.
Action: Check to see if the routine has been coded correctly.
Cause: Failed to successfully execute the ODCIIndexSplitPartition routine.
Action: Check to see if the routine has been coded correctly.
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.
Cause: User attempted to build a domain index on more than one column.
Action: Build the domain index only on a single column.
Cause: IS keyword must be specified with Create Index statement for domain indexes.
Action: Use IS keyword and then specify the index type name.
Cause: An attempt was made to create a domain index with the UNIQUE attribute.
Action: Remove UNIQUE from the CREATE INDEX statement.
Cause: An attempt was made to create a domain index with the BITMAP attribute.
Action: Remove BITMAP from the CREATE INDEX statement.
Cause: Failed to successfully execute the ODCIIndexCreate routine.
Action: Check to see if the routine has been coded correctly.
Cause: Failed to successfully execute the ODCIIndexDrop routine.
Action: Check to see if the routine has been coded correctly.
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.
Cause: Failed to successfully execute the ODCIIndexAlter routine.
Action: Check to see if the routine has been coded correctly.
Cause: Failed to successfully execute the ODCIIndexTruncate routine.
Action: Check to see if the routine has been coded correctly.
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.
Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.
Action: Wait if the specified index is marked LOADING Drop the specified index if it is marked FAILED Drop or rebuild the specified index if it is marked UNUSABLE.
Cause: A DROP INDEX FORCE was issued for a non-domain index.
Action: Reissue the command without the FORCE option.
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.
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.
Cause: The index type is invalid.
Action: Drop and re-create the index type.
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.
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.
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.
Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state.
Action: Truncate the table to mark the index as valid OR do ALTER INDEX REBUILD to rebuild the index.
Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index.
Action: Reissue the statement with the correct syntax for alter.
Cause: The user specified an invalid option for altering a domain index.
Action: Reissue the alter statement with a valid option.
Cause: The user combined PARAMETERS clause with other alter index options.
Action: Reissue the statement with the correct syntax for alter.
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.
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.
Cause: Failed to successfully execute the ODCIIndexInsert routine.
Action: Check to see if the routine has been coded correctly.
Cause: Failed to successfully execute the ODCIIndexDelete routine.
Action: Check to see if the routine has been coded correctly.
Cause: Failed to successfully execute the ODCIIndexUpdate routine.
Action: Check to see if the routine has been coded correctly.
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.
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.
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.
Cause: Index type cannot be compiled.
Action: Try to compile the index type which is referenced by the domain index.
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.
Cause: User specified an expression in the column list.
Action: Specify only simple columns in the column list for domain index.
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.
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.
Cause: Feature is not supported for domain indexes.
Action: No action required.
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.
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.
Cause: The primary operator does not have an index and scan contexts.
Action: Create the primary operator with a context clause.
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.
Cause: The function underlying the operator binding does not exist.
Action: Ensure that the function corresponding to the operator invocation exists.
Cause: The execution of ODCIIndexStart routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.
Cause: The execution of ODCIIndexFetch routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.
Cause: The execution of ODCIIndexClose routine caused an error.
Action: Examine the error messages produced by the index type code and take appropriate action.
Cause: A required method with the required signature does not exist in the specified type.
Action: Add the required method to the type.
Cause: The index type does not exist.
Action: Create the index type.
Cause: There are multiple primary invocations of operators with the same number as the label.
Action: Use distinct labels in primary invocations.
Cause: The primary invocation corresponding to an ancillary operator is missing.
Action: Add the primary invocation with the same label as the ancillary operator.
Cause: The label used for invoking the ancillary operator is not a literal number.
Action: Use a literal number as the label.
Cause: Encountered an invalid callback operation.
Action: Ensure that all the callbacks executed from callouts are valid in the statement context.
Cause: The ODCIIndexStart() routine returned a null scan context.
Action: Ensure that the ODCIIndexStart() routine returns a non-null scan context.
Cause: The execution of the specified callout caused an error.
Action: Examine the error messages take appropriate action.
Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the required stream version for external tables.
Action: Ensure that the ODCIGetInterfaces routine returns the required stream version.
Cause: Collection operands cannot be updated.
Action: Remove the FOR UPDATE clause.
Cause: The specified function does not exist or does not have an appropriate signature.
Action: Implement the function with the appropriate signature.
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.
Cause: The ODCIStatsCollect/ODCIStatsDelete function is causing an error.
Action: Check the ODCIStatsCollect/ODCIStatsDelete function.
Cause: The keyword DEFAULT SELECTIVITY can only be specified once.
Action: Remove the duplicate keyword.
Cause: The scan context is not specified.
Action: Supply the SCAN keyword.
Cause: The COMPUTE ANCILLARY DATA option was specified without the WITH INDEX CONTEXT clause.
Action: Specify the WITH INDEX CONTEXT option.
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.
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.
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.
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.
Cause: The keyword FROM is missing.
Action: Specify the FROM keyword or check the SQL statement.
Cause: User tried to use the ASSOCIATE command with a schema object other than a column or an index.
Action: Specify the NULL clause only with a column or an index.
Cause: A warning was returned from the ODCIIndexMergePartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.
Cause: A warning was returned from the ODCIIndexSplitPartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.
Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition in a LOADING state.
Action: Wait until the index partition operation completes, issue a DROP INDEX FORCE to drop the index, OR issue an ALTER TABLE DROP PARTITION to drop the partition.
Cause: Tried to issue a DROP/ALTER on a domain index partition in a FAILED state.
Action: do ALTER INDEX REBUILD PARTITION to rebuild the index partition OR ALTER TABLE TRUNCATE PARTITION to mark the index partition as valid.
Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.
Action: Wait if the specified index partition is marked LOADING. Rebuild the specified index partition if it is marked FAILED or UNUSABLE.
Cause: Failed to successfully execute the ODCIIndexExchangePartition routine.
Action: Check to see if the routine has been coded correctly.
Cause: A warning was returned from the ODCIIndexExchangePartition routine.
Action: Check to see if the routine has been coded correctly. Check user specified log tables for greater detail.
Cause: User specified an unsupported create function-based domain index statement.
Action: Issue the create function-based domain index statement only on supported types of tables.
Cause: Failed to successfully execute the ODCIIndexCreate routine.
Action: Check to see if the routine has been coded correctly.
Cause: An error occurred during execution of the routine for one or more of the index partitions.
Action: Check the *_IND_PARTITIONS view to see which partitions are marked FAILED. Rebuild or Truncate the FAILED index partitions.
SYS.ODCI_WARNINGS$.Action: Check the warning message.
Cause: The number of warnings during the ODCIIndex DDL routine is too high.
Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages.
Cause: Failed to successfully execute the ODCIIndexAlter routine.
Action: Check to see if the routine has been coded correctly.
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.
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.
Cause: SYS_CONNECT_BY_PATH function is called at places other than select list.
Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than select list.
Action: use a non-empty constant string as the second argument and retry the operation.
Action: Use another seperator which does not occur in any column value and retry.
Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword.
Action: Correct the syntax and retry.
Cause: The requested resource is busy.
Action: Retry the operation later.
Cause: the specified undo tablespace either does not exist or is of the wrong type.
Action: Correct the tablespace name and reissue the statement.
Cause: the specified undo tablespace is currently used by another instance.
Action: Wait for the undo tablespace to become available or change to another name and reissue the statement.
Cause: the operation is only supported in automatic undo mode.
Action: restart the instance in Automatic Undo Management mode before retrying the operation.
Cause: the current operation is not allowed because an undo tablespace containing active transactions is pending from a previous SWITCH UNDO operation. The operation will be allowed again after all transactions in the previous undo tablespace are committed.
Action: Wait for all previous transactions to commit before reissuing the current statement.
Cause: the specified undo tablespace is currently used by this instance. The operation failed.
Action: If the specified undo tablespace name is incorrect, reissue the statement with the correct name.
Cause: The type of the specified undo segment is incompatible with the current undo management mode of the instance.
Action: Check the undo segment name and the undo management mode and reissue the statement if necessary.
Cause: the system runs out of undo segment number. Too many undo segments exist.
Action: drop some of the unused undo segments and retry the operation.
Cause: This operation is only allowed in Manual Undo mode.
Action: Restart the instance in Manual Undo_Management mode and retry the operation.
Cause: Auto undo management mode is not allowed in the specified compatibility release.
Action: restart the instance in correct compatibility release.
Cause: This operation is not allowed on undo tablespaces.
Action: Check the tablespace name and reissue the command if necessary.
Cause: Cannot create segments in undo tablespace.
Action: Check the tablespace name and reissue the command.
Cause: Cannot create more than one undo tablespace during database creation.
Action: Modify the command to contain only one undo tablespace.
Cause: You have specified a clause that should not be used with CREATE UNDO TABLESPACE.
Action: Drop the clause from the command and reissue it.
Cause: Explicit DROP operation is not allowed on undo tablespace segments.
Action: Check the undo segment name and reissue the statement if necessary.
Cause: Tried to drop a tablespace that contains unexpired undo information.
Action: lower the setting of UNDO_RETENTION or wait a while before reissuing the command to drop undo tablespace.
Cause: the amount of undo assigned to the consumer group of this session has been exceeded.
Action: ask the database administrator to increase undo quota, or wait until other transactions commit.
Cause: the current instance does not have an active undo tablespace assigned to execute transactions.
Action: ask the database administrator to create an undo tablespace, online the undo tablespace and then retry the operation.
Cause: The database administrator or the user aborted the execution of the suspended statement in the resumable session.
Action: No action required.
Cause: A correctable error was signaled in the resumable session and the error was not cleared within the timeout interval.
Action: Fix the correctable error within the timeout. The default is 2 hours. Alternatively, increase the (resumable) timeout.
Cause: It is incorrect to specify undo tablespace as default user tablespace.
Action: Check the tablespace name and reissue the command.
Cause: Undo tablespace cannot be specified as default temporary tablespace for the user.
Action: Check the tablespace name and reissue the command.
Cause: Undo tablespace cannot be specified as default temporary tablespace for the database.
Action: Check the tablespace name and reissue the command.
Cause: the specified undo tablespace has no more space available.
Action: Add more space to the undo tablespace before retrying the operation. An alternative is to wait until active transactions to commit.
Cause: Attempt to perform parallel DML after another DML on the same object in the same transaction.
Action: Use bitmap segments to perform multiple (parallel) DML operations on the same object. Alternatively, commit before issueing the DML.
Cause: Attempt to perform parallel insert on a non-partitioned object after a previous DML on the object in the same transaction.
Action: Commit before issueing the insert.
Cause: Cannot drop an undo tablespace that is in use.
Action: Switch to a different undo tablespace and then try to drop.
Cause: Cannot operate on an offlined undo tablespace.
Action: Online the undo tablespace and redo the operation.
Cause: User tried to grant quota on an undo tablespace.
Action: Check the tablespace name and reissue the command.
Cause: Cannot offline an undo tablespace that is in use.
Action: Switch to a different undo tablespace and then try to offline.
Cause: The specified undo management mode is invalid.
Action: Correct the parameter value in the initialization parameter file and retry the operation.
Cause: If Create Database has the datafile clause, then undo tablespace name has to be specified, unless using OMF.
Action: Specify the undo tablespace name.
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.
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.
Cause: The value is none of the followings: 'ADJUST', 'NO_ADJUST', 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value.
Action: Set it to one of the three values.
Cause: An attempt was made to GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE.
Action: Do not GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE.
Cause: An attempt was made to create a constraint on a time or timestamp with or without time zone column without explicitly specifying the time zone.
Action: Use time or timestamp with time zone literals only.
Cause: The extract source does not contain the specified extract field.
Action: Specify a valid extract field for the extract source.
Cause: Cannot cast between the specified datetime types.
Action: No action required.
Cause: An attempt was made to use a time/timestamp expression whose format does not explicitly have time zone on a TIME/TIMESTAMP WITH TIME ZONE column.
Action: Explicitly use the TIME/TIMESTAMP WITH TIME ZONE literal.
Cause: The data types of the operands are not valid for datetime/interval arithmetic.
Action: Specify valid data types for datetime/interval arithmetic.
Cause: Datetime/interval column with existing data is being modified to decrease fractional second or leading field precisions.
Action: Such columns are only allowed to increase the precisions.
Cause: A syntax error was found during parsing an interval value expression.
Action: Correct the syntax.
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.
Cause: A syntax error was found during parsing an overlaps predicate.
Action: Correct the syntax.
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.
Cause: An attempt was made to add two datetime values.
Action: This addition is not allowed.
Cause: The specified datetime/interval precision was not between 0 and 9.
Action: Use a value between 0 and 9 for datetime/interval precision.
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.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.
Cause: You have misspelled the parameter name.
Action: Spell the parameter name correctly.
Cause: The value of the parameter is not within the legal range.
Action: Refer to the Oracle9i SQL Reference for the allowable values for this parameter.
Cause: An illegal integer radix specification was found.
Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.
Cause: The value is not a valid integer.
Action: Specify only valid integers for this parameter.
Cause: The value is not a valid boolean.
Action: Refer to the Oracle9i SQL Reference for allowable boolean values.
Cause: This message is reserved for future use.
Action: No action required.
Cause: The abbreviation given was not unique.
Action: Use a longer abbreviation to make the parameter name unique.
Cause: An invalid positional parameter value has been entered.
Action: Remove the invalid positional parameter.
Cause: The parameter file does not exist.
Action: Create an appropriate parameter file.
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
Cause: A quoted string was begun but not finished.
Action: Put a closing quote in the proper location.
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.
Cause: A problem occurred when processing this file.
Action: Examine the additional error messages and correct the problem.
Cause: A problem occurred when processing the command line.
Action: Examine the additional error messages and correct the problem.
Cause: A problem occurred when processing an environment variable.
Action: Examine the additional error messages and correct the problem.
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
Cause: No valid value was obtained for this parameter.
Action: Rerun the application and enter a valid value.
Cause: The value is not a valid Oracle number.
Action: Refer to the Oracle9i SQL Reference for allowable Oracle number values.
Cause: The value is not a legal value for this parameter.
Action: Refer to the manual for allowable values.
Cause: The value of the parameter is not within the legal range.
Action: Specify a value that is within the legal range.
Cause: A function received an invalid argument.
Action: Check function calls and make sure correct arguments are being passed.
Cause: A function received an invalid parameter key type.
Action: Check parameter key types in function calls.
Cause: The number of parameter keys being set exceeds allocation.
Action: Reduce the number of keys being set or increase allocation.
Cause: The key index specified was not within bounds.
Action: Change key index to ensure it lies within bounds.
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.
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.
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.
Cause: The OCIFile function requires the file to exist, but it does not.
Action: Make sure that the file exists.
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.
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.
Cause: An I/O error occurred at the system level.
Action: This is a system error and the action will depend on the error.
Cause: The disks associated with the underlying file system are full.
Action: Create more disk space.
Cause: The operating system call was called with an invalid argument.
Action: Check the values passed. If you are unable to solve the problem, then contact Oracle Support Services.
Cause: There is no space to write to the file. Its size is at the maximum limit.
Action: If you can, increase the limit.
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.
Cause: The function was unable to access the existing the file.
Action: Check if the user has the required permissions on the file.
Cause: A system error occurred while executing the OCIFile function.
Action: Investigate and solve the system error.
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.
Cause: The call to SlgInit failed in OCIFileInit.
Action: Contact Oracle Support Services.
Cause: There is an argument with an invalid type in the argument list.
Action: Use the correct type wrapper for the argument.
Cause: There is an invalid format code in the format string.
Action: Replace the invalid format code with a valid one.
Cause: There is an invalid flag in a format specification.
Action: Replace the invalid flag with a valid one.
Cause: There is a duplicate flag in a format specification.
Action: Remove the duplicate flag.
Cause: Zero or negative argument index or index not following (.
Action: Replace the invalid argument index with a valid one.
Cause: An argument index exceeds actual number of arguments supplied.
Action: Fix format string or pass additional arguments.
Cause: Missing closing parenthesis in argument index.
Action: Fix the format specification.
Cause: Period in format specification not followed by valid format.
Action: Replace the invalid precision specifier with a valid one.
Cause: Invalid field width supplied.
Action: Replace the invalid field width with a valid one.
Cause: Bad argument type given for a format code.
Action: Make format and arguments be compatible.
Cause: The buffer is not large enough to hold the entire output string.
Action: Fix the buffer size and length passed in.
Cause: In the argument of SQL function UNISTR, a '\' must be followed by four hexadecimal characters or another '\'.
Action: Fix the string format.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: No argument list supplied.
Action: Modify the argument list to have at least OCIFormatEnd in it.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: This message is reserved for future use.
Action: No action required.
Cause: The item is not supported NLS item.
Action: Correct the item number passed to OCINlsGetInfo().
Cause: It may be caused by invalid NLS environment setting.
Action: Check your NLS environment setting such as ORA_NLS33.
Cause: The NULL pointer was passed.
Action: Check the value of the OCIMsgh pointer.
Cause: The message may not exist in your system.
Action: Check the message for the given product and facility.
Cause: The destination buffer is not large enough for storing converted data.
Action: Check the size of the destination buffer.
Cause: The specified character set is invalid.
Action: Check if the character set ID is valid.
Cause: A non-existent summary name was specified.
Action: Check the spelling of the summary name.
Cause: Another summary is already using this table as a container table.
Action: Select another table or materialized view as the container table for this summary.
Cause: The dimension named in a dimension DDL statement does not exist.
Action: Check the spelling of the dimension 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.
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.
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.
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.
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.
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.
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.
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.
Cause: A reference to a level not defined within the dimension was found.
Action: Check the spelling of the level name.
Cause: Two or more levels were defined with the same name.
Action: Check the spelling of the level names.
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.
Cause: A circularity was found the dimension hierarchy.
Action: Check the hierarchy for a level name that occurs more than once.
Cause: The same name was used for more than one hierarchy in a dimension.
Action: Check the spelling of the hierarchy name.
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.
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.
Cause: A hierarchy name was encountered that is not defined within the dimension.
Action: Check the spelling of the hierarchy name.
Cause: An attribute name was encountered that is not defined within the dimension.
Action: Check the attribute name spelling.
Cause: A complex expression was specified that is not currently supported by query rewrite.
Action: Reduce the complexity of the expression.
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.
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.
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.
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.
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.
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.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
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.
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.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
Cause: The dimension statement referenced a column that is a sequence.
Action: Remove the reference to the sequence.
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.
Cause: The level definition contained the same set of columns as another level.
Action: Eliminate the redundant level definition.
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.
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.
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.
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.
Cause: A list of columns was specified using more than 32 columns.
Action: Specify the list using no more than 32 columns.
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.
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.
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.
Cause: An object data type was encountered in an unsupported context.
Action: Re-specify the expression to avoid the use of objects.
Cause: If the materialized view is fresh, ORACLE ignores the ALTER MATERIALIZED VIEW <mv> RELY FRESH command, and issues this error message.
Action: No action required.
Cause: If the materialized view is invalid or unusable, it cannot be considered fresh with the ALTER MATERIALIZED VIEW <mv> CONSIDER FRESH command.
Action: No action required.
Cause: Explain rewrite generates a shared cursor after parsing the user query. Raising this error will prevent the cursor from being shared.
Action: No action required.
Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() API before you have defined the MV_CAPABILITIES_TABLE.
Action: Invoke the ORACLE_HOME/rdbms/admin/utlxmv.sql script after connecting to the desired schema.
Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is either missing or incompatible with the current Oracle version.
Action: Connect to the appropriate schema, DROP TABLE MV_CAPABILITIES_TABLE, and recreate it by invoking the ORACLE_HOME/rdbms/admin/utlxmv.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Cause: You have attempted to use the DBMS_MVIEW.EXPLAIN_REWRITE() API with an empty query text argument.
Action: Input a valid SQL query.
Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have created the REWRITE_TABLE.
Action: Create it using the ORACLE_HOME/rdbms/admin/utlxrw.sql script after connecting to the desired schema.
Cause: One or more column definitions in the REWRITE_TABLE is either missing or incompatible with the current Oracle version.
Action: Connect to the appropriate schema, DROP TABLE REWRITE_TABLE and recreate it by invoking the ORACLE_HOME/rdbms/admin/utlxrw.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_REWRITE() API.
Cause: The drop materialized view operation got an unexpected error while dropping a summary object.
Action: Re-issue the drop materialized view command.
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
Cause: An invalid refresh method was specified.
Action: Verify that the refresh method is one of 'ANY' or 'INCREMENTAL' or 'FORCE_FULL'.
Cause: The summary is in INVALID state and cannot be refreshed.
Cause: There is no such summary, therefore it cannot be refreshed.
Action: Verify the correct name of the summary.
Cause: An invalid refresh method was specified.
Action: Verify that the refresh method is one of 'FC?AN'.
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.
Cause: The refresh process was unable to open a named pipe to the job queue process usually because of insufficient system resources. This is an internal error.
Action: Contact Oracle Support Services.
Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition. This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: Both DML and direct-load are performed against detail tables. Fast refresh can only process direct-load inserts.
Action: Refresh complete or set event 30441 to enable partial refresh with only direct-load inserts.
Cause: For the specified filterid parameter, there is no corresponding filter definition found in the advisor repository.
Action: Use a valid filterid generated by the create_filter function.
Cause: The specified filter is invalid. It contains at least one invalid filter item. If a filter item has a string list, it becomes illegal when the string list cannot be successfully parsed. If the filter item contains a range definition, and the lower bound of the range is greater than the higher bound, the item also becomes invalid.
Action: Remove the illegal filter with the purge_filter sub-program and redefine a correct filter.
Cause: No workload queries in the advisor repository can satisfy the specified filter.
Action: Redefine a new filter or load additional workload queries that can satisfy the specified filter.
Cause: None of the specified queries can be successfully parsed. The error may come from many sources: SQL syntax error or the owner specified by the load_workload() subprograms do not match the real user who generates the SQL statement.
Action: Only load valid SQL statements into the advisor repository. Make sure the statements can be parsed with privilege of the owner as specified in the owner parameter of the load_workload() subprogram.
Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.
Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove the inconsistent data from summary advisor's internal tables.
Cause: The syntax for the specified parameter is incorrect.
Action: Check ORACLE documentation for the correct syntax.
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.
Cause: An internal error was detected by the summary refresh subsystem, and aborted the refresh operation.
Action: Contact Oracle Support Services.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: There are three possible causes: The specified run_id does not exist; the run_id was created by another user other than the current user; the run_id has already been used.
Action: Call DBMS_OLAP.CREATE_ID to create a new id.
Cause: The specified workload_id is not valid.
Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL.
Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.
Action: Users can call the DBMS_OLAP.PURGE_FILTER subprogram to remove the inconsistent data from summary advisor's internal tables.
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user's schema. For more information, refer to the Oracle9i SQL Reference.
Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script UTLXPLAN.SQL will create this table.
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.
Cause: The specified dimension to be verified does not exist.
Action: Check the spelling of the dimension name.
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.
Cause: Window functions are allowed only in the SELECT list of a query. A window function cannot be a group function.
Cause: All window functions should be followed by window specification, like <function>(<argument list>) OVER (<window specification>)
Cause: Either the ORDER BY expression is mandatory for this function, or there is an aggregation group without any ORDER by expression.
Cause: If the window specification is specified using RANGE option and there are multiple ORDER BY expressions, then the aggregation group cannot contain any expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the first end point is CURRENT ROW, then second end point can only be CURRENT ROW or <expr> /UNBOUNDED FOLLOWING. If the first end point is <expr> FOLLOWING, then second end point can only be <expr>/UNBOUNDED FOLLOWING.
Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY clause.
Cause: The argument of the window function should be a constant for a partition.
Cause: GROUP BY clause has more than one rollup/cube expression list.
Action: Modify the query such that only one rollup/cube expression appears per sub-query.
Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an expression in the ordinary GROUP BY expression list.
Action: Remove the expression from either ordinary GROUP BY expression list or ROLLUP or CUBE expression list.
Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function is specified out of range.
Action: Specify a value from [0,1].
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Only BEFORE or AFTER triggers can be created on system events.
Action: Change the trigger type to BEFORE or AFTER.
Cause: A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration.
Action: Modify the trigger to avoid modifications to the objects in the same tablespace as the one which is being made read only, or use autonomous transactions to commit modifications.
Cause: An attempt was made to create a trigger that fires before execution suspended. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires before execution suspended.
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.
Cause: The functional indexes depend on a package/type body which does not exist.
Action: Create the package/type body.
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.
Cause: The function on which the index is defined is not deterministic.
Action: Mark the function deterministic.
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:
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.
Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which a functional index exists.
Action: Drop the functional index before attempting to modify the column.
Cause: The user updated a column on which a function based index is present which was not successfully updated.
Action: Determine the error in updating the index and fix the problem.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
Cause: An attempt was made to reference (+) in select-list.
Action: Do not use the operator in select-list.
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD partition to a HASH partitioned table or ADD subpartition to a composite partitioned table.
Action: Remove the clause and reissue the operation.
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES was specified more than once.
Action: Remove all but one of the INVALIDATE or UPDATE GLOBAL INDEXES clauses and reissue the statement.
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is not allowed for this command.
Action: Remove the clause and reissue the operation.
Cause: The specified log group name has to be unique.
Action: Specify a unique name for the log group. The name cannot be the same as any other log group, constraint, or cluster hash expression.
Cause: The <log_group_name> specified in alter table drop log group is incorrect or nonexistent.
Action: Reenter the statement using the correct log group name.
Cause: An attempt was made to include a column with one of these unsupported data types: LONG, VARRAY, nested table, object, LOB, FILE, or REF in a log group.
Action: Change the column data type or remove the log group. Retry the operation.
Cause: In CREATE TABLESPACE, the SEGMENT SPACE MANAGEMENT option was specified more than once.
Action: Remove all but one of the SEGMENT SPACE MANAGEMENT specifications.
Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause.
Action: Specify one of the valid options:
Cause: In CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used with a DICTIONARY extent management clause.
Action: Either specify LOCAL extent management or remove the AUTO SEGMENT SPACE MANAGEMENT specification.
Cause: In CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used while creating an UNDO or TEMPORARY tablespace.
Action: Remove the AUTO SEGMENT SPACE MANAGEMENT clause.
Cause: A rollback segment is being created in a tablespace that was created with AUTO segment space management.
Action: Create the rollback segment in a different tablespace.
Cause: Oracle executable does not have ConText Option linked in.
Action: Get the correct version of Oracle.
Cause: ConText dictionary tables may be corrupted. This is an internal error.
Action: Contact Oracle Support Services.
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.
Cause: Reject limit specifies the number of records rejected before terminating a table scan. The range is either a number between 1..100000 or UNLIMITED if no limit is intended.
Action: Change the token representing the reject limit to either a number in the range of 0 and 100000 or the keyword UNLIMITED.
Cause: A schema other then SYS was specified for the TYPE.
Action: For this version of the oracle server, always use schema name SYS.
Cause: an error occurred when fetching the access parameters for the specified external table.
Action: If the access parameter is a query which returns a CLOB, check EXTERNAL_TAB$ to make sure the query is correct.
Cause: DEFAULT DIRECTORY clause missing or incorrect.
Action: Provide the DEFAULT DIRECTORY.
Cause: The reject limit has been reached.
Action: Either cleanse the data, or increase the reject limit.
Cause: DEFAULT DIRECTORY clause not specified or incorrect.
Action: Provide the DEFAULT DIRECTORY.
Cause: A select for update on an external table was attempted.
Action: Do not select for update on an external table.
Cause: An attempt was made to create an external organized table with a column of type LONG, LOB, BFILE, ADT, or VARRAY.
Action: These column types are not supported, change the DDL.
Cause: User attempted on operation on an external table which is not supported.
Action: Do not attempt the operation.
Cause: An attempt was made to create an External Organized Temporary table. This is not supported.
Action: Do not attempt to create External Organized Temporary tables.
Cause: A problem kept a socket from reading or writing the expected amount of data. More specific information is not available.
Action: Try re-establishing a connection. You may need to restart whatever program is at the other end of the socket that failed, or you may need to have some problem on your network fixed.
Cause: An attempt to connect a session to a debugger could not proceed because the session is already connected to some debugger.
Action: Either use the option to force a connection or first disconnect the session from it's existing debugger.
Cause: An attempt to open a connection failed because too many are already open by this session. The number of allowed connections varies as some may be in use through other components which share the same pool of allowed connections.
Action: Retry after closing some other connection. The number of connections supported is currently not adjustable.
Cause: An attempt to open a debugging connection failed because this server configuration cannot support the required asynchronous socket traffic detection.
Action: This feature will not work under this server configuration. Either the feature is not supported on this platform at all, or is available only through use of a protocol=tcp dispatcher in shared-server configurations. Please consult the platform-specific documentation and "readme" material.
Cause: A problem occurred when trying to establish a debugger connection. This might indicate that the port specified as the location of the debugger is actually being used by some other type of application.
Action: Correct the host or port specifications if they are incorrect, and verify that the debugger is properly waiting for a connection.
Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP.
Action: Correct the indicated parameter value and try again.
Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP.
Action: Correct the indicated parameter value and try again.
Cause: An error was indicated when trying to establish a connection to a debugger. Usually a TNS error will display along with this message to further explain the problem, although this TNS error will likely be hidden if you choose to trap the error.
Action: Correct the indicated parameter value and try again.
Cause: The role specified for use by the debugger could not be enabled. The role may not exist or may not be granted to this user, the password specified may be incorrect, or the authenticating routine for the role is not currently active.
Action: Correct or remove the role or password argument in the debugger connection request.
Cause: The installed version of the DBMS_DEBUG_JDWP package is not compatible with the release of Oracle that is being used.
Action: Install the correct version of the DBMS_DEBUG_JDWP package.
Cause: rather than a dispatcher. When this occurs, shared servers are less beneficial because the session that owns the socket cannot relinquish the process until the socket is closed. The most likely cause is that no dispatcher is configured for protocol=tcp.
Action: To improve the scalability of your configuration, configure a dispatcher for protocol=tcp. To route these particular connections through a particular set of dispatchers, you can specify presentation=kgas. However, if you haven't done so, any protocol=tcp dispatcher will be used.
Cause: Your program's execution has been stopped by the debugger. This can occur because of an explicit request to do so sent by the debugger, or because the debugger disconnected without first telling Oracle to let your program continue to run after the disconnection. To stop your program completely, Oracle needs to fully terminate the process.
Action: This is in response to a debugger request; it is not an error. No action required.
Cause: Your program contains a set of calls that are too deep to be handled. Only transitions between the different execution engines (SQL, PL/SQL, and Java) count in reaching this limit; calls within the same engine don't count.
Action: Restructure your program so as to not call so deeply. Perhaps some recursion can be replaced with iteration.
Cause: An improper value was used for ORA_DEBUG_JDWP when trying to establish a connection to a debugger. The value either did not conform to the format of ORA_DEBUG_JDWP or was too long.
Action: Correct the value for ORA_DEBUG_JDWP and try again.
Cause: A timeout occurred while registering a TCP/IP connection for data traffic detection.
Action: Retry the operation later.
Cause: System resources ran out while registering a TCP/IP connection for data traffic detection.
Action: Retry the operation later.
Cause: A message passed from one software subcomponent to another using the JDWP protocol appears invalidly formatted.
Action: This is an internal error. Contact Oracle Support Services.
Cause: This feature is not yet available for use.
Action: Please wait for a future release.
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.
Cause: Multiple referential constraints were specified for a single REF column.
Action: Remove the duplicate referential constraint and retry the operation.
Cause: Adding referential constraint on a REF column requires the creation of an additional column.
Action: Drop some columns and retry the operation.
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.
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.
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.
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.
Cause: An attempt was made to specify ROWID constraint on a scoped REF column.
Action: Remove the ROWID constraint and then retry the operation.
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.
Cause: An attempt was made to create under a supertable (superview), a subtable(subview) of the same type as another existing subtable (subview).
Action: Drop the existing subtable(subview) and retry the operation.
Cause: An attempt was made to create a subtable(subview) under a supertable(superview) located in another schema.
Action: Connect as schema owner of the superobject and retry the operation.
Cause: An attempt was made to create a subtable(subview) of a type which is not a subtype of the type of the super object.
Action: Change the type of the subtable to be a subtype of the superobject's type and then retry the operation.
Cause: The specified object does not exist.
Action: Ensure that the specified object exists and retry the operation.
Cause: The user tried to drop a table that has subtables defined under it.
Action: Drop all subtables before trying this operation.
Cause: The user tried to grant UNDER privilege on an object that is not one of the following : non final object type, object table of non final type, object view of non final type.
Action: Ensure that the UNDER privilege is granted on a valid object.
Cause: The user tried to specify WITH HIERARCHY OPTION for a privilege other than SELECT privilege.
Action: Ensure that the HIERARCHY OPTION is specified only with the SELECT privilege.
Cause: The user tried to grant SELECT privilege WITH HIERARCHY OPTION on an object that is not one of the following : object table of non final type or object view of non final type.
Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is granted on a valid object.
Cause: The specified object is not an object view.
Action: Specify an object view and retry the operation.
Cause: The specified object is not an object table.
Action: Specify an object table and retry the operation.
Cause: The user tried to add a subtype which tried to alter the tables dependent on the supertype.
Action: Ensure that the table will not exceed the columnlimit on adding this subtype.
Cause: The user tried to drop a subtype with VALIDATE option which tried to check for stored instances of the type in the stated table.
Action: Delete all instances of this subtype and then drop the type.
Cause: The user tried to create substitutable table or column of a non final type. This operation is not currently supported.
Action: Change the statement to create a non substitutable table/column.
Cause: The user is trying to enable a column to store instances of a type for which it is already enabled.
Action: No action required.
Cause: The user is trying to disable a column from storing instances of a type for which it is already enabled.
Action: No action required.
Cause: The user is trying to enable a column to store instances of a subtype. The error is raised due to one of the following:
Action: Fix the cause of the error and retry the operation.
Cause: The user is trying to drop a type from being stored in a substitutable column or table. This error is raised due to one of the following reasons :
Action: Fix the cause of the error and retry the operation.
Cause: The user is performing an operation that is not allowed on non substitutable column or table.
Action: No action required.
Cause: The user is performing an operation that is not allowed on a substitutable column or table.
Action: No action required.
Cause: The user is trying to perform an operation that is not allowed on an object column or table that is enabled to store instances of a single type.
Action: No action required.
Cause: There was an error while trying to expand a view hierarchy. This could be due to invalid subviews (or subviews with errors).
Action: Ensure that all subviews are valid. For example alter view ... compile and retry the operation.
Cause: The user tried to create a column or table of an object type that contains a supertype attribute. This is not supported because it leads to infinite recursion in the current storage model. Note that creating a column of a type implies that we create columns corresponding to all subtype attributes as well.
Action: Change the type definition to contain a supertype REF attribute instead of the supertype object attribute.
Cause: Either a subtype was created and operations performed with this new type while the session was in progress, or the type information was unpinned from the object cache.
Action: Commit necessary changes, end the user session, reconnect again and re-try the object operations. If the problem persists, then contact Oracle Support Services.
Cause: An attempt was made to modify the scope for an unscoped REF column.
Action: Use an ALTER TABLE ADD SCOPE FOR command instead.
Cause: An attempt was made to modify the scope for a REF column with a REFERENCES constraint.
Action: Drop the REFERENCES constraint, and retry the operation.
Cause: An attempt was made to modify the scope for a REF column to a table whose object identifier's type is different from that of the original scoped table.
Cause: Pipelined functions can only be used in a TABLE expression in the FROM clause.
Action: Use a non-pipelined function instead.
Cause: Storage clause was specified during table creation for a fixed size opaque type.
Action: Do not provide storage option clause.
Cause: Multiple referential constraints were specified for a single REF column.
Action: Remove the additional referential constraints and retry the operation.
Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors.
Action: Add user-defined constructors to opaque type, or specify a member or static method for the opaque type.
Cause: A stable set of rows could not be got because of a large amount of DML activity or a non-deterministic where clause.
Action: Remove any non-deterministic where clauses and reissue the DML.
Cause: In memory temporary tables we create are aged out of shared pool before we are able to grab them again.
Action: Reduce activities that use a lot of shared pool space or wait for a while, then retry.
Cause: It is probably caused by the fact that there is a loop in the data.
Action: Retry the query with the NO_FILTERING hint. If the same error still occurs, then increase temp tablespace.
Cause: ORDER SIBLINGS BY clause is specified in a query which doesn't have CONNECT BY clause.
Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause.
Cause: The given schema URL does not refer to a registered XDB schema.
Action: Make sure the specified schema has been registered in XDB.
Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver.
Action: Pass a valid resource handle or path name to the hierarchical resolver.
Cause: XDB expected the given path name to represent a container.
Action: Pass a path name or resource handle that represents a container.
Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver.
Action: Insert a unique name into the container.
Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.
Action: Set the value of the DB_BLOCK_SIZE initialization parameter to at least 2 KB. For XDB to run at its fastest, set DB_BLOCK_SIZE to 8 KB.
Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length.
Action: Choose a shorter path name.
Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment.
Action: Choose a shorter path name segment.
Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver.
Action: Either perform a recursive deletion or first delete the contents of the container.
Cause: A stream error occurred in XDB.
Cause: An attempt was made to insert an XML element at an invalid index location in the node.
Action: Choose a new index that falls within the allowed range.
Cause: The XML parser returned an error while trying to parse the document.
Action: Check if the document to be parsed is valid.
Cause: XPATH expression passed to the function is currently unsupported.
Action: Check the xpath expression and change it to use a supported expression.
Cause: XPATH expression passed to the function is invalid.
Action: Check the xpath expression for possible syntax errors.
Cause: An attempt was made to delete the root container in the hierarchical index.
Action: Do not delete the root container.
Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name.
Action: Supply a child name and try inserting again.
Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name.
Action: Supply a child name and try deleting again.
Cause: An error occurred while generating a globally unique OID for storing an XML document.
Cause: The XMLType object pointed to by the given REF could not be deleted because either the REF was invalid or it pointed to a non-existent table.
Action: Either use FORCE deletion or supply a valid REF.
Cause: Changes were made to the structure of a directory while it was being recursively deleted.
Action: Try deleting the directory again.
Cause: The attempted operation is not allowed.
Action: See reason and change to a valid operation.
Cause: The element definition was not found.
Action: Supply the definition for the element or use a defined element.
Cause: The element was not found.
Action: Make sure the specified element exists.
Cause: The index is greater than the allowed value.
Action: Make sure the index is less than the allowed value.
Cause: An attempt was made to insert more than the allowed number of elements into an XML document node.
Action: Do not attempt to add more than the maximum number of elements to XML document nodes that maintain order.
Cause: An attempt was made to replace the data at an invalid index number in the XML document.
Action: Supply a correct occurrence number and try again.
Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.
Action: Do not insert more than maxoccurs values into the document.
Cause: An attempt was made to retrieve a resource based on a path name or resource handle that points to an entity other than a resource.
Action: Do not attempt to retrieve a resource based on that path name or resource handle.
Cause: An attempt was made to store an XML text or attribute node whose length exceeded the maximum specified by the XML schema.
Action: Shorten the data so that it conforms to its XML schema definition.
Cause: An attempt was made to bind to a resource that had not been saved to disk.
Action: Bind only to saved resources.
Cause: The resource had an invalid (dangling) REF to an XML document.
Action: Rebind the resource using a valid XMLType REF.
Cause: An attempt was made to insert non-schema-based XML data (for example, such as a comment or processing instruction) into an XML node that did not maintain ordering.
Action: In the schema, define the element with maintainOrder=true in order to add non-schema data.
Cause: An attempt was made to access an out-of-range element in an XML document node.
Action: Access data only at indexes that do not exceed the maximum value.
Cause: An attempt was made to add more than the maximum number of allowable children in an XML element.
Action: Redefine the schema to allow breaking up of the children among siblings.
Cause: An attempt was made to delete an XML element at an index that exceeds the node's total number of elements.
Action: Delete data only at valid indexes.
Cause: An attempt was made to bind an existing resource to a new location in the hierarchy, but a lock could not be obtained on the resource.
Action: Commit or roll back the transaction that has the lock on the resource.
Cause: An attempt was made to store an XML prefix without supplying the namespace to which it should be associated.
Action: Store prefixes only with their associated namespaces.
Cause: The attribute name in the XML document did not match anything in the associated schema.
Action: Supply only schema-defined or XML standard attributes.
Cause: The text in the XML document did not represent a valid value given the datatype and other constraints in the schema.
Action: Ensure that the specified value in XML documents is valid with respect to the datatype and other constraints in the schema.
Cause: The length of the disk-formatted XML namespace exceeded the maximum.
Action: Keep XML namespace declarations below the maximum length.
Cause: The XML datatype given is inconsistent with the database datatype and a conversion cannot be made.
Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas or contact Oracle Support Services.
Cause: The memory type associated with this property is mapped to an incompatible database type and a conversion cannot be made.
Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas or contact Oracle Support Services.
Cause: The type can only have the same number of properties (elements and attributes) as a table can have columns.
Action: Modify the XML schema to move properties into subelements that are not inlined.
Cause: The specified element name has not been defined at the top level of the XML schema (that is, globally). Elements must be defined globally to be the root of an XMLType object.
Action: Check the XML schema definition to make sure the specified element name has been defined at the top level.
Cause: An attempt was made to save to disk a top-level XML namespace prefix whose length exceeded the maximum.
Action: Do not define XML namespace prefixes that exceed the maximum length.
Cause: An attempt was made to store more than the maximum number of XML extras (for example, such as comments and processing instructions) either before or after the document's root node.
Action: Keep the number of extras outside the root node below the maximum.
Cause: One or more of the arguments specified in the operator in the query are incorrect.
Action: Correct the arguments specified in the operator.
Cause: An error occurred while retrieving the contents of a resource, the metadata of a resource, or both.
Action: Contact Oracle Support Services.
Cause: An attempt was made to update a resource that was never saved to disk.
Action: Perform a resource insertion instead.
Cause: The requested access privileges have not been granted to the current user. Users must be granted privileges prior to resource access.
Action: Check the set of requested access privileges to make sure that they are included in the set of access privileges granted to the user.
Cause: The requested access privileges are not supported for the specified resource.
Action: Ensure that the set of requested access privileges are valid access privileges for the specified resource.
Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources.
Action: Remove the resources that are making reference to the ACL in question and try again.
Cause: The value of the depth argument passed to the primary operator was not a positive integer.
Action: Pass a positive value in the depth argument.
Cause: An ancillary operator was used with an operator which does not support ancillary operators.
Action: Remove the ancillary operator in the query.
Cause: The element which is being inserted into the RESOURCE_VIEW is NULL.
Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW.
Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the Resource Schema.
Action: Insert an element which conforms to the Resource Schema.
Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null.
Action: Specify the Display Name and insert the element into RESOURCE_VIEW.
Cause: Read-Only XOBs cannot be modified.
Action: Use only read operations on such a XOB.
Cause: An attempt was made to insert a root node into an XML document that already had a root node.
Action: Call the appropriate replace function to replace the node instead of inserting it anew.
Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack.
Action: Look at the next error on the stack and take approprate action.
Cause: An attempt was made to delete a resource that has not been saved to disk.
Action: Delete only saved resources.
Cause: An attempt was made to modify an immutable XML node.
Action: Use only read operations on such properties.
Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree.
Action: Ensure that links to existing resources do not cause cycles.
Cause: An attempt was made to use updateXML to update an XML node with a node of another type.
Action: Ensure that the node specified by the XPath matches the type of the new data provided.
Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data.
Action: Use CREATEXML or getStringVal to coerce the new data to the proper format.
Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition.
Action: Make changes to non-typed nodes only by referencing their tag names.
Cause: An attempt was made to set an invalid user ID into an XDB resource metadata property.
Action: Verify the validity of the user ID and try again.
Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property.
Action: Verify the validity of the username or GUID and try again.
Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator.
Action: Extract the desired child from the XMLType before passing it to updateXML as the desired new XML node.
Cause: An attempt was made to access the path name of a resource that was either never saved to disk or was loaded using a method other than with its path name.
Action: Perform path name operations only on resources obtained using a path name.
Cause: The XML schema contains an invalid declaration identified by the message.
Action: Fix the identified error and try again.
Cause: The XML schema does not specify a required attribute.
Action: Specify a value for the required attribute.
Cause: The XML schema specifies an invalid attribute.
Action: Remove the specification of the invalid attribute.
Cause: There is an error in the SQL type and table specification within the XML Schema.
Action: Ensure that all specified SQL types and tables are valid and compatible with the corresponding XML types.
Cause: The identified type, attribute, or element could not be resolved.
Action: Make sure that the name corresponds to a valid XML (simple/complex) type or attribute or element and try again.
Cause: The identified attribute or element does not have a type.
Action: Make sure that every attribute and element has a valid type specification.
Cause: The XML schema does not specify the name for the global declaration of attribute, element, simpleType, or complexType.
Action: Specify names for all global declarations.
Cause: The XML schema specifies an invalid attribute.
Action: Remove the specification of the invalid attribute.
Cause: An error occurred while trying to create the SQL type based on the specification of a complex type.
Action: Fix the identified error and try again.
Cause: An error occurred while trying to create the table based on the declaration of the identified element.
Action: Fix the identified error and try again.
Cause: An attempt was made to register a schema with the same URL as a previously registered schema.
Action: Register the schema with a different URL.
Cause: An attempt was made to register a global schema without sufficient privileges.
Action: Make sure that the user has sufficient privileges to register a global schema.
Cause: An attempt was made to delete a schema resource without sufficient privileges.
Action: Make sure that the user has sufficient privileges to delete the schema.
Cause: An attempt was made to delete a schema which has dependent objects.
Action: Either drop the dependent objects prior to deleting the schema or use the CASCADE or FORCE options.
Cause: The schema document contains references (through include and import definitions) to other schemas that do not belong to valid namespaces.
Action: Make sure that all schemas referenced through include definitions target the same namespace as the parent schema. Further more, make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema.
Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema.
Action: Make sure that all database user/schema names specified in the XML schema document refer to existing database users/schemas.
Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again.
Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied.
Cause: The argument value passed for the given parameter is null or invalid.
Action: Make sure that all the input argument values are valid.
Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.
Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.
Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used.
Action: Use different names for types/tables or use the NOGEN mode so that schema compiler does not generate new types/tables.
Cause: The XML Schema could not be validated.
Action: Make sure that the SQLType and other datatype mapping is valid.
Cause: An attempt was made to rebuild the hierarchical index which is not empty.
Action: Delete all rows in the hierarchical index and then rebuild it.
Cause: An XDB Security internal error has occurred.
Action: Contact Oracle Support Services.
Cause: An XDB Locking Internal error has occurred.
Action: Contact Oracle Support Services.
Cause: Locking attempted on resource when the principal already owns a lock given by the token above.
Action: Reattempt the lock with the token.
Cause: The resource is already locked in exclusive mode. Cannot add another lock.
Action: Unlock the existing lock.
Cause: The resource is locked in shared mode. Cannot add a shared lock.
Action: Try locking in shared mode or unlocking the existing lock.
Cause: The lock may have been unlocked or it may have expired.
Action: No action required. Unlock already successful.
Cause: The lock to be unlocked is not owned by the user.
Action: Supply the lock token on parent container or unlock it.
Cause: Lock requests cause the whole request URI to be locked.
Action: Supply lock token or unlock the lock.
Cause: Delete/Rename failed because of an existing lock.
Action: Do lockdiscovery to find the lock and delete it.
Cause: Delete/Rename failed because of a lock on parent resource.
Action: Do lockdiscovery to find the lock and delete it.
Cause: Delete/Rename failed because one of the children is locked.
Action: Do lockdiscovery to find the lock and delete it.
Cause: Trigger <tabname>_xdb_pitrigger already exists.
Action: Either the table is already hierarchically enabled or the user trigger <tabname>_xdb_pitrigger needs to be dropped. Delete all rows in the hierarchical index and then rebuild it.
Cause: port number for the defined presentation is not valid.
Action: Either the port number is already in use or it is protected. Specify another port number.
Cause: An attempt was made to update the XDB configuration resource with non-schema or non-schema compliant data.
Action: Check the document to make sure it is schema based and schema compliant.
Cause: The XDB configuration resource has been deleted or corrupted.
Action: Reinstall XDB, or reinsert a valid configuration document.
Cause: An error related to XDB configuration has occurred.
Action: Make sure the configuration resource contains valid data.
Cause: The value of the operator that is specified is FALSE.
Action: Specify an operator that evaluates to TRUE.
Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE.
Action: Specify a value on the right hand side that evaluates to TRUE.
Cause: The schema definition for this type has cycles.
Action: Remove the cyclic definition and re-compile schema.
Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.
Action: Modify the prefix to a different one.
Cause: The XML document is invalid with respect to its XML Schema.
Action: Fix the errors identified and try again.
Cause: The specified attribute should be prefixed with XDB's namespace.
Action: Ensure that all XDB specified attributes are prefixed with XDB's namespace and try again.
Cause: Either one of the following is the cause:
Action: Put the resource under version-control before checking out.
Cause: Checkout is requested for a resource that is already checked out to the workspace by the same or different user.
Action: Checked in the resource from the workspace before checking out.
Cause: Checkin or uncheckout is requested for a resource that has not been checked out to the workspace by any user in a workspace.
Action: Checked in the resource from the workspace before checking out.
Cause: Container cannot be put under version-controlled.
Action: Avoid using these features.
Cause: Accessed a version-controlled resource that is already deleted.
Action: Re-create the resource.
Cause: There has been an error in the DBMS_LDAP package.
Action: Please report the error number and description to Oracle Support Services.
Cause: There is a problem either on the LDAP server or on the client.
Action: Please report this error to the LDAP server administrator or your Database administrator.
Cause: There has been an error in the DBMS_LDAP Init operation.
Action: Please check the host name and port number, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP bind operation.
Action: Please check the session handler that you use for binding, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP bind operation.
Action: Please check the authentication credentials that you used for binding, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP search operation.
Action: Please check the search scope that you use for search, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP search operation.
Action: Please check the search time value that you use for search, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP message that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP count_entry operation.
Action: Please check the LDAP count_operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP get_dn operation.
Action: Please check the LDAP get_dn, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the entry dn that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP mod_array that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.
Action: Please check the LDAP mod option that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.
Action: Please check the LDAP mod type that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP populate_mod_array operation.
Action: Please check the LDAP mod value that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP rdn value that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP rename_s operation.
Action: Please check the LDAP newparent value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP rename_s operation.
Action: Please check the LDAP deleteoldrdn value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP explode_dn or explode_rdn operation.
Action: Please check the LDAP notypes value that you use for LDAP explode_dn or explode_rdn operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP sslwrl value that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP sslpasswd value that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP sslauth value that you use for LDAP operation, or report the error number and description to Oracle Support Services.
Cause: The session executing functions from the DBMS_LDAP package is being handled by a shared server in the Database.
Action: Use dedicated database sessions to execute functions in the DBMS_LDAP package.
Cause: The specified LDAP server could not be contacted. This can happen if the server is down or inaccessible.
Action: Contact the administrator of the LDAP server.
Cause: The caller did not use the name of an existing asynchronous change source. The name given does not match the name of any existing asynchronous change source.
Action: Check the spelling of the change source name. Choose an existing change source.
Cause: An unrecognized parameter was detected.
Action: Check for too many parameters in the call.
Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column with this name already exists in the specified table.
Action: Check the names and call the procedure again.
Cause: All input parameters are null. At least one property must be altered.
Action: Call the procedure again, making sure that all the required parameters have been specified. Ensure that at least one parameter is not null. Refer to the documentation for the correct method of calling this procedure.
Cause: The change set is currently advancing. Change sources related to an advancing change set cannot be altered. Change tables related to the advancing change set cannot be created, altered, or dropped. Some or all of the parameters of the change set cannot be altered while the set is advancing.
Action: Wait until the change set has finished advancing, then reissue the command. If altering the change set, only the advance_enable parameter can be altered during an advance.
Cause: The operation cannot complete because this change source is referenced by one or more change sets.
Action: Drop the change sets first, then re-issue the command. May have to drop some change tables before the change sets are dropped.
Cause: The end data of the change set is earlier than the begin date. The end date must always be later in time than the begin date, so that the duration between the begin and end dates is a positive amount of time.
Action: Change the begin date and/or the end date, so that the end date is later than the begin date.
Cause: The begin_scn is not greater than zero. The end_scn is less than zero. The end_scn is less than the begin_scn.
Action: Check the values of both begin_scn and end_scn. Correct them to make sure that they form a legal SCN range. An end_scn value of zero indicates an infinite scn range.
Cause: One or more of the inputs to the procedure had illegal values.
Action: Identify the bad parameter(s) and supply correct values to the procedure.
Cause: Could not find an asynchronous change set by this name.
Action: Check the spelling of the change set name. Call the procedure again, passing the correct change set name.
Cause: The operation cannot be performed because the change set contains one or more change tables.
Action: You will need to drop the change table(s) first, then repeat the operation.
Cause: The specified change set is disabled. The change set needs to be enabled for the operation to succeed.
Action: Determine why the change set is disabled and correct this condition. Alter the change set specifying 'y' for advance_enable then retry the operation.
Cause: An advance operation is in progress for this change set when only one is allowed at a time.
Action: Since the change set is currently being advanced, the best action is to wait for it to finish advancing. Only one caller at a time can advance the change set. Check for the cause of long running advance operations.
Cause: One or more errors occurred during the advance operation.
Action: Check the log file(s) for a more detailed report of the underlying errors.
Cause: The specified change set does not exist or the user does not have access to the publications in that change set. The specified name did not match the name of any existing change set. Certain privileges are required to access the publications within that change set.
Action: Check the name and call the procedure again, with the name of an existing change set. Contact the publisher or database administrator if user privileges are required to access the publications in the change set.
Cause: Cannot specify a source_colmap value of 'y' for asynchronous.
Action: Specify 'n' for the source_colmap option and call the procedure again.
Cause: Reserved column name was specified in a column list or column type parameter.
Action: Control columns are selected with separate parameters. If you did not want a control column, then change the name of the specified column so that it does not conflict with a reserved column name.
Cause: Tried to create a synchronous change table and the source schema did not match any existing schema names in the database.
Action: Specify the name of an existing schema.
Cause: When creating a synchronous change table, the underlying source table must exist when the procedure is called. In this case, the source table did not exist.
Action: Specify the name of an existing table.
Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed.
Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, then contact Oracle Support Services.
Cause: The specified change table does not exist.
Action: Recheck the name and call the procedure again using an existing change table.
Cause: The value specified for the owner parameter does not contain the name of an existing schema in the database.
Action: Recheck the name and call the procedure again using an existing schema name.
Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified column does not exist in the change table.
Action: Recheck the names and call the procedure again.
Cause: The change table is subscribed to, so it cannot be dropped.
Action: Do not drop a change table while there are active subscribers. If this is an emergency, use the FORCE parameter. This will forcibly drop the change table out from under all subscribers.
Cause: The subscription handle does not exist or does not belong to this user.
Action: Call the function again with a valid subscription handle.
Cause: The subscription handle has been activated; additional calls to SUBSCRIBE are prohibited.
Action: Subscribe to all the desired tables and columns before activating the subscription. Ensure that the correct subscription handle was specified.
Cause: The subscription represented by the subscription handle already contains source_schema.source_table.
Action: Check the values of the subscription_handle, source_schema, and source_table. Do not attempt to subscribe to the same table more than once using the same subscription handle.
Cause: One or more of the specified columns cannot be found in a single publication.
Action: Change the subscription request to select only columns that are in the same publication. Consult the USER_PUBLISHED_COLUMNS view to see current publications.
Cause: The called procedure requires an activated subscription.
Action: Check the subscription handle and correct if necessary. Call the ACTIVATE_SUBSCRIPTION procedure for this subscription handle and then reissue the original command.
Cause: The change view was not dropped prior to making this call.
Action: Call the DROP_SUBSCRIBER_VIEW procedure and then retry the original command.
Cause: Not all of the source tables belong to the synchronous change set.
Action: Check the spelling of the source tables. Make sure that all of the source tables belong to the synchronous change set.
Cause: The schema_name.source_table does not exist or does not belong to this subscription.
Action: Check the spelling of the schema_name and source_table. Verify that the specified table exists in the specified schema and is subscribed to by the subscription handle.
Cause: Specified an incorrect change view or the view is already dropped.
Action: Recheck the name and specify the name of an existing change view.
Cause: Called the PURGE procedure while a purge job was currently running.
Action: Wait for purge to complete before reissuing this command.
Cause: An error occurred during the purge operation.
Action: Check the logfile for a more detailed report of the underlying errors.
Cause: A change source by the specified name already exists.
Action: Recreate the change source with a unique name.
Cause: A change set by the specified name already exists.
Action: Recreate the change set with a unique name.
Cause: A change table by the specified name already exists.
Action: Recreate the change table with a unique name.
Cause: The subscription is already active.
Action: Check name and retry.
Cause: User attempted to advance a change set which does not contain any change tables. Without change tables, a change set cannot be advanced.
Action: Create change tables in the change set, then retry the advance.
Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a table that is not a CHANGE table. This can also occur when a CHANGE table object has been orphaned. CHANGE tables can become orphaned after a CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE.
Action: Check spelling. If error was due to an incorrect name, then retry the procedure using the correct name. To drop a table that is not a CHANGE table, or an orphaned CHANGE table, use the DROP TABLE DDL command instead.
Cause: CDC attempted to acquire a lock on the resource, but the operation timed out.
Action: Retry the operation later.
Cause: CDC attempted to acquire a lock on the resource, but encountered a deadlock.
Action: Contact Oracle Support Services.
Cause: CDC attempted to acquire a lock on the resource, but encountered a problem passing parameters to the lock manager.
Action: Contact Oracle Support Services.
Cause: CDC attempted to acquire a lock on the resource, but encountered an invalid lock handle, which did not correspond to any existing handle.
Action: Contact Oracle Support Services.
Cause: Attempted to create a change table in the SYS schema. This is not allowed.
Action: Use a different, existing schema and retry the command.
Cause: The specified value is not a valid name for a Change Source.
Action: Specify a valid name and retry the command.
Cause: The specified value is not a valid name for a Change Set.
Action: Specify a valid name and retry the command.
Cause: The specified value is not a valid name for a Change Table.
Action: Specify a valid name and retry the command.
Cause: The specified value is not a valid option for a capture_values.
Action: Specify a valid option and retry the command.
Cause: The specified value is not Y or N.
Action: Specify Y or N for the parameter and retry the command.
Cause: The specified value is not Y, N, or NULL.
Action: Specify Y, N, or NULL for the parameter and retry the command.
Cause: The specified value is not ADD or DROP.
Action: Specify ADD or DROP and retry the command.
Cause: The specified column list is NULL and all optional control columns are 'N'.
Action: Specify one or more columns to ALTER.
Cause: An internal attempt to invoke a procedure within the DBMS_CDC_UTILITY package failed.
Action: Check the trace logs for more information. Ensure that the package has been installed successfully. Try issuing a DESCRIBE command from SQL on the package. If it fails, then try reinstalling the package. If it succeeds, try invoking one of the procedures from SQL.
Cause: The maximum number of characters permitted in the description field was exceeded.
Action: The maximum length of the description field is 30 characters. Ensure the length does not exceed this value and retry the command.
Cause: One or more required system triggers are not installed. These triggers are required for the proper operation of Change Data Capture. Operations on Change tables cannot continue.
Action: Install or reenable the triggers, or reinstall the package.
Cause: The directory specification for logfile location for the change source, does not correspond with an existing directory, or the directory was not accessible.
Action: Create the directory if it does not exist. If the directory does exist, change the file system permissions so the directory can be accessed. Alternatively, perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles.
Cause: The directory specification for logfile location for the change source, does not contain any files whose names pattern-match the logfile_suffix.
Action: Make sure that the logfile location contains logfiles whose names match the logfile_suffix pattern for the change set. Alternatively, perform ALTER CHANGE SOURCE and change the logfile_suffix such that it matches the names of existing logfiles in the directory.
Cause: An unexpected internal error occurred while CDC was accessing its internal Metadata.
Action: Contact Oracle Support Services.
Cause: The directory specification for logfile location for the change source, is an empty directory.
Action: Make sure it is the correct location of the logfiles. If it is, make sure the directory contains logfiles. Alternatively, perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles.
Cause: User tried to drop a change table but its underlying storage table (that contains the change data) has been dropped.
Action: Contact Oracle Support Services.
Cause: A timeout occurred while trying to place a lock on the subscription handle. Another session has already aquired the lock on the subscription handle.
Action: Ensure the subscription handle is correct and correct it if necessary. If it was correct, retry the operation after the session holding the lock has released it.
Cause: Did not find any publications that matched the input parameters or the user does not have the privileges to access the specified publication.
Action: Check the input parameters on the call to SUBSCRIBE. Validate that the proposed source table has been published by checking the USER_PUBLICATIONS view for that source table. Contact the publisher if user privileges are required to access the publication. Retry the command with correct security or publication information.
Cause: The OBJECT_ID flag was set to 'Y' on the call to CREATE_CHANGE_TABLE and change table belongs to the synchronous change set. The corresponding object column was not detected in the source table.
Action: Create the change table with the OBJECT_ID flag set to 'N' or investigate why the object column is not in the source table and add it to the source table.
Cause: If creating an asynchronous change table, the RSID was set to 'N'. If altering an asynchronous change table with an operation parameter of 'DROP' RSID was set to 'Y'.
Action: When creating asynchronous change tables, always specify 'Y' for the RSID parameter. When altering asynchronous change tables, always specify 'N' for RSID.
Cause: Cannot specify an object_id value of 'y' for asynchronous change tables.
Action: Specify 'n' for the object_id option and call the procedure again.
Cause: An attempt was made to Import a file that was exported by a newer version of Oracle than the target instance.
Action: If possible, re-export the file using a version of export that matches the import target. Objects can not be imported into previous versions of Oracle that did not support them.
Cause: While advancing a change set, a CDC attempted to query the LogMiner dictionary system tables to obtain the columns from the source table. The query returned no rows. This may be because none of the redo logs contains a catalog, or it may be an internal error.
Action: First, verify that the source system contains the source table. execute dbms_logmnr_d.build procedure to populate the redos log with logminer dictionary information. If this has been done and the problem persists, then contact Oracle Support Services.
Cause: While advancing a change set, a CDC determined that at least one of the data columns in a change table does not match the name of any of the columns in the source table. The source table column list is stored in dictionary table SYSTEM.LOGMNR_OBJ$.
Action: Make sure that all of the data columns of the change table have the same names as the corresponding columns in the source table, and that all the columns exist in the source table.
Cause: There was an error originating from this synchronous change table. One possible cause is that schema redefinition has occurred on the source table and one or more columns in the change table are now a different type than the corresponding source columns. Another possible cause is that there is a problem accessing the synchronous change table.
Action: Check further error messages in the stack for more detail about the cause. If there has been schema redefinition, drop and recreate the synchronous change table.
Cause: An attempt was made to use the SQL command DROP TABLE for change tables, but DROP TABLE is not supported for change tables.
Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead of the DROP TABLE command.
Cause: A NULL or invalid value was supplied for the parameter.
Action: Correct the input value and try the call again.
Cause: The function was called after the first call to FETCH_xxx.
Action: Correct the program.
Cause: The parameter value is inconsistent with another value specified by the program. It may be inconsistent with the object type associated with the OPEN context, or it may be of the wrong datatype (a boolean rather than a text string or vice versa).
Action: Correct the program.
Cause: The specified object was not found in the database.
Action: Correct the object specification and try the call again.
Cause: The specified parameter value is not valid for this object type.
Action: Correct the parameter and try the call again.
Cause: An LPX routine (XML/XSL processing) returned an internal error number to its PL/SQL wrapper routine in facility KUX which provides the implementation for package UTL_XML.
Action: Look up the LPX error number and follow its corrective action.
Cause: A method in package UTL_XML was called with an invalid XML context handle. All handles must have previously been allocated by UTL_XML.XMLINIT.
Action: Always call XMLINIT before any other methods in pkg. UTL_XML.
Cause: Either FETCH_XML was called when the "DDL" transform was specified or FETCH_DDL was called when the "DDL" transform was omitted.
Action: Correct the program.
Cause: The specified object was not found in the database.
Action: Correct the object specification and try the call again.
Cause: The installation script initmeta.sql failed to load the named file from the file system directory into the database.
Action: Examine the directory and see if the file is present and can be read.
Cause: An alter system command or an internal self tuning mechanism requested a write to the SPFILE but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE.
Cause: A create spfile command is trying to write to an SPFILE that was used to startup the instance.
Action: Specify a different SPFILE name.
Cause: One or more obsolete parameters were specified in the SPFILE or the PFILE on the server side.
Action: See alert log for a list of parameters that are obsolete or deprecated. Remove them from the SPFILE or the server side PFILE.
Cause: The value specified for an alter operation on a size parameter is not valid.
Action: Correct the value and retry the operation.
Cause: A deprecated parameter was specified at startup.
Action: Consult Oracle documentation to find new parameters to use instead.
Cause: An error occurred while processing a parameter on a remote instance.
Action: See accompanying error messages.
Cause: Memory resets of local parameters are only allowed.
Action: Retry the query for the local instance if needed.
Cause: The SPFILE did not contain the sid.parameter entry.
Action: Change the sid and/or the parameter.
Cause: A restore operation trying to write to an SPFILE that was used to startup the instance.
Action: Specify a different SPFILE name.
Cause: Failure during processing of parameters from restored SPFILE.
Action: Further diagnostic information should be in the error stack.
Cause: Failure during processing of parameters from restored SPFILE. It could be that the restored image of the SPFILE is corrupted.
Action: Further diagnostic information should be in the error stack.
Cause: Failure during processing of parameters from restored SPFILE. It could be that the restored image of the SPFILE is corrupted.
Action: Further diagnostic information should be in the error stack.
Cause: Failure during SPFILE restore. It could be that the restore destination is not valid.
Action: Further diagnostic information should be in the error stack.
Cause: The database is mounted.
Action: Unmount the database to update the parameter in the SPFILE.
Cause: A failure occurred while updating the SPFILE.
Action: See associated errors.
Cause: Forward or recursive reference of a query name in WITH clause is not allowed.
Action: Correct the query statement and retry.
Cause: Too many queries using temp table transformation are currently being run to use up all temporay object numbers.
Action: Turn off temporary table transformation or wait, then retry.
Cause: Column aliasing in WITH clause is not supported.
Action: Specify aliasing in definition subquery and retry.
Cause: Improper use of WITH clause due to one of the following:
Action: correct the query and retry.
Cause: There is at least one WITH clause query name that is not referenced in any place.
Action: remove the unreferenced query name and retry.
Cause: There is at least one query name which is inlined more than once because its definition query is too simple and references another query name. This is not currently supported.
Action: remove such a query name and retry.
Cause: An attempt was made to use LEVEL in membership condition with subquery that is not supported.
Action: Rewrite query to avoid using LEVEL in membership condition.
Cause: A mapping operation failed.
Action: Check FMON trace files for errors.
Cause: The mapping service was never started or previously failed to start properly.
Action: Set FILE_MAPPING to true if it is not currently set. Otherwise, check FMON trace files for an ORA-32052 error.
Cause: The mapping service failed to start properly.
Action: Check FMON trace files for errors.
Cause: Mapping libraries do not support this operation.
Action: Check whether mapping libraries are available and whether the operation is supported by the libraries.
Cause: Lost communication with mapping utility.
Action: Check FMON and FMPUTL trace files for errors.
Cause: Invalid file type used when mapping files.
Action: Specify one of the expected file types.
Cause: Invalid number of extents were used for a map operation.
Action: Specify a non-negative number of extents.
Cause: An invalid mode was used for a lock operation.
Action: Specify one of the expected lock modes.
Cause: This operation requires SYSDBA priviliges.
Action: Connect to the database as a user with SYSDBA privileges.
Cause: Mapping structures are already locked by the same session.
Action: Unlock mapping structures before proceeding with the current operation.
Cause: Channel failure between foreground and background process.
Action: Check foreground trace files for errors.
Cause: Trying to perform an operation on transient object which is valid only on persistent objects.
Action: Make sure object is persistent.
Cause: An OCI Environment could not be created for OCCI.
Action: Ensure that the parameters to the creatEnvironment method are valid.
Cause: An invalid Connection was passed to the Session::migrate method.
Action: Pass a valid Connection to the migrate method.
Cause: The setBuffer method was not called for all column positions and the next method was called to fetch more than one row.
Action: Call the setBuffer method for all column positions if next is to be called to fetch more than one row.
Cause: Memory could not be allocated from an OCI heap.
Action: Increase the process memory size.
Cause: The max column or parameter size is not specified.
Action: Specify the max size by setMaxColumnSize or setMaxParamSize.
Cause: An invalid column or parameter position was specified.
Action: Specify a valid column or position number.
Cause: A null connection was passed.
Action: Pass a valid, non-null connection.
Cause: The number of elements in the vector passed to the setVector method was not equal to the size of the VARRAY.
Action: Pass a vector of size equal to the size of the VARRAY.
Cause: An attribute was fetched after a call to wasLastAttrNull().
Action: Fetch an attribute value before making this call.
Cause: A Null object was passed.
Action: Pass a non-null object.
Cause: The LOB instance on which the operation was attempted was null.
Action: Use a valid, non-null LOB instance to perform this operation.
Cause: Neither of the LOBs being compared had associated connection information.
Action: At least one of the LOBs being compared must be associated with a valid connection.
Cause: The buffer size specified for the LOB read or write operation was less than the amount to be read or written.
Action: The buffer size must be equal to or greater than than the amount to be read from or written to the LOB.
Cause: The source LOB instance on which the operation was attempted was null.
Action: Use a valid, non-null source LOB instance for this operation.
Cause: The FILE instance on which the operation was attempted was null.
Action: Use a valid, non-null FILE instance to perform this operation.
Cause: Neither of the FILEs being compared had associated connection information.
Action: At least one of the FILEs being compared must be associated with a valid connection.
Cause: The buffer size specified for the FILE read or write operation was less than the amount to be read or written.
Action: The buffer size must be equal to or greater than than the amount to be read from or written to the FILE.
Cause: The source FILE instance on which the operation was attempted was null.
Action: Use a valid, non-null source FILE instance for this operation.
Cause: An attempt was made to get metadata for a terminated statement.
Action: No action required.
Cause: The attribute number passed is greater than the total number of attributes of the described object.
Action: Pass the attribute number within the allowable range.
Cause: The attribute passed is not applicable for the described object.
Action: Pass a valid attribute.
Cause: The return type of the get method does not match the type of the attribute being passed.
Action: Call the appropriate get method.
Cause: The REF instance on which the operation was attempted was null.
Action: Use a valid, non-null REF instance to perform this operation.
Cause: Neither of the REFs being compared had associated connection information.
Action: At least one of the REFs being compared must be associated with a valid connection.
Cause: Fetch from result set has already started and the setDataBuffer call was made.
Action: Call the setDataBuffer method before calling the next() method.
Cause: The setDataBuffer method was called to get information about this column. Therefore, the current method cannot be called.
Action: Use the information from the buffers specified in the setDataBuffer call.
Cause: The offset/index is out of range of valid data locations in Bytes offsets.
Action: Ensure that offsets or index is within the range of Bytes object.
Cause: The setXXX method is called again with a different data type than originally specified, or the setXXX method is called for a subsequent iteration without being called before the first iteration.
Action: Call the setXXX method with the same data type as done before the first iteration. If no setXXX method was called for this parameter, position the first iteration and make sure that a setXXX method is called before the first addIteration method is called.
Cause: The setMaxIterations was called after a setXXX method has been called.
Action: Call the setMaxIterations method before calling any setXXX methods.
Cause: An open stream exists on the LOB/FILE on which the operation was attempted.
Action: Close the stream before getting another.
Cause: An open stream exists on the target LOB.
Action: Close the stream on the target LOB before assigning the LOBs.
Cause: An open stream exists on the target FILE.
Action: Close the stream on the target FILE before assigning the FILEs.
Cause: The LOB/FILE from which the stream was obtained had been nullified or destroyed.
Action: Use a valid stream.
Cause: The readBuffer() or the writeBuffer() method was called on a UTF16 character set stream.
Action: Use the readUBuffer() or the writeUBuffer() method.
Cause: The readUBuffer() or the writeUBuffer() method was called on a non-UTF16 character set stream.
Action: Use the readBuffer() or the writeBuffer() method.
Cause: A write was performed after the last buffer was written.
Action: Close this stream and get a new stream to perform the write.
Cause: Either a read is attempted from a stream in write mode, or a write is attempted on a stream in read mode.
Action: Check the status of the stream to find out the valid operations that can be performed.
Cause: The getXXX method called on the Statement object does not match the type of the bind parameter.
Action: Call the getXXX method that is the same as the type of the parameter.
Cause: The addIteration exceeds the maximum number of iterations set by the setMaxIterations method.
Action: Increase the maximum number of allowed iterations.
Cause: A null environment was passed.
Action: Pass a valid, non-null environment.
Cause: The interval involved in this operation is null.
Action: Use a valid, non-null interval instance to perform this operation.
Cause: The interval on which the operation was attempted was null and no environment was specified.
Action: Specify a non-null environment or perform the operation on a non null instance.
Cause: The date involved in this operation is null.
Action: Use a valid, non-null date instance to perform this operation.
Cause: The date on which the operation was attempted was null and no environment was specified.
Action: Specify a non-null environment or perform the operation on a non null instance.
Cause: The time involved in this operation is null.
Action: Use a valid, non-null time instance to perform this operation.
Cause: The time on which the operation was attempted was null and no environment was specified.
Action: Specify a non-null environment or perform the operation on a non null instance.
Cause: The timestamp involved in this operation is null.
Action: Use a valid, non-null timestamp instance to perform this operation.
Cause: The timestamp on which the operation was attempted was null and no environment was specified.
Action: Specify a non-null environment or perform the operation on a non null instance.
Cause: The number involved in this operation was null.
Action: Use a valid, non-null number instance to perform this operation.
Cause: The number on which the operation was attempted was null and no environment was specified.
Action: Specify a non-null environment or perform the operation on a non null instance.
Cause: A null anydata context was passed.
Action: Pass a valid, non-null anydata context.
Cause: A null anydata was passed.
Action: Pass a valid, non-null anydata.
Cause: This operation is not applicable to streams obtained from LOBs.
Cause: An inapplicable type was passed to this call.
Action: Pass an applicable type.
Cause: A null Type name was passed.
Action: Pass an non-null Type name.
Cause: A zero or negative value was passed.
Action: Pass a positive value.
Cause: Zero amount was passed and buffer size was less than LOB size.
Action: Specify a larger buffer or use Stream.
Cause: readSQL/writeSQL method was NULL or was not registered.
Action: Register readSQL/writeSQL by calling put method in Map.
Cause: An attempt was made to drop a materialized view of a nested table column's storage table.
Action: Drop the materialized view that contains the nested table column. This will implicitly drop all materialized views.
Cause: An attempt was made to create an object-relational materialized view that is not primary key based.
Action: Create the materialized view with the PRIMARY KEY keyword.
Cause: An attempt was made to create an object materialized view that is not object ID based.
Action: Create the materialized view using the OF clause but omit any ROWID or PRIMARY KEY clauses.
Cause: For materialized views with user-defined types, the definition query cannot reference tables from different master sites.
Action: Do not create materialized views with user-defined types referencing multiple master sites.
Cause: An attempt was made to create a materialized view with the ON PREBUILT TABLE option.
Action: Do not create the materialized view with the ON PREBUILT TABLE option.
Cause: An attempt was made to create a RepAPI materialized view with user-defined types.
Action: Do not create a RepAPI materialized view with user-defined types.
Cause: An attempt was made to create an updatable materialized view with user-defined types where the definition query did not use SELECT * at the topmost level.
Action: Rewrite the definition query so that SELECT * is used at the topmost level.
Cause: An attempt was made to create a materialized view whose definition query references object tables without the FROM ONLY clause.
Action: Rewrite the definition query to use the FROM ONLY clause for all the object tables in the query.
Cause: An attempt was made to create an object materialized view where the definition query did not use SELECT * at the topmost level.
Action: Rewrite the definition query so that SELECT * is used at the topmost level.
Cause: An attempt was made to create an object materialized view whose type does not match the type of the master object table.
Action: Redefine the type so that it matches the type of the master object table.
Cause: An attempt was made to create an object materialized view whose definition query did not select from an object table.
Action: Rewrite the definition query to select from an object table.
Cause: An attempt was made in the definition query to select an embedded user-defined type function, returning a user-defined type, or a function whose arguments are user-defined types.
Action: Rewrite the definition query to exclude these unsupported user-defined types.
Cause: An attempt was made to refresh a materialized view of a nested table column's storage table.
Action: Refresh the materialized view that contains the nested table column. This will implicitly refresh all secondary materialized views.
Cause: A Partition Maintenance Operation (PMOP) has been performed on a detail table, and the specified materialized view does not support fast refersh after PMOPs.
Action: Use REFRESH COMPLETE. You can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Cause: One or more deletions or updates has been performed on one or more of the detail tables referenced by the specified materialized view. This materialized view does not support fast refresh after deletions or updates.
Action: Use REFRESH COMPLETE. You can determine why your materialized view does not support fast refresh after deletions or updates using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletions or updates and direct path insert.
Action: Use REFRESH COMPLETE. You can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option.
Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletions or updates have been performed on multiple detail tables.
Action: Use REFRESH COMPLETE. You can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option.
Cause: An attempt was made to execute a job from within another job.
Action: Do not submit jobs that run other jobs.
Cause: Renaming a materialized view or its base table is not supported.
Action: Do not rename the base table of a materialized view.
Cause: The direct loader log might have been dropped.
Action: Need to perform a complete refresh.
Cause: A Partition Maintenance Operation (PMOP) has been performed on the materialized view, and no materialized view supports fast refersh after container table PMOPs.
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Cause: A detail table has been truncated and no materialized view supports fast refersh after a detail table has been truncated.
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after TRUNCATE using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Cause: An invalid operation was performed on an interim table which was being used for online redefinition of a table.
Action: Do not perform any unsupported operation on the interim table.
Cause: A type used by the materialized view was found to be incompatible with it's coressponding type on the master site. This could be because the type does not exist on the master site or has been evolved to a different version from that on the materialized view site.
Action: Make sure that the types used by the materialized view are the same on both the materialized view and master sites.
Cause: The types used by the materialized view or its master tables have been evolved.
Action: Ensure that the types used by the materialized view have been evolved to the same version at both the master and materialized sites. Before refreshing the materialized view, evolve the materialized view using ALTER MATERIALIZED VIEW.
Cause: An event is set for disabling table scn update to prevent deadlock situation.
Action: Disable null refresh and/or base table scn update for Materialized view.
Cause: The table on which the materialized view is created as prebuilt is already referenced by a materialized view.
Action: Create the materialized view on a different table.
Cause: A level-less dimension is not allowed.
Action: Do not drop the only level of a dimension.
Cause: The USING NO INDEX option was specified to create an updatable primary key based materialized view, an index-organized materialized view, or an object-id materialized view.
Action: Do not use the USING NO INDEX option to create an updatable primary key based materialized view, an index-organized materialized view, or an object-id materialized view.
Cause: There are some pending changes in the detail tables.
Action: Execute an on-demand refresh on the materialized view to synchronize the data between the materialized view and the detail tables and then issue an ALTER MATERIALIZED VIEW statement.
Cause: The materialized view log either does not have object id columns logged, or the timestamp associated with the object id columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add object id columns to the materialized view log, if required.
Cause: The materialized view log on the indicated table does not have new values information.
Action: Add new values to the materialized view log using the ALTER MATERIALIZED VIEW LOG command.
Cause: The materialized view log either does not have new values logged, or the timestamp associated with the new values columns is more recent than the last refresh time.
Action: Perform a complete refresh is required before the next fast refresh.
Cause: A snapshot log that utilizes Change Data Capture is being imported to a database where Change Data Capture has not been enabled.
Action: First enable Change Data Capture on the database then retry the import.
Cause: Path name too long.
Action: Use shorter pathname than maximum specified for dirname.
Cause: Underlying OSDs encountered an error.
Action: Check additional information. slercerrno contains errno.
Cause: This command can only be issued after a flash freeze.
Action: Refer to instructions for flash freeze and Oracle diagnostics.
Cause: Underlying OSDs encountered an error.
Action: Check additional information. slercerrno contains errno.
Cause: An illegal value was specified for create watchpoint mode.
Action: Specify one of the expected modes.
Cause: Too many watchpoints created.
Action: Increase appropriate initialization parameters.
Cause: Invalid arguments were provided.
Action: Provide one of the expected arguments.
Cause: Invalid arguments to the command were provided.
Action: Provide one of the expected arguments.
Cause: Invalid watchpoint ID.
Action: Use oradebug show to list valid watchpoint IDs.
Cause: An attempt was made to delete an already deleted watchpoint.
Action: Use oradebug show to list valid watchpoint IDs.
Cause: An attempt was made to create a watchpoint on an invalid address.
Action: Provide a different valid address.
Cause: Overlap exists between requested memory range to watch and internal memory structures that watchpointing operations need.
Action: Provide a different address range.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Default keyword was used to modify views.
Action: Use implicit default - omitting column-value pair.
Cause: keyword TYPE is missing.
Action: Use TYPE keyword.
Cause: A user name of SYS or SYSTEM was not specified when providing a password in the CREATE DATABASE statement.
Action: Only passwords for the SYS and SYSTEM users can be provided in the CREATE DATABASE statement. Re-issue the statement with passwords for users SYS or SYSTEM.
Cause: A password for the SYS user was specified twice in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with only one password for the SYS user.
Cause: A password for the SYSTEM user was specified twice in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with only one password for the SYSTEM user.
Cause: Passwords for both the SYS and SYSTEM users were not provided in the CREATE DATABASE statement. If one of the passwords was provided, then both should be provided.
Action: Re-issue the CREATE DATABASE statement with a password for both the SYS and SYSTEM users.
Cause: An incorrect password was provided for the SYS or SYSTEM users in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with a valid password.
Cause: A table function T2 contains a reference to a table T1. Table function T2 is also left outer-joined to T1. This is not allowed.
Action: Remove the reference to T1 from T2 or remove the left outer-join specification.
Cause: cannot use both RETENTION and PCTVERSION together.
Action: Use either RETENTION or PCTVERSION.
Cause: cannot give a value for Retention Period.
Action: do not provide the value for parameter.
Cause: cannot use both FREEPOOLS and FREELIST GROUPS together.
Action: Use either FREEPOOLS or FREELIST GROUPS.
Cause: The specified FREEPOOLS LOB storage option value must be an integer.
Action: Choose an appropriate integer value and retry the operation.
Cause: Keyword FREEPOOLS expected after the REBUILD keyword.
Action: User must specify FREEPOOLS keyword.
Cause: Cannot rebuild freepools while creating table with lob column.
Action: User must not specify REBUILD ... in this context.
Cause: An unexpected error occurred while performing a DIAG Group Service operation.
Action: Verify that the DIAG process is still active. Also, check the Oracle DIAG trace files for errors.
Cause: DIAG is not registered with DIAG Group Service.
Action: Issue the command without the cluster database syntax.
Cause: Another session for Parallel Oradebug is in progress with the database.
Action: Issue the command later when the current session has finished.
Cause: Group reconfiguration is occurring among DIAGs.
Action: Issue the command later when group reconfiguration completes.
Cause: Error is encountered during executing command at local node.
Action: Check alert log and DIAG trace file for error detail.
Cause: IPC communication problem encountered.
Action: Check IPC communication between DIAGs and issue the command again at a later time.
Cause: DIAG process is not alive.
Action: Check error in DIAG trace file and issue the command again when DIAG is restarted.
Cause: DIAG received wrong message.
Action: Check DIAG trace files for errors.
Cause: DIAG couldn't allocate buffer for remote copy.
Action: Check DIAG trace files for errors.
Cause: DIAG couldn't copy buffer to remote node.
Action: Check DIAG trace files for errors.
Cause: DIAG couldn't re-grow the heap for wait-for-graphs.
Action: Check DIAG trace files for errors.
Cause: The current varchar behavior is different. That is, instr('abcd', 'cd', -2, 1) returns 3, whereas instr(to_clob('abcd'), 'cd', -2, 1) returns 0, (for example, no match), because the reverse search starts from offset -2, which points to 'c' and moving backward, 'd' is ignored. This is symmetric to instr('dcba','dc',2,1), which returns 0.
Action: ORACLE uses the same varchar semantics on LOBs (instr). Using the same example, instr(to_clob('abcd'), 'cd', -2, 1) will return 3 as in the varchar case.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|