dbTalk Databases Forums  

UTL_FILE.PUT_LINE

comp.databases.oracle.misc comp.databases.oracle.misc


Discuss UTL_FILE.PUT_LINE in the comp.databases.oracle.misc forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
amerar@iwc.net
 
Posts: n/a

Default UTL_FILE.PUT_LINE - 03-04-2008 , 01:18 PM







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?

Reply With Quote
  #2  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 01:36 PM






On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) net> wrote:
Quote:
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/B...e.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


Reply With Quote
  #3  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 01:36 PM



On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) net> wrote:
Quote:
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/B...e.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


Reply With Quote
  #4  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 01:36 PM



On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) net> wrote:
Quote:
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/B...e.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


Reply With Quote
  #5  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 01:36 PM



On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) net> wrote:
Quote:
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/B...e.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


Reply With Quote
  #6  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 09:10 PM



On Mar 4, 1:36*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Quote:
On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) 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/B.../b14258/u_file...

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
Gollee, he was so thrilled to get the answer he took the time to
delete his original post. I guess he was so busy deleting that piece
of work that he simply forgot to say, well, 'Thank you'.

What a guy.


David Fitzjarrell


Reply With Quote
  #7  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 09:10 PM



On Mar 4, 1:36*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Quote:
On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) 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/B.../b14258/u_file...

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
Gollee, he was so thrilled to get the answer he took the time to
delete his original post. I guess he was so busy deleting that piece
of work that he simply forgot to say, well, 'Thank you'.

What a guy.


David Fitzjarrell


Reply With Quote
  #8  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 09:10 PM



On Mar 4, 1:36*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Quote:
On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) 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/B.../b14258/u_file...

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
Gollee, he was so thrilled to get the answer he took the time to
delete his original post. I guess he was so busy deleting that piece
of work that he simply forgot to say, well, 'Thank you'.

What a guy.


David Fitzjarrell


Reply With Quote
  #9  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-04-2008 , 09:10 PM



On Mar 4, 1:36*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Quote:
On Mar 4, 1:18*pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) 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/B.../b14258/u_file...

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
Gollee, he was so thrilled to get the answer he took the time to
delete his original post. I guess he was so busy deleting that piece
of work that he simply forgot to say, well, 'Thank you'.

What a guy.


David Fitzjarrell


Reply With Quote
  #10  
Old   
DA Morgan
 
Posts: n/a

Default Re: UTL_FILE.PUT_LINE - 03-05-2008 , 12:14 PM



fitzjarrell (AT) cox (DOT) net wrote:
Quote:
On Mar 4, 1:18 pm, "ame... (AT) iwc (DOT) net" <ame... (AT) iwc (DOT) 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/B...e.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@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.