![]() | |
#11
| |||
| |||
|
|
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 |
#12
| |||
| |||
|
|
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 |
#13
| |||
| |||
|
|
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 |
#14
| |||
| |||
|
|
fitzjarr... (AT) cox (DOT) net wrote: 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 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 damor...@x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Groupwww.psoug.org- Hide quoted text - - Show quoted text - |
#15
| |||
| |||
|
|
fitzjarr... (AT) cox (DOT) net wrote: 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 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 damor...@x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Groupwww.psoug.org- Hide quoted text - - Show quoted text - |
#16
| |||
| |||
|
|
fitzjarr... (AT) cox (DOT) net wrote: 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 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 damor...@x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Groupwww.psoug.org- Hide quoted text - - Show quoted text - |
#17
| |||
| |||
|
|
fitzjarr... (AT) cox (DOT) net wrote: 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 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 damor...@x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Groupwww.psoug.org- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |