Oracle Database Error Messages (ORA-26001 - ORA-29500)


I summarized a list of (ORA) oracle error codes list with cause and action, use browser find (CTRL+F) to get your desire error code, cause and possible action.

Oracle Database Error Messages (ORA-26001 - ORA-29500)




ORA-26001: Index string specified in SORTED INDEXES does not exist on table string
Cause: A nonexistent index was specified in the SORTED INDEXES clause.
Action: Do not specify as a SORTED INDEX.

ORA-26002: Table string has index defined upon it.
Cause: Parallel load was specified into a table which has index defined upon it.
Action: Drop index(es) defined upon table, or don't use parallel load, or use SKIP_INDEX_MAINTENANCE option.

ORA-26003: parallel load not supported for index-organized table string.
Cause: Parallel load is not supported for index-organized tables.
Action: load the index-organized table without the PARALLEL option.

ORA-26004: Tables loaded through the direct path may not be clustered
Cause: User attempted to load a clustered table via the direct path.
Action: Use the conventional path.

ORA-26005: Invalid handle for direct path load
Cause: In direct path load, the handle passed in does not match the type listed.
Action: Verify the handle and type are correct.

ORA-26006: Incorrect bind variable in column string's sql expression - string
Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.
Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list.

ORA-26007: invalid value for SETID or OID column
Cause: The value passed in a Direct Path API stream for a column containing a SETID or OID has an invalid value. SETIDs and Object IDs must be either 16 bytes of RAW data or 32 bytes of hexidecimal characters.
Action: Regenerate the Direct Path API stream with a valid value for the SETID column.

ORA-26008: Invalid syntax or bind variable in SQL string for column stringstring
Cause: See following error message for more information. A SQL string cannot have quoted strings improperly terminated. A bind variable in a SQL string cannot have a length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a double quote.
Action: Fix the SQL string. See following error for more information.

ORA-26010: Column string in table string is NOT NULL and is not being loaded
Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.
Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file.

ORA-26011: Cannot load type string into column string in table string
Cause: A column can only store data of type declared for that column. And a substitutable column can only store data of valid subtypes of the supertype declared for that column.
Action: Check that the type or subtype specified is valid for that column.

ORA-26012: header in file string has an incompatible version number
Cause: A dump file was specified for a load operation whose version number is incompatible with the dump file version currently produced by the Oracle server on the system. Usually this message indicates that the dump file was produced by a newer version of the Oracle server.
Action: Load this dump file using the same version of the Oracle server that created the file.

ORA-26013: List allocated may not be big enough
Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.
Action: Contact Oracle Customer Support.

ORA-26014: unexpected error on string string while retrieving string string
Cause: The SQL error was returned from an OCIStmtExecute call.
Action: Correct the SQL error that was returned.

ORA-26015: Array column string in table string is not supported by direct path
Cause: User attempted to load an array column via the direct path.
Action: Use the conventional path.

ORA-26016: Virtual column string in table string.string cannot be loaded by direct path
Cause: You attempted to load an virtual column using the direct path.
Action: Virtual columns cannot be loaded using the direct path.

ORA-26017: global indexes not allowed for direct path load of table partition string
Cause: Global indexes are defined on a table when direct path loading a single partition of the table.
Action: None

ORA-26018: Column string in table string does not exist
Cause: Column specified in the loader control file does not exist.
Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong.

ORA-26019: Column string in table string of type string not supported by direct path
Cause: The Specified column of SQL column type %s is not supported by the direct path loader.
Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL.

ORA-26020: index string.string loaded successfully with string keys
Cause: Non-partitioned index information put to loader log file.
Action: None. Informational only.

ORA-26021: index string.string partition string loaded successfully with string keys
Cause: Partitioned index information put to loader log file.
Action: None. Informational only.

ORA-26022: index string.string was made unusable due to:
Cause: A Non-partitioned index was made index unusable due to the error displayed below this error.
Action: Depending on the error, either rebuild the index, or drop and re-create it.

ORA-26023: index string.string partition string was made unusable due to:
Cause: A partition of a partitioned index was made index unusable due to error displayed below this error.
Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index.

ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment
* was in unusable state prior to the beginning of the load.
Action: Informational only. User will need to either rebuild the index
* or index partition, or re-create the index.

ORA-26025: SKIP_INDEX_MAINTENANCE option requested
Cause: User requested that index maintenance be skipped on a direct path load.
Action: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index.

ORA-26026: unique index string.string initially in unusable state
Cause: A unique index is in IU state (a unique index cannot have
* index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use
* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.

ORA-26027: unique index string.string partition string initially in unusable state
Cause: A partition of a unique index is in IU state (a unique index
* cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use
* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.

ORA-26028: index string.string initially in unusable state
Cause: An index is in IU state prior to the beginning of a direct
* path load, it cannot be maintained by the loader.
Action: Either rebuild the index, re-create the index, or use either
* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).

ORA-26029: index string.string partition string initially in unusable state
Cause: A partition of an index is in IU state prior to the beginning
* of a direct path load, it cannot be maintained by the loader.
Action: Either rebuild index partition, re-create the index, or use either
* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).

ORA-26030: index string.string had string partitions made unusable due to:
Cause: A logical index error occurred on a partitioned index which
* affected one or more index partitions, which are listed below
* this message.
Action: The affected index partitions will have to be re-built, or, the
* entire index dropped and re-created.

ORA-26031: index maintenance error, the load cannot continue
Cause: A index errror occurred during the index maintenance phase of
* a direct path load. The load cannot continue. See error message
* below this message.
Action: See action for the error message which follows this one.

ORA-26032: index string.string loading aborted after string keys
Cause: An index error occurred during direct-load of an index-organized table.
* Loading had to be aborted. No rows were loaded.
Action: Check the key just following the number of keys mentioned above.
* This key caused the index problem mentioned in an earlier message. *

ORA-26033: column string.string encryption properties differ for source or target table
Cause: The source and destination columns did not have the same
* encryption properties.
Action: For security reasons, check that the source and target table have
* the same encryption properties. *

ORA-26034: Column string does not exist in stream
Cause: Column specified in the column list does not exist in the stream.
Action: Make sure the column exists or remove it from the list.

ORA-26035: Error attempting to encrypt or decrypt column
Cause: An error occurred while attemping to encrypt or decrypt
* a database column.
Action: Verify correct encryption key was specified. *

ORA-26036: subpartition load specified but table string is not subpartitioned
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned.
Action: Remove the subpartition specification from the SQL*Loader control file and retry the load.

ORA-26037: must specify partition name(s) for system partitioned table string
Cause: An attempt was made to load a system partitioned table with no partition name(s) specified.
Action: Specify the partition name(s) explicitly.

ORA-26040: Data block was loaded using the NOLOGGING option
Cause: Trying to access data in block that was loaded without
* redo generation using the NOLOGGING/UNRECOVERABLE option
Action: Drop the object containing the block.

ORA-26041: DATETIME/INTERVAL datatype conversion error
Cause: The column could not be converted from DATETIME
* datatype to internal DATETIME/CHARACTER datatype.
Action: Contact Oracle Customer Support.

ORA-26045: REF column string expects string arguments; found string.
Cause: The number of arguments for the REF column is incorrect.
Action: Specify the correct number of input arguments for REFs.
1. Unscoped system-generated REFs can have exactly 1 or 2 input arguments. a) It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
2. Scoped system-generated REFs can have 1 or 2 input arguments. Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted.
3. Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments. Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.

ORA-26046: REF column string expects scoped table name string; user passed in string.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.

ORA-26048: Scoped REF column has wrong table name.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.

ORA-26049: Unscoped REF column has non-existent table name.
Cause: The table name passed in by the user does not exist in the schema.
Action: Specify a valid table name for the unscoped REF column.

ORA-26050: Direct path load of domain index is not supported for this column type.
Cause: Direct path can not load a domain index of that column type.
Action: Drop the index and try again or load using conventional path.

ORA-26051: internal error parsing packed decimal format string
Cause: A packed decimal field with a non-zero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.
Action: Examine the packed decimal field's precision and scale specifications and make sure that they contain valid values.

ORA-26052: Unsupported type number for SQL expression on column string.
Cause: The direct path api does not support a SQL expression on a column of that type.
Action: Make sure the types are correct.

ORA-26053: Row was not loaded due to conversion error.
Cause: The current row was not loaded due to a conversion error.
Action: Continue with the load anyways. 260xx - 260xx Direct Path API

ORA-26054: Direct Path Context prepared for a different mode than operation requested.
Cause: The user prepared the direct path context for one operation (Load, Unload, Convert), but then tried to perform a different operation.
Action: Make sure the direct path context mode and operation matches.

ORA-26055: Invalid buffer specified for direct path unload
Cause: The user specified a zero length or null buffer to be used for the Direct Path Unload operation.
Action: Specify a valid buffer and length.

ORA-26056: Requested direct path operation on a view is not supported.
Cause: User attempted to unload or load from/into a view via direct path.
Action: Unload from or load into a normal table.

ORA-26057: Conversion is not necessary for this direct path stream.
Cause: User attempted to convert a direct path stream that does not require conversion.
Action: Load the stream without conversion it.

ORA-26058: unexpected error fetching metadata for column string in table string
Cause: The direct path API encountered an unexpected error while retrieving metadata for a column.
Action: Contact Oracle support.

ORA-26059: Data is too large for column string
Cause: The direct path API encountered a column that can not be loaded because the input data is too large for a column.
Action: Make the target column larger.

ORA-26060: Can not convert type identifier for column string
Cause: The direct path API encountered a type identifier for a column that can not be loaded because a mapping can not be found for the input value.
Action: Verify the input data.

ORA-26061: Concurrent direct unloads is not allowed.
Cause: User attempted a direct unload when another is still in progress.
Action: Complete the current direct unload before starting another.

ORA-26062: Can not continue from previous errors.
Cause: User attempted to continue a direct path load after receiving an error which indicates the load can not continue.
Action: Address the original error that was returned.

ORA-26063: Can not flashback to specified SCN value - Wrap: string Base: string.
Cause: User specified an SCN which occurs before the last time the table definition was modified.
Action: Specify a more recent SCN.

ORA-26064: Invalid SCN specified - Wrap: string Base: string.
Cause: User specified an invalid SCN.
Action: Specify a valid SCN.

ORA-26065: check constraint cannot reference column, string, in direct path load
Cause: An enabled check constraint was found on a column stored as a lob.
Action: Either disable the check constraint before loading the table data
* using the direct path mode, or use the conventional path mode
* instead.

ORA-26076: cannot set or reset value after direct path structure is allocated
Cause: Client attempted to set or reset the number of rows in a direct path
* structure after it has already been allocated and initialized.
* Attributes used is one of the following:
* - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array
* - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache
* (default is 0)
* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be
* disabled on overflow (default is FALSE)
Action: Set the following attributes before:
* - OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array
* - OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare
* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare

ORA-26077: direct path column array is not initialized
Cause: Client attempted to allocate a column array for a direct path
* function context before allocating a column array for the
* table-level direct path context.
Action: Allocate the table-level direct path context's column array
* via OCIHandleAlloc before allocating column arrays for
* direct path function contexts.

ORA-26078: file "string" is not part of database being loaded
Cause: A parallel load file was specified which is not part
* of the database.
Action: Check filename and pathname for correctness.

ORA-26079: file "string" is not part of table string.string
Cause: A parallel load file was specified which is not in the
* tablespace of the table being loaded.
Action: Check to make sure that the specified parallel load file
* is in the tablespace of the table being loaded.

ORA-26080: file "string" is not part of table string.string partition string
Cause: A parallel load file was specified which is not in the
* tablespace of the table (partition, subpartition) being loaded.
* When a partitioned table is being loaded, the file must be
* in the tablespace of every partition or subpartition
* (i.e. each (sub)partition must be in the same tablespace).
Action: Specify a different parallel load file, or no file at all.

ORA-26082: load of overlapping segments on table string.string is not allowed
Cause: Client application is attempting to do multiple direct path load
* operations on the same table, but the segments overlap.
Action: Check the partition names (subname attribute of the direct path
* context) being loaded. Make sure you are not loading a table,
* and a partition of the same table. Make sure you are not
* loading a partition, and a sub-partition within the same
* partition.

ORA-26083: unsupported direct path stream version string
Cause: The stream version requested is not supported by the server.
Action: Check to make sure that the VERSION attribute of the direct
* stream is not being set to an invalid value.

ORA-26084: direct path context already finished
Cause: An OCIDirPathLoadStream operation was attempted after
* OCIDirPathFinish was called. Once a direct path operaton
* has been finished, no more data can be loaded.
Action: Check program logic to make sure OCIDirPathLoadStream is
* not called after OCIDirPathFinish.

ORA-26085: direct path operation must start its own transaction
Cause: A direct path operation is being attempted within a transaction
* that has already been started.
Action: Commit the transaction and Prepare the direct path operation again.

ORA-26086: direct path does not support triggers
Cause: A direct path operation is being attempted on a table which
* has enabled triggers.
Action: Disable the triggers on the table and try again.

ORA-26088: scalar column "string" must be specified prior to LOB columns
Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be
* specified by the client of the direct path API prior to
* specifying any LOB columns.
Action: Specify all scalar columns prior to specifying any LOB columns.

ORA-26089: LONG column "string" must be specified last
Cause: A client of the direct path API specified a LONG column to be
* loaded, but the LONG column was not the last column to be
* specified.
Action: Specify the LONG column last.

ORA-26090: row is in partial state
Cause: A direct path operation is being finished or a data save request
* has been made, but the table for which the request is being made
* on has a row in partial state. The row must be completed before
* the segment high water marks can be moved.
Action: Either complete the row, or abort the direct path operation.

ORA-26091: requested direct path operation not supported
Cause: A direct path operation was requested that is not supported
Action: Do not use that operation. Currently, UNLOAD is not supported.

ORA-26092: only LONG or LOB types can be partial
Cause: A column which is not a LONG or LOB had the
* OCI_DIRPATH_COL_PARTIAL flag associated with it.
* Only LONG or LOB type columns can be loaded in pieces.
Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.

ORA-26093: input data column size (number) exceeds the maximum input size (number)
Cause: The user attempted to specify a column size (%d) that exceeded
* the maximum allowable input size (%d)."
Action: Make sure the input column metadata matches the column definition.

ORA-26094: stream format error: input column overflow
Cause: An input stream contained data for more input columns
* than specified by the client of the direct path API.
Action: Make sure that the stream being loaded is for the
* correct table. Check initialization sequence.

ORA-26095: unprocessed stream data exists
Cause: Either a OCIDirPathLoadStream call was made which provided
* more stream data prior to the server being able to fully
* process the stream data that it already has, or a
* OCIDirPathFinish call was made when the server had
* unprocessed stream data.
Action: Most likely an application mis-use of the direct path API.
* Make sure that the stream is not being reset inadvertently
* prior to any previous stream data being processed, or, that
* OCIDirPathFinish is not being called prematurely (i.e. stream
* pushed, error encountered and LoadStream not called to process
* the remainder of the stream before Finish is called.)

ORA-26096: transfer size too small for row data (number bytes required)
Cause: Either the transfer buffer size specified, or the default
* transfer buffer size (if you did not specify a size), is
* too small to contain a single row of the converted row data.
Action: Set the transfer buffer size attribute of the direct path
* context to be larger.

ORA-26097: unsupported conversion for column string (from type number to type number)
Cause: The direct path api does not support the required conversion.
Action: Make sure the types are correct. *

ORA-26098: direct path context is not prepared
Cause: A direct path api function was called with a direct path
* context which has not been prepared.
Action: Make sure all necessary attributes in the direct path
* context have been set, and the context is prepared via
* OCIDirPathPrepare.

ORA-26099: direct path context is already prepared
Cause: OCIDirPathPrepare was called with a context that has already
* been prepared.
Action: Free the direct path context, set necessary attributes, and
* call OCIDirPathPrepare.

ORA-26101: tablespace # in file header is string rather than string for file string
Cause: The tablespace number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and data file.

ORA-26102: relative file # in file header is string rather than string for file string
Cause: The relative file number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and data file.

ORA-26103: V6 or V7 data file used to create control file
Cause: The file header of the referenced file is in V6 or V7 format.
Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format.

ORA-26500: error on caching "string"."string"
Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.
Action: Use dbms_reputil.sync_up_rep to validate the replication catalog, or use dbms_reputil.make_internal_pkg to validate internal package.

ORA-26501: RepAPI operation failure
Cause: An external RepAPI operation failed.
Action: consult detail error message.

ORA-26502: error resignal
Cause: An internal service failed and signalled an error"
Action: consult detail error message.

ORA-26503: internal RepAPI operation failure on object string.string
Cause: An unexpected internal RepAPI failure was detected
Action: Contact Oracle support.

ORA-26504: operation not implemented
Cause: The caller requested a RepAPI operation that was not implemented
Action: Do not issue this call.

ORA-26505: unexpected internal null
Cause: An internal buffer control structure was NULL
Action: Verify that sufficient memory resources are available to RepAPI.

ORA-26506: null global context
Cause: An internal buffer control structure was NULL
Action: Verify that sufficient memory resources are available to RepAPI.

ORA-26507: null master connection
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid.

ORA-26508: null materialized view connection
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.

ORA-26509: null materialized view control structure
Cause: An internal materialized view control structure could not be obtained.
Action: Check that the owner and users provided are correct.

ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes
Cause: The specified materialized view name was too long.
Action: Shorten the materialized view name.

ORA-26511: master table 'string.string' not found
Cause: A RepAPI operation was attempted against a non-existent or invalid master table
Action: Verify that the master table object exists.

ORA-26512: error pushing transaction to def$error
Cause: An unexpected error occurred while sending an def$error rpc to the master site
Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary.

ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string
Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.
Action: Notify master site system adminstrator or DBA.

ORA-26514: object 'string.string' not found
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.

ORA-26515: no master log available for 'string.string'
Cause: The specified master log was not found or available for the named table.
Action: Create the master log at the master site or correct any problems that may exist with the log.

ORA-26516: no push transaction acknowledgement
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully commited by the master site.
Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction.

ORA-26517: materialized view control entry for 'string.string' was not found
Cause: The specified materialized view catalog control reocrd was not found.
Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined.

