Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: 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_SIZE large enough to accommodate.
Cause: Accumulated codepoint length exceeds allowed codepoint length.
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate.
Cause: Incoming data larger than receiving buffer.
Action: Set OCI_MAXDATA/OCI_MAXCHAR_SIZE appropriately 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_TARGET is not a valid MTTR.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
Cause: One value in _DB_MTTR_SIM_TARGET is empty.
Action: Set the value of _DB_MTTR_SIM_TARGET properly.
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_TARGET was not specified.
Action: Set FAST_START_MTTR_TARGET.
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.
Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory.
Action: Set a smaller FAST_START_MTTR_TARGET or 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.
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.
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.
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.
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 following are possible reasons for name mismatches:
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:
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:
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:
Action: Check Net8 administration in the following ways:
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.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
