SQL*Loader-00307: Warning: conflicting lengths number and
number specified for column string table string
- 1 Answers
- 3375 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The SQL*Loader control file specifies two different
lengths for the named column. There are three ways to
specify the length of a field: --with the POSITION keyword:
POSITION(1:3) -- with the length specifier: CHAR(6) -- with
the implied length of a datatype; for example, INTEGER -- A
conflict could occur between any two of these specifications
(or among all three, but only two are shown). A common cause
of this error is the specification of some numeric datatype,
such as INTEGER, when the numeric external form is intended
(INTEGER EXTERNAL). The external form consists of character
data, so it is considerably longer than the numeric form,
which consists of binary data.
Action: No action is necessarily required, because
SQL*Loader uses only one of the lengths. Check the log file
under the heading "Len" in the table-description section to
see which length was used. Adjusting the SQL*Loader control
file to produce uniform length specifications will remove
the warning.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
ORA-07415: slpath: allocation of memory buffer failed.
ORA-06557: null values are not allowed for any parameters to pipe icd's
ORA-29812: incorrect object name specified
RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE
ORA-34276: (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
ORA-30945: Could not create mapping table 'string'
SQL-02113: Unable to open message file
ORA-28508: invalid value string for Heterogeneous Services initialization parameter string
ORA-00397: instance recovery process terminated with error
SQL*Loader-00622: Column not found before end of logical record (use TRAILING NULLCOLS)
ORA-29298: Character set mismatch
ORA-36772: (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
Oracle Errors 
