Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!postnews2.google.com!not-for-mail
From: cjbj@hotmail.com (cjbj)
Newsgroups: comp.databases.oracle.server
Subject: Re: Oracle9i: How to pull LOB data via SQL*Plus ?
Date: 8 Sep 2004 23:15:02 -0700
Organization: http://groups.google.com
Lines: 35
Message-ID: <2ce8b846.0409082215.24512be@posting.google.com>
References: <4138944c$1@olaf.komtel.net> <2ce8b846.0409071810.66defe1@posting.google.com> <413eb8fa$1@olaf.komtel.net>
NNTP-Posting-Host: 202.92.75.130
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1094710503 28134 127.0.0.1 (9 Sep 2004 06:15:03 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 9 Sep 2004 06:15:03 +0000 (UTC)
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:224553

"André Hartmann" <andrehartmann@hotmail.com> wrote in message news:<413eb8fa$1@olaf.komtel.net>...
> > Can you tell us a little more on how you want to use the data?  If a
> > future version of SQL*Plus were going to support BLOBs, what
> > commands/interface would be useful to you?  Do you want the end result
> > to be a binary file?  Since SQL*Plus output is traditionally character
> > based would a column of, say, uuencoded or base64 data be better than
> > hex encoding?
> 
>   In the cutomer's database we have binary content stored in LOBs, the
> binary content being for example .gif files, CCD (Catia Cadam Draft) files
> (that is CAD models), MS Office documents or fractions of those, movie files
> and so on.
> 
>   The customer requests a shell script (nothing compiled like C/C++) that is
> able to issue a SQL statement that would select a particulat LOB, for
> example "SELECT CCDContents FROM CADLibrary WHERE Id=4711" (where
> CCDContents is a BLOB column and Id is the primary key) and store the result
> (the stream of bytes that makes the LOB) in a local file on the client
> computer.
> 
>    With a little convincing we might get away with a Java/JDBC application
> if it is not possible otherwise. But of course I have to evaluate first
> whether it is possible otherwise, that's why I am doing.
> 
>   We do not expect to be the LOB size around a tera byte. The argest
> files/LOBs we have seen in our environment so far are 500MB and its not
> likely to exceed 1GB per LOB in the future. TB is just not a use case (for
> us) so I dont think about that.
> 
> AH


Thanks for the feedback.

-- CJ