ORA-26518: push queue synchronization error detected
Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.
Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transactionIDs and is not accidently generating non-unique values.

ORA-26519: no memory available to allocate
Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.
Action: Shutdown one or more local applications to attempt to free heap memory and retry the RepAPI operation.

ORA-26520: internal memory failure
Cause: An internal memory error was detected.
Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem.

ORA-26521: rpc initialization error
Cause: An error occurred during the initialization of a PL/SQL rpc.
Action: Verify that the procudure to be invoked exists and is valid at the master site and is executable by the RepAPI user.

ORA-26522: rpc execution error
Cause: An error occurred during the execution of a PL/SQL rpc.
Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked rpc.

ORA-26523: rpc termination error
Cause: An error occurred during the termination of a PL/SQL rpc. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.
Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted.

ORA-26524: nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly initialized.
Action: Check that the error message directory and file(s) have been properly installed.

ORA-26525: session connection attempt failed for string (@string)
Cause: A connection could not be established to the specified database using the provided connection string.
Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working.

ORA-26526: materialized view sql ddl parse/expansion failed for string.string
Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site.
Action: Check that materialized view ddl sql is compatible with the currently connected version of Oracle and does not violate any of the RepAPI sql limitations or restrictions.

ORA-26527: local store callback init phase failed for 'string.string'
Cause: The client callback failed during its INIT phase for the named object.
Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26528: local store callback proc phase failed for 'string.string'
Cause: The client callback failed during its PROC phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26529: local store callback term phase failed for 'string.string'
Cause: The client callback failed during its TERM phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26530: unable to build materialized view refresh control list
Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.
Action: Verify that the named materialized view(s) are properly defined and valid.

ORA-26532: replication parallel push simulated site failure
Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.
Action: Do not enable the event for normal operation.

ORA-26534: collision: tranID number ignored and purged
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: See the action section for E_QUEUESYNC (26518).

ORA-26535: number byte row cache insufficient for table with rowsize=number
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables.

ORA-26536: refresh was aborted because of conflicts caused by deferred transactions
Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view's master site.
Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.

ORA-26563: renaming this table is not allowed
Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has beencreated.
Action: If desired, unregister the replicated table with dbms_repcat.drop_master_repobject, or use the recommended procedure to rename the master table of a materialized view.

ORA-26564: string argument is not of specified type
Cause: User passed type of the given argument number doesn't match with the type of the argument in the stored arguments.
Action: Invoke correct type procedure (i.e. get_XXX_arg)

ORA-26565: Call to _arg made before calling dbms_defer.call
Cause: User invoked _arg procedure before starting a deferred call
Action: Invoke various procedures in the correct order.

ORA-26566: Couldn't open connect to string
Cause: Failed to open connection using given dblink
Action: Make sure that the dblink is valid and remote m/c is up.

ORA-26571: string.string.string: number of arguments (string) does not match replication catalog
Cause: number of arguments does not match replication catalog
Action: examine total number of arguments for the rpc call

ORA-26572: string.string.string: argument string does not match replication catalog
Cause: the (rpc) call is corrupted
Action: examine total number of arguments and each argument for the rpc call

ORA-26575: remote database does not support replication parallel propagation
Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.
Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.

ORA-26576: cannot acquire SR enqueue
Cause: An attempt to acquire the SR enqueue in exclusive mode failed.
Action: None

ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string
Cause: The materialized view consists of a view and a container table.
Action: Drop the materialized view without PRESERVE TABLE option.

ORA-26650: string background process string might not be started successfully
Cause: An error occurred during creation of a capture or apply background process.
Action: Please review V$Capture and V$Apply_coordinator views for the status of these processes. Please also check the trace file for more information.

ORA-26651: Unable to start or stop capture process string
Cause: An attempt was made to start or stop a capture process while another capture process was concurrently starting or stopping.
Action: You cannot concurrently start or stop capture processes. Wait before attempting to start or stop additional capture processes.

ORA-26660: Invalid action context value for string
Cause: The value specified in the action context is invalid for use in STREAMS.
Action: Check that the type and value are correct.

ORA-26662: unable to process STREAMS Data Dictonary information for object
Cause: The database is unable to process STREAMS Data Dictionary for this object.
Action: Check that the compatibility for the database supports the object, and check the trace file for information about the object.

ORA-26663: error queue for apply process string must be empty
Cause: The error queue for this apply process contains error entries.
Action: Execute or delete errors in the error queue.

ORA-26664: cannot create STREAMS process string
Cause: An attempt was made to create a STREAMS process when another was being created concurrently.
Action: Wait for the creation of the other STREAMS process to finish before attempting to create the STREAMS process.

ORA-26665: STREAMS process string already exists
Cause: An attempt was made to create a STREAMS process that already exists.
Action: Either specify another STREAMS process or remove the existing STREAMS process.

ORA-26666: cannot alter STREAMS process string
Cause: An attempt was made to alter a STREAMS process that is currently running.
Action: Stop the STREAMS process with FORCE parameter set to TRUE and reissue the command.

ORA-26667: invalid STREAMS parameter string
Cause: An attempt was made to specify an invalid parameter.
Action: Check the documentation for valid parameters.

ORA-26668: STREAMS process string exists
Cause: An attempt to remove the component failed because it is associated with the STREAMS process.
Action: Either remove the process manually or specify the "cascade" option in dbms_streams_adm.remove_queue.

ORA-26669: parameter string inconsistent with parameter string
Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.
Action: Check the documentation for valid parameter values.

ORA-26671: maximum number of STREAMS processes exceeded
Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.
Action: Remove existing STREAMS processes and retry the operation.

ORA-26672: timeout occurred while stopping STREAMS process string
Cause: Timeout occurred while waiting for a STREAMS process to shut down.
Action: Retry the operation. If the error persists, try stopping the process with the FORCE option, or contact Oracle Support Services.

ORA-26673: duplicate column name string
Cause: An attempt was made to specify a duplicate column name in an LCR.
Action: Remove the duplicate column and retry the operation.

ORA-26674: Column mismatch in 'string.string' (LCR: string type=string; DB: string type=string)
Cause: The columns in the LCR were not the same or not found in the database table.
Action: Alter the database table.

ORA-26675: cannot create Streams capture process string
Cause: Streams capture process could not be created because one or more parameters contain invalid value.
Action: Refer to trace file for more details.

ORA-26676: Table 'string.string' has string columns in the LCR and string columns in the replicated site
Cause: The number of columns in the LCR was not the same as the the replicated site.
Action: Alter the table structure

ORA-26677: Streams downstream capture process string cannot proceed
Cause: Database global name has been set to a value which is same as the source database name of the downstream capture process.
Action: Change database global name to a value other than the source database name for the downstream capture.

ORA-26678: Streams downstream capture process for source database string must be created at database string first
Cause: A Streams downstream capture process was nonexistent when this operation was attempted.
Action: Create a Streams downstream capture process, then retry the operation.

ORA-26679: operation not allowed on LOB or LONG columns in LCR
Cause: Certain operations on LOB/LONG columns of the LCR through rule-based transformations, DML handlers, or error handlers were not allowed.
Action: Do not perform restricted operations on LOB or LONG columns in LCRs. See the documentation for operations that are restricted on LOB/LONG columns in LCRs.

ORA-26680: object type not supported
Cause: The specified object type is not supported.
Action: Retry with a supported object type.

ORA-26681: command type not supported
Cause: The specified command type is not supported.
Action: Retry with a supported command type.

ORA-26682: invalid value for publication_on
Cause: The publication_on parameter should be either 'Y' or 'N'
Action: Retry with a proper value for publication_on.

ORA-26683: invalid value for value_type
Cause: The value_type parameter should be either 'OLD' or 'NEW'
Action: Retry with proper value_type.

ORA-26684: invalid value for value_type
Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'
Action: Retry with proper value_type.

ORA-26685: cannot apply transactions from multiple sources
Cause: Transactions from multiple sources were sent to the same apply process.
Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.

ORA-26686: cannot capture from specified SCN
Cause: An attempt was made to specify an invalid SCN.
Action: Retry with a valid SCN.

ORA-26687: no instantiation SCN provided for "string"."string" in source database "string"
Cause: Object SCN was not set. If the object is a table, then both fields will be filled, for example "SCOTT"."EMP". If the object is a schema, only one field will be set, for example "SCOTT"."". And if the object is the entire database, no fields will be set, for example ""."".
Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN

ORA-26688: missing key in LCR
Cause: Metadata mismatch, or not enough information in the user generated LCR.
Action: Alter the database object, or provide all defined keys in the LCR.

ORA-26689: column datatype mismatch in LCR
Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.
Action: Alter the database object.

ORA-26690: datatype not supported at non-Oracle system
Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.
Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.

ORA-26691: operation not supported at non-Oracle system
Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.
Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.

ORA-26692: invalid value stringstring should be in string format
Cause: The parameter specified was not in the correct format.
Action: Specify the parameter value in the correct format.

ORA-26693: STREAMS 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 STREAMS proccess successfully.
Action: Check existence of rule set and manually drop if necessary.

ORA-26694: error while enqueueing into queue string.string
Cause: An error occurred while enqueueing a message.
Action: If the situation described in the next error on the stack can be corrected, do so.

ORA-26695: error on call to string: return code string
Cause: A locking related call failed.
Action: Try the call again after fixing the condition indicated by the return code.

ORA-26696: no streams data dictionary for object with number string and version number string from source database string
Cause: An attempt to access the database object failed because the data dictionary for the object was either never populated or it was purged.
Action: Make sure the streams data dictionary is created by calling DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION.

ORA-26697: LCR contains extra column 'string'
Cause: The LCR contained more columns than the replicated table.
Action: Alter the database object.

ORA-26698: string did not have a string rule set
Cause: The STREAMS client does not have a rule set of the indicated type.
Action: Verify that the Streams client has a rule set of the specified type, and retry the operation.

ORA-26699: STREAMS message consumer string already exists
Cause: An attempt was made to create a STREAMS message consumer that already exists.
Action: Either specify another STREAMS message consumer or remove the existing STREAMS message consumer.

ORA-26701: STREAMS process string does not exist
Cause: An attempt was made to access a STREAMS process which does not exist.
Action: Check with the relevant security views for the correct name of the object.

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 Streams data dictionary.
Action: Drop the capture process before attempting the downgrade.

ORA-26706: cannot downgrade capture process
Cause: An attempt was made to downgrade a capture process that has a higher version than the downgrade release version.
Action: Drop the capture process after capture has finished consuming all the redo logs before attempting the downgrade.

ORA-26708: remote DDL not supported by STREAMS : dblink string
Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not supported.
Action: Do not attempt to apply DDL LCRs via a dblink. If possible, filter out DDL LCRs before applying.

ORA-26709: Streams RFS restart
Cause: Remote file server (RFS) process was restarted to reflect a change in DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process.
Action: No action required. This is an informational message only.

ORA-26710: incompatible version marker encountered during Capture
Cause: Capture process cannot mine redo from a version higher than the current software release version.
Action: Drop and recreate the capture process.

ORA-26711: remote table does not contain a primary key constraint
Cause: The master table for remote apply does not constain a primary key constraint or the primary key constraint has been disabled.
Action: Create a primary key constraint on the master table or enable the existing constraint.

ORA-26712: remote object is "string"."string"\@"string"
Cause: See the preceding error message to identify the cause. This message names the remote object, usually a table or view, for which an error occurred when Streams tried to access it for remote apply.
Action: See the preceding error message.

ORA-26713: remote object does not exist or is inaccessible
Cause: Streams replication could not access the named table or view at a remote database to apply changes.
Action: Confirm that the given remote table or view exists and is accessible through the given database link. When using a Heterogeneous Services database link to access a non-Oracle system, it may be necessary to check administration details for network connections at the non-Oracle system.

ORA-26714: User error encountered while applying
Cause: An error was encountered while applying.
Action: Query the dba_apply_error view to determine the error and take the appropriate action.

ORA-26715: time limit reached
Cause: The specified time limit was reached for the STREAMS process.
Action: Restart the STREAMS process, increasing the TIME_LIMIT parameter if necessary.

ORA-26716: message limit reached
Cause: The specified message limit was reached for the Capture process.
Action: Restart the Capture process, increasing the MESSAGE_LIMIT parameter if necessary.

ORA-26717: SCN limit reached
Cause: The specified SCN limit was reached for the STREAMS process.
Action: Change the MAXIMUM_SCN parameter, then restart the STREAMS process.

ORA-26718: transaction limit reached
Cause: The specified transaction limit was reached for the Apply process.
Action: Restart the Apply process, increasing the TRANSACTION_LIMIT parameter if necessary.

ORA-26721: enqueue of the LCR not allowed
Cause: An apply process attempted to enqueue an LCR with a LONG column. This is not supported.
Action: Modify rules or unset the enqueue destination to prevent LCRs with LONG columns from being enqueued by the apply process.

ORA-26723: user "string" requires the role "string"
Cause: The caller did not have the specified role or called the procedure from a definer's rights package or procedure.
Action: Grant the specified role to the caller. If the procedure is called from a definer's rights package or procedure, change the definer's rights package or procedure to an invoker's rights package or procedure. Or grant all the privileges for the specified role explicitly.

ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.
Cause: The Capture or Apply user was specified as SYS by a user other than SYS.
Action: Set SYS as the Capture or Apply user while logged in as SYS.

ORA-26725: cannot downgrade apply handlers
Cause: An attempt was made to downgrade apply handlers that are not associated with a local database object, or the apply handlers are associated with a specific apply process.
Action: Drop the associated apply handlers before attempting the downgrade.

ORA-26726: logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
Cause: An attempt was made to set the logical standby database and DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process on the same database.
Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a Streams capture process on a logical standby database. Do not attempt to make a database logical standby if there exists a Streams capture process with the DOWNSTREAM_REAL_TIME_MINE parameter set to Y.

ORA-26727: Cannot alter queue_to_queue property of existing propagation.
Cause: The queue_to_queue property was specified for an existing propagation.
Action: Pass NULL for the queue_to_queue argument.

ORA-26730: string 'string' already exists
Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE failed because the item in question already exists.
Action: Remove the object if appropriate and re-attempt the operation.

ORA-26731: string 'string' does not exist
Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist.
Action: Make sure the object exists and re-attempt the operation.

ORA-26732: invalid file group string privilege
Cause: The specified privilege number that was specified is invalid.
Action: Check specification of dbms_file_group for valid privileges.

ORA-26733: timed-out waiting for file group lock
Cause: The procedure waited too long while getting a lock to perform a file group repository operation.
Action: Retry the operation.

ORA-26734: different datafiles_directory_object parameter must be specified
Cause: The attempted operation involved datafiles platform conversion which required the datafiles_directory_object parameter to be specified for placing the converted data files.
Action: Retry the operation after specifying a valid datafiles_directory_object parameter. This directory must be different from the directory objects for any of the datafiles for the specified file group version.

ORA-26735: operation not allowed on the specified file group version
Cause: One or more datafiles or export dump file(s) were missing from the specified file group version.
Action: Retry the operation after adding all the data files and Data Pump dump file(s) to the specified version.

ORA-26736: Data Pump error
Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation.
Action: Check the error stack and trace file for error details.

ORA-26737: version string already has an export dump file
Cause: A Data Pump dump file was added to a file group version that already has a dump file.
Action: Remove the existing dump file if appropriate, and retry the operation.

ORA-26738: string 'string' is not empty
Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects.
Action: Remove the child objects, then retry the operation.

ORA-26740: cannot downgrade because there are file groups
Cause: An attempt was made to downgrade a database that has file groups.
Action: Drop all file groups before attempting the downgrade.

ORA-26741: cannot assemble lobs
Cause: An attempt was made to assemble lobs, but the compatibility of the source database for the LOB information is lower than 10.2.0.
Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while this handler is processing LOB information from a source database with a compatibility level lower than 10.2.0.

ORA-26742: Maximum number of ignored transactions exceeded
Cause: An attempt was made to add more than the allowed number of ignored transactions.
Action: Please clear the current list of ignored transactions.

ORA-26744: STREAMS capture process "string" does not support "string"."string" because of the following reason: string
Cause: STREAMS capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.
Action: Revise the Capture rules to skip over the table in question. One way might be to add a negative rule excluding changes from the unsupported table from being captured. Also query the DBA_STREAMS_UNSUPPORTED view to determine which tables are not supported by STREAMS and for what reason. Consider adding negative rules for any tables that may be captured, but are present in this view. For potential workarounds to certain unsupported properties, see Metalink.

ORA-26745: cursors (string) are not sufficient
Cause: The maximum number of open cursors was too small for Streams Apply.
Action: Increase the value of open_cursors.

ORA-26746: DDL rule "string"."string" not allowed for this operation
Cause: A DDL rule was specified for this operation.
Action: Specify a non-DDL rule for this operation.

ORA-26747: The one-to-many transformation function string encountered the following error: string
Cause: The specified transformation function encountered an error.
Action: Ensure that the function does not process or return DDL LCRs. Also ensure that the function does not return NULL.

ORA-26748: The one-to-one transformation function string encountered the following error: string
Cause: The specified transformation function encountered an error.
Action: Ensure that the function does not return an LCR that has a different type from the LCR which was passed to the function. Also ensure that the function does not return NULL. For DDL transformation functions, creating and returning a new DDL LCR is not allowed.

ORA-26752: Unsupported LCR received for "string"."string"
Cause: Streams capture process received an LCR with unsupported operation from LogMiner.
Action: If this object is listed in DBA_STREAMS_UNSUPPORTED view, modify rules to prevent changes made to this object from getting captured.

ORA-26753: Mismatched columns found in 'string.string'
Cause: The columns in the LCR were not the same as the table in the database.
Action: Alter the database table.

ORA-26754: cannot specify both one-to-one transformation function string and one-to-many transformation function string
Cause: Both a one-to-one transformation function and a one-to-many transformation function were specified for a rule.
Action: Remove either the one-to-one transformation function, or the one-to-many transformation function.

ORA-26760: Could not find message number string for transaction with id string
Cause: Error
Action: Contact Oracle support"

