ORA-26103: V6 or V7 data file used to create control file

ORA-26103: V6 or V7 data file used to create control file

Cause: The file header of the referenced file is in V6 or V7 format.

Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format.

ORA-26102: relative file # in file header is string rather than string for file string

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-26101: tablespace # in file header is string rather than string for file string

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-26099: direct path context is already prepared

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-26098: direct path context is not prepared

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-26097: unsupported conversion for column string (from type number to type number)

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-26096: transfer size too small for row data (number bytes required)

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-26095: unprocessed stream data exists

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-26094: stream format error: input column overflow

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-26093: input data column size (number) exceeds the maximum input size (number)

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-26092: only LONG or LOB types can be partial

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-26091: requested direct path operation not supported

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-26090: row is in partial state

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-26089: LONG column string must be specified last

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-26088: scalar column string must be specified prior to LOB columns

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-26086: direct path does not support triggers

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-26085: direct path operation must start its own transaction

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-26084: direct path context already finished

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-26083: unsupported direct path stream version string

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-26082: load of overlapping segments on table string.string is not allowed

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-26080: file string is not part of table string.string partition string

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-26079: file string is not part of table string.string

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-26078: file string is not part of database being loaded

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-26077: direct path column array is not initialized

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-26076: cannot set or reset value after direct path structure is allocated

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-26065: check constraint cannot reference column, string, in direct path load

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-26064: Invalid SCN specified - Wrap: string Base: string.

ORA-26064: Invalid SCN specified - Wrap: string Base: string.

Cause: User specified an invalid SCN.

Action: Specify a valid SCN.

ORA-26063: Can not flashback to specified SCN value - Wrap: string Base: string.

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-26062: Can not continue from previous errors.

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-26061: Concurrent direct unloads is not allowed.

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-26060: Can not convert type identifier for column string

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-26059: Data is too large for column string

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-26058: unexpected error fetching metadata for column string in table string

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-26057: Conversion is not necessary for this direct path stream.

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-26056: Requested direct path operation on a view is not supported.

ORA-26056: Requested direct path operation on a view is not supported.

Cause: User attempted to unload or load from or into a view via direct path.

Action: Unload from or load into a normal table.

ORA-26055: Invalid buffer specified for direct path unload

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-26054: Direct Path Context prepared for a different mode than operation requested.

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-26053: Row was not loaded due to conversion error.

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-26052: Unsupported type number for SQL expression on column string.

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-26051: internal error parsing packed decimal format string

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-26050: Direct path load of domain index is not supported for this column type.

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-26049: Unscoped REF column has non-existent table name.

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-26048: Scoped REF column has wrong table name.

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-26046: REF column string expects scoped table name string; user passed in string.

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-26045: REF column string expects string arguments; found string.

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-26041: DATETIME or INTERVAL datatype conversion error

ORA-26041: DATETIME or INTERVAL datatype conversion error

Cause: The column could not be converted from DATETIME * datatype to internal DATETIME or CHARACTER datatype.

Action: Contact Oracle Customer Support.

ORA-26040: Data block was loaded using the NOLOGGING option

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 or UNRECOVERABLE option

Action: Drop the object containing the block.

ORA-26036: subpartition load specified but table string is not subpartitioned

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-26035: Error attempting to encrypt or decrypt column

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-26034: Column string does not exist in stream

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-26033: column string.string encryption properties differ for source or target table

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-26032: index string.string loading aborted after string keys

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-26031: index maintenance error, the load cannot continue

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-26030: index string.string had string partitions made unusable due to:

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-26029: index string.string partition string initially in unusable state

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-26028: index string.string initially in unusable state

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-26027: unique index string.string partition string initially in unusable state

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-26026: unique index string.string initially in unusable state

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-26025: SKIP_INDEX_MAINTENANCE option requested

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-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable

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-26023: index string.string partition string was made unusable due to:

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-26022: index string.string was made unusable due to:

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-26021: index string.string partition string loaded successfully with string keys

