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.
ORA-25403 could not reconnect
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
Action: Manually reconnect.
ORA-25404 lost instance
Cause: The primary instance has died.
Action: This is an internally used error message and should not be seen by the user.
ORA-25405 transaction status unknown
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.
ORA-25406 could not generate a connect address
Cause: Failover was unable to generate an address for a backup instance.
Action: Contact Oracle Customer Support.
ORA-25407 connection terminated
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.
ORA-25408 can not safely replay call
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.
ORA-25425 connection lost during rollback
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.
ORA-25426 remote instance does not support shared dblinks
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.
ORA-25436 ruleset specified does not exist
Cause: An attempt to access a ruleset was made, but the ruleset referenced does not exist.
Action: Look up the correct name of the ruleset in USER_RULESETS.
ORA-25437 rule string does not exist
Cause: An attempt to access a rule was made, which failed because the rule does not exist.
Action: Look up the rule in the rules storage table, which can be found from USER_RULESETS.
ORA-25438 table specified does not exist
Cause: An attempt to define a ruleset on a table was made, which failed because the rule does not exist.
Action: Define rulesets only on existing tables.
ORA-25440 duplicate ruleset
Cause: An attempt to define a ruleset was made, which failed because a ruleset with the same name exists in the same schema.
Action: Define a ruleset with a different name.
ORA-25441 duplicate rule string
Cause: An attempt to define a rule was made, which failed because a rule with the same name already exists in the same ruleset.
Action: Define a rule with a different name.
ORA-26000 partition load specified but table string is not partitioned
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.
ORA-26001 Index string specified in SORTED INDEXES does not exist on table string
Cause: A non-existent index was specified in the SORTED INDEXES clause.
Action: Do not specify as a SORTED INDEX.
ORA-26002 Table string has index defined upon it.
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.
ORA-26004 Tables loaded through the direct path may not be clustered
Cause: An attempt was made to load a clustered table via the direct path.
Action: Use the conventional path.
ORA-26007 For INSERT option, table must be empty. Error on table string
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.
ORA-26008 NOT NULL column string has a nullif clause
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.
ORA-26009 NOT NULL column string has a defaultif clause which may evaluate to null
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.
ORA-26010 Column string in table string is NOT NULL and is not being loaded
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.
ORA-26011 Tables loaded through the direct path may not be object tables
Cause: An attempt was made to load an object table via the direct path.
Action: Use the conventional path.
ORA-26012 Tables loaded through the direct path may not have object columns
Cause: An attempt was made to load a table with an object column via the direct path.
Action: Use the conventional path.
ORA-26013 Tables loaded through the direct path may not be nested
Cause: An attempt was made to load a nested table via the direct path.
Action: Use the conventional path.
ORA-26014 Tables loaded through the direct path may not have REF columns
Cause: An attempt was made to load a table with a REF column via the direct path.
Action: Use the conventional path.
ORA-26015 Tables loaded through the direct path may not have array columns
Cause: An attempt was made to load a table with an array column via the direct path.
Action: Use the conventional path.
ORA-26016 Record string: Rejected - Error on table string, partition string
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.
ORA-26017 Global indexes not allowed on direct path partition load, table string
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.
ORA-26018 Column string in table string does not exist
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.
ORA-26019 Column string in table string of type string not supported by direct path
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.
ORA-26020 index string.string loaded successfully with string keys
Cause: Non-partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26021 index string.string partition string loaded successfully with string keys
Cause: Partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26022 index string.string was made unusable due to:
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.
ORA-26023 index string.string partition string was made unusable due to:
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.
ORA-26024 SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
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.
ORA-26025 SKIP_INDEX_MAINTENANCE option requested
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.
ORA-26026 unique index string.string initially in unusable state
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.
ORA-26027 unique index string.string partition string initially in unusable state
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.
ORA-26028 index string.string initially in unusable state
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).
ORA-26029 index string.string partition string initially in unusable state
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).
ORA-26030 index string.string had string partitions made unusable due to:
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.
ORA-26031 index maintenance error, the load cannot continue
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.
ORA-26032 index string.string loading aborted after string keys
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.
ORA-26033 error while evaluating index string.string, row string due to:
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.
ORA-26034 end of logical record found when reading length of varying length field
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
ORA-26035 Record string: Rejected - Error on table string, subpartition string
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.
ORA-26036 subpartition load specified but table string is not subpartitioned
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.
ORA-26037 Record string: Rejected - Error on table string, subpartition string
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.
ORA-26038 error converting character length field to a number
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.
ORA-26039 Table string has domain index defined upon it
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.
ORA-26040 Data block was loaded using the NOLOGGING option
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.
ORA-26086 direct path does not support triggers
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.
ORA-26087 direct path does not support referential or check constraints
Cause: A direct path operation is being attempted on a table which has enabled referential integrity or enabled check constraints.
Action: Disable the referential integrity and/or check constraints on the table and try again.
ORA-26088 scalar column 'string' must be specified prior to LOB columns
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.
ORA-26089 LONG column 'string' must be specified last
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.
ORA-26090 row is in partial state
Cause: A direct path operation is being finished, but the server has a row in partial state. The row must be completed (or flushed) before the direct path operation can be finished.
Action: Either complete the row, flush the row, or abort the operation.
ORA-26091 requested direct path operation not supported
Cause: A direct path operation was requested that is not supported
Action: Do not use that operation. Currently, UNLOAD is not supported.
ORA-26092 only LONG or LOB types can be partial
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.
ORA-26093 stream offset does not map to a column array
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.
ORA-26094 stream format error: input column overflow
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.
ORA-26095 unprocessed stream data exists
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).
ORA-26096 transfer size too small for row data (number bytes required)
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.
ORA-26097 unsupported conversion for column string (from type number to type number)
Cause: The direct path API does not support the required conversion.
Action: Make sure the types are correct.
ORA-26098 direct path context is not prepared
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.
ORA-26099 direct path context is already prepared
Cause: OCIDirPathPrepare was called with a context that has already been prepared.
Action: Free the direct path context, set necessary attributes, and call OCIDirPathPrepare.
ORA-26100: unused error
Cause: This error is not used.
Action: No action required.
ORA-26101 tablespace # in file header is string rather than string for file string
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.
ORA-26102 relative file # in file header is string rather than string for file string
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.
ORA-26103 V6 or V7 data file used to create control file
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.
ORA-26500 error on caching "string"."string"
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.
ORA-26501 RepAPI operation failure
Cause: An external RepAPI operation failed.
Action: Consult detail error message.
ORA-26502 error resignal
Cause: An internal service failed and signalled an error.
Action: Consult detail error message.
ORA-26503 internal RepAPI operation failure on object string.string
Cause: An unexpected internal RepAPI failure was detected.
Action: Contact Oracle Customer Support.
ORA-26504 operation not implemented
Cause: The caller requested a RepAPI operation that was not implemented.
Action: Do not issue this call.
ORA-26505 unexpected internal null
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26506 null global context
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26507 null master connection
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid.
ORA-26508 null snapshot connection
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.
ORA-26509 null snapshot control structure
Cause: An internal snapshot control structure could not be obtained.
Action: Check that the owner and users provided are correct.
ORA-26510 snapshot name: 'string' is greater than max. allowed length of string bytes
Cause: The specified snapshot name was too long.
Action: Shorten the snapshot name.
ORA-26511 master table 'string.string' not found
Cause: A RepAPI operation was attempted against a non-existent or invalid master table.
Action: Verify that the master table object exists.
ORA-26512 error pushing transaction to def$error
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.
ORA-26513 push error: master proc. string$RP.string failed for trans:string seq:string
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.
ORA-26514 object 'string.string' not found
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.
ORA-26515 no master log available for 'string.string'
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.
ORA-26516 no push transaction acknowledgement
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.
ORA-26517 snapshot control entry for 'string.string' was not found
Cause: The specified snapshot catalog control record was not found.
Action: Verify that the local snapshot catalog is valid and that the local snapshot is properly defined.
ORA-26518 push queue synchronization error detected
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 snapshot logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
ORA-26519 no memory available to allocate
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.
ORA-26520 internal memory failure
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.
ORA-26521 rpc initialization error
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.
ORA-26522 rpc execution error
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.
ORA-26523 rpc termination error
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.
ORA-26524 nls subsystem initialization failure for product=string, facility=string
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.
ORA-26525 session connection attempt failed for string (@string)
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.
ORA-26526 snapshot sql ddl parse/expansion failed for string.string
Cause: The client SQL snapshot definition query could not be properly parsed by the master Oracle site.
Action: Check that snapshot DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.
ORA-26527 local store callback init phase failed for 'string.string'
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 Customer Support.
ORA-26528 local store callback proc phase failed for 'string.string'
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 Customer Support.
ORA-26529 local store callback term phase failed for 'string.string'
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 Customer Support.
ORA-26530 unable to build snapshot refresh control list
Cause: The snapshot control list could not be constructed. This is generally the result of an error while accessing the local snapshot catalog.
Action: Verify that the named snapshot(s) are properly defined and valid.
ORA-26532 replication parallel push simulated site failure
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.
ORA-26534 collision: tranID number ignored and purged
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).
ORA-26535 number byte row cache insufficient for table with rowsize=number
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.
ORA-26536 refresh was aborted because of conflicts caused by deferred transactions
Cause: There are outstanding conflicts logged in the DEFERROR table at the snapshot'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 snapshot's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
ORA-26563 renaming this table is not allowed
Cause: Attempt to rename a replicated table, an updatable snapshot table or the master table of a snapshot for which a snapshot 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 snapshot.
ORA-26564 string argument is not of specified type
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).
ORA-26565 Call to type_arg made before calling dbms_defer.call
Cause: User invoked type_arg procedure before starting a deferred call.
Action: Invoke various procedures in the correct order.
ORA-26566 Couldn't open connect to string
Cause: Failed to open connection using given database link.
Action: Make sure that the database link is valid and remote m/c is up.
ORA-26571 string.string.string: number of arguments (string) does not match replication catalog
Cause: The number of arguments does not match the replication catalog.
Action: Examine the total number of arguments for the RPC call.
ORA-26572 string.string.string: argument string does not match replication catalog
Cause: The (RPC) call is corrupted.
Action: Examine total number of arguments and each argument for the RPC call.
ORA-26575 remote database does not support replication parallel propagation
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.
ORA-27000 skgfqsbi: failed to initialize storage subsystem (SBT) layer
Cause: SBTINIT returned an error, additional information indicates error.
Action: Verify that vendor's storage subsystem product is operating correctly.
ORA-27001 unsupported device type
Cause: The specified device type is supported on this platform.
Action: Check V$BACKUP_DEVICE for supported device types.
ORA-27002 function called with invalid device structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27003 cannot open file on device allocated with NOIO option
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 Customer Support.
ORA-27004 invalid blocksize specified
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 Customer Support.
ORA-27005 cannot open file for async I/O on device not supporting async
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 Customer Support.
ORA-27006 sbtremove returned error
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.
ORA-27007 failed to open file
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.
ORA-27008 function called with invalid file structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27009 skgfwrt: cannot write to file opened for read
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27010 skgfwrt: write to file failed
Cause: SBTWRITE returned error, additional information indicates error returned from SBTWRITE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27011 skgfrd: cannot read from file opened for write
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27012 skgfrd: read from file failed
Cause: SBTREAD returned error, additional information indicates error returned from SBTREAD.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27013 skgfqdel: cannot delete an open file
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27014 skgfqpini: translation error while expanding SS_UDMPDIR
Cause: Failure of SLTLN in SKGFQPINI.
Action: Check additional return error for more information.
ORA-27015 skgfcls: failed to close the file
Cause: SBTCLOSE returned an error. Additional information indicates error returned from SBTCLOSE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27016 skgfcls: sbtinfo returned error
Cause: Additional information indicates error returned from SBTINFO.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27017 skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
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).
ORA-27018 skgfidev: blocksize in device parms must be multiple of SSTKBLCK
Cause: A blocking factor was specified that is not a multiple of SSTKBLCK.
Action: Additional information indicates the blocking factor provided by user and the value of SSTKBLCK. Specify a value that is a multiple of SSTKBLCK.
ORA-27019 tape filename length exceeds limit (SBTOPMXF)
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.
ORA-27020 named devices not supported
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.
ORA-27021 sequential file handle must be specified
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.
ORA-27022 skgfqsbi: could not allocate memory for media manager
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.
ORA-27023 skgfqsbi: media manager protocol error
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.
ORA-27024 skgfqsbi: sbtinit2 returned error
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.
ORA-27025 skgfqsbi: invalid media manager context area size
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.
ORA-27026 skgfrls: sbtend returned error
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.
ORA-27027 sbtremove2 returned error
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.
ORA-27028 skgfqcre: sbtbackup returned error
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.
ORA-27029 skgfrtrv: sbtrestore returned error
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.
ORA-27030 skgfwrt: sbtwrite2 returned error
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.
ORA-27031 mirror resilvering functions not supported
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27032 skgfrpini: failed to obtain file size limit
Cause: GETRLIMIT system call returned an error.
Action: Check errno.
ORA-27033 skgfrpini: failed to obtain file size limit
Cause: ULIMIT system call returned an error.
Action: Check errno.
ORA-27034 skgfrcre: maximum length of ORACLE_SID exceeded
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.
ORA-27035 logical block size is invalid
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.
ORA-27036 translation error, unable to expand file name
Cause: Additional information indicates SLTLN/SLNRM error, and also indicates which function encountered the error.
Action: Check additional information.
ORA-27037 unable to obtain file status
Cause: STAT system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27038 skgfrcre: file exists
Cause: Trying to create a database file, but file by that name already exists.
Action: Verify that name is correct, specify reuse if necessary.
ORA-27039 create file failed, file size limit reached
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.
ORA-27040 skgfrcre: create error, unable to create file
Cause: Create system call returned an error, unable to create file.
Action: Verify the file name and permissions.
ORA-27041 unable to open file
Cause: Open system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27042 not enough space on raw partition to fullfill request
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 Customer Support.
ORA-27043 unable to seek to beginning of file
Cause: Seek system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27044 unable to write the header block of file
Cause: Write system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27045 unable to close the file
Cause: Close system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27046 file size is not a multiple of logical block size
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.
ORA-27047 unable to read the header block of file
Cause: Read system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27048 skgfifi: file header information is invalid
Cause: Possibly trying to use a non-database file as a database file.
Action: Verify that file is a database file.
ORA-27049 unable to seek to and read the last block
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.
ORA-27050 function called with invalid FIB/IOV structure
Cause: This is an internal error. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27052 unable to flush file data
Cause: FSYNC system call returned error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27053 skgfifi: blocksize in file header not a multiple of logical block size
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.
ORA-27056 skgfrdel: could not delete file
Cause: Unlink system call returned error.
Action: Check errno.
ORA-27057 skgfask: cannot perform async I/O to file
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 Customer Support.
ORA-27058 skgfask: question parameter is invalid
Cause: This is an internal error. An invalid query is being asked.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27059 skgfrsz: could not reduce file size
Cause: FTRUNCATE system call returned error.
Action: Check errno.
ORA-27060 skgfofi: could not set close-on-exec bit on file
Cause: FCNTL system call returned error.
Action: Check errno.
ORA-27061 skgfospo: waiting for async I/Os failed
Cause: AIOWAIT function returned error.
Action: Check errno.
ORA-27062 skgfospo: could not find pending async I/Os
Cause: This is an internal error. There should have been some asynchronous I/Os in the system but a blocking AIOWAIT indicates that there are no more I/Os.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27063 skgfospo: number of bytes read/written is incorrect
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.
ORA-27064 skgfdisp: cannot perform async I/O to file
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 Customer Support.
ORA-27065 skgfdisp: cannot perform async vector I/O to file
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 Customer Support.
ORA-27066 skgfdisp: number of buffers in vector I/O exceeds maximum
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 Customer Support.
ORA-27067 skgfdisp: size of buffer is invalid
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 Customer Support.
ORA-27068 skgfdisp: buffer is not aligned properly
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 Customer Support.
ORA-27069 skgfdisp: attempt to do I/O beyond the range of the file
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 Customer Support.
ORA-27070 skgfdisp: async read/write failed
Cause: AIOREAD/AIOWRITE system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27071 skgfdisp: unable to seek to desired position in file
Cause: LSEEK system call returned error, additional information indicates block number in file to which seek was attempted.
Action: Check errno.
ORA-27072 skgfdisp: I/O error
Cause: READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27073 skgfcfi: async I/Os remaining to be dequeued for this file
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 Customer Support.
ORA-27074 skgfrofl: unable to determine limit for open files
Cause: GETRLIMIT system call returned error.
Action: Check errno.
ORA-27075 skgfrofl: SSTMOFRC constant too large
Cause: This is an internal error.
Action: Check for a trace file and contact Oracle Customer Support.
ORA-27076 skgfrofl: unable to set limit for open files
Cause: SETRLIMIT system call returned error.
Action: Check errno.
ORA-27077 skgfofi: too many files open
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 Customer Support.
ORA-27086 skgfglk: unable to lock file - already in use
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.
ORA-27087 skgfglk: unable to get share lock - file not readable
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.
ORA-27088 skgfglk: unable to get file status
Cause: The file is not open or the file descriptor is invalid.
Action: Make sure the file is open and the descriptor is valid.
ORA-27089 skgfrlk: unable to release advisory lock
Cause: The file lock release failed.
Cause: See the errno.
ORA-27091 skgfqio: unable to queue I/O
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.
ORA-27100 shared memory realm already exists
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.
ORA-27101 shared memory realm does not exist
Cause: Unable to locate shared memory realm.
Action: Verify that the realm is accessible.
ORA-27102 out of memory
Cause: Out of memory.
Action: Consult the trace file for details.
ORA-27103 internal error
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
ORA-27120 unable to removed shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Customer Support.
ORA-27121 unable to determine size of shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Customer Support.
ORA-27122 unable to protect memory
Cause: MPROTECT() call failed.
Action: Contact Oracle Customer Support.
ORA-27123 unable to attach to shared memory segment
Cause: SHMAT() call failed.
Action: Check permissions on segment, contact Oracle Customer Support.
ORA-27124 unable to detach from shared memory segment
Cause: SHMDT() call failed.
Action: Contact Oracle Customer Support.
ORA-27125 unable to create shared memory segment
Cause: SHMGET() call failed.
Action: Contact Oracle Customer Support.
ORA-27126 unable to lock shared memory segment in core
Cause: Insufficient privileges to lock shared memory segment in core.
Action: Make sure the process is running with the necessary privileges.
ORA-27127 unable to unlock shared memory segment
Cause: Insufficient privileges to unlock shared memory segment.
Action: Make sure the process is running with the necessary privileges.
ORA-27128 unable to determine pagesize
Cause: SYSCONF() call failed.
Action: Contact Oracle Customer Support.
ORA-27141 invalid process ID
Cause: Process operation attempted using invalid process ID.
Action: Contact Oracle Customer Support.
ORA-27142 could not create new process
Cause: Operating system call error.
Action: Check errno and if possible increase the number of processes.
ORA-27143 OS system call failure
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27144 attempt to kill process failed
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27145 insufficient resources for requested number of processes
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27146 post/wait initialization failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27147 post/wait reset failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27148 spawn wait error
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27149 assignment out of range
Cause: This is an internal error. A request was made for a conversion too large for the type.
Action: Contact Oracle Customer Support.
ORA-27150 attempt to notify process of pending oradebug call failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27151 buffer not large enough to hold process ID string
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
ORA-27152 attempt to post process failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27153 wait operation failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27154 post/wait create failed
Cause: This is an internal error. Multiple post/wait creates were attempted simultaneously.
Action: Check errno and contact Oracle Customer Support.
ORA-27155 could not execute file
Cause: Operating system call failed.
Action: Check errno and contact Oracle Customer Support.
ORA-27156 request for process information failed
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
ORA-27190 skgfrd: sbtread2 returned error
Cause: SBTREAD 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.
ORA-27191 sbtinfo2 returned error
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.
ORA-27192 skgfcls: sbtclose2 returned error - failed to close file
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.
ORA-27193 sbtinfo2 did not return volume label
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.
ORA-27194 skgfdvcmd: sbtcommand returned error
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.
ORA-27195 proxy copy not supported
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.
ORA-27196 skgfpbk: sbtpcbackup returned error
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.
ORA-27197 skgfprs: sbtpcrestore returned error
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.
ORA-27198 skgfpvl: sbtpcvalidate returned error
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.
ORA-27199 skgfpst: sbtpcstatus returned error
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.
ORA-27200 skgfpgo: sbtpcstart returned error
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.
ORA-27201 skgfpcm: sbtpccommit returned error
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.
ORA-27202 skgfpen: sbtpcend returned error
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.
ORA-27203 skgfpqb: sbtpcquerybackup returned error
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.
ORA-27204 skgfpqr: sbtpcqueryrestore returned error
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.
ORA-27205 skgfpcn: sbtpccancel returned error
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.
ORA-27206 requested file not found in media management catalog
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.
ORA-27300 OS system dependent operation:string failed with status: string
Cause: Operating system call error.
Action: Contact Oracle Customer Support.
ORA-27301 OS failure message: string
Cause: Operating system call error.
Action: Contact Oracle Customer Support.
ORA-27302 failure occurred at: string
Cause: Operating system call error.
Action: Contact Oracle Customer Support.
ORA-27303 additional information: string
Cause: Operating system call error.
Action: Contact Oracle Customer Support.
ORA-27500 inter-instance IPC error
Cause: Most likely operating system call error.
Action: Check extra information and contact Oracle Customer Support.
ORA-27501 IPC error creating a port
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27502 IPC error setting up signal handler
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27504 IPC error querying network address of a port
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27505 IPC error destroying a port
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27506 IPC error connecting to a port
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27507 IPC error disconnecting from a port
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27508 IPC error sending a message
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27509 IPC error receiving a message
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27510 IPC error waiting for a request to complete
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27512 IPC error posting a process
Cause: Operating system call error.
Action: Check errno and contact Oracle Customer Support.
ORA-27528 cannot allocate communication buffers of zero size
Cause: Client is trying to allocate a zero length message.
Action: Refer to KGXP.H for usage of KGXPVALO().
ORA-27529 cannot allocate zero sized communication buffers
Cause: Client is trying to allocate a zero length message.
Action: Refer to KGXP.H for usage of KGXPVALO().
ORA-27530 cannot deallocate pointer to NULL memory
Cause: Client is passing in a NULL pointer for deallocation.
Action: Refer to KGXP.H for usage of KGXPVFRE().
ORA-27531 cannot destroy invalid port
Cause: The port is invalid.
Action: Re-create the port.
ORA-27532 IPC global name service is not supported
Cause: The global name service used by KGXP is not supported.
Action: Either use a different name service, of abort the current process/thread.
ORA-27533 trying to destroy invalid connection identifier
Cause: The connection identifier passed in is invalid.
Action: Check the connection identifier, or abort the process/thread.
ORA-27534 cannot send unaligned message
Cause: The message being sent is not aligned on the required boundaries.
Action: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary.
ORA-27535 exceeded the maximum vectored message size
Cause: An attempt was made to send a vectored message that exceeds the maximum vector size.
Action: Use a smaller vector size.
ORA-27536 multicast message is not aligned on the correct boundary
Cause: The message to multicast is not aligned on the proper boundary.
Action: Align the message appropriately.
ORA-27537 cannot receive messages into unaligned buffers
Cause: The message being posted for receive is not aligned on the required boundary.
Action: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary.
ORA-27538 failed to added accept handle to the free pool
Cause: Could not add an accept handle to the free pool.
Action: Exit the process.
ORA-27539 accept handle free pool is empty. Cannot accept new connections
Cause: The free pool of accept handles is empty.
Action: Add accept handles to the free pool.
ORA-27540 no more communication channels can be created for process/thread. already at maximum.
Cause: The maximum communication channels are already in use for this process/thread.
Action: Destroy connections which are not needed.
ORA-27541 fatal error trying to connect to remote port
Cause: Either the remote address is not valid, or the process is in bad shape.
Action: Destroy all connections, and try to re-establish them.
ORA-27542 failed trying to queue up accept handles
Cause: The OSD would not allow KGXP to queue up the storage necessary to accept new incoming connections.
Action: Check the parameters; if they are okay, abort the process.
ORA-27543 cannot cancel an outstanding request
Cause: The OSD cannot cancel an outstanding request immediately.
Action: Shut down all connections and abort the process.
ORA-27544 memory mapped communication is not supported
Cause: The platform does not support memory communication.
Action: Use the default send/receive.
ORA-28000 the account is locked
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.
ORA-28001 the password has expired
Cause: The user's account has expired and the password needs to be changed.
Action: Change the password or contact the database administrator.
ORA-28002 the password will expire within string days
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.
ORA-28003 password verification for the specified password failed
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.
ORA-28004 invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
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 Oracle Security Server Guide to find out the format of the password verification function.
ORA-28005 invalid logon flags
Cause: The flags are not properly set or conflicting flags are set in making calls.
Action: Call the function with appropriate flags set.
ORA-28006 conflicting values for parameters string and string
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.
ORA-28007 the password cannot be reused
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.
ORA-28008 invalid old password
Cause: Old password supplied is wrong; Hence user cannot be authenticated using old password.
Action: Supply the correct old password for authentication.
ORA-28009 connection to sys should be as sysdba or sysoper
Cause: Connect sys/password is no longer a valid syntax.
Action: Try connect sys/password as sysdba or connect sys/password as sysoper.
ORA-28010 cannot expire external or global accounts
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.
ORA-28020 IDENTIFIED GLOBALLY already specified
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.
ORA-28021 cannot grant global roles
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.
ORA-28022 cannot grant external roles to global user or role
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.
ORA-28023 must revoke grants of this role to other user(s) first
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.
ORA-28024 must revoke grants of external roles to this role/user
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.
ORA-28025 missing or null external name
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
Action: Provide a valid external name.
ORA-28026 user with same external name already exists
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.
ORA-28027 privileged database links may be used by global users
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.
ORA-28028 could not authenticate remote server
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.
ORA-28029 could not authorize remote server for user string
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.
ORA-28030 Server encountered problems accessing LDAP directory service
Cause: Unable to access LDAP directory service.
Action: Contact your system administrator.
ORA-28035 Cannot Get Session Key for Authentication
Cause: Client and server cannot negotiate shared secret during logon.
Action: Contact your system administrator.
ORA-28100 policy function schema string is invalid
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.
ORA-28101 policy already exists
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.
ORA-28102 policy does not exist
Cause: Try to drop/enable/refresh a non-existent policy.
Action: Correct the policy name argument.
ORA-28103 adding a policy to an object owned by SYS is not allowed
Cause: Try to add a policy to a table or a view owned by SYS.
Action: You cannot perform this operation.
ORA-28104 policy function or package is invalid
Cause: The function or package implementing a policy does not exist or was created with errors.
Action: Correct the function or package.
ORA-28106 input value for argument #string is not valid
Cause: Input values for the argument is missing or invalid.
Action: Correct the input values.
ORA-28107 policy was disabled
Cause: Try to flush a disabled policy.
Action: If the policy is supposed to be enforced, it must be enabled.
ORA-28108 circular row level security policies detected
Cause: Policies for the same object reference each other.
Action: Drop the policies.
ORA-28109 the number of related policies has exceeded the limit of 16
Cause: Too many policies are involved in the same objects.
Action: Drop one or more policies. Or combine a few of them into one.
ORA-28110 policy function or package string.string has error
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.
ORA-28111 insufficient privilege to evaluate policy predicate
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.
ORA-28112 failed to execute policy function
Cause: The policy function has one or more error during execution.
Action: Check the trace file and correct the errors.
ORA-28113 policy predicate has error
Cause: Policy function generates invalid predicate.
Action: Review the trace file for detailed error information.
ORA-28115 policy with check option violation
Cause: Policy predicate was evaluated to FALSE with the updated values.
Action: Check the trace file and correct the errors.
ORA-28116 insufficient privileges to do direct path access
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.
ORA-28150 proxy not authorized to connect as client
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.
ORA-28151 more than one user name specified for command
Cause: More than one user name was specified for an ALTER USER command.
Action: Try the command again with only one user name.
ORA-28152 proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
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.
ORA-28153 Invalid client initial role specified: 'string'
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.
ORA-28154 Proxy user may not act as client 'string'
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.
ORA-28155 user 'string' specified as a proxy is actually a role
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.
ORA-28156 Proxy user 'string' not authorized to set role 'string' for client 'string'
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.
ORA-28157 Proxy user 'string' forbidden to set role 'string' for client 'string'
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.
ORA-28158 missing ALL keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28159 missing BEHALF keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28160 missing EXCEPT keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28161 missing ROLES keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28162 missing THROUGH keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28163 GRANT already specified
Cause: The GRANT clause was specified twice.
Action: Use only one GRANT clause.
ORA-28164 REVOKE already specified
Cause: The REVOKE clause was specified twice.
Action: Use only one REVOKE clause.
ORA-28165 proxy 'string' may not specify password-protected role 'string' for client 'string'
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.
ORA-28166 duplicate rolename in list
Cause: The name of a role was specified more than once in a list.
Action: Repeat the command specifying the role once.
ORA-28168 attempted to grant password-protected role
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.
ORA-28500 connection from ORACLE to a non-Oracle system returned this message:
Cause: The cause is explained in the forwarded message.
Action: See the non-Oracle system's documentation of the forwarded message.
ORA-28501 communication error on heterogeneous database link
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.
ORA-28502 internal communication error on heterogeneous database link
Cause: A communication error internal to Oracle's heterogeneous services has occurred.
Action: Contact Oracle Customer Support.
ORA-28503 bind value cannot be translated into SQL text for non-Oracle system
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.
ORA-28504 ROWID not found in ROWID cache for heterogeneous database link
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 initialization parameter ROWID_CACHE_SIZE in the server data dictionary by using the DBMS_HS PL/SQL package.
ORA-28505 cannot get non-Oracle system capabilities from string
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.
ORA-28506 parse error in data dictionary translation for string stored in string
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.
ORA-28507 error in data dictionary view string
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.
ORA-28508 invalid value string for Heterogeneous Services initialization parameter string
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 documentation to determine acceptable values, and update that parameter in HS_INST_INIT using a PL/SQL procedure in the DBMS_HS package.
ORA-28509 unable to establish a connection to non-Oracle system
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:
ORA-28510 heterogeneous database link initialization failed
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.
ORA-28511 lost RPC connection to heterogeneous remote agent using SID=string
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.
ORA-28512 cannot get data dictionary translations from string
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.
ORA-28513 internal error in heterogeneous remote agent
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.
ORA-28514 heterogeneous database link initialization could not convert system date
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.
ORA-28515 cannot get external object definitions from string
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.
ORA-28518 data dictionary translation has illegal translation type
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.
ORA-28519 no heterogeneous data dictionary translations available
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.
ORA-28520 error initializing heterogeneous data dictionary translations
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.
ORA-28521 no heterogeneous capability information available
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.
ORA-28522 error initializing heterogeneous capabilities
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.
ORA-28523 ORACLE and heterogeneous agent are incompatible versions
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.
ORA-28525 unable to create Heterogeneous Services error message text
Cause: Incorrect arguments were passed into the error message creation routine.
Action: Contact Oracle Customer Support.
ORA-28526 invalid describe information returned to Heterogeneous 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.
ORA-28527 Heterogeneous Services datatype mapping error
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.
ORA-28528 Heterogeneous Services datatype conversion error
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.
ORA-28529 invalid or missing parameter in Net8 service name definition
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.
ORA-28530 Heterogeneous Services initialization error in NLS language ID
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 Customer Support.
ORA-28533 Heterogeneous Services coercion handling error
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.
ORA-28534 Heterogeneous Services preprocessing error
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.
ORA-28535 invalid Heterogeneous Services context
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.
ORA-28536 error in processing Heterogeneous Services initialization parameters
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.
ORA-28550 pass-through SQL: cursor not found
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.
ORA-28551 pass-through SQL: SQL parse error
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.
ORA-28552 pass-through SQL: call flow error
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.
ORA-28553 pass-through SQL: invalid bind-variable position
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.
ORA-28554 pass-through SQL: out of cursors
Cause: The maximum number of open cursors has been exceeded.
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.
ORA-28555 pass-through SQL: required parameter missing or NULL
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
Action: Use a non-NULL value for the parameter.
ORA-28556 authorization insufficient to access table
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.
ORA-28557 unknown string for database link to non-Oracle system
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.
ORA-28558 HS_FDS_CONNECT_STRING undefined for non-Oracle system
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 (see HS_INST_INITS view in the Oracle8 Reference book). It may be necessary to use PL/SQL procedures in the SYS.DBMS_HS package to create or replace an entry for the connection's FDS_CLASS_NAME and FDS_INST_NAME.
ORA-28559 FDS_CLASS_NAME is string, FDS_INST_NAME is string
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.
ORA-28560 error in configuration of agent process
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:
ORA-28575 unable to open RPC connection to external procedure 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.
ORA-28576 lost RPC connection to external procedure agent
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 Customer Support.
ORA-28577 argument string of external procedure string has unsupported datatype string
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.
ORA-28578 protocol error during callback from an external procedure
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 Customer Support.
ORA-28579 network error during callback from external procedure agent
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 Customer Support.
ORA-28580 recursive external procedures are not supported
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.
ORA-28581 protocol error while executing recursive external procedure
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
Action: Contact Oracle Customer Support.
ORA-28582 a direct connection to this agent is not allowed
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.
ORA-28590 agent control utility: illegal or badly formed command
Cause: The user has issued an unrecognized or syntactically incorrect command.
Action: Refer to documentation and correct the syntax of the command.
ORA-28591 agent control utility: unable to access parameter file
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.
ORA-28592 agent control utility: agent SID not set
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.
ORA-28593 agent control utility: command terminated with error
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.
ORA-28594 agent control utility: invalid parameter name
Cause: The user tried to set or unset an invalid agent parameter.
Action: Refer to documentation and correct the parameter name.
ORA-28601 invalid [no]MINIMIZE option
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.
ORA-28602 statement not permitted on tables containing bitmap indexes
Cause: Table has bitmap indexes and user is minimizing or nominalizing RECORDS_PER_BLOCK.
Action: Drop all bitmap indexes before changing RECORDS_PER_BLOCK.
ORA-28603 statement not permitted on empty tables
Cause: Table is empty and statement does not work on empty tables.
Action: Try statement after loading your data.
ORA-28605 bitmap indexes cannot be reversed
Cause: An attempt was made to create reverse bitmap index. This is not supported.
Action: No action required.
ORA-28611 bitmap index is corrupted - see trace file for diagnostics
Cause: Validate Index detected bitmap corruption in its argument index.
Action: Drop this bitmap index and create a new one.
ORA-28650 Primary index on an IOT cannot be rebuilt
Cause: An attempt was made to issue alter index rebuild on IOT-TOP.
Action: Use Alter table MOVE to reorganize the table(IOT).
ORA-28651 Primary index on IOTs can not be marked unusable
Cause: An attempt was made to mark IOT-TOP unusable through ALTER INDEX.
Action: Remove the option UNUSABLE.
ORA-28652 overflow segment attributes cannot be specified
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).
ORA-28653 tables must both be index-organized
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.
ORA-28654 table and partition not overflow compatible
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.
ORA-28655 Alter table add overflow syntax error
Cause: Syntax error.
Action: Check the syntax.
ORA-28656 incomplete attribute specification
Cause: The attribute specification is not done for all partitions.
Action: Specify the storage attributes either for ALL partitions or NONE.
ORA-28658 This operation is supported only for Index-Organized tables
Cause: Attempt to perform some IOT specific operation on a non-IOT. This is not supported.
Action: No action required.
ORA-28659 COMPRESS must be specified at object level first
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 ...
ORA-28660 Partitioned Index-Organized table may not be MOVEd as a whole
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.
ORA-28661 Object already has COMPRESS clause specified
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.
ORA-28662 IOT index and overflow segments must share the same LOGGING attribute
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.
ORA-28663 Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
Cause: An attempt was made to specify LOGGING for an ALTER TABLE ADD OVERFLOW statement.
Action: Do not specify LOGGING in this context.