ORA-26761: Standby Redo Logs not available for real time mining
Cause: Standby Redo Logs required for real time mining by downstream capture process were not available.
Action: Check the configuration of Standby Redo Logs and retry the operation at a later time. To start the capture process without real time mining property, reset DOWNSTREAM_REAL_TIME_MINE parameter of the capture process and retry the operation.

ORA-26762: Cannot autogenerate name for parameter string because of the following reason: string
Cause: An error was encountered while attempting to generate a name for a parameter which was passed a NULL value.
Action: If possible, fix the error, otherwise specify the parameter name explicitly.

ORA-26763: invalid file type "string"
Cause: An invalid file type was specified for the ASM file.
Action: Check documentation for valid ASM file types.

ORA-26764: invalid parameter "string" for local capture "string"
Cause: An invalid parameter was specified for the local capture process.
Action: Check documentation for valid parameters.

ORA-26765: invalid parameter "string" for downstream capture "string"
Cause: An invalid parameter was specified for the downstream capture process.
Action: Check documentation for valid parameters.

ORA-26766: Unexpected redo pattern encountered by LogMiner
Cause: d by tables with unsupported data types or newer table features.
Action: Remove the capture rule for the table and restart capture.

ORA-26767: No enough redo log information for LogMiner
Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with UNRECOVERABLE clause was specified for the table.
Action: Remove the capture rule for the table and restart capture.

ORA-26768: Maximum number of unsupported tables exceeded
Cause: An attempt was made to add more than the allowed number of unsupported tables.
Action: Clear the current list of unsupported tables.

ORA-26785: Object has a NULL value
Cause: A method was invoked on a NULL object.
Action: Initialize the object with a non-NULL value.

ORA-26786: A row with key string exists but has conflicting column(s) string in table string
Cause: The row to update or delete exists in the table but had conflicting value for some columns.
Action: For Streams, please define a conflict resolution, or resolve the conflict and execute the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status of the database guard to ensure local modifications are not allowed, then re-instantiate the table and contact support if the problem persists.

ORA-26787: The row with key string does not exist in table string
Cause: The row to update or delete does not exist in the table.
Action: For Streams, please define a conflict resolution, or resolve the conflict and execute the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status of the database guard to ensure local modifications are not allowed, then re-instantiate the table and contact support if the problem persists.

ORA-26788: The column string is not encrypted in the local database.
Cause: The column in the destination database is NOT encrypted while it is encrypted in the source database.
Action: Set the corresponding column property in the destination database to 'encrypted' or change the apply parameter, PRESERVE_ENCRYPTED_COLS, to 'N' to supress the error.

ORA-26789: Cannot split propagation string because only one propagation originates from its source queue "string"."string"
Cause: Only one propagation originated from the propagation source queue.
Action: Please do not split this propagation.

ORA-26790: Requesting a lock on string "string" timed out
Cause: Could not get a lock on the object because another process was holding the lock.
Action: Please try later.

ORA-26791: Cannot split or merge propagation "string"
Cause: A process tried to split or merge this propagation, but failed and left STREAMS in an inconsistent state.
Action: Query DBA_RECOVERABLE_SCRIPT_BLOCKS view, and roll back the script which tried to split or merge this propagation.

ORA-26792: Invalid source database name string
Cause: The value for the source database global name was not valid.
Action: Specify a valid database global name. If the source database is not the local database, check the listener is up and running.

ORA-26793: Number of capture processes that enqueued message to queue "string"."string" not equal to one
Cause: Split-merge API requires only one capture process enqueued message to the queue where the propagation originated
Action: Please drop one capture, or split or merge another propagation.

ORA-26794: Hierarchically enabled tables not supported
Cause: Hierarchically enabled tables are not supported.
Action: Disable hierarchy for the table.

ORA-26800: Apply not the only subscriber for "string"."string".
Cause: The combined capture and apply optimization could not be used since Apply was not the lone subscriber to the queue.
Action: Apply has to be the only subscriber to the queue.

ORA-26801: More than one subscriber for "string"."string".
Cause: The combined capture and apply optimization could not be used since there was more than one subscriber to the queue.
Action: Configure a single subscriber - apply or propagation for the queue.

ORA-26802: Queue "string"."string" has messages.
Cause: The combined capture and apply optimization could not be used since the queue had messages.
Action: Make sure queue is empty before starting apply and capture.

ORA-26803: Subscribers have changed for queue "string"."string".
Cause: The combined capture and apply optimization could not be used since the subscribers had changed.
Action: Optimization can be used only if the queue has a single subscriber.

ORA-26804: Apply "string" is disabled.
Cause: The apply process was disabled or aborted.
Action: Start the apply process.

ORA-26805: Queue "string"."string" has rule based subscribers.
Cause: The combined capture and apply optimization could not be used since the queue had rule based subscribers.
Action: Make sure queue has no rule based subscribers before starting apply and capture.

ORA-26806: Remote database could not support combined capture and apply optimization.
Cause: The remote database has a version lower than Oracle 11.0 and hence does not understand combined capture and apply optimization.
Action: Upgrade the remote database to Oracle 11.0 or above in order to use the combined capture and apply optimization.

ORA-26807: Database link is not NULL for Apply with the name "string" .
Cause: The combined capture and apply optimization could not be used since apply_database_link was not NULL.
Action: Drop and recreate the apply with NULL value for apply_database_link.

ORA-26808: Apply process string died unexpectedly.
Cause: Apply process died unexpectedly.
Action: Check your system for anomalies and restart apply. If this error persists, contact Oracle Support Services. See trace file for more details.

ORA-26809: Capture aborted: checkpoint-free mode requires combined capture and apply mode.
Cause: The requirements for combined capture and apply mode were broken.
Action: Restore the combined capture and apply mode and then restart the capture. If combined capture and apply mode is no longer desired, drop the existing checkpoint-free capture and create another one that will take checkpoints.

ORA-26810: Apply "string" on database "string" is in the mode of combined capture and apply.
Cause: The combined capture and apply optimization could not be used because Apply was already in the mode of combined capture and apply.
Action: Do not configure two captures for one apply.

ORA-26811: Client has already attached to STREAMS apply "string".
Cause: The client has already attached to the specified apply process.
Action: Detach apply process before re-attach.

ORA-26812: Too many sessions currently attached to STREAMS apply "string".
Cause: Only one active external session is allowed per apply process.
Action: More than one active external session attempted to attach to apply process. Wait until there is no active external sessions before attempting to attach again.

ORA-26813: The value for argument "ARRAY_SIZE" is too small
Cause: The value for argument "ARRAY_SIZE" was less than the number of columns in the requested column list.
Action: Check the return value for "NUM_COLUMNS" parameter then allocate all input arrays to at least that size and invoke the same OCI function again.

ORA-26814: The value for argument "string" exceeds maximum string
Cause: The value for specified value exceeded the maximum allowed.
Action: Correct the value of specified argument.

ORA-26815: Error from Apply Network Receiver for Apply "string" and Capture "string".
Cause: The Apply Network Receiver aborted due to an unexpected error.
Action: Query DBA_APPLY_ERROR to determine the error and then restart the Capture and Apply.

ORA-26816: STREAMS apply process "string" (OS id string) is exiting due to
ORA-number.
Cause: An apply process encountered an unexpected error.
Action: Query DBA_APPLY to examine the status of Apply and restart Apply if needed.

ORA-26817: STREAMS capture process "string" is unable to communicate with capture server number during initialization.
Cause: Capture server might not be started properly
Action: Fix any errors during capture server creation and re-start capture process

ORA-26819: STREAMS capture server number for apply "string" and capture "string" encounters disabled/aborted propagation "string".
Cause: Propagation is disabled/aborted
Action: Start propagation

ORA-26820: STREAMS capture server number for apply "string" and propagation "string" becomes active and needs join capture process "string".
Cause: Capture server was waiting for propagation or apply to start
Action: Capture process needs restart (done automatically).

ORA-26821: STREAMS capture server number for apply "string" and capture "string" detects propagation "string" has changed.
Cause: Propagation is dropped/modified.
Action: Capture process needs restart (automatically).

ORA-26822: Failure in creating capture servers (ksv error code number).
Cause: Failure in ksv slave creation.
Action: Identify the actual ksv error and act accordingly.

ORA-26823: STREAMS capture server number is unable to communicate with capture process "string" during initialization.
Cause: Capture process might not be started properly
Action: Fix any errors during capture process creation and re-start capture process

ORA-26824: Client is not attached to STREAMS apply "string".
Cause: An attempt was made to execute OCIXApplyDetach call while not attached to the specified apply process.
Action: Remove detach call.

ORA-26825: STREAMS Apply "string" is not configured as an external apply.
Cause: An attempt was made to attach to a STREAMS apply process, which was not configured as an external apply.
Action: Check the apply name or re-create the apply process as an external apply.

ORA-26826: STREAMS apply coordinator and apply slave are unable to communicate.
Cause: STREAMS Apply process may have died unexpectedly.
Action: Check your system for anomalies and restart apply. If this error persists, contact Oracle Support Services. See trace file for more details.

ORA-26827: Insufficient privileges to attach to STREAMS apply "string".
Cause: Sufficient privileges were not granted to attach to the specified STREAMS apply.
Action: Ask the Streams administrator to perform the operation or grant the required privileges.

ORA-26828: STREAMS external apply "string" requires combined capture and apply mode.
Cause: The specified STREAMS external apply was not in combined capture and apply mode.
Action: Restore the combined capture and apply mode and then restart the capture.

ORA-26829: Cannot set "DISABLE_ON_ERROR" parameter to 'N'.
Cause: An attempt was made to change the "DISABLE_ON_ERROR" parameter for a STREAMS external apply to 'N'.
Action: Remove invalid statement.

ORA-26830: Cannot define handler for a STREAMS external apply.
Cause: An attempt was made to define a handler for a STREAMS external apply.
Action: Remove invalid statement.

ORA-26831: Cannot delete or execute error transaction from STREAMS external apply "string".
Cause: An attempt was made to delete or execute an error transaction from the specified STREAMS external apply.
Action: Remove invalid statement.

ORA-26832: Unable to create STREAMS external apply "string" due to existing handler.
Cause: An attempt was made to create the specified STREAMS external apply while there was a handler defined for the specified apply.
Action: Use DBMS_APPLY_ADM.SET_DML_HANDLER procedure to remove all handlers defined on the specified apply then retry statement.

ORA-26850: STREAMS capture process detects queue subscribers been changed.
Cause: The subscribers for capture queue have changed.
Action: Capture process should restart

ORA-26851: Unable to connect to apply "string" because it has connected to another capture.
Cause: Another capture process is already connected to apply.
Action: Wait for the connected capture process to terminate or abort the connected capture process.

ORA-26852: Invalid NULL value for column_value parameter.
Cause: NULL is not allowed to be passed as the column value.
Action: Replace NULL with a proper AnyData instance containing NULL, e.g., sys.AnyData.ConvertVarchar2(NULL), as the column value if the column value is NULL.

ORA-26853: invalid cca maximum percentage string
Cause: Specified percentage value was not in range 0 - 100.
Action: Specify a percentage value in the range 0 - 100.

ORA-26854: STREAMS string has no enqueue or dequeue privileges to the queue.
Cause: The STREAMS user did not have enqueue or dequeue privilege to the queue.
Action: Grant STREAMS user enqueue or dequeue privileges to the queue.

ORA-26855: STREAMS string has insufficient database privilege to access the queue.
Cause: The STREAMS user did not have sufficient database privilege to access the queue.
Action: Grant STREAMS user database privileges to access the queue.

ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
Cause: sbtinit returned an error, additional information indicates error
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27001: unsupported device type
Cause: the specified device type is supported on this platform
Action: check V$BACKUP_DEVICE for supported device types

ORA-27002: function called with invalid device structure
Cause: internal error, aditional information indicates which function encountered error
Action: check for trace file and contact Oracle Support

ORA-27003: cannot open file on device allocated with NOIO option
Cause: internal error, a file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error
Action: check for trace file and contact Oracle Support

ORA-27004: invalid blocksize specified
Cause: internal error, blocksize specified is incorrect for the device on which file is being created, aditional information indicates blocksize specified, and the function that encountered the error
Action: check for trace file and contact Oracle Support

ORA-27005: cannot open file for async I/O on device not supporting async
Cause: internal error, a file is being opened for async I/O on a device that does not support async I/O, additional information indicates which function encountered error
Action: check for trace file and contact Oracle Support

ORA-27006: sbtremove returned error
Cause: additional information indicates error returned by sbtremove, and the function that encountered the error
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27007: failed to open file
Cause: sbtopen returned error, additional information indicates error returned from sbtopen, and the function that encountered the error
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27008: function called with invalid file structure
Cause: internal error, aditional information indicates which function encountered error
Action: check for trace file and contact Oracle Support

ORA-27009: skgfwrt: cannot write to file opened for read
Cause: internal error
Action: check for trace file and contact Oracle Support

ORA-27010: skgfwrt: write to file failed
Cause: sbtwrite returned error, additional information indicates error returned from sbtwrite
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27011: skgfrd: cannot read from file opened for write
Cause: internal error
Action: check for trace file and contact Oracle Support

ORA-27012: skgfrd: read from file failed
Cause: sbtread returned error, additional information indicates error returned from sbtread
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27013: skgfqdel: cannot delete an open file
Cause: internal error
Action: check for trace file and contact Oracle Support

ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR
Cause: Failure of sltln in skgfqpini
Action: Check additional return error for more information.

ORA-27015: skgfcls: failed to close the file
Cause: sbtclose returned error, additional information indicates error returned from sbtclose
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27016: skgfcls: sbtinfo returned error
Cause: additional information indicates error returned from sbtinfo
Action: verify that vendor's storage subsystem product is operating correctly

ORA-27017: skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
Cause: media handle string length exceeds SSTMXQMH
Action: verify that vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is atleast 64 (the limit specified for sbtinfo). additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH)

ORA-27018: BLKSIZE is not a multiple of the minimum physical block size
Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.
Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.

ORA-27019: tape filename length exceeds limit (SBTOPMXF)
Cause: length of tape filename provided to sequential I/O OSD functions is too long
Action: additional information indicates in which function this error is encountered, the length of filename provided, and the limit on filename

ORA-27020: named devices not supported
Cause: the platform or the specified device type does not support named devices
Action: do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available.

ORA-27021: sequential file handle must be specified
Cause: The filename which will be passed to sbtopen was not specified.
Action: Specify a filename and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name.

ORA-27022: skgfqsbi: could not allocate memory for media manager
Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services.
Action: Increase the amount of memory available to the Oracle process and retry the backup/restore.

ORA-27023: skgfqsbi: media manager protocol error
Cause: The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle.
Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27024: skgfqsbi: sbtinit2 returned error
Cause: sbtinit2 returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27025: skgfqsbi: invalid media manager context area size
Cause: The media management software requested a context area size which is greater than the maximum allowable size.
Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27026: skgfrls: sbtend returned error
Cause: sbtend returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27027: sbtremove2 returned error
Cause: sbtremove2 returned an error. This happens when deleting a backup file.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27028: skgfqcre: sbtbackup returned error
Cause: sbtbackup returned an error. This happens when creating a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27029: skgfrtrv: sbtrestore returned error
Cause: sbtrestore returned an error. This happens when retrieving a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27030: skgfwrt: sbtwrite2 returned error
Cause: sbtwrite2 returned an error. This happens while writing a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27031: mirror resilvering functions not supported
Cause: internal error
Action: check for trace file and contact Oracle Support

ORA-27032: failed to obtain file size limit
Cause: getrlimit system call returned an error
Action: check errno

ORA-27033: failed to obtain file size limit
Cause: ulimit system call returned an error
Action: check errno

ORA-27034: maximum length of ORACLE_SID exceeded
Cause: too many characters in the ORACLE_SID string
Action: rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system

ORA-27035: logical block size is invalid
Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum
Action: block size specified is returned as additional information, check init.ora parameters, additional information also indicates which function encountered the error

ORA-27036: translation error, unable to expand file name
Cause: additional information indicates sltln/slnrm error, and also indicates which function encountered the error
Action: check additional information

ORA-27037: unable to obtain file status
Cause: stat system call returned an error, additional information indicates which function encountered the error
Action: check errno

ORA-27038: created file already exists
Cause: trying to create a database file, but file by that name already exists
Action: verify that name is correct, specify reuse if necessary

ORA-27039: create file failed, file size limit reached
Cause: an attempt was made to create a file that exceeds the process's file size limit, additional information indicates which function encountered the error
Action: raise the file size limit

ORA-27040: file create error, unable to create file
Cause: create system call returned an error, unable to create file
Action: verify filename, and permissions

ORA-27041: unable to open file
Cause: open system call returned an error, additional information indicates which function encountered the error
Action: check errno

ORA-27042: not enough space on raw partition to fullfill request
Cause: internal error, file too large for raw partition, additional information indicates which function encountered the error
Action: check for trace file and contact Oracle Support

ORA-27043: unable to seek to beginning of file
Cause: seek system call failed, additional information indicates which function encountered the error
Action: check errno

ORA-27044: unable to write the header block of file
Cause: write system call failed, additional information indicates which function encountered the error
Action: check errno

ORA-27045: unable to close the file
Cause: close system call failed, additional information indicates which function encountered the error
Action: check errno

ORA-27046: file size is not a multiple of logical block size
Cause: file size as indicated by stat is not correct, additional information indicates which function encountered the error
Action: verify that the file has not been overwritten or truncated

ORA-27047: unable to read the header block of file
Cause: read system call failed, additional information indicates which function encountered the error
Action: check errno

ORA-27048: skgfifi: file header information is invalid
Cause: possibly trying to use a non-database file as a database file
Action: verify that file is a database file

ORA-27049: unable to seek to and read the last block
Cause: an attempt was made to seek to and read the last block in file, additional information indicates which function encountered error
Action: check errno

ORA-27050: function called with invalid FIB/IOV structure
Cause: internal error, aditional information indicates which function encountered error
Action: check for trace file and contact Oracle Support

ORA-27052: unable to flush file data
Cause: fsync system call returned error, additional information indicates which function encountered the error
Action: check errno

ORA-27053: blocksize in file header not a multiple of logical block size
Cause: the logical block size is invalid, additional information indicates the logical block size and the blocksize in the file header
Action: use a different logical block size, or do not reuse file

ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Cause: The file was on an NFS partition and either reading the mount tab file failed or the partition wass not mounted with the correct mount option.
Action: Make sure mount tab file has read access for Oracle user and the NFS partition where the file resides is mounted correctly. For the list of mount options to use refer to your platform specific documentation.

ORA-27056: could not delete file
Cause: unlink system call returned error
Action: check errno

ORA-27057: cannot perform async I/O to file
Cause: internal error, query is being asked about async vector I/O when the file does not support async I/O
Action: check for trace file and contact Oracle Support

ORA-27058: file I/O question parameter is invalid
Cause: internal error, invalid query is being asked
Action: check for trace file and contact Oracle Support

ORA-27059: could not reduce file size
Cause: ftruncate system call returned error
Action: check errno

ORA-27060: could not set close-on-exec bit on file
Cause: fcntl system call returned error
Action: check errno

ORA-27061: waiting for async I/Os failed
Cause: aiowait function returned error
Action: check errno

ORA-27062: could not find pending async I/Os
Cause: There should have been some async I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be either because of an Oracle bug or the vendor OS bug or due to a NFS server not responding
Action: check Oracle trace file, OS message files and contact Oracle Support

ORA-27063: number of bytes read/written is incorrect
Cause: the number of bytes read/written as returned by aiowait does not match the original number, additional information indicates both these numbers
Action: check errno

ORA-27064: cannot perform async I/O to file
Cause: internal error, asked to perform async I/O when IOV indicates that it cannot be performed on the file
Action: check for trace file and contact Oracle Support

ORA-27065: cannot perform async vector I/O to file
Cause: internal error, asked to perform async vector I/O when it cannot be performed on the file
Action: check for trace file and contact Oracle Support

ORA-27066: number of buffers in vector I/O exceeds maximum
Cause: internal error, number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers
Action: check for trace file and contact Oracle Support

ORA-27067: size of I/O buffer is invalid
Cause: internal error, buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size
Action: check for trace file and contact Oracle Support

ORA-27068: I/O buffer is not aligned properly
Cause: internal error, buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer
Action: check for trace file and contact Oracle Support

ORA-27069: attempt to do I/O beyond the range of the file
Cause: internal error, the range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file
Action: check for trace file and contact Oracle Support

ORA-27070: async read/write failed
Cause: aioread/aiowrite system call returned error, additional information indicates starting block number of I/O
Action: check errno

ORA-27071: unable to seek to desired position in file
Cause: lseek system call returned error, additional information indicates block number in file to which seek was attempted
Action: check errno

ORA-27072: File I/O error
Cause: read/write/readv/writev system call returned error, additional information indicates starting block number of I/O
Action: check errno

ORA-27073: Trying to close a file which has async I/Os pending to be dequeued
Cause: internal error, the file is being closed but not all async I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file
Action: check for trace file and contact Oracle Support

ORA-27074: unable to determine limit for open files
Cause: The getrlimit() system call returned an error.
Action: Check errno.

ORA-27075: SSTMOFRC constant too large
Cause: internal error
Action: check for trace file and contact Oracle Support

ORA-27076: unable to set limit for open files
Cause: The setrlimit() system call returned an error.
Action: Check errno.

ORA-27077: too many files open
Cause: internal error, the number of files opened through skgfofi has reached the limit
Action: Check for trace file and contact Oracle Support.

ORA-27078: unable to determine limit for open files
Cause: The getrlimit() system call returned an error.
Action: Check errno.

ORA-27079: unable to set async IO limit
Cause: The setting of the limit for async I/O has failed.
Action: Check errno.

ORA-27080: too many files open
Cause: The number of files opened has reached the system limit.
Action: Check the error, and set system configuration values.

ORA-27081: unable to close the file
Cause: The close() system call failed.
Action: Check errno.

ORA-27083: waiting for async I/Os failed
Cause: The aio_waitn() library call returned an error.
Action: Check errno.

ORA-27084: unable to get/set file status flags
Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error.
Action: Check errno.

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.
Action: determine which database instance legitimately owns this file.

ORA-27087: unable to get share lock - file not readable
Cause: share lock request was made on a file not open for read access.
Action: file must be open read-only or read-write to get a share lock.

ORA-27088: unable to get file status
Cause: file not open or file descriptor is invalid.
Action: None

ORA-27089: unable to release advisory lock
Cause: release of file lock failed
Action: see errno

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.
Action: Check errno

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
Action: check errno

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)
Action: increase the processes file size limit (ulimit) and retry

ORA-27093: could not delete directory
Cause: rmdir system call returned error
Action: check errno

ORA-27094: raw volume used can damage partition table
Cause: A raw device with VTOC information was provided as a database file.
Action: Make sure the disk partition that is provided to Oracle does not start at sector 0

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
Action: Use a different instance name, or cleanup the failed instance's SGA

ORA-27101: shared memory realm does not exist
Cause: Unable to locate shared memory realm
Action: Verify that the realm is accessible

ORA-27102: out of memory
Cause: Out of memory
Action: Consult the trace file for details

ORA-27103: internal error
Cause: internal error
Action: contact Oracle support

ORA-27120: unable to removed shared memory segment
Cause: shmctl() call failed
Action: check permissions on segment, contact Oracle support

ORA-27121: unable to determine size of shared memory segment
Cause: shmctl() call failed
Action: check permissions on segment, contact Oracle support

ORA-27122: unable to protect memory
Cause: mprotect() call failed
Action: contact Oracle support

ORA-27123: unable to attach to shared memory segment
Cause: shmat() call failed
Action: check permissions on segment, contact Oracle support

ORA-27124: unable to detach from shared memory segment
Cause: shmdt() call failed
Action: contact Oracle support

ORA-27125: unable to create shared memory segment
Cause: shmget() call failed
Action: contact Oracle support

ORA-27126: unable to lock shared memory segment in core
Cause: insufficient privileges to lock shared memory segment in core
Action: make sure process is running with necessary privileges.

ORA-27127: unable to unlock shared memory segment
Cause: insufficient privileges to unlock shared memory segment
Action: make sure process is running with necessary privileges.

ORA-27128: unable to determine pagesize
Cause: sysconf() call failed
Action: contact Oracle support

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.
Action: Check for additional errors and contact Oracle Support.

ORA-27141: invalid process ID
Cause: process operation attempted using invalid process ID
Action: contact Oracle Support

ORA-27142: could not create new process
Cause: OS system call
Action: check errno and if possible increase the number of processes

ORA-27143: OS system call failure
Cause: OS system call failed
Action: check errno and contact Oracle support

ORA-27144: attempt to kill process failed
Cause: OS system call error
Action: check errno and contact Oracle Support

ORA-27145: insufficient resources for requested number of processes
Cause: OS system call error
Action: check errno and contact Oracle Support

ORA-27146: post/wait initialization failed
Cause: OS system call failed
Action: check errno and contact Oracle Support

ORA-27147: post/wait reset failed
Cause: OS system call failed
Action: check errno and contact Oracle Support

ORA-27148: spawn wait error
Cause: OS system call failed
Action: check errno and contact Oracle Support

ORA-27149: assignment out of range
Cause: internal error, requested conversion too large for type
Action: contact Oracle Support

ORA-27150: attempt to notify process of pending oradebug call failed
Cause: OS system call
Action: check errno contact Oracle Support

ORA-27151: buffer not large enough to hold process ID string
Cause: internal error
Action: contact Oracle Support

ORA-27152: attempt to post process failed
Cause: OS system call failed
Action: check errno and contact Oracle Support

ORA-27153: wait operation failed
Cause: OS system called failed
Action: check errno contact Oracle Support

ORA-27154: post/wait create failed
Cause: internal error, multiple post/wait creates attempted simultaneously
Action: check errno and contact Oracle Support

ORA-27155: could not execute file
Cause: OS system call failed
Action: check errno and contact Oracle Support

ORA-27156: request for process information failed
Cause: internal error
Action: contact Oracle Support

ORA-27157: OS post/wait facility removed
Cause: the post/wait facility for which the calling process is awaiting
Action: check errno and contact Oracle Support

ORA-27158: process control failure
Cause: Oracle was unable to set the specified process control.
Action: Consult the Oracle Administrator's Guide.

ORA-27159: failure setting process scheduling priority
Cause: Oracle was unable to set the scheduling priority desired.
Action: Consult the Oracle Administrator's Guide.

ORA-27160: process requested to perform operation
Cause: The current process was requested to perform an operation by another process.
Action: This is used internally; no action is required.

ORA-27161: request for Oracle binary information failed
Cause: The program was unable to get information about the Oracle binary.
Action: Check for additional errors and contact Oracle support.

ORA-27162: thread creation failed
Cause: The program was unable to create a thread.
Action: Check errno and contact Oracle support.

ORA-27163: out of memory
Cause: The program ran out of memory when allocating a temporary data structure.
Action: Increase the amount of memory on the system.

ORA-27164: tried to join detached thread
Cause: The program tried to join a detached thread.
Action: This is an internal error; contact Oracle support.

ORA-27165: tried to join thread that does not exist
Cause: The program tried to join a thread that does not exist.
Action: This is an internal error; contact Oracle support.

ORA-27166: tried to join current thread
Cause: A thread in the program tried to join itself.
Action: This is an internal error; contact Oracle support.

ORA-27167: Attempt to determine if Oracle binary image is stored on remote server failed
Cause: OS dependent operation failed
Action: None

ORA-27190: skgfrd: sbtread2 returned error
Cause: sbtread returned an error. This happens while reading a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27191: sbtinfo2 returned error
Cause: sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager's catalog.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
Cause: sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27193: sbtinfo2 did not return volume label
Cause: sbtinfo2 did not return the volume label information for the backup file that was just created.
Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27194: skgfdvcmd: sbtcommand returned error
Cause: sbtcommand returned an error. This happens when an rman SEND command is issued.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27195: proxy copy not supported
Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.
Action: Re-run the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy.

ORA-27196: skgfpbk: sbtpcbackup returned error
Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27197: skgfprs: sbtpcrestore returned error
Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27198: skgfpvl: sbtpcvalidate returned error
Cause: sbtpcvalidate returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27199: skgfpst: sbtpcstatus returned error
Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27200: skgfpgo: sbtpcstart returned error
Cause: sbtpcstart returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27201: skgfpcm: sbtpccommit returned error
Cause: sbtpccommit returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27202: skgfpen: sbtpcend returned error
Cause: sbtpcend returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27203: skgfpqb: sbtpcquerybackup returned error
Cause: sbtpcquerybackup returned an error. This happens during a proxy backup.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27204: skgfpqr: sbtpcqueryrestore returned error
Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27205: skgfpcn: sbtpccancel returned error
Cause: sbtpccancel returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27206: requested file not found in media management catalog
Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.
Action: Retry the command with a different file.

ORA-27207: syntax error in device PARMS - parentheses mismatch or missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

ORA-27208: syntax error in device PARMS - environment variable value missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..)

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.
Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

ORA-27210: syntax error in device PARMS
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

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.
Action: Retry the command with proper media library. Or re-install Media management module for Oracle.

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
Action: Retry the command with proper media library.

ORA-27213: failed to unload Media Management Library
Cause: dlclose for media library returned error. See Additional Additional information for error code.
Action: contact Oracle Support.

ORA-27214: skgfrsfe: file search failed
Cause: The FindNextFile function returned unxpected error.
Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.

ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file
Cause: During an sbtinfo2() call, the media management software returned information about an unknown backup file.
Action: Contact the media management vendor.

ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response
Cause: The media management software returned a malformed response during an sbtinfo2() call.
Action: Contact the media management vendor.

ORA-27217: failed to load Media Management Library from secure location
Cause: SBT libraries were not installed in a secure location.
Action: Remove SBT_SECURE parameter or Request third party vendors to provide patch that installs SBT libraries in secured locations as mandated by Oracle.

ORA-27230: OS system call failure
Cause: OS system call failed
Action: check errno and contact Oracle support

ORA-27250: OS system call failure
Cause: OS system call failed
Action: check errno and contact Oracle support

ORA-27300: OS system dependent operation:string failed with status: string
Cause: OS system call error
Action: contact Oracle Support

ORA-27301: OS failure message: string
Cause: OS system call error
Action: contact Oracle Support

ORA-27302: failure occurred at: string
Cause: OS system call error
Action: contact Oracle Support

ORA-27303: additional information: string
Cause: OS system call error
Action: contact Oracle Support

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.
Action: Resolve the conflict by changing the value of one of the attributes and issue the call again.

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.
Action: Issue the call again with the required attribute set.

ORA-27354: attribute string cannot be set for lightweight jobs
Cause: The CREATE_JOBS call or the JOB object constructor was called with an argument that is illegal in the case of lightweight jobs.
Action: Set the argument to the default value and issue the call again.

ORA-27356: invalid job argument
Cause: An invalid job argument was passed into either the CREATE_JOBS call or the JOB object constructor.
Action: Correct the argument value and issue the call again.

ORA-27357: duplicate reference to job object string
Cause: The scheduler CREATE_JOBS call had two or more references to the same job.
Action: Eliminate the duplicate references and issue the call again.

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.
Action: Eliminate the duplicate references and issue the call again.

ORA-27361: scheduler API invoked with illegal or inconsistent arguments
Cause: A DBMS_SCHEDULER API call was invoked with either illegal or inconsistent arguments.
Action: Refer to scheduler documentation for the call, make the necessary changes and issue the call again.

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.
Action: Check the view SCHEDULER_JOB_ERRORS to see which commands failed and why. Make the appropriate corrections and submit the failed commands again.

ORA-27363: invalid program for lightweight job
Cause: You tried to create a lightweight job using an invalid program. A program used in a lightweight 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.
Action: Use a valid program for the lightweight job.

ORA-27364: remote database string already registered as string
Cause: The user attempted to register a remote database that was already registered.
Action: To update the registration information, the REPLACE argument of the REGISTER_REMOTE_DATABASE procedure should be set to TRUE. If the registration information is already current, no further action is needed.

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.
Action: No action is required for the job to be stopped, but calling stop_job with force (if you have the privilege) may cause the job to be stopped sooner.

ORA-27366: job "string.string" is not running
Cause: An attempt was made to stop a job that was not running.
Action: Verify the status of the job. If the job is running but this message is still being returned, contact Oracle support.

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.
Action: Reenable the program before running the job.

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.
Action: Correct the cause of the exit code and reschedule the job.

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.
Action: Correct the problem specified in the error stack and reschedule the job.

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.
Action: Switch to a different platform or create a different type of job or program.

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.
Action: Reduce the total length by specifying fewer and/or shorter arguments

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.
Action: Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues.

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.
Action: The job owner has to have dequeue privileges on event source queue or he has to have manage queue or dequeue any queue system privileges. Make sure one of these privileges is granted.

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.
Action: If no agent name was specified, retry the call with a valid agent name. If the agent name was valid, check if the agent is currently subscribed to the queue and, in the case of jobs, check is the agent has been authorized to act as the job owner.

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.
Action: Pass in a legal event condition.

ORA-27377: windows cannot have event based schedules
Cause: Event based schedules for windows are currently not supported.
Action: Use a time-based schedule instead.

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.
Action: If the attempt to stop the job was made with the FORCE option set to FALSE, try again but change the FORCE option to TRUE.

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.
Action: Change the value of the INSTANCE_ID attribute or place the job in a job class whose settings do not conflict with the INSTANCE_ID attribute. Then re-enable the job.

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.
Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or create another job in a schema which does have the CREATE EXTERNAL JOB system privilege.

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.
Action: Specify a valid repeat interval, e.g., 'FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0' for a job that executes daily at 8am.

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.
Action: Correct the repeat interval such that it no longer contains the invalid keyword.

ORA-27413: repeat interval is too long
Cause: The repeat interval consisted of a calendar string larger than the maximum size allowed.
Action: Use a shorter calendar string for the repeat interval.

ORA-27414: Invalid BY value type
Cause: The type of BY value was not allowed for the frequency specified
Action: Ommit BY values of this type or alter the frequency

ORA-27415: repeat interval or calendar must start with the FREQ= clause
Cause: The specified calendar string for the repeat interval did not start with the frequency clause.
Action: Create a repeat interval that starts with a frequency clause, e.g. 'FREQ=YEARLY;BYMONTH=FEB'

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 doesn't properly represent a weekday.
Action: Use the correct three letter abbreviations for weekdays, e.g. MON for Monday and FRI for Friday.

ORA-27417: BYWEEKNO clause is only supported when FREQ=YEARLY
Cause: A repeat interval or calendar contained a BYWEEKNO clause with a frequency other than yearly.
Action: Remove the BYWEEKNO clause or change the frequency to yearly.

ORA-27418: syntax error in repeat interval or calendar
Cause: The repeat interval or calendar definition could not be recognized as a valid syntax.
Action: Specify a valid repeat interval.

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.
Action: Remove the conflicting clauses, or simplify the repeat interval so that it is easier to determine the next execution date.

ORA-27421: usage of string not supported in a calendar definition
Cause: The calendar definition contained a clause that is specific for a repeat interval
Action: Specify a valid calendar definition.

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.
Action: Modify the rule set directly using the dbms_rule_adm package or create another chain without specifying a rule set.

ORA-27432: step string does not exist for chain string.string
Cause: The step specified does not exist for the given chain.
Action: Reissue the command using a step that exists for this 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.
Action: Wait until the step has finished running.

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.
Action: Stop or drop the chain step job or alter the running chain step instead.

ORA-27435: chain job terminated abnormally
Cause: A chain job has ended abnormally. The error code for the running chain could not be retrieved.
Action: No action necessary. The job will run again when it is scheduled to.

ORA-27451: string cannot be NULL
Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL.
Action: Reissue the command using a non-NULL value for the specified attribute.

ORA-27452: string is an invalid name for a database object.
Cause: An invalid name was used to identify a database object.
Action: Reissue the command using a valid name.

ORA-27453: string is an invalid job or program argument name.
Cause: An invalid job or program argument name was specified.
Action: Reissue the command using a valid name for this argument.

ORA-27454: argument name and position cannot be NULL
Cause: The name or position of a program or job argument was defined as NULL.
Action: Reissue the command providing either a valid argument name or valid argument position.

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.
Action: Reissue the command, leaving out the schema name or using the schema name of SYS.

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.
Action: Define as many arguments as the number of arguments, or change the number of arguments.

ORA-27457: argument string of job "string.string" has no value
Cause: No value was provided for the job argument with the specified position.
Action: Provide a value for the job argument using any of the set_job_xxxx_value() routines. Or, when using a named program, specify a default value for the corresponding argument of the program.

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.
Action: Change the number of arguments to zero, or change the type of the program.

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.
Action: Change the arguments to be of character-only datatypes.

ORA-27460: cannot execute disabled job "string.string"
Cause: An attempt was made to run a job that is disabled.
Action: Enable the job and then reschedule the job.

ORA-27461: The value for attribute string is too large.
Cause: The value that was provided for the specified attribute was too large.
Action: Reissue the command using a smaller or shorter value.

ORA-27463: invalid program type string
Cause: An invalid program type was specified.
Action: Reissue the command using a valid program type.

ORA-27464: invalid schedule type string
Cause: An invalid schedule type was specified.
Action: Reissue the command using a valid schedule type.

ORA-27465: invalid value string for attribute string
Cause: An invalid value was provided for the specified attribute.
Action: Reissue the command using a valid value for this attribute.

ORA-27467: invalid datatype for string value
Cause: The value provided for the named scheduler attribute was of an invalid datatype.
Action: Reissue the command using a value of the correct 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.
Action: Retry the operation. Scheduler locks are held for a very short duration. If the error persists, contact Oracle Support.

ORA-27469: string is not a valid string attribute
Cause: A non-existant attribute was specified.
Action: Reissue the command using a valid attribute for that specific scheduler object.

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.
Action: Alter the object so that it becomes valid and then enable it.

ORA-27471: window "string.string" is already closed
Cause: An attempt was made to close a window that was not open.
Action: No action required.

ORA-27472: invalid metadata attribute string
Cause: An invalid metadata attribute was specified.
Action: Reissue the command using a valid metadata attribute.

ORA-27473: argument string does not exist
Cause: An argument which was specified does not exist.
Action: Reissue the command using an argument name defined by the program or using a valid argument position.

ORA-27474: cannot give both an argument name and an argument position
Cause: An argument was specified using both a name and a position.
Action: Reissue the command using either the argument name or the argument position but not both.

ORA-27475: "string.string" must be a string
Cause: An object of the wrong type was specified. For example, a table could have been passed to the drop_job() procedure.
Action: Reissue a different command applicable to this object type or reissue the same command using an object of the valid type.

ORA-27476: "string.string" does not exist
Cause: A database object was specified that does not exist.
Action: Reissue the command using an object that exists or create a new object and then reissue this command.

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.
Action: Reissue the command using a different name or schema.

ORA-27478: job "string.string" is running
Cause: An attempt was made to drop a job that is currently running.
Action: Stop the job and then reissue the command, or reissue the command specifying the force option to stop the job first.

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.
Action: Alter the associated jobs so they do not point to the scheduler object being dropped or disabled and then reissue the command. Alternatively reissue the command specifying the force option. If the force option is specified and a scheduler object is being dropped, all associated jobs will be disabled.

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.
Action: Close the window that is open and then reissue the command, or reissue the command while setting the force option to TRUE.

ORA-27481: "string.string" has an invalid schedule
Cause: An attempt was made to enable a job or window that has an invalid schedule.
Action: Alter the schedule of the job or window so that it is valid and then reissue the enable command.

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.
Action: Alter the job or window so that the end date becomes valid (possibly null) and then reissue the command.

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.
Action: Use argument position instead of name and then issue the command again.

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.
Action: Use a different name for the argument or drop or alter the argument which already exists with this name and then reissue the command.

ORA-27486: insufficient privileges
Cause: An attempt was made to perform a scheduler operation without the required privileges.
Action: Ask a sufficiently privileged user to perform the requested operation, or grant the required privileges to the proper user(s).

ORA-27487: invalid object privilege for a string
Cause: The granted object privilege is not valid for the specified scheduler object.
Action: Check the scheduler documentation to verify which object privileges can be granted on which scheduler objects.

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.
Action: Set the other conflicting attributes to NULL and then reissue the command.

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.
Action: Resolve the error for this job and then reissue the command. See the next error message on the stack to find out what the error for the job is.

ORA-27490: cannot open disabled window "string.string"
Cause: The user tried to open a disabled window.
Action: Enable the window and then try to open it again.

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.
Action: If either repeat_interval or start_date is set to equal NULL, the other should be set to a non-NULL value.

ORA-27500: inter-instance IPC error
Cause: This is an operating system/cluster interconnect error.
Action: Check the extra information and contact Oracle Support Services.

ORA-27501: IPC error creating a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27502: IPC error deleting OSD context
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27503: IPC error attempting to cancel request
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27504: IPC error creating OSD context
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27505: IPC error destroying a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27506: IPC error connecting to a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27507: IPC error disconnecting from a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27508: IPC error sending a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27509: IPC error receiving a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27510: IPC error waiting for a request to complete
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27512: IPC error posting a process
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27513: parameter string contains invalid value string
Cause: The program could not identify the value as an IP address.
Action: Change the value to be a valid IP address.

ORA-27542: Failed to unprepare a buffer prepared for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27543: Failed to cancel outstanding IPC request
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27544: Failed to map memory region for export
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27545: Fail to prepare buffer for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27546: Oracle compiled against IPC interface version string.string found version string.string
Cause: A misconfiguration or installation error occurred.
Action: Install the IPC library for this release of Oracle.

ORA-27547: Unable to query IPC OSD attribute string
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle support Services.

ORA-27548: Unable to unprepare IPC buffer
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle support Services.

ORA-27550: Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number
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.
Action: Check additional error messages in the alert log and the process trace file.

ORA-27601: Cell storage initialization failed, cell library error code [string]
Cause: Cell storage client did not succeed in initializing.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27602: Failure to publish network status information, cell library error code [string]
Cause: Network status information publishing failed.
Action: Check the value of errno and contact Oracle Support Services.

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.
Action: Check the value of errno and contact Oracle Support Services.

ORA-27604: Cell storage ioctl error, ioctl failed on disk string
Cause: Ioctl operation on a cell storage disk failed.
Action: Check the value of errno and contact Oracle Support Services.

ORA-28000: the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account
Action: Wait for PASSWORD_LOCK_TIME or contact DBA

ORA-28001: the password has expired
Cause: The user's account has expired and the password needs to be changed
Action: change the password or contact the DBA

ORA-28002: the password will expire within string days
Cause: The user's account is about to about to expire and the password needs to be changed
Action: change the password or contact the DBA

ORA-28003: password verification for the specified password failed
Cause: The new password did not meet the necessary complexity specifications and the password_verify_function failed
Action: Enter a different password. Contact the DBA to know the rules for choosing the new password

ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument
Action: Check the manual to find out the format of the password verification function

ORA-28005: invalid logon flags
Cause: The flags are not properly set or conflicting flags are set in making calls
Action: Call the function with appropriate flags set.

ORA-28006: conflicting values for parameters string and string
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set
Action: Set one value to UNLIMITED explicitly

ORA-28007: the password cannot be reused
Cause: The password cannot be reused for the specified number of days or for the specified nunmber of password changes
Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement

ORA-28008: invalid old password
Cause: old password supplied is wrong; Hence user cannot be authenticated using old password
Action: Supply the correct old password for authentication

ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Cause: connect SYS/ is no longer a valid syntax
Action: Try connect SYS/ as SYSDBA or connect SYS/ as SYSOPER

ORA-28010: cannot expire external or global accounts
Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired
Action: Try to expire the password of the user that has database password

ORA-28011: the account will expire soon; change your password now
Cause: The user's account is marked for expiry; the expiry period is unlimited.
Action: Change the password or contact the DBA.

ORA-28012: Manual commit not allowed here
Cause: An attempt was made to commit a non-autonomous transaction from within a change password trigger or password verification routine
Action: Remove the COMMIT from the password trigger or password verification routine

ORA-28020: IDENTIFIED GLOBALLY already specified
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.

ORA-28021: cannot grant global roles
Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.
Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority.

ORA-28022: cannot grant external roles to global user or role
Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles.
Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee.

ORA-28023: must revoke grants of this role to other user(s) first
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role.
Action: Use REVOKE to revoke the role from other users or roles first.

ORA-28024: must revoke grants of external roles to this role/user
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted - these must be revoked, since external roles cannot be granted to global users or roles.
Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed.

ORA-28025: missing or null external name
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
Action: Provide a valid external name.

ORA-28026: user with same external name already exists
Cause: The external name specified for the user being created or altered already exists for another user.
Action: External names must be unique among users. Specify another.

ORA-28027: privileged database links may be used by global users
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
Action: Either change the user to a global user or try to use a different database link.

ORA-28028: could not authenticate remote server
Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.
Action: Consult the network security service documentation on how to properly configure the remote server.

ORA-28029: could not authorize remote server for user string
Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.
Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access.

ORA-28030: Server encountered problems accessing LDAP directory service
Cause: Unable to access LDAP directory service
Action: Please contact your system administrator

ORA-28031: maximum of string enabled roles exceeded
Cause: The user attempted to enable too many roles.
Action: Enable fewer roles.

ORA-28035: Cannot Get Session Key for Authentication
Cause: Client and server cannot negotiate shared secret during logon
Action: User should not see this error. Please contact your system administrator

ORA-28037: Cannot Get Session Key for RACF Authentication
Cause: Client and server cannot negotiate shared secret during logon
Action: User should not see this error. Please contact your system administrator

ORA-28038: disallow O2LOGON
Cause: turn off O2LOGON
Action: None

ORA-28039: cannot validate Kerberos service ticket
Cause: The Kerberos service ticket provided was invalid or expired
Action: Provide a valid, unexpired service ticket.

ORA-28040: No matching authentication protocol
Cause: No acceptible authentication protocol for both client and server
Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter on both client and servers to values that matches the minimum version supported in the system.

ORA-28041: Authentication protocol internal error
Cause: Authentication protocol failed with an internal error
Action: None

ORA-28042: Server authentication failed
Cause: Server failed to authenticate itself to the client
Action: Confirm that the server is a valid database server.

ORA-28043: invalid bind credentials for DB-OID connection
Cause: The Database password stored in the wallet did not match the one in OID .
Action: Use DBCA to reset the database password so that it is the same in database wallet and in OID.

ORA-28044: unsupported directory type
Cause: The database tried to work with a directory which is not OID.
Action: Enterprise User Security works only with Oracle Internet Directory. Update the ldap.ora file to reflect an appropriate OID.

ORA-28045: SSL authentication between database and OID failed
Cause: Server failed to authenticate itself to the Directory.
Action: Make sure the sqlnet.ora used is pointing to the wallet with the right certificate.

ORA-28046: Password change for SYS disallowed
Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS password changes.
Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or NONE.

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.
Action: An administrator should put the database into an enterprise domain in OID, and then the user should reconnect.

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.
Action: An administrator should put the database into only one enterprise domain in OID, and then the user should reconnect.

ORA-28049: the password has expired
Cause: The enterprise user's password has expired and the password needs to be changed.
Action: change the password in the directory or contact the directory administrator.

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.
Action: Contact the directory administrator.

ORA-28052: the account is disabled
Cause: The enterprise user's account in the directory has been disabled.
Action: Contact the directory administrator.

ORA-28053: the account is inactive
Cause: The enterprise user's account in the directory is currently not active.
Action: Contact the directory administrator.

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.
Action: change the password in the directory or contact the directory administrator.

ORA-28055: the password will expire within string days
Cause: The enterprise user's password is about to expire.
Action: Change the password in the directory or contact the directory administrator.

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.
Action: Check the error number for a possible operating system error. If there is no error, contact Oracle Support Services.

ORA-28100: policy function schema string is invalid
Cause: The schema was dropped after the policy associated with the function had been added to the object.
Action: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user.

ORA-28101: policy already exists
Cause: A policy with the same name for the same object already exists.
Action: Check if the policy has already been added or use a different policy name.

ORA-28102: policy does not exist
Cause: Try to drop/enable/refresh a non-existent policy.
Action: Correct the policy name argument.

ORA-28103: adding a policy to an object owned by SYS is not allowed
Cause: Try to add a policy to a table or a view owned by SYS.
Action: You can not perform this operation.

ORA-28104: input value for string is not valid
Cause: Input value for the argument is not valid
Action: specify a valid argument value.

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

ORA-28106: input value for argument #string is not valid
Cause: Input values for the argument is missing or invalid.
Action: Correct the input values.

ORA-28107: policy was disabled
Cause: Try to flush a disabled policy.
Action: If the policy is supposed to be enforced, it must be enabled.

ORA-28108: circular security policies detected
Cause: Policies for the same object reference each other.
Action: Drop the policies

ORA-28109: the number of related policies has exceeded the limit of 16
Cause: Too many policies are involved in the same objects.
Action: Drop one or more policies. Or combine a few of them into one.

ORA-28110: policy function or package string.string has error
Cause: The policy function may have been dropped, or is no longer valid.
Action: Check the status of the function and correct the problem. Or re-create the policy with a valid function.

ORA-28111: insufficient privilege to evaluate policy predicate
Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access.
Action: Grant appropriate privileges to the policy function owner.

ORA-28112: failed to execute policy function
Cause: The policy function has one or more error during execution.
Action: Check the trace file and correct the errors.

ORA-28113: policy predicate has error
Cause: Policy function generates invalid predicate.
Action: Review the trace file for detailed error information.

ORA-28115: policy with check option violation
Cause: Policy predicate was evaluated to FALSE with the updated values.
Action: None

ORA-28116: insufficient privileges to do direct path access
Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.
Action: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully.

ORA-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.
Action: make sure that the updated foreign key values must also visible in the parent

ORA-28118: policy group already exists
Cause: try to create a policy group that already exists
Action: None

ORA-28119: policy group does not exist
Cause: try to drop a policy group that does not exist
Action: None

ORA-28120: driving context already exists
Cause: try to create a driving context that already exists
Action: None

ORA-28121: driving context does not exist
Cause: try to drop a driving context that does not exist
Action: None

ORA-28132: Merge into syntax does not support security policies.
Cause: Merge into syntax currently does not support a security policy on the destination table.
Action: use the insert / update DML stmts on the table that has a security policy defined on it.

ORA-28134: object cannot have fine-grained access control policy
Cause: Only tables, views, or synonyms of tables or views may have VPD policies
Action: None

ORA-28137: Invalid FGA audit Handler
Cause: An invalid audit handler was specified.
Action: Specify a valid audit handler.

ORA-28138: Error in Policy Predicate
Cause: An invalid policy predicate was specified.
Action: Please specify a valide policy Predicate for the FGA policy

ORA-28139: Maximum allowed Fine Grain Audit Policies Exceeded
Cause: A maximum of 256 policies can be enabled on an object
Action: Drop or disable an existing policy before creating more

ORA-28140: Invalid column specified
Cause: Column name specified during policy creation is invalid
Action: Please specify a valid column name. Object columns are not supported

ORA-28141: error in creating audit index file
Cause: ORACLE was not able to create the file being used to hold audit file names.
Action: Examine the directory pointed to by the initialization parameter "audit_file_dest." Make sure that all of the following is true:
1. The directory exists.
2. The name indeed points to a directory and not a file.
3. The directory is accessible and writable to the ORACLE user.

ORA-28142: error in accessing audit index file
Cause: ORACLE was not able to access the file being used to hold audit file names.
Action: Make sure the file exists in the directory pointed to by the initialization parameter "audit_file_dest" and is readable by the ORACLE user.

ORA-28150: proxy not authorized to connect as client
Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.
Action: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER ... GRANT CONNECT command.

ORA-28151: more than one user name specified for command
Cause: More than one user name was specified for an ALTER USER command.
Action: Try the command again with only one user name.

ORA-28152: proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role.
Action: Change the proxy user so that it does not specify the role or grant the role to the client.

ORA-28153: Invalid client initial role specified: 'string'
Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid.
Action: Connect again as the client specifying a valid role.

ORA-28154: Proxy user may not act as client 'string'
Cause: A proxy user may not assume the identity of a privileged user in order to limit the privileges that a proxy may possess.
Action: Execute the statement again specify a client other than a privileged user.

ORA-28155: user 'string' specified as a proxy is actually a role
Cause: A user specified in an AUDIT BY ON BEHALF OF is actually a role.
Action: Execute the statement again with a valid proxy user.

ORA-28156: Proxy user 'string' not authorized to set role 'string' for client 'string'
Cause: A proxy user has not been granted the right to use a role on behalf of a client.
Action: Execute the command ALTER USER GRANT CONNECT THROUGH PROXY to grant the needed role.

ORA-28157: Proxy user 'string' forbidden to set role 'string' for client 'string'
Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER GRANT CONNECT THROUGH WITH ALL ROLES EXCEPT
Action: Execute the command ALTER USER GRANT CONNECT THROUGH PROXY to grant the needed role.

ORA-28163: GRANT already specified
Cause: The GRANT clause was specified twice.
Action: Use only one GRANT clause.

ORA-28164: REVOKE already specified
Cause: The REVOKE clause was specified twice.
Action: Use only one REVOKE clause.

ORA-28165: proxy 'string' may not specify password-protected role 'string' for client 'string'
Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed.
Action: Attempt to activate a different role or change the role administratively so that there is no password.

ORA-28166: duplicate rolename in list
Cause: The name of a role was specified more than once in a list.
Action: Repeat the command specifying the role once.

ORA-28168: attempted to grant password-protected role
Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client.
Action: Either specify a role that does not have a password or alter the role so that a password is not required.

ORA-28169: unsupported certificate type
Cause: The type of certificate from which the server is to extract the credentials of the client is not supported.
Action: Specify a supported type.

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.
Action: Specify a supported version.

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.
Action: Specify a supported version.

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.
Action: Provide a distinguished name.

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.
Action: Provide a certificate.

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.
Action: Provide a Kerberos ticket.

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.
Action: Provide a certificate of the correct type.

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.
Action: Provide a certificate of the correct version.

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.
Action: Provide a Kerberos ticket of the correct version.

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.
Action: Provide a password.