ORA-26021: index string.string partition string loaded successfully with string keys

Cause: Partitioned index information put to loader log file.

Action: None. Information only.

ORA-26020: index string.string loaded successfully with string keys

ORA-26020: index string.string loaded successfully with string keys

Cause: Non-partitioned index information put to loader log file.

Action: None. Information only.

ORA-26019: Column string in table string of type string not supported by direct path

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-26018: Column string in table string does not exist

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-26017: global indexes not allowed for direct path load of table partition string

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-26015: Array column string in table string is not supported by direct path

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-26014: unexpected error on string string while retrieving string string

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-26013: List allocated may not be big enough

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-26011: Cannot load type string into column string in table string

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-26010: Column string in table string is NOT NULL and is not being loaded

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-26008: Invalid syntax or bind variable in SQL string for column string. string

ORA-26008: Invalid syntax or bind variable in SQL string for column string. string

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-26007: invalid value for SETID or OID column

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-26006: Incorrect bind variable in column string s sql expression -string

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-26005: Invalid handle for direct path load

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-26004: Tables loaded through the direct path may not be clustered

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-26003: parallel load not supported for index-organized table string.

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-26002: Table string has index defined upon it.

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-26001: Index string specified in SORTED INDEXES does not exist on table string

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-26000: partition load specified but table string is not partitioned

ORA-26000: partition load specified but table string is not partitioned

Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned.

Action: Remove the partition specification from the SQL*Loader control file and retry the load.

ORA-25966: join index cannot be based on an index organized table

ORA-25966: join index cannot be based on an index organized table

Cause: An attempt to create a join index was made, which failed because one of the tables was an index organized table.

Action: Ensure no underlying tables are index organized.

ORA-25965: fact table must be included in the from clause

ORA-25965: fact table must be included in the from clause

Cause: An attempt to create a join index was made, which failed because the from clause does not contain the fact table.

Action: Ensure that the from clause contains the fact table.

ORA-25964: column type incompatible with join column type

ORA-25964: column type incompatible with join column type

Cause: The datatype of the join column is incompatible with the datatype of the joined column.

Action: Select a compatible datatype for the join column.

ORA-25963: join index must be created on tables

ORA-25963: join index must be created on tables

Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.

Action: Ensure that the from clause only contains tables.

ORA-25962: join index prevents multitable insert or merge

ORA-25962: join index prevents multitable insert or merge

Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.

Action: Drop the join index.

ORA-25961: join index prevents dml cascade constraint operation

ORA-25961: join index prevents dml cascade constraint operation

Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.

Action: Drop the join index or remove the constraint.

ORA-25960: join index cannot be based on a temporary table

ORA-25960: join index cannot be based on a temporary table

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

Action: Ensure no underlying tables are temporary.

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

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

Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.

Action: Make the index a bitmap index.

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

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

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

Action: Ensure that the where clause only contains columns.

ORA-25957: join index where clause cannot contain cycles

ORA-25957: join index where clause cannot contain cycles

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ORA-25953: join index cannot be a functional index

ORA-25953: join index cannot be a functional index

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

Action: Remove any functional indexing columns.

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

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

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

Action: Remove the inappropriate predicate.

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

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

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

Action: Reformulate the where clause without using ORs.

ORA-25950: missing where clause in join index specification

ORA-25950: missing where clause in join index specification

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

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

ORA-25534: _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified

ORA-25534: _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified

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

Action: No action required.

ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified

ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified

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

Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0

ORA-25532: MTTR specified is too large: string

ORA-25532: MTTR specified is too large: string

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

Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.

ORA-25531: MTTR specified is too small: string

ORA-25531: MTTR specified is too small: string

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

Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.

ORA-25530: FAST_START_MTTR_TARGET is not specified

ORA-25530: FAST_START_MTTR_TARGET is not specified

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

Action: Set FAST_START_MTTR_TARGET.

ORA-25528: too many candidate MTTRs are specified in _DB_MTTR_SIM_ TARGET

ORA-25528: too many candidate MTTRs are specified in _DB_MTTR_SIM_ TARGET

Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.

Action: Alter the value of _DB_MTTR_SIM_TARGET.

ORA-25527: bad format of _DB_MTTR_SIM_TARGET

ORA-25527: bad format of _DB_MTTR_SIM_TARGET

Cause: One value in _DB_MTTR_SIM_TARGET is empty.

Action: Set the value of _DB_MTTR_SIM_TARGET properly.

ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string

ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string

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

Action: Alter the value of _DB_MTTR_SIM_TARGET.

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

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

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

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

ORA-25508: database is not mounted

ORA-25508: database is not mounted

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

Action: Mount the database and retry this command.

ORA-25507: resource manager has not been continuously on

ORA-25507: resource manager has not been continuously on

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

Action: none

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

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

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

Action: none

ORA-25505: the system is not in quiesced state

ORA-25505: the system is not in quiesced state

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

Action: none

ORA-25504: the system is already in quiesced state

ORA-25504: the system is already in quiesced state

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

Action: none

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

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

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

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

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

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

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

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

ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed

ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed

Cause: Database resource manager failed to change plan.

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

ORA-25500: database is not open

ORA-25500: database is not open

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

Action: Open the database and retry this command.

ORA-25473: cannot store string in rule action context

ORA-25473: cannot store string in rule action context

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

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

ORA-25472: maximum open iterators exceeded

ORA-25472: maximum open iterators exceeded

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

Action: Close some rule hit iterators.

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

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

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

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

ORA-25470: duplicate attribute value for variable: string

ORA-25470: duplicate attribute value for variable: string

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

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

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

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

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

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

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

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

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

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

ORA-25467: table alias not specified

ORA-25467: table alias not specified

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

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

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

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

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

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

ORA-25465: variable name not specified

ORA-25465: variable name not specified

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

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

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

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

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

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

ORA-25463: table alias not specified

ORA-25463: table alias not specified

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

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

ORA-25462: evaluation context not specified

ORA-25462: evaluation context not specified

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

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

ORA-25461: rule set not specified

ORA-25461: rule set not specified

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

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

ORA-25457: evaluation function string returns failure

ORA-25457: evaluation function string returns failure

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

Action: Check arguments to evaluate and retry.

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

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

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

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

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

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

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

Action: Check additional errors signalled to determine the problem.

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

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

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

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

ORA-25453: invalid iterator: string

ORA-25453: invalid iterator: string

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

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

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

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

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

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

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

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

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

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

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

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

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

Action: Check the error and take appropriate action.

ORA-25449: invalid variable name: string

ORA-25449: invalid variable name: string

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

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

ORA-25448: rule string.string has errors

ORA-25448: rule string.string has errors

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

Action: Check the rule and retry the operation.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ORA-25440: invalid table alias: string

ORA-25440: invalid table alias: string

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

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

ORA-25439: duplicate variable value for variable: string

ORA-25439: duplicate variable value for variable: string

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

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

ORA-25438: invalid variable name: string

ORA-25438: invalid variable name: string

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

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

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

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

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

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

ORA-25436: invalid table alias: string

ORA-25436: invalid table alias: string

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

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

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

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

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

Action: Drop the database links before attempting the downgrade.

ORA-25426: remote instance does not support shared dblinks

ORA-25426: remote instance does not support shared dblinks

Cause: A shared dblink is being used to connect to a remote instance that does not support this feature because it is an older version.

Action: Use a normal dblink if you need to connect to this instance.

ORA-25425: connection lost during rollback

ORA-25425: connection lost during rollback

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

Action: The connection was lost and failover happened during rollback. If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine pending_trans$ to determine if rollback force is required.

ORA-25409: failover happened during the network operation,cannot continue

ORA-25409: failover happened during the network operation,cannot continue

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

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

ORA-25408: can not safely replay call

ORA-25408: can not safely replay call

Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.

Action: Check to see if the results of the call have taken place, and then replay it if desired.

ORA-25407: connection terminated

ORA-25407: connection terminated

Cause: The connection was lost while doing a fetch.

Action: This is an internally used error message and should not be seen by the user.

ORA-25406: could not generate a connect address

ORA-25406: could not generate a connect address

Cause: Failover was unable to generate an address for a backup instance.

Action: Contact Oracle customer support.

ORA-25405: transaction status unknown

ORA-25405: transaction status unknown

Cause: A failure occured while a transaction was attempting to commit. Failover could not automatically determine instance status.

Action: The user must determine the transaction s status manually.

ORA-25404: lost instance

ORA-25404: lost instance

Cause: The primary instance has died.

Action: This is an internally used error message and should not be seen by the user.

ORA-25403: could not reconnect

ORA-25403: could not reconnect

Cause: The connection to the database has been lost, and attempts to reconnect have failed.

Action: Manually reconnect.

ORA-25402: transaction must roll back

ORA-25402: transaction must roll back

Cause: A failure occured while a transaction was active on this connection.

Action: The client must roll back.

ORA-25401: can not continue fetches

ORA-25401: can not continue fetches

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

Action: Reexecute the statement and start fetching from the beginning

ORA-25400: must replay fetch

ORA-25400: must replay fetch

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

Action: This is an internally used error message and should not be seen by the user.

ORA-25353: branch marked for deletion

ORA-25353: branch marked for deletion

Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed.

Action: No action is required for the branch to be deleted.

ORA-25352: no current transaction

ORA-25352: no current transaction

Cause: The user session is not attached to any transaction.

Action: Do not attempt to detach when there is no current transaction.

ORA-25351: transaction is currently in use

ORA-25351: transaction is currently in use

Cause: The transaction is currently used by a different session.

Action: Do not switch to a transaction attached to some other session.

ORA-25350: maximum number of concurrent transaction branches exceeded

ORA-25350: maximum number of concurrent transaction branches exceeded

Cause: the limit on the number of concurrent transaction branches has been reached

Action: Increase the INIT.ORA parameter transactions and restart the system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Action: Use single enqueue or dequeue with this queue.

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

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

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

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

ORA-25327: Array size is invalid

ORA-25327: Array size is invalid

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

Action: Use corrected array size and retry array operation.

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

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

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

Action: Fix cause of error and retry array operation.

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

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

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

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

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

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

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

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

ORA-25315: unsupported configuration for propagation of buffered messages

ORA-25315: unsupported configuration for propagation of buffered messages

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

Action: Use queue to queue propagation for buffered messages.

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

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

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

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

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

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

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

Action: Provide a valid subscriber and retry the operation.

ORA-25312: Cannot specify nonzero sender protocol

ORA-25312: Cannot specify nonzero sender protocol

Cause: Sender protocol was specified during an enqueue operation.

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

ORA-25311: %s not supported for non-persistent queue

ORA-25311: %s not supported for non-persistent queue

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

Action: Specify the right QOS.

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

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

Cause: Notification only subscribers are not allowed to dequeue.

Action: Recreate subscriber if necessary.

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

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

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

Action: Try enqueue after sleeping for some time.

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

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

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

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

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

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

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

Action: Set expiration to zero.

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

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

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

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

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

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

Cause: Operation was not performed on the owner instance.

Action: Perform operation on the owner instance.

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

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

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

Action: The operation is not supported.

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

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

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

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

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

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

Cause: Cannot drop buffer for queue with buffered subscribers

Action: Either drop buffered subscribers or forcibly drop the buffer

ORA-25299: Invalid message delivery_mode

ORA-25299: Invalid message delivery_mode

Cause: Invalid value was specified for delivery mode

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

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

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

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

Action: Supply a visibility of dbms_aq.IMMEDIATE

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

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

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

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

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

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

Cause: Subscriber is only allowed to dequeue persistent messages

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

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

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

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

Action: Do not propagate buffered messages to the database.

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

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

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

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

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

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

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

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

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

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

Cause: Buffer does not exist for the specified queue

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

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

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

Cause: Queue already has messages. Cannot complete operation

Action: Truncate the queue before adding or dropping a buffer

ORA-25289: Buffer Already Exists

ORA-25289: Buffer Already Exists

Cause: Buffer already exists for the specified queue.

Action: None

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

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

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

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

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

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

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

Action: Specify a non negative integer.

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

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

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

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

ORA-25285: Invalid value string for array_mode

ORA-25285: Invalid value string for array_mode

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

Action: Check the documentation for valid values.

ORA-25284: Invalid value string for string

ORA-25284: Invalid value string for string

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

Action: Check the documentation for valid values.

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

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

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

Action: Provide the agent info.

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

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

Cause: message id. was not provided

Action: Provide the message id.

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

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

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

Action: Provide the complete reciever information

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

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

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

Action: Provide the complete sender information

ORA-25279: dequeue as select not supported before 8.2

ORA-25279: dequeue as select not supported before 8.2

Cause: Dequeue as select not supported before 8.2.

Action: Dont use select condition while dequeuing

ORA-25278: grantee name cannot be NULL

ORA-25278: grantee name cannot be NULL

Cause: An attempt was made to specify NULL for the grantee parameter.

Action: Specify a valid grantee parameter.

ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible queues

ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible queues

Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.

Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege.

ORA-25276: table specified is not a queue table

ORA-25276: table specified is not a queue table

Cause: An invalid queue table name is specified.

Action: Check the dictionary views to see if the table is a queue table.

ORA-25275: Test support for buffered queues

ORA-25275: Test support for buffered queues

Cause: internal use only

Action: none.

ORA-25274: AQ Buffered Queue event

ORA-25274: AQ Buffered Queue event

Cause: N or A.

Action: event used for AQ Buffered Queue mode.

ORA-25273: AQ QMN process alternate cleanup event

ORA-25273: AQ QMN process alternate cleanup event

Cause: N or A.

Action: event used for AQ QMN alternate cleanup mode.

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

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

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

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

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

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

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

Action: Provide the right queue name

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

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

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

Action: Try dequeue again without the signature in dequeue options

ORA-25269: cant specify sognature with get signature option

ORA-25269: cant specify sognature with get signature option

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

Action: Try dequeue again without the signature in dequeue options

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

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

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

Action: Try dequeue again in browse mode

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

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

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

Action: Try dequeue again along with the signature

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

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

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

Action: Try dequeue again by message id.

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

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

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

Action: Try dequeue again without the signature

ORA-25264: cant get signature for this queue

ORA-25264: cant get signature for this queue

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

Action: Try dequeue again without the get signature option

ORA-25263: no message in queue string.string with message ID string

ORA-25263: no message in queue string.string with message ID string

Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue.

Action: Try dequeue again with a valid message ID.

ORA-25262: agent name cannot be NULL if address is a multi-consumer queue

ORA-25262: agent name cannot be NULL if address is a multi-consumer queue

Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue.

Action: Specify a non-NULL name for the agent.

ORA-25261: JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation

ORA-25261: JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation

Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.

Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation.

ORA-25260: AQ latch cleanup testing event

ORA-25260: AQ latch cleanup testing event

Cause: N or A.

Action: event used for AQ statistics latch cleanup testing.

ORA-25259: cannot specify protocol for agent

ORA-25259: cannot specify protocol for agent

Cause: The user specified the protocol attribute for an agent in the agent list.

