Re: SQL*Loader Column Widths

From: Mark Prebilic <mprebilic_at_winstar.com>
Date: Thu, 11 Nov 1999 14:04:26 -0500
Message-ID: <382B1339.63648F09@winstar.com>

Pete,
I've run across this problem before and I was able to solve it by explicitly indicating a size in the fields clause of the control file. I'm not sure why that works, but who can argue with success? Here's an example where the where_clause field is larger than 257:

LOAD DATA
INFILE *
DISCARDFILE 'ld_mfsc_mapping_layout.dis' LOG YES
INTO TABLE LKP_MAPPING_LAYOUT
APPEND
FIELDS TERMINATED BY '#' TRAILING NULLCOLS (
-- FIELD_ID (Note: using SEQUENCE in the database)  RECORD_TYPE_ID INTEGER EXTERNAL,
 INVOICE_TYPE_CODE,
 FILE_NAME,
 CT_ID_COL,
 CID_ID_COL,
 CDD_TEXT_COL,

 CD_TEXT_COL,
 CC_TEXT_COL,
 CO_ID_COL,
 CT_COL_ID_COL,

 IMPORT_VALUE_COL,
 IIR_VALUE,
 DRIVING_TABLE,
 DB_TABLES,

 WHERE_CLAUSE char(500),
 WHERE_TEXT,
 GROUP_BY_TEXT,

 HINT_TEXT
)
BEGINDATA Mark Prebilic
PrebSon Consulting

Pete Kolton wrote:

> I can't believe I've not come across this problem before, but it is a while
> since I used Loader and maybe I never used it to load large columns, but...
>
> It seems that I can only load fields that are up to 257 characters long,
> despite the fact that the column is varchar2(1000).
>
> Any one know why this would be?
Received on Thu Nov 11 1999 - 13:04:26 CST