ORA-28179: client user name not provided by proxy
Cause: No user name was provided by the proxy user for the client user.
Action: Either specify a client database user name, a distinguished name or an X.509 certificate.

ORA-28180: multiple authentication methods provided by proxy
Cause: More than one authentication method was specified by the proxy user for the client user.
Action: Specify only one of the following: a client database user name, a distinguished name or an X.509 certificate.

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.
Action: Check that the initial roles are valid, granted to client, and not password protected.

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.
Action: Check that the Kerberos forwardable ticket granting ticket belongs to the client, is valid, and that the key distribution center is available.

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.
Action: Provide some form of authentication credentials.

ORA-28184: global user cannot have proxy permissions managed in the directory
Cause: The client name specified was a global user.
Action: Use ALTER USER to change the type of user (from IDENTIFIED GLOBALLY to something else, such as IDENTIFIED BY password or IDENTIFIED EXTERNALLY).

ORA-28200: IDENTIFIED USING already specified
Cause: The IDENTIFIED USING clause was specified twice.
Action: Use only one IDENTIFIED USING clause.

ORA-28201: Not enough privileges to enable application role 'string'
Cause: An attempt to enable application role outside the scope of the designated package
Action: Enable the role directly or indirectly using the designated package

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.
Action: Supply the original password.

ORA-28231: no data passed to obfuscation toolkit
Cause: A NULL value was passed to a function or procedure.
Action: Make sure that the data passed is not empty.

ORA-28232: invalid input length for obfuscation toolkit
Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes.
Action: Make sure that the length of the data to be encrypted or decrypted is a multiple of 8 bytes.

ORA-28233: double encryption not supported
Cause: The obfuscation toolkit does not support the encryption of already-encrypted data.
Action: Do not attempt to encrypt 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.
Action: Specify a longer key.

ORA-28235: algorithm not available
Cause: The encryption algorithm desired is not available.
Action: Run the installer to install the needed algorithm in Oracle Advanced Security.

ORA-28236: invalid Triple DES mode
Cause: An unknown value was specified for the mode in which triple DES encryption is to run.
Action: Specify a valid value. See the package declaration for a list of valid values.

ORA-28237: seed length too short
Cause: The seed specified for the key generation routine must be at least 80 characters.
Action: Specify a longer seed.

ORA-28238: no seed provided
Cause: A NULL value was passed in as the seed to be used in generating a key.
Action: Provide a non-NULL value for the seed.

ORA-28239: no key provided
Cause: A NULL value was passed in as an encryption or decryption key.
Action: Provide a non-NULL value for the 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.
Action: Use a SQL statement to query CURRENT_USER inside a DR procedure.

ORA-28262: global_context_pool_size has invalid value.
Cause: Parameter global_context_pool_size has a value less than the minimum required value (10K).
Action: Please specify a value for the init.ora parameter global_context_pool_size which is atleast 10k.

ORA-28263: Insufficient memory in global context pool
Cause: Allocations for the global context heap exceeded the value set in init.ora.
Action: Increase the value of global_context_pool_size parameter in init.ora or clear usused global context.

ORA-28264: Client identifier is too long
Cause: The length of the client identifier is longer than 64
Action: Set a client identifier whose length is less than 64.

ORA-28265: NameSpace beginning with 'sys_' is not allowed
Cause: Namespace beginning with 'sys_' is not allowed.
Action: Use a namespace that does not begin with 'sys_'.

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.
Action: Use a valid namespace.

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.
Action: Please change the value for _session_context_size in the init.ora file.

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.
Action: Make sure the nickname is valid and re-login.

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.
Action: Make sure ORACLE server is using right SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are right.

ORA-28272: Domain policy restricts password based GLOBAL user authentication.
Cause: Domain policy does not allow password-authenticated GLOBAL users.
Action: Make sure ORACLE server is using right SSL credentials to connect to LDAP directory services. Make sure orclDBAuthTypes attributes within Oracle enterprise domain object is either set to PWD or ALL.

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.
Action: Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values.

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.
Action: Make sure user entries in LDAP are correctly provisioned with correct ORACLE password attribute values.

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.
Action: Make sure user nickname is unique within the enterprise.

ORA-28276: Invalid ORACLE password attribute.
Cause: The ORACLE password attribute of a user entry has an invalid format.
Action: Make sure ORACLE password attribute value is RFC-2307 compliant.

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.
Action: Make sure LDAP directory service is up and running.

ORA-28278: No domain policy registered for password based GLOBAL users.
Cause: No policy about password authenticated GLOBAL users has been registered.
Action: Add attribute orclDBAuthTypes to the database server's Enterprise domain.

ORA-28279: Error reading ldap_directory_access init parameter.
Cause: ldap_directory_access parameter is not specified corrrectly.
Action: Make sure spfile.ora has ldap_directory_access set correctly. Possible correct values are PASSWORD, SSL and NONE.

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.
Action: Make sure ORACLE password attribute has one entry for ORACLE Database password.

ORA-28290: Multiple entries found for the same Kerberos Principal Name
Cause: Multiple user entries has been configured with the same krbPrincipalName
Action: Modify enterprise user's entry to assign its Kerberos principal name Make sure the user entries in LDAP are provisioned correctly.

ORA-28291: No Kerberos Principal Value found.
Cause: Oracle server fails to get value of krbPrincipalName attribute
Action: Make sure user entries are correctly provisioned with correct Kerberos principal value

ORA-28292: No Domain Policy registered for Kerberos based authentication
Cause: The enterprise domain entry is not configured for Kerberos based global authentication.
Action: Modify orclDBAuthType of the database server's enterprise domain entry and assign it "ALL" or "KRB5"

ORA-28293: No matched Kerberos Principal found in any user entry
Cause: Oracle server fails to find the principal in the user search base
Action: Make sure the user search base is correct. Use ESM to configure the enterprise user its Kerberos principal name

ORA-28300: No permission to read user entry in LDAP directory service.
Cause: ORACLE server does not have read permission on user entries.
Action: Make sure ORACLE server is using right credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are configured correctly.

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.
Action: Modify orclDBAuthType of the server's enterprise domain entry and assign it "ALL" or "SSL".

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.
Action: Add an user entry whose DN matches the user's PKI DN in the LDAP directory.

ORA-28330: encryption is not allowed for this data type
Cause: Data type was not supported for column encryption.
Action: None

ORA-28331: encrypted column size too long for its data type
Cause: column was encrypted and for VARCHAR2, the length specified was > 3932; for CHAR, the length specified was > 1932; for NVARCHAR2, the length specified was > 1966; for NCHAR, the length specified was > 966;
Action: Reduce the column size.

ORA-28332: cannot have more than one password for the encryption key
Cause: More than one password was specified in the user command.
Action: None

ORA-28333: column is not encrypted
Cause: An attempt was made to rekey or decrypt an unencrypted column.
Action: None

ORA-28334: column is already encrypted
Cause: An attempt was made to encrypt an encrypted column.
Action: None

ORA-28335: referenced or referencing FK constraint column cannot be encrypted
Cause: encrypted columns were involved in the referential constraint
Action: None

ORA-28336: cannot encrypt SYS owned objects
Cause: An attempt was made to encrypt columns in a table owned by SYS.
Action: None

ORA-28337: the specified index may not be defined on an encrypted column
Cause: Index column was either a functional, domain, or join index.
Action: None

ORA-28338: cannot encrypt indexed column(s) with salt
Cause: An attempt was made to encrypt index column with salt.
Action: Alter the table and specify column encrypting without salt.

ORA-28339: missing or invalid encryption algorithm
Cause: Encryption algorithm was missing or invalid in the user command.
Action: Must specify a valid algorithm.

ORA-28340: a different encryption algorithm has been chosen for the table
Cause: Existing encrypted columns were associated with a different algorithm.
Action: No need to specify an algorithm, or specify the same one for the existing encrypted columns.

ORA-28341: cannot encrypt constraint column(s) with salt
Cause: An attempt was made to encrypt constraint columns with salt.
Action: Encrypt the constraint columns without salt.

ORA-28342: integrity check fails on column key
Cause: Encryption metadata may have been improperly altered.
Action: None

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

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

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.
Action: Decrypt these columns before attempting to downgrade.

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.
Action: The column must be decrypted.

ORA-28347: encryption properties mismatch
Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but encryption properties were mismatched.
Action: Make sure encrytion algorithms and columns keys are identical. The corresponding columns must be encrypted on both tables with the same salt and non-salt flavor.

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.
Action: drop the 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.
Action: drop 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.
Action: drop the 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.
Action: None

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.
Action: Execute the command again using the correct wallet password or verfying a wallet exists in the specified directory. If necessary, create a new wallet and initialize it.

ORA-28354: wallet already open
Cause: The security module wallet has already been opened.
Action: None

ORA-28356: invalid open wallet syntax
Cause: The command to open the wallet contained improper spelling or syntax.
Action: If attempting to open the wallet, verify the spelling and syntax and execute the command again.

ORA-28357: password required to open the wallet
Cause: A password was not provided when executing the open wallet command.
Action: Retry the command with a valid password.

ORA-28358: improper set key syntax
Cause: The command to set the master key contained improper spelling or syntax.
Action: If attempting to set the master key for Transparent Database Encryption, verify the spelling and syntax and execute the command again.

ORA-28359: invalid certificate identifier
Cause: The certificate specified did not exist in the wallet.
Action: Query the V$WALLET fixed view to find the proper certificate identifier for certificate to be used.

ORA-28361: master key not yet set
Cause: The master key for the instance was not set.
Action: Execute the ALTER SYSTEM SET KEY command to set a master key for the database instance.

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.
Action: Check wallet location parameters to see if they specify the correct wallet. Also, verify that an SSO wallet is not being used when an encrypted wallet is intended.

ORA-28363: buffer provided not large enough for output
Cause: A provided output buffer is too small to contain the output.
Action: Check the size of the output buffer to make sure it is initialized to the proper size.

ORA-28364: invalid wallet operation
Cause: The command to operate the wallet contained improper spelling or syntax.
Action: Verify the spelling and syntax and execute the command again.

ORA-28365: wallet is not open
Cause: The security module wallet has not been opened.
Action: Open the wallet.

ORA-28366: invalid database encryption operation
Cause: The command for database encryption contained improper spelling or syntax.
Action: Verify the spelling and syntax and execute the command again.

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.
Action: Verify that the WALLET_LOCATION or the ENCRYPTION_WALLET_LOCATION parameter is correct and that a valid wallet exists in the path specified.

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.
Action: Confirm that proper directory permissions are granted to the Oracle user and that neither an encrypted or obfuscated wallet exists in the specified wallet location and try again.

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.
Action: Bring the tablespace online and try again

ORA-28370: ENCRYPT storage option not allowed
Cause: You attempted to specify the ENCRYPT storage option. This option may only be specified during CREATE TABLESPACE.
Action: Remove this option and retry the statement.

ORA-28371: ENCRYPTION clause and/or ENCRYPT storage option not allowed
Cause: You attempted to specify the ENCRYPTION clause or ENCRYPT storage option for creating TEMP or UNDO tablespaces.
Action: Remove these options and retry the statement.

ORA-28372: missing ENCRYPT storage option for encrypted tablespace
Cause: You attempted to specify ENCRYPTION property for CREATE TABLESPACE without specifying ENCRYPT storage option to encrypt the tablepsace.
Action: Add ENCRYPT storage option and retry the statement.

ORA-28373: missing ENCRYPTION clause for encrypted tablespace
Cause: You attempted to specify storage option ENCRYPT in CREATE TABLESPACE without specifying ENCRYPTION property to encrypt the tablepsace.
Action: Add ENCRYPTION clause and retry the statement.

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.
Action: Copy the correct Oracle Wallet from the instance where the tablespace was created.

ORA-28375: cannot perform cross-endianism conversion on encrypted tablespace
Cause: You attempted to perform cross-endianism conversion on encrypted tablespace.
Action: Cross-endianism conversion on encrypted tablespace is not supported.

ORA-28376: cannot find PKCS11 library
Cause: The HSM vendor's library cannot be found.
Action: Place the HSM vendor's library in the following directory structure: For Unix like system: /opt/oracle/extapi/[32,64]/hsm/{VENDOR}/{VERSION}/lib. For Windows systems: %SYSTEM_DRIVE%\oracle\extapi\[32,64]\hsm\{VENDOR}\{VERSION}\lib. [32, 64] - refers to 32bit or 64bit binary. {VENDOR} - The name of the vendor supplying the library. {VERSION} - Version of the library, perferably in num#.num#.num# for// mat.

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.
Action: No action required.

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.
Action: Reopen the wallet.

ORA-28379: a different integrity algorithm has been chosen for the table
Cause: Existing encrypted columns were associated with a different algorithm.
Action: No need to specify an algorithm, or specify the same one for the existing encrypted columns.

ORA-28380: database is not open in read/write mode
Cause: Database was not open in read/write mode and could not perform these wallet operations.
Action: Open the database in read/write mode and retry this command.

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
Cause: The cause is explained in the forwarded message.
Action: See the non-Oracle system's documentation of the forwarded message.

ORA-28501: communication error on heterogeneous database link
Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.
Action: See the documentation for the non-Oracle system for an explanation of the second error message.

ORA-28502: internal communication error on heterogeneous database link
Cause: A communication error internal to ORACLE's heterogeneous services has occurred.
Action: Contact Oracle customer support.

ORA-28503: bind value cannot be translated into SQL text for non-Oracle system
Cause: A SQL statement used bind variables on a Heterogenous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables.
Action: Change your SQL statement so that it does not use bind variables.

ORA-28504: ROWID not found in ROWID cache for heterogeneous database link
Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache.
Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the Heterogenous Services initialization parameter HS_ROWID_CACHE_SIZE.

ORA-28505: cannot get non-Oracle system capabilities from string
Cause: ORACLE was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
Action: Contact the DBA to check the server data dictionary table named in the error message. If table contents are incorrect, the DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.

ORA-28506: parse error in data dictionary translation for string stored in string
Cause: A reference to an ORACLE data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The ORACLE data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation.
Action: Contact customer support of the agent vendor.

ORA-28507: error in data dictionary view string
Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect.
Action: Verify correct installation of the following Heterogeneous Services' initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory.

ORA-28508: invalid value string for Heterogeneous Services initialization parameter string
Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system.
Action: Check the Heterogeneous Services and agent documentation to determine acceptable values

ORA-28509: unable to establish a connection to non-Oracle system
Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.
Action: Check the Net8 service name definition in the following places: -- the USING clause of the CREATE DATABASE LINK statement -- the TNSNAMES.ORA file -- the Oracle Names Server The following are possible reasons for name mismatches: -- The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server. -- The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener. -- The SID= in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener.

ORA-28510: heterogeneous database link initialization failed
Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.
Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly.

ORA-28511: lost RPC connection to heterogeneous remote agent using SID=string
Cause: A fatal error occurred in one of the following places: -- 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.
Action: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact a customer support representative of the agent vendor.

ORA-28512: cannot get data dictionary translations from string
Cause: ORACLE was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views.
Action: Ask your DBA to check the server data dictionary table named in the error message. If table contents are incorrect, the DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.

ORA-28513: internal error in heterogeneous remote agent
Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.
Action: Make a note of how the error was produced and contact the customer support representative of the agent vendor.

ORA-28514: heterogeneous database link initialization could not convert system date
Cause: The system date was not retrievable.
Action: Verify that the ORACLE server's host machine and operating system are operational. This error should not occur unless low level system functions are failing.

ORA-28515: cannot get external object definitions from string
Cause: ORACLE was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed.
Action: Verify that the ORACLE server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory.

ORA-28518: data dictionary translation has illegal translation type
Cause: A data dictionary translation definition, either in the ORACLE server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the ORACLE instance and to the ORACLE instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an ORACLE server on the first connection from the server to the agent.
Action: Contact the customer support of the agent vendor.

ORA-28519: no heterogeneous data dictionary translations available
Cause: The ORACLE server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a DBA to resolve this problem. The easiest solution is to enable automatic self-registration by setting the ORACLE server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact the customer support representative of the agent vendor.

ORA-28520: error initializing heterogeneous data dictionary translations
Cause: ORACLE was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the ORACLE server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the ORACLE server, verify that the script has been run. If both scripts were executed and the error persists, contact the customer support representative of the agent vendor.

ORA-28521: no heterogeneous capability information available
Cause: The ORACLE server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a DBA to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the ORACLE server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact the customer support representative of the agent vendor.

ORA-28522: error initializing heterogeneous capabilities
Cause: ORACLE was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the ORACLE server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the ORACLE server, verify that the script has been run. If both scripts were executed and the error persists, contact the customer support representative of the agent vendor.

ORA-28523: ORACLE and heterogeneous agent are incompatible versions
Cause: An operation on a database link attempted to connect to a non-Oracle system, but the ORACLE instance and the agent process for the non-Oracle system are incompatible.
Action: Ask your DBA to confirm configuration of both the ORACLE instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the ORACLE instance and the agent, and in the ORACLE instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported.

ORA-28525: unable to create Heterogeneous Services error message text
Cause: Incorrect arguments were passed into the error message creation routine.
Action: Contact Oracle customer support.

ORA-28526: invalid describe information returned to Heterogeneous Services
Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.
Action: Contact customer support of the agent vendor.

ORA-28527: Heterogeneous Services datatype mapping error
Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the ORACLE server's data dictionary.
Action: Verify that the ORACLE server's data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact the customer support representative of the agent vendor.

ORA-28528: Heterogeneous Services datatype conversion error
Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for 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
Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value.

ORA-28529: invalid or missing parameter in Net8 service name definition
Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server.
Action: Ask your DBA to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's documentation.

ORA-28530: Heterogeneous Services initialization error in NLS language ID
Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the ORACLE server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs.
Action: Contact Oracle customer support.

ORA-28533: Heterogeneous Services coercion handling error
Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions.
Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed.

ORA-28534: Heterogeneous Services preprocessing error
Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled.
Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed.

ORA-28535: invalid Heterogeneous Services context
Cause: A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver.
Action: Contact Oracle customer support or your agent vendor.

ORA-28536: error in processing Heterogeneous Services initialization parameters
Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the ORACLE server data dictionary.
Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one.

