* was in unusable state prior to the beginning of the load.
* or index partition, or re-create the index.
* index maintenance skipped via SKIP_UNUSABLE_INDEXES).
* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
* cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
* path load, it cannot be maintained by the loader.
* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
* of a direct path load, it cannot be maintained by the loader.
* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
* affected one or more index partitions, which are listed below
* this message.
* entire index dropped and re-created.
* Loading had to be aborted. No rows were loaded.
* This key caused the index problem mentioned in an earlier message. *
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.
* using the direct path mode, or use the conventional path mode
* instead.
* 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)
* - 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
* function context before allocating a column array for the
* table-level direct path context.
* via OCIHandleAlloc before allocating column arrays for
* direct path function contexts.
* 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).
* operations on the same table, but the segments overlap.
* 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.
* OCIDirPathFinish was called. Once a direct path operaton
* has been finished, no more data can be loaded.
* not called after OCIDirPathFinish.
* specified by the client of the direct path API prior to
* specifying any LOB columns.
* 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.
* 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.
* 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.)
* transfer buffer size (if you did not specify a size), is
* too small to contain a single row of the converted row data.
* context to be larger.
1. The directory exists.
2. The name indeed points to a directory and not a file.
3. The directory is accessible and writable to the ORACLE user.