85 ORA-24280 to ORA-28716

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 exceeded the maximum allowed LOB size of (4 Gigabytes - 1) * DB_BLOCK_SIZE.

Action: Correct the input values for amount and offset such that their sum is less than or equal to (4 Gigabytes - 1) * DB_BLOCK_SIZE. If an error occurs in a read or write loop, check the looping conditions and offset increments.

ORA-24291: Sort Hash Cluster error string

ORA-24292: no more tables permitted in this sorted hash cluster

Cause: A sorted hash cluster only supports a maximum of 2 tables

Action: n/a

ORA-24295: max key length (string) for sorted hash cluster exceeded

Cause: Sorted hash clusters have a maximum key size

Action: n/a

ORA-24296: error in processing the XML configuration file string

Cause: Parameters or their values were specified incorrectly in the configuration file.

Action: Check and correct the configuration parameters or their values.

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 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 user manual to specify an attribute valid for this handle.

ORA-24316: illegal handle type

Cause: An illegal handle type was specified.

Action: Consult user manual 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 re-define.

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 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 customer support.

ORA-24323: value not allowed

Cause: A null value or a bogus 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 users manual and specify a legal attribute value for the handle.

ORA-24329: invalid character set identifier

Cause: The character set identifier specifed 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: Please 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: n/a

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 or describe was attempted before executing a statement handle.

Action: Execute a statement and then fetch or describe 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: n/a

ORA-24343: user defined callback error

Cause: The only valid return value for a user defined callback function is OCI_CONTINUE or OCI_ROWCBK_DONE. Any other value will cause this error.

Action: Please insure that OCI_CONTINUE or OCI_ROWCBK_DONE is returned from the user defined callback function.

ORA-24344: success with compilation error

Cause: A sql/plsql 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: Please ensure 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: Please 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-24348: Update or Delete without Where

Cause: An update or delete was executed without where clause

Action: An OCI_SUCCESS_WITH_INFO is returned.

ORA-24349: Array DML row counts not available

Cause: One of the following occurred: -The attribute in OCIAttrGet was used incorrectly. -The version of the database used does not support this feature -There was an error in the array DML for all of the iterations.

Action: Ensure that the statement is an array DML and also ensure that the database version is Oracle 12 or higher and the correct mode is used.

ORA-24350: OCI call not allowed

Cause: OCI used is not permitted from external procedures.

Action: Refer to user manual 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: Please 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: Please 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 customer support.

ORA-24357: internal error while converting from to OCIDate.

Cause: An internal error was encountered during conversion to OCIDate type.

Action: Contact 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: Please 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: Please 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: Please 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: Please 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: Please use a non-zero value for the mamimum 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 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 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 statememt 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: Please 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.

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 OCI call is invalid

Action: Use only 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 successfuly 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-24384: Application context size is not initialized

Cause: The size of the application context must be initialized before populating each context element.

Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size

ORA-24385: Application context size or index is not valid

Cause: The size or index of the application context must be non-zero and non-negative.

Action: Use an appropriate value for the size.

ORA-24386: statement/server handle is in use when being freed

Cause: This is an internal OCI error.

Action: The user should reset in-use flag in statement handle before freeing the handle.

ORA-24387: Invalid attach driver

Cause: Trying to attach using the wrong driver

Action: Relink the application in the right mode

ORA-24388: Unsupported functionality in fast path mode

Cause: Feature not supported in fast path mode

Action: Avoid using the functionality in this mode

ORA-24389: Invalid scrollable fetch parameters

Cause: All the requested rows in this fetch could not be received.

Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION and number of rows in OCIStmtFetch2 call. If required, change some of above parameters and fetch again.

ORA-24390: Unsupported scrollable cursor operation

Cause: The scrollable cursor execute or fetch has failed.

Action: Check the documentation for supported types, and other restrictions while using scrollable cursors.

ORA-24391: invalid fetch operation

Cause: Scrollable cursor operation requested with non-scrollable cursor.

Action: Check if the statement was executed in the scrollable mode. Else the only acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter.

ORA-24392: no connection pool to associate server handle

Cause: OCIServerAttach called in OCI_POOL mode but no connection pool found to associate the server handle.

Action: 1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link.

ORA-24393: invalid mode for creating connection pool

Cause: Mode specified in OCIConnectionPoolCreate is invalid.

Action: Use a valid mode.

ORA-24394: invalid mode for destroying connection pool

Cause: Mode specified in OCIConnectionPoolDestroy is invalid.

Action: Use a valid mode.

ORA-24395: cannot reinitialize non-existent pool

Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.

Action: Create a connection pool prior to reinitializing it.

ORA-24396: invalid attribute set in server handle

Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode.

Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server handle while attaching in OCI_POOL mode.

ORA-24397: error occured while trying to free connections

Cause: An internal error occured while trying to free connections.

Action: Contact customer support.

ORA-24398: connection pool already exists

Cause: A connection pool has already been created for the specified pool handle.

Action: 1) Specify a different pool handle to create a new connection pool. 2) If you wish to modify the pool parameters, call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode.

ORA-24399: invalid number of connections specified

Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call.

Action: Specify a valid combination of parameters.

ORA-24400: error occured while creating connections in the pool

Cause: The database link specified in OCIConnectionPoolCreate might be an invalid one.

Action: Specify a valid database link.

ORA-24401: cannot open further connections

Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached.

Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and increase the value of the connMax parameter.

ORA-24402: error occured while creating connections in the pool

Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.

Action: Specify a valid username and password.

ORA-24403: error occured while trying to destroy the connection pool

Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made.

Action: Ensure no connections from the pool are being used.

ORA-24404: connection pool does not exist

Cause: An attempt was made to use the connection pool before creating it.

Action: Create the connection pool.

ORA-24405: error occured while trying to create connections in the pool

Cause: An internal error occured while creating connections in the pool.

Action: Contact customer support.

ORA-24406: API mode switch is disallowed when a call is in progress.

Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.

Action: The user should perform the API mode switch either prior to initiating the top call or after the main call is done.

ORA-24407: connection pool already exists

Cause: A connection pool has already been created for the specified pool name.

Action: Specify a different pool name to create a new connection pool.

ORA-24408: could not generate unique server group name

Cause: An internal error occured while generating unique server group name.

Action: Contact customer support.

ORA-24409: client cannot understand the object

Cause: The client cannot process all the new features in the object.

Action: Upgrade the client so that features like inheritance and SQLJ objects can be used.

ORA-24410: scrollable cursor max size exceeded

Cause: Result set size exceeded the max limits.

Action: Check the documentation for allowable maximum result set size for scrollable cursors. Re-execute with a smaller expected result set size or make the cursor non-scrollable.

ORA-24411: Session pool already exists.

Cause: A session pool has already been created for the specified pool handle.

Action: 1) Specify a different pool handle to create a new session pool. 2) If you wish to modify the pool parameters, call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode.

ORA-24412: Cannot reinitialize non-existent pool

Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.

Action: Create a session pool prior to reinitializing it.

ORA-24413: Invalid number of sessions specified

Cause: An invalid combination of minimum, maximum, max per shard and increment number of sessions was specified in the OCISessionPoolCreate call.

Action: Specify a valid combination of parameters.

ORA-24414: Only number sessions could be started.

Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server."

Action: This is a warning. Check the maximum number of sessions allowed on the server.

ORA-24415: Missing or null username.

Cause: Username and password must be specified when pool is created in this mode.

Action: Specify a valid username and password.

ORA-24416: Invalid session Poolname was specified.

Cause: An attempt was made to use a Session Pool that does not exist.

Action: Create a Session Pool before using it.

ORA-24417: Session pool size has exceeded the maximum limit

Cause: The number of sessions has exceeded the maximum size of the Session Pool.

Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters.

ORA-24419: Proxy sessions are not supported in this mode.

Cause: A proxy session was requested for from a Session Pool which does not support proxy sessions.

Action: Do not specify mode OCI_CRED_PROXY.

ORA-24420: OCISessionRelease must be used to release this session.

Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease.

Action: Call OCISessionRelease.

ORA-24421: OCISessionRelease cannot be used to release this session.

Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease.

Action: Release the session using an appropriate call.

ORA-24422: error occurred while trying to destroy the Session Pool

Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy.

Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.

ORA-24423: Cannot set the ROWID attribute - OCI_ATTR_FETCH_ROWID

Cause: An attempt was made to set the implicit ROWID attribute.

Action: Use a SELECT ... FOR UPDATE statement that has not previously been described or executed before setting this ROWID attribute.

ORA-24424: Invalid attempt to define at position 0

Cause: An invalid attempt was made to call OCIDefineByPos for position 0.

Action: Ensure that the implicit ROWID attribute, OCI_ATTR_FETCH_ROWID, is set on the statement handle before doing the execute.

ORA-24425: Invalid mode passed when defining at position 0

Cause: An invalid mode was passed to OCIDefineByPos.

Action: Ensure a valid mode is passed to OCIDefineByPos when defining at position 0.

ORA-24427: Invalid attributes on user handle

Cause: Some of the attributes set on the user handle were not allowed in pooled mode.

Action: Unset the attributes on the user handle and call OCISessionGet or use sessions that are not pooled.

ORA-24428: Sessions with SYSDBA privileges are not supported in this mode.

Cause: A session with SYSDBA privileges was requested from a Session Pool which does not support sessions with SYSDBA privileges.

Action: Do not specify mode OCI_SESSGET_SYSDBA.

ORA-24429: External authentication is not supported in this mode.

Cause: An externally authenticated session was requested from a Session Pool which does not support external authentication.

Action: Do not specify mode OCI_SESSGET_CREDEXT.

ORA-24430: Null values for sqltext and key were specified.

Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified.

Action: Specify valid values for sqltext or key or both.

ORA-24431: Statement does not exist in the cache

Cause: The statement that was requested for does not exist in the statement cache.

Action: Please request for a valid statement.

ORA-24432: The statement that was returned is not tagged.

Cause: A tagged statement was requested for, but an untagged statement has been returned.

Action: This is a warning. Please modify and tag the statement as desired.

ORA-24433: This statement has already been prepared using OCIStmtPrepare2.

Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare."

Action: Please use a different statement handle.

ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.

Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.

Action: Call OCIStmtPrepare2 before OCIStmtRelease.

ORA-24435: Invalid Service Context specified.

Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.

Action: Please specify the same service context that the statement was prepared with.

ORA-24436: Invalid statement Handle.

Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.

Action: Release the statement using OCIStmtRelease.

ORA-24437: OCIStmtExecute called before OCIStmtPrepare2.

Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.

Action: Call OCIStmtPrepare2 before OCIStmtExecute.

ORA-24438: Invalid Authentication Handle specified.

Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.

Action: n/a

ORA-24439: success with PLSQL compilation warning

Cause: A plsql compilation warning occurred.

Action: Return OCI_SUCCESS_WITH_INFO along with the error code.

ORA-24440: OCI Easy Install mode cannot be initialized

Cause: An internal OCI error has occurred.

Action: Please contact Oracle customer support.

ORA-24441: Invalid cookie, resend sql text

Cause: An internal OCI error has occurred.

Action: Please contact Oracle customer support.

ORA-24442: SCN exceeds the capability of the target OCI database or client

Cause: An attempt was made to transfer a system change number (SCN) to an Oracle database or client that is older than Release 12.2 and the SCN exceeds the maximum value that such a system can handle.

Action: If needed, update the target database or client to Release 12.2 or higher.

ORA-24444: TTC RPC (string) not allowed by the security policy configured on the database

Cause: The database security policy configuration did not allow the specified Two-Task Common (TTC) RPC.

Action: Do not use functionality that issues the specified TTC RPC which is disallowed by the database security policy.

ORA-24445: object type input parameter in TTC RPC not allowed by the security policy configured on the database

Cause: The database security policy configuration did not allow object types as input parameters (including IN bind variables) in Two-Task Common (TTC) RPCs.

Action: Do not use the functionality that relies on object type input parameter usage in a TTC RPC.

ORA-24450: Cannot pre-process OCI statement

Cause: An error occured during statement pre-processing. E.g., SQL statement has invalid usage of N' or Q' literals.

Action: Correct the SQL statement.

ORA-24451: string, Maximum call depth exceeded

Cause: Your program has too many levels of recursion.

Action: Restructure your program to eliminate some levels of recursion.

ORA-24452: value_sz exceeding SB4MAXVAL is not supported

Cause: value_sz specified in OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2 exceeds SB4MAXVAL and is not supported in this release.

Action: Specify a value less than or equal to SB4MAXVAL for value_sz in OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2.

ORA-24453: number of application context settings supplied during authentication has exceeded the supported limit of number settings

Cause: The number of application context settings supplied during authentication exceeded the specified limit.

Action: Reduce the number of application context settings that are passed during authentication.

ORA-24454: client host name is not set

Cause: The network host name in files like /etc/hosts was not set.

Action: Set the host name and try again.

ORA-24457: OCISessionGet() could not find a free session in the specified timeout period

Cause: The contention on OCI Session Pool is high.

Action: Increase the timeout for OCISessionGet() using the OCI_ATTR_SPOOL_WAIT_TIMEOUT setting or reduce the number of threads accessing the pool concurrently.

ORA-24458: OCISessionGet() timed out trying to find a free session to the desired shard and max connections per shard limit is reached

Cause: OCISessionGet() could not find a free session to the appropriate shard in the specified timeout period. No new sessions can be opened to the shard either as the number of connections open to the shard is already at the value specified by OCI_ATTR_SPOOL_MAX_PER_SHARD.

Action: Increase value of OCI_ATTR_SPOOL_MAX_PER_SHARD or increase the timeout specified by or use OCI_SPOOL_ATTRVAL_WAIT

ORA-24459: OCISessionGet() timed out waiting for pool to create new connections

Cause: The OCISessionGet() timeout expired waiting for OCI Session Pool to create new sessions

Action: Retry the request later. Use OCISessionGet() with OCI_SPOOL_ATTRVAL_TIMEDWAIT mode (with an appropriate OCI_ATTR_SPOOL_WAIT_TIMEOUT setting) or OCI_SPOOL_ATTRVAL_WAIT mode.

ORA-24460: Native Net Internal Error

Cause: Internal error .

Action: This error should not normally occur. If it persists, please contact your customer service representative.

ORA-24480: invalid OCI mode

Cause: An attempt was made to invoke OCI API with an invalid mode.

Action: Provide the OCI API with legitimate mode.

ORA-24481: Failed to initialize multithreaded environment

Cause: Operating system did not support multithreaded mode.

Action: Use single thread mode instead.

ORA-24482: Pool size was less than 1 in shared mode

Cause: Pool size must be positive in shared mode.

Action: Set a positive pool size.

ORA-24483: Invalid parameters were passed into environment creation call

Cause: Invalid parameters were passed into the environment creation call. Check the passed in parameters for the following conditions: -envp should not be NULL -xtramem_sz should not be negative -Either both xtramem_sz and usrmempp have to be provided. Or, neither should be provided.

Action: Pass in legitimate parameters.

ORA-24484: Setting authentication handle not allowed after pool create

Cause: An attempt was made to set the authentication handle on session pool handle after OCISessionPoolCreate.

Action: Set the authentication handle on session pool handle before calling OCISessionPoolCreate.

ORA-24485: Invalid attributes in session pool authentication handle

Cause: Some of the attributes set on the authentication handle being set on the session pool handle are invalid.

Action: Unset the illegal attributes on the authentication handle being set on session pool handle and then call OCIAttrSet. Refer to OCI documentation for details.

ORA-24486: Conflicting attributes in session pool authentication handle

Cause: Some attributes could not be set both on the authentication handle passed to OCISessionGet and the authentication handle set on session pool handle.

Action: Unset the conflicting attributes on the authentication handle and call OCISessionGet.

ORA-24487: Invalid properties or values provided for OCISessionGet

Cause: Some of the properties or their values provided during OCISessionGet with mode OCI_SESSGET_MULTIPROPERTY_TAG were invalid.

Action: Provide valid properties and values when calling OCISessionGet with mode OCI_SESSGET_MULTIPROPERTY_TAG. Refer to Oracle Call Interface documentation for details.

ORA-24488: Invalid properties or values provided for OCISessionRelease

Cause: Some of the properties or their values provided during OCISessionRelease with mode OCI_SESSRLS_MULTIPROPERTY_TAG were invalid.

Action: Provide valid properties and values when calling OCISessionRelease with mode OCI_SESSRLS_MULTIPROPERTY_TAG. Refer to Oracle Call Interface documentation for details.

ORA-24489: reserved OCI error

Cause: A reserved Oracle Call Interface (OCI) error has occurred.

Action: Contact Oracle Support Services.

ORA-24490: error while getting shard instances

Cause: There was a mismatch in the shard keys or group keys with the corresponding connect string.

Action: Check if the keys are properly specified along with the corresponding connection string.

ORA-24491: attempt to get sharding-related topology information failed

Cause: An unexpected error was encountered while building and processing sharding-related information.

Action: Contact Oracle Support Services.

ORA-24492: Shard library initialization failed

Cause: An attempt to initialize the shard library failed.

Action: Contact Oracle Support Services.

ORA-24493: general sharding error

Cause: An unexpected error was encountered while processing sharding-related information.

Action: Contact Oracle Support Services.

ORA-24494: error in constructing shard key or shard group key

Cause: An invalid column value was passed.

Action: Pass in a column value in the appropriate format specified by the data type.

ORA-24495: OCISessionGet() timed out waiting for a suitable writable chunk

Cause: There was no instance available with a writable chunk for the specified shard key at the time the OCISessionGet() request was issued. This may be a transient condition due to chunk migration.

Action: Retry the request later. If needed, increase the timeout specified in OCI_ATTR_SPOOL_WAIT_TIMEOUT to minimize or eliminate the chances of running into this error during chunk migrations.

ORA-24496: OCISessionGet() timed out waiting for a free connection

Cause: There was no free connection as the pool reached its maximum and all connections were in use at the time the request was issued.

Action: Retry the request later. Use OCISessionGet() with OCI_SPOOL_ATTRVAL_TIMEDWAIT mode (with an appropriate OCI_ATTR_SPOOL_WAIT_TIMEOUT setting) or OCI_SPOOL_ATTRVAL_WAIT mode. If needed, increase the maximum size of the OCI session pool.

ORA-24497: PL/SQL fix up callback name too long

Cause: The PL/SQL fix up callback name was too long.

Action: Use a shorter PL/SQL fix up callback name.

ORA-24498: OCIShardingKey usage is not supported with OCISessionBegin()

Cause: OCIShardingKey was set on user handle passed to OCISessionBegin().

Action: Use OCISessionGet() instead of OCISessionBegin().

ORA-24500: invalid UTF16 mode

Cause: UTF16 mode is allowed only at environment handle creation time.

Action: Remove UTF16 mode for functions other than OCIEnvCreate()

ORA-24501: invalid UTF16 string passed in

Cause: Non-UTF16 string is passed in while UTF16 string is expected

Action: Check the parameter which is actually a string

ORA-24502: codepoint length overflows

Cause: Returned buffer has more codepoints than allowed

Action: Set OCI_MAXCHAR_SIZE large enough to accommodate

ORA-24503: codepoint length overflows for piecewise operation

Cause: Accumulated codepoint length exceeds allowed codepoint length

Action: Set OCI_MAXCHAR_SIZE large enough to accommodate

ORA-24504: data length larger than expected

Cause: Incoming data larger than receiving buffer

Action: Set OCI_MAXDATA/MAXCHAR_SIZE appropriately or remove the setting

ORA-24505: cannot change character set id on the handle

Cause: Attempts to change character set id on non-environment handles

Action: Only try to change character set id on environment handles

ORA-24506: invalid attempt to change character set id on env handle

Cause: Attempts to change character set id after other handles have been allocated from the env handle

Action: Change character set id after creating environment handle but before allocating any handles from it.

ORA-24507: invalid combination of character set ids

Cause: Attempts to set one character set id as zero

Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate()

ORA-24508: Buffer is not aligned correctly.

Cause: Alignment error ocurred in buffer when converting between character sets.

Action: Align buffer appropriately. For UTF16 buffer, pass a ub2 pointer.

ORA-24509: OCI function currently not supported in UTF16 mode.

Cause: Attempt to call an OCI function that was not supported in OCI_UTF16ID mode.