ORA-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.
Action: Contact Oracle customer support.

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.
Action: Check the documentation for the gateway that you are using and see if it will automatically close currently open result sets each time a stored procedure is executed. Then check if your client program is doing anything that violates this rule. If it is, fix your program. If it is not then contact Oracle customer support.

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.
Action: Check the documentation for the gateway that you are using and see if it supports result sets returned from stored procedures. If it does not, then the only way of accessing such stored procedures is to upgrade to a version of the gateway that does support result sets (if such a version exists). If the gateway does have result set support and you are still seeing this error then contact Oracle customer support.

ORA-28540: internal result set error
Cause: A protocol error internal to Heterogeneous Services or Oracle Database Gateway code has occurred.
Action: Contact Oracle customer support.

ORA-28541: Error in HS init file on line number.
Cause: A syntax error occurred in the gateway initialization file.
Action: Check gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file.

ORA-28542: Error in reading HS init file
Cause: Reading the gateway init file generated an error.
Action: Check the gateway initialization file name to see that the gateway initialization file acctually exists. Check the ifile parameter to see that it points to the correct location.

ORA-28543: Error initializing apply connection to non-Oracle system
Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed.
Action: Check if the listener used to connect to the gateway is up and is correctly configured. Make sure that the database link used has been configured correctly and, if a tnsnames alias has been used in the database link definition, make sure that the configuration of the entry in tnsnames.ora has been done correctly.

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.
Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the agent's host machine to assure that the service name or SID refers to the correct agent executable in its (PROGRAM=...) clause. -- Confirm in TNSNAMES.ORA or the equivalent service definition that sevice 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).

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.
Action: Refer to the Net8 NCRO error message. If this isn't clear, check connection administrative setup in tnsnames.ora and listener.ora for the service associated with the Heterogeneous Services database link being used, or with 'extproc_connection_data' for an external procedure call.

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=).
Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID connects to the correct program. -- Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (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.
Action: Check Oracle Net administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the client connection to the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID refers to the correct server. -- Confirm in TNSNAMES.ORA or the equivalent service definition that the connect string does NOT contain (HS=).

ORA-28550: pass-through SQL: cursor not found
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call.

ORA-28551: pass-through SQL: SQL parse error
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system.

ORA-28552: pass-through SQL: call flow error
Cause: A pass-through SQL function was called in an invalid order.
Action: Correct program flow by changing the order of API calls to match the flow described in the manual.

ORA-28553: pass-through SQL: invalid bind-variable position
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.

ORA-28554: pass-through SQL: out of cursors
Cause: The maximum number of open cursors has been exceeded.
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.

ORA-28555: pass-through SQL: required parameter missing or NULL
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
Action: Use a non-NULL value for the parameter.

ORA-28556: authorization insufficient to access table
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
Action: Contact the DBA for the non-Oracle system. The DBA can grant permission to access the privileged table or columns.

ORA-28557: unknown string for database link to non-Oracle system
Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these names to configure the heterogeneous database link.
Action: Contact the DBA to check setup of the connection and the Heterogeneous Services agent.

ORA-28558: HS_FDS_CONNECT_STRING undefined for non-Oracle system
Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the ORACLE server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed.
Action: Contact your DBA to verify correct setup of an HS_FDS_CONNECT_STRING entry in the ORACLE Heterogeneous Services data dictionary.

ORA-28559: FDS_CLASS_NAME is string, FDS_INST_NAME is string
Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the ORACLE data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store.
Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check ORACLE data dictionary contents when necessary to diagnose the cause of the associated error.

ORA-28560: error in configuration of agent process
Cause: An ORACLE server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable.
Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct SID. -- Check LISTENER.ORA on the agent's host machine to assure that this SID refers to the correct agent executable in its (PROGRAM=...) clause.

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.
Action: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent.

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.
Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server.

ORA-28576: lost RPC connection to external procedure agent
Cause: of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact your customer support representative.
Action: First check the 3GL code you are invoking; the most likely

ORA-28577: argument string of external procedure string has unsupported datatype string
Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected.
Action: Check your documentation for the supported datatypes of external procedure arguments.

ORA-28578: protocol error during callback from an external procedure
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle customer support.

ORA-28579: network error during callback from external procedure agent
Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle customer support.

ORA-28580: recursive external procedures are not supported
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
Action: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, etc.

ORA-28581: protocol error while executing recursive external procedure
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
Action: Contact Oracle customer support.

ORA-28582: a direct connection to this agent is not allowed
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.
Action: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent.

ORA-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.
Action: Make sure that SQL code issued by Heterogeneous Services agents does not reference a database link.

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.
Action: Make sure that the apply database link is correctly configured and that the gateway listener and the non-Oracle system are correctly set up and are up and running. If everything is configured correctly and the problem still occurs, contact Oracle customer support. errors 28590 - 28599 are reserved for the HS agent control utility

ORA-28590: agent control utility: illegal or badly formed command
Cause: The user has issued an unrecognized or syntactically incorrect command.
Action: Refer to documentation and correct the syntax of the command.

ORA-28591: agent control utility: unable to access parameter file
Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its admin directory or because permissions on directory were not correctly set.
Action: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to.

ORA-28592: agent control utility: agent SID not set
Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail.
Action: Issue the command SET AGENT_SID and then retry the command that failed.

ORA-28593: agent control utility: command terminated with error
Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shutdown an agent that is no longer running.
Action: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shutdown first by issuing the SHUTDOWN command.

ORA-28594: agent control utility: invalid parameter name
Cause: The user tried to set or unset an invalid agent parameter.
Action: Refer to documentation and correct the parameter name.

ORA-28595: Extproc agent : Invalid DLL Path
Cause: The path of DLL supplied for the extproc execution is invalid.
Action: Check if the DLL path is set properly using the EXTPROC_DLLS environment variable. errors 28600 - 28620 are reserved for bitmap indexes

ORA-28601: invalid [no]MINIMIZE option
Cause: user didn't type this alter table MINIMIZE RECORDS_PER_BLOCK or alter table NOMINIMIZE RECORDS_PER_BLOCK
Action: reenter correct sql command

ORA-28602: statement not permitted on tables containing bitmap indexes
Cause: table has bitmap indexes and user is minimizing or nominimizing records_per_block
Action: drop all bitmap indexes before changing records_per_block

ORA-28603: statement not permitted on empty tables
Cause: table is empty and statement does not work on empty tables
Action: try statement after loading your data

ORA-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)
Action: Defragment the table or block(s). Use the values in the message to determine the FIRST block affected. (There may be others).

ORA-28605: bitmap indexes cannot be reversed
Cause: user tried to create reverse bitmap index
Action: don't do this; it is not supported

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)
Action: alter system flush shared_pool; update tab$ set spare1 = 8192 where obj# = (select obj# from obj$ where NAME= AND owner# = ; commit;

ORA-28611: bitmap index is corrupted - see trace file for diagnostics
Cause: Validate Index detected bitmap corruption in its argument index
Action: Drop this bitmap index and create a new one.

ORA-28650: Primary index on an IOT cannot be rebuilt
Cause: An attempt is made to issue alter index rebuild on IOT-TOP
Action: Use Alter table MOVE to reorganize the table(IOT)

ORA-28651: Primary index on IOTs can not be marked unusable
Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX
Action: Remove the option UNUSABLE

ORA-28652: overflow segment attributes cannot be specified
Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING.
Action: Remove the illegal option(s).

ORA-28653: tables must both be index-organized
Cause: Attempt to exchange a non IOT table/partition with a partition/table respectively
Action: Ensure that non-partitioned and partitioned tables are both index-organized.

ORA-28654: table and partition not overflow compatible
Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one doesn't.
Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does.

ORA-28655: Alter table add overflow syntax error
Cause: Syntax error
Action: Check the syntax.

ORA-28656: incomplete attribute specification
Cause: The attribute specification is not done for all partitions"
Action: Specify the storage attributes either for ALL partitions or NONE NLS_DO_NOT_TRANSLATE [28657,28657]

ORA-28658: This operation is supported only for Index-Organized tables
Cause: Attempt to perform some IOT specific operation on a non-IOT
Action: don't do this. This is not supported

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
Action: Specify COMPRESS at table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ...

ORA-28660: Partitioned Index-Organized table may not be MOVEd as a whole
Cause: Attempt to MOVE partitioned IOT as a whole
Action: don't do this. This is not supported

ORA-28661: Object already has COMPRESS clause specified
Cause: Attempt to specify compress for iot/index which already has a compression clause.
Action: This is a 'create time only' attribute

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.
Action: don't do that

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.
Action: don't do that

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
Action: Coalesce the table a partition at a time (using ALTER TABLE MODIFY PARTITION COALESCE)

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
Action: Make sure the compression attributes match If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS

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)
Action: Build the index without these options

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.
Action: Remove the USING INDEX clause and specify all attributes directly for the table

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
Action: Issue the statement against the parent index-organized table containing the specified mapping 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.
Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using 'ALTER TABLE .. MOVE 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.
Action: Drop the bitmap index(es) before dropping the mapping table.

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.
Action: Issue a partition level operation with ALTER INDEX .. PARTITION .. UPDATE BLOCK REFERENCES

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.
Action: Use online index [partition] rebuild to fix the block references

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 .
Action: Use updates and inserts on index-organized table .

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.
Action: Issue the statement against the associated permanent index-organized table.
RA-29250: Invalid index specifed in call to dbms_sql.bind_array
Cause: An invalid index was specified in a call to bind_array of dbms_sql. The index may have been null or of an improper value.
Action: Correct the index value by modifying your PL/SQL program and try the bind_array call again.

ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array
Cause: The value of index1 was greater than the value for index2 in the call to bind_array. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2.
Action: Correct the value of the two indexes and try the call to again bind_array.

ORA-29252: collection does not contain elements at index locations in call to dbms_sql.bind_array
Cause: The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true.
Action: Either modify the two indexes or the contents of the table and try the call again.

ORA-29253: Invalid count argument passed to procedure dbms_sql.define_array
Cause: The count argument specified in the call to procedure define_array of package dbms_sql had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer.
Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again.

ORA-29254: Invalid lower_bound argument passed to procedure dbms_sql.define_array
Cause: The lower_bound argument specified in the call to procedure define_array had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal.
Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again.

ORA-29255: Cursor contains both bind and define arrays which is not permissible
Cause: Both define_array and bind_array have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries.
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand.

ORA-29256: Cursor contains both regular and array defines which is illegal
Cause: Both define_array and define_column have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables.
Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the situation at hand.

ORA-29257: host string unknown
Cause: The specified host was unknown.
Action: Check the spelling of the host name or the IP address. Make sure that the host name or the IP address is valid.

ORA-29258: buffer too small
Cause: The input or output buffer was too small for the operation.
Action: Increase the size of the buffer and retry the operation.

ORA-29259: end-of-input reached
Cause: The end of the input was reached.
Action: If the end of the input is reached prematurely, check if the input source terminates prematurely. Otherwise, close the connection to the input.

ORA-29260: network error: string
Cause: A network error occurred.
Action: Fix the network error and retry the operation.

ORA-29261: bad argument
Cause: A bad argument was passed to the PL/SQL API.
Action: Check the arguments passed to the PL/SQL API and retry the call.

ORA-29262: bad URL
Cause: An improperly formed URL was passed to the PL/SQL API.
Action: Check the URL and retry the call.

ORA-29263: HTTP protocol error
Cause: A HTTP protocol error occured during the HTTP operation.
Action: Check the HTTP server that the HTTP operation was performed to make sure that it follows the HTTP protocol standard.

ORA-29264: unknown or unsupported URL scheme
Cause: The URL scheme was unknown or unsupported.
Action: Check the URL to make sure that the scheme is valid and supported.

ORA-29265: HTTP header not found
Cause: The requested HTTP header was not found.
Action: Check to make sure that the requested HTTP header is present.

ORA-29266: end-of-body reached
Cause: The end of the HTTP response body was reached.
Action: If the end of the HTTP response is reached prematurely, check if the HTTP response terminates prematurely. Otherwise, end the HTTP response.

ORA-29267: illegal call
Cause: The call to the PL/SQL API was illegal at the current stage of the operation.
Action: Retry the call at a different stage of the operation.

ORA-29268: HTTP client error string
Cause: The HTTP response indicated that the HTTP client error occurred.
Action: Fix the HTTP client error and retry the HTTP request.

ORA-29269: HTTP server error string
Cause: The HTTP response indicated that the HTTP server error occurred.
Action: Fix the HTTP server error and retry the HTTP request. Contact the admistrator of the HTTP server when necessary.

ORA-29270: too many open HTTP requests
Cause: Too many HTTP requests were opened.
Action: End some HTTP requests and retry the HTTP request.

ORA-29271: not connected
Cause: The network connection was not made while the network operation was attempted.
Action: Retry the network operation after the network connection is made successfully.

ORA-29272: initialization failed
Cause: The UTL_HTTP package failed to initialize.
Action: Free up some memory or other system resources and retry the operation.

ORA-29273: HTTP request failed
Cause: The UTL_HTTP package failed to execute the HTTP request.
Action: Use get_detailed_sqlerrm to check the detailed error message. Fix the error and retry the HTTP request.

ORA-29274: fixed-width multibyte character set not allowed for a URL
Cause: The character set used as an encoding of the URL is a fixed-width multibyte character set and is not allowed for a URL.
Action: Use the corresponding variable-width multibyte character set for the URL instead.

ORA-29275: partial multibyte character
Cause: The requested read operation could not complete because a partial multibyte character was found at the end of the input.
Action: Ensure that the complete multibyte character is sent from the remote server and retry the operation. Or read the partial multibyte character as RAW.

ORA-29276: transfer timeout
Cause: Timeout occurred while reading from or writing to a network connection.
Action: Check the remote server or the network to ensure that it responds within the timeout limit. Or increase the timeout value.

ORA-29277: invalid SMTP operation
Cause: The SMTP operation was invalid at the current stage of the SMTP transaction.
Action: Retry the SMTP operation at the appropriate stage of the SMTP transaction.

ORA-29278: SMTP transient error: string
Cause: A SMTP transient error occurred.
Action: Correct the error and retry the SMTP operation.

ORA-29279: SMTP permanent error: string
Cause: A SMTP permanent error occurred.
Action: Correct the error and retry the SMTP operation.

ORA-29280: invalid directory path
Cause: A corresponding directory object does not exist.
Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command.

ORA-29281: invalid mode
Cause: An invalid value was specified for file open mode.
Action: Correct the mode to be one of the values: 'r','a', or 'w'.

ORA-29282: invalid file ID
Cause: A file ID handle was specified for which no corresponding open file exists.
Action: Verify that the file ID handle is a value returned from a call to UTL_FILE.FOPEN.

ORA-29283: invalid file operation
Cause: An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system.
Action: Verify file and directory access privileges on the file system, and if reading, verify that the file exists.

ORA-29284: file read error
Cause: An attempt to read from a file failed.
Action: Verify that the file exists, and that it is accessible, and that it is open in read mode.

ORA-29285: file write error
Cause: Failed to write to, flush, or close a file.
Action: Verify that the file exists, that it is accessible, and that it is open in write or append mode.

ORA-29286: internal error
Cause: A fatal error occurred while allocating PL/SQL session memory.
Action: Verify that the PL/SQL session is connected and that adequate memory resources are available.

ORA-29287: invalid maximum line size
Cause: An invalid maximum line size value was specified.
Action: Correct the maximum line size to be in the range [1, 32767].

ORA-29288: invalid file name
Cause: A NULL or zero length file name was specified.
Action: Correct the file name to be a nonzero length string.

ORA-29289: directory access denied
Cause: A directory object was specified for which no access is granted.
Action: Grant access to the directory object using the command GRANT READ ON DIRECTORY [object] TO [username];.

ORA-29290: invalid offset specified for seek
Cause: An attempt was made to seek past the end of the file, or both the absolute and relative offsets were NULL, or absolute offset was less than zero.
Action: If specifying an absolute offset, ensure it is in the range [0, ], or if specifying a relative offset, ensure it is no greater than the current byte position plus the number of bytes remaining in the file.

ORA-29291: file remove operation failed
Cause: A file deletion attempt was refused by the operating system.
Action: Verify that the file exists and delete privileges granted on the directory and the file.

ORA-29292: file rename operation failed
Cause: A file rename attempt was refused by the operating system either because the source or destination directory does not exist or is inaccessible, or the source file isn't accessible, or the destination file exists.
Action: Verify that the source file, source directory, and destination directory exist and are accessible, and that the destination file does not already exist.

ORA-29293: A stream error occurred during compression or uncompression.
Cause: The stream state was discovered to be invalid during compression or uncompression, or an invalid compression quality was requested or a NULL or invalid compression parameter was detected.
Action: Verify that quality is within the range [0,9] and that valid input source data exists.

ORA-29294: A data error occurred during compression or uncompression.
Cause: An error occurred while compressing or uncompressing input source.
Action: Verify that source data is a valid compressed or uncompressed data set.

ORA-29295: invalid mime header tag
Cause: An error occurred while scanning string for mime header tag
Action: Verify that source data is a valid mime header string, in the format: =????=

ORA-29296: invalid encoded string
Cause: An error occurred while decoding the input string
Action: Verify that source data is a valid encoded string.

ORA-29297: The compressed representation is too big
Cause: The compressed output is too big to return.
Action: Do not attempt to compress source data.

ORA-29298: Character set mismatch
Cause: The character set mode in which the file was opened did not match the character set of the read or write operation.
Action: Use the correct UTL_FILE read and write procedures which coorespond to the character set mode in which the file was opened.

ORA-29299: Invalid handle for piecewise compress or uncompress
Cause: The process program opened too many handles, and the specified handle was either uninitialized or outside a valid range.
Action: Close some handles and verify that the specified handle is opened or within a valid range.

ORA-29300: ORACLE error, tablespace point-in-time recovery
Cause: Another ORACLE error occured in the DBMS_PITR package.
Action: See the text of the error message for a description of the error.

ORA-29301: wrong DBMS_PITR package function/procedure order
Cause: The DBMS_PITR package function/procedure was called in an incorrect order.
Action: Restart tablespace point-in-time recovery with a correct procedure.