Action: Do not specify the protocol attribute of the agent object type.

ORA-25258: cannot register for notifications on an 8.0 style exception queue

ORA-25258: cannot register for notifications on an 8.0 style exception queue

Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.

Action: Specify a normal queue or a non-persistent queue.

ORA-25257: consumer must be specified with a multi-consumer queue

ORA-25257: consumer must be specified with a multi-consumer queue

Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string.

Action: Specify a consumer in the subscription string.

ORA-25256: consumer cannot be specified with a single-consumer queue or an exception queue

ORA-25256: consumer cannot be specified with a single-consumer queue or an exception queue

Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue.

Action: Do not specify the consumer in the subscription string.

ORA-25255: incorrect subscription string string

ORA-25255: incorrect subscription string string

Cause: An incorrect subscription string was specified with OCIRegister.

Action: Specify a subscription string using the (CONSUMER:(SCHEMA.QUEUE form.

ORA-25254: time-out in LISTEN while waiting for a message

ORA-25254: time-out in LISTEN while waiting for a message

Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.

Action: Try the LISTEN call with an appropriate time-out.

ORA-25253: listen failed, queue string.string is not enabled for dequeue

ORA-25253: listen failed, queue string.string is not enabled for dequeue

Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.

Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call.

ORA-25252: listen failed, the address string is a non-persistent queue

ORA-25252: listen failed, the address string is a non-persistent queue

Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.

Action: Specify a normal queue as address for the agent, and retry the the LISTEN call.

ORA-25251: exceeded maximum number of recipients for message

ORA-25251: exceeded maximum number of recipients for message

Cause: An attempt was made to issue an ENQUEUE call that exceeded the the maximum number (1024) of recipients per message.

Action: Reduce the number of recipients to 1024 or less, and retry the call.

ORA-25250: Cannot specify a remote recipient for the message

ORA-25250: Cannot specify a remote recipient for the message

Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.

Action: Do not specify the address field or specify the queue which is the target of the enqueue

ORA-25249: dequeue failed, dequeue not allowed for queue string.string

ORA-25249: dequeue failed, dequeue not allowed for queue string.string

Cause: An attempt was made to dequeue from a non-persistent queue.

Action: Dequeue from a different queue.

ORA-25248: duplicate agent specified in the agent list

ORA-25248: duplicate agent specified in the agent list

Cause: An agent was specified more than once in the agent list of the LISTEN call.

Action: Remove the duplicate agent specification(s), and retry the call.

ORA-25247: %s is not a recipient of specified message

ORA-25247: %s is not a recipient of specified message

Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message id.

Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message id.

ORA-25246: listen failed, the address string is an 8.0 style exception queue

ORA-25246: listen failed, the address string is an 8.0 style exception queue

Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.

Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.

ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue

ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue

Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.

Action: Do not specify the agent name.

ORA-25244: dequeue index key not found, QUEUE string, rowid string

ORA-25244: dequeue index key not found, QUEUE string, rowid string

Cause: An internal error was encountered. There may be an inconsistency in the queue table index.

Action: Contact your Oracle customer support representative. You may need to provide the trace file and information about reproducing the error.

ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.

Action: Specify only the message id in the dequeue options to dequeue a message from an exception queue.

ORA-25242: cannot change subscriber name from string to string without FIRST_ MESSAGE option

ORA-25242: cannot change subscriber name from string to string without FIRST_ MESSAGE option

Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.

Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.

ORA-25241: cannot change correlation ID from string to string without FIRST_ MESSAGE option

ORA-25241: cannot change correlation ID from string to string without FIRST_ MESSAGE option

Cause: An attempt was made to change the correlation ID while using the NEXT_ MESSAGE or NEXT_TRANSACTION option for dequeuing.

Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.

ORA-25240: message ID and dequeue condition or correlation ID specified in dequeue options

ORA-25240: message ID and dequeue condition or correlation ID specified in dequeue options

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

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