Action: Remove the offending function or do not create an OCI environment with OCI_UTF16ID mode or OCI_UTF16ID character set ID.

ORA-24530: User not authorized to access column value.

Cause: Column security is enabled and column value is not authorized.

Action: The program needs to handle this error and take appropriate action.

ORA-24531: Column value authorization is unknown.

Cause: Column security is unknown for the column.

Action: Verify the fetched data. It may or may not contain a meaningful value because it is probably the result of an expression that operated on unauthorized values.

ORA-24536: Warning - column authorization unknown.

Cause: Column security is unknown for one or more columns.

Action: Verify the fetched data. It may or may not contain a meaningful value because it is probably the result of an expression that operated on unauthorized values.

ORA-24542: PRELIM mode logon not allowed to a pluggable database

Cause: PRELIM mode logon was attempted to a pluggable database.

Action: Create PRELIM mode connections to CDB$ROOT only.

ORA-24543: instance startup or shutdown not allowed in pluggable database

Cause: An instance startup or shutdown operation was attempted when connected to a pluggable database.

Action: Perform instance startup or shutdown operations by connecting to CDB$ROOT.

ORA-24544: Oracle RAC One Node instance is already running.

Cause: An instance startup failed because an instance of the Oracle RAC One Node database was already running on one of the cluster nodes.

Action: In Oracle RAC One Node, avoid any attempt to start a second instance by any means while the instance is already running.

ORA-24550: unhandled signal #number received. string

Cause: Serious error: signal received

Action: Refer to the platform-specific signal code, and see if the application code caused the error. Otherwise, record all error state and notify Oracle Support Services.

ORA-24557: error string encountered while handling error string; exiting server process

Cause: A second-level error occurred in an Oracle server process that required that process to exit.

Action: None. If an excessive number of incidents are dumped, contact Oracle Support Services.

ORA-24600: could not create OCI environment

Cause: The Oracle Client library used to communicate with the database failed to initialize correctly.

Action: Check that the Oracle environment or registry entries are consistent and correct. If using the Oracle Instant Client, make sure the Oracle driver for MySQL and Oracle libraries are from the same release. Make sure you have read access to the libraries.

ORA-24601: bind buffer not allocated by caller

Cause: A valid buffer was not provided for the bind call.

Action: Provide a non-NULL pointer for the bind call and a valid length for the buffer.

ORA-24602: attempting to read with no fetch

Cause: A column was being fetched while not in fetch state.

Action: Fetch the column after fetching of the result set has started.

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: n/a

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 only one of the following values is specified: OCI_TRANS_NEW, OCI_TRANS_JOIN, OCI_TRANS_RESUME, or OCI_TRANS_PROMOTE.

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

ORA-24762: server failed due to unspecified error

Cause: An internal error has occured in the server commit protocol.

Action: Contact 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

ORA-24765: transaction branch has been heuristically rolled back

ORA-24766: transaction branch has been partly committed and aborted

ORA-24767: transaction branch prepare returns read-only

Cause: The transaction is read-only, or this is the outcome of an optimization for two-phase commit protocol.

Action: None. Informational only.

ORA-24768: commit protocol error occured in the server

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 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-multi threaded server process.

Action: Perform the work in the local database or open a connection to the remote database from the client. If multi threaded 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 having an open remote cursor.

Action: Close any open remote cursor prior to detach.

ORA-24780: cannot recover a transaction while in an existing transaction

Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long).

Action: Detach from the current transaction and retry the operation.

ORA-24781: branches don't belong to the same global transaction

Cause: The list of xids passed into kpotxmp() don't have the same gtrid

Action: n/a

ORA-24782: Cannot detach from a non-migratable transaction

Cause: An attempt was made to detach from a non-migrateable transaction.

Action: Either commit or rollback the transaction.

ORA-24783: Cannot switch non-migratable transactions

Cause: An attempt was made to prepare/commit a txn different from current.

Action: n/a

ORA-24784: Transaction exists

Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction

Action: n/a

ORA-24785: Cannot resume a non-migratable transaction

Cause: An attempt was made to resume a non-migrateable transaction.

Action: n/a

ORA-24786: separated transaction has been completed

Cause: The current transaction has been completed by another process.

Action: Start a new transaction

ORA-24787: remote cursors must be closed before a call completes

Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed.

Action: Close all remote cursors in each call, or start a regular (non-separated) transaction.

ORA-24788: cannot switch to specified transaction (server type)

Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server.

Action: All parts of this application should connect as dedicated or as shared.

ORA-24789: start not allowed in recursive call

Cause: Oracle RM will not start/resume a branch in a recursive call

Action: Reconsider your application stack design

ORA-24790: cannot mix OCI_TRANS_RESUME and transaction isolation flags

Cause: An attempt was made to change the isolation level of an existing transaction.

Action: No action required

ORA-24791: invalid transaction start flags

Cause: An invalid transaction start flag was passed.

Action: Verify that OCI_TRANS_LOOSE was not passed along with OCI_TRANS_JOIN, OCI_TRANS_RESUME. Also, verify that other flags (such as OCI_TRANS_SEPARABLE) passed by the client are supported by the version of the Oracle server.

ORA-24792: cannot mix services in a single global transaction

Cause: Oracle RM will not serve global (distributed) transaction requests if branches are created using different services

Action: Configure clients such that those participating in the same distributed transaction use the same service name.

ORA-24794: no active DTP service found

Cause: Oracle RM will not serve global (distributed) transaction requests until DTP services are configured in RAC. It is possible that a service was stopped while transactions were in-flight.

Action: Provision/Start DTP services first.

ORA-24795: Illegal string attempt made

Cause: An illegal attempt was made to commit/rollback current transaction

Action: Use appropriate commit/rollback mechanism

ORA-24796: operation completed; resume of original transaction rolled back

Cause: The commit, rollback, or prepare completed successfully, but the current transaction for this thread was rolled back.

Action: If desired, retry the current transaction. If the operation was prepare, then end transaction appropriately with a commit or rollback operation.

ORA-24797: cannot promote the current transaction to a distributed transaction

Cause: An illegal attempt was made to promote the current transaction.

Action: Verify that OCI_ATTR_XID, OCI_ATTR_INTERNAL_NAME, and OCI_ATTR_EXTERNAL_NAME attributes have been set properly, and verify that the current transaction has neither performed IDL or PDML operations, nor already been a distributed transaction. Also, verify that the local transaction is in the same isolation level if the isolation flag value is set.

ORA-24798: cannot resume the distributed transaction branch on another instance

Cause: An attempt was made to resume a distributed transaction branch that is physically located on another RAC instance.

Action: Get a connection to the instance where the transaction branch is located.

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: Internal error .

Action: This error should not normally occur. If it persists, please contact your customer service representative.

ORA-24804: Lob read/write functions called while another OCI LOB read/write streaming is in progress

Cause: Internal error.

Action: Wait for the ongoing LOB streaming call to finish before issuing the next server call, or use OCIBreak() abort the current LOB streaming call.

ORA-24805: LOB type mismatch

Cause: When copying or appending LOB locators, both source and desctination 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 desctination 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: Attempted 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 tha 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 Worldwide 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-24814: operation not allowed for temporary LOBs

Cause: Temporary LOB locators are not allowed in the operation. For example: OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.

Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign.

ORA-24815: Invalid character set form

Cause: An invalid character set form was passed into an OCI LOB function. For example, the only valid cs form for OCILobCreateTemporary() is OCI_DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2).

Action: Specify a valid character set form.

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

Cause: A Bind value of length potentially > 4000 bytes follows binding for LOB or LONG.

Action: Re-order the binds so that the LONG bind or LOB binds are all at the end of the bind list.

ORA-24817: Unable to allocate the given chunk for current lob operation

Cause: The given size is increased to accomodate the number of bytes from server due to varying width db char/nchar set.

Action: Use smaller chunk sizes when you have character set conversion between client/server or perform piece-wise read or write.

ORA-24818: Operation not permitted on Abstract LOBs

Cause: Abstract LOB locators were not allowed in the operation. For example, OCILobAssign only takes persistent LOB locators as parameters, not Abstract (i.e., client-side created) LOBs.

Action: Avoid the operation on Abstract LOBs.

ORA-24819: Illegal reference count encountered for a temporary LOB

Cause: Internal error.

Action: This error should not normally occur. If it persists, contact Oracle Support Services.

ORA-24820: Differnt LOB function called while another OCI LOB call is in progress

Cause: An attempt was made to execute a new OCI LOB call while another OCI LOB call was in progress.

Action: Wait for the ongoing LOB streaming call to finish before issuing the next server call, or use OCIBreak() to abort the current LOB streaming call.

ORA-24821: LOB prefetch size supplied is larger than the supported limit.

Cause: A very large LOB prefetch size was specified during a query.

Action: Reduce the prefetch size to an acceptable value.

ORA-24850: failed to startup shared subsystem

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting up 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-24854: invalid pieceinfo provided

Cause: While making the first call to write LOB data, an invalid pieceinfo value provided.

Action: Correct the call to use OCI_ONE_PIECE or OCI_FIRST_PIECE. If using OCCI, make sure to call writeBuffer before calling writeLastBuffer.

ORA-24855: attempt to pass a LOB locator over an invalid database link

Cause: There was an attempt to send a LOB locator over a database link which was different from the one on which it was obtained.

Action: Ensure that remote LOB locators are passed back on the same database link from which they were obtained.

ORA-24900: invalid or unsupported mode parameter passed in call

Cause: The mode parameter passed into the OCI Client Notification call is incorrect.

Action: Please 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: Please ensure 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: Please 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: Please 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: Please set the callback attribute using the OCIAttrSet() call.

ORA-24905: invalid recipient protocol attribute passed into OCI call

Cause: The subscription handle passed into the OCI call did not have a proper recipient protocol attribute.

Action: Please set the recipient protocol attribute using the OCIAttrSet() call.

ORA-24906: invalid recipient attribute passed into OCI call

Cause: The subscription handle passed into the OCI call did not have a proper recipient attribute.

Action: Please set the recipient attribute using the OCIAttrSet() call.

ORA-24907: invalid pair of callback and recipient protocol attributes

Cause: The subscription handle passed into the OCI call can't have both the callback defined and a recipient protocol other than OCI_SUBSCR_PROTO_OCI at the same time.

Action: Please set the appropriate callback and recipient protocol attributes using the OCIAttrSet() call.

ORA-24908: invalid recipient presentation attribute

Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute.

Action: Set the recipient presentation attribute using the OCIAttrSet() call

ORA-24909: call in progress. Current operation cancelled

Cause: The OCI call was invoked when another call on the connection was in progress.

Action: Check if the OCI call is supported when the call is in progress under special conditions; for example, if it is being used by a signal handler.

ORA-24911: Cannot start listener thread at specified port

Cause: Thread already running at a different port.

Action: Set the correct port in the environment handle or let the system choose the port.

ORA-24912: Listener thread failed. string

Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message.

Action: The client needs to be restarted.

ORA-24913: Event to enable NLS validation

Cause: N/A

Action: Set this event in your environment to enable NLS character validation even when character sets are the same for client/server.

ORA-24915: Cannot start Listener at specified IP address

Cause: Thread was already listening at a different IP address.

Action: Set the correct IP address in the environment handle or let the system choose the correct IP address.

ORA-24916: cannot use IP address attribute before release 11.2 compatible notifications

Cause: An attempt was made to use OCI_ATTR_SUBSCR_IPADDR attribute before release 11.2 compatible notifications.

Action: Change the compatibility to 11.2.

ORA-24918: secure notification mode not supported

Cause: An attempt was made to use OCI_SECURE_NOTIFICATION before release 12.0 compatible notifications.

Action: Change the compatibility to 12.0.

ORA-24919: subscription to Fast Application Notification failed

Cause: An error occurred while subscribing to Fast Application Notification. This could be due to problems in the Oracle clusterware configuration.

Action: Look at the client trace files for additional information. Ensure that the Oracle clusterware is properly configured.

ORA-24920: column size too large for client

Cause: Client attempted to fetch a column whose size is larger than the maximum size that can be handled by the client.

Action: Upgrade the client stack to Oracle 12c or higher.

ORA-24922: cannot send or receive an SCN value which is too high for the current compatibility setting

Cause: An attempt was made to send or receive a high value system change number (SCN) over the network, but either the sever or client does not support such a high value SCN. This error usually occurs when either the server or client compatibility is lower than 12.2.

Action: Be sure the database compatibility is 12.2 or above on both the client and server.

ORA-24940: invalid combination of string namespace, string presentation and string receive protocol

Cause: An invalid combination of namespace, presentation and receive protocol was specified during notification registration. Currently, only AQ namespace is supported with XML presentation. Non-AQ namespace is not supported for e-mail and HTTP receive protocols.

Action: Please change the register call appropriately.

ORA-24941: invalid combination of notification grouping attributes

Cause: An invalid combination of notification grouping attributes was specified. Currently, only TIME notification grouping class is supported. If notification grouping class is zero, all other notification grouping attributes must be zero.

Action: Refer to documentation and change the attributes appropriately.

ORA-24942: cannot use ntfn grouping attributes on before release 11.0 compatible ntfns

Cause: An attempt was made to use notification grouping on before release 11.0 compatible notifications.

Action: Change the compatibility to 11.0.

ORA-24943: cannot use ntfn grouping with this receive protocol, presentation and/or QoS

Cause: An attempt was made to use notification grouping with e-mail or HTTP receive protocol or XML presentation or payload delivery or reliable QoS. Currently, only OCI and PLSQL receive protocols and default presentation are supported with notification grouping.

Action: Refer to documentation and change the call appropriately.

ORA-24944: cannot use timeout or grouping with ANONYMOUS namespace

Cause: An attempt was made to use timeout or grouping with ANONYMOUS namespace. Currently, timeout and grouping are supported only with AQ and DBCHANGE namespaces.

Action: Refer to documentation and change the call appropriately.

ORA-24945: cannot use context, QOS and timeout attributes of notification on lower than 10.2 compatible notifications

Cause: An attempt was made to use context, QOS and timeout attributes of notification on lower than 10.2 compatible notifications.

Action: Change the database compatibility to 10.2.

ORA-24946: invalid registration callback

Cause: An attempt was made to use a reserved callback for notification registration.

Action: Choose a different name for the notification callback and change the register call appropriately.

ORA-24947: Invalid namespace attribute specified for the subscription string

Cause: An attempt was made to register with invalid namespace attribute.

Action: Refer to documentation and change the namespace appropriately.

ORA-24948: number of registrations for this subscription exceeds the limit

Cause: The maximum number of registrations already existed for this subscription.

Action: Change the queue policy or close any existing registrations and try again.

ORA-24950: unregister failed, registration not found

Cause: The registration that was asked to be unregistered could not be found.

Action: Please check the callback function name and the subscription name in the unregister call.

ORA-24952: register, unregister or post has incorrect collection count

Cause: The register, unregister or post function was invoked with a collection that was smaller than the size specified by the parameter to the function.

Action: Please check the function's use and ensure that the size parameter is correct.

ORA-24960: the attribute string is greater than the maximum allowable length of number

Cause: The user attempted to pass an attribute that is too long

Action: Shorten the specified attribute and retry the operation.

ORA-24962: connect string could not be parsed, error = string

Cause: The address portion of the connect string could not be parsed. The client may be using a format of the connect string that the server does not understand.

Action: Correct the connect string.

ORA-24964: ALTER SESSION SET CONTAINER error

Cause: An attempt to switch to a PDB with different settings such as character set, time zone or time zone file version on an Oracle 12c Release 1 (12.1) or earlier client failed.

Action: Upgrade client to Oracle 12 Release 2 (or later) to support such operations.

ORA-24969: iteration count of number not supported for this statement

Cause: This statement was not supported with iteration count greater than one.

Action: Execute the statement with an iteration count of one.

ORA-24981: deferred SGA thread spawn failed

Cause: This is an internal error.

Action: None

ORA-24982: deferred SGA segment allocation failed, index = string location = string

Cause: System-defined shared memory limits are inadequate for Oracle.

Action: Consult the alert file for details.

ORA-24983: Process (string) failed to attach to deferred SGA segments.

Cause: The process failed to attach to deferred SGA segments.

Action: Consult the alert file for details and contact Oracle Support Services.

ORA-24984: SGA allocation slaves termination failed

Cause: This is an internal error.

Action: None

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 this type of view

Cause: INSTEAD OF triggers can be created on any view which is not an Editioning View, while BEFORE and AFTER triggers may only be created on Editioning Views.

Action: Change the trigger type to INSTEAD OF or change the view on which you are attempting to create a DML trigger.

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: PLSQL 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-25011: cannot create trigger on internal AQ table

Cause: An attempt was made to try to create a trigger on a table that is used internally to support the Advanced Queueing (AQ) feature.

Action: Do not create the trigger.

ORA-25012: PARENT and NEW values cannot be identical

Cause: The referencing clause specifies identical values for PARENT and OLD.

Action: Re-specify 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: Re-specify 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-25018: conflicting trigger string already exists

Cause: Conflicting instead of DDL trigger on schema/database already exists.

Action: Remove the old trigger

ORA-25019: too much concurreny

Cause: cannot pin the database/schema because of too much concurrency

Action: try the operation later

ORA-25020: renaming system triggers is not allowed

Cause: renaming system triggers is not allowed

Action: Drop the trigger, and create a new one for the same

ORA-25021: cannot reference a trigger defined on another table

Cause: Referenced trigger in the FOLLOWS clause was defined on another table.

Action: Create the referenced trigger on the same table

ORA-25022: cannot reference a trigger of a different type

Cause: Referenced trigger in the FOLLOWS or PRECEDES clause was either a different type or not a compound trigger.

Action: Create the referenced trigger as the same type or a compound trigger.

ORA-25023: Cyclic trigger dependency is not allowed

Cause: A cycle of trigger dependency can be formed.

Action: Do not create a trigger that can formed a cyclic dependency.

ORA-25024: cannot specify FOLLOWS for a REVERSE CROSSEDITION trigger

Cause: The FOLLOWS clause was specified when creating the REVERSE CROSSEDITION trigger.

Action: Do not create a REVERSE CROSSEDITION trigger with a FOLLOWS clause.

ORA-25025: cannot specify PRECEDES clause

Cause: The PRECEDES clause was specified when creating a FORWARD CROSSEDITION trigger or a regular trigger.

Action: Do not create a FORWARD CROSSEDITION or a regular trigger with a PRECEDES clause.

ORA-25026: FOR EACH ROW was specified with compound triggers

Cause: FOR EACH ROW is not allowed with compound triggers.

Action: Remove the FOR EACH ROW clause.

ORA-25027: compound triggers cannot be used as system triggers

Cause: Compound trigger was defined as system trigger.

Action: Do not use compound trigger as system trigger.

ORA-25028: regular trigger body can not start with keyword COMPOUND

Cause: Regular triggers body should start with BEGIN/DECLARE etc .

Action: Fix the syntax and recompile.

ORA-25029: compound triggers should always start with keyword COMPOUND

Cause: Compound trigger body was started with incorrect keyword.

Action: Fix the syntax and recreate.

ORA-25030: crossedition trigger cannot be owned by a non-editioned user

Cause: An attempt was made to create a crossedition trigger in a schema where triggers were not editionable.

Action: Enable editions for the user for triggers and then create the crossedition trigger.

ORA-25031: only a crossedition trigger may be specified

Cause: The trigger specified was not a crossedition trigger.

Action: Specify a crossedition trigger.

ORA-25032: crossedition trigger cannot be created in ORA$BASE

Cause: An attempt was made to create crossedition trigger in the ORA$BASE edition.

Action: Do not create a crossedition trigger in the ORA$BASE edition.

ORA-25033: triggers cannot be executed at this time

Cause: An attempt was made to execute a trigger when the session was almost finished.

Action: Do not attempt to DML with triggers that are expected to execute when session has almost ended.

ORA-25034: cannot bypass trigger owned by another user

Cause: An attempt was made to do DML from a crossedition trigger on an object that has a non-crossedition trigger owned by another user. DML from a crossedition trigger bypasses the running of non-crossedition triggers; this cannot be allowed for triggers owned by other users.

Action: Permit the non-crossedition trigger to be bypassed by attaching it to the editioning view rather than the table, moving one of the triggers to be in the same schema as the other, or explicitly disabling the non-crossedition trigger.

