Re: DIRECTORIES and BFILE problems

From: Hexathioorthooxalate <ruler_at_removemetoemail.clara.co.uk>
Date: Fri, 4 Mar 2005 14:42:29 -0000
Message-ID: <1109947331.30174.0@lotis.uk.clara.net>

"D Rolfe" <dwrolfeFRUITBAT_at_orindasoft.com> wrote in message news:rOBVd.48733$Z14.36488_at_news.indigo.ie...
>

> 2. Use BFILE to access (not store!) the file by
> 2(a) Running your program on the same machine as the database server.
> or
> 2(b) Creating the BFILE pointers and then using some other process to
> copy the file to the DB server before anyone notices it's not really
> there.
>
>

Or 2(c), mapping a drive and having both the client and database server write to and read from the same mapped drive. This way the file referred to by the BFILE can be on the DB server but it need not be.

I note that the original poster is running Oracle on a WinBox - a cautionary note that has caught me out before should you go down this route. The database can only access drives that it can see when the database instance is started, it cannot access drives that have been mapped subsequently. Put another way, is the Z: drive is mapped before Oracle starts up, and it is on a different machine/storage array etc, the database instance can access files from the share via BFILE/DBMS_LOB or whatever. If the Z: drive is mapped once the database instance has started, you cannot.

Regards
Hex Received on Fri Mar 04 2005 - 08:42:29 CST