There is a pl/sql limit of 32k for long columns, you must parse it into a piece-wise transaction to pull all the information out of it. It's one of the reasons Oracle switched to LOB's... Long's are just so difficult to work with.
How to make it a piece-wise transaction is a little beyond my knowledge... maybe one of the other guru's can help here.
Nick
-----Original Message-----
From: Regina Harter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 03, 2001 3:03 PM
To: Multiple recipients of list ORACLE-L
Subject: Restrictions returning a Long field
Hi People,
Does anyone know of a database parameter (or any other reason) in a 7.1.6
database that would restrict the amount of data returned from a long
field? We have an application that won't show any data over 32K from a
long field. I'm thinking the problem is on the application side somewhere,
but the programmer responsible for it claims Oracle is only delivering 32K
of the long field to the application and we should look to the
database. The only thing I could find that sounds like it might even
remotely affect this is the db_block_buffers, and that's already at 5000,
but I don't have all the books and could have easily overlooked
something. Anyone have any ideas?
Regina
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Regina Harter
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