ORA-25035: cannot perform DML on remote object from a crossedition trigger

Cause: An attempt was made to do DML from a crossedition trigger that would modify data in a remote database. DML from a crossedition trigger has special rules applied regarding what triggers will fire as part of that DML; these special rules cannot be applied across database links and therefore the DML cannot be allowed.

Action: Perform the DML in a helper function separate from the crossedition trigger itself; the special rules are not applied when the DML is not issued from within the crossedition trigger itself.

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 tempfile.

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 tempfile.

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 partioned table.

Action: create a local bitmap index instead.

ORA-25123: Too many components specified in the name.

Cause: Specifying more components to a name than allowed.

Action: Check the name specified for the operation.

ORA-25124: Database link name not allowed.

Cause: Specifying a database link name when it is not permitted.

Action: Check the name specified for the operation.

ORA-25125: BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE storage option not allowed

Cause: An attempt was made to specify the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE storage option. This option may only be specified during - CREATE or ALTER TABLE - CREATE or ALTER CLUSTER - CREATE or ALTER INDEX

Action: Remove this option and retry the statement.

ORA-25126: Invalid name specified for BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE

Cause: The name of the cache hints specified by was invalid. The only valid names for BUFFER_POOL are KEEP, RECYCLE and DEFAULT. The only valid names for FLASH_CACHE and CELL_FLASH_CACHE are KEEP, NONE and DEFAULT.

Action: Use a valid name or remove the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE clause.

ORA-25127: RELY not allowed in NOT NULL constraint

Cause: An attempt 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: Try 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: Obvious

ORA-25130: cannot modify primary key - primary key not defined for table

Cause: Attempted to modify a primary key that is not defined for the table.

Action: None

ORA-25131: cannot modify unique(string) - unique key not defined for table

Cause: attempted to modify a unique key that is not deined for the table.

Action: None

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 partion 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-25154: column part of USING clause cannot have qualifier

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Action: Remove the qualifier.

ORA-25155: column used in NATURAL join cannot have qualifier

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Action: Remove the qualifier.

ORA-25156: old style outer join (+) cannot be used with ANSI joins

Cause: When a query block uses ANSI style joins, the old notation for specifying outer joins (+) cannot be used.

Action: Use ANSI style for specifying outer joins also.

ORA-25157: Specified block size string is not valid

Cause: An attempt was made to create a tablespace with a block size which is not supported.

Action: Specify one of the valid blocksizes i.e the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform.

ORA-25158: Cannot specify RELY for foreign key if the associated primary key is NORELY

Cause: RELY is specified for the foreign key contraint, when the associated primary key constraint is NORELY.

Action: Change the option of the primary key also to RELY.

ORA-25159: Must specify a valid tablespace number

Cause: A valid tablespace number was missing.

Action: Specify a valid tablespace number.

ORA-25160: Must specify a valid relative data block address

Cause: A valid relative data block address was missing.

Action: Specify a valid relative data block address.

ORA-25161: Cannot have both DBA and RDBA options

Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP REDO.

Action: Use either the DBA option or the RDBA option but not both.

ORA-25162: Must specify both RDBA MIN and RDBA MAX options

Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO.

Action: Specify both RDBA MIN and RDBA MAX.

ORA-25163: Invalid tablespace number or relative data block address

Cause: The relative data block adress is invalid for the given tablespace number or the table space number is invalid.

Action: Specify a valid tablespace number or relative data block address.

ORA-25164: The tag expression is too complex.

Cause: The statement tag value was not specified using a simple expression.

Action: Reduce the complexity of the statement tag expression. For example, assign the tag expression to a variable and reference the variable in the error logging clause.

ORA-25165: number of passwords in statement exceeds maximum limit of string

Cause: The SQL statement had more passwords than the maximum limit allowed.

Action: Reconstruct the SQL statement to have a number of passwords less than or equal to the maximum allowed.

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: ON keyword 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: CREATE TABLE with LOB/BFILE/VARRAY columns, partitioning/PARALLEL/CREATE TABLE AS SELECT options, ALTER TABLE with ADD/MODIFY column options, CREATE INDEX

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 is 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 or sorted hash cluster

ORA-25189: illegal ALTER TABLE option for an index-organized table

Cause: While altering an index-organized table, an attempt was made to enter either the PCTFREE or PCTUSED value 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 (e.g. changing physical attributes) with some other operation (e.g. 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 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 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 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 to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED

Action: n/a

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 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: n/a

ORA-25198: partitioning method is not supported for index-organized table

Cause: An unsupported partitioning method was specified.

Action: Select a different partitioning scheme. Consult the documentation for supported partitioning methods.

ORA-25199: partitioning key of a index-organized table must be a subset of the primary key

Cause: An attempt 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 don't 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 inm 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 prioirty 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: n/a

ORA-25214: cannot specify delay or expiration for enqueue to exception queue

Cause: A message was enqueued to the exception queue with either delay or expiration specified.

Action: Enqueue a message without delay or expiration.

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-25220: enqueue failed, signature not specified for a non-repudiable queue

Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature

Action: Give the signature

ORA-25221: enqueue failed, signature specified queue not supporting non-repudiation

Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation

Action: Remove the signature

ORA-25222: enqueue failed, complete sender info. not provided for a queue supporting non-repudiation

Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation

Action: Provide the sender information

ORA-25223: user_data type used is not supported

Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.

Action: Enqueue the message again with data of raw or object type.

ORA-25224: sender name must be specified for enqueue into secure queues

Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.

Action: Enqueue the message with sender name specified.

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-25227: Propagation job string doesn't exist

Cause: The job doesn't exist in AQ$_SCHEDULES or cache.

Action: n/a

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-25229: error on transformation of message string string

Cause: There was an error when transforming a message at enqueue, dequeue or propagation time.

Action: Correct the transformation function.

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 satisifies the criterion, NEXT_MESSAGE for dequeuing the next message that satisifies 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 from string.string

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 naviagtion 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 dequeue condition/correlation ID specified in dequeue options

Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either message ID or dequeue condition/correlation ID, or neither.

Action: To dequeue a message, specify a message ID or a dequeue condition/correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or dequeue condition/correlation ID in the dequeue options.

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 your Oracle customer support representative. 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 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 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-25260: AQ latch cleanup testing event

Cause: N/A.

Action: event used for AQ statistics latch cleanup testing.

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-25264: cant get signature for this queue

Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable.

Action: Try dequeue again without the get signature option

ORA-25265: specified signature for a queue which does not support reciever non-repudiation

Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification

Action: Try dequeue again without the signature

ORA-25266: didnt try to dequeue by message id. with the signature

Cause: The signature was specified for a queue, but the dequeue was not done by message id.

Action: Try dequeue again by message id.

ORA-25267: didnt specify the signature for a reciever non-repudiable queue

Cause: The signature was not specified for a reciever non-repudiable queue

Action: Try dequeue again along with the signature

ORA-25268: didnt dequeue in browse mode with get signature option

Cause: The dequeue was not performed in browse mode with get signature option

Action: Try dequeue again in browse mode

ORA-25269: cant specify sognature with get signature option

Cause: The signature is not required for the dequeue with get signature option

Action: Try dequeue again without the signature in dequeue options

ORA-25270: sender info does not match with the actual sender of the message

Cause: The sender info. and the message id. do not match

Action: Provide the right sender info. Try dequeue again without the signature in dequeue options

ORA-25271: queue table not found for the given queue

Cause: The queue table does not exist for the given queue

Action: Provide the right queue name

ORA-25272: Signature does not exist for the given reciever and message id.

Cause: Signature does not exist for the given reciever and message id.

Action: Check the message id. and the reciever's information

ORA-25273: AQ QMN process alternate cleanup event

Cause: N/A.

Action: event used for AQ QMN alternate cleanup mode.

ORA-25274: AQ Buffered Queue event

Cause: N/A.

Action: event used for AQ Buffered Queue mode.

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-25279: dequeue as select not supported before 8.2

Cause: Dequeue as select not supported before 8.2.

Action: Dont use select condition while dequeuing

ORA-25280: complete sender information not provided to non-repudiate sender

Cause: complete sender information not provided to non-repudiate sender

Action: Provide the complete sender information

ORA-25281: complete reciever information not provided to non-repudiate reciever

Cause: complete reciever information not provided to non-repudiate reciever

Action: Provide the complete reciever information

ORA-25282: message id. not provided for non-repudiation

Cause: message id. was not provided

Action: Provide the message id.

ORA-25283: either agent's name or address needed for non-repudiation

Cause: neither agent's name nor address provided for non-repudiation"

Action: Provide the agent info.

ORA-25284: Invalid value string for string

Cause: An Invalid value or NULL was specified for the parameter.

Action: Check the documentation for valid values.

ORA-25285: Invalid value string for array_mode

Cause: An Invalid value or NULL was specified for the array_mode.

Action: Check the documentation for valid values.

ORA-25286: Invalid number of elements in the message properties array

Cause: Number of elements in the message properties array do not match the number of elements in the payload array.

Action: Create a message property array with one element (that applies for all the elements in the payload array) or create a message property array with the same number of elements as there are in the payload array.

ORA-25287: Invalid value string, string should be non-negative

Cause: An Invalid value or NULL was specified for the parameter.

Action: Specify a non negative integer.

ORA-25288: AQ HTTP propagation encountered error, status-code number, string

Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error

Action: Specify a valid address in the connect string of the propagation destination dblink, the dblink user has the correct permissions, check if the AQ propagation servlet was properly installed.

ORA-25289: Buffer Already Exists

Cause: Buffer already exists for the specified queue.

Action: None

ORA-25290: Cannot complete operation on queue string with existing messages

Cause: Queue already has messages. Cannot complete operation

Action: Truncate the queue before adding/dropping a buffer

ORA-25291: Buffer does not exist for the specified queue

Cause: Buffer does not exist for the specified queue

Action: Operation on the buffer cannot be performed. create the buffer

ORA-25292: Buffer operations are not supported on the queue

Cause: Buffer operations are not supported on the specified queue type

Action: Buffered operations are only supported on to 8.1 style queues, which do not have transaction grouping.

ORA-25293: Lob attributes must be null for buffered operations

Cause: Enqueue of a buffered message with a non-null lob attribute was attempted

Action: Set the lob attributes to null before enqueuing the buffered message

ORA-25294: Cannot propagate user buffered messages to a database with version lower than 10.2

Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2.

Action: Do not propagate buffered messages to the database.

ORA-25295: Subscriber is not allowed to dequeue buffered messages

Cause: Subscriber is only allowed to dequeue persistent messages

Action: Drop the subscriber and re-create it, or dequeue only persistent messages for the subscriber

ORA-25296: Queue Table string has a buffered queue string

Cause: Buffered message was enqueued by specifying delay or sequence deviation.

Action: Do not specify delay of sequence deviation when enqueuing buffered messages.

ORA-25298: Only immediate visibility mode supported for buffered message enqueue or dequeue

Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered message enqueue or dequeue

Action: Supply a visibility of dbms_aq.IMMEDIATE

ORA-25299: Invalid message delivery_mode

Cause: Invalid value was specified for delivery mode

Action: Specify dbms_aq.BUFFERED or dbms_aq.PERSISTENT during Enqueue or dbms_aq.BUFFERED, dbms_aq.PERSISTENT or dbms_aq.PERSISTENT_OR_BUFFERED during Dequeue and Listen.

ORA-25300: Cannot drop buffer for queue with buffered subscribers

Cause: Cannot drop buffer for queue with buffered subscribers

Action: Either drop buffered subscribers or forcibly drop the buffer

ORA-25301: Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2

Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2.

Action: Do not attempt to enqueue or dequeue user buffered messages.

ORA-25302: Operation not possible for non-buffered queue string

Cause: Last enqd/ackd message is only supported for buffered queues

Action: The operation is not supported.

ORA-25303: Buffered operation allowed only on the owner instance

Cause: Operation was not performed on the owner instance.

Action: Perform operation on the owner instance.

ORA-25304: Cannot use priority order queues for capture LCRs

Cause: Capture LCRs can only use commit time or enqueue time ordered queues.

Action: Use the appropriate type of queue for captured LCRs.

ORA-25305: enqueue failed, expiration must be zero for queue string.string

Cause: An attempt was made to enqueue to a buffered queue with expiration greater than zero seconds.

Action: Set expiration to zero.

ORA-25306: Cannot connect to buffered queue's owner instance

Cause: cannot connect to the owner instance of the buffered queue

Action: set listener information in REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter.

ORA-25307: Enqueue rate too high, flow control enabled

Cause: Subscribers could not keep pace with the enqueue rate.

Action: Try enqueue after waiting for some time.

ORA-25310: Subscriber is Notification only; dequeue not supported

Cause: Notification only subscribers are not allowed to dequeue.

Action: Recreate subscriber if necessary.

ORA-25311: string not supported for non-persistent queue

Cause: Specified QOS is not supported for non-persistent queues.

Action: Specify the right QOS.

ORA-25312: Cannot specify nonzero sender protocol

Cause: Sender protocol was specified during an enqueue operation.

Action: Specify the enqueue sender protocol as null or zero.

ORA-25313: a queue may not subscribe to itself for propagation

Cause: The specified subscriber had a NULL name and an address equal to the queue name.

Action: Provide a valid subscriber and retry the operation.

ORA-25314: a commit-time queue table cannot be migrated to 8.0

Cause: An attempt was made to migrate a commit-time queue table to an unsupported compatibility level.

Action: Provide an appropriate compatibility level, and retry the operation.

ORA-25315: unsupported configuration for propagation of buffered messages

Cause: An attempt was made to propagate buffered messages with the database link pointing to an instance in the destination database which is not the owner instance of the destination queue.

Action: Use queue to queue propagation for buffered messages.

ORA-25316: Late in the current transaction to begin an Enqueue/Dequeue operation

Cause: Check if the Enqueue/Dequeue operation is performed via triggers on Materialized Views which isn't supported.

Action: Triggers on materialized views aren't supported. Workarounds are on-demand materialized views or execution of trigger code within an autonomous txn.

ORA-25317: Propagation stopped because of instance shutdown

Cause: A propagation job has stopped because the instance is shutting down.

Action: No user action is required.

ORA-25318: Propagation stopped because of instance affinity change

Cause: A propagation job has stopped because its instance affinity has changed.

Action: No user action is required. The job will restart on the appropriate instance.

ORA-25319: Queue table repartitioning aborted

Cause: During instance restart in an Oracle RAC environment, queue table repartitioning aborted due to errors.

Action: Look at the incident generated for this error and report the problem to Oracle Support Services.

ORA-25320: Failed to create, alter, or remove Subscriber

Cause: There is a pending enqueue or dequeue operation on this queue from the same session.

Action: Either COMMIT or ROLLBACK pending enqueue or dequeue operation before attempting to create, alter, or remove the subscriber.

ORA-25321: enqueue failed, user property specified but queue string.string is not an 8.1 style queue

Cause: user properties can only be specified when enqueueing into 8.1 style queues.

Action: Specify an 8.1 style queue or pass user property as NULL.

ORA-25322: message priority is out of range

Cause: The message priority range of 0 to 9 was exceeded.

Action: Set the message priority in the range of 0 to 9.

ORA-25326: Array string operation failed for message at index string

Cause: Array operation fails for the message at specified index. Look at the remainder of the error stack to see what the problem was.

Action: Fix cause of error and retry array operation.

ORA-25327: Array size is invalid

Cause: Array size must be a positive, non-zero integer.

Action: Use corrected array size and retry array operation.

ORA-25328: string argument size string is smaller than array size

Cause: The size of the argument is smaller than the given array size.

Action: Lower array size or use a larger sized input argument.

ORA-25329: AQ array operations not allowed on 8.0 queues

Cause: An array enqueue/dequeue was attempted on an 8.0 queue.

Action: Use single enqueue/dequeue with this queue.

ORA-25330: PL/SQL associative arrays may not be used with AQ array operations

Cause: A PL/SQL associative array was provided for the payload parameter in an enqueue/dequeue array operation.

Action: Use VARRAY or NESTED TABLE types with AQ array operations.

ORA-25331: cannot downgrade because there are commit-time queue tables

Cause: An attempt was made to downgrade a database that has commit-time queue tables.

Action: Drop all commit-time queue tables before attempting the downgrade.

ORA-25332: Invalid release value string for queue table compatible parameter

Cause: The release level given for the queue table compatible parameter is invalid

Action: Specify a valid release value for the queue table compatible parameter

ORA-25333: Buffered Queue to Queue propagation did not connect to the correct instance

Cause: Queue to Queue propagation for buffered messages didn't connect to the correct instance, most likely because service was not started for the destination queue.

Action: No user action is required. Propagation will start the service for the destination queue and retry.

ORA-25334: Buffered propagation must restart as the destination queue was recreated/moved

Cause: Buffered propagation destination queue was recreated or its ownership was moved to another instance during propagation.

Action: No user action is required. Propagation will reinitialize its metadata and retry.

ORA-25335: AQ array operations not allowed for buffered messages

Cause: An array enqueue/dequeue was attempted for buffered messages

Action: Use single enqueue/dequeue for buffered messages or an array size of one.

ORA-25336: Cannot contact instance string during Streams AQ operation

Cause: The specified instance was not responding to AQ requests.

Action: Set parameter aq_tm_processes to a non-zero value. If the problem persists, contact Oracle Support Services.

ORA-25337: Cannot propagate in queue-to-queue mode to a database with version lower than 10.2

Cause: Remote subscriber with queue_to_queue mode set to TRUE was added. The remote subscriber is on a database version lower than 10.2. Propagation was scheduled to a destination database with version lower than 10.2.

Action: Remove the remote subscriber with queue_to_queue mode and add the subscriber back with queue_to_queue set to FALSE. Unschedule the queue-to-queue propagation and schedule propagation in queue-to-dblink mode.

ORA-25338: operation 'string' is not allowed for sync_capture 'string'

Cause: An attempt was made to execute the specified operation for a sync_capture process.

Action: Remove the offending call.

ORA-25339: STREAMS 'string' must be sync_capture

Cause: The specified capture STREAMS did not exist or was not a sync_capture process.

Action: Remove the offending call.

ORA-25340: must use commit-time queue for sync_capture

Cause: An attempt was made to create a sync_capture without using a commit-time queue.

Action: Rerun statement with a commit-time queue.

ORA-25341: sync_capture does not support "string"."string" because of the following reason:

Cause: sync_capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.

Action: Revise the Capture rules to skip over the table in question. One option is to remove the rule that captures changes from the unsupported table. Check DBA_STREAMS_TABLE_RULES to determine the rule on the table specified in the error. Also query the DBA_STREAMS_UNSUPPORTED view to determine which tables are not supported by STREAMS and for what reason. For potential workarounds to certain unsupported properties, see Metalink.

ORA-25342: cannot downgrade because there are apply processes for user buffered messages

Cause: An attempt was made to downgrade a database that has apply process for user-buffered messages.

Action: Drop all the apply processes for user-buffered messages before attempting the downgrade.

ORA-25343: Streams error queue cannot be exported

Cause: An attempt was made to export a database that has apply errors.

Action: Delete or reexecute errors before attempting the export.

ORA-25344: statement has bind variables

Cause: Current API could not handle a statement with bind variables.

Action: Use alternative API which handles bind variables.

ORA-25345: requested AQ minimum Oracle Streams Pool size string greater than Oracle Streams Pool size string

Cause: The minimum value requested for the Oracle Streams Advanced Queuing (AQ) pool size was greater than the Oracle Streams pool size.

Action: Set the minimum value for the Oracle Streams AQ pool size to less than or equal to the Oracle Streams pool size.

ORA-25346: requested AQ maximum Oracle Streams Pool size string less than AQ minimum Oracle Streams Pool size string

Cause: The maximum value requested for the Oracle Streams Advanced Queuing (AQ) pool size was less than the minimum value of the Oracle Streams (AQ) pool size.

Action: Set the maximum value for the Oracle Streams AQ pool size to greater than or equal to the minimum value of the Oracle Streams AQ pool size.

ORA-25347: Dequeue operation on sharded queue is not possible.

Cause: Dequeue of a buffered subscriber or JMS sharded queue failed with OCIAQDeq().

Action: Use OCIAQDeq2() for buffered subscribers and JMS sharded queues.

ORA-25348: cannot connect to shard owner instance string of database string

Cause: An Oracle Advanced Queuing (AQ) operation was attempted at a non-owner instance of the shard which could not establish an internal connection to it.

Action: Set the listener information in the REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter. If the REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter is already set, then retry the operation from the suggested owner instance.

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 INIT.ORA 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-25401: can not continue fetches

Cause: A failure occured since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches.

Action: Reexecute the statement and start fetching from the beginning

ORA-25402: transaction must roll back

Cause: A failure occured 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-25405: transaction status unknown

Cause: A failure occured 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-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-25409: failover happened during the network operation,cannot continue

Cause: The connection was lost when fetching a LOB column.

Action: Failover happened when fetching LOB data directly or indirectly. Please replay the top level statement.

ORA-25410: Application requested failover retry

Cause: The application failover callback requested failover retry.

Action: None. Informational only.

ORA-25411: transaction replay was not successful

Cause: Replay was not able to restore the transaction state to match the pre-failover state.

Action: Manually determine if it is safe to resubmit the transaction.

ORA-25412: transaction replay disabled by call to string

Cause: The application called an Oracle Call Interface (OCI) function that is not supported with transactional failover.

Action: Manually recover the pending transaction.

ORA-25413: transaction replay disabled by user request

Cause: The application explicitly disabled transaction replay by setting attribute OCI_ATTR_TRANSACTIONAL_TAF=FALSE.

Action: This message is informational only.

ORA-25414: Uncommitted transaction detected after TAF callback.

Cause: The Transparent Application Failover (TAF) callback started a transaction and did not commit or rollback prior to exiting.

Action: End the transaction with a COMMIT or a ROLLBACK prior to exiting the TAF callback.

ORA-25415: Application Continuity replay initiation timeout exceeded.

Cause: Application Continuity replay was attempted after REPLAY_INITIATION_TIMEOUT expired. The value for REPLAY_INITIATION_TIMEOUT is configured for the service to which the application is connected.

Action: Manually recover the pending transaction.

ORA-25416: Retry current call

Cause: Failover sucessfully recovered an in-flight transaction

Action: Re-execute the current call

ORA-25417: replay disabled; call (string) too large to record

Cause: Oracle Call Interface (OCI) Application Continuity replay was attempted after a large call that could not be recorded due to excessive memory requirements.

Action: Break up the call into smaller pieces and retry failover, or manually retry the user operation.

ORA-25418: transaction replay disabled by the use of object type in function string

Cause: The application used an Oracle Call Interface (OCI) object type that is not supported with transactional failover.

Action: Manually recover the pending transaction.

ORA-25419: transaction replay disabled in function string by the use of unsupported type string

Cause: The application used an Oracle Call Interface (OCI) type that is not supported with transactional failover.

Action: Manually recover the pending transaction.

ORA-25420: too many calls in request; replay disabled

Cause: Application Continuity failover was attempted after executing a request with a large number of Oracle Call Interface (OCI) calls, so replay of the request was not possible.

Action: Resubmit and consider partitioning application work into more requests with fewer OCI calls in each request.

ORA-25425: connection lost during rollback

Cause: The connection was lost while issuing a rollback and the application failed over.

Action: The connection was lost and failover happened during rollback. 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 dblink 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 dblink if you need to connect to this instance.

ORA-25427: cannot downgrade database links after database link data dictionary has been upgraded

Cause: An attempt was made to downgrade after the upgrade of the database link data dictionary.

Action: Drop the database links before attempting the downgrade.

ORA-25428: authentication failure while connecting through database link

Cause: An attempt to connect using the database link failed.

Action: Ensure connection details for the database link are correct.

ORA-25429: Break request cannot be propagated over shared database link.

Cause: No call in progress over shared database link.

Action: No action required. This is an informational message only.

ORA-25430: connected user database links are not supported in proxy session

Cause: A connected user database link is being used to connect to a remote database from a proxy user session.

Action: No action required. This was an informational message only.

ORA-25431: Connection with protocol string is disallowed by the outbound_dblink_protocols parameter.

Cause: An attempt to connect using the database link failed because the network protocol used for the database link is disallowed.

Action: Either set the value of the outbound_dblink_protocols initialization parameter appropriately to include the required protocol or change the protocol used by the database link to conform to the protocols allowed by the outbound_dblink_protocols parameter.

ORA-25433: User string does not have INHERIT REMOTE PRIVILEGES privilege on connected user string.

Cause: An attempt was made to use a connected user database link inside a definer's rights function, procedure or view, and the owner of the function, procedure or view lacked INHERIT REMOTE PRIVILEGES privilege on the connected user.

Action: Either do not start the function, procedure or view, or grant the owner of the function, procedure or view INHERIT REMOTE PRIVILEGES privilege on the connected user.

ORA-25434: Connected user database link usage by the common user string is not allowed.

Cause: The COMMON_SCHEMA_ACCESS lockdown profile feature was disabled.

Action: Either do not use the database link as a common user or have the administrator enable COMMON_SCHEMA_ACCESS lockdown profile feature.

ORA-25435: Database link cannot be used after failing over with Transparent Application Continuity.

Cause: The use of database link was detected in the failed-over session while Transparent Application Continuity was in use.

Action: Consider whether the application can use Transaction mode of Application Continuity that supports failover with database links. (Use FAILOVER_TYPE=TRANSACTION). Use Fast Application Notification with Oracle connection pools for planned maintenance.

ORA-25436: invalid table alias: string

Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias.

Action: Check the valid table aliases in the evaluation context, and try again with a valid alias.

ORA-25437: duplicate table value for table alias: string

Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias.

Action: Check the table values specified, and try again with only one value per table.

ORA-25438: invalid variable name: string

Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name.

Action: Check the valid variable names in the evaluation context, and try again with a valid name.

ORA-25439: duplicate variable value for variable: string

Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name.

Action: Check the variable names specified, and try again with only one value per variable.

ORA-25440: invalid table alias: string

Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias.

Action: Check the valid table aliases in the evaluation context, and try again with a valid name.

ORA-25441: duplicate column value for table alias: string

Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied.

Action: Check the table and column values specified, and try again with either a table value or column values for each table alias.

ORA-25442: too many column values for table alias: string

Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias.

Action: Check the column values specified, and try again with the right number of column values.

ORA-25443: duplicate column value for table alias: string, column number: string

Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number.

Action: Check the column values specified, and try again with only one column value for each table alias, and column number.

ORA-25444: invalid ROWID: string for table alias: string

Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias.

Action: Check the column values specified, and try again with only one column value for each table alias, and column number.

ORA-25445: invalid column number: string for table alias: string

Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value.

Action: Check the column values specified, and try again with a valid column number.

ORA-25446: duplicate column value for table alias: string, column: string

Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name.

Action: Check the column values specified, and try again with only one column value for each table alias, and column name.

ORA-25447: encountered errors during evaluation of rule string.string

Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule.

Action: Check the rule and the values passed to evaluate, and try again with valid values.

ORA-25448: The string string.string has errors.

Cause: An attempt to load the specified rule or expression failed due to errors in the rule or expression.

Action: Check the rule or expression and retry the operation.

ORA-25449: invalid variable name: string

Cause: An attempt to evaluate was made, which failed because one of the attribute values specified had an invalid variable name.

Action: Check the valid variable names in the evaluation context, and try again with a valid name.

ORA-25450: error string during evaluation of rule set string.string

Cause: The specified error occurred during evaluation of the rule set.

Action: Check the error and take appropriate action.

ORA-25451: too many attribute values for variable: string

Cause: An attempt to evaluate was made, which failed because too many attribute values were supplied for the specified variable.

Action: Check the attribute values specified, and try again with the right number of attribute values.

ORA-25452: duplicate attribute value for variable: string, attribute: string

Cause: An attempt to evaluate was made, which failed because duplicate attribute values were supplied for the specified variable and attribute name.

Action: Check the attribute values specified, and try again with only one attribute value for each variable, and attribute name.

ORA-25453: invalid iterator: string

Cause: An attempt to get rule hits or to close an iterator was made, which failed because an invalid iterator was passed in.

Action: Check the iterator, and try again with a valid iterator.

ORA-25454: error during evaluation of rule set: string.string for iterator: string

Cause: An attempt to get rule hits for an iterator was made, which failed because of an error in evaluation of the specified rule set.

Action: Check the validity of the rule set and try again.

ORA-25455: evaluation error for rule set: string.string, evaluation context: string.string

Cause: An attempt to evaluate the specified rule set using the evaluation context specified failed due to some errors.

Action: Check additional errors signalled to determine the problem.

ORA-25456: rule set was modified or evaluation terminated for iterator: string

Cause: An attempt to get rule hits was made, which failed because the underlying rule set was modified after the iterator was returned.

Action: Try again after re-evaluating the rule set.

ORA-25457: evaluation function string returns failure

Cause: The specified evaluation function returned a failure during evaluation, causing evaluation to terminate.

Action: Check arguments to evaluate and retry.

ORA-25458: Value not supplied for string string

Cause: Variable or table column values were not supplied for evaluation.

Action: Supply all the required variable and column data points for Independent Expression Evaluation.

ORA-25459: Data conversion for string string failed

Cause: The attempt to convert data to the data type of the variable or column failed.

Action: Supply the correct data for variable or column.

ORA-25461: rule set not specified

Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.

Action: Check the rule set name, and try again with a valid name.

ORA-25462: evaluation context not specified

Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.

Action: Check the evaluation context name, and try again with a valid name.

ORA-25463: table alias not specified

Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name.

Action: Check the list of table values, and try again with a valid alias name.

ORA-25464: ROWID not specified for table alias: string

Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID.

Action: Check the list of table values, and try again with a valid ROWID.

ORA-25465: variable name not specified

Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name.

Action: Check the list of variable values, and try again with a valid variable name.

ORA-25466: data not specified for variable name: string

Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data.

Action: Check the list of variable values, and try again with valid data.

ORA-25467: table alias not specified

Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name.

Action: Check the list of column values, and try again with a valid alias name.

ORA-25468: column name not specified for alias: string

Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name.

Action: Check the list of column values, and try again with a valid column name.

ORA-25469: data not specified for alias: string column name: string

Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data.

Action: Check the list of column values, and try again with valid data.

ORA-25470: duplicate attribute value for variable: string

Cause: An attempt to evaluate was made, which failed because one of the attribute values supplied a value for a variable, which already had a variable value supplied.

Action: Check the variable and attribute values specified, and try again with either a variable value or attribute values for each variable.

ORA-25471: attribute name not specified for variable: string

Cause: An attempt to evaluate was made, which failed because one of the attribute values for the specified variable had a NULL attribute name.

Action: Check the list of attribute values, and try again with a valid attribute name.

ORA-25472: maximum open iterators exceeded

Cause: The open rule hit iterators in the session exceeded 2 * OPEN_CURSORS.

Action: Close some rule hit iterators.

ORA-25473: cannot store string in rule action context

Cause: The user attempted to put unsupported data types, such as LOBs and evolved ADTs, into the rule action context.

Action: Use only supported data types in rule action context.

ORA-25476: use pre-5523578 behaviour when looking up enabled roles

Cause: N/A

Action: Derive the enabled roles under the rules engine using the old method that existed before the fix to bug 5523578.

ORA-25500: database is not open

Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.

Action: Open the database and retry this command.

ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed

Cause: Database resource manager failed to change plan.

Action: Look at the alert logs to see detailed description of the error.

ORA-25502: concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running

Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system.

Action: Contact the database administrator who is responsible for the concurrent command.

ORA-25503: cannot open database because the database is being quiesced

Cause: Database cannot be opened because the system is being or has been quiesced.

Action: Open the database after the system has been quiesced.

ORA-25504: the system is already in quiesced state

Cause: Cannot quiesce the system because the system is already quiesced.

Action: n/a

ORA-25505: the system is not in quiesced state

Cause: Cannot unquiesce the system because the system is not in quiesced state.

Action: n/a

ORA-25506: resource manager has not been continuously on in some instances

Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances.

Action: n/a

ORA-25507: resource manager has not been continuously on

Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.

Action: n/a

ORA-25508: database is not mounted

Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command.

Action: Mount the database and retry this command.

ORA-25509: operation on "string"."string".string not allowed

Cause: A column has been added to a replicated table, but replication support processing has not completed.

Action: Wait until replication support processing has completed before updating the column

ORA-25510: quiesce not supported for the root container

Cause: Could not quiesce the root container.

Action: This operation is not supported for the root container.

ORA-25511: quiesce not supported for pluggable databases

Cause: Could not quiesce the pluggable database.

Action: This operation is not supported for pluggable databases.

ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string

Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.

Action: Alter the value of _DB_MTTR_SIM_TARGET.

ORA-25527: bad format of _DB_MTTR_SIM_TARGET

Cause: One value in _DB_MTTR_SIM_TARGET is empty.

Action: Set the value of _DB_MTTR_SIM_TARGET properly.

ORA-25528: too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET

Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.

Action: Alter the value of _DB_MTTR_SIM_TARGET.

ORA-25530: FAST_START_MTTR_TARGET is not specified

Cause: An attempt to start MTTR advisory was made, which failed because FAST_START_MTTR_TARGET was not specified.

Action: Set FAST_START_MTTR_TARGET.

ORA-25531: MTTR specified is too small: string

Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.

Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.

ORA-25532: MTTR specified is too large: string

Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory.

Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.

ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified

Cause: An attempt to start MTTR advisory was made, which failed because either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was specified.

Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0.

ORA-25950: missing where clause in join index specification\n

Cause: An attempt to create a join index was made, which failed because no valid where clause was found.

Action: Ensure that a where clause with valid join conditions is specified in the create index statement.

ORA-25951: join index where clause cannot contain OR condition\n

Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause.

Action: Reformulate the where clause without using ORs.

ORA-25952: join index must only contain inner equi-joins\n

Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn't an equi-inner join.

Action: Remove the inappropriate predicate.

ORA-25953: join index cannot be a functional index\n

Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone).

Action: Remove any functional indexing columns.

ORA-25954: missing primary key or unique constraint on dimension\n

Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions.

Action: Ensure that the where clause is correct (contains all of the constraint columns) and that an enforced constraint is on each dimension table.

ORA-25955: all tables must be joined in the where clause\n

Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.

Action: Ensure that the where clause contains all from clause tables.

ORA-25956: join index cannot be created on tables owned by SYS\n

Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS.

Action: Ensure that no join index related table is owned by SYS.

ORA-25957: join index where clause cannot contain cycles\n

Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle.

Action: Ensure that the where clause is in the form of a star or snowflake schema.

ORA-25958: join index where clause predicate may only contain column references\n

Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column.

Action: Ensure that the where clause only contains columns.

ORA-25959: join index must be of the bitmap type\n

Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.

Action: Make the index a bitmap index.

ORA-25960: join index cannot be based on a temporary table\n

Cause: An attempt to create a join index was made, which failed because one of the tables was temporary.

Action: Ensure no underlying tables are temporary.

ORA-25961: join index prevents dml cascade constraint operation\n

Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.

Action: Drop the join index or remove the constraint.

ORA-25962: join index prevents multitable insert or merge\n

Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.

Action: Drop the join index.

ORA-25963: join index must be created on tables\n

Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.

Action: Ensure that the from clause only contains tables.

ORA-25964: column type incompatible with join column type\n

Cause: The datatype of the join column is incompatible with the datatype of the joined column.

Action: Select a compatible datatype for the join column.

ORA-25965: fact table must be included in the from clause\n

Cause: An attempt to create a join index was made, which failed because the from clause does not contain the fact table.

Action: Ensure that the from clause contains the fact table.

ORA-25966: join index cannot be based on an index organized table\n

Cause: An attempt to create a join index was made, which failed because one of the tables was an index organized table.

Action: Ensure no underlying tables are index organized.

ORA-26000: partition load specified but table string is not partitioned\n

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\n

Cause: A nonexistent 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.\n

Cause: Parallel load was specified into a table which has index defined upon it.

Action: Drop index(es) defined upon table, or don't use parallel load, or use SKIP_INDEX_MAINTENANCE option.

ORA-26003: parallel load not supported for index-organized table string.\n

Cause: Parallel load is not supported for index-organized tables.

Action: load the index-organized table without the PARALLEL option.

ORA-26004: Tables loaded through the direct path may not be clustered\n

Cause: User attempted to load a clustered table via the direct path.

Action: Use the conventional path.

ORA-26005: Invalid handle for direct path load\n

Cause: In direct path load, the handle passed in does not match the type listed.

Action: Verify the handle and type are correct.

ORA-26006: Incorrect bind variable in column string's sql expression - string\n

Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.

Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list.

ORA-26007: invalid value for SETID or OID column\n

Cause: The value passed in a Direct Path API stream for a column containing a SETID or OID has an invalid value. SETIDs and Object IDs must be either 16 bytes of RAW data or 32 bytes of hexidecimal characters.

Action: Regenerate the Direct Path API stream with a valid value for the SETID column.

ORA-26008: Invalid syntax or bind variable in SQL string for column string.\nstring\n

Cause: See following error message for more information. A SQL string cannot have quoted strings improperly terminated. A bind variable in a SQL string cannot have a length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a double quote.

Action: Fix the SQL string. See following error for more information.

ORA-26009: stream verification error: string\n

Cause: An error has occurred in a Data Pump stream verification operation.

Action: Contact Oracle Support Services.

ORA-26010: Column string in table string is NOT NULL and is not being loaded\n

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: Cannot load type string into column string in table string\n

Cause: A column can only store data of type declared for that column. And a substitutable column can only store data of valid subtypes of the supertype declared for that column.

Action: Check that the type or subtype specified is valid for that column.

ORA-26012: header in file string has an incompatible version number\n

Cause: A dump file was specified for a load operation whose version number is incompatible with the dump file version currently produced by the Oracle server on the system. Usually this message indicates that the dump file was produced by a newer version of the Oracle server.

Action: Load this dump file using the same version of the Oracle server that created the file.

ORA-26013: List allocated may not be big enough\n

Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.

Action: Contact Oracle Customer Support.

ORA-26014: unexpected error on string string while retrieving string\nstring

Cause: The SQL error was returned from an OCIStmtExecute call.

Action: Correct the SQL error that was returned.

ORA-26015: Array column string in table string is not supported by direct path\n

Cause: User attempted to load an array column via the direct path.

Action: Use the conventional path.

ORA-26016: Virtual column string in table string.string cannot be loaded by direct path\n

Cause: You attempted to load an virtual column using the direct path.

Action: Virtual columns cannot be loaded using the direct path.

ORA-26017: global indexes not allowed for direct path load of table partition string

Cause: Global indexes are defined on a table when direct path loading a single partition of the table.

Action: n/a

ORA-26018: Column string in table string does not exist\n

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\n

Cause: The Specified column of SQL column type %s 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: None. Informational only.

ORA-26021: index string.string partition string loaded successfully with string keys

Cause: Partitioned index information put to loader log file.

Action: None. Informational only.

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: User requested 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 re-built, or, the * entire index dropped and re-created.

ORA-26031: index maintenance error, the load cannot continue

Cause: A index errror 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: column string.string encryption properties differ for source or target table

Cause: The source and destination columns did not have the same * encryption properties.

Action: For security reasons, check that the source and target table have * the same encryption properties. *

ORA-26034: Column string does not exist in stream\n

Cause: Column specified in the column list does not exist in the stream.

Action: Make sure the column exists or remove it from the list.

ORA-26035: Error attempting to encrypt or decrypt column

Cause: An error occurred while attemping to encrypt or decrypt * a database column.

Action: Verify correct encryption key was specified. *

ORA-26036: subpartition load specified but table string is not subpartitioned\n

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: must specify partition name(s) for system partitioned table string\n

Cause: An attempt was made to load a system partitioned table with no partition name(s) specified.

Action: Specify the partition name(s) explicitly.

ORA-26038: attempt to write audit record for SQL*Loader direct path load of string.string failed with error code: number\n

Cause: An attempt to write an audit record during a SQL*Loader direct path load failed.

Action: Contact Oracle Support Services.

ORA-26040: Data block was loaded using the NOLOGGING option\n

Cause: Trying to access data in block that was loaded without * redo generation using the NOLOGGING/UNRECOVERABLE option

Action: Drop the object containing the block.

ORA-26041: DATETIME/INTERVAL datatype conversion error\n

Cause: The column could not be converted from DATETIME * datatype to internal DATETIME/CHARACTER datatype.

Action: Contact Oracle Customer Support.

ORA-26045: REF column string expects string arguments; found string.\n

Cause: The number of arguments for the REF column is incorrect.

Action: Specify the correct number of input arguments for REFs. 1. Unscoped system-generated REFs can have exactly 1 or 2 input arguments. a) It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME. 2. Scoped system-generated REFs can have 1 or 2 input arguments. Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted. 3. Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments. Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.

ORA-26046: REF column string expects scoped table name string; user passed in string.\n

Cause: The scoped table name passed in by the user does not match the name in the schema.

Action: Specify the correct table name for the scoped REF column.

ORA-26048: Scoped REF column has wrong table name.\n

Cause: The scoped table name passed in by the user does not match the name in the schema.

Action: Specify the correct table name for the scoped REF column.

ORA-26049: Unscoped REF column has non-existent table name.\n

Cause: The table name passed in by the user does not exist in the schema.

Action: Specify a valid table name for the unscoped REF column.

ORA-26050: Direct path load of domain index is not supported for this column type.\n

Cause: Direct path can not load a domain index of that column type.

Action: Drop the index and try again or load using conventional path.

ORA-26051: internal error parsing packed decimal format string

Cause: A packed decimal field with a non-zero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.

Action: Examine the packed decimal field's precision and scale specifications and make sure that they contain valid values.

ORA-26052: Unsupported type number for SQL expression on column string.\n

Cause: The direct path api does not support a SQL expression on a column of that type.

Action: Make sure the types are correct.

ORA-26053: Row was not loaded due to conversion error.\n

Cause: The current row was not loaded due to a conversion error.

Action: Continue with the load anyways. 260xx - 260xx Direct Path API

ORA-26054: Direct Path Context prepared for a different mode than operation requested.\n

Cause: The user prepared the direct path context for one operation (Load, Unload, Convert), but then tried to perform a different operation.

Action: Make sure the direct path context mode and operation matches.

ORA-26055: Invalid buffer specified for direct path unload\n

Cause: The user specified a zero length or null buffer to be used for the Direct Path Unload operation.

Action: Specify a valid buffer and length.

ORA-26056: Requested direct path operation on a view is not supported.\n

Cause: An attempt was made to load into a view using direct path that has user-defined types, XML data, object type table or SQL expressions.

Action: Do not attempt to use direct path when loading a view that has nonscalar columns or when using SQL expressions on input columns.

ORA-26057: Conversion is not necessary for this direct path stream.\n

Cause: User attempted to convert a direct path stream that does not require conversion.

Action: Load the stream without conversion it.

ORA-26058: unexpected error fetching metadata for column string in table string\n

Cause: The direct path API encountered an unexpected error while retrieving metadata for a column.

Action: Contact Oracle support.

ORA-26059: Data is too large for column string\n

Cause: The direct path API encountered a column that can not be loaded because the input data is too large for a column.

Action: Make the target column larger.

ORA-26060: Can not convert type identifier for column string\n

Cause: The direct path API encountered a type identifier for a column that can not be loaded because a mapping can not be found for the input value.

Action: Verify the input data.

ORA-26061: Concurrent direct unloads is not allowed.\n

Cause: User attempted a direct unload when another is still in progress.

Action: Complete the current direct unload before starting another.

ORA-26062: Can not continue from previous errors.\n

Cause: User attempted to continue a direct path load after receiving an error which indicates the load can not continue.

Action: Address the original error that was returned.

ORA-26063: Can not flashback to specified SCN value - Wrap: string Base: string.\n

Cause: User specified an SCN which occurs before the last time the table definition was modified.

Action: Specify a more recent SCN.

ORA-26064: Invalid SCN specified - Wrap: string Base: string.\n

Cause: User specified an invalid SCN.

Action: Specify a valid SCN.

ORA-26065: check constraint cannot reference column, string, in direct path load\n

Cause: An enabled check constraint was found on a column stored as a lob.

Action: Either disable the check constraint before loading the table data * using the direct path mode, or use the conventional path mode * instead.

ORA-26076: cannot set or reset value after direct path structure is allocated

Cause: Client attempted to set or reset the number of rows in a direct path * structure after it has already been allocated and initialized. * Attributes used is one of the following: * - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache * (default is 0) * - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be * disabled on overflow (default is FALSE)

Action: Set the following attributes before: * - OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare * - OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare

ORA-26077: direct path column array is not initialized

Cause: Client attempted to allocate a column array for a direct path * function context before allocating a column array for the * table-level direct path context.

Action: Allocate the table-level direct path context's column array * via OCIHandleAlloc before allocating column arrays for * direct path function contexts.

ORA-26078: file "string" is not part of database being loaded\n

Cause: A parallel load file was specified which is not part * of the database.

Action: Check filename and pathname for correctness.

ORA-26079: file "string" is not part of table string.string\n

Cause: A parallel load file was specified which is not in the * tablespace of the table being loaded.

Action: Check to make sure that the specified parallel load file * is in the tablespace of the table being loaded.

ORA-26080: file "string" is not part of table string.string partition string\n

Cause: A parallel load file was specified which is not in the * tablespace of the table (partition, subpartition) being loaded. * When a partitioned table is being loaded, the file must be * in the tablespace of every partition or subpartition * (i.e. each (sub)partition must be in the same tablespace).

Action: Specify a different parallel load file, or no file at all.

ORA-26082: load of overlapping segments on table string.string is not allowed

Cause: Client application is attempting to do multiple direct path load * operations on the same table, but the segments overlap.

Action: Check the partition names (subname attribute of the direct path * context) being loaded. Make sure you are not loading a table, * and a partition of the same table. Make sure you are not * loading a partition, and a sub-partition within the same * partition.

ORA-26083: unsupported direct path stream version string

Cause: The stream version requested is not supported by the server.

Action: Check to make sure that the VERSION attribute of the direct * stream is not being set to an invalid value.

ORA-26084: direct path context already finished

Cause: An OCIDirPathLoadStream operation was attempted after * OCIDirPathFinish was called. Once a direct path operaton * has been finished, no more data can be loaded.

Action: Check program logic to make sure OCIDirPathLoadStream is * not called after OCIDirPathFinish.

ORA-26085: direct path operation must start its own transaction

Cause: A direct path operation is being attempted within a transaction * that has already been started.

Action: Commit the transaction and Prepare the direct path operation again.

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-26088: scalar column "string" must be specified prior to LOB columns

