Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 02351-02375: SQL*Loader in Direct Path Mode Messages

This section lists messages generated when the direct path mode is used to load data into the database. See also range ORA-02476 to ORA-02479 in 02476-02479: Parallel Direct Loader Messages on page -16 for parallel direct path loader messages.

##### ORA-02351: record num: Rejected - Error on table name, column name

Cause: The indicated record caused an error on insert.

Action: Determine the error and correct the record.

##### ORA-02352: direct path connection must be homogeneous

Cause: The user-side to kernel-side connection is heterogeneous.

Action: Check that the connection is between identical hardware and operating systems.

##### ORA-02353: multi-byte character error

Cause: The text specified by POSITION or terminated by new lines is invalid.

Action: Edit the control file or the datafile to fix the alignment of the column.

##### ORA-02354: conversion initialization error occurred on field name

Cause: An error occurred during conversion initialization for a field.

Action: This is an internal error. Contact customer support.

##### ORA-02355: conversion error occurred on CONSTANT field str

Cause: A CONSTANT field caused an error. All rows will be rejected.

Action: Determine the Oracle error and correct the record.

##### ORA-02356: the database is out of space. The load cannot continue

Cause: The load was discontinued due to space exhaustion in the database.

Action: Add space for the specified table.

##### ORA-02357: packed decimal conversion error

Cause: The column could not be converted from packed decimal to character.

Action: Check the column and make it conform to packed decimal format.

##### ORA-02358: zoned decimal conversion error

Cause: The column could not be converted from packed decimal to character.

Action: Check the column and make it conform to packed decimal format.

##### ORA-02359: field in datafile exceeded maximum specified length

Cause: The field is too long for the specified column.

Action: Shorten the field so that the length of the field equals or is less than the column length.

##### ORA-02360: column not found before end of logical record (use TRAILING NULLCOLS)

Cause: A column started after the end of the logical record had been reached.

Action: Use the TRAILING NULLCOLS option or supply data for the column.

##### ORA-02361: initial enclosing character not found

Cause: The initial enclosing character of an enclosed field was not found.

Action: Supply the character before the start of the field.

##### ORA-02362: logical record ended - second enclosing character not present

Cause: The second enclosing character of an enclosed field was not found.

Action: Supply the character after the end of the field.

##### ORA-02363: no terminator found after TERMINATED and ENCLOSED field

Cause: No terminator was found after a terminated and enclosed field.

Action: Supply the terminator after the end of the field.

##### ORA-02364: record num: Discarded - failed all WHEN clauses

Cause: The record was not loaded because it failed the WHEN clauses of all the tables.

Action: No action required.

##### ORA-02365: index name was left in Direct Load State due to

Cause: The index was not loaded. The cause of the error is stated after the message.

Action: Correct the cause of the error, then reload.

##### ORA-02366: the following index or indexes on table name were processed

Cause: The indexes listed for the named table were loaded.

Action: No action required.

##### ORA-02367: index name was loaded

Cause: The index specified in the message was loaded.

Action: No action required.

##### ORA-02368: record num: Discarded - all columns null.

Cause: The record was not loaded because all of the columns in the table were null for that record.

Action: No action required.

##### ORA-02369: warning: Variable-length field was truncated

Cause: A variable-length field was truncated by the end of the logical record.

Action: Although this is a warning, a variable length field has the length embedded in the data for each row, so check the data.

##### ORA-02370: record num - Warning on table name, column num

Cause: The record indicated caused a warning.

Action: Determine the warning and correct the record, if necessary.

##### ORA-02371: loader must be at least version num for direct path

Cause: The version of SQL*Loader being used is incompatible with this version of Oracle.

Action: Upgrade the version of SQL*Loader to at least the specified version or use the conventional path.

##### ORA-02372: relative start position > absolute field end position

Cause: The relative start of a field specified as POSITION(*+n:y) occurred after the absolute position y.

Action: Check that the values of n and y are correct and that the statement was entered correctly. Also check that all opening delimiters have matching closing delimiters.

##### ORA-02373: error parsing insert statement for table name

Cause: A parsing error occurred.

Action: Check the message following this parsing error message.

##### ORA-02374: no more slots for read buffer queue

Cause: There are no free read buffers.

Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers.

##### ORA-02375: record num: Rejected - Error on table 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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index