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.
- 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.
- 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
- ORA-24295: max key length (string) for sorted hash cluster exceeded
-
Cause: Sorted hash clusters have a maximum key size
- ORA-24296: error in processing the XML configuration file string
-
Cause: Parameters or their values were specified incorrectly in the configuration file.
- ORA-24300: bad value for mode
-
Cause: An undefined mode value was 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.
- 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.
- 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.
- ORA-24304: datatype not allowed for this call
-
Cause: Data of this datatype cannot be sent or fetched in pieces.
- ORA-24305: bad bind or define context
-
Cause: The call was executed on a cursor for which this is invalid.
- ORA-24306: bad buffer for piece
-
Cause: A zero length buffer or a null buffer pointer was provided.
- ORA-24307: invalid length for piece
-
Cause: The length of the piece exceeded the maximum possible size.
- ORA-24308: illegal define position
-
Cause: Call to modify attributes was done for a non-existent position
- ORA-24309: already connected to a server
-
Cause: This server handle is already attached to a server.
- ORA-24310: length specified for null connect string
-
Cause: The connect string is null, but a length was specified for it.
- ORA-24311: memory initialization failed
-
Cause: Cannot initialize user memory.
- ORA-24312: illegal parameters specified for allocating user memory
-
Cause: An illegal size or null pointer was specified for user memory.
- ORA-24313: user already authenticated
-
Cause: A user has already been authenticated on this service handle.
- ORA-24314: service handle not initialized
-
Cause: The server context does not done exist.
- ORA-24315: illegal attribute type
-
Cause: An illegal attribute type was specified for the handle.
- ORA-24316: illegal handle type
-
Cause: An illegal handle type was specified.
- ORA-24317: define handle used in a different position
-
Cause: A define was done with an existing handle on a different position.
- ORA-24318: call not allowed for scalar data types
-
Cause: This call is valid only for object types.
- ORA-24319: unable to allocate memory
-
Cause: Process was unable to allocate memory to store diagnostics.
- ORA-24320: unable to initialize a mutex
-
Cause: An attempt to initialize a mutex failed.
- ORA-24321: inconsistent parameters passed
-
Cause: One of the three memory function pointers is null or non-null.
- ORA-24322: unable to delete an initialized mutex
-
Cause: An attempt to delete an initialized mutex failed.
- ORA-24323: value not allowed
-
Cause: A null value or a bogus value was passed in for a mandatory parameter.
- ORA-24324: service handle not initialized
-
Cause: An attempt was made to use an improper service context handle.
- ORA-24325: this OCI operation is not currently allowed
-
Cause: An attempt was made to use a context handle outside its scope.
- ORA-24326: handle passed in is already initialized
-
Cause: An attempt was made to pass an initialized handle.
- ORA-24327: need explicit attach before authenticating a user
-
Cause: A server context must be initialized before creating a session.
- ORA-24328: illegal attribute value
-
Cause: The attribute value passed in is illegal.
- ORA-24329: invalid character set identifier
-
Cause: The character set identifier specifed is invalid
- ORA-24330: internal OCI error
-
Cause: An internal OCI error has occurred.
- ORA-24331: user buffer too small
-
Cause: The user buffer to contain the output data is too small.
- ORA-24332: invalid object type
-
Cause: An invalid object type is requested for the describe call.
- ORA-24333: zero iteration count
-
Cause: An iteration count of zero was specified for the statement
- ORA-24334: no descriptor for this position
-
Cause: The application is trying to get a descriptor from a handle for an illegal position.
- ORA-24335: cannot support more than 1000 columns
-
Cause: The number of columns exceeds the maximum number supported.
- 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
- ORA-24337: statement handle not prepared
-
Cause: A statement cannot be executed before making preparing a request.
- ORA-24338: statement handle not executed
-
Cause: A fetch or describe was attempted before executing a statement handle.
- 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.
- ORA-24340: cannot support more than 255 columns
-
Cause: The number of columns exceeds maximum supported by the server.
- ORA-24341: bad mode specified
-
Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
- ORA-24342: unable to destroy a mutex
-
Cause: An attempt to destroy a mutex failed.
- 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.
- ORA-24344: success with compilation error
-
Cause: A sql/plsql compilation error occurred.
- ORA-24345: A Truncation or null fetch error occurred
-
Cause: A truncation or a null fetch error"
- ORA-24346: cannot execute without binding variables
-
Cause: None of the bind variables in the SQL statement are bound.
- ORA-24347: Warning of a NULL column in an aggregate function
-
Cause: A null column was processed by an aggregate function
- ORA-24348: Update or Delete without Where
-
Cause: An update or delete was executed without where clause
- 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.
- ORA-24350: OCI call not allowed
-
Cause: OCI used is not permitted from external procedures.
- ORA-24351: invalid date passed into OCI call
-
Cause: A bad date was passed into one of the OCI calls.
- ORA-24352: invalid COBOL display type passed into OCI call
-
Cause: A bad COBOL display type was passed into one of the OCI calls.
- 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.
- 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.
- 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.
- ORA-24356: internal error while converting from to COBOL display type.
-
Cause: An internal error was encountered during conversion to COBOL display type.
- ORA-24357: internal error while converting from to OCIDate.
-
Cause: An internal error was encountered during conversion to OCIDate type.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-24368: OCI mutex counter non-zero when freeing a handle
-
Cause: This is an internal OCI error.
- 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.
- 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.
- ORA-24371: data would not fit in current prefetch buffer
-
Cause: An internal OCI error has occurred.
- ORA-24372: invalid object for describe
-
Cause: The object to be described is not valid. It either has compilation or authorization errors.
- ORA-24373: invalid length specified for statement
-
Cause: The length specified for the statement is either 0 or too large.
- 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.
- ORA-24375: Cannot use V6 syntax when talking to a V8 server
-
Cause: V6 syntax is no longer supported in V8 server.
- 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.
- ORA-24377: invalid OCI function code
-
Cause: An invalid function code was used.
- 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.
- ORA-24379: invalid user callback type
-
Cause: An invalid type of user callback was specified.
- ORA-24380: invalid mode specification
-
Cause: The mode parameter in an OCI call is invalid
- ORA-24381: error(s) in array DML
-
Cause: One or more rows failed in the DML.
- ORA-24382: statement handled already executed or described
-
Cause: The Statement handle was executed or described successfuly before.
- ORA-24383: Overflow segment of an IOT cannot be described
-
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.
- ORA-24384: Application context size is not initialized
-
Cause: The size of the application context must be initialized before populating each context element.
- 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.
- ORA-24386: statement/server handle is in use when being freed
-
Cause: This is an internal OCI error.
- ORA-24387: Invalid attach driver
-
Cause: Trying to attach using the wrong driver
- ORA-24388: Unsupported functionality in fast path mode
-
Cause: Feature not supported in fast path mode
- ORA-24389: Invalid scrollable fetch parameters
-
Cause: All the requested rows in this fetch could not be received.
- ORA-24390: Unsupported scrollable cursor operation
-
Cause: The scrollable cursor execute or fetch has failed.
- ORA-24391: invalid fetch operation
-
Cause: Scrollable cursor operation requested with non-scrollable cursor.
- 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.
- ORA-24393: invalid mode for creating connection pool
-
Cause: Mode specified in OCIConnectionPoolCreate is invalid.
- ORA-24394: invalid mode for destroying connection pool
-
Cause: Mode specified in OCIConnectionPoolDestroy is invalid.
- ORA-24395: cannot reinitialize non-existent pool
-
Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
- 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.
- ORA-24397: error occured while trying to free connections
-
Cause: An internal error occured while trying to free connections.
- ORA-24398: connection pool already exists
-
Cause: A connection pool has already been created for the specified pool handle.
- 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.
- ORA-24400: error occured while creating connections in the pool
-
Cause: The database link specified in OCIConnectionPoolCreate might be an invalid one.
- 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.
- ORA-24402: error occured while creating connections in the pool
-
Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.
- 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.
- ORA-24404: connection pool does not exist
-
Cause: An attempt was made to use the connection pool before creating it.
- ORA-24405: error occured while trying to create connections in the pool
-
Cause: An internal error occured while creating connections in the pool.
- 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.
- ORA-24407: connection pool already exists
-
Cause: A connection pool has already been created for the specified pool name.
- ORA-24408: could not generate unique server group name
-
Cause: An internal error occured while generating unique server group name.
- ORA-24409: client cannot understand the object
-
Cause: The client cannot process all the new features in the object.
- ORA-24410: scrollable cursor max size exceeded
-
Cause: Result set size exceeded the max limits.
- ORA-24411: Session pool already exists.
-
Cause: A session pool has already been created for the specified pool handle.
- ORA-24412: Cannot reinitialize non-existent pool
-
Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
- ORA-24413: Invalid number of sessions specified
-
Cause: An invalid combination of minimum, maximum and increment number of sessions was specified in the OCISessionPoolCreate call.
- 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."
- ORA-24415: Missing or null username.
-
Cause: Username and password must be specified when pool is created in this mode.
- ORA-24416: Invalid session Poolname was specified.
-
Cause: An attempt was made to use a Session Pool that does not exist.
- ORA-24417: Session pool size has exceeded the maximum limit
-
Cause: The number of sessions has exceeded the maximum size of the Session Pool.
- ORA-24418: Cannot open further sessions.
-
Cause: Sufficient number of sessions are not present in the pool to execute the call. No new sessions can be opened as the sessMax parameter supplied in OCISessionPoolCreate has been reached.
- 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.
- 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.
- 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.
- 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.
- ORA-24423: Cannot set the ROWID attribute - OCI_ATTR_FETCH_ROWID
-
Cause: An attempt was made to set the implicit ROWID attribute.
- ORA-24424: Invalid attempt to define at position 0
-
Cause: An invalid attempt was made to call OCIDefineByPos for position 0.
- ORA-24425: Invalid mode passed when defining at position 0
-
Cause: An invalid mode was passed to OCIDefineByPos.
- ORA-24427: Invalid attributes on user handle
-
Cause: Some of the attributes set on the user handle were not allowed in pooled mode.
- 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.
- 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.
- 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.
- ORA-24431: Statement does not exist in the cache
-
Cause: The statement that was requested for does not exist in the statement cache.
- ORA-24432: The statement that was returned is not tagged.
-
Cause: A tagged statement was requested for, but an untagged statement has been returned.
- 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."
- ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.
-
Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.
- ORA-24435: Invalid Service Context specified.
-
Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.
- ORA-24436: Invalid statement Handle.
-
Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.
- ORA-24437: OCIStmtExecute called before OCIStmtPrepare2.
-
Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.
- ORA-24438: Invalid Authentication Handle specified.
-
Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.
- ORA-24439: success with PLSQL compilation warning
-
Cause: A plsql compilation warning occurred.
- ORA-24440: OCI Easy Install mode cannot be initialized
-
Cause: An internal OCI error has occurred.
- ORA-24441: Invalid cookie, resend sql text
-
Cause: An internal OCI error has occurred.
- 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.
- 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.
- 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.
- 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.
- ORA-24451: string, Maximum call depth exceeded
-
Cause: Your program has too many 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.
- 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.
- ORA-24454: client host name is not set
-
Cause: The network host name in files like /etc/hosts was not set.
- ORA-24460: Native Net Internal Error
-
Cause: Internal error .
- ORA-24480: invalid OCI mode
-
Cause: An attempt was made to invoke OCI API with an invalid mode.
- ORA-24481: Failed to initialize multithreaded environment
-
Cause: Operating system did not support multithreaded mode.
- ORA-24482: Pool size was less than 1 in shared mode
-
Cause: Pool size must be positive in shared mode.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-24489: reserved OCI error
-
Cause: A reserved Oracle Call Interface (OCI) error has occurred.
- ORA-24490: error while getting shard instances
-
Cause: There was a mismatch in the shard keys or group keys with the corresponding connect string.
- ORA-24491: attempt to get sharding-related topology information failed
-
Cause: An unexpected error was encountered while building and processing sharding-related information.
- ORA-24492: Shard library initialization failed.
-
Cause: An attempt to initialize the shard library failed.
- ORA-24493: general sharding error
-
Cause: An unexpected error was encountered while processing sharding-related information.
- ORA-24494: error in constructing shard key or shard group key
-
Cause: An invalid column value was passed.
- 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.
- 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.
- ORA-24497: PL/SQL fix up callback name too long
-
Cause: The PL/SQL fix up callback name was too long.
- ORA-24500: invalid UTF16 mode
-
Cause: UTF16 mode is allowed only at environment handle creation time.
- ORA-24501: invalid UTF16 string passed in
-
Cause: Non-UTF16 string is passed in while UTF16 string is expected
- ORA-24502: codepoint length overflows
-
Cause: Returned buffer has more codepoints than allowed
- ORA-24503: codepoint length overflows for piecewise operation
-
Cause: Accumulated codepoint length exceeds allowed codepoint length
- ORA-24504: data length larger than expected
-
Cause: Incoming data larger than receiving buffer
- ORA-24505: cannot change character set id on the handle
-
Cause: Attempts to change character set id on non-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
- ORA-24507: invalid combination of character set ids
-
Cause: Attempts to set one character set id as zero
- ORA-24508: Buffer is not aligned correctly.
-
Cause: Alignment error ocurred in buffer when converting between character sets.
- 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.
- ORA-24530: User not authorized to access column value.
-
Cause: Column security is enabled and column value is not authorized.
- ORA-24531: Column value authorization is unknown.
-
Cause: Column security is unknown for the column.
- ORA-24536: Warning - column authorization unknown.
-
Cause: Column security is unknown for one or more columns.
- ORA-24542: PRELIM mode logon not allowed to a pluggable database
-
Cause: PRELIM mode logon was attempted to a pluggable database.
- 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.
- 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.
- ORA-24550: unhandled signal #number received. string
-
Cause: Serious error: signal received
- 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.
- ORA-24600: could not create OCI environment
-
Cause: The Oracle Client library used to communicate with the database failed to initialize correctly.
- ORA-24601: bind buffer not allocated by caller
-
Cause: A valid buffer was not provided for the bind call.
- ORA-24602: attempting to read with no fetch
-
Cause: A column was being fetched while not in fetch state.
- ORA-24750: incorrect size of attribute
-
Cause: Transaction ID attribute size is incorrect.
- 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.
- ORA-24753: local transactions cannot be detached
-
Cause: An attempt to detach a local transaction was made.
- 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.
- ORA-24755: OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
-
Cause: These flags are currently not supported.
- ORA-24756: transaction does not exist
-
Cause: An invalid transaction identifier or context was used or the transaction has completed.
- 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.
- 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.
- ORA-24759: invalid transaction start flags
-
Cause: An invalid transaction start flag was passed.
- ORA-24760: invalid isolation level flags
-
Cause: An invalid isolation level flag was passed.
- ORA-24761: transaction rolled back
-
- ORA-24762: server failed due to unspecified error
-
Cause: An internal error has occured in the server commit protocol.
- 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.
- 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.
- ORA-24768: commit protocol error occured in the server
-
- ORA-24769: cannot forget an active transaction
-
Cause: Transaction identifier refers to an active transaction.
- ORA-24770: cannot forget a prepared transaction
-
Cause: Transaction identifier refers to a prepared transaction.
- ORA-24771: cannot detach, prepare or forget a local transaction
-
Cause: Service handle contains a local transaction context.
- 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.
- ORA-24773: invalid transaction type flags
-
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
- ORA-24774: cannot switch to specified transaction
-
Cause: The transaction specified in the call refers to a transaction created by a different user.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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).
- 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
- ORA-24782: Cannot detach from a non-migratable transaction
-
Cause: An attempt was made to detach from a non-migrateable transaction.
- ORA-24783: Cannot switch non-migratable transactions
-
Cause: An attempt was made to prepare/commit a txn different from current.
- ORA-24784: Transaction exists
-
Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction
- ORA-24785: Cannot resume a non-migratable transaction
-
Cause: An attempt was made to resume a non-migrateable transaction.
- ORA-24786: separated transaction has been completed
-
Cause: The current transaction has been completed by another process.
- 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.
- 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.
- ORA-24789: start not allowed in recursive call
-
Cause: Oracle RM will not start/resume a branch in a recursive call
- 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.
- ORA-24791: invalid transaction start flags
-
Cause: An invalid transaction start flag was passed.
- 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
- 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.
- ORA-24795: Illegal string attempt made
-
Cause: An illegal attempt was made to commit/rollback current transaction
- 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.
- ORA-24797: cannot promote the current transaction to a distributed transaction
-
Cause: An illegal attempt was made to promote the current transaction.
- 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.
- ORA-24801: illegal parameter value in OCI lob function
-
Cause: One of the parameter values in the OCI lob function is illegal.
- 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.
- ORA-24803: illegal parameter value in lob read function
-
Cause: Internal error .
- ORA-24804: Lob read/write functions called while another OCI LOB read/write streaming is in progress
-
Cause: Internal error.
- ORA-24805: LOB type mismatch
-
Cause: When copying or appending LOB locators, both source and desctination LOB locators should be of the same type.
- 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.
- ORA-24807: LOB form mismatch
-
Cause: When copying or appending LOBs, both source and desctination LOB locators should have the same character set form.
- 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.
- 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.
- ORA-24810: attempting to write more data than indicated
-
Cause: While writing into a LOB, more data was supplied than indicated.
- ORA-24811: less data provided for writing than indicated
-
Cause: While writing into a LOB, less data was provided than indicated.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- ORA-24819: Illegal reference count encountered for a temporary LOB
-
Cause: Internal error.
- 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.
- ORA-24821: LOB prefetch size supplied is larger than the supported limit.
-
Cause: A very large LOB prefetch size was specified during a query.
- 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.
- 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.
- 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.
- 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.
- ORA-24854: invalid pieceinfo provided
-
Cause: While making the first call to write LOB data, an invalid pieceinfo value provided.
- 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.
- ORA-24900: invalid or unsupported mode parameter passed in call
-
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-24908: invalid recipient presentation attribute
-
Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute.
- ORA-24909: call in progress. Current operation cancelled
-
Cause: The OCI call was invoked when another call on the connection was in progress.
- ORA-24911: Cannot start listener thread at specified port
-
Cause: Thread already running at a different 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.
- ORA-24913: Event to enable NLS validation
-
Cause: N/A
- ORA-24915: Cannot start Listener at specified IP address
-
Cause: Thread was already listening at a different 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.
- ORA-24918: secure notification mode not supported
-
Cause: An attempt was made to use OCI_SECURE_NOTIFICATION before release 12.0 compatible notifications.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-24946: invalid registration callback
-
Cause: An attempt was made to use a reserved callback for notification registration.
- ORA-24947: Invalid namespace attribute specified for the subscription string
-
Cause: An attempt was made to register with invalid namespace attribute.
- ORA-24950: unregister failed, registration not found
-
Cause: The registration that was asked to be unregistered could not be found.
- 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.
- 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
- 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.
- 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.
- ORA-24969: iteration count of number not supported for this statement
-
Cause: This statement was not supported with iteration count greater than one.
- ORA-24981: deferred SGA thread spawn failed
-
Cause: This is an internal error.
- ORA-24982: deferred SGA segment allocation failed, index = string location = string
-
Cause: System-defined shared memory limits are inadequate for Oracle.
- ORA-24983: Process (string) failed to attach to deferred SGA segments.
-
Cause: The process failed to attach to deferred SGA segments.
- ORA-24984: SGA allocation slaves termination failed
-
Cause: This is an internal error.
- ORA-25000: invalid use of bind variable in trigger WHEN clause
-
Cause: A bind variable was used in the when clause of a trigger.
- 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.
- ORA-25002: cannot create INSTEAD OF triggers on tables
-
Cause: Only BEFORE or AFTER triggers can be created on a table.
- 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.
- ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers
-
Cause: WHEN clause is specified in 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25012: PARENT and NEW values cannot be identical
-
Cause: The referencing clause specifies identical values for PARENT and OLD.
- ORA-25013: OLD and PARENT values cannot be identical
-
Cause: The referencing clause specifies identical values for OLD and PARENT.
- ORA-25014: cannot change the value of a PARENT reference variable
-
Cause: Parent values can only be read and not changed.
- 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
- 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.
- 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
- ORA-25018: conflicting trigger string already exists
-
Cause: Conflicting instead of DDL trigger on schema/database already exists.
- ORA-25019: too much concurreny
-
Cause: cannot pin the database/schema because of too much concurrency
- ORA-25020: renaming system triggers is not allowed
-
Cause: renaming system triggers is not allowed
- ORA-25021: cannot reference a trigger defined on another table
-
Cause: Referenced trigger in the FOLLOWS clause was defined on another 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.
- ORA-25023: Cyclic trigger dependency is not allowed
-
Cause: A cycle of trigger dependency can be formed.
- ORA-25024: cannot specify FOLLOWS for a REVERSE CROSSEDITION trigger
-
Cause: The FOLLOWS clause was specified when creating the REVERSE CROSSEDITION trigger.
- ORA-25025: cannot specify PRECEDES clause
-
Cause: The PRECEDES clause was specified when creating a FORWARD CROSSEDITION trigger or a regular trigger.
- ORA-25026: FOR EACH ROW was specified with compound triggers
-
Cause: FOR EACH ROW is not allowed with compound triggers.
- ORA-25027: compound triggers cannot be used as system triggers
-
Cause: Compound trigger was defined as system trigger.
- ORA-25028: regular trigger body can not start with keyword COMPOUND
-
Cause: Regular triggers body should start with BEGIN/DECLARE etc .
- ORA-25029: compound triggers should always start with keyword COMPOUND
-
Cause: Compound trigger body was started with incorrect keyword.
- 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.
- ORA-25031: only a crossedition trigger may be specified
-
Cause: The trigger specified was not 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.
- ORA-25033: triggers cannot be executed at this time
-
Cause: An attempt was made to execute a trigger when the session was almost finished.
- 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.
- 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.
- 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.
- ORA-25101: duplicate REBUILD option specification
-
Cause: The REBUILD option to ALTER INDEX is specified more than 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25107: duplicate TABLESPACE option specification
-
Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.
- 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.
- 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.
- 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.
- ORA-25111: creation of BITMAP cluster indices is not supported
-
Cause: An attempt was made to create a cluster index with the BITMAP attribute.
- ORA-25112: maximum number of BITMAP index columns is 30
-
Cause: Too many columns were specified for the index.
- 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.
- 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.
- ORA-25115: duplicate BLOCK option specification
-
Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.
- 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.
- 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.
- ORA-25118: invalid DUMP DATAFILE/TEMPFILE option
-
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
- ORA-25119: LOGGING/NOLOGGING option already specified
-
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.
- ORA-25120: MINIMUM EXTENT option already specified
-
Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.
- 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.
- 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.
- ORA-25123: Too many components specified in the name.
-
Cause: Specifying more components to a name than allowed.
- ORA-25124: Database link name not allowed.
-
Cause: Specifying a database link name when it is not permitted.
- 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
- 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.
- ORA-25127: RELY not allowed in NOT NULL constraint
-
Cause: An attempt to set RELY on for 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.
- ORA-25129: cannot modify constraint (string) - no such constraint
-
Cause: the named constraint does not exist for this table.
- 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.
- 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.
- 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.
- ORA-25133: duplicate SINGLE TABLE option specified
-
Cause: The SINGLE TABLE option was specified more than once.
- ORA-25134: keyword TABLE expected
-
Cause: The keyword TABLE is missing from the SINGLE TABLE option.
- ORA-25135: cannot use the SINGLE TABLE option
-
Cause: The SINGLE TABLE option is only valid for hash clusters.
- 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.
- ORA-25137: Data value out of range
-
Cause: Value from cast operand is larger than cast target size.
- ORA-25138: string initialization parameter has been made obsolete
-
Cause: An obsolete initialization parameter has been specified
- ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE
-
Cause: An invalid option appears.
- ORA-25140: string space policy cannot be specified for the string extent management
-
Cause: An invalid option appears.
- ORA-25141: invalid EXTENT MANAGEMENT clause
-
Cause: An invalid option appears for EXTENT MANAGEMENT clause
- ORA-25142: default storage clause specified twice
-
Cause: default storage clause was specified twice for create tablespace
- 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
- ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents
-
Cause: An invalid option appears.
- ORA-25145: allocation policy already specified
-
Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM.
- ORA-25146: EXTENT MANAGEMENT option already specified
-
Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once.
- 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.
- 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.
- 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
- 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.
- 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.
- ORA-25152: TEMPFILE cannot be dropped at this time
-
Cause: An attempt was made to drop a TEMPFILE being used by online users
- ORA-25153: Temporary Tablespace is Empty
-
Cause: An attempt was made to use space in a temporary tablespace with no files.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25159: Must specify a valid tablespace number
-
Cause: A valid tablespace number was missing.
- ORA-25160: Must specify a valid relative data block address
-
Cause: A valid relative data block address was missing.
- ORA-25161: Cannot have both DBA and RDBA options
-
Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP REDO.
- ORA-25162: Must specify both RDBA MIN and RDBA MAX options
-
Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO.
- 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.
- ORA-25164: The tag expression is too complex.
-
Cause: The statement tag value was not specified using a simple expression.
- ORA-25165: number of passwords in statement exceeds maximum limit of string
-
Cause: The SQL statement had more passwords than the maximum limit allowed.
- ORA-25175: no PRIMARY KEY constraint found
-
Cause: A PRIMARY KEY constraint must be defined for a table with this organization
- 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
- ORA-25177: UNRECOVERABLE option not permitted
-
Cause: The UNRECOVERABLE option may not be specified for a primary key for a table with this organization
- ORA-25178: duplicate PCTTHRESHOLD storage option specification
-
Cause: The storage option PCTTHRESHOLD is specified more than once.
- ORA-25179: invalid PCTTHRESHOLD storage option value
-
Cause: The specified value must be a positive integer.
- ORA-25180: PCTTHRESHOLD only valid for certain table organizations
-
Cause: PCTTHRESHOLD can only be specified for tables with certain organizations.
- ORA-25181: missing ON keyword for NESTED INDEX
-
Cause: ON keyword required to specify nested index column nest
- 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
- 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"
- 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
- 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
- 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).
- ORA-25187: specified exceptions table form incorrect
-
Cause: The specified table does not have the proper field definitions.
- 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.
- 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
- 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
- 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
- ORA-25193: cannot use COMPRESS option for a single column key
-
Cause: An attempt to use COMPRESS option on single column key
- ORA-25194: invalid COMPRESS prefix length value
-
Cause: The specified value must be a positive integer less than the number of key columns
- 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
- ORA-25196: keyword MOVE in ALTER TABLE MOVE must immediately follow table name
-
Cause: MOVE specified after one/more other ALTER options
- 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
- ORA-25198: partitioning method is not supported for index-organized table
-
Cause: An unsupported partitioning method was specified.
- 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
- ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
-
Cause: A NULL parameter was specified for QUEUE_NAME.
- ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
-
Cause: An invalid value specified for parameter VISIBILITY.
- ORA-25202: invalid value NULL, string should be non-NULL
-
Cause: A NULL value was specified for the parameter.
- ORA-25203: invalid value string, DELAY should be non-negative
-
Cause: A negative value or NULL was specified for DELAY.
- ORA-25204: invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
-
Cause: An invalid SEQUENCE_DEVIATION was specified.
- ORA-25205: the QUEUE string.string does not exist
-
Cause: The specified queue does not exist.
- ORA-25206: enqueue failed, enqueue to exception queue string.string not permitted
-
Cause: An attempt was made to enqueue to an exception queue.
- ORA-25207: enqueue failed, queue string.string is disabled from enqueueing
-
Cause: The queue has been stopped to prevent any further enqueueing.
- 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.
- ORA-25209: invalid value string, EXPIRATION should be non-negative or NEVER
-
Cause: The expiration is less than zero or NULL.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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
- 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
- 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.
- 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.
- ORA-25225: invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
-
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
- ORA-25226: dequeue failed, queue string.string is not enabled for dequeue
-
Cause: The queue has not been enabled for dequeue.
- ORA-25227: Propagation job string doesn't exist
-
Cause: The job doesn't exist in AQ$_SCHEDULES or cache.
- 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.
- ORA-25229: error on transformation of message string string
-
Cause: There was an error when transforming a message at enqueue, dequeue or propagation time.
- ORA-25230: invalid value string, WAIT should be non-negative
-
Cause: A negative value has been specified for WAIT.
- 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.
- ORA-25232: duplicate recipients specified for message
-
Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.
- ORA-25233: invalid parameter specified for NAVIGATION
-
Cause: An invalid parameter has been specified for NAVIGATION.
- 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.
- 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.
- 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.
- ORA-25237: navigation option used out of sequence
-
Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25249: dequeue failed, dequeue not allowed for queue string.string
-
Cause: An attempt was made to dequeue from a non-persistent 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25255: incorrect subscription string string
-
Cause: An incorrect subscription string was specified with OCIRegister.
- 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.
- 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.
- 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.
- ORA-25259: cannot specify protocol for agent
-
Cause: The user specified the protocol attribute for an agent in the agent list.
- ORA-25260: AQ latch cleanup testing event
-
Cause: N/A.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- ORA-25267: didnt specify the signature for a reciever non-repudiable queue
-
Cause: The signature was not specified for a reciever non-repudiable queue
- ORA-25268: didnt dequeue in browse mode with get signature option
-
Cause: The dequeue was not performed in browse mode with get signature option
- ORA-25269: cant specify sognature with get signature option
-
Cause: The signature is not required for the dequeue with get signature option
- 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
- ORA-25271: queue table not found for the given queue
-
Cause: The queue table does not exist for the given queue
- 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.
- ORA-25273: AQ QMN process alternate cleanup event
-
Cause: N/A.
- ORA-25274: AQ Buffered Queue event
-
Cause: N/A.
- ORA-25276: table specified is not a queue table
-
Cause: An invalid queue table name is specified.
- 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.
- ORA-25278: grantee name cannot be NULL
-
Cause: An attempt was made to specify NULL for the grantee parameter.
- ORA-25279: dequeue as select not supported before 8.2
-
Cause: Dequeue as select not supported before 8.2.
- ORA-25280: complete sender information not provided to non-repudiate sender
-
Cause: complete sender information not provided to non-repudiate sender
- ORA-25281: complete reciever information not provided to non-repudiate reciever
-
Cause: complete reciever information not provided to non-repudiate reciever
- ORA-25282: message id. not provided for non-repudiation
-
Cause: message id. was not provided
- ORA-25283: either agent's name or address needed for non-repudiation
-
Cause: neither agent's name nor address provided for non-repudiation"
- ORA-25284: Invalid value string for string
-
Cause: An Invalid value or NULL was specified for the parameter.
- ORA-25285: Invalid value string for array_mode
-
Cause: An Invalid value or NULL was specified for the array_mode.
- 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.
- ORA-25287: Invalid value string, string should be non-negative
-
Cause: An Invalid value or NULL was specified for the parameter.
- 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
- ORA-25289: Buffer Already Exists
-
Cause: Buffer already exists for the specified queue.
- ORA-25290: Cannot complete operation on queue string with existing messages
-
Cause: Queue already has messages. Cannot complete operation
- ORA-25291: Buffer does not exist for the specified queue
-
Cause: Buffer does not exist for the specified queue
- ORA-25292: Buffer operations are not supported on the queue
-
Cause: Buffer operations are not supported on the specified queue type
- ORA-25293: Lob attributes must be null for buffered operations
-
Cause: Enqueue of a buffered message with a non-null lob attribute was attempted
- 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.
- ORA-25295: Subscriber is not allowed to dequeue buffered messages
-
Cause: Subscriber is only allowed to dequeue persistent messages
- ORA-25296: Queue Table string has a buffered queue string
-
Cause: Buffered message was enqueued by specifying delay or sequence deviation.
- 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
- ORA-25299: Invalid message delivery_mode
-
Cause: Invalid value was specified for delivery mode
- ORA-25300: Cannot drop buffer for queue with buffered subscribers
-
Cause: Cannot drop buffer for queue with buffered subscribers
- 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.
- ORA-25302: Operation not possible for non-buffered queue string
-
Cause: Last enqd/ackd message is only supported for buffered queues
- ORA-25303: Buffered operation allowed only on the owner instance
-
Cause: Operation was not performed 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.
- 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.
- ORA-25306: Cannot connect to buffered queue's owner instance
-
Cause: cannot connect to the owner instance of the buffered queue
- ORA-25307: Enqueue rate too high, flow control enabled
-
Cause: Subscribers could not keep pace with the enqueue rate.
- ORA-25310: Subscriber is Notification only; dequeue not supported
-
Cause: Notification only subscribers are not allowed to dequeue.
- ORA-25311: string not supported for non-persistent queue
-
Cause: Specified QOS is not supported for non-persistent queues.
- ORA-25312: Cannot specify nonzero sender protocol
-
Cause: Sender protocol was specified during an enqueue operation.
- 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.
- 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.
- 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.
- 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.
- ORA-25317: Propagation stopped because of instance shutdown
-
Cause: A propagation job has stopped because the instance is shutting down.
- ORA-25318: Propagation stopped because of instance affinity change
-
Cause: A propagation job has stopped because its instance affinity has changed.
- ORA-25319: Queue table repartitioning aborted
-
Cause: During instance restart in an Oracle RAC environment, queue table repartitioning aborted due to errors.
- 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.
- 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.
- ORA-25322: message priority is out of range
-
Cause: The message priority range of 0 to 9 was exceeded.
- 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.
- ORA-25327: Array size is invalid
-
Cause: Array size must be a positive, non-zero integer.
- ORA-25328: string argument size string is smaller than array size
-
Cause: The size of the argument is smaller than the given array size.
- ORA-25329: AQ array operations not allowed on 8.0 queues
-
Cause: An array enqueue/dequeue was attempted on an 8.0 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.
- 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.
- ORA-25332: Invalid release value string for queue table compatible parameter
-
Cause: The release level given for the queue table compatible parameter is invalid
- 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.
- 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.
- ORA-25335: AQ array operations not allowed for buffered messages
-
Cause: An array enqueue/dequeue was attempted for buffered messages
- ORA-25336: Cannot contact instance string during Streams AQ operation
-
Cause: The specified instance was not responding to AQ requests.
- 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.
- 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.
- ORA-25339: STREAMS 'string' must be sync_capture
-
Cause: The specified capture STREAMS did not exist or was not a sync_capture process.
- 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.
- 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.
- 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.
- ORA-25343: Streams error queue cannot be exported
-
Cause: An attempt was made to export a database that has apply errors.
- ORA-25344: statement has bind variables
-
Cause: Current API could not handle a statement with 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.
- 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.
- ORA-25347: Dequeue operation on sharded queue is not possible.
-
Cause: Dequeue of a buffered subscriber or JMS sharded queue failed with OCIAQDeq().
- ORA-25348: This AQ operation can be performed only at instance string of database string.
-
Cause: An Advanced Queuing (AQ) operation was attempted at wrong database instance.
- ORA-25350: maximum number of concurrent transaction branches exceeded
-
Cause: the limit on the number of concurrent transaction branches has been reached
- ORA-25351: transaction is currently in use
-
Cause: The transaction is currently used by a different session.
- ORA-25352: no current transaction
-
Cause: The user session is not attached to any 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.
- 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.
- ORA-25402: transaction must roll back
-
Cause: A failure occured while a transaction was active on this connection.
- ORA-25403: could not reconnect
-
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
- ORA-25405: transaction status unknown
-
Cause: A failure occured while a transaction was attempting to commit. Failover could not automatically determine instance status.
- ORA-25406: could not generate a connect address
-
Cause: Failover was unable to generate an address for a backup instance.
- 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.
- ORA-25409: failover happened during the network operation,cannot continue
-
Cause: The connection was lost when fetching a LOB column.
- ORA-25410: Application requested failover retry
-
Cause: The application failover callback requested failover retry.
- ORA-25411: transaction replay was not successful
-
Cause: Replay was not able to restore the transaction state to match the pre-failover state.
- 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.
- ORA-25413: transaction replay disabled by user request
-
Cause: The application explicitly disabled transaction replay by setting attribute OCI_ATTR_TRANSACTIONAL_TAF=FALSE.
- 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.
- 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.
- ORA-25416: Retry current call
-
Cause: Failover sucessfully recovered an in-flight transaction
- 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.
- 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.
- 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.
- 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.
- ORA-25425: connection lost during rollback
-
Cause: The connection was lost while issuing a rollback and the application failed over.
- 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.
- 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.
- ORA-25428: authentication failure while connecting through database link
-
Cause: An attempt to connect using the database link failed.
- ORA-25429: Break request cannot be propagated over shared database link.
-
Cause: No call in progress over shared database link.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25450: error string during evaluation of rule set string.string
-
Cause: The specified error occurred during evaluation of the rule set.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25457: evaluation function string returns failure
-
Cause: The specified evaluation function returned a failure during evaluation, causing evaluation to terminate.
- ORA-25458: Value not supplied for string string
-
Cause: Variable or table column values were not supplied for 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.
- ORA-25461: rule set not specified
-
Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.
- ORA-25462: evaluation context not specified
-
Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-25472: maximum open iterators exceeded
-
Cause: The open rule hit iterators in the session exceeded 2 * OPEN_CURSORS.
- 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.
- ORA-25476: use pre-5523578 behaviour when looking up enabled roles
-
Cause: N/A
- ORA-25500: database is not open
-
Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.
- ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed
-
Cause: Database resource manager failed to change plan.
- 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.
- 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.
- ORA-25504: the system is already in quiesced state
-
Cause: Cannot quiesce the system because the system is already quiesced.
- ORA-25505: the system is not in quiesced state
-
Cause: Cannot unquiesce the system because the system is not in quiesced state.
- 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.
- ORA-25507: resource manager has not been continuously on
-
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.
- ORA-25508: database is not mounted
-
Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE 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.
- ORA-25510: quiesce not supported for the root container
-
Cause: Could not quiesce the root container.
- ORA-25511: quiesce not supported for pluggable databases
-
Cause: Could not quiesce the pluggable database.
- ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string
-
Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.
- ORA-25527: bad format of _DB_MTTR_SIM_TARGET
-
Cause: One value in _DB_MTTR_SIM_TARGET is empty.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26002: Table string has index defined upon it.\n
-
Cause: Parallel load was specified into a table which has index defined upon it.
- ORA-26003: parallel load not supported for index-organized table string.\n
-
Cause: Parallel load is not supported for index-organized tables.
- 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.
- ORA-26005: Invalid handle for direct path load\n
-
Cause: In direct path load, the handle passed in does not match the type listed.
- 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.
- 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.
- 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.
- ORA-26009: stream verification error: string\n
-
Cause: An error has occurred in a Data Pump stream verification operation.
- 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.
- 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.
- 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.
- 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.
- ORA-26014: unexpected error on string string while retrieving string\nstring
-
Cause: The SQL error was returned from an OCIStmtExecute call.
- 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.
- 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.
- 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.
- ORA-26018: Column string in table string does not exist\n
-
Cause: Column specified in the loader control file does not exist.
- 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.
- ORA-26020: index string.string loaded successfully with string keys
-
Cause: Non-partitioned index information put to loader log file.
- ORA-26021: index string.string partition string loaded successfully with string keys
-
Cause: Partitioned index information put to loader log file.
- 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.
- 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.
- 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.
- ORA-26025: SKIP_INDEX_MAINTENANCE option requested
-
Cause: User requested that index maintenance be skipped on a direct path load.
- 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).
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26034: Column string does not exist in stream\n
-
Cause: Column specified in the column list does not exist in the stream.
- ORA-26035: Error attempting to encrypt or decrypt column
-
Cause: An error occurred while attemping to encrypt or decrypt * a database column.
- 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.
- 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.
- 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.
- 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
- ORA-26041: DATETIME/INTERVAL datatype conversion error\n
-
Cause: The column could not be converted from DATETIME * datatype to internal DATETIME/CHARACTER datatype.
- ORA-26045: REF column string expects string arguments; found string.\n
-
Cause: The number of arguments for the REF column is incorrect.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26053: Row was not loaded due to conversion error.\n
-
Cause: The current row was not loaded due to a conversion error.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26061: Concurrent direct unloads is not allowed.\n
-
Cause: User attempted a direct unload when another is still in progress.
- 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.
- 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.
- ORA-26064: Invalid SCN specified - Wrap: string Base: string.\n
-
Cause: User specified an invalid 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.
- 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)
- 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.
- 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.
- 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.
- 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).
- 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.
- ORA-26083: unsupported direct path stream version string
-
Cause: The stream version requested is not supported by the server.
- 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.
- 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.
- ORA-26086: direct path does not support triggers
-
Cause: A direct path operation is being attempted on a table which * has enabled triggers.
- 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.
- 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.
- 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.
- ORA-26091: requested direct path operation not supported
-
Cause: A direct path operation was requested that 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.
- 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)."
- 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.
- 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.
- 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.
- ORA-26097: unsupported conversion for column string (from type number to type number)
-
Cause: The direct path api does not support the required conversion.
- 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.
- ORA-26099: direct path context is already prepared
-
Cause: OCIDirPathPrepare was called with a context that has already * been prepared.
- 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.
- 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.
- 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.
- ORA-26500: error on caching "string"."string"
-
Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.
- ORA-26501: RepAPI operation failure
-
Cause: An external RepAPI operation failed.
- ORA-26502: error resignal
-
Cause: An internal service failed and signalled an error"
- ORA-26503: internal RepAPI operation failure on object string.string
-
Cause: An unexpected internal RepAPI failure was detected
- ORA-26504: operation not implemented
-
Cause: The caller requested a RepAPI operation that was not implemented
- ORA-26505: unexpected internal null
-
Cause: An internal buffer control structure was NULL
- ORA-26506: null global context
-
Cause: An internal buffer control structure was NULL
- ORA-26507: null master connection
-
Cause: The master connection handle was or became invalid.
- ORA-26508: null materialized view connection
-
Cause: The client connection handle was or became invalid.
- ORA-26509: null materialized view control structure
-
Cause: An internal materialized view control structure could not be obtained.
- ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes
-
Cause: The specified materialized view name was too long.
- ORA-26511: master table 'string.string' not found
-
Cause: A RepAPI operation was attempted against a non-existent or invalid master table
- ORA-26512: error pushing transaction to def$error
-
Cause: An unexpected error occurred while sending an def$error rpc to the master site
- 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.
- ORA-26514: object 'string.string' not found
-
Cause: The specified object was expected but not found.
- ORA-26515: no master log available for 'string.string'
-
Cause: The specified master log was not found or available for the named table.
- ORA-26516: no push transaction acknowledgement
-
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully commited by the master site.
- ORA-26517: materialized view control entry for 'string.string' was not found
-
Cause: The specified materialized view catalog control reocrd was not found.
- 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.
- 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.
- ORA-26520: internal memory failure
-
Cause: An internal memory error was detected.
- ORA-26521: rpc initialization error
-
Cause: An error occurred during the initialization of a PL/SQL rpc.
- ORA-26522: rpc execution error
-
Cause: An error occurred during the execution of a PL/SQL 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.
- 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.
- 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.
- 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.
- ORA-26527: local store callback init phase failed for 'string.string'
-
Cause: The client callback failed during its INIT phase for the named object.
- ORA-26528: local store callback proc phase failed for 'string.string'
-
Cause: The client callback failed during its PROC phase for the named object.
- ORA-26529: local store callback term phase failed for 'string.string'
-
Cause: The client callback failed during its TERM phase for the named object.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26565: Call to type_arg made before calling dbms_defer.call
-
Cause: User invoked type_arg procedure before starting a deferred call
- ORA-26566: Couldn't open connect to string
-
Cause: Failed to open connection using given dblink
- ORA-26571: string.string.string: number of arguments (string) does not match replication catalog
-
Cause: number of arguments does not match replication catalog
- ORA-26572: string.string.string: argument string does not match replication catalog
-
Cause: the (rpc) call is corrupted
- 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.
- ORA-26576: cannot acquire SR enqueue
-
Cause: An attempt to acquire the SR enqueue in exclusive mode failed.
- 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.
- 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.
- 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.
- 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.
- ORA-26652: Capture string did not start properly and is currently in state string
-
Cause: An attempt to restart a capture process failed.
- ORA-26653: Apply string did not start properly and is currently in state string
-
Cause: An attempt to restart an apply process failed.
- 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.
- ORA-26655: Invalid string specified for string procedure
-
Cause: An attempt was made to execute the specified procedure with an invalid SCN value.
- ORA-26656: supplemental logging version error: string
-
Cause: The supplemental logging versions of capture side and apply side are incompatible.
- 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.
- 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.
- ORA-26663: error queue for apply process string must be empty
-
Cause: The error queue for this apply process contains error entries.
- 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.
- ORA-26665: string process string already exists
-
Cause: An attempt was made to create a GoldenGate, XStream or Streams process that already exists.
- ORA-26666: cannot alter string process string
-
Cause: An attempt was made to alter a GoldenGate, XStream or Streams process that is currently running.
- ORA-26667: invalid string parameter string
-
Cause: An attempt was made to specify an invalid parameter.
- 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.
- 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.
- 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.
- 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.
- ORA-26672: timeout occurred while stopping string process string
-
Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams process to shut down.
- ORA-26673: duplicate column name string
-
Cause: An attempt was made to specify a duplicate column name in an LCR.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26680: object type not supported
-
Cause: The specified object type is not supported.
- ORA-26681: command type not supported
-
Cause: The specified command type is not supported.
- ORA-26682: invalid value for publication_on
-
Cause: The publication_on parameter should be either 'Y' or 'N'
- ORA-26683: invalid value for value_type
-
Cause: The value_type parameter should be either 'OLD' or 'NEW'
- ORA-26684: invalid value for value_type
-
Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'
- ORA-26685: cannot apply transactions from multiple sources
-
Cause: Transactions from multiple sources were sent to the same apply process.
- ORA-26686: cannot capture from specified SCN
-
Cause: An attempt was made to specify an invalid 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 ""."".
- ORA-26688: missing key in LCR
-
Cause: Metadata mismatch, or not enough information in the user generated 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.
- 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.
- 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.
- ORA-26692: invalid value string, string should be in string format
-
Cause: The parameter specified was not 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.
- ORA-26694: error while enqueueing into queue string.string
-
Cause: An error occurred while enqueueing a message.
- ORA-26695: error on call to string: return code string
-
Cause: A locking related call failed.
- 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.
- ORA-26697: LCR contains extra column 'string'
-
Cause: The LCR contained more columns than the replicated table.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26710: incompatible version marker encountered during Capture
-
Cause: Capture process cannot mine redo from a version higher than the current software release version.
- 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.
- 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.
- 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.
- ORA-26714: User Error string encountered during apply process
-
Cause: An error was encountered during an apply process.
- ORA-26715: time limit reached
-
Cause: The specified time limit was reached for the GoldenGate, XStream or Streams process.
- ORA-26716: message limit reached
-
Cause: The specified message limit was reached for the Capture process.
- ORA-26717: SCN limit reached
-
Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams process.
- ORA-26718: transaction limit reached
-
Cause: The specified transaction limit was reached for the Apply process.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26727: Cannot alter queue_to_queue property of existing propagation.
-
Cause: The queue_to_queue property was specified for an existing propagation.
- 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.
- ORA-26731: string 'string' does not exist
-
Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist.
- ORA-26732: invalid file group string privilege
-
Cause: The specified privilege number that was specified is invalid.
- 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.
- 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.
- 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.
- ORA-26736: Data Pump error
-
Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation.
- 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.
- ORA-26738: string 'string' is not empty
-
Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects.
- ORA-26740: cannot downgrade because there are file groups
-
Cause: An attempt was made to downgrade a database that has file groups.
- 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.
- ORA-26742: Maximum number of ignored transactions exceeded
-
Cause: An attempt was made to add more than the allowed number 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.
- ORA-26745: cursors (string) are not sufficient
-
Cause: The maximum number of open cursors was too small for GoldenGate, XStream or Streams Apply.
- ORA-26746: DDL rule "string"."string" not allowed for this operation
-
Cause: A DDL rule was specified 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.
- ORA-26748: The one-to-one transformation function string encountered the following error: string
-
Cause: The specified transformation function encountered an error.
- ORA-26752: Unsupported LCR received for "string"."string"
-
Cause: GoldenGate, XStream or Streams capture process received an LCR with unsupported operation from LogMiner.
- ORA-26753: Mismatched columns found in 'string.string'
-
Cause: The columns in the LCR were not the same as the table in the database.
- 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.
- 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
- 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.
- 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.
- ORA-26763: invalid file type "string"
-
Cause: An invalid file type was specified for the ASM file.
- ORA-26764: invalid parameter "string" for local capture "string"
-
Cause: An invalid parameter was specified for the local capture process.
- ORA-26765: invalid parameter "string" for downstream capture "string"
-
Cause: An invalid parameter was specified for the downstream capture process.
- 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.
- 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.
- ORA-26768: Maximum number of unsupported tables exceeded
-
Cause: An attempt was made to add more than the allowed number 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26792: Invalid source database name string
-
Cause: The value for the source database global name was not valid.
- 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
- ORA-26794: Hierarchically enabled tables not supported
-
Cause: Hierarchically enabled tables are not supported.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26802: Queue "string"."string" has messages.
-
Cause: The combined capture and apply optimization could not be used since the queue had messages.
- 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.
- ORA-26804: Apply "string" is disabled.
-
Cause: The apply process was disabled or aborted.
- 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.
- 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.
- 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.
- ORA-26808: Apply process string died unexpectedly.
-
Cause: Apply process died unexpectedly.
- ORA-26809: Capture aborted: checkpoint-free mode requires combined capture and apply mode.
-
Cause: The requirements for combined capture and apply mode were broken.
- 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.
- ORA-26811: Client has already attached to string apply "string".
-
Cause: The client has already attached to the specified apply process.
- 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.
- 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.
- ORA-26814: The value for argument string exceeds maximum string
-
Cause: The value for specified value exceeded the maximum allowed.
- ORA-26815: Error from Apply Network Receiver for Apply "string" and Capture "string".
-
Cause: The Apply Network Receiver aborted due to an unexpected error.
- ORA-26816: string apply process "string" (OS id string) is exiting due to ORA-string.
-
Cause: An apply process encountered an unexpected error.
- ORA-26817: string capture process "string" is unable to communicate with capture server string during initialization.
-
Cause: Capture server might not be started properly
- ORA-26818: string capture process string receives an error from capture server.
-
Cause: Capture server received an error.
- ORA-26819: string capture server for apply "string" and capture "string"encounters disabled or aborted propagation "string".
-
Cause: Propagation was disabled or aborted.
- 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
- ORA-26821: No propagation process found between source queue "string"."string" and destination queue "string"."string".
-
Cause: Propagation has not been configured.
- ORA-26822: Failure in creating capture servers (ksv error code string).
-
Cause: Failure in ksv slave creation.
- ORA-26823: string capture server string is unable to communicate with capture process "string".
-
Cause: Capture process was not started properly or was aborted.
- 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.
- 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.
- ORA-26826: string apply coordinator and apply slave are unable to communicate.
-
Cause: GoldenGate, XStream or Streams Apply process may have died unexpectedly.
- 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.
- 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.
- 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'.
- ORA-26830: Cannot define handler for an XStream outbound server.
-
Cause: An attempt was made to define a handler for an XStream outbound server.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26841: No subscribers are found for queue "string"."string".
-
Cause: No propagation or apply was configured 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- ORA-26848: Split a nonexistent Streams Capture process "string" in job "string"
-
Cause: The job attempted to split a non-existent original Streams Capture.
- 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.
- ORA-26850: Changes to queue subscribers were detected by string capture process.
-
Cause: The subscribers for capture queue might have changed.
- ORA-26851: Unable to connect to apply "string" because it has connected to another capture.
-
Cause: Another capture process is already connected to apply.
- ORA-26852: Invalid NULL value for column_value parameter.
-
Cause: NULL is not allowed to be passed as the column value.
- ORA-26853: invalid cca maximum percentage string
-
Cause: Specified percentage value was not in 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.
- 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.
- 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.
- ORA-26857: LCR position cannot be null (XID=string).
-
Cause: The position of an LCR in the specified transaction was null.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26864: Error occurred in string automatic job: "string"
-
Cause: An error has happened inside GoldenGate, XStream or Streams automatic job.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26885: OCIXStreamInCommit called before OCIXStreamInFlush
-
Cause: An attempt was made to call OCIXStreamInCommit before calling OCIXStreamInFlush.
- 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.
- 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.
- ORA-26888: Redo compatibilty must be 10.2 or greater
-
Cause: XStream Out requires redo comptibility to be 10.2 or greater.
- ORA-26889: LOB assembly not supported for PDML parent transaction string, child transaction string.
-
Cause: LOB assembly is not supported for PDML transactions.
- 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".
- 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.
- ORA-26892: XStream feature not supported
-
Cause: The XStream feature was not supported.
- ORA-26893: Input LCR must be a commit LCR
-
Cause: The input LCR was not a commit LCR.
- ORA-26894: Invalid "string" in Apply Progress redo
-
Cause: The value of the field reported was possibly corrupted.
- 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.
- 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.
- 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.
- 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.
- ORA-26899: internal string error
-
Cause: An internal Streams, XStream or GoldenGate error has occurred.
- 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.
- 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.
- 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.
- ORA-26903: Invalid edition name "string"
-
Cause: The edition associated with the LCR did not exist in 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.
- ORA-26905: Invalid LCR method expression "string" in statement handler.
-
Cause: The Logical Change Record method listed was not allowed in the statement handler.
- ORA-26906: No change handler exists.
-
Cause: There was no change handler for the specified apply, operation, source table, change table, and capture values.
- ORA-26907: Insufficient privileges to set converge tag
-
Cause: Privileges were insufficient to set converge tag.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26916: Must call OCIPOGGRedoLogOpen function before OCIPOGGRedoLogRead
-
Cause: An attempt was made to call OCIPOGGRedoLogRead before calling OCIPOGGRedoLogOpen.
- 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.
- 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.
- 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.
- ORA-26920: string outbound server "string" has been stopped.
-
Cause: The specified outbound server was stopped.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26927: Unable to communicate with string capture process "string" from outbound server "string".
-
Cause: A timeout occurred while waiting for capture to respond.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-26936: must execute OCIPOGGCaptureAttach before invoking string function
-
Cause: An attempt was made to invoke the specified function before executing OCIPOGGCaptureAttach call.
- ORA-26937: client has already attached to string capture "string".
-
Cause: The client was already attached to the specified capture.
- 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.
- ORA-26939: string capture "string" is disabled.
-
Cause: The capture process was disabled or aborted.
- 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.
- 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.
- 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.
- 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.
- ORA-26944: User "string" attempted to invoke a procedure without proper permissions.
-
Cause: An attempt was made to invoke a procedure without proper permissions.
- ORA-26945: unsupported hint string
-
Cause: The specified hint was not supported.
- ORA-26946: OCIPOGGRedoLog API not supported in CDB.
-
Cause: An attempt was made to call an OCIPOGGRedoLog API in a multitenant container database (CDB).
- ORA-26947: Oracle GoldenGate replication is not enabled.
-
Cause: The 'enable_goldengate_replication' parameter was not set to 'true'.
- 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.
- 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).
- 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.
- 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.
- 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.
- ORA-26954: invalid protocol (opcode string) received during XStream execution
-
Cause: An internal protocol error occurred while executing an XStream function.
- 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.
- 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.
- ORA-26957: LCR identifier length is invalid.
-
Cause: A logical change record (LCR) identifier with an incompatible length was used.
- ORA-26958: LCR identifier version is invalid.
-
Cause: An invalid logical change record (LCR) identifier version number was used.
- 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.
- ORA-26960: automatic CDR already configured for table "string"."string"
-
Cause: Automatic conflict detection and resolution was already configured.
- ORA-26961: automatic CDR not configured for table "string"."string"
-
Cause: Automatic conflict detection and resolution was not configured.
- ORA-26962: automatic CDR delta resolution not configured for column "string"
-
Cause: Automatic conflict detection and resolution delta resolution was not configured.
- ORA-26963: automatic CDR column group cannot be created
-
Cause: Automatic conflict detection and resolution was configured with column granularity.
- ORA-26964: column "string" already assigned to a column group
-
Cause: The column was already part of a column group.
- ORA-26965: column group name "string" not available
-
Cause: The column group name was already in use.
- ORA-26967: delete tombstone table "string"."string" cannot be dropped
-
Cause: An attempt was made to drop a delete tombstone table.
- ORA-26968: column group "string" not found
-
Cause: The column group did not exist.
- ORA-26969: column "string" not part of column group "string"
-
Cause: The column did not belong to the column group.
- 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.
- ORA-26971: resolution column "string" not present
-
Cause: The resolution column was not set in the logical change record (LCR).
- 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.
- 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.
- 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.
- ORA-26975: Only one instance of an Oracle GoldenGate downstream live standby permitted.
-
Cause: An attempt was made to create an additional capture session for an Oracle GoldenGate downstream live standby. At most, one instance of this capture type is permitted on a database.
- ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
-
Cause: sbtinit returned an error, additional information indicates error
- ORA-27001: unsupported device type
-
Cause: the specified device type is supported on this platform
- ORA-27002: function called with invalid device structure
-
Cause: internal error, aditional information indicates which function encountered error
- 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
- 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
- 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
- ORA-27006: sbtremove returned error
-
Cause: additional information indicates error returned by sbtremove, and the function that encountered the error
- ORA-27007: failed to open file
-
Cause: sbtopen returned error, additional information indicates error returned from sbtopen, and the function that encountered the error
- ORA-27008: function called with invalid file structure
-
Cause: internal error, aditional information indicates which function encountered error
- ORA-27009: cannot write to file opened for read
-
Cause: internal error
- ORA-27010: skgfwrt: write to file failed
-
Cause: sbtwrite returned error, additional information indicates error returned from sbtwrite
- ORA-27011: skgfrd: cannot read from file opened for write
-
Cause: internal error
- ORA-27012: skgfrd: read from file failed
-
Cause: sbtread returned error, additional information indicates error returned from sbtread
- ORA-27013: skgfqdel: cannot delete an open file
-
Cause: internal error
- ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR
-
Cause: Failure of sltln in skgfqpini
- ORA-27015: skgfcls: failed to close the file
-
Cause: sbtclose returned error, additional information indicates error returned from sbtclose
- ORA-27016: skgfcls: sbtinfo returned error
-
Cause: additional information indicates error returned from sbtinfo
- ORA-27017: skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
-
Cause: media handle string length exceeds 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.
- ORA-27019: tape filename length exceeds limit (SBTOPMXF)
-
Cause: length of tape filename provided to sequential I/O OSD functions is too long
- ORA-27020: named devices not supported
-
Cause: the platform or the specified device type does not support named devices
- ORA-27021: sequential file handle must be specified
-
Cause: The filename which will be passed to sbtopen was not specified.
- 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.
- 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.
- ORA-27024: skgfqsbi: sbtinit2 returned error
-
Cause: sbtinit2 returned an error. This happens during a backup or restore operation.
- 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.
- ORA-27026: skgfrls: sbtend returned error
-
Cause: sbtend returned an error. This happens during a backup or restore operation.
- ORA-27027: sbtremove2 returned error
-
Cause: sbtremove2 returned an error. This happens when deleting a backup file.
- ORA-27028: skgfqcre: sbtbackup returned error
-
Cause: sbtbackup returned an error. This happens when creating a backup file during a backup operation.
- ORA-27029: skgfrtrv: sbtrestore returned error
-
Cause: sbtrestore returned an error. This happens when retrieving a backup file during a restore operation.
- ORA-27030: skgfwrt: sbtwrite2 returned error
-
Cause: sbtwrite2 returned an error. This happens while writing a backup file during a backup operation.
- ORA-27031: mirror resilvering functions not supported
-
Cause: internal error
- ORA-27032: failed to obtain file size limit
-
Cause: getrlimit system call returned an error
- ORA-27033: failed to obtain file size limit
-
Cause: ulimit system call returned an error
- ORA-27034: maximum length of ORACLE_SID exceeded
-
Cause: too many characters in the ORACLE_SID string
- 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
- ORA-27036: translation error, unable to expand file name
-
Cause: additional information indicates sltln/slnrm error, and also indicates which function encountered the error
- ORA-27037: unable to obtain file status
-
Cause: stat system call returned an error, additional information indicates which function encountered the error
- ORA-27038: created file already exists
-
Cause: trying to create a database file, but file by that name already exists
- 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
- ORA-27040: file create error, unable to create file
-
Cause: create system call returned an error, unable to create file
- ORA-27041: unable to open file
-
Cause: open system call returned an error, additional information indicates which function encountered the error
- 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
- ORA-27043: unable to seek to beginning of file
-
Cause: seek system call failed, additional information indicates which function encountered the error
- ORA-27044: unable to write the header block of file
-
Cause: write system call failed, additional information indicates which function encountered the error
- ORA-27045: unable to close the file
-
Cause: close system call failed, additional information indicates which function encountered the error
- 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
- ORA-27047: unable to read the header block of file
-
Cause: read system call failed, additional information indicates which function encountered the error
- ORA-27048: skgfifi: file header information is invalid
-
Cause: possibly trying to use a non-database file as 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
- ORA-27050: function called with invalid FIB/IOV structure
-
Cause: internal error, aditional information indicates which function encountered error
- ORA-27052: unable to flush file data
-
Cause: fsync system call returned error, additional information indicates which function encountered the error
- 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
- 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.
- ORA-27056: could not delete file
-
Cause: unlink system call returned error
- 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
- ORA-27058: file I/O question parameter is invalid
-
Cause: internal error, invalid query is being asked
- ORA-27059: could not reduce file size
-
Cause: ftruncate system call returned error
- ORA-27060: could not set close-on-exec bit on file
-
Cause: fcntl system call returned error
- ORA-27061: waiting for async I/Os failed
-
Cause: aiowait function returned error
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- ORA-27070: async read/write failed
-
Cause: aioread/aiowrite system call returned error, additional information indicates starting block number of I/O
- 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
- ORA-27072: File I/O error
-
Cause: read/write/readv/writev system call returned error, additional information indicates starting block number of I/O
- 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
- ORA-27074: unable to determine limit for open files
-
Cause: The getrlimit() system call returned an error.
- ORA-27075: SSTMOFRC constant too large
-
Cause: internal error
- ORA-27076: unable to set limit for open files
-
Cause: The setrlimit() system call returned an error.
- ORA-27077: too many files open
-
Cause: internal error, the number of files opened through skgfofi has reached the limit
- ORA-27078: unable to determine limit for open files
-
Cause: The getrlimit() system call returned an error.
- ORA-27079: unable to set async IO limit
-
Cause: The setting of the limit for async I/O has failed.
- ORA-27080: too many files open
-
Cause: The number of files opened has reached the system limit.
- ORA-27081: unable to close the file
-
Cause: The close() system call failed.
- ORA-27083: waiting for async I/Os failed
-
Cause: The aio_waitn() library call returned an error.
- ORA-27084: unable to get/set file status flags
-
Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error.
- ORA-27086: unable to lock file - already in use
-
Cause: the file is locked by another process, indicating that it is currently in use by a database instance.
- ORA-27087: unable to get share lock - file not readable
-
Cause: share lock request was made on a file not open for read access.
- ORA-27088: unable to get file status
-
Cause: file not open or file descriptor is invalid.
- ORA-27089: unable to release advisory lock
-
Cause: release of file lock failed
- ORA-27090: Unable to reserve kernel resources for asynchronous disk I/O
-
Cause: The system call to reserve kernel resources for asynchronous I/O has failed.
- ORA-27091: unable to queue I/O
-
Cause: read/write/readv/writev system call returned error, additional information indicates starting block number of I/O
- ORA-27092: size of file exceeds file size limit of the process
-
Cause: an attempt was made to open a file that exceeds the process's file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks)
- ORA-27093: could not delete directory
-
Cause: rmdir system call returned error
- ORA-27094: raw volume used can damage partition table
-
Cause: A raw device with VTOC information was provided as a database file.
- ORA-27095: fail to get the disk sector size
-
Cause: The system call to get the sector size failed. Additional information indicates which function encountered the error.
- ORA-27096: fail to get file size
-
Cause: The system call to get file size failed. Additional information indicates which function encountered the error.
- ORA-27097: failed to set Access Control List ownership for ASM devices
-
Cause: The system call to set ACL ownership for ASM devices failed. Additional information indicates which function encountered the error.
- ORA-27098: failed to rename file
-
Cause: The system call to change the file name failed. Additional information indicates which function encountered the error.
- ORA-27099: failed to create file
-
Cause: The system call to create this file type in this file system failed. Check if the creation of this file type is supported in this file system. Additional information indicates which function encountered the error.
- ORA-27100: shared memory realm already exists
-
Cause: Tried to start duplicate instances, or tried to restart an instance that had not been properly shutdown
- ORA-27101: shared memory realm does not exist
-
Cause: Unable to locate shared memory realm
- ORA-27102: out of memory
-
Cause: Out of memory
- ORA-27103: internal error
-
Cause: internal error
- ORA-27104: system-defined limits for shared memory was misconfigured
-
Cause: System-defined shared memory limits were inadequate for Oracle.
- ORA-27105: unable to support any system page size for shared memory allocation
-
Cause: Current configuration was not supported by any system page size.
- ORA-27106: system pages not available to allocate memory
-
Cause: System page count for supported page sizes was misconfigured.
- ORA-27107: AUTO value for USE_LARGE_PAGES parameter is no longer supported
-
Cause: The USE_LARGE_PAGES configuration parameter was set to AUTO.
- ORA-27120: unable to remove shared memory segment
-
Cause: shmctl() call failed
- ORA-27121: unable to determine size of shared memory segment
-
Cause: shmctl() call failed
- ORA-27122: unable to protect memory
-
Cause: mprotect() call failed
- ORA-27123: unable to attach to shared memory segment
-
Cause: shmat() call failed
- ORA-27124: unable to detach from shared memory segment
-
Cause: shmdt() call failed
- ORA-27125: unable to create shared memory segment
-
Cause: shmget() call failed
- ORA-27126: unable to lock shared memory segment in core
-
Cause: insufficient privileges to lock shared memory segment in core
- ORA-27127: unable to unlock shared memory segment
-
Cause: insufficient privileges to unlock shared memory segment
- ORA-27128: unable to determine pagesize
-
Cause: sysconf() call failed
- ORA-27133: unable to determine stacksize
-
Cause: getrlimit() call failed
- ORA-27134: unable to set stacksize
-
Cause: setrlimit() call failed
- ORA-27135: Operating System hard stack limit is set too low
-
Cause: Operating System hard stack limit was set too low.
- ORA-27136: MPMT and VLM are both enabled
-
Cause: When the _mpmt_enabled parameter is set to TRUE, none of the following parameters should be set to TRUE: * use_indirect_buffers * _db_block_cache_protect * _db_block_cache_clone
- ORA-27137: unable to allocate large pages to create a shared memory segment
-
Cause: Parameter USE_LARGE_PAGES set to only, but large pages were not configured properly
- ORA-27138: unable to allocate large pages with current parameter setting
-
Cause: With parameter USE_LARGE_PAGES set to only, none of the following parameters can be set: * memory_target/memory_max_target * _db_block_cache_protect
- ORA-27139: unable to reserve Oracle VM mapping in process address space
-
Cause: The address space region was already mapped.
- ORA-27140: attach to post/wait facility failed
-
Cause: The program attempted to initialize the post/wait facility, but the facility could not be attached.
- ORA-27141: invalid process ID
-
Cause: process operation attempted using invalid process ID
- ORA-27142: could not create new process
-
Cause: OS system call
- ORA-27143: OS system call failure
-
Cause: OS system call failed
- ORA-27144: attempt to kill process failed
-
Cause: OS system call error
- ORA-27145: insufficient resources for requested number of processes
-
Cause: OS system call error
- ORA-27146: post/wait initialization failed
-
Cause: OS system call failed
- ORA-27147: post/wait reset failed
-
Cause: OS system call failed
- ORA-27148: spawn wait error
-
Cause: OS system call failed
- ORA-27149: assignment out of range
-
Cause: internal error, requested conversion too large for type
- ORA-27150: attempt to notify process of pending oradebug call failed
-
Cause: OS system call
- ORA-27151: buffer not large enough to hold process ID string
-
Cause: internal error
- ORA-27152: attempt to post process failed
-
Cause: OS system call failed
- ORA-27153: wait operation failed
-
Cause: OS system called failed
- ORA-27154: post/wait create failed
-
Cause: internal error, multiple post/wait creates attempted simultaneously
- ORA-27155: could not execute file
-
Cause: OS system call failed
- ORA-27156: request for process information failed
-
Cause: internal error
- ORA-27157: OS post/wait facility removed
-
Cause: the post/wait facility for which the calling process is awaiting action is removed from the system
- ORA-27158: process control failure
-
Cause: Oracle was unable to set the specified process control.
- ORA-27159: failure setting process scheduling priority
-
Cause: Oracle was unable to set the scheduling priority desired.
- ORA-27160: process requested to perform operation
-
Cause: The current process was requested to perform an operation by another process.
- ORA-27161: request for Oracle binary information failed
-
Cause: The program was unable to get information about the Oracle binary.
- ORA-27162: thread creation failed
-
Cause: The program was unable to create a thread.
- ORA-27163: out of memory
-
Cause: The program ran out of memory when allocating a temporary data structure.
- ORA-27164: tried to join detached thread
-
Cause: The program tried to join a detached thread.
- ORA-27165: tried to join thread that does not exist
-
Cause: The program tried to join a thread that does not exist.
- ORA-27166: tried to join current thread
-
Cause: A thread in the program tried to join itself.
- ORA-27168: Translation from hostname to network address failed
-
Cause: Internal error
- ORA-27170: Oracle RAC option of current Oracle binary differs from running instance
-
Cause: The Oracle installation environment may have been modified while the instance was running.
- ORA-27190: skgfrd: sbtread2 returned error
-
Cause: sbtread returned an error. This happens while reading a backup file during a restore operation.
- ORA-27191: sbtinfo2 returned error
-
Cause: sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager's catalog.
- ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
-
Cause: sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.
- ORA-27193: sbtinfo2 did not return volume label
-
Cause: sbtinfo2 did not return the volume label information for the backup file that was just created.
- ORA-27194: skgfdvcmd: sbtcommand returned error
-
Cause: sbtcommand returned an error. This happens when an rman SEND command is issued.
- ORA-27195: proxy copy not supported
-
Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.
- ORA-27196: skgfpbk: sbtpcbackup returned error
-
Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun.
- ORA-27197: skgfprs: sbtpcrestore returned error
-
Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun.
- ORA-27198: skgfpvl: sbtpcvalidate returned error
-
Cause: sbtpcvalidate returned an error. This happens during a proxy backup or restore.
- ORA-27199: skgfpst: sbtpcstatus returned error
-
Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore.
- ORA-27200: skgfpgo: sbtpcstart returned error
-
Cause: sbtpcstart returned an error. This happens during a proxy backup or restore.
- ORA-27201: skgfpcm: sbtpccommit returned error
-
Cause: sbtpccommit returned an error. This happens during a proxy backup or restore.
- ORA-27202: skgfpen: sbtpcend returned error
-
Cause: sbtpcend returned an error. This happens during a proxy backup or restore.
- ORA-27203: skgfpqb: sbtpcquerybackup returned error
-
Cause: sbtpcquerybackup returned an error. This happens during a proxy backup.
- ORA-27204: skgfpqr: sbtpcqueryrestore returned error
-
Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore.
- ORA-27205: skgfpcn: sbtpccancel returned error
-
Cause: sbtpccancel returned an error. This happens during a proxy restore.
- ORA-27206: requested file not found in media management catalog
-
Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.
- ORA-27207: syntax error in device PARMS - parentheses mismatch or missing
-
Cause: User-supplied PARMS value has incorrect syntax.
- ORA-27208: syntax error in device PARMS - environment variable value missing
-
Cause: User-supplied PARMS value has incorrect syntax.
- ORA-27209: syntax error in device PARMS - unknown keyword or missing =
-
Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword.
- ORA-27210: syntax error in device PARMS
-
Cause: User-supplied PARMS value has incorrect syntax.
- ORA-27211: Failed to load Media Management Library
-
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for error code.
- ORA-27212: some entrypoints in Media Management Library are missing
-
Cause: media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit
- ORA-27213: failed to unload Media Management Library
-
Cause: dlclose for media library returned error. See Additional Additional information for error code.
- ORA-27214: skgfrsfe: file search failed
-
Cause: The FindNextFile function returned unxpected error.
- ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file
-
Cause: During an sbtinfo2() call, the media management software returned information about an unknown backup file.
- ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response
-
Cause: The media management software returned a malformed response during an sbtinfo2() call.
- ORA-27217: failed to load Media Management Library from secure location
-
Cause: SBT libraries were not installed in a secure location.
- ORA-27218: failed to read ACFS mirror
-
Cause: An attempt to communicate with the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) kernel driver failed.
- ORA-27219: syntax error in device PARMS - quotes missing or mismatch
-
Cause: The user-supplied PARMS value had incorrect syntax. Either quotes were missing or there was a mismatch in the ENV parameter.
- ORA-27230: OS system call failure
-
Cause: OS system call failed
- ORA-27231: unable to close file
-
Cause: A file could not be closed.
- ORA-27232: unable to get file information
-
Cause: Information about the file could not be obtained.
- ORA-27233: file is not an ELF file
-
Cause: A file was not an ELF file.
- ORA-27234: unable to read file
-
Cause: A file could not be read.
- ORA-27235: unable to map file region into memory
-
Cause: A file region could not be mapped into memory.
- ORA-27236: unable to unmap file from memory
-
Cause: A file region could not be unmapped from memory.
- ORA-27237: ELF file is not a relocatable object file
-
Cause: An ELF file was not the expected type.
- ORA-27238: ELF file is not an executable
-
Cause: An ELF file was not the expected type.
- ORA-27239: ELF file is not a shared object file
-
Cause: An ELF file was not the expected type.
- ORA-27240: ELF file does not have a required section
-
Cause: An ELF file did not have a required section.
- ORA-27241: ELF-shared library has multiple sections of the same type
-
Cause: An ELF-shared library had multiple sections of the same type.
- ORA-27242: ELF file has invalid hash table entry size
-
Cause: An ELF file had an invalid hash table entry size.
- ORA-27243: ELF file has too many relocation sections
-
Cause: An ELF file had too many relocation sections.
- ORA-27244: unable to determine base value for data relocation from ELF file
-
Cause: An ELF file was missing important information.
- ORA-27245: unable to dlopen() binary image
-
Cause: A file could not be accessed via dlopen().
- ORA-27246: unable to open file
-
Cause: A file could not be opened.
- ORA-27250: OS system call failure
-
Cause: OS system call failed
- ORA-27270: szingroup: malloc failed
-
Cause: The malloc library call failed to allocate space for a group list.
- ORA-27271: szingroup: group lookup failure
-
Cause: The 'getgrnam_r' library call failed to determine the members of a UNIX group.
- ORA-27300: OS system dependent operation:string failed with status: string
-
Cause: OS system call error
- ORA-27301: OS failure message: string
-
Cause: OS system call error
- ORA-27302: failure occurred at: string
-
Cause: OS system call error
- ORA-27303: additional information: string
-
Cause: OS system call error
- ORA-27351: conflicting values of job attributes string and string
-
Cause: The values of two attributes passed in to the CREATE_JOBS call or the JOB object constructor conflicted with each other. This is usually because both attributes cannot be non-NULL at the same time.
- ORA-27353: job attribute string is missing
-
Cause: An attribute needed to fully specify a job was not passed in to a call to CREATE_JOBS or the JOB object constructor.
- ORA-27354: attribute string cannot be set for string jobs
-
Cause: The CREATE_JOBS call or the JOB object constructor was called with an argument that is illegal in the case of lightweight or in-memory jobs.
- ORA-27356: invalid job argument
-
Cause: An invalid job argument was passed into either the CREATE_JOBS call or the JOB object constructor.
- ORA-27357: duplicate reference to job object string
-
Cause: The scheduler CREATE_JOBS call had two or more references to the same job.
- ORA-27359: duplicate reference to attribute string of job string
-
Cause: The scheduler SET_JOB_ATTRIBUTES call had two or more references to a specific atrribute of a job.
- ORA-27361: scheduler API invoked with illegal or inconsistent arguments
-
Cause: A DBMS_SCHEDULER API call was invoked with either illegal or inconsistent arguments.
- ORA-27362: batch API call completed with errors
-
Cause: Some of the commands submitted to a scheduler batch API call could not be successfully carried out because of errors. Other commands in the batch may have completed successfully.
- ORA-27363: invalid program for string job
-
Cause: An attempt was made to create a lightweight or in-memory job using an invalid program. A program used in a lightweight or in-memory job has to be enabled, has to be in the same schema as the job, and the program action has to be either a PL/SQL block or a stored procedure.
- ORA-27364: remote database "string" already registered as string
-
Cause: The user attempted to register a remote database that was already registered.
- ORA-27365: job has been notified to stop, but failed to do so immediately
-
Cause: The job specified in the stop_job command cannot be stopped immediately(because it is rolling back or blocked on a network operation), but it has been notified to stop. This means it will be stopped as soon as possible after its current uninterruptable operation is done.
- ORA-27366: job "string"."string" is not running
-
Cause: An attempt was made to stop a job that was not running.
- ORA-27367: program "string"."string" associated with this job is disabled
-
Cause: An attempt was made to run a job whose program has been disabled.
- ORA-27369: job of type EXECUTABLE failed with exit code: string
-
Cause: A problem was encountered while running a job of type EXECUTABLE. The cause of the actual problem is identified by the exit code.
- ORA-27370: job slave failed to launch a job of type EXECUTABLE
-
Cause: The scheduler ran into an error when the job slave tried to start a job of type EXECUTABLE. The rest of the error stack will provide more detailed information on what the exact problem was.
- ORA-27371: jobs of type EXECUTABLE are not supported on this platform
-
Cause: The user tried to create a job or program of type EXECUTABLE on a platform where such jobs are not supported.
- ORA-27372: length of action and arguments exceeds platform limit string
-
Cause: The total length of the job or program action and the arguments exceeds the platform limit specified.
- ORA-27373: unknown or illegal event source queue
-
Cause: The source queue specified for the event based job or event based schedule was either not found or was of the wrong type.
- ORA-27374: insufficient privileges on event source queue
-
Cause: The job owner had insufficient privileges on the event source queue that was specified for the job.
- ORA-27375: valid agent name must be specified for secure queues
-
Cause: The queue specified for the event based job or schedule was a secure queue and either no agent name was specified or an invalid agent name was specified.
- ORA-27376: event condition cannot be NULL
-
Cause: A null event condition was passed in for an event based job or schedule. This is not allowed.
- ORA-27377: windows cannot have event based schedules
-
Cause: Event based schedules for windows are currently not supported.
- ORA-27378: cannot stop jobs of type EXECUTABLE on this platform
-
Cause: An attempt was made to stop a job of type EXECUTABLE on a platform where the stop operation was not supported.
- ORA-27379: INSTANCE_ID attribute conflicts with job class settings
-
Cause: The value of the INSTANCE_ID attribute of the job conflicted with the value of the SERVICE attribute of its job class.
- ORA-27380: not enough units to satisfy the constraint
-
Cause: There were not enough resources to satisfy the constraint.
- ORA-27381: job cannot run, state is RESOURCE_UNAVAILABLE
-
Cause: The job could not run because one of the resources was in a BLOCKED_ALL_JOBS state.
- ORA-27382: job type string has errors in the job action
-
Cause: There were errors in the job action when the FAIL_ON_SCRIPT_ERROR job attribute was set to TRUE.
- ORA-27399: job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege
-
Cause: The owner of a job of type EXECUTABLE does not have the CREATE EXTERNAL JOB system privilege.
- ORA-27400: In a PDB, the JOB_QUEUE_PROCESSES initialization parameter can only be set to 1000 or 0.
-
Cause: A value other than 1000 or 0 was specified for the JOB_QUEUE_PROCESSES initialization parameter. Inside a pluggable database (PDB), the JOB_QUEUE_PROCESSES initialization parameter can only accept the values of 1000 or 0 to indicate whether or not jobs should run in the PDB.
- ORA-27411: empty string is not a valid repeat interval.
-
Cause: An empty string '' was provided as a repeat interval for a window or a schedule.
- ORA-27412: repeat interval or calendar contains invalid identifier: string
-
Cause: The calendar string or calendar definition for the repeat interval of a job, schedule or window contained an unsupported keyword or reference to an undefined calendar.
- ORA-27413: repeat interval is too long
-
Cause: The repeat interval consisted of a calendar string larger than the maximum size allowed.
- ORA-27414: Invalid string clause value
-
Cause: The BY clause value was not recognized or was out-of-range for the frequency specified.
- ORA-27415: repeat interval or calendar must start with a frequency clause
-
Cause: The specified calendar string for the repeat interval did not start with a frequency clause.
- ORA-27416: BYDAY clause in repeat interval or calendar contains an invalid weekday
-
Cause: The BYDAY clause of the repeat interval contained a value that did not represent a weekday.
- ORA-27417: BYWEEKNO clause requires YEARLY clause
-
Cause: A repeat interval or calendar contained a BYWEEKNO clause with a frequency other than yearly.
- ORA-27418: syntax error in repeat interval or calendar
-
Cause: The repeat interval or calendar definition was not recognized as valid syntax.
- ORA-27419: unable to determine valid execution date from repeat interval
-
Cause: The specified repeat interval contained conflicting clauses that made it impossible to ever find a matching date, e.g., 'FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31'. Alternatively, the scheduler reached its maximum number of attempts to try to find a valid execution date. This occurs when theoretically there is a valid execution date far in the future, but the scheduler took too many attempts to determine this date.
- ORA-27420: Following message from string interval interpreter
-
Cause: The repeat interval or calendar definition was not recognized as valid syntax.
- ORA-27421: calendar expression restriction string encountered
-
Cause: The calendar expression was not valid because a limit test failed. For example, the maximum value of the interval that can be specified in the INTERVAL clause is limited to a value derived from the frequency clause.
- ORA-27422: usage of string not supported in embedded calendar application "string"."string"
-
Cause: The main calendar definition used an embedded calendar in an INCLUDE, EXCLUDE, INTERSECT, or FREQ clause for which extra limitations apply.
- ORA-27423: calendar clause string specified more than once
-
Cause: The calendar definition contained a clause that was specified twice or more times.
- ORA-27424: calendar clauses string and string are incompatible
-
Cause: The calendar definition contained clauses that were incompatible.
- ORA-27425: instance_id cannot be specified if database is not in Oracle RAC mode
-
Cause: 'stop_job' was called with 'instance_id' outside Oracle RAC mode.
- ORA-27431: chain "string"."string" has a user-managed rule set
-
Cause: An attempt was made to modify a rule set that is not managed by the Scheduler.
- ORA-27432: step "string" does not exist for chain "string"."string"
-
Cause: The step specified does not exist for the given chain.
- ORA-27433: cannot alter state of step "string" for job "string"."string" to string
-
Cause: The step cannot be changed to the requested state. The state of a running step cannot be changed. A step which is running or has already run cannot be run again.
- ORA-27434: cannot alter chain step job "string"."string"."string"
-
Cause: A step job of a running chain cannot be altered, only stopped or dropped.
- ORA-27435: chain job terminated abnormally
-
Cause: A chain job has ended abnormally. The error code for the running chain could not be retrieved.
- ORA-27436: Scheduler agent operation failed with message: string
-
Cause: The Scheduler agent encountered an unexpected error when trying to perform the specified action.
- ORA-27451: string cannot be NULL
-
Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL.
- ORA-27452: "string" is an invalid name for a database object.
-
Cause: An invalid name was used to identify a database object.
- ORA-27453: "string" is an invalid job or program argument name.
-
Cause: An invalid job or program argument name was specified.
- ORA-27454: argument name and position cannot be NULL
-
Cause: The name or position of a program or job argument was defined as NULL.
- ORA-27455: Only "SYS" is a valid schema for a string.
-
Cause: A non-SYS schema was specified for an object that must be in the SYS schema.
- ORA-27456: not all arguments of program "string"."string" have been defined
-
Cause: The number_of_arguments attribute of the named program did not match the actual number of arguments that have been defined.
- ORA-27457: argument string of job "string"."string" has no value
-
Cause: No value was provided for the job argument with the specified position.
- ORA-27458: A program of type PLSQL_BLOCK cannot have any arguments.
-
Cause: An attempt was made to create or enable a program of type PLSQL_BLOCK with arguments. This is not allowed.
- ORA-27459: A program of type EXECUTABLE must have character-only arguments.
-
Cause: A program of type EXECUTABLE was created or enabled with one or more arguments of non-character datatypes.
- ORA-27460: cannot execute disabled job "string"."string"
-
Cause: An attempt was made to run a job that is disabled.
- ORA-27461: The value for attribute string is too large.
-
Cause: The value that was provided for the specified attribute was too large.
- ORA-27463: invalid program type string
-
Cause: An invalid program type was specified.
- ORA-27464: invalid schedule type string
-
Cause: An invalid schedule type was specified.
- ORA-27465: invalid value string for attribute string
-
Cause: An invalid value was provided for the specified attribute.
- ORA-27467: invalid datatype for string value
-
Cause: The value provided for the named scheduler attribute was of an invalid datatype.
- ORA-27468: "string"."string" is locked by another process
-
Cause: An attempt was made to read or modify the state of the named scheduler object when another process was also updating the same object and held the lock.
- ORA-27469: string is not a valid string attribute
-
Cause: A non-existant attribute was specified.
- ORA-27470: failed to re-enable "string"."string" after making requested change
-
Cause: A change was made to an enabled scheduler object that caused it to become disabled.
- ORA-27471: window "string"."string" is already closed
-
Cause: An attempt was made to close a window that was not open.
- ORA-27472: invalid metadata attribute string
-
Cause: An invalid metadata attribute was specified.
- ORA-27473: argument string does not exist
-
Cause: An argument which was specified does not exist.
- ORA-27474: cannot give both an argument name and an argument position
-
Cause: An argument was specified using both a name and a position.
- ORA-27475: unknown string "string"."string"
-
Cause: The specified object did not exist, privileges were not granted, or the object was of the wrong type.
- ORA-27476: "string"."string" does not exist
-
Cause: A database object was specified that does not exist.
- ORA-27477: "string"."string" already exists
-
Cause: An attempt was made to create an object with a name that has already been used by another object in the same schema.
- ORA-27478: job "string"."string" is running
-
Cause: An attempt was made to drop a job that is currently running.
- ORA-27479: Cannot string "string"."string" because other objects depend on it
-
Cause: An attempt was made to drop or disable a scheduler object that has jobs associated with it without specifying the force option.
- ORA-27480: window "string" is currently open
-
Cause: An attempt was made to drop a window that is currently open, or to manually open a window while another window is already open.
- ORA-27481: "string"."string" has an invalid schedule
-
Cause: An attempt was made to enable a job or window that has an invalid schedule.
- ORA-27482: The scheduler credential "string"."string" is unusable.
-
Cause: An attempt was made to use a scheduler credential for which the key to decrypt its password was lost. Therefore, the password of the credential could not be retrieved.
- ORA-27483: "string"."string" has an invalid END_DATE
-
Cause: An attempt was made to enable a job or window that has an invalid end_date. Either the end_date is before the start_date or the end_date is in the past.
- ORA-27484: Argument names are not supported for jobs without a program.
-
Cause: An attempt was made to set or reset a job argument by using the name of the argument. Identifying job arguments by their name is only supported in combination with jobs that are based on programs. Jobs that are not using a program cannot have named arguments.
- ORA-27485: argument "string" already exists at a different position
-
Cause: An attempt was made to create or replace an argument with a name that is already used by an argument at a different position.
- ORA-27486: insufficient privileges
-
Cause: An attempt was made to perform a scheduler operation without the required privileges.
- ORA-27487: invalid object privilege for a string
-
Cause: The granted object privilege is not valid for the specified scheduler object.
- ORA-27488: unable to set string because string was/were already set
-
Cause: An attempt was made to set an object's attribute even though one or more conflicting attributes of the same object had already been set.
- ORA-27489: unable to process job "string"."string" from job class "string"
-
Cause: An error was encountered while processing the named job from the specified job class.
- ORA-27490: cannot open disabled window "string"."string"
-
Cause: The user tried to open a disabled window.
- ORA-27491: repeat_interval and start_date cannot both be NULL
-
Cause: An attempt was made to set both repeat_interval and start_date to equal NULL for a Scheduler window or schedule.
- ORA-27492: unable to run job "string"."string": scheduler unavailable
-
Cause: A job run with current session set to false can not be issued if the scheduler is not active. Check value of job_queue_processes parameter, issue dbms_ijob.set_enabled(true), database is in upgrade/migrade mode, database is in data guard mode, or scheduler attribute SCHEDULER_DISABLED is set to TRUE
- ORA-27493: In-memory job "string.string" cannot be modified
-
Cause: Once enabled, the full in-memory job could not be further modified.
- ORA-27494: operation not permitted on lightweight and in-memory jobs
-
Cause: An attempt was made to perform an action that was not permitted.
- ORA-27495: attribute string cannot be set for in-memory jobs
-
Cause: An attempt was made in a CREATE or SET_ATTRIBUTE call to set an attribute that could not be set for run-time in-memory jobs.
- ORA-27496: credential "string"."string" is disabled
-
Cause: An attempt was made to run a job, file watcher or external procedure whose credential was disabled.
- ORA-27497: operation is not permitted inside a pluggable database
-
Cause: This operation was not permitted in a pluggable database.
- ORA-27498: resource constraint object type mismatch
-
Cause: Not all of the resource constraints of a resource were of the same type.
- ORA-27499: in-memory job metadata is too large
-
Cause: The in-memory job was too large. Due to the need to keep in-memory jobs efficient and performing well,we limit the size of in-memory job metadata to 8 kilobytes. This includes the space used for job argument values.
- ORA-27500: inter-instance IPC error
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27501: IPC error creating a port
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27502: IPC error deleting OSD context
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27503: IPC error attempting to cancel request
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27504: IPC error creating OSD context
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27505: IPC error destroying a port
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27506: IPC error connecting to a port
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27507: IPC error disconnecting from a port
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27508: IPC error sending a message
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27509: IPC error receiving a message
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27510: IPC error waiting for a request to complete
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27512: IPC error posting a process
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27513: parameter string contains invalid value string
-
Cause: The program could not identify the value as an IP address.
- ORA-27514: IPC error copying memory to remote process
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27515: inadequate memlock limit or driver settings
-
Cause: Inter Process Communication(IPC) queue creation failed due to inadequate memlock limit or driver settings.
- ORA-27528: Transport: string required by string is not available
-
Cause: The IP addresses assigned to the instance did not support the specified transport.
- ORA-27529: IPC IP address string is not available.
-
Cause: The IP address assigned to the instance was not associated with any network adapters.
- ORA-27530: IPC Ephemeral ports on IP address string are exhausted.
-
- ORA-27532: IPC global name service error
-
- ORA-27542: Failed to unprepare a buffer prepared for remote update
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27543: Failed to cancel outstanding IPC request
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27544: Failed to map memory region for export
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27545: Fail to prepare buffer for remote update
-
Cause: This is an operating system/cluster interconnect error.
- ORA-27546: Oracle compiled against IPC interface version string.string found version string.string
-
Cause: A misconfiguration or installation error occurred.
- ORA-27547: Unable to query IPC OSD attribute string
-
Cause: This is an operating system-dependent IPC error.
- ORA-27548: Unable to unprepare IPC buffer
-
Cause: This is an operating system-dependent IPC error.
- ORA-27550: Target ID protocol check failed. tid vers=string, type=string, remote instance number=string, local instance number=string
-
Cause: The local Oracle Real Application Cluster instance and remote instance are running with incompatible implementation of the inter-instance IPC protocol library. A misconfiguration or installation error occurred.
- ORA-27552: exception accessing Global Shared Memory (GSM) in Oracle RAC cluster
-
Cause: GSM is used to provide shared memory semantics on an Oracle RAC cluster. An error has occurred accessing shared memory hosted on a remote node. This is an internal programming error.
- ORA-27553: incompatible IPC settings in Oracle RAC cluster
-
Cause: Inter-process Communication (IPC) settings were not compatible with other instances in the Oracle RAC cluster.
- ORA-27601: Cell storage initialization failed, cell library error code [string]
-
Cause: Cell storage client did not succeed in initializing.
- ORA-27602: Failure to publish network status information, cell library error code [string]
-
Cause: Network status information publishing failed.
- ORA-27603: Cell storage I/O error, I/O failed on disk string at offset string for data length string
-
Cause: Cell storage I/O read or write failed, possibly due to a configuration problem or a hardware failure.
- ORA-27604: Cell storage ioctl error, ioctl failed on disk string
-
Cause: Ioctl operation on a cell storage disk failed.
- ORA-27605: Smart I/O failed as a handle could not be obtained to the cell "string" as the cell is not accessible.
-
Cause: The cell could have been unavailable.
- ORA-27606: Smart I/O failed because the diskgroup was found to be unmounted. tablespace number: "string", file number: "string"
-
Cause: The diskgroup to which the specified file belongs was found to be unmounted.
- ORA-27607: Smart I/O failed because there were no online disks. tablespace number: "string", file number: "string"
-
Cause: There were no online disks found for the specified file.
- ORA-27608: Smart I/O failed because the disk "string" on the cell "string" was not open. error code: "string", "string"
-
Cause: The specified disk on the specified cell could not be opened.
- ORA-27609: Smart I/O failed due to a network error to the cell "string". error code "string", "string"
-
Cause: The specified cell could not be connected to.
- ORA-27610: Smart I/O failed due to shortage of memory on the cell "string"
-
Cause: The specified cell had a shortage of memory to perform smart I/O.
- ORA-27611: Smart I/O failed due to a block corruption detected on the host. The block was received from cell "string". disk: "string", block: "string", disk offset: "string"
-
Cause: The data block indicated was corrupted on the host, but a corruption was not found on the cell.
- ORA-27612: Smart I/O failed due to a block corruption detected on the cell "string". disk: "string", block: "string", disk offset: "string"
-
Cause: The data block indicated was found to be corrupted on the cell.
- ORA-27613: Smart I/O failed due to an I/O error on the cell "string". disk: "string", block: "string", disk offset: "string" I/O size: "string"
-
Cause: An I/O request failed on the specified cell and disk.
- ORA-27614: Smart I/O failed due to an error "string, string" from the cell "string". disk: "string", block: "string", disk offset: "string" I/O size: "string"
-
Cause: An I/O request failed, due to an internal error on the specified cell and disk.
- ORA-27615: Smart I/O file to ASM disk translation failed with error: string.
-
Cause: An internal error caused a smart I/O operation to fail.
- ORA-27616: ASM Allocation Unit: string
-
Cause: This error message is usually accompanied by another message, indicating the real problem. This message exists to provide additional information to Oracle Support Services.
- ORA-27617: Smart I/O failed because of an internal error. Cell "string", disk "string", cell library error code "string, string", error information "string"
-
Cause: An internal error caused a smart I/O operation to fail.
- ORA-27618: Smart I/O failed because of an internal error. Cell "string", cell library error code "string, string", error information "string"
-
Cause: An internal error caused a smart I/O operation to fail.
- ORA-27619: Smart I/O failed because of an internal error when determining the time zone file version. Error code "string"
-
Cause: An internal error caused a smart I/O operation to fail.
- ORA-27621: The value of string is not valid for parameter string
-
Cause: Incorrect value is specified for an internal parameter.
- ORA-27623: Cell automation SQL action failed
-
Cause: Cell automation manager or worker process failed to execute SQL action through OCI recursive call.
- ORA-27624: Smart I/O failed because the number of reconnects to the cell "string" exceeded the maximum allowed "string".
-
Cause: The number of reconnects to a cell exceeded the maximum allowed. This problem indicates a possible network problem or a software problem on the cell.
- ORA-27625: Exadata configuration failed.
-
Cause: One or both of the files, cellinit.ora and cellip.ora, were either invalid or missing.
- ORA-27626: Exadata error: string (string)
-
Cause: The cause of this error is dependent on the context in which this error is reported.
- ORA-27627: Software edition incompatible with Exadata storage.
-
Cause: Oracle Exadata can be used only with Oracle Database Enterprise Edition.
- ORA-27628: An invalid value was specified for the parameter string.
-
Cause: An invalid value was specified for a parameter.
- ORA-27629: External table smart I/O failed because the cell is not accessible.
-
Cause: The cell was unavailable.
- ORA-27631: External encryption or decryption is disabled.
-
Cause: Either decryption was disabled in the cellinit.ora initialization parameter file, or the cryptography mode requested by the database was incompatible with what was available on the cell.
- ORA-27778: MGA namespace is already marked for deletion.
-
Cause: Managed Global Area (MGA) namespace was already marked for deletion. No further attaches are allowed.
- ORA-27779: MGA segment creation failure
-
Cause: The Managed Global Area (MGA) segment creation failed.
- ORA-27800: invalid configuration (string) for event creation (string).
-
Cause: Invalid configuration values were given while creating the event.
- ORA-27801: event notification handle not valid
-
Cause: The event notification handle was not valid.
- ORA-28000: The account is locked.
-
Cause: The wrong password was entered multiple consecutive times as specified by the profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA locked the account, or the user is a common user locked in the root container.
- ORA-28001: the password has expired
-
Cause: The user's account has expired and the password needs to be changed.
- ORA-28002: the password will expire within string days
-
Cause: The password of the user's account has expired. Since the user's account is associated with a password profile with a limited password grace period and grace period is yet to elapse, the user will not be prompted to input a new password and ORA-28002 warning message will continue to be displayed upon each successful login to the user account, until the user changes their password. Once the grace period elapses, the password will expire and user login will start failing with ORA-28001 error, until the user changes their password.
- ORA-28003: password verification for the specified password failed
-
Cause: The new password did not meet the necessary complexity specifications and the password_verify_function failed
- ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
-
Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument
- ORA-28005: invalid logon flags
-
Cause: The flags are not properly set or conflicting flags are set in making calls
- ORA-28006: conflicting values for parameters string and string
-
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set
- ORA-28007: the password cannot be reused
-
Cause: The password cannot be reused for the specified number of days or for the specified nunmber of password changes
- ORA-28008: invalid old password
-
Cause: old password supplied is wrong; Hence user cannot be authenticated using old password
- ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
-
Cause: connect SYS/password is no longer a valid syntax
- ORA-28010: cannot expire external users, global users, or users with no authentication method
-
Cause: If a user account is created as IDENTIFIED EXTERNALLY, IDENTIFIED GLOBALLY, NO AUTHENTICATION, this account cannot be expired.
- ORA-28011: the password has expired; change your password now
-
Cause: The password of the user's account has expired. Since the user's account is associated with a password profile with an UNLIMITED password grace period, the user will not be prompted to input a new password (as normally happens for accounts with a limited grace period). Instead, ORA-28011 warning message will continue to be displayed upon each successful login to the user account, until the user changes their password.
- ORA-28012: connection as string should use AS string
-
Cause: An attempt was made to connect as an administrative user without using AS SYSBACKUP, AS SYSDG, or AS SYSKM.
- ORA-28013: the password has expired
-
Cause: The password of the proxy user expired.
- ORA-28014: cannot drop administrative users
-
Cause: An attempt was made to drop administrative users. Administrative users can be dropped only by SYS during migration mode.
- ORA-28015: account unlock attempted on read-only database but a conflicting account lockout on the primary exists
-
Cause: An attempt to unlock an account on a read-only database was prevented, because the account was previously marked as locked on the primary database. All attempts to unlock the account on the read-only database will be prevented as long as the overriding "account locked" condition exists at the primary database.
- ORA-28016: Privilege string cannot be granted to SYS.
-
Cause: An attempt was made to grant SYSBACKUP, SYSDG or SYSKM to the SYS user. These administrative privileges cannot be granted to SYS.
- ORA-28017: The password file is in the legacy format.
-
Cause: An attempt was made to perform one of the following operations, but none of these operations are allowed while the password file is in LEGACY format. - Attempting to grant SYSBACKUP, SYSDG or SYSKM privileges. - Attempting to grant an administrative privilege to a user who has large password verifiers, for example, SHA-512 hashed verifiers. - Attempting to grant a common administrative privilege to a common user in a multitenant container database (CDB).
- ORA-28018: This operation requires connection as SYS or SYSBACKUP.
-
Cause: An attempt was made to execute a command even though the user was not connected as SYS or SYSBACKUP.
- ORA-28019: audit cannot be configured on administrative privileges
-
Cause: An attempt was made to configure audit on an administrative privilege using either the AUDIT, NOAUDIT, CREATE AUDIT POLICY, or ALTER AUDIT POLICY command.
- ORA-28020: IDENTIFIED GLOBALLY already specified
-
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
- ORA-28021: cannot grant global roles
-
Cause: The role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.
- ORA-28022: cannot grant external roles to global user or role
-
Cause: The role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users, to global roles or to any other roles.
- ORA-28023: must revoke grants of this role to other user(s) first
-
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role.
- ORA-28024: must revoke grants of external roles to this role/user
-
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted - these must be revoked, since external roles cannot be granted to global users or roles.
- ORA-28025: missing or null external name
-
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
- ORA-28026: user with same external name already exists
-
Cause: The external name specified for the user being created or altered already exists for another user.
- ORA-28027: privileged database links may be used by global users
-
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
- ORA-28028: could not authenticate remote server
-
Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.
- ORA-28029: could not authorize remote server for user string
-
Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.
- ORA-28030: Server encountered problems accessing LDAP directory service
-
Cause: Unable to access LDAP directory service
- ORA-28031: maximum of string enabled roles exceeded
-
Cause: The user attempted to enable too many roles.
- ORA-28032: Your password has expired and the database is set to read-only
-
Cause: Your password expired and needs to be changed before your login request can be processed. Because the database is currently open in read-only mode, the password change operation cannot be performed on this database.
- ORA-28034: cannot grant string to an Oracle supplied user
-
Cause: The KEEP DATE TIME, KEEP SYSGUID or KEEP SEQUENCE privilege could not be granted to an Oracle supplied user.
- ORA-28035: Cannot Get Session Key for Authentication
-
Cause: Client and server cannot negotiate shared secret during logon
- ORA-28036: HTTP digest authentication cannot be configured for this user
-
Cause: An attempt was made to configure HTTP digest authentication for a global user, an external user, a no authentication type user, or a SYS user.
- ORA-28037: Cannot Get Session Key for RACF Authentication
-
Cause: Client and server cannot negotiate shared secret during logon
- ORA-28038: disallow O2LOGON
-
Cause: turn off O2LOGON
- ORA-28039: cannot validate Kerberos service ticket
-
Cause: The Kerberos service ticket provided was invalid or expired
- ORA-28040: No matching authentication protocol
-
Cause: There was no acceptable authentication protocol for either client or server.
- ORA-28041: Authentication protocol internal error
-
Cause: Authentication protocol failed with an internal error
- ORA-28042: Server authentication failed
-
Cause: Server failed to authenticate itself to the client
- ORA-28043: invalid bind credentials for DB-OID connection
-
Cause: The Database password stored in the wallet did not match the one in OID .
- ORA-28044: unsupported directory type
-
Cause: The database tried to work with a directory which is not OID.
- ORA-28045: SSL authentication between database and OID failed
-
Cause: Server failed to authenticate itself to the Directory.
- ORA-28046: Password change for SYS disallowed
-
Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS password changes.
- ORA-28047: database is not a member of any enterprise domain in OID
-
Cause: An enterprise user login was attempted on a database that is not a member of any enterprise domain in OID.
- ORA-28048: database is a member of multiple enterprise domains in OID
-
Cause: An enterprise user login was attempted on a database that is a member of multiple enterprise domains in OID.
- ORA-28049: the password has expired
-
Cause: The enterprise user's password has expired and the password needs to be changed.
- ORA-28050: specified user or role cannot be dropped
-
Cause: The user or role specified in the DROP statement was a reserved Oracle object that could not be dropped.
- ORA-28051: the account is locked
-
Cause: The enterprise user has consecutively entered the wrong password for maximum number of times specified in the realm's password policy profile.
- ORA-28052: the account is disabled
-
Cause: The enterprise user's account in the directory has been disabled.
- ORA-28053: the account is inactive
-
Cause: The enterprise user's account in the directory is currently not active.
- ORA-28054: the password has expired. string Grace logins are left
-
Cause: The enterprise user's password has expired. The user is able to login because he has gracelogins left.
- ORA-28055: the password will expire within string days
-
Cause: The enterprise user's password is about to expire.
- ORA-28056: Writing audit records to Windows Event Log failed
-
Cause: Unable to write an audit entry to the Windows event log used as the audit trail.
- ORA-28057: name of the password file could not be constructed
-
Cause: Possibly environment variable ORACLE_SID was not set.
- ORA-28058: login is allowed only through a proxy
-
Cause: This account is marked "proxy only connect".
- ORA-28059: Cross-instance call failed
-
Cause: An attempt to inform other Oracle RAC instances of a security event failed.
- ORA-28060: A data redaction policy already exists on this column.
-
Cause: A data redaction policy was already in existence on this column.
- ORA-28061: This object cannot have a data redaction policy defined on it.
-
Cause: An attempt was made to define a data redaction policy on an object other than a table or view. Note that a data redaction policy cannot be defined on an editioned view, or on specialized tables created internally by the server in conjunction with various features such as materialized view.
- ORA-28062: The policy expression is too long.
-
Cause: The policy expression was longer than 4000 characters.
- ORA-28063: The policy expression is empty.
-
Cause: The EXPRESSION parameter to DBMS_REDACT.ADD_POLICY was empty.
- ORA-28064: The redaction function is not valid.
-
Cause: The FUNCTION_TYPE parameter to DBMS_REDACT.ADD_POLICY was invalid.
- ORA-28066: invalid column "string"
-
Cause: An invalid column was specified in the COLUMN_NAME parameter.
- ORA-28067: missing or invalid column name
-
Cause: A valid column name was not specified in the COLUMN_NAME parameter when a column name was required. Note that when using DBMS_REDACT.ALTER_POLICY, the default action is DBMS_REDACT.ADD_COLUMN
- ORA-28068: The object "string" does not have a data redaction policy.
-
Cause: The specified object did not have a data redaction policy defined on it.
- ORA-28069: A data redaction policy already exists on this object.
-
Cause: A data redaction policy was already in existence on this object.
- ORA-28070: The column "string" does not have a data redaction policy.
-
Cause: The specified column did not have a data redaction policy defined on it.
- ORA-28071: The action is not valid.
-
Cause: The ACTION parameter to DBMS_REDACT.ALTER_POLICY was invalid.
- ORA-28072: The specified policy name is incorrect.
-
Cause: The POLICY_NAME parameter was incorrect.
- ORA-28073: The column "string" has an unsupported data type or attribute.
-
Cause: The column had a data type or attribute which is not supported by data redaction. The supported data types are CHAR, NCHAR, VARCHAR2, NVARCHAR2, NUMBER types, BINARY_FLOAT, BINARY_DOUBLE, DATE, TIMESTAMP, CLOB, NCLOB, and BLOB, except as listed below for certain function types: For DBMS_REDACT.PARTIAL and DBMS_REDACT.RANDOM, the CLOB, NCLOB, and BLOB datatypes are not supported. For DBMS_REDACT.REGEXP, the NUMBER, BINARY_FLOAT, BINARY_DOUBLE, DATE, TIMESTAMP, and BLOB datatypes are not supported. Virtual columns and base columns of virtual columns are not supported by data redaction. Columns with the INVISIBLE attribute are not supported by data redaction (this applies to both user-specified hidden columns and system-generated hidden columns). Vector encoded columns are not supported by data redaction. Columns with the IS JSON constraint are not supported.
- ORA-28074: The "string" field of the redaction parameters is not valid.
-
Cause: The redaction parameters specified had one or more fields that were invalid.
- ORA-28075: The data redaction policy expression has an error.
-
Cause: The data redaction policy expression had an error.
- ORA-28076: An attribute was not specified for SYS_SESSION_ROLES.
-
Cause: An attribute was not specified for the SYS_SESSION_ROLES namespace in the policy expression.
- ORA-28077: The attribute specified (string) exceeds the maximum length.
-
Cause: The attribute specified in the policy expression for the SYS_SESSION_ROLES namespace exceeded the maximum length.
- ORA-28078: A regular expression parameter is missing or invalid.
-
Cause: The FUNCTION_TYPE was DBMS_REDACT.REGEXP, but one or more of the regular expression parameters were missing or invalid, the REGEXP_PATTERN failed to compile properly, or the regular expression replacement operation failed.
- ORA-28079: The policy was already enabled.
-
Cause: The redaction policy specified has already been enabled.
- ORA-28080: The policy was already disabled.
-
Cause: The redaction policy specified has already been disabled.
- ORA-28081: Insufficient privileges - the command references a redacted object.
-
Cause: The command referenced a redacted column in an object protected by a data redaction policy.
- ORA-28082: The parameter string is invalid.
-
Cause: The specified parameter was either empty or too long.
- ORA-28083: A redacted column was referenced in a virtual column expression.
-
Cause: This redacted column was referenced in a virtual column expression.
- ORA-28085: The input and output lengths of the redaction do not match.
-
Cause: As specified, the redaction parameters produced an output with a length different to that of the input.
- ORA-28086: The data redaction policy expression has an error.\nstring
-
Cause: The data redaction policy expression had an error.
- ORA-28087: The policy expression has an unsupported (use of) operator 'string'.
-
Cause: The policy expression used an unsupported operator, or used an operator in an unsupported way.
- ORA-28088: The policy expression has an unsupported PL/SQL function string.string.string.
-
Cause: The policy expression had an unsupported PL/SQL function.
- ORA-28089: invalid SYS_CONTEXT namespace string in policy expression
-
Cause: The SYS_CONTEXT (or XS_SYS_CONTEXT) namespace used in the policy expression was not valid.
- ORA-28090: unsupported nesting of function string.string.string within function string.string.string in policy expression
-
Cause: The policy expression had an unsupported PL/SQL function nesting.
- ORA-28091: unsupported use of PL/SQL function string.string.string in policy expression
-
Cause: The policy expression used a PL/SQL function in an unsupported way.
- ORA-28092: The parameter string with value 'string' has an error.
-
Cause: The value of the parameter had an error. If DBMS_REDACT.CREATE_POLICY_EXPRESSION was invoked and the POLICY_EXPRESSION_NAME parameter had an error, the policy expression name either already existed, or was invalid. If DBMS_REDACT.DROP_POLICY_EXPRESSION was invoked and the POLICY_EXPRESSION_NAME parameter had an error, the policy expression either did not exist, was still in use (was applied to a column), or was invalid. If DBMS_REDACT.APPLY_POLICY_EXPR_TO_COL was invoked and the POLICY_EXPRESSION_NAME parameter had an error, a policy expression may already exist on this column. Only one policy expression may be associated with any given column. The name of any Oracle Data Redaction policy expression associated with a given column can be found in the REDACTION_EXPRESSIONS catalog view. If the DBMS_REDACT.ADD_POLICY was invoked and the OBJECT_SCHEMA parameter referenced the APEX or Spatial installation schema, the operation was prevented. Data redaction policies are not supported on objects within the APEX or Spatial installation schema. If the DBMS_REDACT.ADD_POLICY was invoked and the OBJECT_NAME references a metadata-linked view, the operation was prevented. Data redaction policies are not supported on metadata-linked views.
- ORA-28093: operation on column string is not supported by data redaction
-
Cause: The operation was not supported by data redaction.
- ORA-28094: SQL construct not supported by data redaction
-
Cause: The query had a SQL construct that was not supported by data redaction.
- ORA-28100: policy function schema string is invalid
-
Cause: The schema was dropped after the policy associated with the function had been added to the object.
- ORA-28101: policy already exists
-
Cause: A policy with the same name for the same object already exists.
- ORA-28102: policy does not exist
-
Cause: Try to drop/enable/refresh a non-existent policy.
- ORA-28103: adding a policy to an object owned by SYS is not allowed
-
Cause: Try to add a policy to a table or a view owned by SYS.
- ORA-28104: input value for string is not valid
-
Cause: Input value for the argument is not valid
- ORA-28105: cannot create security relevant column policy in an object view
-
Cause: Security relevant column argument is not null in policy creation for an object view
- ORA-28106: input value for argument #string is not valid
-
Cause: Input values for the argument is missing or invalid.
- ORA-28107: policy was disabled
-
Cause: Try to flush a disabled policy.
- ORA-28108: circular security policies detected
-
Cause: Policies for the same object reference each other.
- ORA-28109: the number of related policies has exceeded the limit of 16
-
Cause: Too many policies are involved in the same objects.
- ORA-28110: policy function or package string.string has error
-
Cause: The policy function may have been dropped, or is no longer valid.
- ORA-28111: insufficient privilege to evaluate policy predicate
-
Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access.
- ORA-28112: failed to execute policy function
-
Cause: The policy function has one or more error during execution.
- ORA-28113: policy predicate has error
-
Cause: Policy function generates invalid predicate.
- ORA-28115: policy with check option violation
-
Cause: Policy predicate was evaluated to FALSE with the updated values.
- ORA-28116: insufficient privileges to do direct path access
-
Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.
- ORA-28117: integrity constraint violated - parent record not found
-
Cause: try to update/insert a child record with new foreign key values, but the corresponding parent row is not visible because of fine-grained security in the parent.
- ORA-28118: policy group already exists
-
Cause: try to create a policy group that already exists
- ORA-28119: policy group does not exist
-
Cause: try to drop a policy group that does not exist
- ORA-28120: driving context already exists
-
Cause: try to create a driving context that already exists
- ORA-28121: driving context does not exist
-
Cause: try to drop a driving context that does not exist
- ORA-28122: can not update SYS_DEFAULT policy group
-
Cause: An attempt was made to execute either DBMS_RLS.CREATE_POLICY_GROUP or DBMS_RLS.DELETE_POLICY_GROUP using SYS_DEFAULT as the policy group name.
- ORA-28123: Driving context 'string,string' contains invalid group 'string'
-
Cause: A previous call to DBMS_SESSION.SET_CONTEXT specified an invalid policy group.
- ORA-28124: Column string in sec_relevant_cols cannot be of an object data type
-
Cause: A column specified in sec_relevant_cols was of an object data type.
- ORA-28125: A protected base column was referenced in an unprotected virtual column expression.
-
Cause: A protected base column was referenced in an unprotected virtual column expression.
- ORA-28126: Attribute association failed for policy "string".
-
Cause: An attempt was made to associate a global application context attribute to either a context-sensitive or shared context-sensitive policy. Only local application context attribute association is supported.
- ORA-28132: The MERGE INTO syntax does not support the security policy.
-
Cause: The MERGE INTO syntax did not support a security policy on the destination table, because the policy's statement_types did not include each of INSERT, UPDATE and DELETE.
- ORA-28134: object cannot have fine-grained access control policy
-
Cause: Only tables, views, or synonyms of tables or views may have VPD policies
- ORA-28135: VPD check option silent error event
-
- ORA-28136: Ignore check option error
-
- ORA-28137: Invalid FGA audit Handler
-
Cause: An invalid audit handler was specified.
- ORA-28138: Error in Policy Predicate
-
Cause: An invalid policy predicate was specified.
- ORA-28139: Maximum allowed Fine Grain Audit Policies Exceeded
-
Cause: A maximum of 256 policies can be enabled on an object
- ORA-28140: Invalid column specified
-
Cause: Column name specified during policy creation is invalid
- ORA-28141: error in creating audit index file
-
Cause: ORACLE was not able to create the file being used to hold audit file names.
- ORA-28142: error in accessing audit index file
-
Cause: ORACLE was not able to access the file being used to hold audit file names.
- ORA-28143: Invalid argument passed to FGA ADD_POLICY procedure
-
Cause: Invalid input argument was specified for FGA ADD_POLICY procedure.
- ORA-28144: Failed to execute fine-grained audit handler
-
Cause: An error was encountered while executing fine-grained audit handler.
- ORA-28145: XDS policy already exists for string
-
Cause: An XDS policy was enabled for an object that already has an associated XDS policy.
- ORA-28146: invalid operation for policy "string"
-
Cause: Attribute association (NAMESPACE, ATTRIBUTE) was specified for an invalid policy type. Attribute association can be specified only for context-sensitive and shared context-sensitive policy types.
- ORA-28147: The specified attribute association ("string", "string") is already attached to policy "string".
-
Cause: An attempt was made to create the attribute association using names that were already used by existing attribute association of the policy.
- ORA-28148: The specified attribute association ("string", "string") is not attached to policy "string".
-
Cause: An attempt was made to drop the attribute association that was not attached to the policy.
- ORA-28149: input value for argument "string" is missing
-
Cause: Only one input value was specified for the (NAMESPACE, ATTRIBUTE) arguments.
- ORA-28150: proxy not authorized to connect as client
-
Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.
- ORA-28151: more than one user name specified for command
-
Cause: More than one user name was specified for an ALTER USER command.
- ORA-28152: proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
-
Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role.
- ORA-28153: Invalid client initial role specified: 'string'
-
Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid.
- ORA-28154: Proxy user may not act as client 'string'
-
Cause: A proxy user may not assume the identity of a privileged user in order to limit the privileges that a proxy may possess.
- ORA-28155: user 'string' specified as a proxy is actually a role
-
Cause: A user specified in an AUDIT operation BY proxy ON BEHALF OF client is actually a role.
- ORA-28156: Proxy user 'string' not authorized to set role 'string' for client 'string'
-
Cause: A proxy user has not been granted the right to use a role on behalf of a client.
- ORA-28157: Proxy user 'string' forbidden to set role 'string' for client 'string'
-
Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER client GRANT CONNECT THROUGH proxy WITH ALL ROLES EXCEPT role
- ORA-28158: missing ALL keyword
-
- ORA-28159: missing BEHALF keyword
-
- ORA-28160: missing EXCEPT keyword
-
- ORA-28161: missing ROLES keyword
-
- ORA-28162: missing THROUGH keyword
-
- ORA-28163: GRANT already specified
-
Cause: The GRANT clause was specified twice.
- ORA-28164: REVOKE already specified
-
Cause: The REVOKE clause was specified twice.
- ORA-28165: proxy 'string' may not specify password-protected role 'string' for client 'string'
-
Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed.
- ORA-28166: duplicate rolename in list
-
Cause: The name of a role was specified more than once in a list.
- ORA-28168: attempted to grant password-protected role
-
Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that was password-protected.
- ORA-28169: unsupported certificate type
-
Cause: The type of certificate from which the server is to extract the credentials of the client is not supported.
- ORA-28170: unsupported certificate version
-
Cause: The version of the certificate from which the server is to extract the credentials of the client is not supported.
- ORA-28171: unsupported Kerberos version
-
Cause: the version the Kerberos ticket which the server is to use to validate the identity of the client is not supported.
- ORA-28172: distinguished name not provided by proxy
-
Cause: A client user is to be identified using a distinguished name, but none was provided by the proxy user.
- ORA-28173: certificate not provided by proxy
-
Cause: A client user is to be identified using a certificate but none was provided by the proxy user.
- ORA-28174: Kerberos ticket not provided by proxy
-
Cause: A client user is to be authenticated using a Kerberos ticket but none was provided by the proxy user.
- ORA-28175: incorrect certificate type
-
Cause: the type of certificate provided by the proxy user to identify a client user does not match the type that is required.
- ORA-28176: incorrect certificate version
-
Cause: the version of certificate provided by the proxy user to identify a client user does not match the version that is required.
- ORA-28177: incorrect Kerberos ticket version
-
Cause: the version of Kerberos ticket provided by the proxy user to authenticate a client user does not match the version that is required.
- ORA-28178: password not provided by proxy
-
Cause: A client user is to be authenticated using a database password but none was provided by the proxy user.
- ORA-28179: client user name not provided by proxy
-
Cause: No user name was provided by the proxy user for the client user.
- ORA-28180: multiple authentication methods provided by proxy
-
Cause: More than one authentication method was specified by the proxy user for the client user.
- ORA-28181: proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
-
Cause: Attempt to enable specified initial roles after logon resulted in failure.
- ORA-28182: cannot acquire Kerberos service ticket for client
-
Cause: An attempt to use a Kerberos forwardable ticket granting ticket to obtain a Kerberos service ticket failed.
- ORA-28183: proper authentication not provided by proxy
-
Cause: A client user must be authenticated but no authentication credentials were provided by the proxy user.
- ORA-28184: global user cannot have proxy permissions managed in the directory
-
Cause: The client name specified was a global user.
- ORA-28185: cannot alter user with administrative privilege to proxy-only connect user
-
Cause: An attempt was made to alter a user with administrative privilege to a proxy-only connect user.
- ORA-28186: cannot grant string to a proxy-only connect user
-
Cause: An attempt was made to grant administrative privilege like SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, or SYSRAC to a proxy-only connect user. Since proxy authentication using an administrative privilege is not supported, such grants are not allowed.
- ORA-28187: cannot alter global user to proxy-only connect user
-
Cause: An attempt was made to alter global user to proxy-only connect.
- ORA-28188: cannot alter user SYS/SYSBACKUP/SYSDG/SYSKM/SYSRAC to be identified as globally
-
Cause: An attempt was made to alter SYS/SYSBACKUP/SYSDG/SYSKM/SYSRAC to be identified as globally.
- ORA-28190: SYSRAC administrative privilege cannot be granted to other users
-
Cause: An attempt was made to grant SYSRAC administrative privilege to a user. This administrative privilege can only be used in operating system authentication and cannot be granted to other users.
- ORA-28191: cannot grant administrative privileges to a user with non-ASCII or non-EBCDIC characters in the user name
-
Cause: An attempt to grant privileges to a user failed. Administrative privileges like SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, and SYSRAC cannot be granted to a user with non-ASCII or non-EBCDIC characters in the user name.
- ORA-28200: IDENTIFIED USING already specified
-
Cause: The IDENTIFIED USING clause was specified twice.
- ORA-28201: invalid command to enable secure application role 'string'
-
Cause: An attempt to enable the secure application role outside of the scope of the designated package failed.
- ORA-28206: password length less than number bytes
-
Cause: The password entered by the user did not meet the minimum length criteria.
- ORA-28207: password contains the user name
-
Cause: The provided password contained the user name.
- ORA-28208: password contains the user name in reverse
-
Cause: The provided password contained the reverse of the user name.
- ORA-28209: password contains the server name
-
Cause: The provided password contained the server name.
- ORA-28210: password too simple
-
Cause: The password was simple enough to guess.
- ORA-28211: new password should differ from the old password by string or more characters
-
Cause: The new and old passwords should differ by at least the minimum number of characters as defined by the administrator.
- ORA-28212: password must NOT contain a double-quotation
-
Cause: The double-quotation mark character is reserved as a password delimiter.
- ORA-28213: password must contain number or more letters
-
Cause: The password did not meet the minimum required number of alphabetic characters.
- ORA-28214: password must contain number or more uppercase characters
-
Cause: The password did not meet the minimum required number of uppercase alphabetic characters.
- ORA-28215: password must contain number or more lowercase characters
-
Cause: The password did not meet the minimum required number lowercase alphabetic characters.
- ORA-28216: password must contain number or more digits
-
Cause: The password did not contain the minimum number of digits.
- ORA-28217: password must contain number or more special characters
-
Cause: The password did not contain the minimum number of special characters.
- ORA-28218: password length more than 30 bytes
-
Cause: The length of the password exceeds 30 bytes.
- ORA-28221: REPLACE not specified
-
Cause: User is changing password but password verification function is turned on and the original password is not specified and the user does not have the alter user system privilege.
- ORA-28222: may not modify reserved user
-
Cause: An attempt was made to change or grant to a reserved user account.
- ORA-28223: first login requires password change
-
Cause: This user was globally authenticated. Password policy settings in Oracle Internet Directory (OID) requires the password to be changed for the first connection. Further connections to the database will be denied if the password in OID is not changed.
- ORA-28231: no data passed to obfuscation toolkit
-
Cause: A NULL value was passed to a function or procedure.
- ORA-28232: invalid input length for obfuscation toolkit
-
Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes.
- ORA-28233: double encryption not supported
-
Cause: The obfuscation toolkit does not support the encryption of already-encrypted data.
- ORA-28234: key length too short
-
Cause: The key specified is too short for the algorithm. DES requires a key of at least 8 bytes. Triple DES requires a key of least 16 bytes in two-key mode and 24 bytes in three-key mode.
- ORA-28235: algorithm not available
-
Cause: The encryption algorithm desired is not available.
- ORA-28236: invalid Triple DES mode
-
Cause: An unknown value was specified for the mode in which triple DES encryption is to run.
- ORA-28237: seed length too short
-
Cause: The seed specified for the key generation routine must be at least 80 characters.
- ORA-28238: no seed provided
-
Cause: A NULL value was passed in as the seed to be used in generating a key.
- ORA-28239: no key provided
-
Cause: A NULL value was passed in as an encryption or decryption key.
- ORA-28261: CURRENT_USER can not be used in PLSQL Definer's Right procedure.
-
Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL interface.
- ORA-28262: unused error
-
- ORA-28263: unused error
-
- ORA-28264: Client identifier is too long
-
Cause: The length of the client identifier is longer than 64
- ORA-28265: Namespace beginning with 'SYS_' is not allowed.
-
Cause: Namespace beginning with 'SYS_' was not allowed.
- ORA-28267: Invalid NameSpace Value
-
Cause: Context NameSpace conflicts with reserved key words or a secure Namespace is not allowed for this type of Application Context.
- ORA-28268: Exceeded the maximum allowed size for Context information in a session
-
Cause: The maximum size specified by the _session_context_size init.ora parameter was exceeded.
- ORA-28270: Malformed user nickname for password authenticated global user.
-
Cause: An attempt to login as password-auuthenticated global user with a malformed user nickname.
- ORA-28271: No permission to read user entry in LDAP directory service.
-
Cause: ORACLE server does not have read permission on user nickname's X.500 user entry.
- ORA-28272: Domain policy restricts password based GLOBAL user authentication.
-
Cause: Domain policy does not allow password-authenticated GLOBAL users.
- ORA-28273: No mapping for user nickname to LDAP distinguished name exists.
-
Cause: ORACLE server cannot map the given user nickname to LDAP distinguished name.
- ORA-28274: No ORACLE password attribute corresponding to user nickname exists.
-
Cause: LDAP user entry corresponding to user nickname does not have a ORACLE password attribute or the attribute is not initialized.
- ORA-28275: Multiple mappings for user nickname to LDAP distinguished name exist.
-
Cause: The given user nickname maps to more than one LDAP distinguished name.
- ORA-28276: Invalid ORACLE password attribute.
-
Cause: The ORACLE password attribute of a user entry has an invalid format.
- ORA-28277: LDAP search, while authenticating global user with passwords, failed.
-
Cause: The LDAP search for finding the appropriate user entry and ORACLE password failed.
- ORA-28278: No domain policy registered for password based GLOBAL users.
-
Cause: No policy about password authenticated GLOBAL users has been registered.
- ORA-28279: Error reading ldap_directory_access init parameter.
-
Cause: ldap_directory_access parameter is not specified corrrectly.
- ORA-28280: Multiple entries for ORACLE database password exist.
-
Cause: The ORACLE password attribute of a user entry has multiple entries of ORACLE database password.
- ORA-28281: Global application context is not updated on one or more Oracle RAC instances
-
Cause: While updating global application context across Oracle RAC instances, the background process errored out or the timeout expired due to some failure.
- ORA-28290: Multiple entries found for the same Kerberos Principal Name
-
Cause: Multiple user entries has been configured with the same krbPrincipalName
- ORA-28291: No Kerberos Principal Value found.
-
Cause: Oracle server fails to get value of krbPrincipalName attribute
- ORA-28292: No Domain Policy registered for Kerberos based authentication
-
Cause: The enterprise domain entry is not configured for Kerberos based global authentication.
- ORA-28293: No matched Kerberos Principal found in any user entry
-
Cause: Oracle server fails to find the principal in the user search base
- ORA-28300: No permission to read user entry in LDAP directory service.
-
Cause: ORACLE server does not have read permission on user entries.
- ORA-28301: Domain Policy hasn't been registered for SSL authentication.
-
Cause: An attempt was made to authenticate with SSL, but the database enterprise domain was not configured for SSL authentication.
- ORA-28302: User does not exist in the LDAP directory service.
-
Cause: An attempt was made to authenticate with SSL using the user's certificate, but there was no user entry in the LDAP server that matched the user's Distinguished Name.
- ORA-28303: Distinguished name for user exceeds maximum supported length
-
Cause: The user's distinguished name (DN) exceeded the maximum supported length.
- ORA-28304: Oracle encrypted block is corrupt (file # string, block # string)
-
Cause: The indicated encrypted block was corrupt. This was an in-memory corruption. The exact cause is unknown. Possible causes could be: - the encryption wallet is incorrect or corrupted - the tablespace encryption key is incorrect or corrupted - decryption engine failure - actual logical error exists in decrypted block
- ORA-28305: WALLET_LOCATION in sqlnet.ora file for container database is not supported.
-
Cause: WALLET_LOCATION was specified in sqlnet.ora file.
- ORA-28306: The directory user has string groups mapped to different database global users.
-
Cause: A directory user connected to the database while there were multiple directory user's groups mapped to different shared database global users.
- ORA-28307: The directory current time string is unreasonable.
-
Cause: Either the directory service time was earlier than year 1900, or the format was incorrect.
- ORA-28308: The directory server type string is not supported.
-
Cause: The database tried to work with a directory service which is not
- ORA-28309: Failed to get the service user's credential from the wallet.
-
Cause: The database tried to get the service user's credential from the wallet but
- ORA-28310: Role with same external name already exists.
-
Cause: The external name specified for the role being created or altered already exists for another role.
- ORA-28311: Oracle encrypted data block not encrypted (file # string, block # string)
-
Cause: The indicated data block was found unencrypted in a fully encrypted tablespace. The exact cause is unknown. Possible causes could be: - An encrypted data block is tampered and replaced with an unencrypted data block. - An Oracle internal issue.
- ORA-28312: Proxy user is not supported with DSI.
-
Cause: Proxy user authentication is currently not supported with Directory Service Integration (DSI).
- ORA-28313: LDAP server connection is down.
-
Cause: The LDAP server is down or the connection to the LDAP server is closed.
- ORA-28314: The current user database link is not supported with DSI.
-
Cause: An attempt was made to use the current user database link with Directory Services Integration (DSI).
- ORA-28315: encryption key mismatched for file # string
-
Cause: Oracle tablespace encryption could not verify the master key or the tablespace key for this data file. The exact cause is unknown. Possible cause could be: - The encryption wallet was incorrect. - The encryption wallet was incorrectly shared between databases. - The tablespace encryption key was incorrect or corrupted.
- ORA-28330: encryption is not allowed for this data type or the data type is invalid
-
Cause: The data type was not supported for column encryption or the data type was invalid.
- ORA-28331: encrypted column size too long for its data type
-
Cause: The column was both encrypted and one of the following: -for VARCHAR2 when extended character data types were disabled, the length specified was > 3932; -for VARCHAR2 when extended character data types were enabled, the length specified was > 32699; -for CHAR, the length specified was > 1932; -for NVARCHAR2 when extended character data types were disabled, the length specified was > 1966; -for NVARCHAR2 when extended character data types were enabled, the length specified was > 16349; -for NCHAR, the length specified was > 966; -for RAW when extended character data types were disabled, the length specified was > 3932; -for RAW when extended character data types were enabled, the length specified was > 32699;
- ORA-28332: cannot have more than one password for the encryption key
-
Cause: More than one password was specified in the user command.
- ORA-28333: column is not encrypted
-
Cause: An attempt was made to rekey or decrypt an unencrypted column.
- ORA-28334: column is already encrypted
-
Cause: An attempt was made to encrypt an encrypted column.
- ORA-28335: referenced or referencing FK constraint column cannot be encrypted
-
Cause: encrypted columns were involved in the referential constraint
- ORA-28336: cannot encrypt SYS owned objects
-
Cause: An attempt was made to encrypt columns in a table owned by SYS.
- ORA-28337: the specified index may not be defined on an encrypted column
-
Cause: Index column was either a functional, domain, or join index.
- ORA-28338: Column(s) cannot be both indexed and encrypted with salt
-
Cause: An attempt was made to encrypt index column with salt or an attempt was made to create an index on encrypted column with salt.
- ORA-28339: missing or invalid encryption algorithm
-
Cause: Encryption algorithm was missing or invalid in the user command.
- ORA-28340: a different encryption algorithm has been chosen for the table
-
Cause: Existing encrypted columns were associated with a different algorithm.
- ORA-28341: cannot encrypt constraint column(s) with salt
-
Cause: An attempt was made to encrypt constraint columns with salt.
- ORA-28342: integrity check fails on column key
-
Cause: Encryption metadata may have been improperly altered.
- ORA-28343: fails to encrypt data
-
Cause: data or encryption metadata may have been improperly altered or the security module may not have been properly setup
- ORA-28344: fails to decrypt data
-
Cause: data or encryption metadata may have been improperly altered or the security module may not have been properly setup
- ORA-28345: cannot downgrade because there exists encrypted column
-
Cause: An attempt was made to downgrade when there was an encrypted column in the system.
- ORA-28346: an encrypted column cannot serve as a partitioning column
-
Cause: An attempt was made to encrypt a partitioning key column or create partitioning index with encrypted columns.
- ORA-28347: encryption properties mismatch
-
Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but encryption properties were mismatched.
- ORA-28348: index defined on the specified column cannot be encrypted
-
Cause: An attempt was made to encrypt a column which is in a functional index, domain index, or join index.
- ORA-28349: cannot encrypt the specified column recorded in the materialized view log
-
Cause: An attempt was made to encrypt a column which is already recorded in the materialized view log.
- ORA-28350: cannot encrypt the specified column recorded in CDC synchronized change table
-
Cause: An attempt was made to encrypt a column which is already recorded in CDC synchronized change table.
- ORA-28351: cannot encrypt the column of a cluster key
-
Cause: An attempt was made to encrypt a column of the cluster key. A column of the cluster key in a clustered table cannot be encrypted.
- ORA-28353: failed to open wallet
-
Cause: The database was unable to open the security module wallet due to an incorrect wallet path or password It is also possible that a wallet has not been created. Type mkwallet from command line for instructions.
- ORA-28354: Encryption wallet, auto login wallet, or HSM is already open
-
Cause: Encryption wallet, auto login wallet, or HSM was already opened.
- ORA-28355: failed to initialize security module
-
- ORA-28356: invalid open wallet syntax
-
Cause: The command to open the wallet contained improper spelling or syntax.
- ORA-28357: password required to open the wallet
-
Cause: A password was not provided when executing the open wallet command, the isolate keystore command, or the unite keystore command.
- ORA-28358: improper set key syntax
-
Cause: The command to set the master key contained improper spelling or syntax.
- ORA-28359: invalid certificate identifier
-
Cause: The certificate specified did not exist in the wallet.
- ORA-28360: security module internal error
-
- ORA-28361: master key not yet set
-
Cause: The master key for the instance was not set.
- ORA-28362: master key not found
-
Cause: The required master key required could not be located. This may be casued by the use of an invalid or incorrect wallet.
- ORA-28363: buffer provided not large enough for output
-
Cause: A provided output buffer is too small to contain the output.
- ORA-28364: invalid wallet operation
-
Cause: The command to operate the wallet contained improper spelling or syntax.
- ORA-28365: wallet is not open
-
Cause: The security module wallet has not been opened.
- ORA-28366: invalid database encryption operation
-
Cause: The command for database encryption contained improper spelling or syntax.
- ORA-28367: wallet does not exist
-
Cause: The Oracle wallet has not been created or the wallet location parameters in sqlnet.ora specifies an invalid wallet path.
- ORA-28368: cannot auto-create wallet
-
Cause: The database failed to auto create an Oracle wallet. The Oracle process may not have proper file permissions or a wallet may already exist.
- ORA-28369: cannot add files to encryption-ready tablespace when offline
-
Cause: You attempted to add files to an encryption-ready tablespace when all the files in the tablespace were offline.
- ORA-28370: ENCRYPT, DECRYPT or REKEY option not allowed
-
Cause: An attempt was made to specify the ENCRYPT, DECRYPT or REKEY option on an unsupported tablespace.
- ORA-28371: ENCRYPTION clause or ENCRYPT option not allowed
-
Cause: An attempt was made to specify the ENCRYPTION clause or ENCRYPT option for system and undo tablespaces.
- ORA-28372: missing ENCRYPT option for encrypted tablespace
-
Cause: An attempt was made to specify the ENCRYPTION property for the CREATE TABLESPACE statement without specifying the ENCRYPT option to encrypt the tablespace.
- ORA-28373: missing or out of order ENCRYPTION clause
-
Cause: An attempt was made to specify the ENCRYPT or DECRYPT option in the CREATE TABLESPACE statement or to specify the ENCRYPT or REKEY option in the ALTER TABLESPACE statement without first specifying the ENCRYPTION property for the tablespace.
- ORA-28374: typed master key not found in wallet
-
Cause: You attempted to access encrypted tablespace or redo logs with a typed master key not existing in the wallet.
- ORA-28375: cannot perform cross-endianism conversion on encrypted tablespace
-
Cause: You attempted to perform cross-endianism conversion on encrypted tablespace.
- ORA-28376: cannot find PKCS11 library
-
Cause: The HSM vendor's library cannot be found.
- ORA-28377: No need to migrate from wallet to HSM
-
Cause: There are either no encrypted columns or all column keys are already encrypted with the HSM master key.
- ORA-28378: Wallet not open after setting the Master Key
-
Cause: The Master Key has been set or reset. However, wallet could not be reopened successfully.
- ORA-28379: a different integrity algorithm has been chosen for the table
-
Cause: Encrypted columns were associated with a different algorithm.
- ORA-28382: Global wallet operation in RAC failed
-
Cause: Wallet operation in RAC failed.
- ORA-28383: cannot do a PKI certificate-based Master Key migration
-
Cause: A PKI certificate-based Master Key migration was not allowed.
- ORA-28384: cannot perform Tablespace Encryption
-
Cause: Tablespace Encryption was attempted when PKI certificate-based Master Key was in use.
- ORA-28385: cannot perform a PKI certificate-based migration
-
Cause: A PKI certificate-based migration to HSM was attempted.
- ORA-28386: cannot perform a PKI certificate-based Master Key Rekey
-
Cause: A PKI certificate-based Master Key Rekey was attempted when Tablespace Encryption or HSM was in use.
- ORA-28387: Could not acquire an enqueue for wallet operation in Oracle RAC
-
Cause: Enqueue to block TDE operations in Oracle RAC database could not be obtained.
- ORA-28388: database is not open in read/write mode
-
Cause: Database was not open in read/write mode and could not perform these wallet operations.
- ORA-28389: cannot close auto login wallet
-
Cause: Auto login wallet could not be closed because it was opened with another wallet or HSM requiring a password.
- ORA-28390: auto login wallet not open but encryption wallet may be open
-
Cause: Auto login wallet was not open. But, the encryption wallet may still be open and subsequent TDE operations might succeed.
- ORA-28391: cannot close wallet or HSM, password mismatch
-
Cause: Password provided did not match the password of the open wallet or HSM.
- ORA-28392: invalid close wallet syntax
-
Cause: The command to close the wallet contained improper spelling or syntax.
- ORA-28393: password required to close the wallet
-
Cause: A password was not provided when executing the close wallet command.
- ORA-28394: decryption of data of length string failed
-
Cause: Decryption of data failed. Error may be due to plain text data in an external file being submitted for decryption, data encrypted with a different key or a utility being submitted for decryption, or TDE encrypted data in data files being corrupted.
- ORA-28395: could not write the new master key to the wallet
-
Cause: An attempt was made to write the new master key to the wallet. The wallet or the parent directory may not have the proper file permissions to write the master key in the wallet.
- ORA-28396: rekey of enc$ dictionary table failed
-
Cause: One or more master keys required for the rekey operation could not be found in the wallet. Either incorrect master key identifiers were inserted into the enc$ dictionary table or the wallet containing the referenced master keys were improperly modified or deleted.
- ORA-28397: cannot bring file string online since it has a passphrase-wrapped key
-
Cause: The encrypted tablespace file was rewrapped using passphrase through the DBMS_TTS.PASSPHRASE_REWRAP_KEY procedure. Therefore it cannot be part of the database until it is converted by RMAN.
- ORA-28398: cannot rewrap encryption key for this file
-
Cause: Cannot rewrap encryption key for this file because it was not from an encrypted tablespace, or it had already been rewrapped.
- ORA-28403: file string cannot be modified because it is an online data file
-
Cause: An attempt was made to modify an online data file when the file was not expected to be part of the database.
- ORA-28404: role cannot be altered
-
Cause: An attempt was made to alter the role to become a global, external, password protected, or secure application role. The role could not be altered because it was already granted to one or more other roles or program units.
- ORA-28405: cannot grant secure role to a role
-
Cause: Role granted was a password protected or secure application role. This role can only be granted directly to a user.
- ORA-28407: Hardware Security Module failed with PKCS#11 error string(string)
-
Cause: The Hardware Security Module (HSM) connection may have been lost or another internal HSM error was reached.
- ORA-28408: encryption using passphrase failed
-
Cause: Encryption with the passphrase failed which was likely due to an invalid or missing passphrase or due to an internal error.
- ORA-28409: decryption using passphrase failed
-
Cause: Decryption with the passphrase failed which was likely due to an invalid or missing passphrase or due to an internal error.
- ORA-28410: No need to migrate from HSM to wallet.
-
Cause: There were either no encrypted columns or all column keys were already encrypted with the wallet master key.
- ORA-28411: auto login wallet cannot be open during migration
-
Cause: Auto login wallet could not be opened during migration.
- ORA-28412: cannot determine the database migration status
-
Cause: The migration status of the database could not be determined.
- ORA-28414: specified keys are in HSM
-
Cause: Master key rekey or activation failed because the keys were in Hardware Security Module(HSM) but the configuration indicated that the keys were in wallet.
- ORA-28415: specified keys are in wallet
-
Cause: Master key rekey or activation failed because the keys were in wallet but the configuration indicated that the keys were in Hardware Security Module(HSM).
- ORA-28416: specify the correct keystore in the sqlnet.ora file
-
Cause: The keystore specified in the sqlnet.ora file was incorrect.
- ORA-28417: password-based keystore is not open
-
Cause: Password-based keystore was not opened.
- ORA-28418: password-based HSM is not open
-
Cause: Password-based HSM was not opened.
- ORA-28419: migration from wallet to Hardware Security Module (HSM) failed
-
Cause: The TDE_MASTER_KEY_ID entry did not exist in props$ table. A subsequent attempt to add TDE_MASTER_KEY_ID entry into props$ failed.
- ORA-28420: cannot open resetlogs from a restore point prior to wallet creation
-
Cause: The open resetlogs, open read-only, or standby activation operation failed because the restore point is prior to the wallet creation, and the data file does not contain the database key information as stored in the control file.
- ORA-28421: cannot FINISH a tablespace encrypt, decrypt or rekey command which has not started
-
Cause: The ALTER TABLESPACE FINISH [ENCRYPT | DECRYPT | REKEY] command did not find a failed attempt for tablespace encrypt, decrypt or rekey.
- ORA-28422: operation disallowed: concurrent master key rekey
-
Cause: Concurrent master key rekey was detected.
- ORA-28423: current operation disallowed: string tablespace is being encrypted, decrypted, or rekeyed
-
Cause: The specified tablespace was being concurrently encrypted, decrypted, or rekeyed.
- ORA-28424: ENCRYPT, DECRYPT or REKEY option already specified
-
Cause: In the CREATE or ALTER TABLESPACE statement, the ENCRYPT, DECRYPT or REKEY option was specified more than once.
- ORA-28425: missing a valid FILE_NAME_CONVERT clause
-
Cause: A valid FILE_NAME_CONVERT clause was not specified with the ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] statement. The FILE_NAME_CONVERT clause is required unless Oracle Managed Files are being used.
- ORA-28426: must FINISH a tablespace encrypt, decrypt or rekey command first
-
Cause: The ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] command found a previously failed attempt for tablespace encrypt, decrypt or rekey.
- ORA-28427: cannot create, import or restore unencrypted tablespace: string in Oracle Cloud
-
Cause: The specified tablespaces were not encrypted. Oracle Cloud mandates that all tablespaces must be encrypted.
- ORA-28428: cannot encrypt or decrypt a data file in mount mode when the database is open elsewhere
-
Cause: An attempt was made to encrypt or decrypt a data file in mount mode when the database was already opened by another Oracle RAC instance.
- ORA-28429: cannot encrypt or decrypt a data file on standby when it is open read-only
-
Cause: An attempt was made to encrypt or decrypt a data file on a standby database when it was already opened in read-only mode.
- ORA-28430: cannot encrypt or decrypt a data file for online tablespace string
-
Cause: An attempt was made to encrypt or decrypt a data file for an online tablespace.
- ORA-28431: cannot encrypt an already encrypted data file string
-
Cause: An attempt was made to encrypt a data file that was already encrypted in an encrypted tablespace.
- ORA-28432: cannot encrypt data file string in seed pluggable database
-
Cause: An attempt was made to encrypt a data file that was part of a seed pluggable database, which is not allowed.
- ORA-28433: mismatched encryption property between data file string and tablespace string
-
Cause: Either an unencrypted data file in an encrypted tablespace or an encrypted data file in an unencrypted tablespace was found. When bringing a tablespace online or opening the database, all data files in an encrypted tablespace must be encrypted, and all data files in an unencrypted tablespace must be unencrypted.
- ORA-28434: cannot decrypt an unencrypted data file string
-
Cause: An attempt was made to decrypt a data file that was unencrypted.
- ORA-28435: cannot decrypt data file string which is not encrypted with the database key
-
Cause: An attempt was made to decrypt a data file that was not encrypted with the database key. Only data files encrypted with the ALTER DATABASE DATAFILE ENCRYPT or ALTER TABLESPACE ENCRYPTION OFFLINE ENCRYPT statement are encrypted with the database key.
- ORA-28436: cannot encrypt data file string in SYSTEM or SYSAUX tablespace
-
Cause: An attempt was made to encrypt a data file that was a part of the SYSTEM or SYSAUX tablespace, which is not allowed in compatibility lower than 12.2.
- ORA-28437: unexpected FILE_NAME_CONVERT clause with Oracle Managed Files
-
Cause: A FILE_NAME_CONVERT clause was specified with the ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] statement, which is not allowed when the database is using Oracle Managed Files.
- ORA-28438: ALTER TABLESPACE string ENCRYPTION stringstring operation not complete
-
Cause: The ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] command started but could not complete for all the data files of this tablespace.
- ORA-28439: cannot close wallet when SYSTEM, SYSAUX, UNDO, or TEMP tablespaces are encrypted
-
Cause: An attempt was made to close the wallet for a database with an encrypted SYSTEM, SYSAUX, UNDO, or TEMP tablespace.
- ORA-28440: cannot offline encrypt or decrypt data file string - file is in use or recovery
-
Cause: An attempt was made to offline encrypt or decrypt a data file that was online in an open instance, being encrypted or decrypted by another session, or was being recovered.
- ORA-28441: RMAN clone instance cannot open wallet
-
Cause: The RMAN clone instance failed to open the auto login wallet in an operation such as a pluggable database (PDB) or tablespace point-in-time recovery because the auto login wallet was incorrectly configured, or did not exist.
- ORA-28442: Rekey of the TDE master encryption key is not permitted when the database is in restricted mode.
-
Cause: An attempt was made to rekey the Transparent Data Encryption (TDE) master encryption key when the database was in restricted mode.
- ORA-28443: cannot access the TDE wallet
-
Cause: An attempt was made to access the Transparent Data Encryption (TDE) master encryption key in the TDE wallet.
- ORA-28444: cannot enforce encryption of dictionary data
-
Cause: Either encryption of the dictionary data was already enforced or an attempt was made to enforce encryption of the dictionary data with compatible parameter earlier than release 12.2.0.2.
- ORA-28445: Execution of the command failed.
-
Cause: Command execution failed due to an internal error.
- ORA-28446: cannot execute dictionary data rekey/delete key
-
Cause: Could not find an existing data encryption key.
- ORA-28447: insufficient privilege to execute ALTER DATABASE DICTIONARY statement
-
Cause: An attempt was made to execute the ALTER DATABASE DICTIONARY statement without the necessary SYSKM privilege. For CONTAINER = ALL clause, the user must have the commonly granted SYSKM privilege or the user must have the local SYSKM privilege.
- ORA-28448: The ALTER DATABASE DICTIONARY statement was used incorrectly.
-
Cause: ALTER DATABASE DICTIONARY statement was used incorrectly.
- ORA-28449: cannot use an invalidated database link
-
Cause: An attempt was made to use an invalid database link.
- ORA-28450: encryption specified with CREATE DATABASE or CREATE PLUGGABLE DATABSE
-
Cause: The encryption option was specified in a CREATE DATABASE or a CREATE PLUGGABLE DATABASE statement.
- ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
-
Cause: The cause is explained in the forwarded message.
- ORA-28501: communication error on heterogeneous database link
-
Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.
- ORA-28502: internal communication error on heterogeneous database link
-
Cause: A communication error internal to ORACLE's heterogeneous services has occurred.
- ORA-28503: bind value cannot be translated into SQL text for non-Oracle system
-
Cause: A SQL statement used bind variables on a Heterogenous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables.
- ORA-28504: ROWID not found in ROWID cache for heterogeneous database link
-
Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache.
- ORA-28505: cannot get non-Oracle system capabilities from string
-
Cause: ORACLE was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
- ORA-28506: parse error in data dictionary translation for string stored in string
-
Cause: A reference to an ORACLE data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The ORACLE data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation.
- ORA-28507: error in data dictionary view string
-
Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect.
- ORA-28508: invalid value string for Heterogeneous Services initialization parameter string
-
Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system.
- ORA-28509: unable to establish a connection to non-Oracle system
-
Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.
- ORA-28510: heterogeneous database link initialization failed
-
Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.
- ORA-28511: lost RPC connection to heterogeneous remote agent using SID=string
-
Cause: A fatal error occurred in one of the following places: -- the connection between the ORACLE server and the agent -- the heterogeneous services remote agent itself -- the connection to the non-Oracle system This error occurred after communication had been established successfully.
- ORA-28512: cannot get data dictionary translations from string
-
Cause: ORACLE was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views.
- ORA-28513: internal error in heterogeneous remote agent
-
Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.
- ORA-28514: heterogeneous database link initialization could not convert system date
-
Cause: The system date was not retrievable.
- ORA-28515: cannot get external object definitions from string
-
Cause: ORACLE was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed.
- ORA-28518: data dictionary translation has illegal translation type
-
Cause: A data dictionary translation definition, either in the ORACLE server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the ORACLE instance and to the ORACLE instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an ORACLE server on the first connection from the server to the agent.
- ORA-28519: no heterogeneous data dictionary translations available
-
Cause: The ORACLE server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
- ORA-28520: error initializing heterogeneous data dictionary translations
-
Cause: ORACLE was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
- ORA-28521: no heterogeneous capability information available
-
Cause: The ORACLE server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
- ORA-28522: error initializing heterogeneous capabilities
-
Cause: ORACLE was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
- ORA-28523: ORACLE and heterogeneous agent are incompatible versions
-
Cause: An operation on a database link attempted to connect to a non-Oracle system, but the ORACLE instance and the agent process for the non-Oracle system are incompatible.
- ORA-28525: unable to create Heterogeneous Services error message text
-
Cause: Incorrect arguments were passed into the error message creation routine.
- ORA-28526: invalid describe information returned to Heterogeneous Services
-
Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.
- ORA-28527: Heterogeneous Services datatype mapping error
-
Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the ORACLE server's data dictionary.
- ORA-28528: Heterogeneous Services datatype conversion error
-
Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for for the conversion failure: -- overflow problems (in the case of numbers) -- length limitations (in the case of character strings) -- invalid values passed into the conversion routines
- ORA-28529: invalid or missing parameter in Net8 service name definition
-
Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server.
- ORA-28530: Heterogeneous Services initialization error in NLS language ID
-
Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the ORACLE server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs.
- ORA-28533: Heterogeneous Services coercion handling error
-
Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions.
- ORA-28534: Heterogeneous Services preprocessing error
-
Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled.
- ORA-28535: invalid Heterogeneous Services context
-
Cause: A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver.
- ORA-28536: error in processing Heterogeneous Services initialization parameters
-
Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the ORACLE server data dictionary.
- ORA-28537: no more result sets
-
Cause: This error code was used internally within Oracle Database Gateway and Heterogeneous Services code and should not be reported to a client program.
- ORA-28538: result set not found
-
Cause: The client program tried fetching from a result set that is not open anymore. Many gateways will, on execution of a stored procedure, automatically close all result sets that were returned by any previously executed stored procedure.
- ORA-28539: gateway does not support result sets
-
Cause: The client program tried executing a stored procedure that returns one or more result sets through a gateway that does not have result set support.
- ORA-28540: internal result set error
-
Cause: A protocol error internal to Heterogeneous Services or Oracle Database Gateway code has occurred.
- ORA-28541: Error in HS init file on line number.\n
-
Cause: A syntax error occurred in the gateway initialization file.
- ORA-28542: Error in reading HS init file \n
-
Cause: Reading the gateway init file generated an error.
- ORA-28543: Error initializing apply connection to non-Oracle system
-
Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed.
- ORA-28544: connect to agent failed, probable Net8 administration error
-
Cause: Net8 reported a failure to make a RSLV connection or a protocol mode error when the Oracle server attempted to establish communication with a Heterogeneous Services agent or an external procedure agent. This usually is due to an administration error in setting up Net8 service definitions in TNSNAMES.ORA or LISTENER.ORA: A basic network connection is opened, but it connects to a program which does not use the appropriate protocol. This often is a sign that the connection goes to the wrong program.
- ORA-28545: error diagnosed by Net8 when connecting to an agent
-
Cause: An attempt to call an external procedure or to issue SQL to a non-Oracle system on a Heterogeneous Services database link failed at connection initialization. The error diagnosed by Net8 NCR software is reported separately.
- ORA-28546: connection initialization failed, probable Net8 admin error
-
Cause: A failure occurred during initialization of a network connection from the Oracle server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are: -- Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent. -- Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle server. -- The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent. -- Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=). -- Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=).
- ORA-28547: connection to server failed, probable Oracle Net admin error
-
Cause: A failure occurred during initialization of a network connection from a client process to the Oracle server. The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Oracle Net administrative setup for database links or external procedure calls. The most frequent specific causes are: -- The connection uses a connect string which refers to a Heterogeneous Services agent instead of an Oracle server. -- The connection uses a connect string which includes an (HS=) specification. -- Hitting Ctrl+C before connection initialization is complete. -- Using DRCP on Windows with SQLNET.AUTHENTICATION_SERVICES set to NTS. -- Connection timeout due to SQLNET.INBOUND_CONNECT_TIMEOUT parameter when all shared servers are busy in shared server configuration. -- The character set of the database is not recognized by the client process, which may be caused by an incorrect or unnecessary setting of the ORA_NLS10 client environment variable or by a new or user-defined character set installed in the Oracle server and used for the database.
- ORA-28550: pass-through SQL: cursor not found
-
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
- ORA-28551: pass-through SQL: SQL parse error
-
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
- ORA-28552: pass-through SQL: call flow error
-
Cause: A pass-through SQL function was called in an invalid order.
- ORA-28553: pass-through SQL: invalid bind-variable position
-
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
- ORA-28554: pass-through SQL: out of cursors
-
Cause: The maximum number of open cursors has been exceeded.
- ORA-28555: pass-through SQL: required parameter missing or NULL
-
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
- ORA-28556: authorization insufficient to access table
-
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
- ORA-28557: unknown string for database link to non-Oracle system
-
Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these names to configure the heterogeneous database link.
- ORA-28558: HS_FDS_CONNECT_STRING undefined for non-Oracle system
-
Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the ORACLE server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed.
- ORA-28559: FDS_CLASS_NAME is string, FDS_INST_NAME is string
-
Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the ORACLE data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store.
- ORA-28560: error in configuration of agent process
-
Cause: An ORACLE server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable.
- ORA-28561: unable to set date format on non-Oracle system
-
Cause: Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system.
- ORA-28562: Heterogeneous Services data truncation error
-
Cause: A select operation was attempted with an insufficient data buffer to satisfy the request.
- ORA-28575: unable to open RPC connection to external procedure agent
-
Cause: Initialization of a network connection to the extproc agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code.
- ORA-28576: lost RPC connection to external procedure agent
-
Cause: A fatal error occurred in either an RPC network connection, the extproc agent, or the invoked 3GL after communication had been established successfully.
- ORA-28577: argument string of external procedure string has unsupported datatype string
-
Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected.
- ORA-28578: protocol error during callback from an external procedure
-
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
- ORA-28579: network error during callback from external procedure agent
-
Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
- ORA-28580: recursive external procedures are not supported
-
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
- ORA-28581: protocol error while executing recursive external procedure
-
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
- ORA-28582: a direct connection to this agent is not allowed
-
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.
- ORA-28583: remote references are not permitted during agent callbacks
-
Cause: A Heterogeous Services agent issued a callback to the Oracle server which attemted to to access a remote system. This is not supported.
- ORA-28584: heterogeneous apply internal error
-
Cause: The apply slave process encountered an error while trying to apply changes through a gateway to a non-Oracle system.
- ORA-28590: agent control utility: illegal or badly formed command
-
Cause: The user has issued an unrecognized or syntactically incorrect command.
- ORA-28591: agent control utility: unable to access parameter file
-
Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its admin directory or because permissions on directory were not correctly set.
- ORA-28592: agent control utility: agent SID not set
-
Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail.
- ORA-28593: agent control utility: command terminated with error
-
Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shutdown an agent that is no longer running.
- ORA-28594: agent control utility: invalid parameter name
-
Cause: The user tried to set or unset an invalid agent parameter.
- ORA-28595: Extproc agent : Invalid DLL Path
-
Cause: The path of DLL supplied for the extproc execution is invalid.
- ORA-28596: Extproc agent : Invalid or disabled credential string
-
Cause: The credentail of the PL/SQL library supplied for the extproc execution is invalid.
- ORA-28601: invalid [no]MINIMIZE option
-
Cause: user didn't type this alter table <table_name> MINIMIZE RECORDS_PER_BLOCK or alter table <table_name> NOMINIMIZE RECORDS_PER_BLOCK
- ORA-28602: statement not permitted on tables containing bitmap indexes
-
Cause: table has bitmap indexes and user is minimizing or nominimizing records_per_block
- ORA-28603: statement not permitted on empty tables
-
Cause: table is empty and statement does not work on empty tables
- ORA-28604: table too fragmented to build bitmap index (string,string,string)
-
Cause: The table has one or more blocks that exceed the maximum number of rows expected when creating a bitmap index. This is probably due to deleted rows. The values in the message are: (data block address, slot number found, maximum slot allowed)
- ORA-28605: bitmap indexes cannot be reversed
-
Cause: user tried to create reverse bitmap index
- ORA-28606: block too fragmented to build bitmap index (string,string)
-
Cause: The block(s) exceed the maximum number of rows expected when creating a bitmap index. This is probably due to maximum slot allowed set too low. The values in the message are: (slot number found, maximum slot allowed)
- ORA-28611: bitmap index is corrupted - see trace file for diagnostics
-
Cause: Validate Index detected bitmap corruption in its argument index
- ORA-28650: Primary index on an IOT cannot be rebuilt
-
Cause: An attempt is made to issue alter index rebuild on IOT-TOP
- ORA-28651: Primary index on IOTs can not be marked unusable
-
Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX
- ORA-28652: overflow segment attributes cannot be specified
-
Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING.
- ORA-28653: tables must both be index-organized
-
Cause: Attempt to exchange a non IOT table/partition with a partition/table respectively
- ORA-28654: table and partition not overflow compatible
-
Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one doesn't.
- ORA-28655: Alter table add overflow syntax error
-
Cause: Syntax error
- ORA-28656: incomplete attribute specification
-
Cause: The attribute specification is not done for all partitions"
- ORA-28658: This operation is supported only for Index-Organized tables
-
Cause: Attempt to perform some IOT specific operation on a non-IOT
- ORA-28659: COMPRESS must be specified at object level first
-
Cause: Attempt to specify COMPRESS at partition level without first specifying at the table level
- ORA-28660: Partitioned Index-Organized table may not be MOVEd as a whole
-
Cause: Attempt to MOVE partitioned IOT as a whole
- ORA-28661: Object already has COMPRESS clause specified
-
Cause: Attempt to specify compress for iot/index which already has a compression clause.
- ORA-28662: IOT index and overflow segments must share the same LOGGING attribute
-
Cause: Attempt to specify LOGGING for one segment and NOLOGGING for the other segment.
- ORA-28663: Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
-
Cause: Attempt to specify LOGGING for a Alter Table Add Overflow.
- ORA-28664: a partitioned table may not be coalesced as a whole
-
Cause: User attempted to coalesce a partitioned IOT using ALTER TABLE COALESCE statement, which is illegal
- ORA-28665: table and partition must have same compression attribute
-
Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition
- ORA-28666: option not allowed for an index on UROWID column(s)
-
Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s)
- ORA-28667: USING INDEX option not allowed for the primary key of an IOT
-
Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required.
- ORA-28668: cannot reference mapping table of an index-organized table
-
Cause: An attempt to directly access the mapping table of an index-organized table
- ORA-28669: bitmap index can not be created on an IOT with no mapping table
-
Cause: User attempted to create a bitmap index on an index-organized table without a mapping table.
- ORA-28670: mapping table cannot be dropped due to an existing bitmap index
-
Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexed.
- ORA-28671: UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
-
Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal.
- ORA-28672: UPDATE BLOCK REFERENCES may not be used on a global index
-
Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned index on a partitioned IOT and a global partitioned index on a non-partitioned IOT.
- ORA-28673: Merge operation not allowed on an index-organized table
-
Cause: User attempted merge operation on an index-organized table. Merge is not supported on a IOT .
- ORA-28674: cannot reference transient index-organized table
-
Cause: An attempt was made to directly access a transient table created created on behalf of a index-organized table partition maintenance operation.
- ORA-28700: Only roles can be attached to or detached from program units.
-
Cause: An attempt was made to grant object privileges or system privileges to program units.
- ORA-28701: Keyword PROCEDURE, FUNCTION, or PACKAGE is either missing or not correct.
-
Cause: The keyword PROCEDURE, FUNCTION, or PACKAGE was either missing before the program unit, or it was not consistent with the type of the program unit.
- ORA-28702: Program unit string is not owned by the grantor.
-
Cause: An attempt was made to attach roles to or detach roles from one or more program units by someone other than the owner or SYS. Only a program unit owner or SYS can attach roles to or detach roles from a program unit.
- ORA-28703: Only regular database roles can be attached to or detached from program units.
-
Cause: An attempt was made to attach non-supported types of roles to or detach them from program units. Application roles, secure application roles, external roles, global roles, and light-weight roles cannot be attached to or detached from program units.
- ORA-28704: Role string is not directly granted to the owner of the program units.
-
Cause: An attempt was made to attach roles that were not directly granted to the owner of the program units. The roles must be granted to the owner directly in order to attach them to the owner's program units.
- ORA-28705: The grantor does not have privileges to grant the role string to the program units.
-
Cause: Privileges to grant a role to a program unit were insufficient. The grantor must have the GRANT ANY ROLE privilege or the ADMIN option or the DELEGATE option for the role to do the operation.
- ORA-28706: duplicate program unit string found in list
-
Cause: A duplicate program unit was found in the GRANTEE clause.
- ORA-28707: Reserved word ALL was used with roles in the REVOKE command to detach roles from program units.
-
Cause: An attempt was made to use reserved word ALL jointly with roles in a REVOKE command to detach roles from program units.
- ORA-28708: More than string roles were attached to the program unit.
-
Cause: Too many roles were currently attached to the program unit.
- ORA-28709: Roles with DELEGATE option can only be granted to users.
-
Cause: One of the grantees was not a user when trying to grant roles with the DELEGATE option.
- ORA-28714: OCI_BATCH_ERRORS or OCI_RETURN_ROW_COUNT_ARRAY mode can only be specified for INSERT, UPDATE, DELETE or MERGE statement.
-
Cause: OCI_BATCH_ERRORS or OCI_RETURN_ROW_COUNT_ARRAY mode was specified in a statement which is not INSERT, UPDATE, DELETE or MERGE.
- ORA-28715: OCI_STMT_SCROLLABLE_READONLY can only be specified for SELECT statements.
-
Cause: OCI_STMT_SCROLLABLE_READONLY mode was specified for a non-SELECT statement.
- ORA-28716: Invalid buffer or buffer size for OCIServerRelease2() \n
-
Cause: A zero length or null buffer was specified for the OCIServerRelease2().