Cause: All scalar columns (i.e. 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 or a data save request * has been made, but the table for which the request is being made * on has a row in partial state. The row must be completed before * the segment high water marks can be moved.

Action: Either complete the row, or abort the direct path operation.

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: input data column size (number) exceeds the maximum input size (number)

Cause: The user attempted to specify a column size (%d) that exceeded * the maximum allowable input size (%d)."

Action: Make sure the input column metadata matches the column definition.

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 mis-use 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 (i.e. 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 required for column string

Cause: The conversion required for the column was not supported. For * example, conversion from date to number was not supported.

Action: Ensure that the type is correct for the source and destination. *

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

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 data file.

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 data file.

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 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 materialized view connection

Cause: The client connection handle was or became invalid.

Action: Verify that the client connection is valid.

ORA-26509: null materialized view control structure

Cause: An internal materialized view control structure could not be obtained.

Action: Check that the owner and users provided are correct.

ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes

Cause: The specified materialized view name was too long.

Action: Shorten the materialized view 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 adminstrator or DBA.

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 commited 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: materialized view control entry for 'string.string' was not found

Cause: The specified materialized view catalog control reocrd was not found.

Action: Verify that the local materialized view catalog is valid and that the local materialized view 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 materialized view logs. Check that the local site is correctly assigning new transactionIDs 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: Shutdown 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 procudure 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: materialized view sql ddl parse/expansion failed for string.string

Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site.

Action: Check that materialized view ddl sql is compatible with the currently connected version of Oracle and does not violate any of the RepAPI sql limitations or restrictions.

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 state and notify Oracle 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 state and notify Oracle 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 state and notify Oracle support.

ORA-26530: unable to build materialized view refresh control list

Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.

Action: Verify that the named materialized view(s) are properly defined and valid.

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 materialized view's master site.

Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.

ORA-26562: last RepAPI error

ORA-26563: renaming this table is not allowed

Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has beencreated.

Action: If desired, unregister the replicated table with dbms_repcat.drop_master_repobject, or use the recommended procedure to rename the master table of a materialized view.

ORA-26564: string argument is not of specified type

Cause: User passed type of the given argument number doesn't match with the type of the argument in the stored arguments.

Action: Invoke correct type procedure (i.e. 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 dblink

Action: Make sure that the dblink is valid and remote m/c is up.

ORA-26571: string.string.string: number of arguments (string) does not match replication catalog

Cause: number of arguments does not match replication catalog

Action: examine 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-26576: cannot acquire SR enqueue

Cause: An attempt to acquire the SR enqueue in exclusive mode failed.

Action: n/a

ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string\n

Cause: The materialized view consists of a view and a container table.

Action: Drop the materialized view without PRESERVE TABLE option.

ORA-26578: No capture in this multitenant container database associated with queue "string".

Cause: An outbound server's queue was not associated with a capture from the same multitenant container database (CDB) before adding or starting an outbound server.

Action: Execute the DBMS_STREAMS_ADM.CREATE_CAPTURE procedure to create a capture before adding or starting an outbound server.

ORA-26650: string string background process string might not be started successfully

Cause: An error occurred during creation of a capture or apply background process.

Action: Review V$STREAMS_CAPTURE and V$STREAMS_APPLY_COORDINATOR views for the status of these processes. Also check the trace file for more information.

ORA-26651: Unable to start or stop capture process string

Cause: An attempt was made to start or stop a capture process while another capture process was concurrently starting or stopping.

Action: You cannot concurrently start or stop capture processes. Wait before attempting to start or stop additional capture processes.

ORA-26652: Capture string did not start properly and is currently in state string

Cause: An attempt to restart a capture process failed.

Action: Review V$STREAMS_CAPTURE view for the state of the capture process. Also check the trace files for more information.

ORA-26653: Apply string did not start properly and is currently in state string

Cause: An attempt to restart an apply process failed.

Action: Streams: Review V$STREAMS_APPLY% views for the state of the apply process. Also check the trace files for more information. XStream: Review V$XSTREAM_APPLY% views for the state of the apply process. Also check the trace files for more information. GoldenGate: Review V$GG_APPLY% views for the state of the apply process. Also check the trace files for more information.

ORA-26654: Capture string attempted to connect to apply string already configured for string

Cause: An attempt was made by a GoldenGate, XStream or Streams Capture or XStream In to connect to an Apply that is already connected in the other mode.

Action: You cannot connect a capture to an apply already configured for another apply mode. Create or connect to another apply.

ORA-26655: Invalid string specified for string procedure

Cause: An attempt was made to execute the specified procedure with an invalid SCN value.

Action: Resubmit procedure with a valid SCN value.

ORA-26656: supplemental logging version error: string

Cause: The supplemental logging versions of capture side and apply side are incompatible.

Action: For incompatibility caused by a newer apply side, please bypass or migrate the incompatible logs manually and consider upgrading or patching the capture side. For incompatibility caused by an unrecognizable version group or an older apply side, please upgrade or patch the apply side. For invalid versions, the logs might have been corrupted; please verify the integrity of the supplemental logging data on the capture side.

ORA-26660: Invalid action context value for string

Cause: The value specified in the action context is invalid for use in GoldenGate, XStream or Streams.

Action: Check that the type and value are correct.

ORA-26662: unable to process string Data Dictonary information for object

Cause: The database is unable to process GoldenGate, XStream or Streams Data Dictionary for this object.

Action: Check that the compatibility for the database supports the object, and check the trace file for information about the object.

ORA-26663: error queue for apply process string must be empty

Cause: The error queue for this apply process contains error entries.

Action: Execute or delete errors in the error queue.

ORA-26664: cannot create string process string

Cause: An attempt was made to create a GoldenGate, XStream or Streams process when another was being created concurrently.

Action: Wait for the creation of the other GoldenGate, XStream or Streams process to finish before attempting to create the process.

ORA-26665: string process string already exists

Cause: An attempt was made to create a GoldenGate, XStream or Streams process that already exists.

Action: Either specify another process or remove the existing GoldenGate, XStream or Streams process.

ORA-26666: cannot alter string process string

Cause: An attempt was made to alter a GoldenGate, XStream or Streams process that is currently running.

Action: Stop the GoldenGate, XStream or Streams process with FORCE parameter set to TRUE and reissue the command.

ORA-26667: invalid string parameter string

Cause: An attempt was made to specify an invalid parameter.

Action: Check the documentation for valid parameters.

ORA-26668: string process string exists

Cause: An attempt to remove the component failed because it is associated with the GoldenGate, XStream or Streams process.

Action: Either remove the process manually or specify the "cascade" option in dbms_streams_adm.remove_queue.

ORA-26669: parameter string inconsistent with parameter string

Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.

Action: Check the documentation for valid parameter values.

ORA-26670: No capture is found for queue 'string'

Cause: An attempt was made to add an XStream outbound server to a queue using uncommitted data mode when no co-located XStream capture was configured for that queue.

Action: Change to committed data mode or configure a local XStream capture for the specified queue then retry the operation.

ORA-26671: maximum number of string processes exceeded

Cause: Cannot create additional GoldenGate, XStream or Streams processes since the maximum number of processes has been reached.

Action: Remove existing GoldenGate, XStream or Streams processes and retry the operation.

ORA-26672: timeout occurred while stopping string process string

Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams process to shut down.

Action: Retry the operation. If the error persists, try stopping the process with the FORCE option, or contact Oracle Support Services.

ORA-26673: duplicate column name string

Cause: An attempt was made to specify a duplicate column name in an LCR.

Action: Remove the duplicate column and retry the operation.

ORA-26674: Column mismatch in 'string.string' (LCR: string type=string; DB: string type=string)

Cause: The columns in the LCR were not the same or not found in the database table.

Action: Alter the database table.

ORA-26675: cannot create string capture process string

Cause: GoldenGate, XStream or Streams capture process could not be created because one or more parameters contain invalid value.

Action: Refer to trace file for more details.

ORA-26676: Table 'string.string' has string columns in the LCR and string columns in the replicated site

Cause: The number of columns in the LCR was not the same as the the replicated site.

Action: Alter the table structure

ORA-26677: string downstream capture process string cannot proceed

Cause: Database global name has been set to a value which is same as the source database name of the downstream capture process.

Action: Change database global name to a value other than the source database name for the downstream capture.

ORA-26678: string downstream capture process for source database string must be created at database string first

Cause: A GoldenGate, XStream or Streams downstream capture process was nonexistent when this operation was attempted.

Action: Create a GoldenGate, XStream or Streams downstream capture process, then retry the operation.

ORA-26679: operation not allowed on LOB or LONG columns in LCR

Cause: Certain operations on LOB/LONG columns of the LCR through rule-based transformations, DML handlers, or error handlers were not allowed.

Action: Do not perform restricted operations on LOB or LONG columns in LCRs. See the documentation for operations that are restricted on LOB/LONG columns in LCRs.

ORA-26680: object type not supported

Cause: The specified object type is not supported.

Action: Retry with a supported object type.

ORA-26681: command type not supported

Cause: The specified command type is not supported.

Action: Retry with a supported command type.

ORA-26682: invalid value for publication_on

Cause: The publication_on parameter should be either 'Y' or 'N'

Action: Retry with a proper value for publication_on.

ORA-26683: invalid value for value_type

Cause: The value_type parameter should be either 'OLD' or 'NEW'

Action: Retry with proper value_type.

ORA-26684: invalid value for value_type

Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'

Action: Retry with proper value_type.

ORA-26685: cannot apply transactions from multiple sources

Cause: Transactions from multiple sources were sent to the same apply process.

Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.

ORA-26686: cannot capture from specified SCN

Cause: An attempt was made to specify an invalid SCN.

Action: Retry with a valid SCN.

ORA-26687: no instantiation SCN provided for "string"."string" in source database "string"

Cause: Object SCN was not set. If the object is a table, then both fields will be filled, for example "SCOTT"."EMP". If the object is a schema, only one field will be set, for example "SCOTT"."". And if the object is the entire database, no fields will be set, for example ""."".

Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN

ORA-26688: missing key in LCR

Cause: Metadata mismatch, or not enough information in the user generated LCR.

Action: Alter the database object, or provide all defined keys in the LCR.

ORA-26689: column datatype mismatch in LCR

Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.

Action: Alter the database object.

ORA-26690: datatype not supported at non-Oracle system

Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.

Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.

ORA-26691: operation not supported at non-Oracle system

Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.

Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.

ORA-26692: invalid value string, string should be in string format

Cause: The parameter specified was not in the correct format.

Action: Specify the parameter value in the correct format.

ORA-26693: string string process dropped successfully, but error occurred while dropping rule set string

Cause: An attempt to drop an unused rule set failed after dropping the GoldenGate, XStream or Streams proccess successfully.

Action: Check existence of rule set and manually drop if necessary.

ORA-26694: error while enqueueing into queue string.string

Cause: An error occurred while enqueueing a message.

Action: If the situation described in the next error on the stack can be corrected, do so.

ORA-26695: error on call to string: return code string

Cause: A locking related call failed.

Action: Try the call again after fixing the condition indicated by the return code.

ORA-26696: no string data dictionary for object with number string and version number string from source database string

Cause: An attempt to access the database object failed because the data dictionary for the object was either never populated or it was purged.

Action: Make sure the GoldenGate, XStream or Streams data dictionary is created by calling DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION.

ORA-26697: LCR contains extra column 'string'

Cause: The LCR contained more columns than the replicated table.

Action: Alter the database object.

ORA-26698: string did not have a string rule set

Cause: The GoldenGate, XStream or Streams client does not have a rule set of the indicated type.

Action: Verify that the GoldenGate, XStream or Streams client has a rule set of the specified type, and retry the operation.

ORA-26699: string message consumer string already exists

Cause: An attempt was made to create a GoldenGate, XStream or Streams message consumer that already exists.

Action: Either specify another message consumer or remove the existing GoldenGate, XStream or Streams message consumer.

ORA-26701: string process string does not exist

Cause: An attempt was made to access a GoldenGate, XStream or Streams process which does not exist.

Action: Check with the relevant security views for the correct name of the object.

ORA-26704: The Owner instance string of the queue table is not up or the QMN0 process is down.

ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded

Cause: An attempt was made to downgrade a capture process after it has upgraded the GoldenGate, XStream or Streams data dictionary.

Action: Drop the capture process before attempting the downgrade.

ORA-26706: cannot downgrade capture process

Cause: An attempt was made to downgrade a capture process that has a higher version than the downgrade release version.

Action: Drop the capture process after capture has finished consuming all the redo logs before attempting the downgrade.

ORA-26708: remote DDL not supported by STREAMS : dblink string

Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not supported.

Action: Do not attempt to apply DDL LCRs via a dblink. If possible, filter out DDL LCRs before applying.

ORA-26709: Downstream Capture RFS restart

Cause: Remote file server (RFS) process was restarted to reflect a change in DOWNSTREAM_REAL_TIME_MINE option of the GoldenGate, XStream or Streams capture process.

Action: No action required. This is an informational message only.

ORA-26710: incompatible version marker encountered during Capture

Cause: Capture process cannot mine redo from a version higher than the current software release version.

Action: Drop and recreate the capture process.

ORA-26711: remote table does not contain a primary key constraint

Cause: The master table for remote apply does not constain a primary key constraint or the primary key constraint has been disabled.

Action: Create a primary key constraint on the master table or enable the existing constraint.

ORA-26712: remote object is "string"."string"\@"string"

Cause: See the preceding error message to identify the cause. This message names the remote object, usually a table or view, for which an error occurred when GoldenGate, XStream or Streams tried to access it for remote apply.

Action: See the preceding error message.

ORA-26713: remote object does not exist or is inaccessible

Cause: GoldenGate, XStream or Streams replication could not access the named table or view at a remote database to apply changes.

Action: Confirm that the given remote table or view exists and is accessible through the given database link. When using a Heterogeneous Services database link to access a non-Oracle system, it may be necessary to check administration details for network connections at the non-Oracle system.

ORA-26714: User Error string encountered during apply process

Cause: An error was encountered during an apply process.

Action: Query the DBA_APPLY_ERROR view to determine the error and take the appropriate action.

ORA-26715: time limit reached

Cause: The specified time limit was reached for the GoldenGate, XStream or Streams process.

Action: Restart the GoldenGate, XStream or Streams process, increasing the TIME_LIMIT parameter if necessary.

ORA-26716: message limit reached

Cause: The specified message limit was reached for the Capture process.

Action: Restart the Capture process, increasing the MESSAGE_LIMIT parameter if necessary.

ORA-26717: SCN limit reached

Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams process.

Action: Change the MAXIMUM_SCN parameter, then restart the GoldenGate, XStream or Streams process.

ORA-26718: transaction limit reached

Cause: The specified transaction limit was reached for the Apply process.

Action: Restart the Apply process, increasing the TRANSACTION_LIMIT parameter if necessary.

ORA-26721: enqueue of the LCR not allowed

Cause: An apply process attempted to enqueue an LCR with a LONG column. This is not supported.

Action: Modify rules or unset the enqueue destination to prevent LCRs with LONG columns from being enqueued by the apply process.

ORA-26723: user "string" requires the role "string"

Cause: The caller did not have the specified role or called the procedure from a definer's rights package or procedure.

Action: Grant the specified role to the caller. If the procedure is called from a definer's rights package or procedure, change the definer's rights package or procedure to an invoker's rights package or procedure. Or grant all the privileges for the specified role explicitly.

ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.

Cause: The Capture or Apply user was specified as SYS by a user other than SYS.

Action: Set SYS as the Capture or Apply user while logged in as SYS.

ORA-26725: cannot downgrade apply handlers

Cause: An attempt was made to downgrade apply handlers that are not associated with a local database object, or the apply handlers are associated with a specific apply process.

Action: Drop the associated apply handlers before attempting the downgrade.

ORA-26726: standby and DOWNSTREAM_REAL_TIME_MINE are incompatible

Cause: An attempt was made to set the standby database and DOWNSTREAM_REAL_TIME_MINE option of the Oracle GoldenGate, XStream or Oracle Streams capture process on the same database.

Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a Oracle GoldenGate, XStream or Oracle Streams capture process on a standby database. Do not attempt to change a database role to standby if there exists a capture process with the DOWNSTREAM_REAL_TIME_MINE parameter set to Y.

ORA-26727: Cannot alter queue_to_queue property of existing propagation.

Cause: The queue_to_queue property was specified for an existing propagation.

Action: Pass NULL for the queue_to_queue argument.

ORA-26730: string 'string' already exists

Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE failed because the item in question already exists.

Action: Remove the object if appropriate and re-attempt the operation.

ORA-26731: string 'string' does not exist

Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist.

Action: Make sure the object exists and re-attempt the operation.

ORA-26732: invalid file group string privilege

Cause: The specified privilege number that was specified is invalid.

Action: Check specification of dbms_file_group for valid privileges.

ORA-26733: timed-out waiting for file group lock

Cause: The procedure waited too long while getting a lock to perform a file group repository operation.

Action: Retry the operation.

ORA-26734: different datafiles_directory_object parameter must be specified

Cause: The attempted operation involved datafiles platform conversion which required the datafiles_directory_object parameter to be specified for placing the converted data files.

Action: Retry the operation after specifying a valid datafiles_directory_object parameter. This directory must be different from the directory objects for any of the datafiles for the specified file group version.

ORA-26735: operation not allowed on the specified file group version

Cause: One or more datafiles or export dump file(s) were missing from the specified file group version.

Action: Retry the operation after adding all the data files and Data Pump dump file(s) to the specified version.

ORA-26736: Data Pump error

Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation.

Action: Check the error stack and trace file for error details.

ORA-26737: version string already has an export dump file

Cause: A Data Pump dump file was added to a file group version that already has a dump file.

Action: Remove the existing dump file if appropriate, and retry the operation.

ORA-26738: string 'string' is not empty

Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects.

Action: Remove the child objects, then retry the operation.

ORA-26740: cannot downgrade because there are file groups

Cause: An attempt was made to downgrade a database that has file groups.

Action: Drop all file groups before attempting the downgrade.

ORA-26741: cannot assemble lobs

Cause: An attempt was made to assemble lobs, but the compatibility of the source database for the LOB information is lower than 10.2.0.

Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while this handler is processing LOB information from a source database with a compatibility level lower than 10.2.0.

ORA-26742: Maximum number of ignored transactions exceeded

Cause: An attempt was made to add more than the allowed number of ignored transactions.

Action: Please clear the current list of ignored transactions.

ORA-26744: string capture process "string" does not support "string"."string" because of the following reason: string

Cause: GoldenGate, XStream or Streams capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.

Action: Revise the Capture rules to skip over the table in question. One way might be to add a negative rule excluding changes from the unsupported table from being captured. Streams: Also query the DBA_STREAMS_UNSUPPORTED view to determine which tables are not supported by Streams and for what reason. Consider adding negative rules for any tables that may be captured, but are present in this view. XStream: Also query the DBA_XSTREAM_OUT_SUPPORT_MODE view to determine which tables are not supported by XStream and for what reason. Consider adding negative rules for any tables that may be captured, but are present in this view. GoldenGate: Also query the DBA_GOLDENGATE_SUPPORT_MODE view to determine which tables are not supported by GoldenGate and for what reason. Consider adding EXCLUDETABLE statements for any tables that may be captured, but are present in this view. For potential workarounds to certain unsupported properties, see Metalink.

ORA-26745: cursors (string) are not sufficient

Cause: The maximum number of open cursors was too small for GoldenGate, XStream or Streams Apply.

Action: Increase the value of open_cursors.

ORA-26746: DDL rule "string"."string" not allowed for this operation

Cause: A DDL rule was specified for this operation.

Action: Specify a non-DDL rule for this operation.

ORA-26747: The one-to-many transformation function string encountered the following error: string

Cause: The specified transformation function encountered an error.

Action: Ensure that the function does not process or return DDL LCRs. Also ensure that the function does not return NULL.

ORA-26748: The one-to-one transformation function string encountered the following error: string

Cause: The specified transformation function encountered an error.

Action: Ensure that the function does not return an LCR that has a different type from the LCR which was passed to the function. Also ensure that the function does not return NULL. For DDL transformation functions, creating and returning a new DDL LCR is not allowed.

ORA-26752: Unsupported LCR received for "string"."string"

Cause: GoldenGate, XStream or Streams capture process received an LCR with unsupported operation from LogMiner.

Action: Stream:If this object is listed in DBA_STREAMS_UNSUPPORTED view, modify rules to prevent changes made to this object from getting captured. XStream: If this object is listed in DBA_XSTREAM_OUT_SUPPORT_MODE view, modify rules to prevent changes made to this object from getting captured. GoldenGate: If this object is listed in DBA_GOLDENGATE_SUPPORT_MODE view, modify rules to prevent changes made to this object from getting captured.

ORA-26753: Mismatched columns found in 'string.string'

Cause: The columns in the LCR were not the same as the table in the database.

Action: Alter the database table.

ORA-26754: cannot specify both one-to-one transformation function string and one-to-many transformation function string

Cause: Both a one-to-one transformation function and a one-to-many transformation function were specified for a rule.

Action: Remove either the one-to-one transformation function, or the one-to-many transformation function.

ORA-26757: Timed out waiting for remote operation on instance string to finish

ORA-26760: Could not find message number string for transaction with id string

Cause: Error

Action: Contact Oracle support"

ORA-26761: Standby Redo Logs not available for real time mining

Cause: Standby Redo Logs required for real time mining by downstream capture process were not available.

Action: Check the configuration of Standby Redo Logs and retry the operation at a later time. To start the capture process without real time mining property, reset DOWNSTREAM_REAL_TIME_MINE parameter of the capture process and retry the operation.

ORA-26762: Cannot autogenerate name for parameter string because of the following reason: string

Cause: An error was encountered while attempting to generate a name for a parameter which was passed a NULL value.

Action: If possible, fix the error, otherwise specify the parameter name explicitly.

ORA-26763: invalid file type "string"

Cause: An invalid file type was specified for the ASM file.

Action: Check documentation for valid ASM file types.

ORA-26764: invalid parameter "string" for local capture "string"

Cause: An invalid parameter was specified for the local capture process.

Action: Check documentation for valid parameters.

ORA-26765: invalid parameter "string" for downstream capture "string"

Cause: An invalid parameter was specified for the downstream capture process.

Action: Check documentation for valid parameters.

ORA-26766: Unexpected redo pattern encountered by LogMiner

Cause: LogMiner encountered an unexpected redo pattern. This is usually caused by tables with unsupported data types or newer table features.

Action: Remove the capture rule for the table and restart capture.

ORA-26767: Not enough redo log information for LogMiner

Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with UNRECOVERABLE clause was specified for the table.

Action: Remove the capture rule for the table and restart capture.

ORA-26768: Maximum number of unsupported tables exceeded

Cause: An attempt was made to add more than the allowed number of unsupported tables.

Action: Clear the current list of unsupported tables.

ORA-26770: Index-organized table not supported

ORA-26771: User-defined column type not supported

ORA-26772: Encrypted column not supported

ORA-26773: Invalid data type for column "string"

ORA-26774: Queue table not supported

ORA-26775: Temporary table not supported

ORA-26776: Subordinate object not supported

ORA-26777: External table not supported

ORA-26778: File column not supported

ORA-26779: Materialized view not supported

ORA-26780: Object table not supported

ORA-26781: Nested table not supported

ORA-26782: Function-based index not supported

ORA-26783: Column data type not supported

ORA-26785: Object has a NULL value

Cause: A method was invoked on a NULL object.

Action: Initialize the object with a non-NULL value.

ORA-26786: A row with key string exists but has conflicting column(s) string in table string

Cause: The row to update or delete exists in the table but had conflicting value for some columns.

Action: For Streams and XStream, please define a conflict resolution, or resolve the conflict and execute the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status of the database guard to ensure local modifications are not allowed, then re-instantiate the table and contact support if the problem persists. For GoldenGate, configure Conflict Resolution (CDR) or REPERROR handler for the table and restart replicat.

ORA-26787: The row with key string does not exist in table string

Cause: The row to update or delete does not exist in the table.

Action: For Streams and XStream, please define a conflict resolution, or resolve the conflict and execute the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status of the database guard to ensure local modifications are not allowed, then re-instantiate the table and contact support if the problem persists. For GoldenGate, configure Conflict Resolution (CDR) or REPERROR handler for the table and restart replicat.

ORA-26788: The column string is not encrypted in the local database.

Cause: The column in the destination database is NOT encrypted while it is encrypted in the source database.

Action: Set the corresponding column property in the destination database to 'encrypted' or change the apply parameter, PRESERVE_ENCRYPTED_COLS, to 'N' to supress the error.

ORA-26789: Cannot split propagation string because only one propagation originates from its source queue "string"."string"

Cause: Only one propagation originated from the propagation source queue.

Action: Please do not split this propagation.

ORA-26790: Requesting a lock on string "string" timed out

Cause: Could not get a lock on the object because another process was holding the lock.

Action: Please try later.

ORA-26791: Cannot split or merge propagation "string"

Cause: A process tried to split or merge this propagation, but failed and left STREAMS in an inconsistent state.

Action: Query DBA_RECOVERABLE_SCRIPT_BLOCKS view, and roll back the script which tried to split or merge this propagation.

ORA-26792: Invalid source database name string

Cause: The value for the source database global name was not valid.

Action: Specify a valid database global name. If the source database is not the local database, check the listener is up and running.

ORA-26793: Number of capture processes that enqueued message to queue "string"."string" not equal to one

Cause: Split-merge API requires only one capture process enqueued message to the queue where the propagation originated

Action: Please drop one capture, or split or merge another propagation.

ORA-26794: Hierarchically enabled tables not supported

Cause: Hierarchically enabled tables are not supported.

Action: Disable hierarchy for the table.

ORA-26795: Cannot modify an LCR received from an XStream outbound server

Cause: An attempt was made to modify an LCR generated by an XStream outbound server.

Action: Clone the LCR generated by the XStream outbound server by using the provided OCILCR* functions, such as OCILCRNew, OCILCRHeaderSet, and OCILCRRowColumnInfoSet. Then modify the cloned LCR.

ORA-26798: LOB logical change record (LCR) missing LOB column in table "string"."string"

Cause: The apply slave could not fill update LOB because of missing LOB column.

Action: Check that all LOB columns have been sent correctly.

ORA-26799: unique constraint string.string violated for table string.string with column values string

Cause: The row to update or insert violated the unique constraint.

Action: For XStreams, define a conflict resolution, or resolve the conflict and execute the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR.

ORA-26800: Apply not the only subscriber for "string"."string".

Cause: The combined capture and apply optimization could not be used since Apply was not the lone subscriber to the queue.

Action: Apply has to be the only subscriber to the queue.

ORA-26801: More than one subscriber for "string"."string".

Cause: Multiple subscribers were found when the combined capture and apply optimization was configured to only work for one subscriber.

Action: Configure a single subscriber, apply or propagation for the queue, or enable the optimization for multiple subscribers.

ORA-26802: Queue "string"."string" has messages.

Cause: The combined capture and apply optimization could not be used since the queue had messages.

Action: Make sure queue is empty before starting apply and capture.

ORA-26803: Subscribers have changed for queue "string"."string".

Cause: The combined capture and apply optimization could not be used since the subscribers had changed.

Action: Optimization can be used only if the queue has a single subscriber.

ORA-26804: Apply "string" is disabled.

Cause: The apply process was disabled or aborted.

Action: Start the apply process.

ORA-26805: Queue "string"."string" has rule based subscribers.

Cause: The combined capture and apply optimization could not be used since the queue had rule based subscribers.

Action: Make sure queue has no rule based subscribers before starting apply and capture.

ORA-26806: Remote database could not support combined capture and apply optimization.

Cause: The remote database has a version lower than Oracle 11.0 and hence does not understand combined capture and apply optimization.

Action: Upgrade the remote database to Oracle 11.0 or above in order to use the combined capture and apply optimization.

ORA-26807: Database link is not NULL for Apply with the name "string" .

Cause: The combined capture and apply optimization could not be used since apply_database_link was not NULL.

Action: Drop and recreate the apply with NULL value for apply_database_link.

ORA-26808: Apply process string died unexpectedly.

Cause: Apply process died unexpectedly.

Action: Check your system for anomalies and restart apply. If this error persists, contact Oracle Support Services. See trace file for more details.

ORA-26809: Capture aborted: checkpoint-free mode requires combined capture and apply mode.

Cause: The requirements for combined capture and apply mode were broken.

Action: Restore the combined capture and apply mode and then restart the capture. If combined capture and apply mode is no longer desired, drop the existing checkpoint-free capture and create another one that will take checkpoints.

ORA-26810: Apply "string" on database "string" is in the mode of combined capture and apply.

Cause: The combined capture and apply optimization could not be used because Apply was already in the mode of combined capture and apply.

Action: Do not configure two captures for one apply.

ORA-26811: Client has already attached to string apply "string".

Cause: The client has already attached to the specified apply process.

Action: Detach apply process before reattach.

ORA-26812: An active session currently attached to XStream server "string".

Cause: An attempt was made to attach to the specified XStream server while another session was attached to it.

Action: Retry when there is no session attaching to the specified XStream server.

ORA-26813: The value for argument "ARRAY_SIZE" is too small

Cause: The value for argument "ARRAY_SIZE" was less than the number of columns in the requested column list.

Action: Check the return value for "NUM_COLUMNS" parameter then allocate all input arrays to at least that size and invoke the same OCI function again.

ORA-26814: The value for argument string exceeds maximum string

Cause: The value for specified value exceeded the maximum allowed.

Action: Correct the value of specified argument.

ORA-26815: Error from Apply Network Receiver for Apply "string" and Capture "string".

Cause: The Apply Network Receiver aborted due to an unexpected error.

Action: Query DBA_APPLY_ERROR to determine the error and then restart the Capture and Apply.

ORA-26816: string apply process "string" (OS id string) is exiting due to ORA-string.

Cause: An apply process encountered an unexpected error.

Action: Query DBA_APPLY to examine the status of Apply and restart Apply if needed.

ORA-26817: string capture process "string" is unable to communicate with capture server string during initialization.

Cause: Capture server might not be started properly

Action: Fix any errors during capture server creation and re-start capture process

ORA-26818: string capture process string receives an error from capture server.

Cause: Capture server received an error.

Action: Check log for error details.

ORA-26819: string capture server for apply "string" and capture "string"encounters disabled or aborted propagation "string".

Cause: Propagation was disabled or aborted.

Action: Start propagation.

ORA-26820: string capture server for apply "string" and propagation "string" becomes active and needs join capture process "string".

Cause: Capture server was waiting for propagation or apply to start

Action: Capture process needs restart (done automatically).

ORA-26821: No propagation process found between source queue "string"."string" and destination queue "string"."string".

Cause: Propagation has not been configured.

Action: Configure a propagation between specified queues and restart capture.

ORA-26822: Failure in creating capture servers (ksv error code string).

Cause: Failure in ksv slave creation.

Action: Identify the actual ksv error and act accordingly.

ORA-26823: string capture server string is unable to communicate with capture process "string".

Cause: Capture process was not started properly or was aborted.

Action: If Oracle GoldenGate, XStream or Streams capture process was stopped, then restart the capture process. Otherwise, fix any errors during the capture process creation and restart the capture process.

ORA-26824: user-defined XStream callback error

Cause: A value other than OCI_CONTINUE or OCI_SUCCESS was returned for the user-defined XStream callback function. Any returned value other than OCI_CONTINUE or OCI_SUCCESS is invalid.

Action: Verify that either OCI_CONTINUE or OCI_SUCCESS is returned from the user-defined XStream callback function.

ORA-26825: STREAMS process "string" is not configured as an XStream outbound server.

Cause: An attempt was made to attach to a STREAMS apply process, which was not configured as an XStream outbound server.

Action: Check the apply name or re-create the apply process as an XStream outbound server.

ORA-26826: string apply coordinator and apply slave are unable to communicate.

Cause: GoldenGate, XStream or Streams Apply process may have died unexpectedly.

Action: Check your system for anomalies and restart apply. If this error persists, contact Oracle Support Services. See trace file for more details.

ORA-26827: Insufficient privileges to attach to XStream outbound server "string".

Cause: Sufficient privileges were not granted to attach to the specified XStream outbound server.

Action: Query DBA_XSTREAM_OUTBOUND view to get the connect_user value for the specified outbound server. Then modify the application to connect to the outbound server's database using this value.

ORA-26828: XStream outbound server "string" requires combined capture and apply mode.

Cause: The specified XStream outbound server was not in combined capture and apply mode.

Action: Restore the combined capture and apply mode and then restart the capture.

ORA-26829: Cannot set "DISABLE_ON_ERROR" parameter to 'N'.

Cause: An attempt was made to change the "DISABLE_ON_ERROR" parameter for an XStream outbound server to 'N'.

Action: Remove invalid statement.

ORA-26830: Cannot define handler for an XStream outbound server.

Cause: An attempt was made to define a handler for an XStream outbound server.

Action: Remove invalid statement.

ORA-26831: Cannot delete or execute error transaction from XStream outbound server "string".

Cause: An attempt was made to delete or execute an error transaction from the specified XStream outbound server.

Action: Remove invalid statement.

ORA-26832: Unable to create XStream outbound server "string" due to existing handler.

Cause: An attempt was made to create the specified XStream outbound server while there was a handler defined for the specified server.

Action: Use DBMS_APPLY_ADM.SET_DML_HANDLER procedure to remove all handlers defined on the specified server then retry statement.

ORA-26833: string failed to update acknowledgment SCN for propagation "string" from capture "string" to apply "string".

Cause: propagation might have been modified after GoldenGate, XStream or Streams was started.

Action: Ensure propagation is configured properly and restart GoldenGate, XStream or Streams.

ORA-26834: Unable to alter parameter 'string' because string capture process is not configured to run locally

Cause: An attempt was made to alter the specified capture parameter when the GoldenGate, XStream or Streams capture process was not configured to run on the local database.

Action: Remove the invalid parameter or use DBMS_CAPTURE_ADM.ALTER_CAPTURE procedure to alter the parameter.

ORA-26835: The source database for XStream outbound server "string" is invalid

Cause: An attempt was made to add an XStream outbound server with a source database that was different from the associated capture's source database.

Action: Correct the value for the 'source_database' parameter in the call.

ORA-26836: The specified rules must be created from the same subsetting condition

Cause: An attempt was made to remove an outbound server's subset rules when the specified INSERT, UPDATE, and DELETE rules were not created from the same subsetting condition.

Action: Correct the rules in the statement.

ORA-26837: Server "string" is not an XStream inbound server

Cause: An attempt was made to execute a procedure not appropriate on an XStream inbound server.

Action: Replace with a procedure appropriate for an XStream inbound server and resubmit.

ORA-26838: Setting apply parameter "string" is not permitted for XStream Outbound Server

Cause: An attempt was made to set an apply parameter that was not applicable for XStream Outbound Server.

Action: Configure XStream Outbound Server using valid parameters. Check the documentation for valid parameter values.

ORA-26839: Apply tag for apply "string" is not permitted for XStream Outbound Server

Cause: An attempt was made to set an apply tag that was not applicable for XStream Outbound Server.

Action: Do not set the apply tag when using XStream Outbound Server.

ORA-26840: Combined capture and apply optimization is disabled because string is unable to identify an apply for the source database "string".

Cause: There were multiple Streams apply processes using the same queue which made combined capture and apply (CCA) optimization not possible.

Action: If Streams performance is an issue, check the "Combined Capture and Apply Optimization" chapter in the "Oracle Streams Concepts and Administration" book. Then reconfigure the Streams processes to meet this optimization's requirements.

ORA-26841: No subscribers are found for queue "string"."string".

Cause: No propagation or apply was configured for the specified queue.

Action: Configure propagation or apply for the specified queue.

ORA-26842: Setting apply directive "string" is not permitted for XStream Outbound Server

Cause: An attempt was made to set an apply directive that was not applicable for XStream Outbound Server.

Action: Configure XStream Outbound Server using valid directives. Check the documentation for valid directives.

ORA-26843: Local propagation "string" found for capture queue "string"."string".

Cause: The combined capture and apply optimization could not be used because a local propagation was attached to the capture queue.

Action: Remove the local propagation and restart capture.

ORA-26844: Found "string" active automatic split jobs for string Capture "string" in DBA_STREAMS_SPLIT_MERGE

Cause: Only one active split job is allowed for each GoldenGate, XStream or Streams Capture, but multiple active automatic split jobs were found in DBA_STREAMS_SPLIT_MERGE.

Action: Check trace to see how the jobs were submitted and drop them.

ORA-26845: Found "string" active split rows with the same cloned string Capture "string" in DBA_STREAMS_SPLIT_MERGE

Cause: In DBA_STREAMS_SPLIT_MERGE, for active split rows, the column CLONED_CAPTURE_NAME should be unique. However, multiple rows were found whose ACTION_TYPE column is 'SPLIT', ACTIVE column is 'ACTIVE' and have the same CLONED_CAPTURE_NAME.

Action: Check trace to see how the rows were inserted and call DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.

ORA-26846: Found "string" active automatic merge jobs for cloned string Capture "string" in DBA_STREAMS_SPLIT_MERGE

Cause: Only one active merge job is allowed for each cloned GoldenGate, XStream or Streams Capture , but multiple active automatic merge jobs were found in DBA_STREAMS_SPLIT_MERGE.

Action: Check trace to see how the jobs were submitted and drop them.

ORA-26847: Found invalid string type: "string"

Cause: Invalid GoldenGate, XStream or Streams type to split off was found. Type should only be 'PROPAGATION'(1) or 'APPLY'(2).

Action: Check trace to see how the invalid GoldenGate, XStream or Streams type was created and correct it.

ORA-26848: Split a nonexistent Streams Capture process "string" in job "string"

Cause: The job attempted to split a non-existent original Streams Capture.

Action: Drop the split job, or wait until the Streams Capture comes to existence.

ORA-26849: Split a nonsplittable string Capture process "string" in job "string"

Cause: The job tried to split a GoldenGate, XStream or Streams Capture that was not splittable. That is, the Capture either had less than two subscribers, or it was not the only Capture of its queue.

Action: Drop the split job, or wait untill the GoldenGate, XStream or Streams Capture becomes splittable.

ORA-26850: Changes to queue subscribers were detected by string capture process.

Cause: The subscribers for capture queue might have changed.

Action: Capture process will restart automatically.

ORA-26851: Unable to connect to apply "string" because it has connected to another capture.

Cause: Another capture process is already connected to apply.

Action: Wait for the connected capture process to terminate or abort the connected capture process.

ORA-26852: Invalid NULL value for column_value parameter.

Cause: NULL is not allowed to be passed as the column value.

Action: Replace NULL with a proper AnyData instance containing NULL, e.g., sys.AnyData.ConvertVarchar2(NULL), as the column value if the column value is NULL.

ORA-26853: invalid cca maximum percentage string

Cause: Specified percentage value was not in range 0 - 100.

Action: Specify a percentage value in the range 0 - 100.

ORA-26854: string string has no enqueue or dequeue privileges to the queue.

Cause: The GoldenGate, XStream or Streams user did not have enqueue or dequeue privilege to the queue.

Action: Grant GoldenGate, XStream or Streams user enqueue or dequeue privileges to the queue.

ORA-26855: string string has insufficient database privilege to access the queue.

Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to access the queue.

Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue.

ORA-26856: STREAMS string has insufficient database privilege to access the queue.

Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to access the queue.

Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue.

ORA-26857: LCR position cannot be null (XID=string).

Cause: The position of an LCR in the specified transaction was null.

Action: Use OCILCRHeaderSet to define the LCR position.

ORA-26858: LCR position must be strictly increasing (XID='string', LCR position='string', previous position='string').

Cause: The position of an LCR in the specified transaction was less than or equal to the previous LCR in transaction.

Action: Use OCILCRHeaderSet to correct the LCR position.

ORA-26859: Server "string" is not an XStream outbound server

Cause: An attempt was made to execute a procedure not appropriate on an XStream outbound server.

Action: Replace with a procedure appropriate for an XStream outbound server and resubmit.

ORA-26860: Different transactions must have different transaction IDs (XID='string', LCR position='string', previous commit position='string').

Cause: The position of an LCR in the specified transaction was greater than the position of the previous commit LCR in transaction with same transaction ID.

Action: Use different transaction IDs for different transactions.

ORA-26862: LCR position must be greater than the processed low position of the XStream inbound server (XID='string', LCR position='string').

Cause: The position of an LCR in the specified transaction was less than or equal to the processed low postion of the XStream inbound server.

Action: Use OCILCRHeaderSet to correct the LCR position.

ORA-26863: Job "string" showing as an active job in DBA_STREAMS_SPLIT_MERGE does not exist in DBA_SCHEDULER_JOBS.

Cause: An active job showing in DBA_STREAMS_SPLIT_MERGE did not exist. It may have been dropped accidently or something was wrong with it.

Action: Check trace to identify the problem and call DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.

ORA-26864: Error occurred in string automatic job: "string"

Cause: An error has happened inside GoldenGate, XStream or Streams automatic job.

Action: Check trace for more detail.

ORA-26865: must send a COMMIT LCR to end transaction 'string' before sending another transaction

Cause: An attempt was made by a client application to send LCRs for a new transaction before sending a COMMIT LCR for the specified transaction.

Action: Modify the client application to send a COMMIT LCR at the end of the specified transaction.

ORA-26866: The Queue of string Apply process "string" is not changeable.

Cause: Not all of the conditions for the Queue of a GoldenGate, XStream or Streams Apply process to be changeable were met. Conditions are: -The Apply process is not running. -The Apply process has no error. -The Apply process has no spilling. -The Apply process is not used for XStream Outbound or Inbound Servers. -The Apply process is a local Apply process. -The corresponding GoldenGate, XStream or Streams Capture process should be stopped.

Action: Make sure all of the conditions are met.

ORA-26867: string must be called during OCIXStreamOutLCRReceive execution

Cause: An attempt was made to execute the specified function while OCIXStreamOutLCRReceive call was not in progress.

Action: Check your program and make sure the specified call is invoked during OCIXStreamOutLCRReceive callback function.

ORA-26868: string must be called during OCIXStreamInLCRSend execution

Cause: An attempt was made to execute the specified function while OCIXStreamInLCRSend call was not in progress.

Action: Check your program and make sure the specified call is invoked during OCIXStreamInLCRSend callback function.

ORA-26869: must attach to an XStream inbound server before executing string function

Cause: An attempt was made to invoke the specified function before executing OCIXStreamInAttach call.

Action: Add OCIXStreamInAttach call before the specified function.

ORA-26870: cannot call string while OCIXStreamInLCRCallbackSend call is still executing.

Cause: An attempt was made to invoke the specified call while OCIXStreamInLCRCallbackSend call was executing.

Action: Check your program and remove the specified call when there is an OCIXStreamInLCRCallbackSend call in progress.

ORA-26871: unexpected string call (expecting string)

Cause: Could be one of the following reasons: 1) An attempt was made to invoke OCIXStreamInChunkSend when the most recent LCR or chunk sent did not have the OCI_XSTREAM_MORE_ROW_DATA flag set; 2) An attempt was made to invoke OCIXStreamInLCRSend when the most recent LCR or chunk sent had OCI_XSTREAM_MORE_ROW_DATA flag set.

Action: n/a

ORA-26872: must attach to an XStream outbound server before executing string function

Cause: An attempt was made to invoke the specified function before executing OCIXStreamOutAttach call.

Action: Add OCIXStreamOutAttach call before the specified function.

ORA-26873: cannot call string while OCIXStreamOutLCRCallbackReceive call is still executing.

Cause: An attempt was made to invoke the specified call while OCIXStreamOutLCRCallbackReceive call was executing.

Action: Check your program and remove the specified call when there is an OCIXStreamOutLCRCallbackReceive call in progress.

ORA-26874: string Capture process "string" cannot be split.

Cause: An attempt was made to split a GoldenGate, XStream or Streams Capture process that could not be split. That is, the Capture process either had less than two subscribers, or it was not the only Capture process of its queue.

Action: Wait until the GoldenGate, XStream or Streams Capture process can be split.

ORA-26875: Timeout while string automatic split job "string" waits for the subscriber "string" of Capture process "string" to acknowledge split

Cause: To split a subscriber of a GoldenGate, XStream or Streams Capture process, an automatic split job needs to wait until the subscriber acknowledges the split. The wait timed out.

Action: n/a

ORA-26876: invalid processed low-watermark (current position=string; new position=string)

Cause: An attempt was made to set the processed low-watermark to a value that was less than the current processed low-watermark.

Action: Correct the processed low-watermark in OCIXStreamOutProcessedLWMSet call.

ORA-26877: must reattach after an OCIXStreamOut call was interrupted

Cause: An attempt was made to execute another OCIXStreamOut API when an earlier call was interrupted because the XStream outbound server was disabled or the client requested cancellation of the operation.

Action: Execute OCIXStreamOutAttach call to reattach to the same XStream outbound server.

ORA-26878: inconsistent input LCR (LCR is 'string' type, expecting 'string')

Cause: An attempt was made to send an LCR that was not consistent with the specified LCR type.

Action: Correct your application to specify an LCR type that agrees with the LCR to be sent.

ORA-26879: "SET_ENQUEUE_DESTINATION" directive is not permitted on rules used by XStream outbound server "string"

Cause: One or more rules, used by the specified XStream outbound server, had SET_ENQUEUE_DESTINATION directive defined.

Action: Execute the following: 1) Execute query SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner, xr.rule_set_name FROM dba_apply_enqueue e, dba_xstream_rules xr WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name AND xr.streams_name = specified outbound server; 2) For each rule returned, execute DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION procedure to set the destination queue to null, or execute DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated rule set.

