Longchunksize Instead of Long Dictates Display Length of LOBs
(Doc ID 353764.1)
Last updated on FEBRUARY 27, 2025
Applies to:
SQL*Plus - Version 9.2.0.6 to 10.2.0.5 [Release 9.2 to Oracle10g]Information in this document applies to any platform.
Symptoms
SET LONGCHUNKSIZE dictates the display length of a LONG / CLOB, when it should be SET LONG.
The steps to reproduce are:
SQL> SET LONGCHUNKSIZE 80
SQL> SET LONG 132
SQL> SET LINES 132
SQL> SELECT TO_CLOB(LPAD('X', 100, 'X')) FROM dual;
TO_CLOB(LPAD('X',100,'X'))
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXX
From Oracle9i documentation, Release 2 (9.2).
https://docs.oracle.com/cd/B10501_01/server.920/a90842/ch13.htm#1012703
SET LONG {80|n}
Sets maximum width (in bytes) for displaying CLOB, LONG, NCLOB and XMLType values; and for copying LONG values. The maximum value of n is 2 gigabytes.
https://docs.oracle.com/cd/B10501_01/server.920/a90842/ch13.htm#1012724
SET LONGC[HUNKSIZE] {80|n}
Sets the size (in bytes) of the increments SQL*Plus uses to retrieve a CLOB, LONG, NCLOB or XMLType value.
So SET LONGCHUNKSIZE should not limit the display length of a LONG / CLOB.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |