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.