Workaround for 1023 byte limit in utl_file

Question

I am looking for a work-around for the 1023 byte limit in PL/SQL's utl_file.put_line.
Here's what I need to be able to do :
I need to extract all columns out of a table into a file. Two of the columns are varchar 2000 bytes.
I am using utl_file.put_line to write out the record to a file.
I get a SQLCODE:1 SQLERRM: User-Defined Exception when extracting certain records out.
Looking at the data that's causing the problem, I see that the 2000 byte columns contain data with length greater than 1000 bytes.
I tried extracting the data using a series of utl_file.put, but that does not help either as it generates the same error after it put's the 2000 byte column.
I need the entire record in a single file, as it needs to be used as input to SQLLOAD.
I tried overloading the fopen with buffer size 32000 and the compiler accepts the overload. However it does not seem to have any effect at run-time.
We are at Oracle 8.0.5.1.0.
Anyone with a work-around/tip??
Thanks in advance.
null

Answer 1

Thanks to all who replied, really appreciate your assistance.
I tried the suggestions of using utl_file.put in a loop to split the input record. I still get the same error message [SQLCODE: 1 SQLERRM: User-Defined Exception ]
The code I am using is as follows :
declare
outfile utl_file.file_type;
cursor c1 is
select col1| |delim| |col2| |.....
from tbl
where ....;
vBuf varchar2(32000);
vMaxLineSize number := 1023;
begin
outfile := utl_file.fopen('/tmp','outfil','w',32000);
open c1;
loop
fetch c1
into vBuf;
exit when c1%NOTFOUND;
begin
vStart := 0;
if length(vBuf) >= vMaxLineSize then
for i in 1..ceil(length(vBuf) / vMaxLineSize)
loop
utl_file.put(outfile,substr(vBuf,vStart+1,vMaxLineSize));
vStart := vMaxLineSize * i;
end loop;
utl_file.new_line(outfile);
else
utl_file.put_line(outfile,vBuf);
end if;
exception
when OTHERS then
utl_file.put_line(logFile,'Error: col1: '| |col1| |' SQLCODE: '| |SQLCODE| |' SQLERRM: '| |SQLERRM);
end;
end loop;
close c1;
utl_file.fclose_all;
end;
The error message occurs only for a few records as a result of which they are not extracted out. I looked at the data and there does not seem to be anything out of the ordinary with the records that errored out.
Perhaps there is some error in the code I am using, that hopefully someone else will be able to spot.
Thanks in advance.