Oracle7 Server Messages

00400-00499: Columns

SQL*Loader-401 end field position num must be greater than or equal to start num

Cause: The named field contains a (start:end) clause in which end is less than start.

Action: Modify the clause so that end is greater than or equal to start.
SQL*Loader-402 unable to determine length of column name.name from specification

Cause: The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a POSITION clause.

Action: If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form

POSITION(start:end)

A length can also specified after the datatype, as in

INTEGER EXTERNAL (6)

Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length. SQL*Loader-403 referenced column name not present in table name

Cause: The named column is not present in the given table.

Action: Correct the column name or table name.
SQL*Loader-404 column name present more than once in table name

Cause: The named column is specified more than once in a single INTO TABLE statement.

Action: Remove the extraneous column specification.
SQL*Loader-405 need termination delim with optional enclosure delim: column name.name

Cause: The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.

Action: Specify a termination delimiter or make the enclosure delimiters non-optional.
SQL*Loader-406 if data is all generated, number to load cannot be ALL

Cause: When only generated data is loaded, a number to load must be given so SQL*Loader knows when to stop.

Action: Specify a number to load.
SQL*Loader-407 if data is all generated, number to skip is meaningless

Cause: When all data is generated, no file is read, and there are no records to skip.

Action: Remove the number to skip.
SQL*Loader-408 physical record stack overflow

Cause: An internal error has occurred.

Action: Contact customer support.
SQL*Loader-409 number to skip must be table-level, not load-level on continued loads

Cause: The SKIP parameter was specified on the command line or in the OPTIONS statement, but the load was specified as continued with CONTINUE_LOAD.

When a multiple-table direct load is interrupted, it is possible that a different number of records were loaded into each table. As a result, the number of records to skip must be specified for each table when continuing the load. In this case, the load is specified as continued with the CONTINUE_LOAD statement, and the number of records to skip is given in each INTO TABLE statement.

See also messages 410 and 411 for more information.

Action:

Check the log file to determine the appropriate number of records to skip for each table and specify this number in the INTO TABLE statement for each table in a continued load or with the command-line SKIP parameter in a standard load.

SQL*Loader-410 number to skip must be load-level, not table-level

Cause: A SKIP clause was found in the INTO TABLE statement of a standard (non-continued) load.

In a standard load, specified with LOAD DATA, it is not possible to skip a different number of records for each table. The number of records to skip must be specified for the entire load by using the SKIP parameter on the command line or in the OPTIONS clause.

If table-level skip is required, because a different number of records were loaded into each table (only possible for a multiple-table direct load), then specify a continued load with the CONTINUE_LOAD statement.

See also messages 409 and 411 for more information.

Action:

If the load was not a multiple-table, direct path load, then move the SKIP clause from the INTO TABLE statements to the command line or to the OPTIONS clause. Otherwise, specify the load as continued with CONTINUE_LOAD.

SQL*Loader-411 only a direct path load may be continued

Cause: The load is specified with CONTINUE_LOAD, but DIRECT=FALSE. CONTINUE_LOAD is only possible for a direct path load and is only necessary for a multiple-table, direct path load when a different number of records have been loaded into each table.

See also messages 409 and 410 for more information.

Action:

If CONTINUE_LOAD is necessary, specify a direct load and put the number of records to skip in each INTO TABLE statement. Otherwise, use the command line or OPTIONS clause to specify the number of records to skip and use LOAD DATA instead of CONTINUE_LOAD.

SQL*Loader-412 more columns specified for table name than the maximum num

Cause: More columns were specified for the table than the maximum number allowed by the database.

Action: Remove the extraneous columns.
SQL*Loader-413 maximum number of constraints num exceeded on table name

Cause: An internal error has occurred.

Action: Contact customer support.
SQL*Loader-414 maximum number of triggers num exceeded on table name

Cause: An internal error has occurred.

Action: Contact customer support.
SQL*Loader-415 unimplemented database column type num on column name

Cause: An internal error has occurred.

Action: Contact customer support.
SQL*Loader-417 SQL string (on column name) not allowed in direct path

Cause: Because the direct path bypasses SQL processing, the SQL string cannot be used.

Action: Remove the SQL string or use the conventional path.
SQL*Loader-457 comparison text str of CONTINUEIF LAST must have length 1 not num

Cause: The comparison text is too long. It can only be one character.

Action: Reduce the comparison text to one character.
SQL*Loader-458 comparison text of CONTINUEIF LAST must be non-whitespace

Cause: The comparison text is a whitespace character (blank or tab).

Action: Change the comparison text to a non-whitespace character.