ORA-26880: "SET_EXECUTE" directive is not permitted on rules used by XStream outbound server "string"

Cause: One or more rules, used by the specified XStream outbound server, had SET_EXECUTE directive defined.

Action: Execute the following: 1) Execute query SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner, xr.rule_set_name FROM dba_apply_execute e, dba_xstream_rules xr WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name AND xr.streams_name = specified outbound server; 2) For each rule returned, use DBMS_APPLY_ADM.SET_EXECUTE procedure to set the EXECUTE parameter to TRUE, or use DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated rule set.

ORA-26881: ORA-string: string raised in string automatic string job:"string"."string" for Capture process "string" and cloned Capture process "string".

Cause: An error was raised in a GoldenGate, XStream or Streams automatic split/merge job for the given original and cloned Capture processes.

Action: Check the corresponding split/merge row in DBA_STREAMS_SPLIT_MERGE view, alert log and trace file for details.

ORA-26882: Timeout while string automatic split/merge job:"string"."string" tried to lock Capture process "string".

Cause: The GoldenGate, XStream or Streams Capture process could be locked by other automatic split/merge jobs.

Action: No action required. The GoldenGate, XStream or Streams automatic split/merge job will retry automatically.

ORA-26883: Timeout due to string Apply process "string" while merge original Capture process "string" and cloned Capture process "string".

Cause: When merging two GoldenGate, XStream or Streams Capture processes, the merge needs to wait untill the Apply process of the cloned Capture process goes ahead of the slowest subscriber of the original Capture process. This wait timed out.

Action: Make sure the GoldenGate, XStream or Streams Apply process still works properly.

ORA-26884: Not allowed to specify OCI_LCR_ROW_COLVAL_OLD with OCILCR_NEW_ONLY_MODE.

Cause: An attempt was made to call OCILCRRowColumnInfoGet function with OCI_LCR_ROW_COLVAL_OLD and OCILCR_NEW_ONLY_MODE.

Action: Change OCI_LCR_ROW_COLVAL_OLD to OCI_LCR_ROW_COLVAL_NEW or remove OCILCR_NEW_ONLY_MODE argument.

ORA-26885: OCIXStreamInCommit called before OCIXStreamInFlush

Cause: An attempt was made to call OCIXStreamInCommit before calling OCIXStreamInFlush.

Action: Call OCIXStreamInFlush prior to calling OCIXStreamInCommit.

ORA-26886: LCR commit position ('string') must be greater than the applied high position of the XStream inbound server (position='string').

Cause: The position of the commit LCR was less than or equal to the applied high postion of the XStream inbound server.

Action: Set the commit position higher than the applied high position.

ORA-26887: Insufficient privileges to attach to XStream inbound server "string".

Cause: Sufficient privileges were not granted to attach to the specified XStream inbound server.

Action: Query DBA_XSTREAM_INBOUND view to get the apply_user value for the specified XStream outbound server. Then, modify the application to connect to the inbound server's database using this value.

ORA-26888: Redo compatibilty must be 10.2 or greater

Cause: XStream Out requires redo comptibility to be 10.2 or greater.

Action: Drop the outbound server.

ORA-26889: LOB assembly not supported for PDML parent transaction string, child transaction string.

Cause: LOB assembly is not supported for PDML transactions.

Action: Disable LOB assembly, or filter out the PDML transaction.

ORA-26890: Invalid update LCR on Oracle Sequence "string"."string"

Cause: The new value column list of an update LCR on an Oracle Sequence did not have non-null columns "CYCLE#", "INCREMENT$", "CACHE" and "HIGHWATER".

Action: Make sure the new value column list has all the required columns. This might be a user error if the LCR is from an XStream In client.

ORA-26891: Target Oracle Sequence "string"."string" has inconsistent parameters with the source.

Cause: The source and target Oracle Sequences did not have the identical cache size, increment value, and cycle flag needed for replication purposes.

Action: Make sure the source and target Oracle Sequences have identical parameters. This might be a user error if the LCR is from an XStream In client.

ORA-26892: XStream feature not supported

Cause: The XStream feature was not supported.

Action: No action necessary.

ORA-26893: Input LCR must be a commit LCR

Cause: The input LCR was not a commit LCR.

Action: Make sure the input LCR is a commit LCR.

ORA-26894: Invalid "string" in Apply Progress redo

Cause: The value of the field reported was possibly corrupted.

Action: Contact Oracle Support Services.

ORA-26895: Setting parameter "string" of Streams process "string" is only permitted for Oracle GoldenGate or XStream.

Cause: An attempt was made to set a parameter that is only allowed for XStream.

Action: Oracle GoldenGate license is needed to use this parameter.

ORA-26896: Attempted to connect multiple Oracle GoldenGate Capture processes, including "string", with XStream outbound server "string" through queue "string"."string"

Cause: An attempt was made to connect multiple Oracle GoldenGate Capture processes through a queue with the XStream outbound server.

Action: Each XStream outbound server can only connect with one co-located Capture process. Remove extra Capture processes.

ORA-26897: Unable to start string capture "string" because its subscribers "string" and "string" have different purpose

Cause: An attempt was made to start an Oracle Capture process but it failed to start because its subscribers had conflicting purpose.

Action: Remove one of the specified subscribers from the capture queue.

ORA-26898: Unable to create "string" because there is an Oracle Capture process using the same queue "string"."string"

Cause: An attempt was made to create an inbound server using the same queue that was used by an Oracle Capture process.

Action: Resubmit the statement using another queue name.

ORA-26899: internal string error

Cause: An internal Streams, XStream or GoldenGate error has occurred.

Action: Please contact Oracle customer support.

ORA-26900: Streams failed to update data dictionary table for propagation "string" from capture "string" to apply "string".

Cause: The data dictionary table was corrupted.

Action: Validate the data dictionary table to restart GoldenGate, XStream or Streams capture process.

ORA-26901: string propagation sender in the combined capture and apply mode is to be suspended while apply is disabled.

Cause: The corresponding subscriber was dropped or split.

Action: No action necessary.

ORA-26902: string propagation sender in the combined capture and apply mode is to be suspended while apply is enabled.

Cause: The corresponding subscriber was dropped or split.

Action: No action necessary.

ORA-26903: Invalid edition name "string"

Cause: The edition associated with the LCR did not exist in the destination database.

Action: Check if the edition needs to be created manually on the destination database or if the CREATE EDITION statement for this edition has been applied properly on the destination database.

ORA-26904: Invalid bind variable "string" in LCR field expression.

Cause: In the statement handler, the bind variables listed in the SQL expression did not match the allowed Logical Change Record field names.

Action: Verify that all the bind variables listed in the expression are legal Logical Change Record fields.

ORA-26905: Invalid LCR method expression "string" in statement handler.

Cause: The Logical Change Record method listed was not allowed in the statement handler.

Action: Verify that the Logical Change Record method listed in the expression is a legal DBMS_LCR method.

ORA-26906: No change handler exists.

Cause: There was no change handler for the specified apply, operation, source table, change table, and capture values.

Action: Query DBA_APPLY_CHANGE_HANDLERS view to find the correct change handler.

ORA-26907: Insufficient privileges to set converge tag

Cause: Privileges were insufficient to set converge tag.

Action: The invoker needs EXECUTE_CATALOG_ROLE or execute privilege on DBMS_STREAMS_ADM to set converge tag. Grant appropriate privileges to the invoker.

ORA-26908: XStream API must be executed using a dedicated server process.

Cause: An attempt was made to execute XStream API using a shared server process.

Action: Replace the connect string in the client application to use a dedicated server process.

ORA-26909: cannot reexecute an eager error

Cause: An attempt was made to reexecute an eager error transaction. An eager transaction is applied before the apply process sees the commit or rollback for the transaction.

Action: Fix the cause of the eager error and restart the apply process. When apply is restarted, capture will automatically resend the transaction, and the transaction will be applied by the apply process.

ORA-26910: user error string encountered in eager mode

Cause: An error was encountered during eager apply. An eager transaction is applied before the apply process sees the commit or rollback for the transaction. If an error occurs during an eager transaction, the transaction will be rolled back.

Action: Query the DBA_APPLY_ERROR view to determine the error and take the appropriate action. The apply process will need to be restarted to apply the transaction that had the error. When apply is restarted, capture will automatically resend the transaction, and the transaction will be applied by the apply process.

ORA-26911: invalid oldest position (current position=string; new position=string)

