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

ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area

1 Answers  

---

ORA-13185: failed to generate initial HHCODE

1 Answers  

---

DRG-11725: phrase does not have any synonyms

1 Answers  

---

ORA-09884: Two Task interface: SID doens't match current PU

1 Answers  

---

NNL-00403: Number of answers: number

1 Answers  

---

ORA-12024: materialized view log on "string"."string" does not have primary key columns

1 Answers  

---

ORA-08440: raw buffer is too short to hold converted data

1 Answers  

---

ORA-32618: incorrect use of MODEL PREVIOUS function

1 Answers  

---

RMAN-06598: conversion between platforms 'string' and 'string' is not needed

1 Answers  

---

ORA-15169: destination 'string' is a subdirectory of 'string'

1 Answers  

---

LRM-00121: 'string' is not an allowable value for 'string'

1 Answers   TCS,

---

ORA-02155: invalid DEFAULT tablespace identifier

2 Answers  

---