Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
ORA-24280 invalid input value for parameter string
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.
ORA-24281 invalid access past the maximum size of LOB parameter string
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.
ORA-24300 bad value for mode
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.
ORA-24301 null host specified in thread-safe logon
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.
ORA-24302 host connection in use by another thread
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.
ORA-24303 call not supported in non-deferred linkage
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.
ORA-24304 datatype not allowed for this call
Cause: Data of this datatype cannot be sent or fetched in pieces.
Action: Use other bind or define calls for this datatype.
ORA-24305 bad bind or define context
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.
ORA-24306 bad buffer for piece
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.
ORA-24307 invalid length for piece
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.
ORA-24308 illegal define position
Cause: Call to modify attributes was done for a non-existent position.
Action: Verify that a define has been done for this position.
ORA-24309 already connected to a server
Cause: This server handle is already attached to a server.
Action: Disconnect from the server and then retry the call to establish a connection.
ORA-24310 length specified for null connect string
Cause: The connect string is null, but a length was specified for it.
Action: Set length to zero if connect string is null.
ORA-24311 memory initialization failed
Cause: Cannot initialize user memory.
Action: Contact Oracle Customer Support.
ORA-24312 illegal parameters specified for allocating user memory
Cause: An illegal size or null pointer was specified for user memory.
Action: Specify a legal size and a valid pointer for user memory.
ORA-24313 user already authenticated
Cause: A user has already been authenticated on this service handle.
Action: Terminate the service context before using it for another user.
ORA-24314 service handle not initialized
Cause: The server context does not done exist.
Action: Establish the server context in the service context.
ORA-24315 illegal attribute type
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.
ORA-24316 illegal handle type
Cause: An illegal handle type was specified.
Action: Consult the Oracle Call Interface Programmer's Guide. to specify a valid handle type.
ORA-24317 define handle used in a different position
Cause: A define was done with an existing handle on a different position.
Action: Specify the same position as before on a redefine.
ORA-24318 call not allowed for scalar data types
Cause: This call is valid only for object types.
Action: Verify that the data-type for this variable is an object type.
ORA-24319 unable to allocate memory
Cause: Process was unable to allocate memory to store diagnostics.
Action: Terminate other processes in order to reclaim needed memory.
ORA-24320 unable to initialize a mutex
Cause: An attempt to initialize a MUTEX failed.
Action: Contact Oracle Customer Support.
ORA-24321 inconsistent parameters passed
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.
ORA-24322 unable to delete an initialized mutex
Cause: An attempt to delete an initialized MUTEX failed.
Action: Contact Oracle Customer Support.
ORA-24323 value not allowed
Cause: A null or invalid value was passed in for a mandatory parameter.
Action: Verify that all mandatory parameters are properly initialized.
ORA-24324 service handle not 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.
ORA-24325 this OCI operation is not currently allowed
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.
ORA-24326 handle passed in is already initialized
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.
ORA-24327 need explicit attach before authenticating a user
Cause: A server context must be initialized before creating a session.
Action: Create and initialize a server handle.
ORA-24328 illegal attribute value
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.
ORA-24329 invalid character set identifier
Cause: The character set identifier specified is invalid.
Action: Specify a valid character set identifier in the OCI call.
ORA-24330 internal OCI error
Cause: An internal OCI error has occurred.
Action: Contact Oracle Customer Support.
ORA-24331 user buffer too small
Cause: The user buffer to contain the output data is too small.
Action: Specify a bigger buffer.
ORA-24332 invalid object type
Cause: An invalid object type is requested for the describe call.
Action: Specify a valid object type to the describe call.
ORA-24333 zero iteration count
Cause: An iteration count of zero was specified for the statement.
Action: Specify the number of times this statement must be executed.
ORA-24334 no descriptor for this position
Cause: The application is trying to get a descriptor from a handle for an illegal position.
Action: Check the position number.
ORA-24335 cannot support more than 1000 columns
Cause: The number of columns exceeds the maximum number supported.
Action: Specify a number of columns less than 1000.
ORA-24336 invalid result set descriptor
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.
ORA-24337 statement handle not prepared
Cause: A statement cannot be executed before making preparing a request.
Action: Prepare a statement before attempting to execute it.
ORA-24338 statement handle not executed
Cause: A fetch was attempted before executing a statement handle.
Action: Execute a statement and then fetch the data.
ORA-24339 cannot set server group name after connecting to server
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.
ORA-24340 cannot support more than 255 columns
Cause: The number of columns exceeds maximum supported by the server.
Action: Limit your operation to 255 columns.
ORA-24341 bad mode specified
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.
ORA-24342 unable to destroy a mutex
Cause: An attempt to destroy a MUTEX failed.
Action: Contact Oracle Customer Support.
ORA-24343 user defined callback error
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.
ORA-24344 success with compilation error
Cause: A SQL or PL/SQL compilation error occurred.
Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
ORA-24345 A Truncation or null fetch error occurred
Cause: A truncation or a null fetch error.
Action: Make sure that the buffer size is long enough to store the returned data.
ORA-24346 cannot execute without binding variables
Cause: None of the bind variables in the SQL statement are bound.
Action: Bind all the variables before the execute is done.
ORA-24347 Warning of a NULL column in an aggregate function
Cause: A null column was processed by an aggregate function.
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24350 OCI call not allowed
Cause: OCI used is not permitted from external procedures.
Action: Refer to the Oracle Call Interface Programmer's Guide. for usage restrictions.
ORA-24351 invalid date passed into OCI call
Cause: A bad date was passed into one of the OCI calls.
Action: Check your date bind values and correct them.
ORA-24352 invalid COBOL display type passed into OCI call
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.
ORA-24353 user buffer too small to accommodate COBOL display type
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.
ORA-24354 number fetched too large to fit in COBOL display type buffer.
Cause: The number fetched was beyond the range that can be displayed.
Action: Check the number in the database.
ORA-24355 attempt to store a negative number in an Unsigned Display type.
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.
ORA-24356 internal error while converting from to COBOL display type.
Cause: An internal error was encountered during conversion to COBOL display type.
Action: Contact Oracle Customer Support.
ORA-24357 internal error while converting from to OCIDate.
Cause: An internal error was encountered during conversion to OCIDate type.
Action: Contact Oracle Customer Support.
ORA-24358 OCIBindObject not invoked for a Object type or Reference
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.
ORA-24359 OCIDefineObject not invoked for a Object type or Reference
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.
ORA-24360 Type Descriptor Object not specified for Object Bind/Define
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.
ORA-24361 basic bind call not invoked before invoking advanced bind call
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.
ORA-24362 improper use of the character count flag
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.
ORA-24363 measurements in characters illegal here
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.
ORA-24364 internal error while padding blanks
Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally.
Action: Contact Oracle Customer Support.
ORA-24365 error in character conversion
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.
ORA-24366 migratable user handle is set in service handle
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.
ORA-24367 user handle has not been set in service handle
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.
ORA-24368 OCI mutex counter non-zero when freeing a handle
Cause: This is an internal OCI error.
Action: Contact Oracle Customer Support.
ORA-24369 required callbacks not registered for one or more bind handles
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.
ORA-24370 illegal piecewise operation attempted
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.
ORA-24371 data would not fit in current prefetch buffer
Cause: An internal OCI error has occurred.
Action: Contact Oracle Customer Support.
ORA-24372 invalid object for describe
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.
ORA-24373 invalid length specified for statement
Cause: The length specified for the statement is either 0 or too large.
Action: Specify a valid length for the statement.
ORA-24374 define not done before fetch or execute and fetch
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.
ORA-24375 Cannot use V6 syntax when talking to a V8 server
Cause: V6 syntax is no longer supported in V8 server.
Action: Change syntax to V7 syntax or higher.
ORA-24376 cannot register/get user callback for non-environment handle
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.
ORA-24377 invalid OCI function code
Cause: An invalid function code was used to register or get user callback.
Action: Use a valid OCI function code.
ORA-24378 user callbacks not allowed for this call
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.
ORA-24379 invalid user callback type
Cause: An invalid type of user callback was specified.
Action: Specify a valid user callback type.
ORA-24380 invalid mode specification
Cause: The mode parameter in an OCIU* call is invalid.
Action: Use only a valid mode parameter.
ORA-24381 error(s) in array DML
Cause: One or more rows failed in the DML.
Action: Refer to the error stack in the error handle.
ORA-24382 statement handled already executed or described
Cause: The statement handle was executed or described successfully before.
Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
ORA-24383 Overflow segment of an IOT cannot be described
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.
Action: Use OCIDescribeAny to describe only documented objects.
ORA-24750 incorrect size of attribute
Cause: Transaction ID attribute size is incorrect.
Action: Verify that the size parameter is correct.
ORA-24752 OCI_TRANS_NEW flag must be specified for local transactions
Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW.
Action: Use OCI_TRANS_NEW when starting local transactions.
ORA-24753 local transactions cannot be detached
Cause: An attempt to detach a local transaction was made.
Action: Local transactions may only be committed or rolled back.
ORA-24754 cannot start new transaction with an active transaction
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.
ORA-24755 OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
Cause: These flags are currently not supported.
Action: No action required.
ORA-24756 transaction does not exist
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.
ORA-24757 duplicate transaction identifier
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.
ORA-24758 not attached to the requested transaction
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.
ORA-24759 invalid transaction start flags
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.
ORA-24760 invalid isolation level flags
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.
ORA-24761 transaction rolled back
Cause: The application tried to commit a transaction and the server rolled it back.
Action: No action required.
ORA-24762 server failed due to unspecified error
Cause: An internal error has occurred in the server commit protocol.
Action: Contact Oracle Customer Support.
ORA-24763 transaction operation cannot be completed now
Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction.
Action: Retry the operation later.
ORA-24764 transaction branch has been heuristically committed
Cause: This is an informational message.
Action: No action required.
ORA-24765 transaction branch has been heuristically rolled back
Cause: This is an informational message.
Action: No action required.
ORA-24766 transaction branch has been partly committed and aborted
Cause: This is an informational message.
Action: No action required.
ORA-24767 transaction was read-only and has been committed
Cause: This is an informational message.
Action: No action required.
ORA-24768 commit protocol error occured in the server
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
ORA-24769 cannot forget an active transaction
Cause: Transaction identifier refers to an active transaction.
Action: Verify that the identifier of an active transaction was not passed as an argument.
ORA-24770 cannot forget a prepared transaction
Cause: Transaction identifier refers to a prepared transaction.
Action: Verify that the identifier of a prepared transaction was not passed as an argument.
ORA-24771 cannot detach, prepare or forget a local transaction
Cause: Service handle contains a local transaction context.
Action: Verify that the transaction context does not refer to a local transaction.
ORA-24772 Cannot mix tightly-coupled and loosely-coupled branches
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 Customer Support.
ORA-24773 invalid transaction type flags
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
Action: Verify that the right parameters are being used.
ORA-24774 cannot switch to specified transaction
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.
ORA-24775 cannot prepare or commit transaction with non-zero lock value
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.
ORA-24776 cannot start a new 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.
ORA-24777 use of non-migratable database link not allowed
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.
ORA-24778 cannot open connections
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 Customer Support.
ORA-24779 detach not allowed with open remote cursor
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.
ORA-24801 illegal parameter value in OCI lob function
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.
ORA-24802 user defined lob read callback error
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.
ORA-24803 illegal parameter value in lob read function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact your Oracle Customer Support.
ORA-24804 illegal parameter value in lob write function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact your Oracle Customer Support.
ORA-24805 LOB type mismatch
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.
ORA-24806 LOB form mismatch
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.
ORA-24807 LOB form mismatch
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.
ORA-24808 streaming of lob data is not allowed when using lob buffering
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.
ORA-24809 amount specified will not fit in the lob buffers
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.
ORA-24810 attempting to write more data than indicated
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.
ORA-24811 less data provided for writing than 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.
ORA-24812 character set conversion to or from UCS2 failed
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 Customer Support.
ORA-24813 cannot send or receive an unsupported LOB
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.
ORA-24850 failed to startup shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting the shared subsystem.
Action: Contact Oracle Customer Support.
ORA-24851 failed to connect to shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem.
Action: Contact Oracle Customer Support.
ORA-24852 protocol error during statement execution
Cause: An internal protocol error occurred while receiving describe data from the server during execution of a statement.
Action: Contact Oracle Customer Support.
ORA-24853 failed to connect thread to shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem.
Action: Contact Oracle Customer Support.
ORA-24900 invalid or unsupported mode paramater passed in call
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
Action: Correct the mode parameter passed into OCI.
ORA-24901 handles belonging to different environments passed into an OCI call
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.
ORA-24902 invalid subscription name or name-length in subscription handle
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.
ORA-24903 invalid namespace attribute passed into OCI 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.
ORA-24904 invalid callback attribute passed into OCI 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.
ORA-25000 invalid use of bind variable in trigger WHEN clause
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.
ORA-25001 cannot create this trigger type on views
Cause: Only INSTEAD OF triggers can be created on a view.
Action: Change the trigger type to INSTEAD OF.
ORA-25002 cannot create INSTEAD OF triggers on tables
Cause: Only BEFORE or AFTER triggers can be created on a table.
Action: Change the trigger type to BEFORE or AFTER.
ORA-25003 cannot change NEW values for this column type in trigger
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.
ORA-25004 WHEN clause is not allowed in INSTEAD OF triggers
Cause: WHEN clause is specified in an INSTEAD OF trigger.
Action: Remove the WHEN clause when creating an INSTEAD OF trigger.
ORA-25005 cannot CREATE INSTEAD OF trigger on a read-only view
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.
ORA-25006 cannot specify this column in UPDATE OF clause
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.
ORA-25007 functions or methods not allowed in WHEN 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.
ORA-25008 no implicit conversion to LOB datatype in instead-of trigger
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.
ORA-25009 Nested table clause allowed only for INSTEAD OF triggers
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.
ORA-25010 Invalid nested table column name in nested table clause
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.
ORA-25012 PARENT and NEW values cannot be identical
Cause: The referencing clause specifies identical values for PARENT and OLD.
Action: Respecify either the PARENT or NEW referencing value.
ORA-25013 OLD and PARENT values cannot be identical
Cause: The referencing clause specifies identical values for OLD and PARENT.
Action: Respecify either the OLD or PARENT referencing value.
ORA-25014 cannot change the value of a PARENT reference variable
Cause: Parent values can only be read and not changed.
Action: Do not attempt to change a Parent variable.
ORA-25015 cannot perform DML on this nested table view column
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.
ORA-25016 cannot specify column list for insert into nested table view column
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.
ORA-25017 cannot reference NEW ROWID for movable rows in before triggers
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.
ORA-25100 TABLESPACE option can only be used with ALTER INDEX REBUILD
Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD option.
Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name.
ORA-25101 duplicate REBUILD option specification
Cause: The REBUILD option to ALTER INDEX is specified more than once.
Action: Specify the option at most once.
ORA-25102 PARALLEL option can only be used with ALTER INDEX REBUILD
Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD option.
Action: Use ALTER INDEX REBUILD.
ORA-25103 NOPARALLEL option can only be used with ALTER INDEX REBUILD
Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD option.
Action: Use ALTER INDEX REBUILD.
ORA-25104 UNRECOVERABLE option can only be used with ALTER INDEX REBUILD
Cause: The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option.
Action: Use ALTER INDEX REBUILD.
ORA-25105 RECOVERABLE option can only be used with ALTER INDEX REBUILD
Cause: The RECOVERABLE option to ALTER INDEX was used without the REBUILD option.
Action: Use ALTER INDEX REBUILD.
ORA-25106 only one of PARALLEL or NOPARALLEL clause may be specified
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.
ORA-25107 duplicate TABLESPACE option specification
Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.
Action: Remove all but one of the TABLESPACE clauses.
ORA-25108 standby lock name space exceeds size limit of string characters
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.
ORA-25109 standby lock name space has illegal character 'string'
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.
ORA-25110 NOSORT may not be used with a bitmap index
Cause: An attempt was made to create a bitmap index using the NOSORT option.
Action: Remove NOSORT from the CREATE BITMAP INDEX statement.
ORA-25111 creation of BITMAP cluster indices is not supported
Cause: An attempt was made to create a cluster index with the BITMAP attribute.
Action: Remove BITMAP from the CREATE INDEX statement.
ORA-25112 maximum number of BITMAP index columns is 30
Cause: Too many columns were specified for the index.
Action: Create an index on fewer columns.
ORA-25113 GLOBAL may not be used with a bitmap index
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.
ORA-25114 invalid file number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid file number was used in dumping a datafile or temporary file.
Action: Specify a valid file number.
ORA-25115 duplicate BLOCK option specification
Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.
Action: Specify only one BLOCK option.
ORA-25116 invalid block number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid block number was used in dumping a datafile or temporary file.
Action: Specify a valid block number.
ORA-25117 MIN/MAX/Block Number expected
Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25118 invalid DUMP DATAFILE/TEMPFILE option
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25119 LOGGING/NOLOGGING option already specified
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.
Action: Remove all but one of the logging specifications.
ORA-25120 MINIMUM EXTENT option already specified
Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.
Action: Remove all but one of the MINIMUM EXTENT specifications.
ORA-25121 MINIMUM EXTENT value greater than maximum extent size
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.
ORA-25122 Only LOCAL bitmap indexes are permitted on partitioned tables
Cause: An attempt was made to create a global bitmap index on a partitioned table.
Action: Create a local bitmap index instead.
ORA-25123 Too many components specified in the name.
Cause: More components per name than is allowed were specified.
Action: Check the name specified for the operation.
ORA-25124 Database link name not allowed.
Cause: A database link name was specified when it is not permitted.
Action: Check the name specified for the operation.
ORA-25125 BUFFER_POOL storage option not allowed
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.
ORA-25126 Invalid name specified for BUFFER_POOL
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.
ORA-25127 RELY not allowed in NOT NULL constraint
Cause: An attempt was made to set RELY on for NOT NULL constraint.
Action: Only NORELY may be specified for a NOT NULL constraint.
ORA-25128 No insert/update/delete on table with constraint (string.string) disabled and validated
Cause: An attempt was made to insert/update/delete on table with DISABLE VALIDATE constraint.
Action: Change the constraint's states.
ORA-25129 cannot modify constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Try again with a constraint that does exist for this table.
ORA-25130 cannot modify primary key - primary key not defined for table
Cause: An attempt was made to modify a primary key that is not defined for the table.
Action: No action required.
ORA-25131 cannot modify unique(string) - unique key not defined for table
Cause: An attempt was made to modify a unique key that is not defined for the table.
Action: No action required.
ORA-25132 UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
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.
ORA-25133 duplicate SINGLE TABLE option specified
Cause: The SINGLE TABLE option was specified more than once.
Action: Specify the SINGLE TABLE option only once.
ORA-25134 keyword TABLE expected
Cause: The keyword TABLE is missing from the SINGLE TABLE option.
Action: Place the keyword TABLE after the keyword SINGLE in the command.
ORA-25135 cannot use the SINGLE TABLE option
Cause: The SINGLE TABLE option is only valid for hash clusters.
Action: Do not specify the SINGLE TABLE option.
ORA-25136 this cluster can contain only one table
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.
ORA-25137 Data value out of range
Cause: Value from cast operand is larger than cast target size.
Action: Increase size of cast target.
ORA-25138 string initialization parameter has been made obsolete
Cause: An obsolete initialization parameter has been specified.
Action: The system will come up, but parameters must be examined.
ORA-25139 invalid option for CREATE TEMPORARY TABLESPACE
Cause: An invalid option appears.
Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM.
ORA-25140 string space policy cannot be specified for the string extent management
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
ORA-25141 invalid EXTENT MANAGEMENT clause
Cause: An invalid option appears for EXTENT MANAGEMENT clause.
Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE.
ORA-25142 default storage clause specified twice
Cause: Default storage clause was specified twice for create tablespace.
Action: Specify it once.
ORA-25143 default storage clause is not compatible with allocation policy
Cause: Default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy.
Action: Omit the storage clause.
ORA-25144 invalid option for CREATE TABLESPACE with TEMPORARY contents
Cause: An invalid option appears.
Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, USER.
ORA-25145 allocation policy already specified
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.
ORA-25146 EXTENT MANAGEMENT option already specified
Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once.
Action: Remove all but one of the EXTENT MANAGEMENT specifications.
ORA-25147 UNIFORM SIZE value greater than maximum extent size
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.
ORA-25148 ONLINE option not permitted
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.
ORA-25149 Columns of UROWID type may not be indexed
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.
ORA-25150 ALTERING of extent parameters not permitted
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.
ORA-25151 Rollback Segment cannot be created in this tablespace
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.
ORA-25152 TEMPFILE cannot be dropped at this time
Cause: An attempt was made to drop a TEMPFILE being used by online users.
Action: The TEMPFILE has been taken offline. Try again later.
ORA-25153 Temporary Tablespace is Empty
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.
ORA-25175 no PRIMARY KEY constraint found
Cause: A PRIMARY KEY constraint must be defined for a table with this organization.
Action: Define a PRIMARY KEY.
ORA-25176 storage specification not permitted for 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.
ORA-25177 UNRECOVERABLE option not permitted
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.
ORA-25178 duplicate PCTTHRESHOLD storage option specification
Cause: The storage option PCTTHRESHOLD is specified more than once.
Action: Specify storage options at most once.
ORA-25179 invalid PCTTHRESHOLD storage option value
Cause: The specified value must be a positive integer.
Action: Specify an appropriate value.
ORA-25180 PCTTHRESHOLD only valid for certain table organizations
Cause: PCTTHRESHOLD can only be specified for tables with certain organizations.
Action: Remove the PCTTHRESHOLD option.
ORA-25181 missing ON keyword for NESTED INDEX
Cause: The ON keyword is required to specify nested index column nest.
Action: Add ON keyword.
ORA-25182 feature not currently available for index-organized tables
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.
ORA-25183 index-organized table top index segment is in a different tablespace
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.
ORA-25184 column name expected
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.
ORA-25185 index column other than last can not be specified for INCLUDE clause
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.
ORA-25186 INCLUDING clause specified for index-organized table without OVERFLOW
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.
ORA-25187 specified exceptions table form incorrect
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use.
ORA-25188 cannot drop/disable/defer the primary key constraint for index-organized tables
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.
ORA-25189 illegal ALTER TABLE option for an index-organized 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).
ORA-25190 an index-organized table maintenance operation may not be combined with other operations
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.
ORA-25191 cannot reference overflow table of an index-organized table
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.
ORA-25192 invalid option for an index-organized 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).
ORA-25193 cannot use COMPRESS option for a single column key
Cause: An attempt was made to use COMPRESS option on single column key.
Action: Remove the COMPRESS option.
ORA-25194 invalid COMPRESS prefix length value
Cause: The specified value must be a positive integer less than the number of key columns.
Action: Specify an appropriate value.
ORA-25195 invalid option for index on an index-organized table
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.
ORA-25196 keyword MOVE in ALTER TABLE MOVE must immediately follow table_name
Cause: MOVE specified after one/more other ALTER options.
Action: Change order of options, MOVE should be first or remove the illegal option(s).
ORA-25197 an overflow segment already exists for the indexed-organized table
Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment.
Action: No action required.
ORA-25198 only range partitioning is supported for index-organized table
Cause: Hash, system, or composite partitioning schemes are not supported.
Action: Select a different partitioning scheme.
ORA-25199 partitioning key of a index-organized table must be a subset of the primary key
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.
ORA-25200 invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
Cause: A NULL parameter was specified for QUEUE_NAME.
Action: Specify a non-NULL queue name.
ORA-25201 invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
ORA-25202 invalid value NULL, string should be non-NULL
Cause: A NULL value was specified for the parameter.
Action: Specify a non-NULL value.
ORA-25203 invalid value string, DELAY should be non-negative
Cause: A negative value or NULL was specified for DELAY.
Action: Specify a non-negative integer for DELAY.
ORA-25204 invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
Cause: An invalid SEQUENCE_DEVIATION was specified.
Action: Specify either the option 'BEFORE' or 'TOP'.
ORA-25205 the QUEUE string.string does not exist
Cause: The specified queue does not exist.
Action: Create the queue first before specifying it for enqueue or dequeue.
ORA-25206 enqueue failed, enqueue to exception queue string.string not permitted
Cause: An attempt was made to enqueue to an exception queue.
Action: Try enqueueing to another queue.
ORA-25207 enqueue failed, queue string.string is disabled from enqueueing
Cause: The queue has been stopped to prevent any further enqueueing.
Action: Enable the queue first by using an administrative operation.
ORA-25208 RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
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.
ORA-25209 invalid value string, EXPIRATION should be non-negative or NEVER
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.
ORA-25210 invalid value for RELATIVE_MSGID, no message in queue with that msgid
Cause: No message in the queue with the MSGID equal to the specified RELATIVE_MSGID.
Action: Try again with a valid RELATIVE_MSGID.
ORA-25211 invalid DELAY specified when using sequence deviation
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.
ORA-25212 invalid PRIORITY specified when using sequence deviation
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.
ORA-25213 message with specified RELATIVE_MSGID has been dequeued
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.
ORA-25215 user_data type and queue type do not match
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.
ORA-25216 invalid recipient, either NAME or ADDRESS must be specified
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.
ORA-25217 enqueue failed, visibility must be IMMEDIATE for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.
Action: Set visibility to IMMEDIATE.
ORA-25218 enqueue failed, delay must be zero for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.
Action: Set delay to zero.
ORA-25219 enqueue failed, sequence deviation not allowed for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.
Action: Do not specify sequence deviation.
ORA-25225 invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
Action: Specify either REMOVE, BROWSE or LOCKED.
ORA-25226 dequeue failed, queue string.string is not enabled for dequeue
Cause: The queue has not been enabled for dequeue.
Action: Enable the queue using START_QUEUE.
ORA-25228 timeout or end-of-fetch during message dequeue from string.string
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.
ORA-25230 invalid value string, WAIT should be non-negative
Cause: A negative value has been specified for WAIT.
Action: Specify a non-negative value or FOREVER.
ORA-25231 cannot dequeue because CONSUMER_NAME not specified
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.
ORA-25232 duplicate recipients specified for message
Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.
Action: Remove the duplicate queue agent and retry the call.
ORA-25233 invalid parameter specified for NAVIGATION
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.
ORA-25234 NEXT_TRANSACTION navigation option invalid for queue table string.string
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.
ORA-25235 fetched all messages in current transaction
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.
ORA-25236 buffer too small for user data
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.
ORA-25237 navigation option used out of sequence
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.
ORA-25238 too many recipients specified for message destination string
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.
ORA-25239 message ID not supplied when dequeuing from exception queue string.string
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.
ORA-25240 message ID and correlation ID specified in dequeue options
Cause: An attempt was made to dequeue by including both a message ID and a correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either one of message ID or correlation ID, or neither ID.
Action: To dequeue a message, specify a message ID or a 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 correlation ID in the dequeue options.
ORA-25241 cannot change correlation ID from string to string without FIRST_MESSAGE option
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.
ORA-25242 cannot change subscriber name from string to string without FIRST_MESSAGE 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.
ORA-25243 CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
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.
ORA-25244 dequeue index key not found, QUEUE string, rowid string
Cause: An internal error was encountered. There may be an inconsistency in the queue table index.
Action: Contact Oracle Customer Support. You may need to provide the trace file and information about reproducing the error.
ORA-25245 agent name cannot be specified if address is a single-consumer queue or an exception queue
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.
ORA-25246 listen failed, the address string is an 8.0 style exception queue
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.
ORA-25247 string is not a recipient of specified message
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.
ORA-25248 duplicate agent specified in the agent list
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.
ORA-25249 dequeue failed, dequeue not allowed for queue string.string
Cause: An attempt was made to dequeue from a non-persistent queue.
Action: Dequeue from a different queue.
ORA-25250 Cannot specify a remote recipient for the message
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
ORA-25251 exceeded maximum number of recipients for message
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.
ORA-25252 listen failed, the address string is a non-persistent queue
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.
ORA-25253 listen failed, queue string.string is not enabled for dequeue
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.
ORA-25254 time-out in LISTEN while waiting for a message
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.
ORA-25255 incorrect subscription string string
Cause: An incorrect subscription string was specified with OCIRegister.
Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form.
ORA-25256 consumer cannot be specified with a single-consumer queue or an exception queue
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.
ORA-25257 consumer must be specified with a multi-consumer queue
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.
ORA-25258 cannot register for notifications on an 8.0 style exception queue
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.
ORA-25259 cannot specify protocol for agent
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.
ORA-25261 JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
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.
ORA-25262 agent name cannot be NULL if address is a multi-consumer queue
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.
ORA-25263 no message in queue string.string with message ID string
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.
ORA-25276 table specified is not a queue table
Cause: An invalid queue table name is specified.
Action: Check the dictionary views to see if the table is a queue table.
ORA-25277 cannot grant or revoke object privilege on release 8.0 compatible queues
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.
ORA-25278 grantee name cannot be NULL
Cause: An attempt was made to specify NULL for the grantee parameter.
Action: Specify a valid grantee parameter.
ORA-25350 maximum number of concurrent transaction branches exceeded
Cause: The limit on the number of concurrent transaction branches has been reached.
Action: Increase the initialization parameter TRANSACTIONS and restart the system.
ORA-25351 transaction is currently in use
Cause: The transaction is currently used by a different session.
Action: Do not switch to a transaction attached to some other session.
ORA-25352 no current transaction
Cause: The user session is not attached to any transaction.
Action: Do not attempt to detach when there is no current transaction.
ORA-25353 branch marked for deletion
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.
ORA-25400 must replay fetch
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.
ORA-25401 can not continue fetches
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.
ORA-25402 transaction must roll back
Cause: A failure occurred while a transaction was active on this connection.
Action: The client must roll back.