Cause: An attempt was made to set the oldest position to a value that was less than the current value.

Action: Correct the oldest_position argument in OCIXStreamOutProcessedLWMSet2 call.

ORA-26912: not allowed to invoke 'string' while in committed data-only mode

Cause: An attempt was made to call the specified API while the attached XStream server was in committed data-only mode.

Action: Perform one of the following: 1) If the invalid call is OCIXStreamOutProcessedLWMSet2, then change it to OCIXStreamOutProcessedLWMSet or pass a null oldest_position to OCIXStreamOutProcessedLWMSet2 call. 2) If the invalid call is OCIXStreamInProcessedLWMGet2, then change it to OCIXStreamInProcessedLWMGet or pass a null oldest_position to OCIXStreamInProcessedLWMGet2 call.

ORA-26913: must connect to instance string where string string server "string" is running

Cause: The client application was not connected to the same Oracle RAC instance as the specified Oracle GoldenGate or XStream server.

Action: Connect to the specified instance using the network service name obtained from the following query: SELECT network_name FROM all_queues q, all_xstream_outbound ob WHERE q.owner = ob.queue_owner AND q.name = ob.queue_name AND server_name = '<server_name>';

ORA-26914: Unable to communicate with string capture process "string" from outbound server "string".

Cause: Capture process might not haven been started properly or was aborted.

Action: If Oracle GoldenGate or XStream capture process was stopped, then restart the capture process. Otherwise, query the DBA_CAPTURE view to determine the reason and take the appropriate action. If the error is ORA-4031, either increase the initialization parameter STREAMS_POOL_SIZE or increase the capture parameter MAX_SGA_SIZE or increase both. Refer to the XStream documentation for additional information on these parameters.

ORA-26915: Unable to return Logical Change Record (LCR) information due to missing data dictionary.

Cause: The current session was unable to return the requested information on the given LCR due to missing dictionary data on that LCR.

Action: Detach and reattach the XStream outbound server. Then retry the current call.

ORA-26916: Must call OCIPOGGRedoLogOpen function before OCIPOGGRedoLogRead

Cause: An attempt was made to call OCIPOGGRedoLogRead before calling OCIPOGGRedoLogOpen.

Action: Add OCIPOGGRedoLogOpen call before OCIPOGGRedoLogRead.

ORA-26917: OCIPOGG API must be executed using a dedicated server process.

Cause: An attempt was made to execute OCIPOGG API using a shared server process.

Action: Replace the connect string in the client application to use a dedicated server process.

ORA-26918: Must use 'string' procedure for outbound server "string".

Cause: An attempt was made to execute START_APPLY on an outbound server that uses uncommitted data mode.

Action: Use the specified procedure instead.

ORA-26919: Capture "string" is not associated with queue "string"."string".

Cause: The capture specified in the ADD_OUTBOUND procedure was not associated with the specified queue.

Action: Resubmit the ADD_OUTBOUND procedure after removing either the capture_name or the queue_name argument.

ORA-26920: string outbound server "string" has been stopped.

Cause: The specified outbound server was stopped.

Action: Execute START_OUTBOUND procedure to restart the outbound server or execute OCIXStreamOutAttach function to reattach to the outbound server.

ORA-26921: Cannot alter the start SCN or time of string Capture "string".

Cause: An attempt was made to alter the start SCN or time for a capture while other outbound servers were still attached to it.

Action: Execute the following: 1) Get the names of other outbound servers currently attached to the specified Capture using the query: SELECT server_name FROM dba_xstream_outbound WHERE (status = 'ATTACHED') AND (server_name '<altered_server>') AND (capture_name = '<specified_capture_name>'); 2) Detach the client application from each server_name returned. 3) Retry the operation.

ORA-26922: user string does not have LOGMINING privilege

Cause: An attempt was made to start the capture process or attach to an outbound server when the specified user did not have LOGMINING privilege.

Action: Grant LOGMINING privilege to the specified user and resubmit the failed operation.

ORA-26923: cannot configure string outbound server "string" with string capture "string" due to different purpose

Cause: An attempt was made to configure an outbound server with a capture used for different purpose.

Action: Execute the following: 1) Get the purpose of each capture and its associated queue: SELECT capture_name, queue_owner, queue_name, purpose FROM dba_capture; 2) Resubmit the statement using a queue or capture with the same purpose.

ORA-26924: cannot configure string using "string"."string" queue because it is used by "string" for string purpose

Cause: An attempt was made to configure the specified process using a queue already used by another process for different purpose.

Action: Resubmit the statement using another queue of the same purpose.

ORA-26925: cannot configure outbound server "string" with capture "string" because it is not using apply-state checkpoint

Cause: An attempt was made to configure an outbound server with a capture not using apply-state checkpoint.

Action: Specify a different capture in the ADD_OUTBOUND procedure or re-create the capture and resubmit the statement.

ORA-26926: Unable to attach because capture "string" is missing dictionary redo logs

Cause: The specified capture was unable to locate the dictionary redo log.

Action: Check the state of the specified capture from gv$streams_capture to determine the SCN or filename of the missing log file. Confirm that the filename exists and is accessible online and also in the DBA_REGISTERED_ARCHIVED_LOG view. In addition, for local capture, confirm that an entry exists for the file in the V$ARCHIVED_LOG view. If an entry is missing, it can be added using the ALTER DATABASE REGISTER .... LOGFILE command, specifying the keyword LOGICAL LOGFILE or PHYSICAL LOGFILE as appropriate.

ORA-26927: Unable to communicate with string capture process "string" from outbound server "string".

Cause: A timeout occurred while waiting for capture to respond.

Action: Check the state of the specified capture from GV$XSTREAM_CAPTURE view. Determine the reason for capture's unresponsiveness. If streams_pool_size is not set or set with an inadequate value, consider setting or increasing the value of this parameter.

ORA-26928: Unable to communicate with string apply coordinator process "string" from outbound server "string".

Cause: A timeout occurred while waiting for apply coordinator to respond.

Action: Check the state of the specified apply coordinator from GV$STREAMS_APPLY_COORDINATOR view. Determine the reason for apply coordinator's unresponsiveness. If streams_pool_size is not set or set with an inadequate value, consider setting or increasing the value of this parameter.

ORA-26929: altering an outbound server with a remote capture is not allowed

Cause: An attempt was made to alter an outbound server with a remote capture.

Action: None

ORA-26930: User "string" does not have privileges to perform this operation

Cause: An attempt was made to create, alter, or drop a process that has a different user (such as capture user or apply user) than the invoking user.

Action: Use the DBMS_XSTREAM_AUTH.GRANT_ADMIN_PRIVILEGE or DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE procedures to grant the invoking user proper privileges.

ORA-26931: This procedure can only be invoked from the root container.

Cause: An attempt was made to execute a procedure in a multitenant container database (PDB) or a non-container database.

Action: Execute the procedure from the root container.

ORA-26932: Streams configuration is not allowed in a container database.

Cause: An attempt was made to configure a Streams environment in a container database.

Action: None

ORA-26933: Cannot start Streams process "string" while in a container database.

Cause: An attempt was made to start the specified Streams process while in a container database.

Action: None

ORA-26934: Streams synchronous capture is not supported in a container database.

Cause: An attempt was made to perform a DML operation on a table being captured by a Streams synchronous capture in a container database.

Action: Remove all Streams synchronous captures then reexecute the DML operation.

ORA-26935: Unsupported type string.string for parameter for procedure string.string.string.\n

Cause: Apply encountered a procedure call with a parameter with an unsupported type.

Action: Modify the rules to filter out the procedure call.

ORA-26936: must execute OCIPOGGCaptureAttach before invoking string function

Cause: An attempt was made to invoke the specified function before executing OCIPOGGCaptureAttach call.

Action: Add OCIPOGGCaptureAttach call before the specified function.

ORA-26937: client has already attached to string capture "string".

Cause: The client was already attached to the specified capture.

Action: Detach from the specified capture before reattaching.

ORA-26938: cannot pack LCR into LCR buffer (buffer size is string, LCR size is string)

Cause: The logical change record (LCR) buffer was not large enough to store the current LCR.

Action: Increase the buffer size in the OCIPOGGCaptureAttach call.

ORA-26939: string capture "string" is disabled.

Cause: The capture process was disabled or aborted.

Action: Start the capture process.

ORA-26940: OCIPOGGCapture API must be executed using a dedicated server process.

Cause: An attempt was made to execute OCIPOGGCapture API using a shared server process.

Action: Replace the connect string in the client application to use a dedicated server process.

ORA-26941: unable to perform LOB assembly for table string.string

Cause: The apply process was unable to perform the LOB assembly for a DML for the specified table.

Action: Verify that the storage type for the columns are compatible at the source and destination.

ORA-26942: LCR should not contain old value for column string in table string.string

Cause: The LCR contained old values for LOB, XMLType and object columns.

Action: Remove old values for any LOB, XMLType and object columns in the LCR.

ORA-26943: cross PDB operation not allowed

Cause: An attempt was made to perform an operation on a container database different from the container database where the call was made.

Action: Log into the root container or into the container where you want to perform the requested action.

ORA-26944: User "string" attempted to invoke a procedure without proper permissions.

Cause: An attempt was made to invoke a procedure without proper permissions.

Action: Use the DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE to grant the invoking user proper privileges.

ORA-26945: unsupported hint string

Cause: The specified hint was not supported.

Action: Remove the hint from the SQL statement.

ORA-26946: OCIPOGGRedoLog API not supported in CDB.

Cause: An attempt was made to call an OCIPOGGRedoLog API in a multitenant container database (CDB).

Action: Do not call the OCIPOGGRedoLog API in a CDB.

ORA-26947: Oracle GoldenGate replication is not enabled.

Cause: The 'enable_goldengate_replication' parameter was not set to 'true'.

Action: Set the 'enable_goldengate_replication' parameter to 'true' and retry the operation. Oracle GoldenGate license is needed to use this parameter.

ORA-26948: Streams API must be executed using a dedicated server process.

Cause: The dblink configured for the propagation from the capture queue to the apply queue is using a shared server connection.

Action: Modify the dblink for this propagation to use a dedicated server connection.

ORA-26949: Advanced Replication is not allowed in a container database.

Cause: An attempt was made to configure an advanced replication in a multitenant container database (CDB).

Action: Do not call the Advanced Replication API in a CDB.

ORA-26951: table "string"."string" has column data type not supported by conflict resolution

Cause: A conflict was detected, but unsupported columns prevented resolving the conflict.

Action: Remove conflict resolution configuration for tables with LOB, LONG, XML, object, or extended types.

ORA-26952: could not clone from the specified clone_capture_name string while creating capture process string

Cause: The specified clone_capture_name could not be used as a clone candidate while creating the capture process.

Action: Re-create the capture without setting clone_capture_name.

ORA-26953: source database character set is not a subset of the mining database character set

Cause: An attempt was made to configure a downstream capture but the source database character set was not a subset of the mining database character set.

Action: Use AL32UTF8 character set or other compatible character set for the mining database.

ORA-26954: invalid protocol (opcode string) received during XStream execution

Cause: An internal protocol error occurred while executing an XStream function.

Action: Contact Oracle Support Services.

ORA-26955: cannot capture TIMESTAMP WITH LOCAL TIME ZONE data type

Cause: The capture process was unable to capture TIMESTAMP WITH LOCAL TIME ZONE data type because the source database time zone was not available.

Action: Refer to My Oracle Support Note 1928808.1 to set the source database time zone for the specified capture process.

ORA-26956: capture string created successfully but the source database time zone is not available

Cause: The capture process was created successfully; however, it will not be able to capture TIMESTAMP WITH LOCAL TIME ZONE data type unless the source database time zone is set.

Action: Refer to My Oracle Support Note 1928808.1 to set the source database time zone for the specified capture process.

ORA-26957: LCR identifier length is invalid.

Cause: A logical change record (LCR) identifier with an incompatible length was used.

Action: Use an LCR identifier compatible with release 12.2 or higher specification.

ORA-26958: LCR identifier version is invalid.

Cause: An invalid logical change record (LCR) identifier version number was used.

Action: Use an LCR identifier version compatible with release 12.2 or higher specification.

ORA-26959: SCN value does not fit in SCN version 1.

Cause: The system change number (SCN) value was too big to fit in the original SCN specification.

Action: Use an SCN value compatible with the original SCN specification.

ORA-26960: automatic CDR already configured for table "string"."string"

Cause: Automatic conflict detection and resolution was already configured.

Action: Remove the automatic conflict detection and resolution configuration and retry.

ORA-26961: automatic CDR not configured for table "string"."string"

Cause: Automatic conflict detection and resolution was not configured.

Action: None

ORA-26962: automatic CDR delta resolution not configured for column "string"

Cause: Automatic conflict detection and resolution delta resolution was not configured.

Action: None

ORA-26963: automatic CDR column group cannot be created

Cause: Automatic conflict detection and resolution was configured with column granularity.

Action: Remove the column-level configuration and retry.

ORA-26964: column "string" already assigned to a column group

Cause: The column was already part of a column group.

Action: Remove the column from the column group and retry.

ORA-26965: column group name "string" not available

Cause: The column group name was already in use.

Action: Remove the existing column group and retry.

ORA-26967: delete tombstone table "string"."string" cannot be dropped

Cause: An attempt was made to drop a delete tombstone table.

Action: Remove the automatic conflict detection and resolution from the base table.

ORA-26968: column group "string" not found

Cause: The column group did not exist.

Action: Check if the column group needs to be created.

ORA-26969: column "string" not part of column group "string"

Cause: The column did not belong to the column group.

Action: Check the column list and retry.

ORA-26970: table "string'" does not contain a primary key constraint

Cause: An attempt was made to configure automatic conflict detection and resolution with delete tombstones on a table without a primary key.

Action: Add a primary key and retry.

ORA-26971: resolution column "string" not present

Cause: The resolution column was not set in the logical change record (LCR).

Action: Manually resolve the conflict.

ORA-26972: An apply process attempted to modify the SYSAUX tablespace.

Cause: An ALTER TABLESPACE DDL to SYSAUX was attempted by Oracle GoldenGate, XStream or Streams process.

Action: Only SYS is allowed to modify SYSAUX.

ORA-26973: automatic CDR not supported for table "string"."string" which has long columns

Cause: Automatic conflict detection and resolution (CDR) support for long columns failed. CDR does not support long columns.

Action: None

ORA-26974: Apply process is stuck in synchronous error handling mode.

Cause: The apply process ran out of memory or queue space while suspended for synchronous error handling.

Action: Restart Oracle GoldenGate Replicat process.

ORA-26975: Only one instance of an Oracle GoldenGate downstream live standby is permitted.

Cause: An attempt was made to create an additional capture session for an Oracle GoldenGate downstream live standby system.

Action: None

ORA-26976: Oracle Streams is no longer supported.

Cause: An attempt was made to use a feature of Oracle Streams.

Action: None

ORA-26977: Parameter 'string' is not a valid parameter for an XStream inbound server.

Cause: An attempt was made to alter a parameter that was not valid for an XStream inbound server.

Action: None

ORA-26978: cannot specify more than 1000 key columns

Cause: An attempt was made to define more than 1000 key columns.

Action: Reduce the number of key columns.

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: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27003: cannot open file on device allocated with NOIO option

Cause: internal error, a file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27004: invalid blocksize specified

Cause: internal error, blocksize specified is incorrect for the device on which file is being created, aditional information indicates blocksize specified, and the function that encountered the error

Action: check for trace file and contact Oracle Support

ORA-27005: cannot open file for async I/O on device not supporting async

Cause: internal error, a file is being opened for async I/O on a device that does not support async I/O, additional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27006: sbtremove returned error

Cause: additional information indicates error returned by sbtremove, and the function that encountered the error

Action: verify that 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 vendor's storage subsystem product is operating correctly

ORA-27008: function called with invalid file structure

Cause: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27009: cannot write to file opened for read

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27010: skgfwrt: write to file failed

Cause: sbtwrite returned error, additional information indicates error returned from sbtwrite

Action: verify that vendor's storage subsystem product is operating correctly

ORA-27011: skgfrd: cannot read from file opened for write

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27012: skgfrd: read from file failed

Cause: sbtread returned error, additional information indicates error returned from sbtread

Action: verify that vendor's storage subsystem product is operating correctly

ORA-27013: skgfqdel: cannot delete an open file

Cause: internal error

Action: check for trace file and contact Oracle 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 error, additional information indicates error returned from sbtclose

Action: verify that 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 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 vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is atleast 64 (the limit specified for sbtinfo). additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH)

ORA-27018: BLKSIZE is not a multiple of the minimum physical block size

Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.

Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.

ORA-27019: tape filename length exceeds limit (SBTOPMXF)

Cause: length of tape filename provided to sequential I/O OSD functions is too long

Action: additional information indicates in which function this error is encountered, the length of filename provided, and the limit on filename

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 filename which will be passed to sbtopen was not specified.

Action: Specify a filename 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.

Action: This is an internal error in the media management product. 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.

Action: This is an internal error in the media management product. 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: internal error

Action: check for trace file and contact Oracle Support

ORA-27032: failed to obtain file size limit

Cause: getrlimit system call returned an error

Action: check errno

ORA-27033: failed to obtain file size limit

Cause: ulimit system call returned an error

Action: check errno

ORA-27034: 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 init.ora 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: created file already 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's file size limit, additional information indicates which function encountered the error

Action: raise the file size limit

ORA-27040: file create error, unable to create file

Cause: create system call returned an error, unable to create file

Action: verify filename, 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: internal error, file too large for raw partition, additional information indicates which function encountered the error

Action: check for trace file and contact Oracle 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: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle 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: 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 blocksize in the file header

Action: use a different logical block size, or do not reuse file

ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

Cause: The file was on an NFS partition and either reading the mount tab file failed or the partition wass not mounted with the correct mount option.

Action: Make sure mount tab file has read access for Oracle user and the NFS partition where the file resides is mounted correctly. For the list of mount options to use refer to your platform specific documentation.

ORA-27056: could not delete file

Cause: unlink system call returned error

Action: check errno

ORA-27057: cannot perform async I/O to file

Cause: internal error, query is being asked about async vector I/O when the file does not support async I/O

Action: check for trace file and contact Oracle Support

ORA-27058: file I/O question parameter is invalid

Cause: internal error, invalid query is being asked

Action: check for trace file and contact Oracle Support

ORA-27059: could not reduce file size

Cause: ftruncate system call returned error

Action: check errno

ORA-27060: could not set close-on-exec bit on file

Cause: fcntl system call returned error

Action: check errno

ORA-27061: waiting for async I/Os failed

Cause: aiowait function returned error

Action: check errno

ORA-27062: could not find pending async I/Os

Cause: There should have been some async I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be either because of an Oracle bug or the vendor OS bug or due to a NFS server not responding

Action: check Oracle trace file, OS message files and contact Oracle Support

ORA-27063: 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: cannot perform async I/O to file

Cause: internal error, asked to perform async I/O when IOV indicates that it cannot be performed on the file

Action: check for trace file and contact Oracle Support

ORA-27065: cannot perform async vector I/O to file

Cause: internal error, asked to perform async vector I/O when it cannot be performed on the file

Action: check for trace file and contact Oracle Support

ORA-27066: number of buffers in vector I/O exceeds maximum

Cause: internal error, number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers

Action: check for trace file and contact Oracle Support

ORA-27067: size of I/O buffer is invalid

Cause: internal error, 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 trace file and contact Oracle Support

ORA-27068: I/O buffer is not aligned properly

Cause: internal error, buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer

Action: check for trace file and contact Oracle Support

ORA-27069: attempt to do I/O beyond the range of the file

Cause: 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 trace file and contact Oracle Support

ORA-27070: 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: 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: File 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: Trying to close a file which has async I/Os pending to be dequeued

Cause: internal error, the file is being closed but not all async I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file

Action: check for trace file and contact Oracle Support

ORA-27074: unable to determine limit for open files

Cause: The getrlimit() system call returned an error.

Action: Check errno.

ORA-27075: SSTMOFRC constant too large

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27076: unable to set limit for open files

Cause: The setrlimit() system call returned an error.

Action: Check errno.

ORA-27077: too many files open

Cause: internal error, the number of files opened through skgfofi has reached the limit