Skip Headers
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
13
ORA-24280 to ORA-29249
-
Cause: The parameter has been provided a negative, out of range, or NULL input value.
-
Action: Correct the input value such that it is valid, and is within the range as specified in the documentation.
-
Cause: The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes.
-
Action: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and/or offset increments.
-
Cause: An undefined mode value was specified.
-
Action: Check that the correct mode is selected and that an allowed value for that mode is specified.
-
Cause: An HDA was not specified in the logon call while running in a thread safe environment.
-
Action: Make sure that HDA is not NULL when calling the logon routine.
-
Cause: An attempt was made to use the host connection while it was in use by another thread.
-
Action: Wait for another thread to finish before using this connection.
-
Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.
-
Action: Use this call in deferred mode of linkage.
-
Cause: Data of this datatype cannot be sent or fetched in pieces.
-
Action: Use other bind or define calls for this datatype.
-
Cause: The call was executed on a cursor for which this is invalid.
-
Action: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor.
-
Cause: A zero length buffer or a null buffer pointer was provided.
-
Action: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.
-
Cause: The length of the piece exceeded the maximum possible size.
-
Action: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application.
-
Cause: Call to modify attributes was done for a non-existent position.
-
Action: Verify that a define has been done for this position.
-
Cause: This server handle is already attached to a server.
-
Action: Disconnect from the server and then retry the call to establish a connection.
-
Cause: The connect string is null, but a length was specified for it.
-
Action: Set length to zero if connect string is null.
-
Cause: Cannot initialize user memory.
-
Action: Contact Oracle Support Services.
-
Cause: An illegal size or null pointer was specified for user memory.
-
Action: Specify a legal size and a valid pointer for user memory.
-
Cause: A user has already been authenticated on this service handle.
-
Action: Terminate the service context before using it for another user.
-
Cause: The server context does not done exist.
-
Action: Establish the server context in the service context.
-
Cause: An illegal attribute type was specified for the handle.
-
Action: Consult the Oracle Call Interface Programmer's Guide to specify an attribute valid for this handle.
-
Cause: An illegal handle type was specified.
-
Action: Consult the Oracle Call Interface Programmer's Guide to specify a valid handle type.
-
Cause: A define was done with an existing handle on a different position.
-
Action: Specify the same position as before on a redefine.
-
Cause: This call is valid only for object types.
-
Action: Verify that the data-type for this variable is an object type.
-
Cause: Process was unable to allocate memory to store diagnostics.
-
Action: Terminate other processes in order to reclaim needed memory.
-
Cause: An attempt to initialize a MUTEX failed.
-
Action: Contact Oracle Support Services.
-
Cause: One of the three memory function pointers is null or non-null.
-
Action: Verify that either all the memory functions are null or non-null.
-
Cause: An attempt to delete an initialized MUTEX failed.
-
Action: Contact Oracle Support Services.
-
Cause: A null or invalid value was passed in for a mandatory parameter.
-
Action: Verify that all mandatory parameters are properly initialized.
-
Cause: An attempt was made to use an improper service context handle.
-
Action: Verify that the service context handle has all the parameters initialized prior to this call.
-
Cause: An attempt was made to use a context handle outside its scope.
-
Action: Verify that the context handle is set to a service context handle that has been converted to a logon data area for other OCI calls. The logon data area must be converted back to a service context before it can be used.
-
Cause: An attempt was made to pass an initialized handle.
-
Action: Verify that the parameter passed in to retrieve a handle does not already point to a handle.
-
Cause: A server context must be initialized before creating a session.
-
Action: Create and initialize a server handle.
-
Cause: The attribute value passed in is illegal.
-
Action: Consult the Oracle Call Interface Programmer's Guide and specify a legal attribute value for the handle.
-
Cause: The character set identifier specified is invalid.
-
Action: Specify a valid character set identifier in the OCI call.
-
Cause: An internal OCI error has occurred.
-
Action: Contact Oracle Support Services.
-
Cause: The user buffer to contain the output data is too small.
-
Action: Specify a bigger buffer.
-
Cause: An invalid object type is requested for the describe call.
-
Action: Specify a valid object type to the describe call.
-
Cause: An iteration count of zero was specified for the statement.
-
Action: Specify the number of times this statement must be executed.
-
Cause: The application is trying to get a descriptor from a handle for an illegal position.
-
Action: Check the position number.
-
Cause: The number of columns exceeds the maximum number supported.
-
Action: Specify a number of columns less than 1000.
-
Cause: The result set descriptor should have valid data fetched into it before it can be converted to a statement handle.
-
Action: Fetch valid data into the descriptor before attempting to convert it into a statement handle.
-
Cause: A statement cannot be executed before making preparing a request.
-
Action: Prepare a statement before attempting to execute it.
-
Cause: A fetch or describe was attempted before executing a statement handle.
-
Action: Execute a statement and then fetch or describe the data.
-
Cause: An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore.
-
Action: Attach to the server after setting the server group name in the server handle.
-
Cause: The number of columns exceeds maximum supported by the server.
-
Action: Limit your operation to 255 columns.
-
Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
-
Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been specified at process initialization.
-
Cause: An attempt to destroy a MUTEX failed.
-
Action: Contact Oracle Support Services.
-
Cause: The only valid return value for a user defined callback function is OCI_CONTINUE. Any other value will cause this error.
-
Action: Make sure that OCI_CONTINUE is returned from the user-defined callback function.
-
Cause: A SQL or PL/SQL compilation error occurred.
-
Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
-
Cause: A truncation or a null fetch error.
-
Action: Make sure that the buffer size is long enough to store the returned data.
-
Cause: None of the bind variables in the SQL statement are bound.
-
Action: Bind all the variables before the execute is done.
-
Cause: A null column was processed by an aggregate function.
-
Action: An OCI_SUCCESS_WITH_INFO is returned.
-
Cause: An UPDATE or DELETE was executed without a WHERE clause.
-
Action: An OCI_SUCCESS_WITH_INFO is returned.
-
Cause: OCI used is not permitted from external procedures.
-
Action: Refer to the Oracle Call Interface Programmer's Guide for usage restrictions.
-
Cause: A bad date was passed into one of the OCI calls.
-
Action: Check your date bind values and correct them.
-
Cause: A bad COBOL display type was passed into one of the OCI calls.
-
Action: Check your COBOL display type bind values and correct them.
-
Cause: User supplied buffer for a COBOL display type was too small to accommodate fetched number.
-
Action: Increase the allocation for COBOL display type buffer.
-
Cause: The number fetched was beyond the range that can be displayed.
-
Action: Check the number in the database.
-
Cause: An attempt was made to convert a negative number into an unsigned display type.
-
Action: Check the number in the database or change the defined datatype.
-
Cause: An internal error was encountered during conversion to COBOL display type.
-
Action: Contact Oracle Support Services.
-
Cause: An internal error was encountered during conversion to OCIDate type.
-
Action: Contact Oracle Support Services.
-
Cause: OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
-
Action: Invoke the OCIBindObject call for all Object Types and References.
-
Cause: OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
-
Action: Invoke the OCIDefineObject call for all Object Types and References.
-
Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines.
-
Action: Invoke the OCIBindObject() or OCIDefineObject() call with a valid Type Descriptor Object.
-
Cause: One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call.
-
Action: Invoke the advanced bind call on this bind handle only after performing a basic bind call.
-
Cause: When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value.
-
Action: Use a non-zero value for the maximum size of the buffer in the server.
-
Cause: Measurements in characters instead of bytes are illegal if either the server's or client's character set is varying width.
-
Action: If either the client's or server's character set is varying width then do not use the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use OCI_ATTR_MAXDATA_SIZE instead.
-
Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally.
-
Action: Contact Oracle Support Services.
-
Cause: This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character.
-
Action: Make sure that all multibyte character data is properly terminated.
-
Cause: This occurs during user authentication, a migratable user handle has been set in the service handle.
-
Action: Service handle must not be set with migratable user handle when it is used to authenticate another user.
-
Cause: This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle.
-
Action: Service handle must be set with non-migratable user handle when it is used to authenticate a migratable user.
-
Cause: This is an internal OCI error.
-
Action: Contact Oracle Support Services.
-
Cause: No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause.
-
Action: The bind handles which are to receive data in a DML statement with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic.
-
Cause: Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces.
-
Action: Always set the piece value to OCI_ONE_PIECE for datatypes that does not support piecewise operation.
-
Cause: An internal OCI error has occurred.
-
Action: Contact Oracle Support Services.
-
Cause: The object to be described is not valid. It either has compilation or authorization errors.
-
Action: The object to be described must be valid.
-
Cause: The length specified for the statement is either 0 or too large.
-
Action: Specify a valid length for the statement.
-
Cause: The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call.
-
Action: Issue OCI define calls for the columns to be fetched.
-
Cause: V6 syntax is no longer supported in V8 server.
-
Action: Change syntax to V7 syntax or higher.
-
Cause: A user callback registration or get was attempted on a handle which is not an environment handle.
-
Action: Pass the environment handle to register/get user callback.
-
Cause: An invalid function code was used to register or get user callback.
-
Action: Use a valid OCI function code.
-
Cause: An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks.
-
Action: Do not register user callback for this OCI call.
-
Cause: An invalid type of user callback was specified.
-
Action: Specify a valid user callback type.
-
Cause: The mode parameter in an OCIU* call is invalid.
-
Action: Use only a valid mode parameter.
-
Cause: One or more rows failed in the DML.
-
Action: Refer to the error stack in the error handle.
-
Cause: The statement handle was executed or described successfully before.
-
Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
-
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.
-
Action: Use OCIDescribeAny to describe only documented objects.
-
Cause: The size of the application context must be initialized before populating each context element.
-
Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size.
-
Cause: The size or index of the application context must be non-zero and non-negative.
-
Action: Use an appropriate value for the size.
-
Cause: This is an internal OCI error.
-
Action: The user should reset in-use flag in statement handle before freeing the handle.
-
Cause: Trying to attach using the wrong driver.
-
Action: Relink the application in the correct mode.
-
Cause: Feature not supported in fast path mode.
-
Action: Avoid using the functionality in this mode.
-
Cause: All the requested rows in this fetch could not be received.
-
Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION, and the number of rows in the OCIStmtFetch2 call. If required, change some of the above parameters and fetch again.
-
Cause: The scrollable cursor execute or fetch has failed.
-
Action: Check the documentation for supported types, and other restrictions while using scrollable cursors.
-
Cause: Scrollable cursor operation requested with non-scrollable cursor.
-
Action: Check if the statement was executed in the scrollable mode. The only acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter.
-
Cause: OCIServerAttach was called in OCI_POOL mode but no connection pool was found to associate the server handle.
-
Action: 1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link.
-
Cause: The mode specified in OCIConnectionPoolCreate is invalid.
-
Action: Use a valid mode.
-
Cause: The mode specified in OCIConnectionPoolDestroy is invalid.
-
Action: Use a valid mode.
-
Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
-
Action: Create a connection pool prior to reinitializing it.
-
Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode.
-
Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server handle while attaching in OCI_POOL mode.
-
Cause: An internal error occurred while trying to free connections.
-
Action: Contact Oracle Support Services.
-
Cause: A connection pool has already been created for the specified pool handle.
-
Action: 1) Specify a different pool handle to create a new connection pool. 2) If you wish to modify the pool parameters, call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode.
-
Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call.
-
Action: Specify a valid combination of parameters.
-
Cause: The database link specified in OCIConnectionPoolCreate might be invalid.
-
Action: Specify a valid database link.
-
Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached.
-
Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and increase the value of the connMax parameter.
-
Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.
-
Action: Specify a valid username and password.
-
Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made.
-
Action: Ensure no connections from the pool are being used.
-
Cause: An attempt was made to use the connection pool before it was created.
-
Action: Create the connection pool.
-
Cause: An internal error occurred while creating connections in the pool.
-
Action: Contact Oracle Support Services.
-
Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.
-
Action: The user should perform the API mode switch either prior to initiating the top call or after the main call has completed.
-
Cause: A connection pool has already been created for the specified pool name.
-
Action: Specify a different pool name to create a new connection pool.
-
Cause: An internal error occurred while generating unique server group name.
-
Action: Contact Oracle Support Services.
-
Cause: The client cannot process all the new features in the object.
-
Action: Upgrade the client so that features like inheritance and SQLJ objects can be used.
-
Cause: Result set size exceeded the max limits.
-
Action: Check the documentation for allowable maximum result set size for scrollable cursors. Re-execute with a smaller expected result set size or make the cursor non-scrollable.
-
Cause: A session pool has already been created for the specified pool handle.
-
Action:
-
Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
-
Action: Create a session pool prior to reinitializing it.
-
Cause: An invalid combination of minimum, maximum, and increment number of sessions was specified in the OCISessionPoolCreate call.
-
Action: Specify a valid combination of parameters.
-
Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server.
-
Action: This is a warning. Check the maximum number of sessions allowed on the server.
-
Cause: Username and password must be specified when pool is created in this mode.
-
Action: Specify a valid username and password.
-
Cause: An attempt was made to use a Session Pool that does not exist.
-
Action: Create a Session Pool before using it.
-
Cause: The number of sessions has exceeded the maximum size of the Session Pool.
-
Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters.
-
Cause: Sufficient number of sessions are not present in the pool to execute the call. No new sessions can be opened as the sessMax parameter supplied in OCISessionPoolCreate has been reached.
-
Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and increase the value of the sessMax parameter.
-
Cause: A proxy session was requested from a Session Pool which does not support proxy sessions.
-
Action: Do not specify mode OCI_CRED_PROXY.
-
Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease.
-
Action: Call OCISessionRelease.
-
Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease.
-
Action: Release the session using an appropriate call.
-
Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy.
-
Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
-
Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified.
-
Action: Specify valid values for sqltext, key, or both.
-
Cause: The statement that was requested does not exist in the statement cache.
-
Action: Request a valid statement.
-
Cause: A tagged statement was requested, but an untagged statement has been returned.
-
Action: This is a warning. Please modify and tag the statement as desired.
-
Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare.
-
Action: Use a different statement handle.
-
Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.
-
Action: Call OCIStmtPrepare2 before OCIStmtRelease.
-
Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.
-
Action: Please specify the same service context that the statement was prepared with.
-
Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.
-
Action: Release the statement using OCIStmtRelease.
-
Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.
-
Action: Call OCIStmtPrepare2 before OCIStmtExecute.
-
Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.
-
Cause: UTF16 mode is allowed only at environment handle creation time.
-
Action: Remove UTF16 mode for functions other than
OCIEnvCreate(). -
Cause: Non-UTF16 string is passed in while UTF16 string is expected.
-
Action: Check the parameter which is actually a string.
-
Cause: Returned buffer has more codepoints than allowed.
-
Action: Set
OCI_MAXCHAR_SIZElarge enough to accommodate. -
Cause: Accumulated codepoint length exceeds allowed codepoint length.
-
Action: Set
OCI_MAXCHAR_SIZElarge enough to accommodate. -
Cause: Incoming data larger than receiving buffer.
-
Action: Set
OCI_MAXDATA/OCI_MAXCHAR_SIZEappropriately or remove the setting. -
Cause: An attempt was made to change character set id on non-environment handles.
-
Action: Only try to change character set id on environment handles.
-
Cause: An attempt was made to change character set id after other handles have been allocated from the env handle.
-
Action: Change character set id after creating environment handle but before allocating any handles from it.
-
Cause: Attempts to set one character set id as zero.
-
Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate()
-
Cause: Transaction ID attribute size is incorrect.
-
Action: Verify that the size parameter is correct.
-
Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW.
-
Action: Use OCI_TRANS_NEW when starting local transactions.
-
Cause: An attempt to detach a local transaction was made.
-
Action: Local transactions may only be committed or rolled back.
-
Cause: An attempt to start a new transaction was made when there was an active transaction.
-
Action: Commit, rollback or detach the existing transaction before starting a new transaction.
-
Cause: These flags are currently not supported.
-
Action: No action required.
-
Cause: An invalid transaction identifier or context was used or the transaction has completed.
-
Action: Supply a valid identifier if the transaction has not completed and retry the call.
-
Cause: An attempt was made to start a new transaction with an identifier already in use by an existing transaction.
-
Action: Verify that the identifier is not in use.
-
Cause: An attempt was made to detach or complete a transaction that is not the current transaction.
-
Action: Verify that the transaction context refers to the current transaction.
-
Cause: An invalid transaction start flag was passed.
-
Action: Verify that one of the values OCI_TRANS_NEW, OCI_TRANS_JOIN, or OCI_TRANS_RESUME was specified.
-
Cause: An invalid isolation level flag was passed.
-
Action: Verify that only one of following values - OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used.
-
Cause: The application tried to commit a transaction and the server rolled it back.
-
Action: No action required.
-
Cause: An internal error has occurred in the server commit protocol.
-
Action: Contact Oracle Support Services.
-
Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction.
-
Action: Retry the operation later.
-
Cause: This is an informational message.
-
Action: No action required.
-
Cause: This is an informational message.
-
Action: No action required.
-
Cause: This is an informational message.
-
Action: No action required.
-
Cause: This is an informational message.
-
Action: No action required.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Transaction identifier refers to an active transaction.
-
Action: Verify that the identifier of an active transaction was not passed as an argument.
-
Cause: Transaction identifier refers to a prepared transaction.
-
Action: Verify that the identifier of a prepared transaction was not passed as an argument.
-
Cause: Service handle contains a local transaction context.
-
Action: Verify that the transaction context does not refer to a local transaction.
-
Cause: Application attempted to start a transaction with a global transaction identifier and a wrong option.
-
Action: Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact Oracle Support Services.
-
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
-
Action: Verify that the right parameters are being used.
-
Cause: The transaction specified in the call refers to a transaction created by a different user.
-
Action: Create transactions with the same authentication so that they can be switched.
-
Cause: An attempt was made to detach the transaction with a non-zero lock value.
-
Action: Detach the transaction with lock value set to zero and then try to prepare or commit the transaction.
-
Cause: An attempt was made to start a new transaction when session was already attached to an existing transaction.
-
Action: End the current transaction before creating a new transaction.
-
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multithreaded server process.
-
Action: Perform the work in the local database or open a connection to the remote database from the client. If the multithreaded server option is installed, connect to the Oracle instance through the dispatcher.
-
Cause: The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s).
-
Action: Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle Support Services.
-
Cause: The migratable transaction tried to detach from the current session while an open remote cursor exists.
-
Action: Close any open remote cursor prior to detach.
-
Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long).
-
Action: Detach from the current transaction and retry the operation.
-
Cause: The list of xids passed into kpotxmp() do not have the same gtrid
-
Cause: An attempt was made to detach from a non-migrateable transaction.
-
Action: Either commit or rollback the transaction.
-
Cause: An attempt was made to prepare/commit a txn different from current.
-
Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction.
-
Cause: An attempt was made to resume a non-migrateable transaction.
-
Cause: The current transaction has been completed by another process.
-
Action: Start a new transaction.
-
Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed.
-
Action: Close all remote cursors in each call, or start a regular (non-separated) transaction.
-
Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server.
-
Action: All parts of this application should connect as dedicated or as shared.
-
Cause: An attempt was made to change the isolation level of an existing transaction.
-
Action: No action required.
-
Cause: One of the parameter values in the OCI LOB function is illegal.
-
Action: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one.
-
Cause: The only valid return value for a user defined LOB read callback function is OCI_CONTINUE. Any other value will cause this error.
-
Action: Verify that OCI_CONTINUE is returned from the user defined LOB read callback function.
-
Cause: This is an internal error.
-
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
-
Cause: When copying or appending LOB locators, both source and destination LOB locators should be of the same type.
-
Action: Pass the same type of LOB locators for copying or appending.
-
Cause: When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB.
-
Action: Make sure that the buffer you are using to read or write has the same form as that of the LOB.
-
Cause: When copying or appending LOBs, both source and destination LOB locators should have the same character set form.
-
Action: Pass locators of the same character set form for copying or appending LOBs.
-
Cause: An attempt was made to stream LOB data via the polling mode or a callback when LOB buffering was enabled for the input LOB locator.
-
Action: Lob buffering is useful when reading/writing small amounts of LOB data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the OCILobRead/OCILobWrite call.
-
Cause: LOB buffering is enabled for the input LOB locator so buffering will be used. However, the amount of LOB data to read or write is larger than what the LOB buffers can hold.
-
Action: Either disable buffering on the input LOB locator and reissue the command or pass a smaller amount.
-
Cause: While writing into a LOB, more data was supplied than indicated.
-
Action: If data is written in pieces, then make sure that you do not provide more data in the pieces (cumulatively), than you indicated.
-
Cause: While writing into a LOB, less data was provided than indicated.
-
Action: If writing data in single pieces, then make sure that the buffer length specified is big enough to accommodate the data being provided. If data is written in pieces, then make sure that all the data has been provided before specifying OCI_LAST_PIECE.
-
Cause: If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle.
-
Action: Use a version of the Oracle that supports the LOB on both the client and the server.
-
Cause: Temporary LOB locators are not allowed in the operation. For example, OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.
-
Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign.
-
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting the shared subsystem.
-
Action: Contact Oracle Support Services.
-
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem.
-
Action: Contact Oracle Support Services.
-
Cause: An internal protocol error occurred while receiving describe data from the server during execution of a statement.
-
Action: Contact Oracle Support Services.
-
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem.
-
Action: Contact Oracle Support Services.
-
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
-
Action: Correct the mode parameter passed into OCI.
-
Cause: All handles passed into an OCI call should belong to the same environment. In the call that returned this error, handles belonging to different environments were passed in.
-
Action: Make sure that the handle parameters in the call to come from the same OCI Environment.
-
Cause: The subscription handle passed into the OCI call does not have a proper name or name-length attribute.
-
Action: Set the name and name-length attributes using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call does not have a proper NAMESPACE attribute.
-
Action: Set the NAMESPACE attribute using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call does not have a proper callback attribute.
-
Action: Set the callback attribute using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call does not have a proper recepient protocol attribute.
-
Action: Set the recepient protocol attribute using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call does not have a proper recepient attribute.
-
Action: Set the recepient attribute using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call can't have both the callback defined and a recepient protocol other than OCI_SUBSCR_PROTO_OCI at the same time.
-
Action: Set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call.
-
Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute.
-
Action: Set the recipient presentation attribute using the OCIAttrSet() call.
-
Cause: The registeration that was asked to be unregistered could not be found.
-
Action: Check the callback function name and the subscription name in the unregister call.
-
Cause: A bind variable was used in the when clause of a trigger.
-
Action: Remove the bind variable. To access the table columns use (new/old).column_name.
-
Cause: Only INSTEAD OF triggers can be created on a view.
-
Action: Change the trigger type to INSTEAD OF.
-
Cause: Only BEFORE or AFTER triggers can be created on a table.
-
Action: Change the trigger type to BEFORE or AFTER.
-
Cause: Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported.
-
Action: Do not change the NEW trigger variables in the trigger body.
-
Cause: WHEN clause is specified in an INSTEAD OF trigger.
-
Action: Remove the WHEN clause when creating an INSTEAD OF trigger.
-
Cause: Attempt to create an INSTEAD OF trigger on a view created with read-only option. The view cannot be updated using INSTEAD OF triggers.
-
Action: Do not create the trigger.
-
Cause: Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table.
-
Action: Remove the UPDATE OF clause.
-
Cause: PL/SQL function call or method invocation is not allowed in the WHEN clause when creating a trigger.
-
Action: Remove the function call or method invocation from the WHEN clause.
-
Cause: When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype.
-
Action: Specified a LOB value as the new value for the LOB view column.
-
Cause: Triggers on nested tables can only be created on view columns using INSTEAD OF triggers.
-
Action: Use view nested table columns for defining nested table triggers.
-
Cause: The column name specified in the nested table clause of an INSTEAD OF trigger does not correspond to a nested table column.
-
Action: Specify a nested table column on which the trigger is to be defined.
-
Cause: The referencing clause specifies identical values for PARENT and OLD.
-
Action: Respecify either the PARENT or NEW referencing value.
-
Cause: The referencing clause specifies identical values for OLD and PARENT.
-
Action: Respecify either the OLD or PARENT referencing value.
-
Cause: Parent values can only be read and not changed.
-
Action: Do not attempt to change a Parent variable.
-
Cause: DML cannot be performed on a nested table view column except through an INSTEAD OF trigger.
-
Action: Create an INSTEAD OF trigger over the nested table view column and then perform the DML.
-
Cause: A column list cannot be specified for inserts into the nested table view column.
-
Action: Specify all the columns for insert into the nested table.
-
Cause: NEW ROWID was referenced in a before row trigger which is defined on an index-organized table, or a partitioned table with enabled movement of rows. The ROWID cannot be computed in a before row update trigger because it depends on the actual values of the row.
-
Action: Remove references to NEW ROWID from the trigger definition.
-
Cause: Conflicting instead of DDL trigger on schema/database already exists.
-
Action: Remove the old trigger.
-
Cause: Cannot pin the database/schema because of too much concurrency.
-
Action: Try the operation later.
-
Cause: renaming system triggers is not allowed.
-
Action: Drop the trigger and create a new one.
-
Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD option.
-
Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name.
-
Cause: The REBUILD option to ALTER INDEX is specified more than once.
-
Action: Specify the option at most once.
-
Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD option.
-
Action: Use ALTER INDEX REBUILD.
-
Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD option.
-
Action: Use ALTER INDEX REBUILD.
-
Cause: The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option.
-
Action: Use ALTER INDEX REBUILD.
-
Cause: The RECOVERABLE option to ALTER INDEX was used without the REBUILD option.
-
Action: Use ALTER INDEX REBUILD.
-
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement.
-
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses.
-
Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.
-
Action: Remove all but one of the TABLESPACE clauses.
-
Cause: The lock name space for the standby database exceeded the maximum string length.
-
Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a character string of less than the specified characters.
-
Cause: An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, '_', '#', '$', '.' and '@' characters.
-
Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a valid character string.
-
Cause: An attempt was made to create a bitmap index using the NOSORT option.
-
Action: Remove NOSORT from the CREATE BITMAP INDEX statement.
-
Cause: An attempt was made to create a cluster index with the BITMAP attribute.
-
Action: Remove BITMAP from the CREATE INDEX statement.
-
Cause: Too many columns were specified for the index.
-
Action: Create an index on fewer columns.
-
Cause: An attempt was made to create a bitmap index using the GLOBAL option.
-
Action: Remove GLOBAL from the CREATE BITMAP INDEX statement, and/or add a LOCAL partition descriptor if the table is partitioned.
-
Cause: An invalid file number was used in dumping a datafile or temporary file.
-
Action: Specify a valid file number.
-
Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.
-
Action: Specify only one BLOCK option.
-
Cause: An invalid block number was used in dumping a datafile or temporary file.
-
Action: Specify a valid block number.
-
Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.
-
Action: Correct the syntax.
-
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
-
Action: Correct the syntax.
-
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.
-
Action: Remove all but one of the logging specifications.
-
Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.
-
Action: Remove all but one of the MINIMUM EXTENT specifications.
-
Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT option was greater than the maximum extent size.
-
Action: Choose a lower value for the MINIMUM EXTENT option.
-
Cause: An attempt was made to create a global bitmap index on a partitioned table.
-
Action: Create a local bitmap index instead.
-
Cause: More components per name than is allowed were specified.
-
Action: Check the name specified for the operation.
-
Cause: A database link name was specified when it is not permitted.
-
Action: Check the name specified for the operation.
-
Cause: An attempt was made to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX.
-
Action: Remove this option and retry the statement.
-
Cause: The name of the buffer pool specified by the user is invalid. The only valid names are KEEP, RECYCLE and DEFAULT.
-
Action: Use a valid name or remove the BUFFER_POOL clause.
-
Cause: An attempt was made to set RELY on for NOT NULL constraint.
-
Action: Only NORELY may be specified for a NOT NULL constraint.
-
Cause: An attempt was made to insert/update/delete on table with DISABLE VALIDATE constraint.
-
Action: Change the constraint's states.
-
Cause: The named constraint does not exist for this table.
-
Action: Try again with a constraint that does exist for this table.
-
Cause: An attempt was made to modify a primary key that is not defined for the table.
-
Action: No action required.
-
Cause: An attempt was made to modify a unique key that is not defined for the table.
-
Action: No action required.
-
Cause: Cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partition is not mutually exclusive from the rest of the table.
-
Action: Change the constraint's status.
-
Cause: The SINGLE TABLE option was specified more than once.
-
Action: Specify the SINGLE TABLE option only once.
-
Cause: The keyword TABLE is missing from the SINGLE TABLE option.
-
Action: Place the keyword TABLE after the keyword SINGLE in the command.
-
Cause: The SINGLE TABLE option is only valid for hash clusters.
-
Action: Do not specify the SINGLE TABLE option.
-
Cause: An attempt was made to store more than one table in a cluster that was created with the SINGLE TABLE option.
-
Action: Do not attempt to store more than one table in the cluster.
-
Cause: Value from cast operand is larger than cast target size.
-
Action: Increase size of cast target.
-
Cause: An obsolete initialization parameter has been specified.
-
Action: The system will come up, but parameters must be examined.
-
Cause: An invalid option appears.
-
Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM.
-
Cause: An invalid option appears.
-
Action: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE is specified, and for DICTIONARY extent management UNIFORM or AUTOALLOCATE are not specified
-
Cause: An invalid option appears for EXTENT MANAGEMENT clause.
-
Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE.
-
Cause: Default storage clause was specified twice for create tablespace.
-
Action: Specify it once.
-
Cause: Default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy.
-
Action: Omit the storage clause.
-
Cause: An invalid option appears.
-
Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, USER.
-
Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM.
-
Action: Remove all but one of the allocation policy specifications.
-
Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once.
-
Action: Remove all but one of the EXTENT MANAGEMENT specifications.
-
Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size.
-
Action: Choose a lower value for the UNIFORM SIZE option.
-
Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not index-organized. The ONLINE option is currently supported only for index-organized tables.
-
Action: Remove the ONLINE option from the command.
-
Cause: An attempt was made to create an index on a column of UROWID type.
-
Action: Remove the column from the list of indexed columns.
-
Cause: An attempt was made to alter the extent parameters for a segment in a tablespace with autoallocate or uniform extent allocation policy.
-
Action: Remove the appropriate extent parameters from the command.
-
Cause: An attempt was made to create a rollback segment in a tablespace with autoallocate extent allocation policy.
-
Action: Specify a different tablespace for the rollback segment.
-
Cause: An attempt was made to drop a TEMPFILE being used by online users.
-
Action: The TEMPFILE has been taken offline. Try again later.
-
Cause: An attempt was made to use space in a temporary tablespace with no files.
-
Action: Add files to the tablespace using ADD TEMPFILE command.
-
Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.
-
Action: Remove the qualifier.
-
Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.
-
Action: Remove the qualifier.
-
Cause: When a query block uses ANSI style joins, the old notation for specifying outer joins (+) cannot be used.
-
Action: Use ANSI style for specifying outer joins also.
-
Cause: An attempt was made to create a tablespace with a block size which is not supported.
-
Action: Specify either the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform.
-
Cause: A PRIMARY KEY constraint must be defined for a table with this organization.
-
Action: Define a PRIMARY KEY.
-
Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization.
-
Action: Remove storage specification for primary key.
-
Cause: The UNRECOVERABLE option may not be specified for a primary key for a table with this organization.
-
Action: Remove UNRECOVERABLE option for primary key.
-
Cause: The storage option PCTTHRESHOLD is specified more than once.
-
Action: Specify storage options at most once.
-
Cause: The specified value must be a positive integer.
-
Action: Specify an appropriate value.
-
Cause: PCTTHRESHOLD can only be specified for tables with certain organizations.
-
Action: Remove the PCTTHRESHOLD option.
-
Cause: The ON keyword is required to specify nested index column nest.
-
Action: Add ON keyword.
-
Cause: An attempt was made to use one or more of the following feature(s) not currently supported for index-organized tables:
-
Action: Do not use the disallowed feature(s) in this release.
-
Cause: An attempt was made to drop a tablespace which contains an index only table's overflow segment but not the top index segment.
-
Action: Find index-organized tables which span the tablespace being dropped and some other tablespace(s). Drop these tables.
-
Cause: A column name is not present where required by the CREATE TABLE for specifying last column to be included in the index segment of the index-organized table.
-
Action: Specify a column name where required by the syntax.
-
Cause: An index column name other than the last was specified as including column.
-
Action: Specify either a column name which is not part of index-organized table primary key index, or the last key column of the primary key for the INCLUDING clause.
-
Cause: INCLUDING clause of a CREATE TABLE is an valid option only for index-organized tables with OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER time).
-
Action: Specify OVERFLOW clause for the index-organized table: For ALTER, perform ADD OVERFLOW first.
-
Cause: The specified table does not have the proper field definitions.
-
Action: Specify the correct table to use.
-
Cause: An attempt was made to DROP, DISABLE, or DEFER the primary key constraint for an index-only table. This is not allowed.
-
Action: Do not DROP, DISABLE, or DEFER the primary key constraint for an index-only table.
-
Cause: During ALTER of a index-organized table, the user attempted to enter one or more of the following options: TABLESPACE, ALLOCATE/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment
-
Action: Remove the illegal option(s).
-
Cause: ALTER TABLE statement attempted to combine an index-organized table maintenance operation (for example, changing physical attributes) with some other operation (for example, ADD constraint) which is illegal
-
Action: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement.
-
Cause: An attempt was made to directly access the overflow table of an index-organized table.
-
Action: Issue the statement against the parent index-organized table containing the specified overflow table.
-
Cause: An attempt was made to specify one or more of the following options for an index-organized table: [NO]CACHE, NO LOGGING, CLUSTER.
-
Action: Remove the illegal option(s).
-
Cause: An attempt was made to use COMPRESS option on single column key.
-
Action: Remove the COMPRESS option.
-
Cause: The specified value must be a positive integer less than the number of key columns.
-
Action: Specify an appropriate value.
-
Cause: An attempt was made to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED.
-
Action: Specify an appropriate option.
-
Cause: MOVE specified after one/more other ALTER options.
-
Action: Change order of options, MOVE should be first or remove the illegal option(s).
-
Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment.
-
Action: No action required.
-
Cause: System or composite partitioning schemes are not supported.
-
Action: Select a different partitioning scheme.
-
Cause: An attempt was made to specify a partitioning key which is not a prefix of the primary key of the index-organized table.
-
Action: Select a different partitioning key.
-
Cause: A NULL parameter was specified for QUEUE_NAME.
-
Action: Specify a non-NULL queue name.
-
Cause: An invalid value specified for parameter VISIBILITY.
-
Action: Specify either ON_COMMIT or IMMEDIATE.
-
Cause: A NULL value was specified for the parameter.
-
Action: Specify a non-NULL value.
-
Cause: A negative value or NULL was specified for DELAY.
-
Action: Specify a non-negative integer for DELAY.
-
Cause: An invalid SEQUENCE_DEVIATION was specified.
-
Action: Specify either the option 'BEFORE' or 'TOP'.
-
Cause: The specified queue does not exist.
-
Action: Create the queue first before specifying it for enqueue or dequeue.
-
Cause: An attempt was made to enqueue to an exception queue.
-
Action: Try enqueueing to another queue.
-
Cause: The queue has been stopped to prevent any further enqueueing.
-
Action: Enable the queue first by using an administrative operation.
-
Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE.
-
Action: Either specify an existing relative message identifier or do not specify sequence deviation as BEFORE.
-
Cause: The expiration is less than zero or NULL.
-
Action: Specify a valid value for EXPIRE_AFTER which should be greater than or equal to zero or NEVER.
-
Cause: No message in the queue with the MSGID equal to the specified RELATIVE_MSGID.
-
Action: Try again with a valid RELATIVE_MSGID.
-
Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message ID.
-
Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message ID. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue.
-
Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message ID.
-
Action: Set the PRIORITY to be less than the delay of the message with the given relative message ID. If the TOP option is used the priority must be greater than or equal to the priority of all the messages in the queue.
-
Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued.
-
Action: No action required. This is an informational message only.
-
Cause: A message was enqueued to the exception queue with either delay or expiration specified.
-
Action: Enqueue a message without delay or expiration.
-
Cause: A user tries to enqueue an object to a queue that was created for objects of different type.
-
Action: Try enqueue again with an object of the right type.
-
Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list.
-
Action: Specify a non-null NAME or ADDRESS for the recipient.
-
Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.
-
Action: Set visibility to IMMEDIATE.
-
Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.
-
Action: Set delay to zero.
-
Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.
-
Action: Do not specify sequence deviation.
-
Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature.
-
Action: Specify the signature.
-
Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation.
-
Action: Remove the signature.
-
Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation.
-
Action: Provide the sender information.
-
Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.
-
Action: Enqueue the message again with data of raw or object type.
-
Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.
-
Action: Enqueue the message with sender name specified.
-
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
-
Action: Specify either REMOVE, BROWSE or LOCKED.
-
Cause: The queue has not been enabled for dequeue.
-
Action: Enable the queue using START_QUEUE.
-
Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved.
-
Action: Try dequeue again with the appropriate WAIT_TIME or the FIRST_MESSAGE option.
-
Cause: There was an error when transforming a message at enqueue, dequeue, or propagation time.
-
Action: Correct the transformation function.
-
Cause: A negative value has been specified for WAIT.
-
Action: Specify a non-negative value or FOREVER.
-
Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options.
-
Action: Specify the CONSUMER_NAME in the dequeue options.
-
Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.
-
Action: Remove the duplicate queue agent and retry the call.
-
Cause: An invalid parameter has been specified for NAVIGATION.
-
Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisfies the criterion, NEXT_MESSAGE for dequeuing the next message that satisfies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.
-
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping.
-
Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled.
-
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.
-
Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.
-
Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued.
-
Action: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K.
-
Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.
-
Action: Reset the dequeuing position using the FIRST_MESSAGE navigation option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option.
-
Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address).
-
Action: Reduce the number of recipients to 32 or less, and retry the call.
-
Cause: An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options.
-
Action: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the QUEUE_TABLE containing the queue to release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
-
Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either a message ID or a dequeue condition/correlation ID, or neither.
-
Action: To dequeue a message, specify a message ID or a dequeue condition/correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or dequeue condition/correlation ID in the dequeue options.
-
Cause: An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
-
Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
-
Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
-
Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
-
Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.
-
Action: Specify only the message ID in the dequeue options to dequeue a message from an exception queue.
-
Cause: An internal error was encountered. There may be an inconsistency in the queue table index.
-
Action: Contact Oracle Support Services. You may need to provide the trace file and information about reproducing the error.
-
Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.
-
Action: Do not specify the agent name.
-
Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.
-
Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.
-
Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message ID.
-
Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message ID.
-
Cause: An agent was specified more than once in the agent list of the LISTEN call.
-
Action: Remove the duplicate agent specification(s), and retry the call.
-
Cause: An attempt was made to dequeue from a non-persistent queue.
-
Action: Dequeue from a different queue.
-
Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.
-
Action: Do not specify the address field or specify the queue which is the target of the enqueue
-
Cause: An attempt was made to issue an ENQUEUE call that exceeded the maximum number (1024) of recipients per message.
-
Action: Reduce the number of recipients to 1024 or less, and retry the call.
-
Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.
-
Action: Specify a normal queue as address for the agent, and retry the LISTEN call.
-
Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.
-
Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call.
-
Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.
-
Action: Try the LISTEN call with an appropriate time-out.
-
Cause: An incorrect subscription string was specified with OCIRegister.
-
Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form.
-
Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue.
-
Action: Do not specify the consumer in the subscription string.
-
Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string.
-
Action: Specify a consumer in the subscription string.
-
Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.
-
Action: Specify a normal queue or a non-persistent queue.
-
Cause: The user specified the protocol attribute for an agent in the agent list.
-
Action: Do not specify the protocol attribute of the agent object type.
-
Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.
-
Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation.
-
Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue.
-
Action: Specify a non-NULL name for the agent.
-
Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue.
-
Action: Try dequeue again with a valid message ID.
-
Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable.
-
Action: Try dequeue again without the get signature option.
-
Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification.
-
Action: Try dequeue again without the signature.
-
Cause: The signature was specified for a queue, but the dequeue was not done by message id.
-
Action: Try dequeue again by message id.
-
Cause: The signature was not specified for a reciever non-repudiable queue.
-
Action: Try dequeue again along with the signature.
-
Cause: The dequeue was not performed in browse mode with get signature option.
-
Action: Try dequeue again in browse mode.
-
Cause: The signature is not required for the dequeue with get signature option.
-
Action: Try dequeue again without the signature in dequeue options.
-
Cause: The sender info and the message id do not match.
-
Action: Provide the correct sender info or try dequeue again without the signature in dequeue options.
-
Cause: The queue table does not exist for the given queue.
-
Action: Provide the correct queue name.
-
Cause: Signature does not exist for the given reciever and message id.
-
Action: Check the message id and the reciever's information.
-
Cause: An invalid queue table name is specified.
-
Action: Check the dictionary views to see if the table is a queue table.
-
Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.
-
Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege.
-
Cause: An attempt was made to specify NULL for the grantee parameter.
-
Action: Specify a valid grantee parameter.
-
Cause: Dequeue as select not supported before 9.0.0.
-
Action: Don't use select condition while dequeuing.
-
Cause: Complete sender information not provided to non-repudiate sender.
-
Action: Provide the complete sender information.
-
Cause: Complete reciever information not provided to non-repudiate reciever.
-
Action: Provide the complete reciever information.
-
Cause: Message id was not provided.
-
Action: Provide the message id.
-
Cause: neither agent's name nor address provided for non-repudiation.
-
Action: Provide the agent info.
-
Cause: An Invalid value or NULL was specified for the parameter.
-
Action: Check the documentation for valid values.
-
Cause: An Invalid value or NULL was specified for the array_mode.
-
Action: Check the documentation for valid values.
-
Cause: Number of elements in the message properties array does not match the number of elements in the payload array.
-
Action: Create a message property array with one element (that applies for all the elements in the payload array) or create a message property array with the same number of elements as there are in the payload array.
-
Cause: An Invalid value or NULL was specified for the parameter.
-
Action: Specify a non negative integer.
-
Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error.
-
Action: Specify a valid address in the connect string of the propagation destination dblink, make sure the dblink user has the correct permissions, and check if the AQ propagation servlet was properly installed.
-
Cause: Buffer already exists for the specified queue.
-
Action: No action required.
-
Cause: Queue already has messages. Cannot complete operation.
-
Action: Truncate the queue before adding/dropping a buffer.
-
Cause: Buffer does not exist for the specified queue.
-
Action: Operation on the buffer cannot be performed. create the buffer.
-
Cause: Buffer cannot be added on the Specified Queue.
-
Action: Can only add buffers to 8.1 style non-exception multi-consumer queues, which do not have priority, non_repudiation, message_grouping, max_retries, and retention.
-
Cause: Specified Queue has remote recipient subscribers.
-
Action: Cannot add buffers/add buffered subscribers to queues with remote recipient subscribers.
-
Cause: Specified Queue has a buffer.
-
Action: Drop the buffer first.
-
Cause: Subscriber is only allowed to dequeue persistent messages.
-
Action: Drop the subscriber and re-create it.
-
Cause: Cannot downgrade the queue table because it has a buffered queue.
-
Action: Drop the buffer or the buffered queue.
-
Cause: The message options only make sense for buffered messages.
-
Action: Check the enqueue/dequeue options.
-
Cause: The memory threshold for a queue cannot be negative.
-
Action: Correct the memory threshold.
-
Cause: Cannot add buffered subscriber for a non-buffered queue.
-
Action: Either add buffer to the queue, or make the subscriber non-buffered.
-
Cause: Cannot drop buffer for queue with buffered subscribers.
-
Action: Either drop buffered subscribers or forcibly drop the buffer.
-
Cause: Recipient list for buffered queue not supported.
-
Action: Don't specify recipient list for buffered enqueues.
-
Cause: Last enqd/ackd message is only supported for buffered queues.
-
Action: The operation is not supported.
-
Cause: The limit on the number of concurrent transaction branches has been reached.
-
Action: Increase the initialization parameter TRANSACTIONS and restart the system.
-
Cause: The transaction is currently used by a different session.
-
Action: Do not switch to a transaction attached to some other session.
-
Cause: The user session is not attached to any transaction.
-
Action: Do not attempt to detach when there is no current transaction.
-
Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed.
-
Action: No action is required for the branch to be deleted.
-
Cause: A failure occurred since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches.
-
Action: This is an internally used error message and should not be seen by the user.
-
Cause: A failure occurred since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches.
-
Action: Re-execute the statement and start fetching from the beginning.
-
Cause: A failure occurred while a transaction was active on this connection.
-
Action: The client must roll back.
-
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
-
Action: Manually reconnect.
-
Cause: The primary instance has died.
-
Action: This is an internally used error message and should not be seen by the user.
-
Cause: A failure occurred while a transaction was attempting to commit. Failover could not automatically determine instance status.
-
Action: The user must determine the transaction's status manually.
-
Cause: Failover was unable to generate an address for a backup instance.
-
Action: Contact Oracle Support Services.
-
Cause: The connection was lost while doing a fetch.
-
Action: This is an internally used error message and should not be seen by the user.
-
Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.
-
Action: Check to see if the results of the call have taken place, and then replay it if desired.
-
Cause: The connection was lost while issuing a rollback.
-
Action: If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required.
-
Cause: A shared database link is being used to connect to a remote instance that does not support this feature because it is an older version.
-
Action: Use a normal database link if you need to connect to this instance.
-
Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias.
-
Action: Check the valid table aliases in the evaluation context, and try again with a valid alias.
-
Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias.
-
Action: Check the table values specified, and try again with only one value per table.
-
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name.
-
Action: Check the valid variable names in the evaluation context, and try again with a valid name.
-
Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name.
-
Action: Check the variable names specified, and try again with only one value per variable.
-
Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias.
-
Action: Check the valid table aliases in the evaluation context, and try again with a valid name.
-
Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied.
-
Action: Check the table and column values specified, and try again with either a table value or column values for each table alias.
-
Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias.
-
Action: Check the column values specified, and try again with the right number of column values.
-
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number.
-
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
-
Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias.
-
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
-
Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value.
-
Action: Check the column values specified, and try again with a valid column number.
-
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name.
-
Action: Check the specified column values, and try again with only one column value for each table alias and column name.
-
Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule.
-
Action: Check the rule and the values passed to evaluate, and try again with valid values.
-
Cause: An attempt to load the specified rule failed due to errors in the rule.
-
Action: Check the rule and retry the operation.
-
Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.
-
Action: Check the rule set name, and try again with a valid name.
-
Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.
-
Action: Check the evaluation context name, and try again with a valid name.
-
Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name.
-
Action: Check the list of table values, and try again with a valid alias name.
-
Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID.
-
Action: Check the list of table values, and try again with a valid ROWID.
-
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name.
-
Action: Check the list of variable values, and try again with a valid variable name.
-
Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data.
-
Action: Check the list of variable values, and try again with valid data.
-
Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name.
-
Action: Check the list of column values, and try again with a valid alias name.
-
Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name.
-
Action: Check the list of column values, and try again with a valid column name.
-
Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data.
-
Action: Check the list of column values, and try again with valid data.
-
Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.
-
Action: Open the database and retry this command.
-
Cause: Database resource manager failed to change plan.
-
Action: Look at the alert logs to see a detailed description of the error.
-
Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system.
-
Action: Contact the database administrator who is responsible for the concurrent command.
-
Cause: Database cannot be opened because the system is being or has been quiesced.
-
Action: Open the database after the system has been quiesced.
-
Cause: Cannot quiesce the system because the system is already quiesced.
-
Cause: Cannot unquiesce the system because the system is not in quiesced state.
-
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances.
-
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.
-
Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command.
-
Action: Mount the database and retry this command.
-
Cause: A column has been added to a replicated table, but replication support processing has not completed.
-
Action: Wait until replication support processing has completed before updating the column.
-
Cause: One value in
_DB_MTTR_SIM_TARGETis not a valid MTTR. -
Action: Alter the value of
_DB_MTTR_SIM_TARGET. -
Cause: One value in
_DB_MTTR_SIM_TARGETis empty. -
Action: Set the value of
_DB_MTTR_SIM_TARGETproperly. -
Cause: Too many candidate MTTRs are specified in
_DB_MTTR_SIM_TARGET. -
Action: Alter the value of
_DB_MTTR_SIM_TARGET. -
Cause: An attempt to start MTTR advisory was made, which failed because
FAST_START_MTTR_TARGETwas not specified. -
Action: Set
FAST_START_MTTR_TARGET. -
Cause: The current
FAST_START_MTTR_TARGETsetting or a candidate MTTR setting is too small for MTTR advisory. -
Action: Set a larger
FAST_START_MTTR_TARGETor candidate MTTR. -
Cause: The current
FAST_START_MTTR_TARGETsetting or a candidate MTTR setting is too large for MTTR advisory. -
Action: Set a smaller
FAST_START_MTTR_TARGETor candidate MTTR. -
Cause: An attempt to create a join index was made, which failed because no valid where clause was found.
-
Action: Ensure that a where clause with valid join conditions is specified in the create index statement.
-
Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause.
-
Action: Reformulate the where clause without using ORs.
-
Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn't an equi-inner join.
-
Action: Remove the inappropriate predicate.
-
Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone).
-
Action: Remove any functional indexing columns.
-
Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions.
-
Action: Ensure that the where clause is correct (contains all of the constraint columns) and that an enforced constraint is on each dimension table.
-
Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.
-
Action: Ensure that the where clause contains all from clause tables.
-
Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS.
-
Action: Ensure that no join index related table is owned by SYS.
-
Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle.
-
Action: Ensure that the where clause is in the form of a star or snowflake schema.
-
Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column.
-
Action: Ensure that the where clause only contains columns.
-
Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.
-
Action: Make the index a bitmap index.
-
Cause: An attempt to create a join index was made, which failed because one of the tables was temporary.
-
Action: Ensure no underlying tables are temporary.
-
Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.
-
Action: Drop the join index or remove the constraint.
-
Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.
-
Action: Drop the join index.
-
Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.
-
Action: Ensure that the from clause only contains tables.
-
Cause: The datatype of the join column is incompatible with the datatype of the joined column.
-
Action: Select a compatible datatype for the join column.
-
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned.
-
Action: Remove the partition specification from the SQL*Loader control file and retry the load.
-
Cause: A non-existent index was specified in the SORTED INDEXES clause.
-
Action: Do not specify as a SORTED INDEX.
-
Cause: Parallel load was specified into a table which has index defined upon it.
-
Action: Drop index(es) defined upon table, or do not use parallel load, or use SKIP_INDEX_MAINTENANCE option.
-
Cause: Parallel load is not supported for index-organized tables.
-
Action: Load the index-organized table without the PARALLEL option.
-
Cause: An attempt was made to load a clustered table via the direct path.
-
Action: Use the conventional path.
-
Cause: In direct path load, the handle passed in does not match the type listed.
-
Action: Verify the handle and type are correct.
-
Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.
-
Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list.
-
Cause: The user tried to use the INSERT option on a non-empty table.
-
Action: Empty the table from SQL*Plus, or use the REPLACE option.
-
Cause: A column which is NOT NULL in the database has a SQL*Loader NULLIF clause on it.
-
Action: Remove the NULLIF clause in the SQL*Loader control file.
-
Cause: A column which is NOT NULL in the database has a SQL*Loader DEFAULTIF clause which may evaluate to null.
-
Action: Remove the DEFAULTIF clause in the SQL*Loader control file.
-
Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.
-
Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file.
-
Cause: A column can only store data of type declared for that column and a substitutable column can only store data of valid subtypes of the supertype declared for that column.
-
Action: Check that the type or subtype specified is valid for that column.
-
Cause: Executing sql statement against the data dictionary tables returned "ORA-01403: no data found".
-
Action: No data retrieved when selecting against the data dictionary tables most likely means that there's an error in user input. Check that the input listed is correct.
-
Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.
-
Action: Contact Oracle Support Services.
-
Cause: Client set OCI_ATTR_DIRPATH_SUBST_OBJ_TBL for either a non-object table or for a final object table. This attribute can only be, and must be, set for non-final object tables.
-
Action: Check the type of the loading table. Do not set this attribute if the table is not a non-final object table.
-
Cause: User attempted to load an array column via the direct path.
-
Action: Use the conventional path.
-
Cause: The record indicated caused an Oracle error on insert.
-
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
-
Cause: Global indexes are defined on a table when direct path loading a single partition of the table.
-
Action: Remove the global index from the named table and retry the operation.
-
Cause: Column specified in the loader control file does not exist.
-
Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong.
-
Cause: The specified column of SQL column type string is not supported by the direct path loader.
-
Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL.
-
Cause: Non-partitioned index information put to loader log file.
-
Action: No action required. This is an informational message.
-
Cause: Partitioned index information put to loader log file.
-
Action: No action required. This is an informational message.
-
Cause: A non-partitioned index was made index unusable due to the error displayed below this error.
-
Action: Depending on the error, either rebuild the index, or drop and re-create it.
-
Cause: A partition of a partitioned index was made index unusable due to error displayed below this error.
-
Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index.
-
Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment was in unusable state prior to the beginning of the load.
-
Action: Informational only. User will need to either rebuild the index or index partition, or re-create the index.
-
Cause: A request was made that index maintenance be skipped on a direct path load.
-
Action: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index.
-
Cause: A unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
-
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
-
Cause: A partition of a unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
-
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
-
Cause: An index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
-
Action: Either rebuild the index, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
-
Cause: A partition of an index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
-
Action: Either rebuild index partition, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
-
Cause: A logical index error occurred on a partitioned index which affected one or more index partitions, which are listed below this message.
-
Action: The affected index partitions will have to be rebuilt, or, the entire index dropped and re-created.
-
Cause: A index error occurred during the index maintenance phase of a direct path load. The load cannot continue. See error message below this message.
-
Action: See action for the error message which follows this one.
-
Cause: An index error occurred during direct-load of an index-organized table. Loading had to be aborted. No rows were loaded.
-
Action: Check the key just following the number of keys mentioned above. This key caused the index problem mentioned in an earlier message.
-
Cause: An index error occurred while attempting to evaluate an expression on a functional index.
-
Action: Verify that the input data is valid for the functional index.
-
Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.
-
Action: Verify that the control file describes the data correctly and that the data in the datafile matches the description in the control file
-
Cause: The record indicated caused an Oracle error on insert.
-
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
-
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned.
-
Action: Remove the subpartition specification from the SQL*Loader control file and retry the load.
-
Cause: The record indicated caused an Oracle error on insert.
-
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
-
Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.
-
Action: Verify that the count portion for the field has the correct value.
-
Cause: Direct path load was specified for a table which has a domain index defined upon it.
-
Action: Drop domain index(es) defined on the table or use the conventional path.
-
Cause: An attempt was made to access data in a block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option.
-
Action: Drop the object containing the block.
-
Cause: The column could not be converted from DATETIME datatype to internal DATETIME/CHARACTER datatype.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to convert a DATETIME format string into internal format in preparation for DATETIME datatype processing failed.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to convert the time zone specified by the ORA_STDZ environment variable to internal format failed.
-
Action: Verify that the setting for ORA_STDZ is valid.
-
Cause: An attempt to retrieve the system reference date for DATETIME/INTERVAL datatypes failed.
-
Action: Contact Oracle Support Services.
-
Cause: The number of arguments for the REF column is incorrect.
-
Action: Specify the correct number of input arguments for REFs.
- Unscoped system-generated REFs can have exactly 1 or 2 input arguments.
It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through
OCI_DIRPATH_EXPR_REF_TBLNAME.It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through
OCI_DIRPATH_EXPR_REF_TBLNAME. - Scoped system-generated REFs can have 1 or 2 input arguments.
Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted.
- Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments.
Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.
- Unscoped system-generated REFs can have exactly 1 or 2 input arguments.
-
Cause: The scoped table name passed in by the user does not match the name in the schema.
-
Action: Specify the correct table name for the scoped REF column.
-
Cause: The value passed in by the user for the system generated oid does not consist of valid hexadecimal digits.
-
Action: Specify a valid oid value for the REF column.
-
Cause: The scoped table name passed in by the user does not match the name in the schema.
-
Action: Specify the correct table name for the scoped REF column.
-
Cause: The table name passed in by the user does not exist in the schema.
-
Action: Specify a valid table name for the unscoped REF column.
-
Cause: Direct path can not load a domain index of that column type.
-
Action: Drop the index and try again or load using conventional path.
-
Cause: A packed decimal field with a nonzero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.
-
Action: Examine the packed decimal field's precision and scale specifications and make sure that they contain valid values.
-
Cause: The direct path api does not support a SQL expression on a column of that type.
-
Action: Make sure the types are correct.
-
Cause: Client attempted to set or reset the number of rows in a direct path structure after it has already been allocated and initialized. Attributes used is one of the following:
-
Action: Set the following attributes before:
-
Cause: Client attempted to allocate a column array for a direct path function context before allocating a column array for the table-level direct path context.
-
Action: Allocate the table-level direct path context's column array via OCIHandleAlloc before allocating column arrays for direct path function contexts.
-
Cause: A parallel load file was specified which is not part of the database.
-
Action: Check filename and pathname for correctness.
-
Cause: A parallel load file was specified which is not in the tablespace of the table being loaded.
-
Action: Check to make sure that the specified parallel load file is in the tablespace of the table being loaded.
-
Cause: A parallel load file was specified which is not in the tablespace of the table (partition, subpartition) being loaded. When a partitioned table is being loaded, the file must be in the tablespace of every partition or subpartition (that is, each (sub)partition must be in the same tablespace).
-
Action: Specify a different parallel load file, or no file at all.
-
Cause: The row header flag byte contains an unexpected value, this indicates that an error has occurred in either the generation of, or the pushing of the load stream from the client to the server.
-
Action: Usually due to an application programming error when dealing with error handling, or not resetting the stream state.
-
Cause: Client application is attempting to do multiple direct path load operations on the same table, but the segments overlap.
-
Action: Check the partition names (subname attribute of the direct path context) being loaded. Make sure you are not loading a table and a partition of the same table. Make sure you are not loading a partition, and a sub-partition within the same partition.
-
Cause: An OCIDirPathLoadStream operation was attempted after OCIDirPathFinish was called. Once a direct path operation has been finished, no more data can be loaded.
-
Action: Check program logic to make sure OCIDirPathLoadStream is not called after OCIDirPathFinish.
-
Cause: A direct path operation is being attempted within a transaction that has already been started.
-
Action: Commit the transaction and Prepare the direct path operation again.
-
Cause: A direct path operation is being attempted on a table which has enabled triggers.
-
Action: Disable the triggers on the table and try again.
-
Cause: A direct path operation was attempted on a table which has enabled referential integrity constraints.
-
Action: Disable the referential integrity constraints on the table and try again.
-
Cause: All scalar columns (that is, non-LOB and non-LONG columns) must be specified by the client of the direct path API prior to specifying any LOB columns.
-
Action: Specify all scalar columns prior to specifying any LOB columns.
-
Cause: A client of the direct path API specified a LONG column to be loaded, but the LONG column was not the last column to be specified.
-
Action: Specify the LONG column last.
-
Cause: A direct path operation is being finished or a data save request has been made, but the table for which the request is being made on has a row in partial state. The row must be completed before the segment high water marks can be moved.
-
Action: Either complete the row, or abort the direct path operation.
-
Cause: A direct path operation was requested that is not supported
-
Action: Do not use that operation. Currently, UNLOAD is not supported.
-
Cause: A column which is not a LONG or LOB had the OCI_DIRPATH_COL_PARTIAL flag associated with it. Only LONG or LOB type columns can be loaded in pieces.
-
Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.
-
Cause: The ROW_COUNT attribute was being read from a direct path stream handle and it was found that the stream offset for the last processed row did not map to a column array offset.
-
Action: Make sure the stream was sourced from a column array.
-
Cause: An input stream contained data for more input columns than specified by the client of the direct path API.
-
Action: Make sure that the stream being loaded is for the correct table. Check initialization sequence.
-
Cause: Either a OCIDirPathLoadStream call was made which provided more stream data prior to the server being able to fully process the stream data that it already has, or a OCIDirPathFinish call was made when the server had unprocessed stream data.
-
Action: Most likely an application misuse of the direct path API. Make sure that the stream is not being reset inadvertently prior to any previous stream data being processed, or, that OCIDirPathFinish is not being called prematurely (that is, stream pushed, error encountered and LoadStream not called to process the remainder of the stream before Finish is called).
-
Cause: Either the transfer buffer size specified, or the default transfer buffer size (if you did not specify a size), is too small to contain a single row of the converted row data.
-
Action: Set the transfer buffer size attribute of the direct path context to be larger.
-
Cause: The direct path API does not support the required conversion.
-
Action: Make sure the types are correct.
-
Cause: A direct path API function was called with a direct path context which has not been prepared.
-
Action: Make sure all necessary attributes in the direct path context have been set, and the context is prepared via OCIDirPathPrepare.
-
Cause: OCIDirPathPrepare was called with a context that has already been prepared.
-
Action: Free the direct path context, set necessary attributes, and call OCIDirPathPrepare.
-
Cause: This error is not used.
-
Action: No action required.
-
Cause: The tablespace number in the file header is inconsistent with that in the control file.
-
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
-
Cause: The relative file number in the file header is inconsistent with that in the control file.
-
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
-
Cause: The file header of the referenced file is in V6 or V7 format.
-
Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format.
-
Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.
-
Action: Use DBMS_REPUTIL.SYNC_UP_REP to validate the replication catalog, or use DBMS_REPUTIL.MAKE_INTERNAL_PKG to validate internal package.
-
Cause: An external RepAPI operation failed.
-
Action: Consult detail error message.
-
Cause: An internal service failed and signalled an error.
-
Action: Consult detail error message.
-
Cause: An unexpected internal RepAPI failure was detected.
-
Action: Contact Oracle Support Services.
-
Cause: The caller requested a RepAPI operation that was not implemented.
-
Action: Do not issue this call.
-
Cause: An internal buffer control structure was NULL.
-
Action: Verify that sufficient memory resources are available to RepAPI.
-
Cause: An internal buffer control structure was NULL.
-
Action: Verify that sufficient memory resources are available to RepAPI.
-
Cause: The master connection handle was or became invalid.
-
Action: Verify that the master connection is valid.
-
Cause: The client connection handle was or became invalid.
-
Action: Verify that the client connection is valid.
-
Cause: An internal materialized view control structure could not be obtained.
-
Action: Check that the owner and users provided are correct.
-
Cause: The specified materialized view name was too long.
-
Action: Shorten the materialized view name.
-
Cause: A RepAPI operation was attempted against a non-existent or invalid master table.
-
Action: Verify that the master table object exists.
-
Cause: An unexpected error occurred while sending an DEF$ERROR RPC to the master site.
-
Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary.
-
Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.
-
Action: Notify master site system administrator or database administrator.
-
Cause: The specified object was expected but not found.
-
Action: Verify that the specified object exists and is valid.
-
Cause: The specified master log was not found or available for the named table.
-
Action: Create the master log at the master site or correct any problems that may exist with the log.
-
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully committed by the master site.
-
Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction.
-
Cause: The specified materialized view catalog control record was not found.
-
Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined.
-
Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.
-
Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
-
Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.
-
Action: Shut down one or more local applications to attempt to free heap memory and retry the RepAPI operation.
-
Cause: An internal memory error was detected.
-
Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem.
-
Cause: An error occurred during the initialization of a PL/SQL RPC.
-
Action: Verify that the procedure to be invoked exists and is valid at the master site and is executable by the RepAPI user.
-
Cause: An error occurred during the execution of a PL/SQL RPC.
-
Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked RPC.
-
Cause: An error occurred during the termination of a PL/SQL RPC. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.
-
Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted.
-
Cause: The NLS product/facility error message file could not be located or properly initialized.
-
Action: Check that the error message directory and file(s) have been properly installed.
-
Cause: A connection could not be established to the specified database using the provided connection string.
-
Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working.
-
Cause: The client SQL materialized view definition query could not be properly parsed by the master Oracle site.
-
Action: Check that materialized view DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.
-
Cause: The client callback failed during its INIT phase for the named object.
-
Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
-
Cause: The client callback failed during its PROC phase for the named object.
-
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
-
Cause: The client callback failed during its TERM phase for the named object.
-
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
-
Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.
-
Action: Verify that the named materialized view(s) are properly defined and valid.
-
Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.
-
Action: Do not enable the event for normal operation.
-
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
-
Action: See the action section for E_QUEUESYNC (26518).
-
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
-
Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables.
-
Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view's master site.
-
Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
-
Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has been created.
-
Action: If desired, unregister the replicated table with DBMS_REPCAT.DROP_MASTER_REPOBJECT, or use the recommended procedure to rename the master table of a materialized view.
-
Cause: User passed type of the given argument number does not match with the type of the argument in the stored arguments.
-
Action: Invoke correct type procedure (that is, get_XXX_arg).
-
Cause: User invoked type_arg procedure before starting a deferred call.
-
Action: Invoke various procedures in the correct order.
-
Cause: Failed to open connection using given database link.
-
Action: Make sure that the database link is valid and remote m/c is up.
-
Cause: The number of arguments does not match the replication catalog.
-
Action: Examine the total number of arguments for the RPC call.
-
Cause: The (RPC) call is corrupted.
-
Action: Examine total number of arguments and each argument for the RPC call.
-
Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.
-
Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.
-
Cause: An error occurred during creation of a capture or apply background process.
-
Action: Review V$Capture and V$Apply_coordinator views for the status of these processes. Also check the trace file for more information.
-
Cause: The value specified in the action context is invalid for use in STREAMS.
-
Action: Check that the type and value are correct.
-
Cause: An attempt was made to create a STREAMS process that already exists.
-
Action: Either specify another STREAMS process or remove the existing STREAMS process.
-
Cause: An attempt was made to alter a STREAMS process that is currently running.
-
Action: Stop the STREAMS process and re-issue the command.
-
Cause: An attempt was made to specify an invalid parameter.
-
Action: Check the documentation for valid parameters.
-
Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.
-
Action: Check the documentation for valid parameter values.
-
Cause: Streams requires compatibility to be 9.2.0 or higher.
-
Action: Shut down and restart with an appropriate compatibility setting.
-
Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.
-
Action: Remove existing STREAMS processes and retry the operation.
-
Cause: Timeout occurred while waiting for a STREAMS process to shut down.
-
Action: Retry the operation. If the error persists, then try stopping the process with the FORCE option, or contact Oracle Support Services.
-
Cause: The specified object type is not supported.
-
Action: Retry with a supported object type.
-
Cause: The specified command type is not supported.
-
Action: Retry with a supported command type.
-
Cause: The publication_on parameter should be either 'Y' or 'N'.
-
Action: Retry with a proper value for publication_on.
-
Cause: The value_type parameter should be either 'OLD' or 'NEW'.
-
Action: Retry with proper value_type.
-
Cause: The value_type parameter should be one of 'OLD', 'NEW', or '*'.
-
Action: Retry with proper value_type.
-
Cause: Transactions from multiple sources were sent to the same apply process.
-
Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.
-
Cause: An attempt was made to specify an invalid SCN.
-
Action: Retry with a valid SCN.
-
Cause: Object SCN has not been set.
-
Action: Set the SCN by calling DBMS_APPLY_ADM.SET_INSTANTIATION_SCN.
-
Cause: Metadata mismatch, or not enough information in the user generated LCR.
-
Action: Alter the database object, or provide all defined keys in the LCR.
-
Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.
-
Action: Alter the database object.
-
Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.
-
Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.
-
Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.
-
Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.
-
Cause: An attempt was made to access a STREAMS process which does not exist.
-
Action: Check with the relevant security views for the correct name of the object.
-
Cause: SBTINIT returned an error, additional information indicates error.
-
Action: Verify that vendor's storage subsystem product is operating correctly.
-
Cause: The specified device type is supported on this platform.
-
Action: Check V$BACKUP_DEVICE for supported device types.
-
Cause: An internal error occurred. Additional information indicates which function encountered error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: An internal error occurred. A file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: An internal error occurred. The block size specified is incorrect for the device on which file is being created, additional information indicates block size specified, and the function that encountered the error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: An internal error occurred. A file is being opened for asynchronous I/O on a device that does not support asynchronous I/O, additional information indicates which function encountered error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: Additional information indicates error returned by SBTREMOVE, and the function that encountered the error.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: SBTOPEN returned error, additional information indicates error returned from SBTOPEN, and the function that encountered the error.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: An internal error occurred. Additional information indicates which function encountered error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: An internal error occurred.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: SBTWRITE returned error, additional information indicates error returned from SBTWRITE.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: An internal error occurred.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: SBTREAD returned error, additional information indicates error returned from SBTREAD.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: An internal error occurred.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: Failure of SLTLN in SKGFQPINI.
-
Action: Check additional return error for more information.
-
Cause: SBTCLOSE returned an error. Additional information indicates error returned from SBTCLOSE.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: Additional information indicates error returned from SBTINFO.
-
Action: Verify that the vendor's storage subsystem product is operating correctly.
-
Cause: Media handle string length exceeds SSTMXQMH.
-
Action: Verify that the vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is at least 64 (the limit specified for SBTINFO). additional information indicates the media handle string length returned by SBTINFO, and the limit (SSTMXQMH).
-
Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.
-
Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.
-
Cause: The length of the tape file name provided to sequential I/O OSD functions is too long.
-
Action: Additional information indicates in which function this error is encountered, the length of file name provided, and the limit on file name.
-
Cause: The platform or the specified device type does not support named devices.
-
Action: Do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available.
-
Cause: The file name which will be passed to SBTOPEN was not specified.
-
Action: Specify a file name and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name.
-
Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services.
-
Action: Increase the amount of memory available to the Oracle process and retry the backup/restore.
-
Cause: The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. This is an internal error in the media management product.
-
Action: Contact the media management vendor.
-
Cause: SBTINIT2 returned an error. This happens during a backup or restore operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: The media management software requested a context area size which is greater than the maximum allowable size. This is an internal error in the media management product.
-
Action: Contact the media management vendor.
-
Cause: SBTEND returned an error. This happens during a backup or restore operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTREMOVE2 returned an error. This happens when deleting a backup file.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTBACKUP returned an error. This happens when creating a backup file during a backup operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTRESTORE returned an error. This happens when retrieving a backup file during a restore operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTWRITE2 returned an error. This happens while writing a backup file during a backup operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: An internal error occurred.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: GETRLIMIT system call returned an error.
-
Action: Check errno.
-
Cause: ULIMIT system call returned an error.
-
Action: Check errno.
-
Cause: Too many characters in the ORACLE_SID string.
-
Action: Rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system.
-
Cause: Logical block size for Oracle files must be a multiple of the physical block size, and less than the maximum.
-
Action: Block size specified is returned as additional information, check initialization parameters, additional information also indicates which function encountered the error.
-
Cause: Additional information indicates SLTLN/SLNRM error, and also indicates which function encountered the error.
-
Action: Check additional information.
-
Cause: STAT system call returned an error, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: Trying to create a database file, but file by that name already exists.
-
Action: Verify that name is correct, specify reuse if necessary.
-
Cause: An attempt was made to create a file that exceeds the process' file size limit, additional information indicates which function encountered the error.
-
Action: Raise the file size limit.
-
Cause: Create system call returned an error, unable to create file.
-
Action: Verify the file name and permissions.
-
Cause: Open system call returned an error, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: This is an internal error. The file is too large for the raw partition. Additional information indicates which function encountered the error.
-
Action: Check for trace file and contact Oracle Support Services.
-
Cause: Seek system call failed, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: Write system call failed, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: Close system call failed, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: File size as indicated by STAT is not correct, additional information indicates which function encountered the error.
-
Action: Verify that the file has not been overwritten or truncated.
-
Cause: Read system call failed, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: Possibly trying to use a non-database file as a database file.
-
Action: Verify that file is a database file.
-
Cause: An attempt was made to seek to and read the last block in file, additional information indicates which function encountered error.
-
Action: Check errno.
-
Cause: This is an internal error. Additional information indicates which function encountered error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: FSYNC system call returned error, additional information indicates which function encountered the error.
-
Action: Check errno.
-
Cause: The logical block size is invalid, additional information indicates the logical block size and the block size in the file header.
-
Action: Use a different logical block size, or do not reuse file.
-
Cause: Unlink system call returned error.
-
Action: Check errno.
-
Cause: This is an internal error. The query is being asked about asynchronous vector I/O when the file does not support asynchronous I/O.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. An invalid query is being asked.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: FTRUNCATE system call returned error.
-
Action: Check errno.
-
Cause: FCNTL system call returned error.
-
Action: Check errno.
-
Cause: AIOWAIT function returned error.
-
Action: Check errno.
-
Cause: There should have been some asynchronous I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be due to an Oracle bug, a vendor OS bug, or an NFS server not responding.
-
Action: Check the Oracle trace file, OS message files, and contact Oracle Support Services.
-
Cause: The number of bytes read/written as returned by AIOWAIT does not match the original number, additional information indicates both these numbers.
-
Action: Check errno.
-
Cause: This is an internal error. A request was made to perform asynchronous I/O when IOV indicates that it cannot be performed on the file.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. A request was made to perform asynchronous vector I/O when it cannot be performed on the file.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. The number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. The buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. The buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: This is an internal error. The range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: AIOREAD/AIOWRITE system call returned error, additional information indicates starting block number of I/O.
-
Action: Check errno.
-
Cause: LSEEK system call returned error, additional information indicates block number in file to which seek was attempted.
-
Action: Check errno.
-
Cause: READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O.
-
Action: Check errno.
-
Cause: This is an internal error. The file is being closed but not all asynchronous I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: GETRLIMIT system call returned error.
-
Action: Check errno.
-
Cause: This is an internal error.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: SETRLIMIT system call returned error.
-
Action: Check errno.
-
Cause: This is an internal error. The number of files opened through SKGFOFI has reached the limit.
-
Action: Check for a trace file and contact Oracle Support Services.
-
Cause: the number of files opened has reached system limit.
-
Action: check error, and set system configuration values.
-
Cause: System call FCNTL with F_GETFL/F_SETFL flag returned error.
-
Action: Check errno.
-
Cause: The file is locked by another process, indicating that it is currently in use by a database instance.
-
Action: Determine which database instance legitimately owns this file.
-
Cause: Share lock request was made on a file not open for read access.
-
Action: File must be open read-only or read-write to get a share lock.
-
Cause: The file is not open or the file descriptor is invalid.
-
Action: Make sure the file is open and the descriptor is valid.
-
Cause: The file lock release failed.
-
Cause: See the errno.
-
Cause: A read/write/readv/writev system call returned error. Additional information indicates the starting block number of the I/O.
-
Action: Check the errno.
-
Cause: An attempt was made to open a file that exceeds the process's file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks).
-
Action: increase the processes file size limit (ulimit) and retry.
-
Cause: An attempt was made to start duplicate instances, or tried to restart an instance that had not been properly shut down.
-
Action: Use a different instance name, or cleanup the failed instance's SGA.
-
Cause: Unable to locate shared memory realm.
-
Action: Verify that the realm is accessible.
-
Cause: Out of memory.
-
Action: Consult the trace file for details.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: SHMCTL() call failed.
-
Action: check permissions on segment, contact Oracle Support Services.
-
Cause: SHMCTL() call failed.
-
Action: check permissions on segment, contact Oracle Support Services.
-
Cause: MPROTECT() call failed.
-
Action: Contact Oracle Support Services.
-
Cause: SHMAT() call failed.
-
Action: Check permissions on segment, contact Oracle Support Services.
-
Cause: SHMDT() call failed.
-
Action: Contact Oracle Support Services.
-
Cause: SHMGET() call failed.
-
Action: Contact Oracle Support Services.
-
Cause: Insufficient privileges to lock shared memory segment in core.
-
Action: Make sure the process is running with the necessary privileges.
-
Cause: Insufficient privileges to unlock shared memory segment.
-
Action: Make sure the process is running with the necessary privileges.
-
Cause: SYSCONF() call failed.
-
Action: Contact Oracle Support Services.
-
Cause: Process operation attempted using invalid process ID.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Check errno and if possible increase the number of processes.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: This is an internal error. A request was made for a conversion too large for the type.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: This is an internal error. Multiple post/wait creates were attempted simultaneously.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Operating system call failed.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The post/wait facility for which the calling process is awaiting action was removed from the system.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: SBTREAD2 returned an error. This happens while reading a backup file during a restore operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTINFO2 returned an error. This happens while retrieving backup file information from the media manager's catalog.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTCLOSE2 returned an error. This happens while closing a backup file during a backup or restore operation.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTINFO2 did not return the volume label information for the backup file that was just created. This is an internal error in the media management product.
-
Action: Contact the media management vendor.
-
Cause: SBTCOMMAND returned an error. This happens when an RMAN SEND command is issued.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.
-
Action: Rerun the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy.
-
Cause: SBTPCBACKUP returned an error. This happens when a proxy backup is begun.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCRESTORE returned an error. This happens when a proxy restore is begun.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCVALIDATE returned an error. This happens during a proxy backup or restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCSTATUS returned an error. This happens during a proxy backup or restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCSTART returned an error. This happens during a proxy backup or restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCCOMMIT returned an error. This happens during a proxy backup or restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCEND returned an error. This happens during a proxy backup or restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCQUERYBACKUP returned an error. This happens during a proxy backup.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCQUERYRESTORE returned an error. This happens during a proxy restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: SBTPCCANCEL returned an error. This happens during a proxy restore.
-
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
-
Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.
-
Action: Retry the command with a different file.
-
Cause: User-supplied PARMS value has incorrect syntax.
-
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
-
Cause: User-supplied PARMS value has incorrect syntax.
-
Action: Retry the command with the correct syntax: ENV=(var1=val1,var2=val2,..)
-
Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword.
-
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
-
Cause: User-supplied PARMS value has incorrect syntax.
-
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
-
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for the error code.
-
Action: Retry the command with proper media library. Or re-install Media management module for Oracle.
-
Cause: Media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, or sbtinit.
-
Action: Retry the command with proper media library.
-
Cause: The dlclose for media library returned an error. See Additional information for the error code.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system call error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the extra information and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: This is an operating system/cluster interconnect error.
-
Action: Check the value of errno and contact Oracle Support Services.
-
Cause: A misconfiguration or installation error occurred.
-
Action: Install the IPC library for this release of Oracle.
-
Cause: This is an operating system-dependent IPC error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an operating system-dependent IPC error.
-
Action: Contact Oracle Support Services.
-
Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the database administrator has locked the account.
-
Action: Wait for PASSWORD_LOCK_TIME or contact the database administrator.
-
Cause: The user's account has expired and the password needs to be changed.
-
Action: Change the password or contact the database administrator.
-
Cause: The user's account is about to about to expire and the password needs to be changed.
-
Action: Change the password or contact the database administrator.
-
Cause: The new password did not meet the necessary complexity specifications and the PASSWORD_VERIFY_FUNCTION failed.
-
Action: Enter a different password. Contact the database administrator to find out the rules for choosing the new password.
-
Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument.
-
Action: Check the Oracle9i Security Overview to find out the format of the password verification function.
-
Cause: The flags are not properly set or conflicting flags are set in making calls.
-
Action: Call the function with appropriate flags set.
-
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set.
-
Action: Set one value to UNLIMITED explicitly.
-
Cause: The password cannot be reused for the specified number of days or for the specified number of password changes.
-
Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement.
-
Cause: Old password supplied is wrong; Hence user cannot be authenticated using old password.
-
Action: Supply the correct old password for authentication.
-
Cause: Connect sys/password is no longer a valid syntax.
-
Action: Try connect sys/password as sysdba or connect sys/password as sysoper.
-
Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired.
-
Action: Try to expire the password of the user that has database password.
-
Cause: The user's account is marked for expire; the expiry period is unlimited.
-
Action: Change the password or contact the DBA.
-
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
-
Action: Use only one IDENTIFIED GLOBALLY clause.
-
Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.
-
Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority.
-
Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles.
-
Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee.
-
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role.
-
Action: Use REVOKE to revoke the role from other users or roles first.
-
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted; these must be revoked, since external roles cannot be granted to global users or roles.
-
Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed.
-
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
-
Action: Provide a valid external name.
-
Cause: The external name specified for the user being created or altered already exists for another user.
-
Action: External names must be unique among users. Specify another.
-
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
-
Action: Either change the user to a global user or try to use a different database link.
-
Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.
-
Action: Consult the network security service documentation on how to properly configure the remote server.
-
Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.
-
Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access.
-
Cause: Unable to access LDAP directory service.
-
Action: Contact your system administrator.
-
Cause: Client and server cannot negotiate shared secret during logon.
-
Action: Contact your system administrator.
-
Cause: The schema was dropped after the policy associated with the function had been added to the object.
-
Action: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user.
-
Cause: A policy with the same name for the same object already exists.
-
Action: Check if the policy has already been added or use a different policy name.
-
Cause: Try to drop/enable/refresh a non-existent policy.
-
Action: Correct the policy name argument.
-
Cause: Try to add a policy to a table or a view owned by SYS.
-
Action: You cannot perform this operation.
-
Cause: The function or package implementing a policy does not exist or was created with errors.
-
Action: Correct the function or package.
-
Cause: Input values for the argument is missing or invalid.
-
Action: Correct the input values.
-
Cause: Try to flush a disabled policy.
-
Action: If the policy is supposed to be enforced, it must be enabled.
-
Cause: Policies for the same object reference each other.
-
Action: Drop the policies.
-
Cause: Too many policies are involved in the same objects.
-
Action: Drop one or more policies. Or combine a few of them into one.
-
Cause: The policy function may have been dropped, or is no longer valid.
-
Action: Check the status of the function and correct the problem. Or re-create the policy with a valid function.
-
Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access.
-
Action: Grant appropriate privileges to the policy function owner.
-
Cause: The policy function has one or more error during execution.
-
Action: Check the trace file and correct the errors.
-
Cause: Policy function generates invalid predicate.
-
Action: Review the trace file for detailed error information.
-
Cause: Policy predicate was evaluated to FALSE with the updated values.
-
Action: Check the trace file and correct the errors.
-
Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.
-
Action: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully.
-
Cause: tried to update/insert a child record with new foreign key values, but the corresponding parent row was not visible because of fine-grained security in the parent.
-
Action: make sure that the updated foreign key values are visible in the parent.
-
Cause: tried to create a policy group that already exists.
-
Cause: tried to drop a policy group that does not exist.
-
Cause: tried to create a driving context that already exists.
-
Cause: tried to drop a driving context that does not exist.
-
Cause: Merge into syntax currently does not support a security policy on the destination table.
-
Action: use the insert / update DML stmts on the table that has a security policy defined on it.
-
Cause: The user is not SYS and doesn't have full table access due to VPD policies. This only happens for internal DML/query under a DDL.
-
Action: Grant the appropriate privilege or contact Oracle Support Services if this is too restrictive.
-
Cause: Only tables, views, or synonyms of tables or views may have VPD policies.
-
Action: No action required.
-
Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.
-
Action: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER... GRANT CONNECT command.
-
Cause: More than one user name was specified for an ALTER USER command.
-
Action: Try the command again with only one user name.
-
Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role.
-
Action: Change the proxy user so that it does not specify the role or grant the role to the client.
-
Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid.
-
Action: Connect again as the client specifying a valid role.
-
Cause: A proxy user cannot assume the identity of a privileged user in order to limit the privileges that a proxy can possess.
-
Action: Execute the statement again, specifying a client other than a privileged user.
-
Cause: A user specified in an AUDIT operation BY proxy ON BEHALF OF client is actually a role.
-
Action: Execute the statement again with a valid proxy user.
-
Cause: A proxy user has not been granted the right to use a role on behalf of a client.
-
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
-
Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER client GRANT CONNECT THROUGH proxy WITH ALL ROLES EXCEPT role.
-
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
-
Cause: Keyword missing.
-
Action: Provide missing keyword.
-
Cause: Keyword missing.
-
Action: Provide missing keyword.
-
Cause: Keyword missing.
-
Action: Provide missing keyword.
-
Cause: Keyword missing.
-
Action: Provide missing keyword.
-
Cause: Keyword missing.
-
Action: Provide missing keyword.
-
Cause: The GRANT clause was specified twice.
-
Action: Use only one GRANT clause.
-
Cause: The REVOKE clause was specified twice.
-
Action: Use only one REVOKE clause.
-
Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed.
-
Action: Attempt to activate a different role or change the role administratively so that there is no password.
-
Cause: The name of a role was specified more than once in a list.
-
Action: Repeat the command specifying the role once.
-
Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client.
-
Action: Either specify a role that does not have a password or alter the role so that a password is not required.
-
Cause: The type of certificate from which the server is to extract the credentials of the client is not supported.
-
Action: Specify a supported type.
-
Cause: The version of the certificate from which the server is to extract the credentials of the client is not supported.
-
Action: Specify a supported version.
-
Cause: The version of the Kerberos ticket which the server is to use to validate the identity of the client is not supported.
-
Action: Specify a supported version.
-
Cause: A client user is to be identified using a distinguished name, but none was provided by the proxy user.
-
Action: Provide a distinguished name.
-
Cause: A client user is to be identified using a certificate but none was provided by the proxy user.
-
Action: Provide a certificate.
-
Cause: A client user is to be authenticated using a Kerberos ticket but none was provided by the proxy user.
-
Action: Provide a Kerberos ticket.
-
Cause: the type of certificate provided by the proxy user to identify a client user does not match the type that is required.
-
Action: Provide a certificate of the correct type.
-
Cause: The version of the certificate provided by the proxy user to identify a client user does not match the version that is required.
-
Action: Provide a certificate of the correct version.
-
Cause: the version of the Kerberos ticket provided by the proxy user to authenticate a client user does not match the version that is required.
-
Action: Provide a Kerberos ticket of the correct version.
-
Cause: A client user is to be authenticated using a database password but none was provided by the proxy user.
-
Action: Provide a password.
-
Cause: No user name was provided by the proxy user for the client user.
-
Action: Either specify a client database user name, a distinguished name or an X.509 certificate.
-
Cause: More than one authentication method was specified by the proxy user for the client user.
-
Action: Specify only one of the following:
-
Cause: The IDENTIFIED USING clause was specified twice.
-
Action: Use only one IDENTIFIED USING clause.
-
Cause: An attempt to enable application role outside the scope of the designated package.
-
Action: Enable the role directly or indirectly using the designated package.
-
Cause: User is changing password but password verification function is turned on, the original password is not specified, and the user does not have the alter user system privilege.
-
Action: Supply the original password.
-
Cause: A NULL value was passed to a function or procedure.
-
Action: Make sure that the data passed is not empty.
-
Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes.
-
Action: Make sure that the length of the data to be encrypted or decrypted is a multiple of 8 bytes.
-
Cause: The obfuscation toolkit does not support the encryption of already-encrypted data.
-
Action: Do not attempt to encrypt already-encrypted data.
-
Cause: The key specified is too short for the algorithm. DES requires a key of at least 8 bytes. Triple DES requires a key of at least 16 bytes in two-key mode and 24 bytes in three-key mode.
-
Action: Specify a longer key.
-
Cause: The desired encryption algorithm is not available.
-
Action: Run the installer to install the needed algorithm in Oracle Advanced Security.
-
Cause: An unknown value was specified for the mode in which triple DES encryption is to run.
-
Action: Specify a valid value. See the package declaration for a list of valid values.
-
Cause: The seed specified for the key generation routine must be at least 80 characters.
-
Action: Specify a longer seed.
-
Cause: A NULL value was passed in as the seed to be used in generating a key.
-
Action: Provide a non-NULL value for the seed.
-
Cause: A NULL value was passed in as an encryption or decryption key.
-
Action: Provide a non-NULL value for the key.
-
Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL interface.
-
Action: Use a SQL statement to query CURRENT_USER inside a DR procedure.
-
Cause: Initialization parameter GLOBAL_CONTEXT_POOL_SIZE has a value less than the minimum required value (10K).
-
Action: Specify a value for the initialization parameter GLOBAL_CONTEXT_POOL_SIZE that is atleast 10k.
-
Cause: Allocations for the global context heap exceeded the value set in the initialization parameter file.
-
Action: Increase the value of the GLOBAL_CONTEXT_POOL_SIZE initialization parameter or clear unused global context.
-
Cause: The length of the client identifier is longer than 64.
-
Action: Set a client identifier whose length is less than 64.
-
Cause: Namespace beginning with 'sys_' is not allowed.
-
Action: Use a namespace that does not begin with 'sys_'.
-
Cause: An attempt to login as password-auuthenticated global user with a malformed user nickname.
-
Action: Make sure the nickname is valid and re-login.
-
Cause: ORACLE server does not have read permission on user nickname's X.500 user entry.
-
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are correct.
-
Cause: Domain policy does not allow password-authenticated GLOBAL users.
-
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure orclDBAuthTypes attributes within Oracle enterprise domain object is either set to PWD or ALL.
-
Cause: ORACLE server cannot map the given user nickname to LDAP distinguished name.
-
Action: Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values.
-
Cause: LDAP user entry corresponding to user nickname does not have a ORACLE password attribute or the attribute is not initialized.
-
Action: Make sure user entries in LDAP are correctly provisioned with correct ORACLE password attribute values.
-
Cause: The given user nickname maps to more than one LDAP distinguished name.
-
Action: Make sure user nickname is unique within the enterprise.
-
Cause: The ORACLE password attribute of a user entry has an invalid format.
-
Action: Make sure ORACLE password attribute value is RFC-2307 compliant.
-
Cause: The LDAP search for finding the appropriate user entry and ORACLE password failed.
-
Action: Make sure LDAP directory service is up and running.
-
Cause: No policy about password authenticated GLOBAL users has been registered.
-
Action: Add attribute orclDBAuthTypes to the database server's Enterprise domain.
-
Cause: The initialization parameter RDBMS_SERVER_DN is not specified corrrectly (cannot be normalized).
-
Action: Make sure the RDBMS_SERVER_DN initialization parameter is set to a correct value.
-
Cause: The ORACLE password attribute of a user entry has multiple entries of ORACLE database password.
-
Action: Make sure ORACLE password attribute has one entry for ORACLE Database password.
-
Cause: The cause is explained in the forwarded message.
-
Action: See the non-Oracle system's documentation of the forwarded message.
-
Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.
-
Action: See the documentation for the non-Oracle system for an explanation of the second error message.
-
Cause: A communication error internal to Oracle's heterogeneous services has occurred.
-
Action: Contact Oracle Support Services.
-
Cause: A SQL statement used bind variables on a Heterogeneous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables.
-
Action: Change your SQL statement so that it does not use bind variables.
-
Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache.
-
Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the HS_ROWID_CACHE_SIZE Heterogenious Services initialization parameter.
-
Cause: Oracle was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
-
Action: Contact the database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
-
Cause: A reference to an Oracle data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The Oracle data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation.
-
Action: Contact customer support of the agent vendor.
-
Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect.
-
Action: Verify correct installation of the following Heterogeneous Services' initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory.
-
Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system.
-
Action: Check the Heterogeneous Services and agent documentation to determine acceptable values.
-
Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.
-
Action: Check the Net8 service name definition in the following places:
- the USING clause of the CREATE DATABASE LINK statement
- the TNSNAMES.ORA file
- the Oracle Names Server
The following are possible reasons for name mismatches:
- The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server.
- The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener.
- The SID=name in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener.
-
Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.
-
Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly.
-
Cause: A fatal error occurred in one of the following places:
- the connection between the Oracle server and the agent
- the heterogeneous services remote agent itself
- the connection to the non-Oracle system
This error occurred after communication had been established successfully.
-
Action: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact customer support of the agent vendor.
-
Cause: Oracle was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views.
-
Action: Ask your database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
-
Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.
-
Action: Make a note of how the error was produced and contact customer support of the agent vendor.
-
Cause: The system date was not retrievable.
-
Action: Verify that the Oracle server's host machine and operating system are operational. This error should not occur unless low level system functions are failing.
-
Cause: Oracle was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed.
-
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory.
-
Cause: A data dictionary translation definition, either in the Oracle server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the Oracle instance and to the Oracle instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an Oracle server on the first connection from the server to the agent.
-
Action: Contact the customer support of the agent vendor.
-
Cause: The Oracle server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
-
Action: Ask a database administrator to resolve this problem. The easiest solution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
-
Cause: Oracle was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
-
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
-
Cause: The Oracle server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
-
Action: Ask a database administrator to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
-
Cause: Oracle was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
-
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
-
Cause: An operation on a database link attempted to connect to a non-Oracle system, but the Oracle instance and the agent process for the non-Oracle system are incompatible.
-
Action: Ask your database administrator to confirm configuration of both the Oracle instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the Oracle instance and the agent, and in the Oracle instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported.
-
Cause: Incorrect arguments were passed into the error message creation routine.
-
Action: Contact Oracle Support Services.
-
Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.
-
Action: Contact customer support of the agent vendor.
-
Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the Oracle server's data dictionary.
-
Action: Verify that the Oracle server's data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact customer support of the agent vendor.
-
Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for the conversion failure:
-
Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value.
-
Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server.
-
Action: Ask your database administrator to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's documentation.
-
Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the Oracle server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs.
-
Action: Contact Oracle Support Services.
-
Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions.
-
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
-
Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled.
-
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
-
Cause: A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver.
-
Action: Contact customer support of the agent vendor.
-
Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the Oracle server data dictionary.
-
Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one.
-
Cause: The client program tried fetching from a result set that is no longer open. Many gateways will, on execution of a stored procedure, automatically close all result sets that were returned by any previously executed stored procedure.
-
Action: Check the documentation for the gateway that you are using and see if it will automatically close currently open result sets each time a stored procedure is executed. Then check if your client program is violating this rule. If it is, fix your program. If it is not, contact Oracle Support Services.
-
Cause: The client program tried executing a stored procedure that returns one or more result sets through a gateway that does not have result set support.
-
Action: Check the documentation for the gateway that you are using and see if it supports result sets returned from stored procedures. If it does not, then the only way of accessing such stored procedures is to upgrade to a version of the gateway that does support result sets (if such a version exists). If the gateway does have result set support and you are still seeing this error, contact Oracle Support Services.
-
Cause: A syntax error occurred in the gateway initialization file.
-
Action: Check the gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file.
-
Cause: Reading the gateway init file generated an error.
-
Action: Check the gateway initialization file name to see that the gateway initialization file acctually exists. Check the ifile parameter to see that it points to the correct location.
-
Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed.
-
Action: Check if the listener used to connect to the gateway is up and is correctly configured. Make sure that the database link used has been configured correctly and, if a tnsnames alias has been used in the database link definition, make sure that the configuration of the entry in tnsnames.ora has been done correctly.
-
Cause: Net8 reported a failure to make a RSLV connection or a protocol mode error when the Oracle database server attempted to establish communication with a Heterogeneous Services agent or an external procedure agent. This usually is due to an administration error in setting up Net8 service definitions in TNSNAMES.ORA or LISTENER.ORA: A basic network connection is opened, but it connects to a program which does not use the appropriate protocol. This often is a sign that the connection goes to the wrong program.
-
Action: Check Net8 administration in the following ways:
- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
- Check LISTENER.ORA on the agent's host machine to assure that the service name or SID refers to the correct agent executable in its (PROGRAM=...) clause.
- Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
-
Cause: An attempt to call an external procedure or to issue SQL to a non-Oracle system on a Heterogeneous Services database link failed at connection initialization. The error diagnosed by Net8 NCR software is reported separately.
-
Action: Refer to the Net8 NCRO error message. If this isn't clear, check connection administrative setup in tnsnames.ora and listener.ora for the service associated with the Heterogeneous Services database link being used, or with 'extproc_connection_data' for an external procedure call.
-
Cause: A failure occurred during initialization of a network connection from the Oracle database server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are:
- Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent.
- Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle database server.
- The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent.
- Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=).
- Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=).
-
Action: Check Net8 administration in the following ways:
- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
- Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID connects to the correct program.
- Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
-
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
-
Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call.
-
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
-
Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system.
-
Cause: A pass-through SQL function was called in an invalid order.
-
Action: Correct program flow by changing the order of API calls to match the flow described in the manual.
-
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
-
Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.
-
Cause: The maximum number of open cursors has been exceeded.
-
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.
-
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
-
Action: Use a non-NULL value for the parameter.
-
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
-
Action: Contact the database administrator for the non-Oracle system. The database administrator can grant permission to access the privileged table or columns.
-
Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. Oracle requires these names to configure the heterogeneous database link.
-
Action: Contact the database administrator to check setup of the connection and the Heterogeneous Services agent.
-
Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the Oracle server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed.
-
Action: Contact your database administrator to verify correct setup of an HS_FDS_CONNECT_STRING entry in the Oracle Heterogeneous Services data dictionary.
-
Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the Oracle data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store.
-
Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check Oracle data dictionary contents when necessary to diagnose the cause of the associated error.
-
Cause: An Oracle server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable.
-
Action: Check Net8 administration in the following ways:
-
Cause: Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system.
-
Action: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent.
-
Cause: Initialization of a network connection to the external procedure agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code.
-
Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server.
-
Cause: A fatal error occurred in either an RPC network connection, the external procedure agent, or the invoked 3GL after communication had been established successfully.
-
Action: First check the 3GL code you are invoking; the most likely cause of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact Oracle Support Services.
-
Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected.
-
Action: Check your documentation for the supported datatypes of external procedure arguments.
-
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
-
Action: Contact Oracle Support Services.
-
Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
-
Action: Contact Oracle Support Services.
-
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
-
Action: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, and so on.
-
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
-
Action: Contact Oracle Support Services.
-
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.
-
Action: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent.
-
Cause: A Heterogeneous Services agent issued a callback to the Oracle database server which attemted to access a remote system. This is not supported.
-
Action: Make sure that SQL code issued by Heterogeneous Services agents does not reference a database link.
-
Cause: The apply slave process encountered an error while trying to apply changes through a gateway to a non-Oracle system.
-
Action: Make sure that the apply database link is correctly configured and that the gateway listener and the non-Oracle system are correctly set up and are up and running. If everything is configured correctly and the problem still occurs, then contact Oracle Support Services.
-
Cause: The user has issued an unrecognized or syntactically incorrect command.
-
Action: Refer to documentation and correct the syntax of the command.
-
Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its ADMIN directory or because permissions on directory were not correctly set.
-
Action: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to.
-
Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail.
-
Action: Issue the command SET AGENT_SID value and then retry the command that failed.
-
Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shut down an agent that is no longer running.
-
Action: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shut down first by issuing the SHUTDOWN command.
-
Cause: The user tried to set or unset an invalid agent parameter.
-
Action: Refer to documentation and correct the parameter name.
-
Cause: User did not type this alter table table_name MINIMIZE RECORDS_PER_BLOCK or alter table table_name NOMINIMIZE RECORDS_PER_BLOCK.
-
Action: Re-enter correct SQL command.
-
Cause: Table has bitmap indexes and user is minimizing or nominalizing RECORDS_PER_BLOCK.
-
Action: Drop all bitmap indexes before changing RECORDS_PER_BLOCK.
-
Cause: Table is empty and statement does not work on empty tables.
-
Action: Try statement after loading your data.
-
Cause: The table has one or more blocks that exceed the maximum number of rows expected when creating a bitmap index. This is probably due to deleted rows. The values in the message are: (data block address, slot number found, maximum slot allowed)
-
Action: Defragment the table or block(s). Use the values in the message to determine the FIRST block affected (there may be others).
-
Cause: An attempt was made to create reverse bitmap index. This is not supported.
-
Action: No action required.
-
Cause: Validate Index detected bitmap corruption in its argument index.
-
Action: Drop this bitmap index and create a new one.
-
Cause: An attempt was made to issue alter index rebuild on IOT-TOP.
-
Action: Use Alter table MOVE to reorganize the table(IOT).
-
Cause: An attempt was made to mark IOT-TOP unusable through ALTER INDEX.
-
Action: Remove the option UNUSABLE.
-
Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING.
-
Action: Remove the illegal option(s).
-
Cause: An attempt was made to exchange a non-IOT table/partition with a partition/table respectively.
-
Action: Ensure that non-partitioned and partitioned tables are both index-organized.
-
Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one does not.
-
Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does.
-
Cause: Syntax error.
-
Action: Check the syntax.
-
Cause: The attribute specification is not done for all partitions.
-
Action: Specify the storage attributes either for ALL partitions or NONE.
-
Cause: Attempt to perform some IOT specific operation on a non-IOT. This is not supported.
-
Action: No action required.
-
Cause: An attempt was made to specify COMPRESS at the partition level without first specifying it at the table level.
-
Action: Specify COMPRESS at the table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ...
-
Cause: An attempt was made to MOVE a partitioned index-organized table as a whole. This is not supported.
-
Action: Do not try to MOVE a partitioned index-organized table as a whole.
-
Cause: An attempt was made to specify COMPRESS for an index-organized table/index which already has a compression clause. This attribute can only be specified at creation time.
-
Action: Do not specify COMPRESS for an index-organized table/index which already has a compression clause.
-
Cause: An attempt was made to specify LOGGING for one segment and NOLOGGING for the other segment.
-
Action: Use the same attribute value for both segments.
-
Cause: An attempt was made to specify LOGGING for an ALTER TABLE ADD OVERFLOW statement.
-
Action: Do not specify LOGGING in this context.
-
Cause: User attempted to coalesce a partitioned IOT using ALTER TABLE COALESCE statement, which is illegal.
-
Action: Coalesce the table a partition at a time (using ALTER TABLE MODIFY PARTITION COALESCE).
-
Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition.
-
Action: Make sure the compression attributes match. If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS.
-
Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s).
-
Action: Build the index without these options.
-
Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required.
-
Action: Remove the USING INDEX clause and specify all attributes directly for the table.
-
Cause: An attempt to directly access the mapping table of an index-organized table.
-
Action: Issue the statement against the parent index-organized table containing the specified mapping table.
-
Cause: User attempted to create a bitmap index on an index-organized table without a mapping table.
-
Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using 'ALTER TABLE ... MOVE MAPPING TABLE'.
-
Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexes.
-
Action: Drop the bitmap index(es) before dropping the mapping table.
-
Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal.
-
Action: Issue a partition level operation with ALTER INDEX ... PARTITION ... UPDATE BLOCK REFERENCES.
-
Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned indexes on a partitioned IOT and a global partitioned index on a non-partitioned IOT.
-
Action: Use online index [partition] rebuild to fix the block references.
-
Cause: User attempted merge operation on an index-organized table. Merge is not supported on an IOT .
-
Action: Use updates and inserts on the index-organized table.
ORA-24280 invalid input value for parameter string
ORA-24281 invalid access past the maximum size of LOB parameter string
ORA-24300 bad value for mode
ORA-24301 null host specified in thread-safe logon
ORA-24302 host connection in use by another thread
ORA-24303 call not supported in non-deferred linkage
ORA-24304 datatype not allowed for this call
ORA-24305 bad bind or define context
ORA-24306 bad buffer for piece
ORA-24307 invalid length for piece
ORA-24308 illegal define position
ORA-24309 already connected to a server
ORA-24310 length specified for null connect string
ORA-24311 memory initialization failed
ORA-24312 illegal parameters specified for allocating user memory
ORA-24313 user already authenticated
ORA-24314 service handle not initialized
ORA-24315 illegal attribute type
ORA-24316 illegal handle type
ORA-24317 define handle used in a different position
ORA-24318 call not allowed for scalar data types
ORA-24319 unable to allocate memory
ORA-24320 unable to initialize a mutex
ORA-24321 inconsistent parameters passed
ORA-24322 unable to delete an initialized mutex
ORA-24323 value not allowed
ORA-24324 service handle not initialized
ORA-24325 this OCI operation is not currently allowed
ORA-24326 handle passed in is already initialized
ORA-24327 need explicit attach before authenticating a user
ORA-24328 illegal attribute value
ORA-24329 invalid character set identifier
ORA-24330 internal OCI error
ORA-24331 user buffer too small
ORA-24332 invalid object type
ORA-24333 zero iteration count
ORA-24334 no descriptor for this position
ORA-24335 cannot support more than 1000 columns
ORA-24336 invalid result set descriptor
ORA-24337 statement handle not prepared
ORA-24338 statement handle not executed
ORA-24339 cannot set server group name after connecting to server
ORA-24340 cannot support more than 255 columns
ORA-24341 bad mode specified
ORA-24342 unable to destroy a mutex
ORA-24343 user defined callback error
ORA-24344 success with compilation error
ORA-24345 A Truncation or null fetch error occurred
ORA-24346 cannot execute without binding variables
ORA-24347 Warning of a NULL column in an aggregate function
ORA-24348 Update or Delete without Where
ORA-24350 OCI call not allowed
ORA-24351 invalid date passed into OCI call
ORA-24352 invalid COBOL display type passed into OCI call
ORA-24353 user buffer too small to accommodate COBOL display type
ORA-24354 number fetched too large to fit in COBOL display type buffer.
ORA-24355 attempt to store a negative number in an Unsigned Display type.
ORA-24356 internal error while converting from to COBOL display type.
ORA-24357 internal error while converting from to OCIDate.
ORA-24358 OCIBindObject not invoked for a Object type or Reference
ORA-24359 OCIDefineObject not invoked for a Object type or Reference
ORA-24360 Type Descriptor Object not specified for Object Bind/Define
ORA-24361 basic bind call not invoked before invoking advanced bind call
ORA-24362 improper use of the character count flag
ORA-24363 measurements in characters illegal here
ORA-24364 internal error while padding blanks
ORA-24365 error in character conversion
ORA-24366 migratable user handle is set in service handle
ORA-24367 user handle has not been set in service handle
ORA-24368 OCI mutex counter non-zero when freeing a handle
ORA-24369 required callbacks not registered for one or more bind handles
ORA-24370 illegal piecewise operation attempted
ORA-24371 data would not fit in current prefetch buffer
ORA-24372 invalid object for describe
ORA-24373 invalid length specified for statement
ORA-24374 define not done before fetch or execute and fetch
ORA-24375 Cannot use V6 syntax when talking to a V8 server
ORA-24376 cannot register/get user callback for non-environment handle
ORA-24377 invalid OCI function code
ORA-24378 user callbacks not allowed for this call
ORA-24379 invalid user callback type
ORA-24380 invalid mode specification
ORA-24381 error(s) in array DML
ORA-24382 statement handled already executed or described
ORA-24383 Overflow segment of an IOT cannot be described
ORA-24384 Application context size is not initialized
ORA-24385 Application context size or index is not valid
ORA-24386 statement/server handle is in use when being freed
ORA-24387 Invalid attach driver
ORA-24388 Unsupported functionality in fast path mode
ORA-24389 Invalid scrollable fetch parameters
ORA-24390 Unsupported scrollable cursor operation
ORA-24391 invalid fetch operation
ORA-24392 no connection pool to associate server handle
ORA-24393 invalid mode for creating connection pool
ORA-24394 invalid mode for destroying connection pool
ORA-24395 cannot reinitialize non-existent pool
ORA-24396 invalid attribute set in server handle
ORA-24397 error occurred while trying to free connections
ORA-24398 connection pool already exists
ORA-24399 invalid number of connections specified
ORA-24400 error occurred while creating connections in the pool
ORA-24401 cannot open further connections
ORA-24402 error occurred while creating connections in the pool
ORA-24403 error occurred while trying to destroy the connection pool
ORA-24404 connection pool does not exist
ORA-24405 error occurred while trying to create connections in the pool
ORA-24406 API mode switch is disallowed when a call is in progress.
ORA-24407 connection pool already exists
ORA-24408 could not generate unique server group name
ORA-24409 client cannot understand the object
ORA-24410 scrollable cursor max size exceeded
ORA-24411 Session pool already exists.
ORA-24412 Cannot reinitialize non-existent pool
ORA-24413 Invalid number of sessions specified
ORA-24414 Only number sessions could be started.
ORA-24415 Missing or null username.
ORA-24416 Invalid session Poolname was specified.
ORA-24417 Session pool size has exceeded the maximum limit
ORA-24418 Cannot open further sessions.
ORA-24419 Proxy sessions are not supported in this mode.
ORA-24420 OCISessionRelease must be used to release this session.
ORA-24421 OCISessionRelease cannot be used to release this session.
ORA-24422 error occurred while trying to destroy the Session Pool
ORA-24430 Null values for sqltext and key were specified.
ORA-24431 Statement does not exist in the cache
ORA-24432 The statement that was returned is not tagged.
ORA-24433 This statement has already been prepared using OCIStmtPrepare2.
ORA-24434 OCIStmtRelease called before OCIStmtPrepare2.
ORA-24435 Invalid Service Context specified.
ORA-24436 Invalid statement Handle.
ORA-24437 OCIStmtExecute called before OCIStmtPrepare2.
ORA-24438 Invalid Authentication Handle specified.
ORA-24500 invalid UTF16 mode
ORA-24501 invalid UTF16 string passed in
ORA-24502 codepoint length overflows
ORA-24503 codepoint length overflows for piecewise operation
ORA-24504 data length larger than expected
ORA-24505 cannot change character set id on the handle
ORA-24506 invalid attempt to change character set id on env handle
ORA-24507 invalid combination of character set ids
ORA-24750 incorrect size of attribute
ORA-24752 OCI_TRANS_NEW flag must be specified for local transactions
ORA-24753 local transactions cannot be detached
ORA-24754 cannot start new transaction with an active transaction
ORA-24755 OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
ORA-24756 transaction does not exist
ORA-24757 duplicate transaction identifier
ORA-24758 not attached to the requested transaction
ORA-24759 invalid transaction start flags
ORA-24760 invalid isolation level flags
ORA-24761 transaction rolled back
ORA-24762 server failed due to unspecified error
ORA-24763 transaction operation cannot be completed now
ORA-24764 transaction branch has been heuristically committed
ORA-24765 transaction branch has been heuristically rolled back
ORA-24766 transaction branch has been partly committed and aborted
ORA-24767 transaction was read-only and has been committed
ORA-24768 commit protocol error occured in the server
ORA-24769 cannot forget an active transaction
ORA-24770 cannot forget a prepared transaction
ORA-24771 cannot detach, prepare or forget a local transaction
ORA-24772 Cannot mix tightly-coupled and loosely-coupled branches
ORA-24773 invalid transaction type flags
ORA-24774 cannot switch to specified transaction
ORA-24775 cannot prepare or commit transaction with non-zero lock value
ORA-24776 cannot start a new transaction
ORA-24777 use of non-migratable database link not allowed
ORA-24778 cannot open connections
ORA-24779 detach not allowed with open remote cursor
ORA-24780 cannot recover a transaction while in an existing transaction
ORA-24781 branches don't belong to the same global transaction
ORA-24782 Cannot detach from a non-migratable transaction
ORA-24783 Cannot switch non-migratable transactions
ORA-24784 Transaction exists
ORA-24785 Cannot resume a non-migratable transaction
ORA-24786 separated transaction has been completed
ORA-24787 remote cursors must be closed before a call completes
ORA-24788 cannot switch to specified transaction (server type)
ORA-24790 cannot mix OCI_TRANS_RESUME and transaction isolation flags
ORA-24801 illegal parameter value in OCI lob function
ORA-24802 user defined lob read callback error
ORA-24803 illegal parameter value in lob read function
ORA-24804 illegal parameter value in lob write function
ORA-24805 LOB type mismatch
ORA-24806 LOB form mismatch
ORA-24807 LOB form mismatch
ORA-24808 streaming of lob data is not allowed when using lob buffering
ORA-24809 amount specified will not fit in the lob buffers
ORA-24810 attempting to write more data than indicated
ORA-24811 less data provided for writing than indicated
ORA-24812 character set conversion to or from UCS2 failed
ORA-24813 cannot send or receive an unsupported LOB
ORA-24814 operation not allowed for temporary LOBs
ORA-24850 failed to startup shared subsystem
ORA-24851 failed to connect to shared subsystem
ORA-24852 protocol error during statement execution
ORA-24853 failed to connect thread to shared subsystem
ORA-24900 invalid or unsupported mode paramater passed in call
ORA-24901 handles belonging to different environments passed into an OCI call
ORA-24902 invalid subscription name or name-length in subscription handle
ORA-24903 invalid namespace attribute passed into OCI call
ORA-24904 invalid callback attribute passed into OCI call
ORA-24905 invalid recepient protocol attribute passed into OCI call
ORA-24906 invalid recepient attribute passed into OCI call
ORA-24907 invalid pair of callback and recepient protocol attributes
ORA-24908 invalid recipient presentation attribute
ORA-24950 unregister failed, registeration not found
ORA-25000 invalid use of bind variable in trigger WHEN clause
ORA-25001 cannot create this trigger type on views
ORA-25002 cannot create INSTEAD OF triggers on tables
ORA-25003 cannot change NEW values for this column type in trigger
ORA-25004 WHEN clause is not allowed in INSTEAD OF triggers
ORA-25005 cannot CREATE INSTEAD OF trigger on a read-only view
ORA-25006 cannot specify this column in UPDATE OF clause
ORA-25007 functions or methods not allowed in WHEN clause
ORA-25008 no implicit conversion to LOB datatype in instead-of trigger
ORA-25009 Nested table clause allowed only for INSTEAD OF triggers
ORA-25010 Invalid nested table column name in nested table clause
ORA-25012 PARENT and NEW values cannot be identical
ORA-25013 OLD and PARENT values cannot be identical
ORA-25014 cannot change the value of a PARENT reference variable
ORA-25015 cannot perform DML on this nested table view column
ORA-25016 cannot specify column list for insert into nested table view column
ORA-25017 cannot reference NEW ROWID for movable rows in before triggers
ORA-25018 conflicting trigger string already exists
ORA-25019 too much concurrency
ORA-25020 renaming system triggers is not allowed
ORA-25100 TABLESPACE option can only be used with ALTER INDEX REBUILD
ORA-25101 duplicate REBUILD option specification
ORA-25102 PARALLEL option can only be used with ALTER INDEX REBUILD
ORA-25103 NOPARALLEL option can only be used with ALTER INDEX REBUILD
ORA-25104 UNRECOVERABLE option can only be used with ALTER INDEX REBUILD
ORA-25105 RECOVERABLE option can only be used with ALTER INDEX REBUILD
ORA-25106 only one of PARALLEL or NOPARALLEL clause may be specified
ORA-25107 duplicate TABLESPACE option specification
ORA-25108 standby lock name space exceeds size limit of string characters
ORA-25109 standby lock name space has illegal character 'string'
ORA-25110 NOSORT may not be used with a bitmap index
ORA-25111 creation of BITMAP cluster indices is not supported
ORA-25112 maximum number of BITMAP index columns is 30
ORA-25113 GLOBAL may not be used with a bitmap index
ORA-25114 invalid file number specified in the DUMP DATAFILE/TEMPFILE command
ORA-25115 duplicate BLOCK option specification
ORA-25116 invalid block number specified in the DUMP DATAFILE/TEMPFILE command
ORA-25117 MIN/MAX/Block Number expected
ORA-25118 invalid DUMP DATAFILE/TEMPFILE option
ORA-25119 LOGGING/NOLOGGING option already specified
ORA-25120 MINIMUM EXTENT option already specified
ORA-25121 MINIMUM EXTENT value greater than maximum extent size
ORA-25122 Only LOCAL bitmap indexes are permitted on partitioned tables
ORA-25123 Too many components specified in the name.
ORA-25124 Database link name not allowed.
ORA-25125 BUFFER_POOL storage option not allowed
ORA-25126 Invalid name specified for BUFFER_POOL
ORA-25127 RELY not allowed in NOT NULL constraint
ORA-25128 No insert/update/delete on table with constraint (string.string) disabled and validated
ORA-25129 cannot modify constraint (string) - no such constraint
ORA-25130 cannot modify primary key - primary key not defined for table
ORA-25131 cannot modify unique(string) - unique key not defined for table
ORA-25132 UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
ORA-25133 duplicate SINGLE TABLE option specified
ORA-25134 keyword TABLE expected
ORA-25135 cannot use the SINGLE TABLE option
ORA-25136 this cluster can contain only one table
ORA-25137 Data value out of range
ORA-25138 string initialization parameter has been made obsolete
ORA-25139 invalid option for CREATE TEMPORARY TABLESPACE
ORA-25140 string space policy cannot be specified for the string extent management
ORA-25141 invalid EXTENT MANAGEMENT clause
ORA-25142 default storage clause specified twice
ORA-25143 default storage clause is not compatible with allocation policy
ORA-25144 invalid option for CREATE TABLESPACE with TEMPORARY contents
ORA-25145 allocation policy already specified
ORA-25146 EXTENT MANAGEMENT option already specified
ORA-25147 UNIFORM SIZE value greater than maximum extent size
ORA-25148 ONLINE option not permitted
ORA-25149 Columns of UROWID type may not be indexed
ORA-25150 ALTERING of extent parameters not permitted
ORA-25151 Rollback Segment cannot be created in this tablespace
ORA-25152 TEMPFILE cannot be dropped at this time
ORA-25153 Temporary Tablespace is Empty
ORA-25154 column part of USING clause cannot have qualifier
ORA-25155 column used in NATURAL join cannot have qualifier
ORA-25156 old style outer join (+) cannot be used with ANSI joins
ORA-25157 Specified block size string is not valid
ORA-25175 no PRIMARY KEY constraint found
ORA-25176 storage specification not permitted for primary key
ORA-25177 UNRECOVERABLE option not permitted
ORA-25178 duplicate PCTTHRESHOLD storage option specification
ORA-25179 invalid PCTTHRESHOLD storage option value
ORA-25180 PCTTHRESHOLD only valid for certain table organizations
ORA-25181 missing ON keyword for NESTED INDEX
ORA-25182 feature not currently available for index-organized tables
ORA-25183 index-organized table top index segment is in a different tablespace
ORA-25184 column name expected
ORA-25185 index column other than last can not be specified for INCLUDE clause
ORA-25186 INCLUDING clause specified for index-organized table without OVERFLOW
ORA-25187 specified exceptions table form incorrect
ORA-25188 cannot drop/disable/defer the primary key constraint for index-organized tables
ORA-25189 illegal ALTER TABLE option for an index-organized table
ORA-25190 an index-organized table maintenance operation may not be combined with other operations
ORA-25191 cannot reference overflow table of an index-organized table
ORA-25192 invalid option for an index-organized table
ORA-25193 cannot use COMPRESS option for a single column key
ORA-25194 invalid COMPRESS prefix length value
ORA-25195 invalid option for index on an index-organized table
ORA-25196 keyword MOVE in ALTER TABLE MOVE must immediately follow table_name
ORA-25197 an overflow segment already exists for the indexed-organized table
ORA-25198 only range and hash partitioning are supported for index-organized table
ORA-25199 partitioning key of a index-organized table must be a subset of the primary key
ORA-25200 invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
ORA-25201 invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
ORA-25202 invalid value NULL, string should be non-NULL
ORA-25203 invalid value string, DELAY should be non-negative
ORA-25204 invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
ORA-25205 the QUEUE string.string does not exist
ORA-25206 enqueue failed, enqueue to exception queue string.string not permitted
ORA-25207 enqueue failed, queue string.string is disabled from enqueueing
ORA-25208 RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
ORA-25209 invalid value string, EXPIRATION should be non-negative or NEVER
ORA-25210 invalid value for RELATIVE_MSGID, no message in queue with that msgid
ORA-25211 invalid DELAY specified when using sequence deviation
ORA-25212 invalid PRIORITY specified when using sequence deviation
ORA-25213 message with specified RELATIVE_MSGID has been dequeued
ORA-25214 cannot specify delay or expiration for enqueue to exception queue
ORA-25215 user_data type and queue type do not match
ORA-25216 invalid recipient, either NAME or ADDRESS must be specified
ORA-25217 enqueue failed, visibility must be IMMEDIATE for queue string.string
ORA-25218 enqueue failed, delay must be zero for queue string.string
ORA-25219 enqueue failed, sequence deviation not allowed for queue string.string
ORA-25220 enqueue failed, signature not specified for a non-repudiable queue
ORA-25221 enqueue failed, signature specified queue not supporting non-repudiation
ORA-25222 enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
ORA-25223 user_data type used is not supported
ORA-25224 sender name must be specified for enqueue into secure queues
ORA-25225 invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
ORA-25226 dequeue failed, queue string.string is not enabled for dequeue
ORA-25228 timeout or end-of-fetch during message dequeue from string.string
ORA-25229 error on transformation of message string string
ORA-25230 invalid value string, WAIT should be non-negative
ORA-25231 cannot dequeue because CONSUMER_NAME not specified
ORA-25232 duplicate recipients specified for message
ORA-25233 invalid parameter specified for NAVIGATION
ORA-25234 NEXT_TRANSACTION navigation option invalid for queue table string.string
ORA-25235 fetched all messages in current transaction
ORA-25236 buffer too small for user data
ORA-25237 navigation option used out of sequence
ORA-25238 too many recipients specified for message destination string
ORA-25239 message ID not supplied when dequeuing from exception queue string.string
ORA-25240 message ID and dequeue condition/correlation ID specified in dequeue options
ORA-25241 cannot change correlation ID from string to string without FIRST_MESSAGE option
ORA-25242 cannot change subscriber name from string to string without FIRST_MESSAGE option
ORA-25243 CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
ORA-25244 dequeue index key not found, QUEUE string, rowid string
ORA-25245 agent name cannot be specified if address is a single-consumer queue or an exception queue
ORA-25246 listen failed, the address string is an 8.0 style exception queue
ORA-25247 string is not a recipient of specified message
ORA-25248 duplicate agent specified in the agent list
ORA-25249 dequeue failed, dequeue not allowed for queue string.string
ORA-25250 Cannot specify a remote recipient for the message
ORA-25251 exceeded maximum number of recipients for message
ORA-25252 listen failed, the address string is a non-persistent queue
ORA-25253 listen failed, queue string.string is not enabled for dequeue
ORA-25254 time-out in LISTEN while waiting for a message
ORA-25255 incorrect subscription string string
ORA-25256 consumer cannot be specified with a single-consumer queue or an exception queue
ORA-25257 consumer must be specified with a multi-consumer queue
ORA-25258 cannot register for notifications on an 8.0 style exception queue
ORA-25259 cannot specify protocol for agent
ORA-25261 JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
ORA-25262 agent name cannot be NULL if address is a multi-consumer queue
ORA-25263 no message in queue string.string with message ID string
ORA-25264 can't get signature for this queue
ORA-25265 specified signature for a queue which does not support reciever non-repudiation
ORA-25266 didn't try to dequeue by message id with the signature
ORA-25267 didn't specify the signature for a reciever non-repudiable queue
ORA-25268 didn't dequeue in browse mode with get signature option
ORA-25269 can't specify signature with get signature option
ORA-25270 sender info does not match with the actual sender of the message
ORA-25271 queue table not found for the given queue
ORA-25272 Signature does not exist for the given reciever and message id
ORA-25276 table specified is not a queue table
ORA-25277 cannot grant or revoke object privilege on release 8.0 compatible queues
ORA-25278 grantee name cannot be NULL
ORA-25279 dequeue as select not supported before 9.0.0
ORA-25280 complete sender information not provided to non-repudiate sender
ORA-25281 complete reciever information not provided to non-repudiate reciever
ORA-25282 message id not provided for non-repudiation
ORA-25283 either agent's name or address needed for non-repudiation
ORA-25284 Invalid value string for string
ORA-25285 Invalid value string for array_mode
ORA-25286 Invalid number of elements in the message properties array
ORA-25287 Invalid value string, string should be non-negative
ORA-25288 AQ HTTP propagation encountered error, status-code number, string
ORA-25289 Buffer Already Exists
ORA-25290 Cannot complete operation on queue string with existing messages
ORA-25291 Buffer does not exist for the specified queue
ORA-25292 Cannot add buffer on the specified queue
ORA-25293 Remote Recipient Subscribers and buffered operations not possible for Queue string
ORA-25294 Queue string has a buffer
ORA-25295 Subscriber is not allowed to dequeue buffered messages
ORA-25296 Queue Table string has a buffered queue string
ORA-25297 The message options only make sense for buffered messages
ORA-25298 The memory threshold for a queue cannot be negative
ORA-25299 Cannot add buffered subscriber for a non-buffered queue
ORA-25300 Cannot drop buffer for queue with buffered subscribers
ORA-25301 cannot specify recipient list during enqueue
ORA-25302 Operation not possible for non-buffered queue string
ORA-25350 maximum number of concurrent transaction branches exceeded
ORA-25351 transaction is currently in use
ORA-25352 no current transaction
ORA-25353 branch marked for deletion
ORA-25400 must replay fetch
ORA-25401 can not continue fetches
ORA-25402 transaction must roll back
ORA-25403 could not reconnect
ORA-25404 lost instance
ORA-25405 transaction status unknown
ORA-25406 could not generate a connect address
ORA-25407 connection terminated
ORA-25408 can not safely replay call
ORA-25425 connection lost during rollback
ORA-25426 remote instance does not support shared dblinks
ORA-25436 invalid table alias: string
ORA-25437 duplicate table value for table alias: string
ORA-25438 invalid variable name: string
ORA-25439 duplicate variable value for variable: string
ORA-25440 invalid table alias: string
ORA-25441 duplicate column value for table alias: string
ORA-25442 too many column values for table alias: string
ORA-25443 duplicate column value for table alias: string, column number: string
ORA-25444 invalid ROWID: string for table alias: string
ORA-25445 invalid column number: string for table alias: string
ORA-25446 duplicate column value for table alias: string, column: string
ORA-25447 encountered errors during evaluation of rule string.string
ORA-25448 rule string.string has errors
ORA-25461 rule set not specified
ORA-25462 evaluation context not specified
ORA-25463 table alias not specified
ORA-25464 ROWID not specified for table alias: string
ORA-25465 variable name not specified
ORA-25466 data not specified for variable name: string
ORA-25467 table alias not specified
ORA-25468 column name not specified for alias: string
ORA-25469 data not specified for alias: string column name: string
ORA-25500 database is not open
ORA-25501 ALTER SYSTEM QUIESCE RESTRICTED command failed
ORA-25502 concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
ORA-25503 cannot open database because the database is being quiesced
ORA-25504 the system is already in quiesced state
ORA-25505 the system is not in quiesced state
ORA-25506 resource manager has not been continuously on in some instances
ORA-25507 resource manager has not been continuously on
ORA-25508 database is not mounted
ORA-25509 operation on "string"."string".string not allowed
ORA-25526 bad format of _DB_MTTR_SIM_TARGET: string
ORA-25527 bad format of _DB_MTTR_SIM_TARGET
ORA-25528 too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
ORA-25530 FAST_START_MTTR_TARGET is not specified
ORA-25531 MTTR specified is too small: number
ORA-25532 MTTR specified is too large: number
ORA-25950 missing where clause in join index specification
ORA-25951 join index where clause cannot contain OR condition
ORA-25952 join index must only contain inner equi-joins
ORA-25953 join index cannot be a functional index
ORA-25954 missing primary key or unique constraint on dimension
ORA-25955 all tables must be joined in the where clause
ORA-25956 join index cannot be created on tables owned by SYS
ORA-25957 join index where clause cannot contain cycles
ORA-25958 join index where clause predicate may only contain column references
ORA-25959 join index must be of the bitmap type
ORA-25960 join index cannot be based on a temporary table
ORA-25961 join index prevents dml cascade constraint operation
ORA-25962 join index prevents multitable insert or merge
ORA-25963 join index must be created on tables
ORA-25964 column type incompatible with join column type
ORA-26000 partition load specified but table string is not partitioned
ORA-26001 Index string specified in SORTED INDEXES does not exist on table string
ORA-26002 Table string has index defined upon it.
ORA-26003 parallel load not supported for index-organized table string
ORA-26004 Tables loaded through the direct path may not be clustered
ORA-26005 Invalid handle for direct path load
ORA-26006 Incorrect bind variable in column string's sql expression - string
ORA-26007 For INSERT option, table must be empty. Error on table string
ORA-26008 NOT NULL column string has a nullif clause
ORA-26009 NOT NULL column string has a defaultif clause which may evaluate to null
ORA-26010 Column string in table string is NOT NULL and is not being loaded
ORA-26011 Cannot load type string into column string in table string
ORA-26012 No data found while executing sql statement string for column string - check input for: string
ORA-26013 List allocated may not be big enough
ORA-26014 OCI_ATTR_DIRPATH_SUBST_OBJ_TBL is set for non-final object table string
ORA-26015 Array column string in table string is not supported by direct path
ORA-26016 Record string: Rejected - Error on table string, partition string
ORA-26017 Global indexes not allowed on direct path partition load, table string
ORA-26018 Column string in table string does not exist
ORA-26019 Column string in table string of type string not supported by direct path
ORA-26020 index string.string loaded successfully with string keys
ORA-26021 index string.string partition string loaded successfully with string keys
ORA-26022 index string.string was made unusable due to:
ORA-26023 index string.string partition string was made unusable due to:
ORA-26024 SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
ORA-26025 SKIP_INDEX_MAINTENANCE option requested
ORA-26026 unique index string.string initially in unusable state
ORA-26027 unique index string.string partition string initially in unusable state
ORA-26028 index string.string initially in unusable state
ORA-26029 index string.string partition string initially in unusable state
ORA-26030 index string.string had string partitions made unusable due to:
ORA-26031 index maintenance error, the load cannot continue
ORA-26032 index string.string loading aborted after string keys
ORA-26033 error while evaluating index string.string, row string due to:
ORA-26034 end of logical record found when reading length of varying length field
ORA-26035 Record string: Rejected - Error on table string, subpartition string
ORA-26036 subpartition load specified but table string is not subpartitioned
ORA-26037 Record string: Rejected - Error on table string, subpartition string
ORA-26038 error converting character length field to a number
ORA-26039 Table string has domain index defined upon it
ORA-26040 Data block was loaded using the NOLOGGING option
ORA-26041 DATETIME/INTERVAL datatype conversion error
ORA-26042 unable to convert format string into internal form
ORA-26043 unable to convert time zone for DATETIME/INTERVAL processing
ORA-26044 unable to to get DATETIME/INTERVAL reference date
ORA-26045 REF column string expects string arguments; found string.
ORA-26046 REF column string expects scoped table name string; user passed in string.
ORA-26047 REF column has invalid value for system generated oid
ORA-26048 Scoped REF column has wrong table name.
ORA-26049 Unscoped REF column has non-existent table name.
ORA-26050 Direct path load of domain index is not supported for this column type.
ORA-26051 internal error parsing packed decimal format string
ORA-26052 Unsupported type number for SQL expression on column string.
ORA-26076 cannot set or reset value after direct path structure is allocated
ORA-26077 direct path column array is not initialized
ORA-26078 file string is not part of database being loaded
ORA-26079 file string is not part of table string.string
ORA-26080 file string is not part of table string.string partition string
ORA-26081 load stream synchronization error
ORA-26082 load of overlapping segments on table string.string is not allowed
ORA-26084 direct path context already finished
ORA-26085 direct path operation must start its own transaction
ORA-26086 direct path does not support triggers
ORA-26087 direct path does not support referential constraints
ORA-26088 scalar column 'string' must be specified prior to LOB columns
ORA-26089 LONG column 'string' must be specified last
ORA-26090 row is in partial state
ORA-26091 requested direct path operation not supported
ORA-26092 only LONG or LOB types can be partial
ORA-26093 stream offset does not map to a column array
ORA-26094 stream format error: input column overflow
ORA-26095 unprocessed stream data exists
ORA-26096 transfer size too small for row data (number bytes required)
ORA-26097 unsupported conversion for column string (from type number to type number)
ORA-26098 direct path context is not prepared
ORA-26099 direct path context is already prepared
ORA-26100: unused error
ORA-26101 tablespace # in file header is string rather than string for file string
ORA-26102 relative file # in file header is string rather than string for file string
ORA-26103 V6 or V7 data file used to create control file
ORA-26500 error on caching "string"."string"
ORA-26501 RepAPI operation failure
ORA-26502 error resignal
ORA-26503 internal RepAPI operation failure on object string.string
ORA-26504 operation not implemented
ORA-26505 unexpected internal null
ORA-26506 null global context
ORA-26507 null master connection
ORA-26508 null materialized view connection
ORA-26509 null materialized view control structure
ORA-26510 materialized view name: 'string' is greater than max. allowed length of string bytes
ORA-26511 master table 'string.string' not found
ORA-26512 error pushing transaction to def$error
ORA-26513 push error: master proc. string$RP.string failed for trans:string seq:string
ORA-26514 object 'string.string' not found
ORA-26515 no master log available for 'string.string'
ORA-26516 no push transaction acknowledgement
ORA-26517 materialized view control entry for 'string.string' was not found
ORA-26518 push queue synchronization error detected
ORA-26519 no memory available to allocate
ORA-26520 internal memory failure
ORA-26521 rpc initialization error
ORA-26522 rpc execution error
ORA-26523 rpc termination error
ORA-26524 nls subsystem initialization failure for product=string, facility=string
ORA-26525 session connection attempt failed for string (@string)
ORA-26526 materialized view sql ddl parse/expansion failed for string.string
ORA-26527 local store callback init phase failed for 'string.string'
ORA-26528 local store callback proc phase failed for 'string.string'
ORA-26529 local store callback term phase failed for 'string.string'
ORA-26530 unable to build materialized view refresh control list
ORA-26532 replication parallel push simulated site failure
ORA-26534 collision: tranID number ignored and purged
ORA-26535 number byte row cache insufficient for table with rowsize=number
ORA-26536 refresh was aborted because of conflicts caused by deferred transactions
ORA-26563 renaming this table is not allowed
ORA-26564 string argument is not of specified type
ORA-26565 Call to type_arg made before calling dbms_defer.call
ORA-26566 Couldn't open connect to string
ORA-26571 string.string.string: number of arguments (string) does not match replication catalog
ORA-26572 string.string.string: argument string does not match replication catalog
ORA-26575 remote database does not support replication parallel propagation
ORA-26650 string background process string might not be started successfully
ORA-26660 Invalid action context value for string
ORA-26665 STREAMS process string already exists
ORA-26666 cannot alter STREAMS process string
ORA-26667 invalid STREAMS parameter string
ORA-26669 parameter string inconsistent with parameter string
ORA-26670 STREAMS option requires COMPATIBLE parameter to be string or higher
ORA-26671 maximum number of STREAMS processes exceeded
ORA-26672 timeout occurred while stopping STREAMS process string
ORA-26680 object type not supported
ORA-26681 command type not supported
ORA-26682 invalid value for publication_on
ORA-26683 invalid value for value_type
ORA-26684 invalid value for value_type
ORA-26685 cannot apply transactions from multiple sources
ORA-26686 cannot capture from specified SCN
ORA-26687 no instantiation SCN provided
ORA-26688 missing key in LCR
ORA-26689 column datatype mismatch in LCR
ORA-26690 datatype not supported at non-Oracle system
ORA-26691 operation not supported at non-Oracle system
ORA-26701 STREAMS process string does not exist
ORA-27000 skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-27001 unsupported device type
ORA-27002 function called with invalid device structure
ORA-27003 cannot open file on device allocated with NOIO option
ORA-27004 invalid blocksize specified
ORA-27005 cannot open file for async I/O on device not supporting async
ORA-27006 sbtremove returned error
ORA-27007 failed to open file
ORA-27008 function called with invalid file structure
ORA-27009 skgfwrt: cannot write to file opened for read
ORA-27010 skgfwrt: write to file failed
ORA-27011 skgfrd: cannot read from file opened for write
ORA-27012 skgfrd: read from file failed
ORA-27013 skgfqdel: cannot delete an open file
ORA-27014 skgfqpini: translation error while expanding SS_UDMPDIR
ORA-27015 skgfcls: failed to close the file
ORA-27016 skgfcls: sbtinfo returned error
ORA-27017 skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
ORA-27018 BLKSIZE is not a multiple of the minimum physical block size
ORA-27019 tape filename length exceeds limit (SBTOPMXF)
ORA-27020 named devices not supported
ORA-27021 sequential file handle must be specified
ORA-27022 skgfqsbi: could not allocate memory for media manager
ORA-27023 skgfqsbi: media manager protocol error
ORA-27024 skgfqsbi: sbtinit2 returned error
ORA-27025 skgfqsbi: invalid media manager context area size
ORA-27026 skgfrls: sbtend returned error
ORA-27027 sbtremove2 returned error
ORA-27028 skgfqcre: sbtbackup returned error
ORA-27029 skgfrtrv: sbtrestore returned error
ORA-27030 skgfwrt: sbtwrite2 returned error
ORA-27031 mirror resilvering functions not supported
ORA-27032 skgfrpini: failed to obtain file size limit
ORA-27033 skgfrpini: failed to obtain file size limit
ORA-27034 skgfrcre: maximum length of ORACLE_SID exceeded
ORA-27035 logical block size is invalid
ORA-27036 translation error, unable to expand file name
ORA-27037 unable to obtain file status
ORA-27038 skgfrcre: file exists
ORA-27039 create file failed, file size limit reached
ORA-27040 skgfrcre: create error, unable to create file
ORA-27041 unable to open file
ORA-27042 not enough space on raw partition to fullfill request
ORA-27043 unable to seek to beginning of file
ORA-27044 unable to write the header block of file
ORA-27045 unable to close the file
ORA-27046 file size is not a multiple of logical block size
ORA-27047 unable to read the header block of file
ORA-27048 skgfifi: file header information is invalid
ORA-27049 unable to seek to and read the last block
ORA-27050 function called with invalid FIB/IOV structure
ORA-27052 unable to flush file data
ORA-27053 skgfifi: blocksize in file header not a multiple of logical block size
ORA-27056 skgfrdel: could not delete file
ORA-27057 skgfask: cannot perform async I/O to file
ORA-27058 skgfask: question parameter is invalid
ORA-27059 skgfrsz: could not reduce file size
ORA-27060 skgfofi: could not set close-on-exec bit on file
ORA-27061 skgfospo: waiting for async I/Os failed
ORA-27062 skgfospo: could not find pending async I/Os
ORA-27063 skgfospo: number of bytes read/written is incorrect
ORA-27064 skgfdisp: cannot perform async I/O to file
ORA-27065 skgfdisp: cannot perform async vector I/O to file
ORA-27066 skgfdisp: number of buffers in vector I/O exceeds maximum
ORA-27067 skgfdisp: size of buffer is invalid
ORA-27068 skgfdisp: buffer is not aligned properly
ORA-27069 skgfdisp: attempt to do I/O beyond the range of the file
ORA-27070 skgfdisp: async read/write failed
ORA-27071 skgfdisp: unable to seek to desired position in file
ORA-27072 skgfdisp: I/O error
ORA-27073 skgfcfi: async I/Os remaining to be dequeued for this file
ORA-27074 skgfrofl: unable to determine limit for open files
ORA-27075 skgfrofl: SSTMOFRC constant too large
ORA-27076 skgfrofl: unable to set limit for open files
ORA-27077 skgfofi: too many files open
ORA-27080 skgfrdup: too many files open
ORA-27084 skgfqio: unable to get/set file status flags
ORA-27086 skgfglk: unable to lock file - already in use
ORA-27087 skgfglk: unable to get share lock - file not readable
ORA-27088 skgfglk: unable to get file status
ORA-27089 skgfrlk: unable to release advisory lock
ORA-27091 skgfqio: unable to queue I/O
ORA-27092 skgfofi: size of file exceeds file size limit of the process
ORA-27100 shared memory realm already exists
ORA-27101 shared memory realm does not exist
ORA-27102 out of memory
ORA-27103 internal error
ORA-27120 unable to removed shared memory segment
ORA-27121 unable to determine size of shared memory segment
ORA-27122 unable to protect memory
ORA-27123 unable to attach to shared memory segment
ORA-27124 unable to detach from shared memory segment
ORA-27125 unable to create shared memory segment
ORA-27126 unable to lock shared memory segment in core
ORA-27127 unable to unlock shared memory segment
ORA-27128 unable to determine pagesize
ORA-27141 invalid process ID
ORA-27142 could not create new process
ORA-27143 OS system call failure
ORA-27144 attempt to kill process failed
ORA-27145 insufficient resources for requested number of processes
ORA-27146 post/wait initialization failed
ORA-27147 post/wait reset failed
ORA-27148 spawn wait error
ORA-27149 assignment out of range
ORA-27150 attempt to notify process of pending oradebug call failed
ORA-27151 buffer not large enough to hold process ID string
ORA-27152 attempt to post process failed
ORA-27153 wait operation failed
ORA-27154 post/wait create failed
ORA-27155 could not execute file
ORA-27156 request for process information failed
ORA-27157 OS post/wait facility removed
ORA-27190 skgfrd: sbtread2 returned error
ORA-27191 sbtinfo2 returned error
ORA-27192 skgfcls: sbtclose2 returned error - failed to close file
ORA-27193 sbtinfo2 did not return volume label
ORA-27194 skgfdvcmd: sbtcommand returned error
ORA-27195 proxy copy not supported
ORA-27196 skgfpbk: sbtpcbackup returned error
ORA-27197 skgfprs: sbtpcrestore returned error
ORA-27198 skgfpvl: sbtpcvalidate returned error
ORA-27199 skgfpst: sbtpcstatus returned error
ORA-27200 skgfpgo: sbtpcstart returned error
ORA-27201 skgfpcm: sbtpccommit returned error
ORA-27202 skgfpen: sbtpcend returned error
ORA-27203 skgfpqb: sbtpcquerybackup returned error
ORA-27204 skgfpqr: sbtpcqueryrestore returned error
ORA-27205 skgfpcn: sbtpccancel returned error
ORA-27206 requested file not found in media management catalog
ORA-27207 syntax error in device PARMS - parentheses mismatch or missing
ORA-27208 syntax error in device PARMS - environment variable value missing
ORA-27209 syntax error in device PARMS - unknown keyword or missing =
ORA-27210 syntax error in device PARMS
ORA-27211 Failed to load Media Management Library
ORA-27212 some entrypoints in Media Management Library are missing
ORA-27213 failed to unload Media Management Library
ORA-27300 OS system dependent operation:string failed with status: string
ORA-27301 OS failure message: string
ORA-27302 failure occurred at: string
ORA-27303 additional information: string
ORA-27500 inter-instance IPC error
ORA-27501 IPC error creating a port
ORA-27502 IPC error deleting OSD context
ORA-27505 IPC error destroying a port
ORA-27506 IPC error connecting to a port
ORA-27507 IPC error disconnecting from a port
ORA-27508 IPC error sending a message
ORA-27509 IPC error receiving a message
ORA-27510 IPC error waiting for a request to complete
ORA-27512 IPC error posting a process
ORA-27542 Failed to unprepare a buffer prepared for remote update
ORA-27543 Failed to cancel outstanding IPC request
ORA-27544 Failed to map memory region for export
ORA-27545 Fail to prepare buffer for remote update
ORA-27546 Oracle compiled against IPC interface version string.string found version string.string
ORA-27547 Unable to query IPC OSD attribute string
ORA-27548 Unable to unprepare IPC buffer
ORA-28000 the account is locked
ORA-28001 the password has expired
ORA-28002 the password will expire within string days
ORA-28003 password verification for the specified password failed
ORA-28004 invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
ORA-28005 invalid logon flags
ORA-28006 conflicting values for parameters string and string
ORA-28007 the password cannot be reused
ORA-28008 invalid old password
ORA-28009 connection to sys should be as sysdba or sysoper
ORA-28010 cannot expire external or global accounts
ORA-28011 the account will expire soon; change your password now
ORA-28020 IDENTIFIED GLOBALLY already specified
ORA-28021 cannot grant global roles
ORA-28022 cannot grant external roles to global user or role
ORA-28023 must revoke grants of this role to other user(s) first
ORA-28024 must revoke grants of external roles to this role/user
ORA-28025 missing or null external name
ORA-28026 user with same external name already exists
ORA-28027 privileged database links may be used by global users
ORA-28028 could not authenticate remote server
ORA-28029 could not authorize remote server for user string
ORA-28030 Server encountered problems accessing LDAP directory service
ORA-28035 Cannot Get Session Key for Authentication
ORA-28100 policy function schema string is invalid
ORA-28101 policy already exists
ORA-28102 policy does not exist
ORA-28103 adding a policy to an object owned by SYS is not allowed
ORA-28104 policy function or package is invalid
ORA-28106 input value for argument #string is not valid
ORA-28107 policy was disabled
ORA-28108 circular security policies detected
ORA-28109 the number of related policies has exceeded the limit of 16
ORA-28110 policy function or package string.string has error
ORA-28111 insufficient privilege to evaluate policy predicate
ORA-28112 failed to execute policy function
ORA-28113 policy predicate has error
ORA-28115 policy with check option violation
ORA-28116 insufficient privileges to do direct path access
ORA-28117 integrity constraint violated - parent record not found
ORA-28118 policy group already exists
ORA-28119 policy group does not exist
ORA-28120 driving context already exists
ORA-28121 driving context does not exist
ORA-28132 Merge into syntax does not support security policies.
ORA-28133 full table access is restricted by fine-grained security
ORA-28134 object cannot have fine-grained access control policy
ORA-28150 proxy not authorized to connect as client
ORA-28151 more than one user name specified for command
ORA-28152 proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
ORA-28153 Invalid client initial role specified: 'string'
ORA-28154 Proxy user may not act as client 'string'
ORA-28155 user 'string' specified as a proxy is actually a role
ORA-28156 Proxy user 'string' not authorized to set role 'string' for client 'string'
ORA-28157 Proxy user 'string' forbidden to set role 'string' for client 'string'
ORA-28158 missing ALL keyword
ORA-28159 missing BEHALF keyword
ORA-28160 missing EXCEPT keyword
ORA-28161 missing ROLES keyword
ORA-28162 missing THROUGH keyword
ORA-28163 GRANT already specified
ORA-28164 REVOKE already specified
ORA-28165 proxy 'string' may not specify password-protected role 'string' for client 'string'
ORA-28166 duplicate rolename in list
ORA-28168 attempted to grant password-protected role
ORA-28169 unsupported certificate type
ORA-28170 unsupported certificate version
ORA-28171 unsupported Kerberos version
ORA-28172 distinguished name not provided by proxy
ORA-28173 certificate not provided by proxy
ORA-28174 Kerberos ticket not provided by proxy
ORA-28175 incorrect certificate type
ORA-28176 incorrect certificate version
ORA-28177 incorrect Kerberos ticket version
ORA-28178 password not provided by proxy
ORA-28179 client user name not provided by proxy
ORA-28180 multiple authentication methods provided by proxy
ORA-28200 IDENTIFIED USING already specified
ORA-28201 Not enough privileges to enable application role 'string'
ORA-28221 REPLACE not specified
ORA-28231 no data passed to obfuscation toolkit
ORA-28232 invalid input length for obfuscation toolkit
ORA-28233 double encryption not supported
ORA-28234 key length too short
ORA-28235 algorithm not available
ORA-28236 invalid Triple DES mode
ORA-28237 seed length too short
ORA-28238 no seed provided
ORA-28239 no key provided
ORA-28261 CURRENT_USER can not be used in PLSQL Definer's Right procedure.
ORA-28262 global_context_pool_size has invalid value.
ORA-28263 Insufficient memory in global context pool
ORA-28264 Client identifier is too long
ORA-28265 NameSpace beginning with 'sys_' is not allowed
ORA-28270 Malformed user nickname for password authenticated global user
ORA-28271 No permission to read user entry in LDAP directory service
ORA-28272 Domain policy restricts password based GLOBAL user authentication
ORA-28273 No mapping for user nickname to LDAP distinguished name exists
ORA-28274 No ORACLE password attribute corresponding to user nickname exists
ORA-28275 Multiple mappings for user nickname to LDAP distinguished name exist
ORA-28276 Invalid ORACLE password attribute
ORA-28277 LDAP search, while authenticating global user with passwords, failed
ORA-28278 No domain policy registered for password based GLOBAL users
ORA-28279 Error reading rdbms_server_dn parameter in INIT.ORA
ORA-28280 Multiple entries for ORACLE database password exist.
ORA-28500 connection from ORACLE to a non-Oracle system returned this message:
ORA-28501 communication error on heterogeneous database link
ORA-28502 internal communication error on heterogeneous database link
ORA-28503 bind value cannot be translated into SQL text for non-Oracle system
ORA-28504 ROWID not found in ROWID cache for heterogeneous database link
ORA-28505 cannot get non-Oracle system capabilities from string
ORA-28506 parse error in data dictionary translation for string stored in string
ORA-28507 error in data dictionary view string
ORA-28508 invalid value string for Heterogeneous Services initialization parameter string
ORA-28509 unable to establish a connection to non-Oracle system
ORA-28510 heterogeneous database link initialization failed
ORA-28511 lost RPC connection to heterogeneous remote agent using SID=string
ORA-28512 cannot get data dictionary translations from string
ORA-28513 internal error in heterogeneous remote agent
ORA-28514 heterogeneous database link initialization could not convert system date
ORA-28515 cannot get external object definitions from string
ORA-28518 data dictionary translation has illegal translation type
ORA-28519 no heterogeneous data dictionary translations available
ORA-28520 error initializing heterogeneous data dictionary translations
ORA-28521 no heterogeneous capability information available
ORA-28522 error initializing heterogeneous capabilities
ORA-28523 ORACLE and heterogeneous agent are incompatible versions
ORA-28525 unable to create Heterogeneous Services error message text
ORA-28526 invalid describe information returned to Heterogeneous Services
ORA-28527 Heterogeneous Services datatype mapping error
ORA-28528 Heterogeneous Services datatype conversion error
ORA-28529 invalid or missing parameter in Net8 service name definition
ORA-28530 Heterogeneous Services initialization error in NLS language ID
ORA-28533 Heterogeneous Services coercion handling error
ORA-28534 Heterogeneous Services preprocessing error
ORA-28535 invalid Heterogeneous Services context
ORA-28536 error in processing Heterogeneous Services initialization parameters
ORA-28538 result set not found
ORA-28539 gateway does not support result sets
ORA-28541 Error in HS init file on line number.
ORA-28542 Error in reading HS init file
ORA-28543 Error initializing apply connection to non-Oracle system
ORA-28544 connect to agent failed, probable Net8 administration error
ORA-28545 error diagnosed by Net8 when connecting to an agent
ORA-28546 connection initialization failed, probable Net8 admin error
ORA-28550 pass-through SQL: cursor not found
ORA-28551 pass-through SQL: SQL parse error
ORA-28552 pass-through SQL: call flow error
ORA-28553 pass-through SQL: invalid bind-variable position
ORA-28554 pass-through SQL: out of cursors
ORA-28555 pass-through SQL: required parameter missing or NULL
ORA-28556 authorization insufficient to access table
ORA-28557 unknown string for database link to non-Oracle system
ORA-28558 HS_FDS_CONNECT_STRING undefined for non-Oracle system
ORA-28559 FDS_CLASS_NAME is string, FDS_INST_NAME is string
ORA-28560 error in configuration of agent process
ORA-28561 unable to set date format on non-Oracle system
ORA-28575 unable to open RPC connection to external procedure agent
ORA-28576 lost RPC connection to external procedure agent
ORA-28577 argument string of external procedure string has unsupported datatype string
ORA-28578 protocol error during callback from an external procedure
ORA-28579 network error during callback from external procedure agent
ORA-28580 recursive external procedures are not supported
ORA-28581 protocol error while executing recursive external procedure
ORA-28582 a direct connection to this agent is not allowed
ORA-28583 remote references are not permitted during agent callbacks
ORA-28584 heterogeneous apply internal error
ORA-28590 agent control utility: illegal or badly formed command
ORA-28591 agent control utility: unable to access parameter file
ORA-28592 agent control utility: agent SID not set
ORA-28593 agent control utility: command terminated with error
ORA-28594 agent control utility: invalid parameter name
ORA-28601 invalid [no]MINIMIZE option
ORA-28602 statement not permitted on tables containing bitmap indexes
ORA-28603 statement not permitted on empty tables
ORA-28604 table too fragmented to build bitmap index (string,string,string)
ORA-28605 bitmap indexes cannot be reversed
ORA-28611 bitmap index is corrupted - see trace file for diagnostics
ORA-28650 Primary index on an IOT cannot be rebuilt
ORA-28651 Primary index on IOTs can not be marked unusable
ORA-28652 overflow segment attributes cannot be specified
ORA-28653 tables must both be index-organized
ORA-28654 table and partition not overflow compatible
ORA-28655 Alter table add overflow syntax error
ORA-28656 incomplete attribute specification
ORA-28658 This operation is supported only for Index-Organized tables
ORA-28659 COMPRESS must be specified at object level first
ORA-28660 Partitioned Index-Organized table may not be MOVEd as a whole
ORA-28661 Object already has COMPRESS clause specified
ORA-28662 IOT index and overflow segments must share the same LOGGING attribute
ORA-28663 Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
ORA-28664 a partitioned table may not be coalesced as a whole
ORA-28665 table and partition must have same compression attribute
ORA-28666 option not allowed for an index on UROWID column(s)
ORA-28667 USING INDEX option not allowed for the primary key of an IOT
ORA-28668 cannot reference mapping table of an index-organized table
ORA-28669 bitmap index can not be created on an IOT with no mapping table
ORA-28670 mapping table cannot be dropped due to an existing bitmap index
ORA-28671 UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
ORA-28672 UPDATE BLOCK REFERENCES may not be used on a global index
ORA-28673 Merge operation not allowed on an index-organized table
|  Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
14
ORA-29250 to ORA-32799
-
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 DIRECTORYcommand. -
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
USINGclause 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_COUNTinitialization 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_COUNTinitialization 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_COUNTinitialization 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_COUNTinitialization parameter has the same value. Then restart the instance. -
Cause: The
ACTIVE_INSTANCE_COUNTinitialization 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_COUNTinitialization 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_NUMBERparameter 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_NUMBERparameter 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 UPDATEclause. -
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_PARTITIONSview to see which partitions are marked FAILED. Rebuild or Truncate the FAILED index partitions. -
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 Databasehas 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:
- Remove the use of the PL/SQL function.
- Mark the PL/SQL function as DETERMINISTIC.
- Disable the REWRITE option on the materialized view.
The function should be marked DETERMINISTIC only if it always returns the same result value for any given set of input argument values, regardless of any database state or session state. Do not mark the function as DETERMINISTIC if it has any meaningful side-effects.
-
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.sqlscript 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.sqlscript 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.sqlscript 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.sqlscript prior to invoking theDBMS_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:
DEFAULTDIRECTORY 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, orVARRAY. -
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
FROMclause. -
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_SIZEinitialization parameter to at least 2 KB. For XDB to run at its fastest, setDB_BLOCK_SIZEto 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
CASCADEorFORCEoptions. -
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
LEVELin membership condition with subquery that is not supported. -
Action: Rewrite query to avoid using
LEVELin 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_MAPPINGtotrueif it is not currently set. Otherwise, check FMON trace files for anORA-32052error. -
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
SYSDBApriviliges. -
Action: Connect to the database as a user with
SYSDBAprivileges. -
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 showto list valid watchpoint IDs. -
Cause: An attempt was made to delete an already deleted watchpoint.
-
Action: Use
oradebug showto 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
SYSorSYSTEMwas not specified when providing a password in theCREATE DATABASEstatement. -
Action: Only passwords for the
SYSandSYSTEMusers can be provided in theCREATE DATABASEstatement. Re-issue the statement with passwords for usersSYSorSYSTEM. -
Cause: A password for the
SYSuser was specified twice in theCREATE DATABASEstatement. -
Action: Re-issue the
CREATE DATABASEstatement with only one password for theSYSuser. -
Cause: A password for the
SYSTEMuser was specified twice in theCREATE DATABASEstatement. -
Action: Re-issue the
CREATE DATABASEstatement with only one password for theSYSTEMuser. -
Cause: Passwords for both the
SYSandSYSTEMusers were not provided in theCREATE DATABASEstatement. If one of the passwords was provided, then both should be provided. -
Action: Re-issue the
CREATE DATABASEstatement with a password for both theSYSandSYSTEMusers. -
Cause: An incorrect password was provided for the
SYSorSYSTEMusers in theCREATE DATABASEstatement. -
Action: Re-issue the
CREATE DATABASEstatement 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.
ORA-29250 Invalid index specifed in call to dbms_sql.bind_array
ORA-29251 Index1 is greater than Index2 in call to dbms_sql.bind_array
ORA-29252 collection does not contain elements at index locations in call to dbms_sql.bind_array
ORA-29253 Invalid count argument passed to procedure dbms_sql.define_array
ORA-29254 Invalid lower_bound argument passed to procedure dbms_sql.define_array
ORA-29255 Cursor contains both bind and define arrays which is not permissible
ORA-29256 Cursor contains both regular and array defines which is illegal
ORA-29257 host string unknown
ORA-29258 buffer too small
ORA-29259 end-of-input reached
ORA-29260 network error: string
ORA-29261 bad argument
ORA-29262 bad URL
ORA-29263 HTTP protocol error
ORA-29264 unknown or unsupported URL scheme
ORA-29265 HTTP header not found
ORA-29266 end-of-body reached
ORA-29267 illegal call
ORA-29268 HTTP client error string
ORA-29269 HTTP server error string
ORA-29270 too many open HTTP requests
ORA-29271 not connected
ORA-29272 initialization failed
ORA-29273 HTTP request failed
ORA-29274 fixed-width multibyte character set not allowed for a URL
ORA-29275 partial multibyte character
ORA-29276 transfer timeout
ORA-29277 invalid SMTP operation
ORA-29278 SMTP transient error: string
ORA-29279 SMTP permanent error: string
ORA-29280 invalid directory path
ORA-29281 invalid mode
ORA-29282 invalid file ID
ORA-29283 invalid file operation
ORA-29284 file read error
ORA-29285 file write error
ORA-29286 internal error
ORA-29287 invalid maximum line size
ORA-29288 invalid file name
ORA-29289 directory access denied
ORA-29290 invalid offset specified for seek
ORA-29291 file remove operation failed
ORA-29292 file rename operation failed
ORA-29300 ORACLE error, tablespace point-in-time recovery
ORA-29301 wrong DBMS_PITR package function/procedure order
ORA-29302 database is not open clone
ORA-29303 user does not login as SYS
ORA-29304 tablespace 'string' does not exist
ORA-29305 cannot point-in-time recover tablespace 'string'
ORA-29306 datafile string is not online
ORA-29307 datafile string error, string
ORA-29308 view TS_PITR_CHECK failure
ORA-29309 export dump file was generated by different version of DBMS_PITR package
ORA-29310 database is not open, or opened as a clone
ORA-29311 export dump file was not generated by this database, string does not match
ORA-29312 database not compatible, string string
ORA-29313 tablespace 'string' cannot be imported twice
ORA-29314 tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
ORA-29315 tablespace 'string' has been recreated
ORA-29316 datafile string been imported twice
ORA-29317 datafile string does not exist
ORA-29318 datafile string is online
ORA-29319 datafile string is not correct
ORA-29320 datafile header error
ORA-29321 too many datafiles added since the point-in-time
ORA-29322 SCN string size too long -- maximum size 58 bytes/characters
ORA-29323 SET COMPATIBILITY command cannot be used for releases before 8.0.0
ORA-29324 SET COMPATIBILITY release string format is wrong
ORA-29325 SET COMPATIBILITY release number mismatches compatibility release number
ORA-29326 specified SET COMPATIBILITY release number reduced to string.string.string.string.string
ORA-29327 unsupported client compatibility mode used when talking to the server
ORA-29328 too many datafiles in this tablespace 'string'
ORA-29335 tablespace 'string' is not read only
ORA-29336 Internal error [string] [string] from DBMS_PLUGTS
ORA-29337 tablespace 'string' has a non-standard block size (string)
ORA-29338 datafile string is in an undesired state (string, string)
ORA-29339 tablespace block size string does not match configured block sizes
ORA-29340 export file appears to be corrupted: [string] [string] [string]
ORA-29341 The transportable set is not self-contained
ORA-29342 user string does not exist in the database
ORA-29343 user string (mapped from user string) does not exist in the database
ORA-29344 Owner validation failed - failed to match owner 'string'
ORA-29345 can not plug a tablespace into a database using a different character set
ORA-29346 invalid tablespace list
ORA-29347 Tablespace name validation failed - failed to match tablespace 'string'
ORA-29348 You must specify the datafiles to be plugged in
ORA-29349 tablespace 'string' already exists
ORA-29350 server version string incompatible with package string version string
ORA-29351 can not transport system or temporary tablespace 'string'
ORA-29353 The transportable list is too long.
ORA-29355 NULL or invalid string argument specified
ORA-29356 These parameters can be specified only for directives that refer to consumer groups
ORA-29357 object string already exists
ORA-29358 resource plan string does not exist
ORA-29359 invalid method name string specified for resource plan string
ORA-29360 retry operation. Too much concurrent activity
ORA-29361 percentage string is outside valid range of 0 to 100
ORA-29362 plan directive string, string does not exist
ORA-29363 plan directive string, string is mandatory and cannot be modified or deleted
ORA-29364 plan directive string, string already exists
ORA-29365 NULL or invalid GROUP_OR_SUBPLAN argument specified
ORA-29366 invalid CONSUMER_GROUP argument specified
ORA-29367 object string does not exist
ORA-29368 consumer group string does not exist
ORA-29369 invalid method name string specified for consumer group string
ORA-29370 pending area is already active
ORA-29371 pending area is not active
ORA-29372 identifier string is too long; it must be less than string characters
ORA-29373 resource manager is not on
ORA-29374 resource plan string in top-plan string has no plan directives
ORA-29375 sum of percentages string for level string, plan string exceeds string
ORA-29376 number of consumer groups string in top-plan string exceeds string
ORA-29377 consumer group string is not part of top-plan string
ORA-29379 resource plan string is involved in a loop in top-plan string
ORA-29380 resource plan string is currently active and cannot be deleted
ORA-29381 plan/consumer_group string referred to by another plan and cannot be deleted
ORA-29382 validation of pending area failed
ORA-29383 all leaves of top-plan string must be consumer groups
ORA-29384 number of children for plan string exceeds string
ORA-29385 cannot create plan directive from string to string
ORA-29386 plan or consumer group string is mandatory and cannot be deleted or modified
ORA-29387 no top-plans found in the pending area
ORA-29388 plan/consumer_group string is part of more than one top-plan
ORA-29389 too many errors during validation
ORA-29390 some resource plans are not part of any top-plan
ORA-29391 string and string must be mandatory to create a mandatory plan directive
ORA-29393 user string does not exist or is not logged on
ORA-29394 session id string and serial# string do not exist
ORA-29395 cannot set the initial consumer group to string
ORA-29396 cannot switch group to string
ORA-29397 cannot grant/revoke switch privilege for string
ORA-29398 invalid privilege name specified
ORA-29399 user string does not have privilege to switch to consumer group string
ORA-29400 data cartridge errorstring
ORA-29500 NAMED keyword is invalid in CREATE JAVA CLASS
ORA-29501 invalid or missing Java source, class, or resource name
ORA-29502 NAMED keyword required in CREATE JAVA RESOURCE
ORA-29503 SCHEMA keyword not valid with NAMED keyword
ORA-29504 invalid or missing schema name
ORA-29505 AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
ORA-29506 invalid query derived from USING clause
ORA-29507 query derived from USING clause found zero or many rows
ORA-29508 query derived from USING clause did not select a value of type string
ORA-29509 incorrectly formed Java binary class definition
ORA-29510 name, string.string, already used by an existing object
ORA-29511 could not resolve Java class
ORA-29512 incorrectly formed name resolver specification
ORA-29513 referenced class name too long
ORA-29514 class name contains illegal character
ORA-29515 exit called from Java code with status string
ORA-29516 Aurora assertion failure: string
ORA-29517 recursive resolution failed for a referenced class
ORA-29518 name string resolved to an object in schema string that is not a Java class
ORA-29519 name string resolved via a synonym in schema string to a class with a different name
ORA-29520 name string resolved to a class in schema string that could not be accessed
ORA-29521 referenced name string could not be found
ORA-29522 authorization error for referenced name string.string
ORA-29523 authorization error for unknown referenced name
ORA-29524 wrong types of arguments in call to 'string'
ORA-29525 referenced name is too long: 'string'
ORA-29526 created Java class string"string"
ORA-29527 created Java source string"string"
ORA-29528 invalid Java call in trigger string
ORA-29529 invalid function or method call string in trigger string
ORA-29530 could not create shortened name for string
ORA-29531 no method string in class string
ORA-29532 Java call terminated by uncaught Java exception: string
ORA-29533 attempt to overwrite class or resource string while defining or compiling string.string
ORA-29534 referenced object string.string could not be resolved
ORA-29535 source requires recompilation
ORA-29536 badly formed source: string
ORA-29537 class or resource cannot be created or dropped directly
ORA-29538 Java not installed
ORA-29539 Java system classes already installed
ORA-29540 class string does not exist
ORA-29541 class string.string could not be resolved
ORA-29542 class string already defined by source string
ORA-29543 Java command string not yet implemented
ORA-29544 invalid type
ORA-29545 badly formed class: string
ORA-29546 badly formed resource: string
ORA-29547 Java system class not available: string
ORA-29548 Java system class reported: string
ORA-29549 class string.string has changed, Java session state cleared
ORA-29550 Java session state cleared
ORA-29551 could not convert string to Unicode
ORA-29552 verification warning: string
ORA-29553 class in use: string.string
ORA-29554 unhandled Java out of memory condition
ORA-29555 Java source, class or resource is not allowed here
ORA-29556 object type has changed
ORA-29557 Java system class string cannot be modified
ORA-29655 USING clause is incompatible with its supertype
ORA-29656 Invalid option for USING
ORA-29657 class defined in EXTERNAL NAME clause is used in another subtype
ORA-29658 EXTERNAL NAME clause is not compatible with its supertype
ORA-29659 SQLJ Object Type validation failed to get default connection
ORA-29660 Unable to find the class defined in the EXTERNAL NAME clause
ORA-29661 Unable to find the superclass of the defined in the EXTERNAL NAME
ORA-29662 Unable to find a field that matches one or more of the attributes
ORA-29663 Unable to find a method that matches one or more of the functions
ORA-29664 Unable to generate the helper class for the defined type
ORA-29665 Java thread deadlock detected
ORA-29701 unable to connect to Cluster Manager
ORA-29702 error occurred in Cluster Group Service operation
ORA-29703 error occurred in global enqueue service operation
ORA-29704 cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
ORA-29705 ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
ORA-29706 incorrect value string for parameter ACTIVE_INSTANCE_COUNT
ORA-29740 evicted by member string, group incarnation string
ORA-29741 IMR active for some, but not all members of cluster
ORA-29760 instance_number parameter not specified
ORA-29800 invalid name for operator
ORA-29801 missing RETURN keyword
ORA-29802 missing CONTEXT keyword
ORA-29803 missing ANCILLARY keyword
ORA-29804 missing DATA keyword
ORA-29805 missing COLUMN keyword
ORA-29806 specified binding does not exist
ORA-29807 specified operator does not exist
ORA-29808 specified primary operator binding does not exist
ORA-29809 cannot drop an operator with dependent objects
ORA-29810 inadequate operator privileges
ORA-29811 missing STATISTICS keyword
ORA-29812 incorrect object name specified
ORA-29813 non-supported object type with associate statement
ORA-29814 expecting USING or DEFAULT keyword
ORA-29815 object being associated is not present
ORA-29816 object being disassociated is not present
ORA-29817 non-supported option with disassociate statement
ORA-29818 column name not properly specified
ORA-29819 cannot associate default values with columns
ORA-29820 the statistics type is not present
ORA-29821 specified primary operator does not exist
ORA-29822 selectivity cannot be specified for the type of object
ORA-29823 object being analyzed is not a table
ORA-29824 operator is invalid
ORA-29825 invalid name for indextype
ORA-29826 keyword FOR is missing
ORA-29827 keyword USING is missing
ORA-29828 invalid name for implementation type
ORA-29829 implementation type does not exist
ORA-29830 operator does not exist
ORA-29831 operator binding not found
ORA-29832 cannot drop or replace an indextype with dependent indexes
ORA-29833 indextype does not exist
ORA-29834 REF datatype not supported with operators
ORA-29835 ODCIGETINTERFACES routine does not return required interface(s)
ORA-29836 failed to validate referenced operators
ORA-29837 insufficient privileges to execute implementation type
ORA-29838 insufficient privileges to execute the operator(s)
ORA-29839 failed to validate implementation type
ORA-29840 indextype and implementation type are not in same schema
ORA-29841 invalid option for ALTER INDEXTYPE
ORA-29842 option not supported with the version string of the indextype interface
ORA-29843 indextype should support atleast one operator
ORA-29844 duplicate operator name specified
ORA-29845 indextype does not support local domain index on string partitioned table
ORA-29846 cannot create a local domain index on a string partitioned table
ORA-29847 cannot create a local domain index on a partitioned index-organized table
ORA-29848 error occurred in the execution of ODCIINDEXMERGEPARTITION routine
ORA-29849 error occurred in the execution of ODCIINDEXSPLITPARTITION routine
ORA-29850 invalid option for creation of domain indexes
ORA-29851 cannot build a domain index on more than one column
ORA-29852 keyword IS is missing
ORA-29853 keyword UNIQUE may not be used in creating domain indexes
ORA-29854 keyword BITMAP may not be used in creating domain indexes
ORA-29855 error occurred in the execution of ODCIINDEXCREATE routine
ORA-29856 error occurred in the execution of ODCIINDEXDROP routine
ORA-29857 domain indexes and/or secondary objects exist in the tablespace
ORA-29858 error occurred in the execution of ODCIINDEXALTER routine
ORA-29859 error occurred in the execution of ODCIINDEXTRUNCATE routine
ORA-29860 cannot truncate a table with domain indexes marked LOADING
ORA-29861 domain index is marked LOADING/FAILED/UNUSABLE
ORA-29862 cannot specify FORCE option for dropping non-domain index
ORA-29863 warning in the execution of ODCIINDEXCREATE routine
ORA-29864 analyzing domain indexes marked LOADING/FAILED not supported
ORA-29865 indextype is invalid
ORA-29866 cannot create domain index on a column of index-organized table
ORA-29867 cannot create a domain index on a LONG column
ORA-29868 cannot issue DDL on a domain index marked as LOADING
ORA-29869 cannot issue ALTER without REBUILD on a domain index marked FAILED
ORA-29870 specified options are only valid for altering a domain index
ORA-29871 invalid alter option for a domain index
ORA-29872 parameters clause cannot be combined with the specified options
ORA-29873 warning in the execution of ODCIINDEXDROP routine
ORA-29874 warning in the execution of ODCIINDEXALTER routine
ORA-29875 failed in the execution of the ODCIINDEXINSERT routine
ORA-29876 failed in the execution of the ODCIINDEXDELETE routine
ORA-29877 failed in the execution of the ODCIINDEXUPDATE routine
ORA-29878 warning in the execution of ODCIINDEXTRUNCATE routine
ORA-29879 cannot create multiple domain indexes on a column list using same indextype
ORA-29880 such column list already indexed using another domain index and indextype
ORA-29881 failed to validate indextype
ORA-29882 insufficient privileges to execute indextype
ORA-29883 cannot create a domain index on column expressions
ORA-29884 domain index is defined on the column to be dropped
ORA-29885 domain index is defined on the column to be modified
ORA-29886 feature not supported for domain indexes
ORA-29887 cannot support row movement if domain index defined on table
ORA-29888 cannot create domain index on a table with row movement enabled
ORA-29890 specified primary operator does not have an index context
ORA-29900 operator binding does not exist
ORA-29901 function underlying operator binding does not exist
ORA-29902 error in executing ODCIIndexStart() routine
ORA-29903 error in executing ODCIIndexFetch() routine
ORA-29904 error in executing ODCIIndexClose() routine
ORA-29905 method string does not exist in type string.string
ORA-29906 indextype string.string does not exist
ORA-29907 found duplicate labels in primary invocations
ORA-29908 missing primary invocation for ancillary operator
ORA-29909 label for the ancillary operator is not a literal number
ORA-29910 invalid callback operation
ORA-29911 null scan context returned by ODCIIndexStart() routine
ORA-29913 error in executing string callout
ORA-29914 ODCIGETINTERFACES routine does not return required stream version
ORA-29915 cannot select FOR UPDATE from collection operand
ORA-29925 cannot execute string
ORA-29926 association already defined for the object
ORA-29927 error in executing the ODCIStatsCollect / ODCIStatsDelete routine
ORA-29928 duplicate default selectivity specified
ORA-29929 missing SCAN Keyword
ORA-29930 COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
ORA-29931 specified association does not exist
ORA-29932 the type being dropped is a statistics type
ORA-29933 object being disassociated has some user defined statistics stored
ORA-29934 index specified for association is not a domain index
ORA-29935 missing FROM keyword
ORA-29936 NULL association is allowed only with a column or an index
ORA-29950 warning in the execution of ODCIINDEXMERGEPARTITION routine
ORA-29951 warning in the execution of ODCIINDEXSPLITPARTITION routine
ORA-29952 cannot issue DDL on a domain index partition marked as LOADING
ORA-29953 cannot issue DDL on a domain index partition marked as FAILED
ORA-29954 domain index partition is marked LOADING/FAILED/UNUSABLE
ORA-29955 error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
ORA-29956 warning in the execution of ODCIINDEXEXCHANGEPARTITION routine
ORA-29957 cannot create a function-based domain index on a string table
ORA-29958 fatal error occurred in the execution of ODCIINDEXCREATE routine
ORA-29959 error in the execution of the string routine for one or more of the index partitions
ORA-29960 line string, stringThe ODCIIndex DDL routine has put a warning message into table
SYS.ODCI_WARNINGS$.
ORA-29961 too many warnings occurred in the execution of ODCIIndex DDL routine
ORA-29962 fatal error occurred in the execution of ODCIINDEXALTER routine
ORA-30000 missing either trim specification or char expression in TRIM
ORA-30001 trim set should have only one character
ORA-30002 SYS_CONNECT_BY_PATH function is not allowed here
ORA-30003 illegal parameter in SYS_CONNECT_BY_PATH function
ORA-30004 when using SYS_CONNECT_BY_PATH function, cannot have seperator as part of column value
ORA-30005 missing or invalid WAIT interval
ORA-30006 resource busy; acquire with WAIT timeout expired
ORA-30012 undo tablespace 'string' does not exist or of wrong type
ORA-30013 undo tablespace 'string' is currently in use
ORA-30014 operation only supported in Automatic Undo Management mode
ORA-30015 previously offlined undo tablespace 'string' is still pending
ORA-30016 undo tablespace 'string' is already in use by this instance
ORA-30017 segment 'string' is not supported in string Undo Management mode
ORA-30018 Create Rollback Segment failed, USN string is out of range
ORA-30019 Illegal rollback Segment operation in Automatic Undo mode
ORA-30020 UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
ORA-30021 Operation not allowed on undo tablespace
ORA-30022 Cannot create segments in undo tablespace
ORA-30023 Duplicate undo tablespace specification
ORA-30024 Invalid specification for CREATE UNDO TABLESPACE
ORA-30025 DROP segment 'string' (in undo tablespace) not allowed
ORA-30026 Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
ORA-30027 Undo quota violation - failed to get string (bytes)
ORA-30029 no active undo tablespace assigned to instance
ORA-30031 the suspended (resumable) statement has been aborted
ORA-30032 the suspended (resumable) statement has timed out
ORA-30033 Undo tablespace cannot be specified as default user tablespace
ORA-30034 Undo tablespace cannot be specified as temporary tablespace
ORA-30035 Undo tablespace cannot be specified as default temporary tablespace
ORA-30036 unable to extend segment by string in undo tablespace 'string'
ORA-30037 Cannot perform parallel DML after a prior DML on the object
ORA-30038 Cannot perform parallel insert on non-partitioned object
ORA-30039 Cannot drop the undo tablespace
ORA-30040 Undo tablespace is offline
ORA-30041 Cannot grant quota on the tablespace
ORA-30042 Cannot offline the undo tablespace
ORA-30043 Invalid value 'string' specified for parameter 'Undo_Management'
ORA-30045 No undo tablespace name specified
ORA-30071 conversion between datetime/interval and string fail
ORA-30072 invalid time zone value
ORA-30073 invalid adjustment value
ORA-30074 GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
ORA- 30075 TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
ORA-30076 invalid extract field for extract source
ORA-30077 illegal casting between specified datetime types
ORA-30078 partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
ORA-30081 invalid data type for datetime/interval arithmetic
ORA-30082 datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
ORA-30083 syntax error was found in interval value expression
ORA-30084 invalid data type for datetime primary with time zone modifier
ORA-30085 syntax error was found in overlaps predicate
ORA-30086 interval year-month result not allowed for datetime subtraction
ORA-30087 Adding two datetime values is not allowed
ORA-30088 datetime/interval precision is out of range
ORA-30089 missing or invalid datetime_field
ORA-30100 internal error [number]
ORA-30101 unknown parameter name 'string'
ORA-30102 'string' is not in the legal range for 'string'
ORA-30103 'string' contains an illegal integer radix for 'string'
ORA-30104 'string' is not a legal integer for 'string'
ORA-30105 'string' is not a legal boolean for 'string'
ORA-30106 reserved for future use
ORA-30107 parameter name abbreviation 'string' is not unique
ORA-30108 invalid positional parameter value 'string'
ORA-30109 could not open parameter file 'string'
ORA-30110 syntax error at 'string'
ORA-30111 no closing quote for value 'string'
ORA-30112 multiple values not allowed for parameter 'string'
ORA-30113 error when processing file 'string'
ORA-30114 error when processing from command line
ORA-30115 error when processing an environment variable
ORA-30116 syntax error at 'string' following 'string'
ORA-30117 syntax error at 'string' at the start of input
ORA-30118 syntax error at 'string' at the end of input
ORA-30119 unable to obtain a valid value for 'string'
ORA-30120 'string' is not a legal oracle number for 'string'
ORA-30121 'string' is not an allowable value for 'string'
ORA-30122 value 'string' for 'string' must be between 'number' and 'number'"
ORA-30129 invalid function argument received
ORA-30130 invalid parameter key type received
ORA-30131 number of keys being set exceeds allocation
ORA-30132 invalid key index supplied
ORA-30135 OCI Thread operation fails
ORA-30150 Invalid argument passed to OCIFile function
ORA-30151 File already exists
ORA-30152 File does not exist
ORA-30153 An invalid File Object is passed to the OCIFile function
ORA-30154 The memory address given as buffer for OCIFileRead/Write is invalid
ORA-30155 An I/O Error occured during an OCIFile function call
ORA-30156 Out of disk space
ORA-30157 An invalid argument was given to operating system call
ORA-30158 The OCIFileWrite causes the file to exceed the maximum allowed size
ORA-30159 OCIFileOpen: Cannot create the file or cannot open in the requested mode
ORA-30160 Unable to access the file
ORA-30161 A system error occurred during the OCIFile function call
ORA-30162 The OCIFile context is not initialzed
ORA-30163 The thread safety initialization failed
ORA-30175 invalid type given for an argument
ORA-30176 invalid format code used in the format string
ORA-30177 invalid flag used in a format specification
ORA-30178 duplicate flag used in a format specification
ORA-30179 invalid argument index used in a format code
ORA-30180 argument index is too large
ORA-30181 integer in argument index is not immediately followed by )
ORA-30182 invalid precision specifier
ORA-30183 invalid field width specifier
ORA-30184 argument type not compatible with a format code
ORA-30185 output too large to fit in the buffer
ORA-30186 '\' must be followed by four hexadecimal characters or another '\'
ORA-30187 reserved for future use
ORA-30188 reserved for future use
ORA-30189 reserved for future use
ORA-30190 reserved for future use
ORA-30191 missing argument list
ORA-30192 reserved for future use
ORA-30193 reserved for future use
ORA-30194 reserved for future use
ORA-30195 reserved for future use
ORA-30196 reserved for future use
ORA-30197 reserved for future use
ORA-30198 reserved for future use
ORA-30199 reserved for future use
ORA-30200 Wrong NLS item was passed into OCINlsGetInfo()
ORA-30201 Unable to load NLS data object
ORA-30202 NULL pointer to OCIMsgh was passed to OCIMsg function
ORA-30203 Cannot open mesage file
ORA-30204 buffer is not large enough
ORA-30205 invalid Character set
ORA-30331 summary does not exist
ORA-30332 container table already in use by other summary
ORA-30333 dimension does not exist
ORA-30334 illegal dimension level name
ORA-30335 JOIN KEY clause references a level not in this hierarchy
ORA-30336 no child for specified JOIN KEY
ORA-30337 multiple JOIN KEY clauses specified for the same parent level
ORA-30338 illegal dimension hierachy name
ORA-30339 illegal dimension attribute name
ORA-30340 illegal dimension name
ORA-30341 dropped level has references
ORA-30342 referenced level is not defined in this dimension
ORA-30343 level name is not unique within this dimension
ORA-30344 number of child cols different from number of parent level cols
ORA-30345 circular dimension hierarchy
ORA-30346 hierarchy name must be unique within a dimension
ORA-30347 a table name is required to qualify the column specification
ORA-30348 ADD and DROP cannot both be specified
ORA-30349 specified dimension hierarchy does not exist
ORA-30350 specified dimension attribute does not exist
ORA-30351 query rewrite does not currently support this expression
ORA-30352 inconsistent numeric precision or string length
ORA-30353 expression not supported for query rewrite
ORA-30354 Query rewrite not allowed on SYS relations
ORA-30355 materialized view container does not exist
ORA-30356 the specified refresh method is not supported in this context
ORA-30357 this PL/SQL function cannot be supported for query rewrite
ORA-30358 summary and materialized view are not in same schema
ORA-30359 Query rewrite is not supported on SYS materialized views
ORA-30360 REF not supported with query rewrite
ORA-30361 unrecognized string type
ORA-30362 dimension column cannot be a sequence
ORA-30363 columns in a dimension column list must be in the same relation
ORA-30364 this level has the same set of columns as another
ORA-30365 left relation in the JOIN KEY clause cannot be same as right
ORA-30366 child JOIN KEY columns not in same relation as child level
ORA-30367 a JOIN KEY clause is required
ORA-30368 ATTRIBUTE cannot determine column in a different relation
ORA-30369 maximum number of columns is 32
ORA-30370 set operators are not supported in this context
ORA-30371 column cannot define a level in more than one dimension
ORA-30372 fine grain access policy conflicts with materialized view
ORA-30373 object data types are not supported in this context
ORA-30374 materialized view is already fresh
ORA-30375 materialized view cannot be considered fresh
ORA-30376 prevent sharing of a parsed query of an explain rewrite session
ORA-30377 MV_CAPABILITIES_TABLE not found
ORA-30378 MV_CAPABILITIES_TABLE is not compatible with Oracle version
ORA-30379 query txt not specified
ORA-30380 REWRITE_TABLE does not exist.
ORA-30381 REWRITE_TABLE is not compatible with Oracle version
ORA-30382 DROP MATERIALIZED VIEW string.string operation is not complete
ORA-30430 list does not contain any valid summaries
ORA-30431 refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
ORA-30432 summary 'string.string' is in INVALID state
ORA-30433 'string.string' is not a summary
ORA-30434 refresh method must be one of FC?AN, not 'string'
ORA-30435 job_queue_processes must be non-zero in order to refresh summaries
ORA-30436 unable to open named pipe 'string'
ORA-30437 all job queue processes have stopped running
ORA-30438 unable to access named pipe 'string'
ORA-30439 refresh of 'string.string' failed because of string
ORA-30440 can't fast refresh;refresh complete or set event 30441 for partial refresh
ORA-30442 can not find the definition for filter string
ORA-30443 definition for filter string's item string is invalid
ORA-30445 workload queries not found
ORA-30446 valid workload queries not found
ORA-30447 internal data for run number string is inconsistent
ORA-30449 syntax error in parameter string
ORA-30450 refresh_after_errors was TRUE; The following MVs could not be refreshed: string
ORA-30451 internal error
ORA-30452 cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
ORA-30453 summary contains AVG without corresponding COUNT
ORA-30454 summary contains STDDEV without corresponding SUM & COUNT
ORA-30455 summary contains VARIANCE without corresponding SUM & COUNT
ORA-30456 'string.string' cannot be refreshed because of insufficient privilege
ORA-30457 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
ORA-30458 'string.string' cannot be refreshed because the refresh mask is string
ORA-30459 'string.string' cannot be refreshed because the refresh method is NONE
ORA-30460 'string.string' cannot be refreshed because it is marked UNUSABLE
ORA-30461 'string.string' cannot be refreshed because it is marked DISABLED
ORA-30462 unsupported operator: string
ORA-30463 'string' is not a detail table of any summary
ORA-30464 no summaries exist
ORA-30465 supplied run_id is not valid: string
ORA-30466 cannot find the specified workload string
ORA-30467 internal data for filter number string is inconsistent
ORA-30475 feature not enabled: string
ORA-30476 PLAN_TABLE does not exist in the user's schema
ORA-30477 The input select_clause is incorrectly specified
ORA-30478 Specified dimension does not exist
ORA-30479 Summary Advisor errorstring
ORA-30480 DISTINCT option not allowed with GROUP BY CUBE or ROLLUP
ORA-30481 GROUPING function only supported with GROUP BY CUBE or ROLLUP
ORA-30483 window functions are not allowed here
ORa-30484 missing window specification for this function
ORA-30485 missing ORDER BY expression in the window specification
ORA-30486 invalid window aggregation group in the window specification
ORA-30487 ORDER BY not allowed here
ORA-30488 argument should be a function of expressions in PARTITION BY
ORA-30489 Cannot have more than one rollup/cube expression list
ORA-30490 Ambiguous expression in GROUP BY ROLLUP or CUBE list
ORA-30493 The percentile value should be a number between 0 and 1.
ORA-30500 database open triggers and server error triggers cannot have BEFORE type
ORA-30501 instance shutdown triggers cannot have AFTER type
ORA-30502 system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
ORA-30503 system triggers cannot have a REFERENCING clause
ORA-30504 system triggers cannot have a FOR EACH ROW clause
ORA-30505 system triggers should not reference a column in a WHEN clause
ORA-30506 system triggers cannot be based on tables or views
ORA-30507 normal triggers cannot be based on a schema or a database
ORA-30508 client logon triggers cannot have BEFORE type
ORA-30509 client logoff triggers cannot have AFTER type
ORA-30510 system triggers cannot be defined on the schema of SYS user
ORA-30511 invalid DDL operation in system triggers
ORA-30512 cannot modify string.string more than once in a transaction
ORA-30513 cannot create system triggers of INSTEAD OF type
ORA-30514 system trigger cannot modify tablespace being made read only
ORA-30515 suspend triggers cannot have BEFORE type
ORA-30550 index depends on a package/function spec/body which is not valid
ORA-30551 The index depends on a package/type body which does not exist
ORA-30552 The package/procedure/function cannot be changed
ORA-30553 The function is not deterministic
ORA-30554 function-based index string.string is disabled
ORA-30555 global index partitioning key is an expression
ORA-30556 functional index is defined on the column to be modified
ORA-30557 function based index could not be properly maintained
ORA-30558 internal error [string] in function based index
ORA-30560 SAMPLE option not allowed with index-organized tables
ORA-30561 SAMPLE option not allowed in statement with multiple table references
ORA-30562 SAMPLE percentage must be in the range [0.000001,100)
ORA-30563 outer join operator (+) not allowed in select-list
ORA-30564 Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
ORA-30565 Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified
ORA-30566 Index maintainence clause not allowed for this command
ORA-30567 name already used by an existing log group
ORA-30568 cannot drop log group - nonexistent log group
ORA-30569 data type of given column is not supported in a log group
ORA-30570 SEGMENT SPACE MANAGEMENT option already specified
ORA-30571 invalid SEGMENT SPACE MANAGEMENT clause
ORA-30572 AUTO segment space management not valid with DICTIONARY extent management
ORA-30573 AUTO segment space management not valid for this type of tablespace
ORA-30574 Cannot create rollback segment in tablespace with AUTO segment space management
ORA-30575 ConText Option not installed
ORA-30576 ConText Option dictionary loading error
ORA-30625 method dispatch on NULL SELF argument is disallowed
ORA-30645 reject limit out of range
ORA-30646 schema for external table type must be SYS
ORA-30647 error retrieving access parameters for external table string.string
ORA-30649 missing DIRECTORY keyword
ORA-30653 reject limit reached
ORA-30654 missing DEFAULT keyword
ORA-30655 cannot select FOR UPDATE from external organized table
ORA-30656 column type not supported on external organized table
ORA-30657 operation not supported on external organized table
ORA-30658 attempt was made to create a temporary table with EXTERNAL organization
ORA-30676 socket read or write failed
ORA-30677 session is already connected to a debugger
ORA-30678 too many open connections
ORA-30679 JDWP-based debugging not supported in this configuration
ORA-30680 debugger connection handshake failed
ORA-30681 improper value for argument EXTENSIONS_CMD_SET
ORA-30682 improper value for argument OPTION_FLAGS
ORA-30683 failure establishing connection to debugger
ORA-30684 specified role could not be enabled
ORA-30685 versions of DBMS_DEBUG_JDWP and Oracle are inconsistent
ORA-30686 no dispatcher accepted TCP/IP connection request
ORA-30687 session terminated by debugger
ORA-30688 maximum program calling depth exceeded
ORA-30689 improper value for ORA_DEBUG_JDWP
ORA-30690 timeout occurred while registering a TCP/IP connection for data traffic detection
ORA-30691 failed to allocate system resources while registering a TCP/IP connection for data traffic detection
ORA-30695 JDWP message format problem
ORA-30725 JDWP-based debugging is not yet available
ORA-30726 cannot specify referenced column list here
ORA-30727 duplicate referential constraint for a REF column
ORA-30728 maximum number of columns exceeded
ORA-30729 maximum number of columns exceeded
ORA-30730 referential constraint not allowed on nested table column
ORA-30731 scope constraint not allowed on nested table column when the nested table is being created
ORA-30732 table contains no user-visible columns
ORA-30733 cannot specify rowid constraint on scoped ref column
ORA-30734 cannot specify scope constraint on ref column with rowid
ORA-30735 cannot create multiple subtables of the same type under a supertable
ORA-30736 objects in a table or view hierarchy have to be in the same schema
ORA-30737 cannot create subtable of a type which is not a subtype of the type of the supertable
ORA-30738 object "string" does not exist in schema "string"
ORA-30739 cannot drop a table that has subtables
ORA-30740 cannot grant UNDER privilege on this object
ORA-30741 WITH HIERARCHY OPTION can be specified only for SELECT privilege
ORA-30742 cannot grant SELECT privilege WITH HIERARCHY OPTION on this object
ORA-30743 "string" is not an object view
ORA-30744 "string" is not an object table
ORA-30745 error occurred while trying to add column "string" in table "string"
ORA-30746 error occurred while trying to drop column "string" in table "string"
ORA-30747 cannot create substitutable tables or columns of non final type string.string
ORA-30748 column string already enabled to store objects of type string.string
ORA-30749 column string not enabled to store objects of type string.string
ORA-30750 cannot enable column string to store objects of type string.string
ORA-30751 cannot disable column string from storing objects of type string.string
ORA-30752 column or table string is not substitutable
ORA-30753 column or table string is substitutable
ORA-30754 column or table string stores objects of only one type
ORA-30755 error during expansion of view hierarchy
ORA-30756 cannot create column or table of type that contains a supertype attribute
ORA-30757 cannot access type information
ORA-30765 cannot modify scope for an unscoped REF column
ORA-30766 cannot modify scope for a REF column with a REFERENCES constraint
ORA-30767 OID type mismatch
ORA-30768 Cannot evaluate pipelined function
ORA-30770 Cannot specify storage options for fixed size opaque type
ORA-30771 Cannot add more than one referential constraint on REF column "string"
ORA-30772 opaque types do not have default constructors
ORA-30926 unable to get a stable set of rows in the source tables
ORA-30927 Unable to complete execution due to failure in temporary table transformation
ORA-30928 Connect by filtering phase runs out of temp tablespace
ORA-30929 ORDER SIBLINGS BY clause not allowed here
ORA-31000 Resource 'string' is not an XDB schema document
ORA-31001 Invalid resource handle or path name "string"
ORA-31002 Path name string is not a container
ORA-31003 Parent string already contains child entry string
ORA-31004 Length string of the BLOB in XDB$H_INDEX is below the minimum string
ORA-31005 Path name length string exceeds maximum length string
ORA-31006 Path name segment length string exceeds maximum length string
ORA-31007 Attempted to delete non-empty container string/string
ORA-31008 stream error in XDB, error code [string], stream type [string]
ORA-31010 XML element index string exceeds maximum insertion index string
ORA-31011 XML parsing failed
ORA-31012 Given XPATH expression not supported
ORA-31013 Invalid XPATH expression
ORA-31014 Attempted to delete the root container
ORA-31015 Attempted to insert entry without name
ORA-31016 Attempted to delete entry without name
ORA-31017 Error generating unique OID for XML document
ORA-31018 Error deleting XML document
ORA-31019 Recursive deletion snapshot too old for string/string
ORA-31020 The operation is not allowed, Reason: string
ORA-31021 Element definition not found
ORA-31022 Element not found
ORA-31023 Index size error
ORA-31024 Exceeded maximum number string of XML node elements
ORA-31025 Invalid document element
ORA-31026 XML maxoccurs value string exceeded
ORA-31027 Path name or handle string does not point to a resource
ORA-31028 XML node string has length string, exceeding maximum string
ORA-31029 Cannot bind to unsaved resource
ORA-31030 Unable to retrieve XML document
ORA-31031 Cannot insert non-schema data into unordered XML nodes
ORA-31032 XML element index string out-of-range for string-element node
ORA-31033 Requested number of XML children string exceeds maximum string
ORA-31034 Could not delete at index string in a string-element node
ORA-31035 Could not bind locked resource to path string/string
ORA-31036 Cannot store an XML prefix without an associated namespace
ORA-31037 Invalid XML attribute name string
ORA-31038 Invalid string value string
ORA-31039 XML namespace length string exceeds maximum string
ORA-31040 Property string: XML type (string) not compatible with internal memory type (string)
ORA-31041 Property string: Memory type (string) not compatible with database type (string)
ORA-31042 Too many properties in type 'string'
ORA-31043 Element 'string' not globally defined in schema 'string'
ORA-31044 Top-level prefix length string exceeds maximum string
ORA-31045 Cannot store more than string extras outside the root XML node
ORA-31046 Incorrect argument(s) specified in the operator
ORA-31047 Could not retrieve resource data at path string
ORA-31048 Unsaved resources cannot be updated
ORA-31050 Access denied
ORA-31051 Requested access privileges not supported
ORA-31052 Cannot delete ACL with other references
ORA-31053 The value of the depth argument in the operator cannot be negative
ORA-31054 The string operator cannot have an ancillary operator
ORA-31055 A null XMLType element cannot be inserted into RESOURCE_VIEW
ORA-31056 The document being inserted does not conform to Resource Schema
ORA-31057 Display Name of the element being inserted is null
ORA-31058 cannot modify read-only XOBs
ORA-31059 Cannot insert root XML document node if it already exists
ORA-31060 Resource at path string could not be deleted
ORA-31062 Cannot delete an unsaved resource
ORA-31065 Cannot modify read-only property [string]
ORA-31066 Insertion of string into string creates a cycle
ORA-31067 XML nodes must be updated with nodes of the same type
ORA-31068 updateXML expected data format [string] instead of [string]
ORA-31069 Cannot apply typed changes to non-schema-based XMLType nodes
ORA-31070 Invalid database user ID string
ORA-31071 Invalid database username or GUID string
ORA-31072 Too many child nodes in XMLType fragment for updateXML
ORA-31073 Resource not retrieved using path name
ORA-31075 invalid string declaration in XML Schema
ORA-31076 required attribute "string" not specified
ORA-31077 invalid attribute "string" specified
ORA-31078 error in SQL mapping information
ORA-31079 unable to resolve reference to string "string"
ORA-31080 type not specified for attribute or element "string"
ORA-31081 name not specified for global declaration
ORA-31082 invalid attribute "string" specified in declaration of "string"
ORA-31083 error while creating SQL type "string"."string"
ORA-31084 error while creating table "string"."string" for element "string"
ORA-31085 schema "string" already registered
ORA-31086 insufficient privileges to register global schema "string"
ORA-31087 insufficient privileges to delete schema "string"
ORA-31088 object "string"."string" depends on the schema
ORA-31089 schema "string" does not target namespace "string"
ORA-31090 invalid database schema name "string"
ORA-31091 empty string specified as a SQL name
ORA-31092 invalid SQL name "string"
ORA-31093 null or invalid value specified for parameter : string
ORA-31094 incompatible SQL type "string" for attribute or element "string"
ORA-31095 cannot generate string : "string.string" already exists
ORA-31096 validation failed for schema
ORA-31097 Hierarchical Index not empty
ORA-31099 XDB Security Internal Error
ORA-31100 XDB Locking Internal Error
ORA-31101 Token "string" not given while locking resource "string"
ORA-31102 Already locked in exclusive mode. Cannot add lock.
ORA-31103 Resource locked in shared mode. Cannot add exclusive lock.
ORA-31104 Cannot find lock with token "string" on "string" for unlock
ORA-31105 User does not own lock "string"
ORA-31106 Action failed as the parent container is locked
ORA-31107 Action failed as resource "string" is locked by name lock
ORA-31108 Action failed as resource string is locked
ORA-31109 Action failed as parent resource string is locked
ORA-31110 Action failed as resource string is locked by name
ORA-31111 table string cannot be hierarchically enabled
ORA-31112 fail to string for string port using xdb configuration
ORA-31113 XDB configuration may not be updated with non-schema compliant data
ORA-31114 XDB configuration has been deleted or is corrupted
ORA-31115 XDB configuration error: string
ORA-31121 The string operator can not be FALSE
ORA-31122 The string operator has incorrect RHS value
ORA-31151 Cyclic definition encountered for string: "string"
ORA-31153 Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
ORA-31154 invalid XML document
ORA-31155 attribute string not in XDB namespace
ORA-31190 Resource string is not a version-controlled resource
ORA-31191 Resource string is already checked out
ORA-31192 Resource string has not been checked out
ORA-31193 This versioning feature isn't supported for resource string
ORA-31194 Resource string is already deleted
ORA-31201 DBMS_LDAP: generic error: string
ORA-31202 DBMS_LDAP: LDAP client/server error: string
ORA-31203 DBMS_LDAP: PL/SQL - Init Failed
ORA-31204 DBMS_LDAP: PL/SQL - Invalid LDAP Session
ORA-31205 DBMS_LDAP: PL/SQL - Invalid LDAP Auth method
ORA-31206 DBMS_LDAP: PL/SQL - Invalid LDAP search scope
ORA-31207 DBMS_LDAP: PL/SQL - Invalid LDAP search time value
ORA-31208 DBMS_LDAP: PL/SQL - Invalid LDAP Message
ORA-31209 DBMS_LDAP: PL/SQL - LDAP count_entry error
ORA-31210 DBMS_LDAP: PL/SQL - LDAP get_dn error
ORA-31211 DBMS_LDAP: PL/SQL - Invalid LDAP entry dn
ORA-31212 DBMS_LDAP: PL/SQL - Invalid LDAP mod_array
ORA-31213 DBMS_LDAP: PL/SQL - Invalid LDAP mod option
ORA-31214 DBMS_LDAP: PL/SQL - Invalid LDAP mod type
ORA-31215 DBMS_LDAP: PL/SQL - Invalid LDAP mod value
ORA-31216 DBMS_LDAP: PL/SQL - Invalid LDAP rdn
ORA-31217 DBMS_LDAP: PL/SQL - Invalid LDAP newparent
ORA-31218 DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn
ORA-31219 DBMS_LDAP: PL/SQL - Invalid LDAP notypes
ORA-31220 DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location
ORA-31221 DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd
ORA-31222 DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode
ORA-31398 DBMS_LDAP: Shared servers are not supported.
ORA-31399 Cannot contact LDAP server string at port number
ORA-31401 change source string is not an existing asynchronous change source
ORA-31402 unrecognized parameter string
ORA-31403 change table string already contains a column string
ORA-31404 all input parameters are null
ORA-31405 cannot make changes while change set string is advancing
ORA-31406 change source string is referenced by a change set
ORA-31407 end_date must be greater than the begin_date
ORA-31408 illegal value specified for begin_scn or end_scn
ORA-31409 one or more values for input parameters are incorrect
ORA-31410 change set string is not an asynchronous change set
ORA-31411 change set string is referenced by a change table
ORA-31412 change set string is disabled and cannot be advanced
ORA-31413 change set string is currently being advanced
ORA-31414 error(s) occurred during change table advance
ORA-31415 change set string does not exist
ORA-31416 illegal SOURCE_COLMAP value
ORA-31417 column list contains control column string
ORA-31418 source schema string does not exist
ORA-31419 source table string does not exist
ORA-31420 unable to submit the purge job
ORA-31421 change table does not exist
ORA-31422 owner schema string does not exist
ORA-31423 change table string does not contain column string
ORA-31424 change table has active subscriptions
ORA-31425 subscription handle does not exist
ORA-31426 cannot modify active subscriptions
ORA-31427 source table string already subscribed
ORA-31428 no publication contains all the specified columns
ORA-31429 subscription handle has not been activated
ORA-31430 change view exists
ORA-31431 all source tables must belong to the synchronous change set
ORA-31432 invalid source table
ORA-31433 change view does not exist
ORA-31434 purge is currently running
ORA-31435 an error occurred during the purge operation
ORA-31436 duplicate change source string
ORA-31437 duplicate change set string
ORA-31438 duplicate change table string
ORA-31439 subscription is already active
ORA-31440 change set string is empty and cannot be advanced
ORA-31441 table is not a change table
ORA-31442 operation timed out while acquiring lock on string
ORA-31443 deadlock detected while acquiring lock on string
ORA-31444 parameter error while acquiring lock on string
ORA-31445 invalid lock handle while acquiring lock on string
ORA-31447 cannot create change tables in the SYS schema
ORA-31448 illegal value for change_source
ORA-31449 illegal value for set_name
ORA-31450 illegal value for change_table_name
ORA-31451 illegal value string for capture_values, expecting: OLD, NEW, or BOTH
ORA-31452 illegal value string for parameter, expecting: Y or N
ORA-31453 illegal value string for parameter, expecting: Y, N, or NULL
ORA-31454 illegal value string for operation parameter, expecting: ADD or DROP
ORA-31455 nothing to ALTER
ORA-31456 error executing a procedure in the DBMS_CDC_UTILITY package
ORA-31457 maximum length of description field exceeded
ORA-31459 system triggers for DBMS_CDC_PUBLISH package are not installed
ORA-31460 logfile location string is not an existing directory
ORA-31461 logfile location string contains no files that match pattern string
ORA-31462 internal error while accessing metadata
ORA-31463 logfile location string is an empty directory
ORA-31464 target table for the change table no longer exists
ORA-31465 cannot obtain a lock on the subscription handle
ORA-31466 no publications found
ORA-31467 no column found in the source table
ORA-31470 asynchronous change tables must contain the RSID$ column
ORA-31471 illegal OBJECT_ID value
ORA-31472 Importing Change Data Capture version string.string is too new
ORA-31475 redo log catalog contains no metadata for the source table
ORA-31476 a change table data column is missing from the source table
ORA-31495 error in synchronous change table on "string"."string"
ORA-31496 must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
ORA-31600 invalid input value string for parameter string in function string
ORA-31601 Function string cannot be called now that fetch has begun
ORA-31602 parameter string value "string" in function string inconsistent with string
ORA-31603 object "string" of type string not found in schema "string"
ORA-31604 invalid string parameter "string" for object type string in function string
ORA-31605 the following was returned from string in routine string: LPX-number: string
ORA-31606 XML context number does not match any previously allocated context
ORA-31607 Function string is inconsistent with transform.
ORA-31608 specified object of type string not found
ORA-31609 error loading file "string" from file system directory "string"
ORA-32001 write to SPFILE requested but no SPFILE specified at startup
ORA-32002 cannot create SPFILE already being used by the instance
ORA-32004 obsolete and/or deprecated parameter(s) specified
ORA-32005 error while parsing size specification [string]
ORA-32006 string initialization parameter has been deprecated
ORA-32008 error while processing parameter update at instance string
ORA-32009 cannot reset the memory value for instance string from instance string
ORA-32010 cannot find entry to delete in SPFILE
ORA-32011 cannot restore SPFILE to location already being used by the instance
ORA-32012 failure in processing system parameters from restored SPFILE
ORA-32013 failure in verifying parameters from the restored SPFILE
ORA-32014 error processing parameter "string" from the SPFILE restore image
ORA-32015 unable to restore SPFILE
ORA-32016 parameter "string" cannot be updated in SPFILE
ORA-32017 failure in updating SPFILE
ORA-32031 illegal reference of a query name in WITH clause
ORA-32032 free temporary object number not available
ORA-32033 unsupported column aliasing
ORA-32034 unsupported use of WITH clause
ORA-32035 unreferenced query name defined in WITH clause
ORA-32036 unsupported case for inlining of query name in WITH clause
ORA-32037 unsupported use of LEVEL in membership condition
ORA-32050 string operation failed
ORA-32051 mapping service not available
ORA-32052 failed to start mapping service
ORA-32053 operation not supported
ORA-32054 lost communication with FMPUTL process
ORA-32055 invalid file type
ORA-32056 invalid number of extents
ORA-32057 invalid lock mode
ORA-32058 operation restricted to SYSDBA users
ORA-32059 deadlock detected on mapping structures
ORA-32060 channel failure
ORA-32100 operation invalid on transient object
ORA-32101 cannot create OCI Environment
ORA-32105 invalid connection passed to the migrate method
ORA-32106 array fetch not allowed without setBuffer on all columns
ORA-32107 internal OCI memory allocation failure
ORA-32108 max column or parameter size not specified
ORA-32109 invalid column or parameter position
ORA-32110 Connection not specified
ORA-32111 The size of the vector does not match the size of the VARRAY
ORA-32112 Call not applicable until an attribute has been fetched
ORA-32113 Null object passed
ORA-32114 Cannot perform operation on a null LOB
ORA-32115 LOBs do not belong to any connection
ORA-32116 Buffer size is less than amount specified
ORA-32117 Source LOB is null
ORA-32118 Cannot perform operation on a null FILE
ORA-32119 FILEs do not belong to any connection
ORA-32120 Buffer size is less than amount specified
ORA-32121 Source FILE is null
ORA-32122 Statement invalidated, cannot get metadata
ORA-32123 Attribute number is out of range
ORA-32124 Illegal attribute passed
ORA-32125 Attribute type is not appropriate
ORA-32126 Cannot perform operations on a null REF
ORA-32127 REFs do not belong to any connection
ORA-32128 setDataBuffer called after fetch has started
ORA-32129 cannot get information about this column
ORA-32130 invalid offset/index referenced in Bytes
ORA-32131 bind data type cannot be changed
ORA-32132 maximum iterations cannot be changed
ORA-32133 Cannot get stream from LOB/FILE
ORA-32134 Cannot assign LOBs
ORA-32135 Cannot assign FILEs
ORA-32136 Cannot perform operation on an invalid stream
ORA-32137 Cannot perform read/write operation on stream
ORA-32138 Cannot perform read/write operation on stream
ORA-32139 Cannot write to the stream
ORA-32140 cannot perform this operation on stream
ORA-32141 get method does not match the type of the parameter
ORA-32142 maximum number of iterations exceeded
ORA-32143 Environment not specified
ORA-32144 Cannot perform operation on a null interval
ORA-32145 Environment not specified
ORA-32146 Cannot perform operation on a null date
ORA-32147 Environment not specified
ORA-32148 Cannot perform operation on a null time
ORA-32149 Environment not specified
ORA-32150 Cannot perform operation on a null timestamp
ORA-32151 Environment not specified
ORA-32152 Cannot perform operation on a null number
ORA-32153 Environment not specified
ORA-32154 Anydata context not specified
ORA-32155 Anydata not specified
ORA-32156 Cannot perform operation on stream
ORA-32158 Invalid type passed
ORA-32159 Cannot set prefetch options for a null Type
ORA-32160 Argument out of range
ORA-32161 Cannot perform piecewise fetch
ORA-32162 Read/Write SQL method not registered
ORA-32300 cannot drop a secondary materialized view "string"."string"
ORA-32301 object-relational materialized views must be primary key based
ORA-32302 object materialized views must be object ID based
ORA-32303 mviews with user-defined types cannot reference multiple master sites
ORA-32304 materialized views with user-defined types cannot use prebuilt table
ORA-32305 RepAPI materialized views with user-defined types are not supported
ORA-32306 updatable materialized views with user-defined types must use SELECT *
ORA-32307 must use FROM ONLY clause when referencing an object table
ORA-32308 object materialized views must use SELECT *
ORA-32309 object mview type "string"."string" does not match the master table type
ORA-32310 object materialized views must select from an object table
ORA-32311 materialized view definition query selects an unsupported user-defined type
ORA-32312 cannot refresh a secondary materialized view "string"."string"
ORA-32313 REFRESH FAST of "string"."string" unsupported after PMOPs
ORA-32314 REFRESH FAST of "string"."string" unsupported after deletes/updates
ORA-32315 REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
ORA-32316 REFRESH FAST of "string"."string" unsupported after mixed DML
ORA-32317 cannot run a job from a job
ORA-32318 cannot rename a materialized view
ORA-32319 Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
ORA-32320 REFRESH FAST of "string"."string" unsupported after container table PMOPs
ORA-32321 REFRESH FAST of "string"."string" unsupported after detail table TRUNCATE
ORA-32330 invalid operation on online redefinition interim table "string"."string"
ORA-32331 type "string"."string" is incompatible with the master site
ORA-32332 cannot refresh materialized view "string"."string" as type evolution has occurred
ORA-32333 disable table scn update for Materialized view
ORA-32334 cannot create prebuilt materialized view on a table already referenced by a materialized view
ORA-32335 dimension must have at least one level
ORA-32336 cannot use USING NO INDEX to create materialized view "string"."string"
ORA-32337 cannot alter materialized view with pending changes refresh on commit
ORA-32400 cannot use object id columns from materialized view log on "string"."string"
ORA-32401 materialized view log on "string"."string" does not have new values
ORA-32403 cannot use new values from mv log on "string"."string"
ORA-32404 snapshot log uses Change Data Capture which is not enabled for this database
ORA-32500 Dirname 'string' cannot exceed 'number' characters
ORA-32501 Writing SGA to file failed
ORA-32502 Cannot execute command. Flash Freeze is not in effect
ORA-32503 Mapping SGA from file failed
ORA-32504 expecting one of string, string, string, or string but found string
ORA-32505 too many watchpoints
ORA-32506 expecting one of string, string, or string but found string
ORA-32507 expecting string but found string
ORA-32508 no such watchpoint id
ORA-32509 watchpoint was already deleted
ORA-32510 cannot create watchpoint on unreadable memory
ORA-32511 cannot create watchpoint in memory needed by watchpointing code
ORA-32550 Replacement occurred despite hint to the contrary
ORA-32575 Explicit column default is not supported for modifying views
ORA-32576 missing TYPE keyword
ORA-32577 username must be SYS or SYSTEM
ORA-32578 password for SYS already specified
ORA-32579 password for SYSTEM already specified
ORA-32580 both SYS and SYSTEM passwords must be provided
ORA-32581 missing or invalid password
ORA-32582 table function with left correlation to a table cannot also be left outer-joined to the table
ORA-32600 RETENTION and PCTVERSION cannot be used together
ORA-32601 value for retention cannot be provided
ORA-32602 FREEPOOLS and FREELIST GROUPS cannot be used together
ORA-32603 invalid FREEPOOLS LOB storage option value
ORA-32604 invalid REBUILD option
ORA-32605 invalid REBUILD option
ORA-32700 error occurred in DIAG Group Service
ORA-32730 Command cannot be executed on remote instance
ORA-32731 Another Parallel Oradebug session is in progress
ORA-32732 Parallel Oradebug session is aborted
ORA-32733 Error occurred when executing Parallel Oradebug
ORA-32734 Error occurred when sending Oradebug command to remote DIAGs
ORA-32735 DIAG process is not running in the instance
ORA-32736 Hang analysis aborted due to wrong message type
ORA-32737 Hang analysis aborted due to failed memory allocation
ORA-32738 Hang analysis aborted due to failed memory copy
ORA-32739 Hang analysis aborted due to failed heap re-grow
ORA-32766 instr with negative offset: use varchar semantics on LOBs
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
1016
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
