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-15109: conflicting protection attributes specified

1 Answers  

---

DRG-11879: Automatic Proxy Redirection Msut Be Explicitly Acknowledged

1 Answers  

---

ORA-19551: device is busy, device type: string, device name: string

1 Answers  

---

PROT-00008: Failed to import data from specified file to the cluster registry

1 Answers  

---

AMD-00108: Dimension "string" is improperly mapped; the dimension has string hierarchies mapped, but hierarchy level "string" has string columns mapped

1 Answers  

---

SQL*Loader-00280: table string is a temporary table

1 Answers  

---

TNS-00297: Logging Level : string

1 Answers  

---

ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom

1 Answers  

---

TNS-02507: Encryption: algorithm not installed

1 Answers  

---

TNS-12160: TNS:internal error: Bad error number

1 Answers  

---

ORA-23346: primary key or object ID is undefined for table or materialized view string

1 Answers  

---

IMG-02008: 2FF08 - color histogram feature cannot be determined

1 Answers  

---