ORA-29302: database is not open clone
Cause: The database was not opened as a clone database.
Action: Mount the database clone and open the database.

ORA-29303: user does not login as SYS
Cause: The user did not log in as SYS to perform tablespace point-in-time recovery in a clone database.
Action: Log in as SYS and restart tablespace point-in-time recovery.

ORA-29304: tablespace 'string' does not exist
Cause: The selected tablespace does not exist in the database.
Action: Check the list of tablespaces in V$TABLESPACE and select a valid tablespace.

ORA-29305: cannot point-in-time recover tablespace 'string'
Cause: An attempt was made to ALTER the tablespace to be read only.
Action: Check if the tablespace is SYSTEM or with online rollback segment.

ORA-29306: datafile string is not online
Cause: The selected datafile was not online.
Action: Bring the the datafile online and rename it if necessary.

ORA-29307: datafile string error, string
Cause: The datafile is not ready for tablespace point-in-time recovery.
Action: Check the correct tablespace point-in-time recovery procedure.

ORA-29308: view TS_PITR_CHECK failure
Cause: Some objects which crossed the boundary of the recovery set were not allowed in the tabelspace point-in-time recovery.
Action: Query TS_PITR_CHECK and resolve the boundary crossing objects.

ORA-29309: export dump file was generated by different version of DBMS_PITR package
Cause: The version of DBMS_PITR is different from the version of the cloned database.
Action: Load the version of DBMS_PITR which matches the version of the cloned database.

ORA-29310: database is not open, or opened as a clone
Cause: Either the database was not open, or an attempt was made to open it as a cloned database.
Action: Open the production database instead.

ORA-29311: export dump file was not generated by this database, string does not match
Cause: The export dump files were imported to an incorrect database.
Action: Open the correct production database and try the import again.

ORA-29313: tablespace 'string' cannot be imported twice
Cause: This is an internal error.
Action: Contact your database administrator.

ORA-29314: tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
Cause: Tablespace clean SCN is either 0 or invalid.
Action: ALTER the tablespace OFFLINE FOR RECOVER.

ORA-29315: tablespace 'string' has been recreated
Cause: An attempt was made to recover a tablespace to a point-in-time before it was recreated.
Action: Choose a different point in time for recovery.

ORA-29316: datafile string been imported twice
Cause: This is an internal error.
Action: Contact your database administrator.

ORA-29317: datafile string does not exist
Cause: The specified datafile could not be found in the production database.
Action: Copy the datafile from the clone database.

ORA-29318: datafile string is online
Cause: The datafile is online.
Action: Take the datafile offline.

ORA-29319: datafile string is not correct
Cause: An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database.
Action: Copy the datafile from the clone database to the production database.

ORA-29320: datafile header error
Cause: An error occured during reading datafile header.
Action: Copy the correct datafile from the clone database to the production database, then retry the operation.

ORA-29321: too many datafiles added since the point-in-time
Cause: Too many datafiles were added to the recovery set since the point-in-time recovery.
Action: Divide the recovery set into smaller subsets and retry.

ORA-29322: SCN string size too long -- maximum size 58 bytes/characters
Cause: Too many characters in specifying the SCN string
Action: Remove all unnecessary characters. Only 15 characters are required for both the hex and decimal representation of the 48 bit SCN.

ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by string
Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances do not support dynamic compatible setting change.
Action: No action required.

ORA-29324: SET COMPATIBILITY release string format is wrong
Cause: It should be of the form x.x.x
Action: Use the correct format.

ORA-29325: SET COMPATIBILITY release number lower than string
Cause: The SET COMPATIBILITY release compatibility release number was lower than the current compatible setting.
Action: Specify a higher release number.

ORA-29326: SET COMPATIBILITY release number higher than string
Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances had a lower release number.
Action: Specify a lower release number.

ORA-29327: unsupported client compatibility mode used when talking to the server
Cause: The client compatibility mode is higher than the version of the server.
Action: Using SET COMPATIBILITY command, specify the same release number as the server.

ORA-29328: too many datafiles in this tablespace 'string'
Cause: Too many datafiles in this bitmap tablespace. ORACLE does not support at this moment.
Action: Call Oracle Support.

ORA-29329: Table not of type XMLType
Cause: Table is not XMLType table
Action: Ensure table is a XMLType table

ORA-29330: Source script length too big
Cause: Source script length exceeded the maximum size of 4 Gigabytes.
Action: Make sure source script length is not greater than 4 Gigabytes.

ORA-29335: tablespace 'string' is not read only
Cause: The tablespace is not read only.
Action: Make the tablespace read only and retry the operation.

ORA-29336: Internal error [string] [string] from DBMS_PLUGTS
Cause: Internal error from package DBMS_PLUGTS.
Action: Call Oracle Support.

ORA-29337: tablespace 'string' has a non-standard block size (string)
Cause: The tablespace has a non-standard block size and making such a tablespace read-write is not permitted.
Action: Use some other mechanism to import the data

ORA-29338: datafile string is in an undesired state (stringstring)
Cause: The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE.
Action: Put the datafile into the desired state.

ORA-29339: tablespace block size string does not match configured block sizes
Cause: The block size of the tablespace to be plugged in or created does not match the block sizes configured in the database.
Action: Configure the appropriate cache for the block size of this tablespace using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.

ORA-29340: export file appears to be corrupted: [string] [string] [string]
Cause: This is caused either by a corrupted export file or by an Oracle internal error.
Action: Make sure the export file used for transportable tablespace is not corrupted. If the error still occurs, call Oracle support.

ORA-29341: The transportable set is not self-contained
Cause: The set of objects in the set of tablespaces selected are not self-contained.
Action: Consider using different export options, or removing some of the pointers that caused the violation, or selecting a different set of tablespaces.

ORA-29342: user string does not exist in the database
Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.
Action: Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options.

ORA-29343: user string (mapped from user string) does not exist in the database
Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.
Action: Consider either creating the user or map the original user to a different user.

ORA-29344: Owner validation failed - failed to match owner 'string'
Cause: The system failed to match the referred owner. There are two cases that this may occur. (1) This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified. (2) This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set.
Action: Retry import with a different OWNER list.

ORA-29345: cannot plug a tablespace into a database using an incompatible character set
Cause: Oracle does not support plugging a tablespace into a database using an incompatible character set.
Action: Use import/export or unload/load to move data instead.

ORA-29346: invalid tablespace list
Cause: the tablespace list supplied to dbms_tts.transport_set_check PL/SQL routine is in an incorrect format.
Action: Check the manual and use the correct format.

ORA-29347: Tablespace name validation failed - failed to match tablespace 'string'
Cause: The system failed to match the referred tablespace. There are 2 cases that this may happen. (1) This tablespace is in the transportable set, but it is not specified in the TABLESPACES list of the import command line option, assuming that TABLESPACES is specified. (2) This tablespace is in the TABLESPACES list, but it is not in the transportable set.
Action: Retry the operation with the correct TABLESPACES list.

ORA-29348: You must specify the datafiles to be plugged in
Cause: The datafiles to be plugged in are not specified.
Action: Specify the datafiles via the import DATAFILES command line option.

ORA-29349: tablespace 'string' already exists
Cause: Tried to plug-in a tablespace which already exists.
Action: Drop the offending tablespace if possible. Otherwise use a different method (e.g., import/export) to move data.

ORA-29351: can not transport system, sysaux, or temporary tablespace 'string'
Cause: The referred tablespace is either the system tablespace, the sysaux tablespace, or a temporary tablespace.
Action: Do not include this tablespace in the transportable set.

ORA-29352: event 'string' is not an internal event
Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event name that is not an internal event.
Action: Check the list of events from X$KSLED and verify the event name parameter passed to the WAIT_FOR_EVENT procedure.

ORA-29353: The transportable list is too long.
Cause: The transportable list exceeds the buffer size of 32767.
Action: Reduce the list of tablespaces to transport.

ORA-29355: NULL or invalid string argument specified
Cause: The named argument was either invalid or specified as a NULL
Action: Specify non-null, valid arguments.

ORA-29356: These parameters can be specified only for directives that refer to consumer groups
Cause: The below parameters were specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.where the GROUP_OR_SUBPLAN argument is a resource plan. "ACTIVE_SESS_POOL_P1", "QUEUEING_P1", "PARALLEL_DEGREE_LIMIT_P1", "SWITCH_P1", "SWITCH_P2", "SWITCH_P3", "MAX_EST_EXEC_TIME", "UNDO_POOL"
Action: Specify these parameters only for consumer group directives.

ORA-29357: object string already exists
Cause: The name specified as argument to procedure CREATE_PLAN, CREATE_CONSUMER_GROUP, or CREATE_CATEGORY of package DBMS_RESOURCE_MANAGER is already in use.
Action: Specify an unused name.

ORA-29358: resource plan string does not exist
Cause: An invalid plan name was specified as an argument to procedure UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan name.

ORA-29359: invalid method name string specified for resource plan string
Cause: An invalid method was specified as an argument to procedure CREATE_PLAN or UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid method name.

ORA-29360: retry operation. Too much concurrent activity
Cause: An attempt was made to revoke the switch consumer group privilege from a user for his/her initial consumer group but someone is modifying the user in another session.
Action: Retry the operation later.

ORA-29361: value string is outside valid range of 0 to 100
Cause: An invalid value was specified for a plan directive parameter.
Action: Specify a value between 0 and 100 inclusive.

ORA-29362: plan directive stringstring does not exist
Cause: A non-existent plan directive was specified for procedure UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan directive for update.

ORA-29363: plan directive stringstring is mandatory and cannot be modified or deleted
Cause: An attempt was made to modify a mandatory plan directive.
Action: Do not attempt to modify mandatory plan directives because they are required by the Resource Manager and cannot be modified.

ORA-29364: plan directive stringstring already exists
Cause: An attempt was made to create a plan directive that already exists.
Action: Retry the create operation using different values.

ORA-29365: parameters string and string cannot both be set
Cause: An attempt was made to set both parameters.
Action: Only set one of parameters or neither of them.

ORA-29366: invalid CONSUMER_GROUP argument specified
Cause: An invalid consumer group name was specified.
Action: Specify a non-NULL, valid consumer group name.

ORA-29367: object string does not exist
Cause: A non-existent object name was specified as an argument to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid plan or consumer group name.

ORA-29368: consumer group string does not exist
Cause: An non-existent consumer group was specified.
Action: Specify an existing consumer group.

ORA-29369: invalid method name string specified for consumer group string
Cause: An invalid method name was specified as an argument to procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER.
Action: Specify a valid method name.

ORA-29370: pending area is already active
Cause: An attempt was made to activate a pending area that is already active.
Action: Wait until the pending area is no longer active; then, retry the operation.

ORA-29371: pending area is not active
Cause: An attempt was made to make changes without creating a pending area.
Action: Invoke procedure CREATE_PENDING_AREA before making any changes.

ORA-29372: identifier string is too long; it must be less than string characters
Cause: An attempt was made to specify an identifier that is more than 30 characters long.
Action: Use an identifier that is 30 characters or less in length.

ORA-29373: resource manager is not on
Cause: An attempt was made to execute an operation that cannot be executed with the resource manager being off
Action: Turn on the resource manager and try again.

ORA-29374: resource plan string in top-plan string has no plan directives
Cause: A plan was created in the pending area that is an orphan or stand-alone.
Action: Create plan directives if needed. Otherwise, delete the plan.

ORA-29375: sum of values string for level string, plan string exceeds string
Cause: The sum of plan directive parameter values for the specified plan level exceeded 100.
Action: Alter the values for the level so that they sum to 100.

ORA-29376: number of consumer groups string in plan string exceeds string
Cause: The number of consumer groups in the specified plan is more than 31.
Action: Change the plan to have no more than 31 consumer groups.

ORA-29377: consumer group string is not part of top-plan string
Cause: OTHER_GROUPS was not included as part of the specified top-plan. Each top plan must include the built-in consumer group OTHER_GROUPS.
Action: Create a plan directive with the argument GROUP_OR_SUBPLAN being OTHER_GROUPS somewhere in the top-plan.

ORA-29378: invalid consumer group mapping priorities
Cause: The mapping priorities were not unique integers within the valid range.
Action: Set the mapping priorities to unique integers within the documented range.

ORA-29379: resource plan string is involved in a loop in top-plan string
Cause: A loop was discovered while validating a top-plan.
Action: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN, and remove the plan directive that causes the loop.

ORA-29380: resource plan string is currently active and cannot be deleted
Cause: An attempt was made to delete an active plan in the pending area. No changes can be made to active plans.
Action: Delete the plan when it is not in use.

ORA-29381: plan/consumer_group string referred to by another plan and cannot be deleted
Cause: An attempt was made to delete a plan or consumer group that is referred to by another plan.
Action: Remove all plan directives that have the plan or consumer group as GROUP_OR_SUBPLAN; then delete the plan or consumer group.

ORA-29382: validation of pending area failed
Cause: Invalid changes were attempted in the pending area.
Action: See documentation and the error messages that follow this one.

ORA-29383: all leaves of top-plan string must be consumer groups
Cause: An attempt was made to create or modify the specified top-plan but it has some plans as leaves.
Action: To identify which plans and/or plan directives need to be modified, look at all plans that have no plan directives. Then, alter the top-plan so that all its leaves are consumer groups.

ORA-29384: number of consumer groups and sub-plans for plan string exceeds string
Cause: An attempt was made to create or modify the specified plan, but the plan has more than 31 consumer groups or sub-plans.
Action: Make sure the specified plan points to no more than 31 distinct consumer groups or sub-plans.

ORA-29385: cannot create plan directive from string to string
Cause: An attempt was made to create a plan directive from a plan to itself.
Action: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are different.

ORA-29386: plan or consumer group string is mandatory and cannot be deleted or modified
Cause: An attempt was made to delete or modify the specified mandatory plan or consumer group.
Action: Do not attempt to delete or modify mandatory plans and consumer groups.

ORA-29387: no top-plans found in the pending area
Cause: The VALIDATE_PENDING_AREA procedure found that either the intended top-plan(s) are involved in a loop or there are no top-plans.
Action: Check all edges going from a subplan to the intended top-plan. Make sure the top plan does not have any plan referring to it.

ORA-29388: plan/consumer_group string is part of more than one top-plan
Cause: An attempt was made to delete a subtree that includes a plan or consumer group that is part of more than one top-plan as part of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. Such a plan or consumer group cannot be deleted.
Action: Check the ancestors of the plan or consumer group and make sure it is only part of the top-plan that includes the subtree being deleted.

ORA-29389: too many errors during validation
Cause: The number of errors detected during validation is too high.
Action: Perform the necessary actions to remove some errors, and retry validation.

ORA-29390: some resource plans are not part of any top-plan
Cause: An attempt was made to create or modify some plans in the pending area that are not part of any top-plan
Action: Remove these plans are try validation again.

ORA-29391: string and string must be mandatory to create a mandatory plan directive
Cause: An attempt was made to create a mandatory plan directive where either PLAN or GROUP_OR_SUBPLAN or both were not mandatory
Action: Recreate these objects as mandatory and then create the plan directive.

ORA-29392: cpu parameters for level string for plan string must be zero
Cause: The cpu parameters for the specified level had a non-zero value, which is not a valid value for the plan's current cpu policy.
Action: Change the cpu level parameters for the specified level to zero or change the plan cpu policy.

ORA-29393: user string does not exist or is not logged on
Cause: An invalid user name was specified as argument to procedure SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or the specified user was not logged on.
Action: Specify a valid user name.

ORA-29394: session id string and serial# string do not exist
Cause: Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM.
Action: Specify valid values from the view V$SESSION.

ORA-29395: cannot set the initial consumer group to string
Cause: An attempt was made to set the initial consumer group of a user to OTHER_GROUPS or an INTERNAL_USE group.
Action: Certain groups are only for the resource manager's internal use. Specify another consumer group.

ORA-29396: cannot switch group to string
Cause: An attempt was made to switch the consumer group of a user or a session to OTHER_GROUPS or an INTERNAL_USE group.
Action: Certain groups are only for the resource manager's internal use. Specify another consumer group.

ORA-29397: cannot grant/revoke switch privilege for string
Cause: An attempt was made to grant or revoke the privilege to switch to OTHER_GROUPS or an INTERNAL_USE group.
Action: Certain groups are only for the resource manager's internal use. Specify another consumer group.

ORA-29398: invalid privilege name specified
Cause: An invalid privilege name was specified as an argument to procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of package DBMS_RESOURCE_MANAGER_PRIVS.
Action: Specify a valid privilege name.

ORA-29399: user string does not have privilege to switch to consumer group string
Cause: An attempt was made to set the initial consumer group of the specified user but the user does not have the privilege to switch to that group.
Action: Grant the privilege to switch to the consumer group to the user and then set the initial group.

ORA-29400: data cartridge error string
Cause: An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error.
Action: See the data cartridge documentation for an explanation of the second error message.

ORA-29470: Effective userid or roles are not the same as when cursor was parsed
Cause: The effective userid or roles on this call to DBMS_SQL are not the same as those at the time the cursor was parsed.
Action: Make sure the effective userid and roles are the same as when cursor was pared.

ORA-29471: DBMS_SQL access denied
Cause: DBMS_SQL access was denied due to security concerns.
Action: Check the alert log and trace file for more information.

ORA-29472: DBMS_SQL.OPEN_CURSOR failed. security_level is outside the valid range of 0 to 2
Cause: An invalid security_level value was specified.
Action: Specify a valid range of 0 to 2.

ORA-29473: privilege checking level specified for 'string' must be between 0 and 2
Cause: Invalid privilege checking level specified.
Action: Correct the privilege checking level specified.

ORA-29474: DBMS_SQL.OPEN_CURSOR failed. security_level of 0 is not allowed
Cause: Security level of 0 is specified with DBMS_SQL.OPEN_CURSOR.
Action: Specify a valid security level.

ORA-29500: NAMED keyword is invalid in CREATE JAVA CLASS
Cause: A NAMED keyword was specified in the CREATE JAVA CLASS statement. NAMED keywords are valid only in CREATE JAVA SOURCE or RESOURCE statements.
Action: Remove the NAMED keyword from the CREATE JAVA CLASS statement.