Re: SQL*Loader-510: Physical record is longer than 1M

Hi,

Try to place CLOBs to separate files and use .ctl file like this:

LOAD DATA
INFILE 'employees.txt'
INTO TABLE employees
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' TRAILING NULLCOLS (EMPLOYEEID,
 LASTNAME,
 FIRSTNAME,
 PHOTO_FILE FILLER,
 PHOTO LOBFILE (PHOTO_FILE) TERMINATED BY EOF NULLIF PHOTO_FILE='', )

FILLER field is used to specify filenames where CLOB is located

---
Best regards, Dmitry
www.ispirer.com - Database migration tool for Oracle, IBM DB2.

"lei wang" <leiwang_q_at_hotmail.com> wrote in message
news:af074b9c.0111150915.3db4de68_at_posting.google.com...


> I was using SQL*Loader to load data from a text file. The table has a

> CLOB column, and the data of CLOB itself is longer than 1M. SQL*Loader

> gave me this serror:

>

> SQL*Loader-510: Physical record in data file(mytable.dat) is longer

> than the maximum(1048576).

>

> I was using Oracle 8i (8.1.7) Enterprise Edition on Solaris 2.7. I

> tried to use bindsize in command line, but it did not work. Is there a

> way to load data longer than 1M?

>

> The control look like:

>

> load data

> infile 'mytable.dat' "str '<endrec>'"

> into table mytable

> fields terminated by x'07'

> trailing nullcols

> (akey char(40),

> adate date 'DD/MM/YYYY',

> atag ,

> aclob char(1024000),

> aversion)

>

>

> I tried to incease the size of clob in control file, but did not work.

>

> Thanks.