Re: UTL_FILE.PUT_LINE
From: DA Morgan <damorgan_at_psoug.org>
Date: Wed, 05 Mar 2008 10:14:42 -0800
Message-ID: <1204740880.684008@bubbleator.drizzle.com>
>
> Had you taken the time to read the documentation on UTL_FILE you'd
> realize that the FOPEN call accepts a MAX_LINESIZE parameter, which,
> if not supplied, defaults to 1024:
>
> http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/u_file.htm#i1005018
>
> Examining Example 2 on that page explains much.
>
> The problem, therefore, isn't with the PUT_LINE call but in how you
> opened the file.
>
>
> David Fitzjarrell
max_linesize IN BINARY_INTEGER DEFAULT NULL) RETURN file_type;
Date: Wed, 05 Mar 2008 10:14:42 -0800
Message-ID: <1204740880.684008@bubbleator.drizzle.com>
fitzjarrell_at_cox.net wrote:
> On Mar 4, 1:18 pm, "ame..._at_iwc.net" <ame..._at_iwc.net> wrote:
>> Does UTL_FILE.PUT_LINE have a limitation on the length of the string >> you are printing to file? >> >> I have a variable declares, VARCHAR2(4000). I print it to a log >> file. However, I have figured out that if I print more than 1000 >> characters, the procedure just stops...... >> >> Anyone?
>
> Had you taken the time to read the documentation on UTL_FILE you'd
> realize that the FOPEN call accepts a MAX_LINESIZE parameter, which,
> if not supplied, defaults to 1024:
>
> http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/u_file.htm#i1005018
>
> Examining Example 2 on that page explains much.
>
> The problem, therefore, isn't with the PUT_LINE call but in how you
> opened the file.
>
>
> David Fitzjarrell
Interesting that the doc specifies 1024 because the package header reads as follows:
utl_file.fopen(
file_location IN VARCHAR2, file_name IN VARCHAR2, open_mode IN VARCHAR2,
max_linesize IN BINARY_INTEGER DEFAULT NULL) RETURN file_type;
-- Daniel A. Morgan Oracle Ace Director & Instructor University of Washington damorgan_at_x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Group www.psoug.orgReceived on Wed Mar 05 2008 - 12:14:42 CST