Server Messages: ORA-02351 to ORA-29799

26000-26099: Direct Path Load Messages

ORA-26000: partition load specified but table name 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-26001: index name specified in SORTED INDEXES does not exist on table %s

Cause: A nonexistent index was specified in the SORTED INDEXES clause.

Action: Specify an existing index as a SORTED INDEX and retry the operation.

ORA-26002: table name has index defined upon it.

Cause: Parallel load was specified into a table which has an index defined on it.

Action: Do one of the following:

drop index(es) defined on the table
do not use parallel load
use SKIP_INDEX_MAINTENANCE option

ORA-26004: tables loaded through the direct path may not be clustered

Cause: An attempt was made to load a clustered table using the direct path.

Action: Retry the operation using the conventional path.

ORA-26007: for INSERT option, table must be empty. Error on table name

Cause: An attempt was made to use the INSERT option on a non-empty table.

Action: Empty the table from SQL*Plus, or use the REPLACE option.

ORA-26008: NOT NULL column name has a NULLIF clause

Cause: A column which is NOT NULL in the database has a SQL*Loader NULLIF clause on it.

Action: Remove the NULLIF clause in the SQL*Loader control file.

ORA-26009: NOT NULL column name has a DEFAULTIF clause which may evaluate to NULL

Cause: A column which is NOT NULL in the database has a SQL*Loader DEFAULTIF clause which may evaluate to NULL.

Action: Remove the DEFAULTIF clause in the SQL*Loader control file.

ORA-26010: column name in table name is NOT NULL and is not being loaded

Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.

Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file.

ORA-26011: tables loaded through the direct path may not be object tables

Cause: An attempt was made to load an object table using the direct path.

Action: Retry the operation using the conventional path.

ORA-26012: tables loaded through the direct path may not have object columns

Cause: User attempted to load a table with an object column using the direct path.

Action: Retry the operation using the conventional path.

ORA-26013: tables loaded through the direct path may not be nested

Cause: An attempt was made to load a nested table using the direct path.

Action: Retry the operation using the conventional path.

ORA-26014: tables loaded through the direct path may not have REF columns

Cause: An attempt was made to load a table with a REF column using the direct path.

Action: Retry the operation using the conventional path.

ORA-26015: tables loaded through the direct path may not have array columns

Cause: An attempt was made to load a table with an array column using the direct path.

Action: Retry the operation using the conventional path.

ORA-26016: record name: rejected - error on table name, partition name

Cause: The record indicated caused an ORACLE error on insert.

Action: Determine the ORACLE error and correct the record. The offending column(s) are not known.

ORA-26017: global indexes not allowed on direct path partition load, table name

Cause: Global indexes are defined on a table when direct path loading a single partition of the table.

Action: Remove the global index from the named table and retry the operation.

ORA-26018: column name in table name does not exist

Cause: The column specified in the loader control file does not exist.

Action: Ensure that the column exists and that you have privileges on it. Correct the loader control file if it is incorrect.

ORA-26019: column name in table name of type name not supported by direct path

Cause: The specified column of SQL column type name is not supported by the direct path loader.

Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL.

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

Cause: Non-partitioned index information was successfully added to the log file.

Action: No action required. This is an informational message only.

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

Cause: Partitioned index information was successfully added to the loader log file.

Action: No action required. This is an informational message only.

ORA-26022: index name.name was made unusable due to:

Cause: A non-partitioned index was made index unusable due to the error displayed in the accompanying error message.

Action: Depending on the error, either rebuild the index, or drop and re-create it.

ORA-26023: index name.name partition name was made unusable due to:

Cause: A partition of a partitioned index was made index unusable due to error displayed in the accompanying error message.

Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index.

ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable

Cause: The SKIP_UNUSABLE_INDEXES option was specified and the index segment was in an unusable state prior to the beginning of the load.

Action: This is an informational message only. You will need to do one of the following: rebuild the index or index partition re-create the index

ORA-26025: SKIP_INDEX_MAINTENANCE option requested

Cause: A request was made that index maintenance be skipped on a direct path load.

Action: The listed index was put into Index Unusable state due to a request that index maintenance be skipped. You will need to do one of the following:

rebuild the index or index partition
re-create the index

ORA-26026: unique index name.name initially in unusable state

Cause: A unique index is in IU state (a unique index cannot have index maintenance skipped by using the SKIP_UNUSABLE_INDEXES option).

Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.

ORA-26027: unique index name.name partition name initially in unusable state

Cause: A partition of a unique index is in IU state (a unique index cannot have index maintenance skipped by using the SKIP_UNUSABLE_INDEXES option).

Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.

ORA-26028: index name.name initially in unusable state

Cause: An index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.

Action: Either rebuild the index, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).

ORA-26029: index .name partition name 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 the index partition, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).

ORA-26030: index name.name had name 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 in an accompanying error message.

Action: The affected index partitions will have to be re-built, or, the entire index dropped and re-created.

ORA-26031: index maintenance error, the load cannot continue

Cause: A index error occurred during the index maintenance phase of a direct path load. The load cannot continue. See the accompanying error message.

Action: See the accompanying error message for more information.

ORA-26032: index name.name loading aborted after name 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.